Understanding Hosting Plans, VMM clouds and multi-tenancy
This could be the first post inside a series of blogs related to Hosting Plans in Azure Pack and exactly how things are mapped towards VMM management servers, VMM clouds poor multi-tenancy.
To explain to you an overview, look into the following figure:
In it, we're dealing with a single management stamp (VMM management server) made up of several scale units, a VMM cloud and is also presented for the service management API through Service Provider Foundation.
Note that were not discussing any specific Active Directory Domain here, nor specific subnets.
This is actually a high-level review of the dependencies the thing is that when coping with a hosting plan in Azure Pack to produce VM Clouds.
Explanation
The picture contains anything you are able to given to a VMM cloud, which is actually the basis of any hosting plan that is certainly offering VM clouds.
In VMM, we can easily create host groups containing our virtualization hosts. These host groups contains several settings, policies and configuration items according to your input. In the example above we have now designed the host group structure to reflect our physical locations, Copenhagen and Oslo – beneath the default “All hosts” group in VMM.
Further, we now have added some logical networks that are show these hosts, so we are able to assume were using SMB, clustering, live migration, management, PA network (NVGRE) and front-end like the involved Hyper-V nodes and clusters we have been managing.
Since i will be using NVGRE with WAP, the PA network is added like a logical network for the VMM cloud. This will be covered in details in the later writing.
We in addition have some port classifications and that is an abstraction with the virtual port profiles, so that people can present those to a cloud and classify the VM NICs to get a desired configuration.
Storage classification is used within a similar way in order that the storage we add to your cloud would be the only storage that ought to be used for our VHDs, matching the HW profiles on the VM templates. The host groups added ought to be associated with these classifications.
To present the library resources from the tenant portal for VM deployments etc, we have to add no less than one read-only library share that will contains vhds, templates, profiles, scripts and much more. If using VM roles in WAP, resource extensions is found this library too.
The VMM Cloud abstracts the information presented resources, add read-only library shares and specifies the proportions of this cloud that defines the disposable amount of resources to take through plans in WAP.
Service Provider Foundation is often a multi-tenant REST Odata API for System Center so that IaaS, and is also the endpoint that connects the Service Management API in Azure Pack for a VMM management server(s) and VMM clouds.
Have the figure as I uses this as being a reference, along with covering the details from the upcoming blogs as well.
Understanding Hosting Plans, VMM clouds and multi-tenancy
This could be the first post inside a series of blogs related to Hosting Plans in Azure Pack and exactly how things are mapped towards VMM management servers, VMM clouds poor multi-tenancy.
To explain to you an overview, look into the following figure:
In it, we're dealing with a single management stamp (VMM management server) made up of several scale units, a VMM cloud and is also presented for the service management API through Service Provider Foundation.
Note that were not discussing any specific Active Directory Domain here, nor specific subnets.
This is actually a high-level review of the dependencies the thing is that when coping with a hosting plan in Azure Pack to produce VM Clouds.
Explanation
The picture contains anything you are able to given to a VMM cloud, which is actually the basis of any hosting plan that is certainly offering VM clouds.
In VMM, we can easily create host groups containing our virtualization hosts. These host groups contains several settings, policies and configuration items according to your input. In the example above we have now designed the host group structure to reflect our physical locations, Copenhagen and Oslo – beneath the default “All hosts” group in VMM.
Further, we now have added some logical networks that are show these hosts, so we are able to assume were using SMB, clustering, live migration, management, PA network (NVGRE) and front-end like the involved Hyper-V nodes and clusters we have been managing.
Since i will be using NVGRE with WAP, the PA network is added like a logical network for the VMM cloud. This will be covered in details in the later writing.
We in addition have some port classifications and that is an abstraction with the virtual port profiles, so that people can present those to a cloud and classify the VM NICs to get a desired configuration.
Storage classification is used within a similar way in order that the storage we add to your cloud would be the only storage that ought to be used for our VHDs, matching the HW profiles on the VM templates. The host groups added ought to be associated with these classifications.
To present the library resources from the tenant portal for VM deployments etc, we have to add no less than one read-only library share that will contains vhds, templates, profiles, scripts and much more. If using VM roles in WAP, resource extensions is found this library too.
The VMM Cloud abstracts the information presented resources, add read-only library shares and specifies the proportions of this cloud that defines the disposable amount of resources to take through plans in WAP.
Service Provider Foundation is often a multi-tenant REST Odata API for System Center so that IaaS, and is also the endpoint that connects the Service Management API in Azure Pack for a VMM management server(s) and VMM clouds.
Have the figure as I uses this as being a reference, along with covering the details from the upcoming blogs as well.
Understanding Hosting Plans, VMM clouds and multi-tenancy
0 comments:
Post a Comment