Cloud Computing vs Grid Computing

For starters, both cloud computing and grid computing are used to provide services through sharing capabilities and resources. And they are very similar concepts which can be easily confused. However, there are some key differences that can distinguish them properly. Here we will talk about cloud computing vs grid computing key differences and help you to understand them more completely.

 Cloud Computing Architecture

What are Cloud Computing and Grid Computing?

To better understand cloud computing vs grid computing differences, we really need to know the basic knowledge of these two technologies. Here introduces cloud computing and grid computing basics in simple terms:

Cloud Computing Tutorial: Definition and Architecture

Cloud computing can be defined as delivering computing services - servers, storage, databases, networking, software, and more - over the Internet, without having the physical computing resources at the customer location. This has decreased the hardware and software demand from the customer’s side. All the customer needs to do is to run the cloud computing systems interface software that is used as simple as the Web browser. Now there are public, private, and hybrid cloud computing that can be deployed. Fore more information about these three cloud, please read Popular ToR and ToR Switch in Data Center Architectures

As shown below, cloud computing consists of two components: front end and back end, which are connected together through the Internet. The front end is at the customer or computer side where end users interact with the cloud. The back end is the cloud section, which involves all the resources needed for providing cloud computing services. It often houses virtualized servers, data storage, virtual networks composed of various network switches, etc.

 Grid Computing Architecture

Grid Computing Tutorial: Definition and Architecture

Grid computing is a loose distributed network of massive computers that can be called to perform dedicated tasks together, allowing each computer to run its independent tasks. Therefore it can solve problems that are too big for a supercomputer and maintain the flexibility to process numerous smaller problems at the same time. In the grid computing network, each computer is connected by parallel nodes that form a computer cluster, which runs on an operating system, Linux or free software.

Cloud Computing vs Grid Computing: What’s the Difference?

Seen from the above, the definition and architecture of cloud computing and grid computing are totally different, which further leads to differences on such aspects as functions, applications, etc. This following chart lists cloud computing vs grid computing differences in details for your reference:

Cloud Computing vs Grid Computing, Which Do You Prefer?

Both cloud computing and grid computing are popular in the industry now, for they each has their own advantages and use cases. To conclude, cloud computing is ideal for applications where flexibility, ease-of-use and security are needed. Whereas grid computing is cheaper, more efficient and fail-safe. So cloud computing vs grid computing, which do you prefer? The answer really depends on what’s your need and how many resources you’ve got.

Originally published at http://www.fiber-optic-transceiver-module.com/cloud-computing-vs-grid-computing-difference.html

OpenvSwitch and OpenFlow: What Are They, What’s Their Relationship?

As software defined networking (SDN) becomes popular in high-bandwidth and dynamic applications (for example, cloud computing), related terms such as OpenvSwitch and OpenFlow are talked a lot by IT technicians. Though they have been introduced for a while, OpenvSwitch and OpenFlow still confuse people in some aspects. And the most frequently asked question is what’s the relationship and difference between OpenvSwitch and OpenFlow. Here we will cover these topics on what is OpenvSwitch, what is OpenFlow, and OpenvSwitch vs OpenFlow.

OpenvSwitch vs OpenFlow: OpenFlow Tutorial

Traditionally, networking hardwares from different vendors often have special configuration and management systems, which limits the interacting between routers and switches from different manufacturers. To solve this, OpenFlow is created as an open programmable network protocol for configuring and managing Gigabit network switches from various vendors. It enables us to offload the control plane of all the switches to a central controller and lets a central software define the behavior of the network. Thus network administrators can use OpenFlow software to manage and control traffic flow among different branded switching equipments.

How OpenFlow Works

How Does OpenFlow Work?

OpenFlow generally consists of three components: OpenFlow controller, OpenFlow protocol and a chain of flow tables set up on the OpenFlow switch (as shown above). The OpenFlow protocol is like a media for the controller talking securely with OpenFlow switch. The OpenFlow controller can set rules about the data-forwarding behaviors of each forwarding device through the OpenFlow protocol. Flow tables installed on the switch often stores a collection of flow entries. So when a data packet arrives at the OpenFlow switch, the switch will search for matched flow entries in the flow tables and executes corresponding actions. If no match is found, an inquiry event will sent to the OpenFlow controller which then responds with a new flow entry for handling that queued packet.

OpenvSwitch vs OpenFlow: OpenvSwitch Tutorial

OpenvSwitch, sometimes abbreviated as OVS, is an open-source OpenFlow switch that works as a virtual switch in the virtualized environments such as KVM. It also used as a multilayer software for interconnecting virtual devices in the same host or between different hosts. Currently, OpenvSwitch can run on any Linux-based virtualization platform, which includes: KVM, VirtualBox, Xen, Xen Cloud Platform, XenServer.

OpenvSwitch Architecture

OpenvSwitch has eight core elements: ovs-vswitchd, Linux kernel module, ovsdb-server, ovs-dpctl, ovs-vsctl, ovs-appctl, ovs-ofctl, and ovs-pki. Ovs-vswitchd is a daemon that implements the switch. Linux kernel module is for flow-based switching. Ovsdb-server is a lightweight database server. Ovs-dpctl is a tool for configuring the switch kernel module. Ovs-vsctl is a utility for querying and updating the configuration of ovs-vswitchd. Ovs-appctl is a utility that sends commands to running Open vSwitch daemons. Ovs-ofctl is a utility for controlling the OpenFlow features of OVS. Ovs-pki is a utility for creating and managing the public-key infrastructure.

OpenvSwitch vs OpenFlow: What's Their Relationship?

OpenvSwitch and OpenFlow are both used for SDN application. OpenFlow is one of the first SDN standards. OpenvSwitch is an OpenStack SDN component. As to their relationship, OpenvSwitch is one of the most popular implementations of OpenFlow. Apart from OpenFlow, OpenvSwitch also supports other switch management protocols such as OVSDB (Open vSwitch Database Management Protocol).

Originally published at http://www.fiber-optic-transceiver-module.com/openvswitch-vs-openflow-what-are-they-whats-their-relationship.html

Rack Cable Manager for Data Center Cable Management

As plenty of devices and cables are added into data center cable racks, cable management in racks becomes one of the most pressing challenges for data center managers. To avoid rack cables looking like messy spaghetti, rack cable manager has long been an ideal solution to keep rack cables properly organized. But there are so many kinds of rack cable managers in the market, do you know which one to use for a specific situation? Here discusses some popular rack cable managers and their respective applications.

Cable Management Sections for A Rack

To better understand different kinds rack cable managers, we’d better to know the four cable management sections of a rack. Which are horizontal cable management, vertical cable management, inside of the rack cable management and top of the rack cable management. Horizontal cable managers and vertical cable managers are used for horizontal and vertical cable managements respectively, while copper/fiber patch panels and fiber raceway systems are for inside and top of the racks. The following parts will introduce various cable organizer for these four cable management sections.

Horizontal Rack Cable Manager

Horizontal rack cable manager is often used to manage cables in the front of racks and draw cables away from equipment neatly. It is usually one or two rack units high. Now there are many types of horizontal rack cable managers in the market, which are mainly divided into finger duct rack cable manager, D-ring horizontal cable manager and horizontal cable manager with brush strip. Among them, finger duct rack cable manager offers fingers and pass-through holes for routing rack cables and reducing cable strains, D-ring cable manager provides an “open” and efficient way to manage cables, brush strip manager is mainly used for allowing cables to be passed from the front to the rear of the rack. For more information on these three rack cable managers, read Selecting the Right Horizontal Cable Manager.

Horizontal Rack Cable Manager Types

Vertical Rack Cable Manager

Vertical rack cable managers are used for providing vertical pathways for cable bundles in the rack. Now the common types of vertical rack cable managers are D-ring vertical cable manager, vertical cable manager with bend radius fingers, and open frame rack vertical cable managers. The first one is a cost-effective solution for organizing and routing cable bundles. The second one is designed to maintain cable bend radius effectively. And the last one is available in single-sided and dual-sided models, which are specially used on the sides of open frame racks. For more information on these three rack cable managers, read Vertical Rack Cable Management: Where to Start?

Vertical Rack Cable Manager Types

Fiber Raceway System

Fiber raceway system is used to route and protect cables above racks. It consists of fiber raceway ducts, ladder racks, various interfaces, elbows and supports, etc. The fiber raceway duct often available in four sizes from 2"x 2" to 4" x 12". The following video shows how to set up a good fiber raceway system for top of the rack cable management:

Copper/Fiber Patch Panel

Copper/fiber patch panel is used to manage cables in the rack. It is often a board or enclosure which allows you to connect cables in various combinations with a number of copper/fiber sockets. Copper/fiber patch panel helps to keep things organized and contained, therefore cables in the rack won’t hang out all over the place. For more information about copper/fiber patch panel, read How to Use Fiber Patch Panel for Better Cable Management and How to Select the Suitable Copper Patch Panel?

Conclusion

Horizontal/vertical rack cable managers, fiber raceways and copper/fiber patch panels are good ways to manage and route your rack cables to sure everything is easy to access and identify. It is suggested to select proper rack cable managers according to your needs during set-up and installation of network cabling system.

Originally published at http://www.fiber-optic-transceiver-module.com/rack-cable-manager-for-data-center-cable-management.html