Learn about the basics of private vs. public clouds.
- [Man] Alright, let's talk about private cloud platforms. What's important to understand about private clouds is that private clouds are only for your use. You own the hardware, you own the software, you're responsible for maintaining it, you're paying for all aspects of it, and ultimately, that is both the advantage and the disadvantage, and we'll find out more about that later in this video. Public clouds rent resources, and they own the hardware. So, if we're leveraging Amazon, or Microsoft, or Google in their public cloud, they're going to basically rent us the resources, we can allocate a virtual server, and we can leverage that virtual server out of their stack.
They own the hardware and software. We don't control it, other than the fact that we're provided a management console for the virtual systems that they provide. So, private clouds provide you with control, but you have to pay for everything. Private clouds are enterprise owned or leased, where community clouds are shared infrastructure for a specific community. Best to describe a university with several different organizations. It may share the same cloud, even though they're different, distinct organizations under the same community infrastructure.
Perhaps a cooperative or a farm cooperative may share a community cloud. Public clouds are sold to the public, and they provide megascale infrastructure. In other words, they can scale up to any number of users that you need, any number of virtual systems that you need, and you only pay for what you use. Hybrid clouds are a composition of two of more clouds. Typically, private and public clouds. So, when we leverage a private cloud with the public cloud, we typically call those hybrid clouds. There are two flavors of private clouds.
Internal, you own the hardware, you own the software, it's on premises, on your premises, typically your data center. An example would be Vmware. External, you don't own the hardware, you don't own the software, and it's remotely managed through a remotely managed location. An example would be Amazon Virtual Private Cloud. We have two types of clouds where one could be on premise in our data center, we control it and we can see the servers, and an external private cloud or a virtual private cloud, it'll exist on a public cloud provider, such as Amazon, but we don't own the hardware and software, but we control it directly, more so than in a public cloud kind of scenario.
Private clouds provide you with the ability to leverage the value of cloud computing using on-premises systems that are directly controlled by enterprise IT. They provide you with the ability to better utilize existing computer resources, thus reducing costs sometimes. So in other words, private clouds may be effective if we've already made the investment in the hardware and software resources, we can't sell those resources on Craigslist, so, we go ahead and leverage them as private clouds, and since we own them, we're repurposing them for a more efficient purpose, leveraging as a private cloud. The ability to provide better scalability through virtualization, or through "cloud bursting," the ability to leverage public cloud instances for a period of time, but returning to the private cloud because we prefer to run on a private infrastructure, and in some instances a public infrastructure, in other instances, we need to be able to choose between the two.
Availability of open-source solutions, and we have OpenStack and CloudStack. Less scary than public clouds for many enterprises. Find they have a control thing. They want to control their cloud, and private clouds provide them the ability to do that because of the control issue.
- Private cloud benefits
- Considering the costs
- Determining compatibility
- Assessing security and governance
- Reviewing OpenStack
- Reviewing Microsoft Private Cloud
- Reviewing VMware vCloud Suite
- Reviewing Apache CloudStack