As you know we have a cloud presence; we have had one for several months. Now we are evaluating the cloud to determine whether to maintain that cloud presence or move back to our local data center. We also documented some early teething problems within this cloud presence. What should be our evaluation the cloud criteria? Now that our data center is moved and fully functional, should we keep our cloud presence? Continue reading Evaluating the Cloud: Keeping your Cloud Presence
The Virtualization Practice recently moved their systems to the Cloud, being cost conscious we chose one of the public clouds to use. The reality of such a move is much different than the hype. We expected stellar support, better performance, improved security, improved DR, and 5 9s uptime, and the hypervisor is a commodity. In essence, it should be better than we could do ourselves. That is the promise of the cloud; the hype of the cloud. What we have seen is something far different. Continue reading Public Cloud Reality is Much Different than the Hype
There has been quite a lot of twitter traffic about the FrankenCloud recently: A cloud with more than one type of hypervisor underneath it. One example, is to build a cloud using Hyper-V three and vSphere, both managed through Microsoft System Center. Another example, is to build a cloud using Hyper-V, KVM, and vSphere all managed through HotLink. But is this a desired cloud topology? Continue reading Enter the FrankenCloud: Or Do we really care about the Hypervisor?
One of the decisions faced by anyone that wishes to have a cloud presence is what will be moved to the cloud, why, and whether or not there is a service that can be used instead of using virtual machines. Give The Virtualization Practice’s case, we plan on moving our customer facing VMs to the cloud, but what are those machines? The most important are a Web Server with a split LAMP stack, a Mail Server, and DNS. Continue reading Moving to the Cloud as a Service or as a Machine