In this day and age of cloud computing, this article’s headline may come as a bit of a shock to many of you. Yes, the mainframe is still a thing. And IBM’s newest is a beast of a machine, capable of over 2.5 billion transactions a day, with real-time encryption built in.
Articles Tagged with Private Cloud
There has been a great deal of passionate debate over the last few months within the OpenStack community. There is one camp that is advocating for building APIs that are compatible with Amazon Web Services (AWS) APIs, while the other camp argues for augmenting the existing OpenStack APIs. Those in favor of making the APIs more compatible with AWS are focused on standardization and compatibility between OpenStack and AWS. Standardizing on the AWS APIs makes moving workloads between OpenStack and AWS clouds easier, thus giving OpenStack a competitive advantage over other private cloud stacks. It also makes it easier for customers to move workloads off of AWS (public cloud) to OpenStack (private cloud) for customers wanting to deploy on bare metal machines, keep critical data out of the public cloud, or have the flexibility to target a cloud endpoint based on their customers’ desires (for those delivering solutions to customers outside of their enterprise).
Is the cloud too much of a good thing? Virtualization and cloud computing have been one of the biggest technological advancements of the twenty-first century and they continue to grow at an amazing pace. Cloud computing has started to obtain mass appeal in corporate data centers as it enables the data center to operate like the Internet through the process of enabling computing resources to be accessed and shared as virtual resources in a scalable manner. Each day there seems to be a new announcement or press release about a new product or service that has been released utilizing some form of cloud computing, and I do not see this trend changing anytime soon.
There are different public cloud use cases. Here at The Virtualization Practice we moved our datacenter from the north to the south part of the country and utilized the cloud to host the workloads during the transition. Edward Haletky, yesterday posted about Evaluating the Cloud: Keeping your Cloud Presence and presented the question and his thoughts of is it worth staying in the cloud or bringing the data home.
How do you define a hybrid cloud? My idea of what a hybrid cloud is does not seem to match what I find as the current definition of a hybrid cloud.
Soon the backup power will be available for our new datacenter and the redesign to make use of VMware vCloud Suite is nearing completion. Soon, our full private cloud will be ready for our existing workloads. These workloads however now run within a XenServer based public cloud. So the question is, do we stay in a poorly performing public cloud (mentioned in our Public Cloud Reality series) or move back to our own private cloud? As the Clash put it “Should I Stay or Should I Go Now.”