VMware VMWARE CLOUD DIRECTOR 1.0 - TECHNICAL NOTE Spécifications Page 8

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 80
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 7
TECHNICAL WHITE PAPER / 8
VMware vCloud Director 5.1 Evaluation Guide
VMware vCenter Server
Each vCloud Director cell can connect to one or more vCenter Server instances to access resources for running
workloads. Each attached vCenter Server instance provides resources, such as CPU and memory, which can be
leveraged by vCloud Director.
vSphere Hosts
VMware vSphere ESXi™ hosts provide the compute power for vCloud Director. vSphere hosts are placed in
groups of resources, such as clusters or resource pools. These groups and their associated storage are then
made available to vCloud Director.
vCloud Networking and Security Manager
vCloud Networking and Security Manager provides a central point of control for managing, deploying, reporting,
logging and integrating vShield as well as third-party security services. Working in conjunction with
vCenter Server, vCloud Networking and Security Manager enables role-based access control and separation
of duties as part of a unified framework for managing virtualization security. To support the automated
management of vCloud Networking and Security Edge Gateway in a vCloud Director environment, an instance
of vCloud Networking and Security Manager is required for each vCenter Server attached to vCloud Director.
vCloud Director Logical Components
Server virtualization abstracted away the concept of the physical server. This removed the complexity of specific
storage or network interfaces and replaced them with a generalized, abstracted hardware layer that was
presented to one or more virtual machines.
vCloud Director takes this abstraction to a new level and creates a virtual datacenter. Rather than individually
selecting a target vSphere host or cluster, datastore and network port group, users deploy workloads into
preallocated containers of compute, storage and networking resources known as virtual datacenters (VDCs).
This dramatically simplifies the provisioning process and removes many of the manual configuration steps. To
the consumer, these are seemingly infinite and elastic pools of resource that can be expanded quickly and easily.
In creating these VDCs, corporate IT has the option to oer multiple service-level alternatives to optimize the use
of compute and storage resources. For example, all development users can be placed into a VDC containing
resources with performance characteristics lower than those of a production environment. Meanwhile, UAT/QA
users can operate in a VDC with resource performance characteristics much closer to production specifications.
vCloud Director introduces a number of logical components to support the notion of a VDC that is presented to
end users. The following are the main logical components:
Provider Virtual Datacenter
A provider VDC is a logical grouping of compute and storage resources. The provider VDC groups together a set
of vSphere hosts and a set of one or more associated datastores. This logical grouping is then made available for
consumption by organizations. Provider VDCs can leverage the Storage Profiles feature of vSphere to provide
multiple classes of storage to diering organizations.
Organizations
One of the key capabilities of a vCloud Director private cloud is secure multitenancy. The organization concept is
one of the key building blocks of this. A vCloud Director organization is a unit of administration that represents a
collection of users and user groups. An organization also serves as a security boundary, because users from a
particular organization have visibility only to other users and resources allocated to that organization.
Organizations can be as simple as dierent functional areas inside a business or as complex as unique
companies being hosted by a provider.
Organization Virtual Datacenter
An organization VDC is a logical grouping of resources from one or more provider VDCs that an organization is
allowed to access. Depending on back-end (provider VDC) configuration and needs of the organization, one or
more sets of resources backed by dierent provider VDCs might be present. This enables dierent performance,
SLA or cost options to be available to organization users when deploying a workload.
Vue de la page 7
1 2 3 4 5 6 7 8 9 10 11 12 13 ... 79 80

Commentaires sur ces manuels

Pas de commentaire