You might be asking yourself what’s new with cloud adoption in 2015. This year cloud adoption might actually hit an all time high.
Those cloud providers with a dog in the fight believe Microsoft ending its support for Windows Server 2003 this July will greatly bolster cloud adoption among SMBs. They are eager to portray cloud as the most affordable way for companies with limited resources to refresh their IT infrastructure.
Get ready for this one… not all multi-cloud offers are created equally. Here are a few ways ‘multi-cloud’ is being used to describe what’s happening with (and in) the multiple clouds.
Multi-cloud – multiple clouds, each hosting a different application belonging to the same organization
In this case, the commonality between clouds is most likely the person managing the cloud. This person is probably jumping from one user interface to another – Microsoft, AWS, Joyent for example. He or she is probably going through the hassle of learning (and keeping him or herself up to date!) with all the user interfaces as well as the terminology and the tool chain of all the clouds involved. Instead, this person could do with a consistent interface between all these clouds, to help simplify the management process and speed up the deployment and the day-to-day operation of his applications across multiple clouds.
Last week Datapipe announced it has acquired infrastructure as a service provider GoGrid. The acquisition will boost Datapipe’s quest to become a global provider of managed services across workload types.
Datapipe has made some interesting and successful moves in the last year. It acquired Layered Tech to expand its AWS expertise and has become a leading Systems Integrator of cloud native apps. Now with the acquisition of GoGrid, it focuses on being the best cloud provider for the common problems of handling Big Data in the cloud.
Chef are industry leaders in IT automation, offering significant benefits such reducing the time and effort, as well as risk of manual error, involved in building, configuring and managing application stacks. For the DevOps community, this is great.
Chef’s a fantastic tool that most people want to dig into straight away. First, though, you have to set it up and configure the Chef servers and clients including all the various dependencies involved. Then you have to manage, pull and execute Chef cookbooks. This is in many cases a repetitive task. The good news is you can manage Chef more easily by having Flexiant Concerto carry out these tasks for you. Here is how.
To overcome cloud networking scalability challenges as outlined in a previous blog post, cloud service providers look to solutions like Layer 2, VLANs and Layer 3. Discussed below are the issues service providers face with Layer 2.
Layer 2 issues
One of the first challenges in scaling the cloud provider’s network comes at layer 2.
To explain this, it is first necessary to recap how a switched Ethernet network works. Each network interface card (physical or virtual) participating in a layer 2 network has a unique MAC address. Each packet contains a header (the MAC header) containing the source and destination MAC address of the sending and receiving network interface. The switches on the layer 2 network learn the source addresses of any packet passing through them. When a switch comes to forward a packet to a given destination, it looks up that destination in the forwarding table that it has learnt, and if an entry is present, the packet is forwarded to that port. If an entry is not present (or if the packet is a broadcast packet), the packet is forwarded to all ports. Such forwarding to all ports is to be avoided as they use bandwidth on each port as well as switch capacity. It is thus vital the forwarding table can contain entries for all source MAC addresses in use.