VMware vCloud Automation Center training @ VEPSUN Technologies
Download as PPTX, PDF1 like429 views
The document discusses VMware vCloud Automation Center 6.0, focusing on its alignment with cloud computing standards as defined by NIST. It outlines the different types of cloud models (private, public, community, and hybrid) and emphasizes the importance of automation, orchestration, and resource management in delivering cloud services. Additionally, it highlights VMware's commitment to evolving cloud standards and provides insights into the operational aspects and benefits of a software-defined data center.
VMware vCloud Automation Center training @ VEPSUN Technologies
- 1. VMware vCloud Automation Center 6.0 Session - I 8– Sep– 2014 Aditya Samal
- 2. Course Introduction VMware vCloud Automation Center 6.0 (Install , Configure & Mange)
- 3. Importance
- 5. References
- 6. What is Cloud computing ? Cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the Internet). Clouds can be classified as public, private or hybrid. According to the National Institute of Standards and Technology (NIST), the key components of a cloud are on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. VMware aligns with the definition of cloud as elastic, lightweight entry and exit, available over Internet protocols, and running on a shared infrastructure A cloud always starts with a shared, virtual infrastructure. If any resource is dedicated to only one customer, you have a managed hosting platform, not a cloud infrastructure. Similarly, it is not considered a cloud if there are manual procedures that must be performed by the cloud administrator or service provider to provision cloud resources following a consumer request. This is why workflow automation and orchestration are included as part of a vCAC.
- 7. The VMware vCloud blueprint follows these basic NIST requirements as the foundation for an IaaS cloud: A cloud must be built on a pooled, virtual infrastructure. Pools include not only CPU and memory resources but also storage, networking, and associated services. •The cloud should provide application mobility between clouds, allowing the consumer to enter and leave the cloud easily with existing workloads. The ability to use existing consumer tools to migrate workloads to or from the cloud is highly desirable. Mobility of workloads between clouds requires cross-cloud resource management. •The cloud should be open and interoperable, allowing the consumption of cloud resources over open, Internet-standard protocols. Access to cloud resources does not require any other specific network protocols or clients. •Cloud consumers should pay only for resources they consume or commit to consuming. •The cloud should be a secure, trusted location for running cloud consumer workloads. Cloud consumers should have the option and the ability to protect their cloud-based workloads from data loss. •Cloud consumers are not responsible for the maintenance of any part of the shared infrastructure and do not need to interact with the cloud provider to maintain the infrastructure. They are not responsible for storage and network maintenance, ongoing cloud infrastructure patches, or business continuity activities. The cloud should be available to run high-availability workloads, and any faults occurring in the cloud infrastructure should be transparent to cloud consumers as a result of built-in availability, scalability, security, and performance guarantees.
- 8. VMware Alignment to Standards VMware continues to develop technologies that align with evolving cloud standards as defined by NIST and other global standards organizations. vCloud solutions focus on the following areas: •People – People who develop solutions, architect the design, operate the implementation, and consume the resources. •Process – Processes for architects, operators, and consumers. •Technology – Alignment with successful design, deployment, and integration considerations. VMware technologies address the relevant areas within the standards. Standards are still evolving for private, public, community, hybrid, and other types of clouds. vCAT focuses on the most common core design areas. The technology is the same, but operations and vCloud resource consumption varies according to the type of vCloud, the type of vCloud provider, and specific consumer requirements. • A private vCloud is operated by an organization and secured behind a firewall. •A public vCloud is generally accessible to users on the Internet. •A community vCloud is a specific public vCloud use case where access is limited to specified groups who share a common set of requirements. •A hybrid vCloud is characterized by a connection between multiple vCloud instances. Typically, there is a bridge between two private vCloud instances that has a dedicated and secured connection. The underlying network resides behind an Internet-facing firewall. As cloud computing continues to evolve, there will be many cloud definitions. The information in this toolkit is a valuable aid in support of your vCloud projects, regardless of your chosen definition
- 9. vCloud Definitions Private cloud: A private vCloud (also known as an internal vCloud.) operates on private networks, where resources are accessible behind the firewall by a single company. In many cases, all the tenants share one legal entity. For example, a university might offer IaaS to its medical and business schools, or a company might do the same for various groups or business units. The private vCloud can be managed by the enterprise and hosted on premise or operated on a dedicated infrastructure provided by a vCloud service provider or systems integrator. In any case, a private vCloud must conform to the organizational security constraints. Public cloud: A public vCloud offers IT resources as a service through external service providers and is shared across multiple organizations or the Internet. This can be viewed as a vCloud infrastructure that is operated by one organization for use by multiple, legally separated organizations. A public vCloud is provisioned for open access and might be owned, managed, and operated by one or more entities. A public vCloud provider might also support a private, community, or hybrid vCloud Hybrid cloud: A hybrid vCloud combines the benefits of the private and the public vCloud, with flexibility and choice of deployment methods. A hybrid vCloud consists of multiple, linked vCloud infrastructures. These distinct vCloud infrastructures can be private, community, or public, they but must meet a set of requirements defined by the providers and agreed to by the consumers. Connecting these vCloud instances requires data and application mobility as well as management. When load-balancing between vCloud instances (cloud bursting), use a consistent monitoring and management approach when migrating an application or data workload. For the theory behind cloud bursting see the document titled Cloud Bursting
- 10. vCloud Definitions Community cloud: A Community vCloud is a specific public vCloud use case where the cloud is shared, and typically owned, by a group of organizations with a common set of requirements. In many cases, the organizations also include some level of legal separation. Community vCloud resources are shared, with some parts under central control and other parts with defined autonomy. A vCloud built for government, education, or healthcare might be an example of a community vCloud. A community vCloud can be offered by a traditional service provider, by a member of the community, or by a third-party vendor and hosted on one or more sites. It can be placed on-premise at one or more of the organizations’ sites, off-premise at a vCloud provider site, or both on- and off-premise.
- 11. Solution Area to Technology Mapping When considering various technology solutions for your vCloud architecture, evaluate the solution and operational requirements to provide justification for the proposed solution. As VMware continues to develop Software Defined Data Center technologies, we will update the matching Infrastructure as a Service components
- 12. Solution Area to Technology Mapping
- 14. Software-Defined Data Center (1)
- 15. Software-Defined Data Center (2)
- 16. Software-Defined Data Center Benefits (1)
- 17. Software-Defined Data Center Benefits (2)
- 19. vCloud Automation Center Resources