Skip to content

Commit becf969

Browse files
author
George Wallace
committed
Merge branch 'release-preview-vmware' of https://github.com/Paul2658/azure-docs-pr 
2 parents e8cc9bc + 575dede commit becf969

File tree

123 files changed

+5463
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

123 files changed

+5463
-0
lines changed

‎articles/azure-vmware/concepts-identity.md

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Concepts - identity and access for Azure VMware Solution by Virtustream
3+
description: Learn about the identity and access concepts of Azure VMware Solution by Virtustream.
4+
services:
5+
author: v-jetome
6+
7+
ms.service: vmware-virtustream
8+
ms.topic: conceptual
9+
ms.date: 07/29/2019
10+
ms.author: v-jetome
11+
ms.custom:
12+
13+
---
14+
15+
# Azure VMware Solution (AVS) by Virtustream identity concepts
16+
17+
A vCenter server and NSX-T manager are provisioned when a private cloud is deployed. You use vCenter to manage virtual machine workloads and NSX-T manager to extend the private cloud software-defined network.
18+
19+
Access and identity management use CloudAdmin group privileges for vCenter and restricted administrator rights for NSX-T manager. This policy ensures that your private cloud platform can be upgraded automatically, delivering the newest features and patches on a regular cadence. See the [private cloud upgrades concepts article][concepts-upgrades] for more details on private cloud upgrades.
20+
21+
## vCenter access and identity
22+
23+
Privileges in vCenter are provided through the CloudAdmin group. That group can be managed locally in vCenter, or through integration of vCenter LDAP single sign-on with Azure Active Directory. You're provided with the ability to enable that integration when you deploy a private cloud.
24+
25+
The CloudAdmin and CloudGlobalAdmin privileges are shown in the table below.
26+
27+
| Privilege Set | CloudAdmin | CloudGlobalAdmin | Comment |
28+
| :--- | :---: | :---: | :--: |
29+
| Alarms | A CloudAdmin user has all Alarms privileges for alarms in the Compute-ResourcePool and VMs. | -- | -- |
30+
| Auto Deploy | -- | -- | Virtustream does host management. |
31+
| Certificates | -- | -- | Virtustream does certificate management. |
32+
| Content Library | A CloudAdmin user has privileges to create and use files in a Content Library. | Enabled with SSO. | Virtustream will distribute files in the Content Library to ESXi hosts. |
33+
| Datacenter | -- | -- | Virtustream does all data center operations. |
34+
| Datastore | Datastore.AllocateSpace, Datastore.Browse, Datastore.Config, Datastore.DeleteFile, Datastore.FileManagement, Datastore.UpdateVirtualMachineMetadata | -- | -- |
35+
| ESX Agent Manager | -- | -- | Virtustream does all operations. |
36+
| Folder | A CloudAdmin user has all Folder privileges. | -- | -- |
37+
| Global | Global.CancelTask, Global.GlobalTag, Global.Health, Global.LogEvent, Global.ManageCustomFields, Global.ServiceManagers, Global.SetCustomField, Global.SystemTag | | |
38+
| Host | Host.Hbr.HbrManagement | -- | Virtustream does all other Host operations. |
39+
| InventoryService | InventoryService.Tagging | -- | -- |
40+
| Network | Network.Assign | | Virtustream does all other Network operations. |
41+
| Permissions | -- | -- | Virtustream does all Permissions operations. |
42+
| Profile-driven Storage | -- | -- | Virtustream does all Profile operations. |
43+
| Resource | A CloudAdmin user has all Resource privileges. | -- | -- |
44+
| Scheduled Task | A CloudAdmin user has all ScheduleTask privileges. | -- | -- |
45+
| Sessions | Sessions.GlobalMessage, Sessions.ValidateSession | -- | Virtustream does all other Sessions operations. |
46+
| Storage Views | StorageViews.View | -- | Virtustream does all other Storage View operations (Configure Service). |
47+
| Tasks | -- | -- | Virtustream manages extensions that manage tasks. |
48+
| vApp | A CloudAdmin user has all vApp privileges. | -- | -- |
49+
| Virtual Machine | A CloudAdmin user has all VirtualMachine privileges. | -- | -- |
50+
| vService | A CloudAdmin user has all vService privileges. | -- | -- |
51+
52+
Request elevated vCenter privileges with an SR in the Azure portal.
53+
54+
## NSX-T Manager access and identity
55+
56+
You access NSX-T Manager using the "administrator" account. That account has full privileges and enables you to create and manage T1 routers, logical switches, and all services. The full privileges in NSX-T also provide you with access to the NSX-T T0 router. A change to the T0 router could result in degraded network performance of a private cloud. To meet support requirements, it's required that you open an SR in the Azure portal to request any changes to your NSX-T T0 router.
57+
58+
## Next steps
59+
60+
The next step is to learn about [private cloud upgrade concepts][concepts-upgrades].
61+
62+
<!-- LINKS - external -->
63+
64+
<!-- LINKS - internal -->
65+
[concepts-upgrades]: ./concepts-upgrades.md

‎articles/azure-vmware/concepts-networking.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title: Concepts - network interconnectivity for Azure VMware Solution by Virtustream
3+
description: Learn about key aspects and use cases of networking and interconnectivity in Azure VMware Solution by Virtustream.
4+
services:
5+
author: v-jetome
6+
7+
ms.service: vmware-virtustream
8+
ms.topic: conceptual
9+
ms.date: 7/29/2019
10+
ms.author: v-jetome
11+
ms.custom:
12+
13+
---
14+
15+
# Azure VMware Solution by Virtustream networking and interconnectivity concepts
16+
17+
Network interconnectivity between your Azure VMware Solution (AVS) by Virtustream private clouds and on-premises environments or VNets in Azure enable you to access and use your private cloud. A few key networking and interconnectivity concepts that establish the basis of interconnectivity are described in this article.
18+
19+
A useful perspective on interconnectivity is to consider the two types of AVS by Virtustream private cloud implementations: those with basic Azure-only interconnectivity, those with full on-premises to private cloud interconnectivity.
20+
21+
The use cases for AVS by Virtustream private clouds include:
22+
- new VMware VM workloads in the cloud
23+
- VM workload bursting to the cloud
24+
- VM workload migration to the cloud
25+
- disaster recovery
26+
- consumption of Azure services
27+
28+
All use cases for the AVS by Virtustream service are enabled with on-premises to private cloud connectivity. The basic interconnectivity model is best suited for AVS by Virtustream evaluations or implementations that don't require access from on-premises environments.
29+
30+
The two types of AVS by Virtustream private cloud interconnectivity are described in the sections below. The most basic interconnectivity is "Azure VNet connectivity", and it enables you to manage and use your private cloud with only a single VNet in Azure. The interconnectivity described in "On-premises connectivity" extends the VNet connectivity to also include interconnectivity between on-premises environments and AVS by Virtustream private clouds.
31+
32+
## Azure VNet interconnectivity
33+
34+
The basic network interconnectivity that is established at the time of a private cloud deployment is shown in the diagram below. It depicts the logical, ExpressRoute-based networking between a VNet in Azure and a private cloud. The interconnectivity fulfills three of the primary use cases:
35+
- Inbound access to management networks where vCenter server and NSX-T manager are located.
36+
- Accessible from VMs within your Azure subscription, not from your on-premises systems.
37+
- Outbound access from VMs to Azure services.
38+
- Inbound access and consumption of workloads running a private cloud.
39+
40+
![Basic VNet -to- private cloud connectivity](./media/concepts/adjacency-overview-drawing-single.png)
41+
42+
The ExpressRoute (ER) circuit in this VNet -to- private cloud scenario is established when you create a connection from a VNet in your subscription to the ExpressRoute circuit of your private cloud. The peering uses an authorization key and a circuit ID that you request in the Azure portal. The ExpressRoute connection that is established through the peering is a private, one-to-one connection between your private cloud and the VNet. You can manage your private cloud, consume workloads in your private cloud, and access Azure services over that ExpressRoute connection.
43+
44+
When you deploy an AVS by Virtustream private cloud, a single /22 private network address space is required. This address space shouldn't overlap with address spaces used in other VNets in your subscription. Within this address space, management, provisioning, and vMotion networks are provisioned automatically. The routing is BGP-based and it's automatically provisioned and enabled by default for each private cloud deployment.
45+
46+
When a private cloud is deployed, you are provided with the IP addresses and credentials for vCenter and NSX-T Manager. To access those management interfaces, you will create additional resources in a VNet in your subscription. The procedures for creating those resources and establishing ER private peering are provided in the tutorials.
47+
48+
You design the private cloud logical networking and implement it with NSX-T. You use NSX-T Manager in your private cloud to create NSX-T T1 routers, logical switches, and all software-defined network services. At least one NSX-T T1 router and a logical switch is required. These logical NSX-T devices provide interconnectivity of VM workloads to VNets in your subscription, the internet, and Azure services.
49+
50+
## On-premises interconnectivity
51+
52+
You can also connect on-premises environments to your AVS by Virtustream private clouds. This type of interconnectivity is an extension to the basic interconnectivity described in the previous section.
53+
54+
![VNet and on-premises full private cloud connectivity](./media/concepts/adjacency-overview-drawing-double.png)
55+
56+
To establish full interconnectivity to a private cloud, you use the Azure portal to enable ExpressRoute Global Reach between a private cloud ER circuit and an on-premises ER circuit. This extends the basic connectivity to include access to private clouds from on-premises environments.
57+
58+
An on-premises to Azure VNet ER circuit is required in order to connect from on-premises environments to your private cloud in Azure. That ER circuit is in your subscription and is not part of a private cloud deployment. The on-premises ER circuit is beyond the scope of this document but if you require on-premises connectivity to your private cloud, you can use one of your existing ER circuits or purchase one in the Azure portal.
59+
60+
Once linked with Global Reach, the two ER circuits will route network traffic between your on-premises environments and your private cloud. The on-premises to private cloud interconnectivity is shown in the following diagram. The interconnectivity represented in the diagram enables the following use cases:
61+
- Hot/Cold Cross-vCenter vMotion
62+
- On-Premise to AVS by Virtustream private cloud management access
63+
64+
To enable full connectivity, an Authorization Key and private peering ID for Global Reach can be requested in the Azure portal. You use the key and ID to establish Global Reach between an ER circuit in your subscription and the ER circuit for your new private cloud. The [tutorial for creating a private cloud](tutorials-create-private-cloud.md) provides you with the procedures for requesting and using the key and ID.
65+
66+
The routing requirements of the solution require you to plan private cloud network address spaces so that you avoid overlaps with other VNets and on-premises networks. A /22 network block used for each private cloud needs to be unique across your routing domains. This network block includes management and production networks in the private cloud.
67+
68+
## Next steps
69+
70+
The next step is to learn about [private cloud storage concepts](concepts-storage.md).
71+
72+
<!-- LINKS - external -->
73+
[enable Global Reach]: https://docs.microsoft.com/azure/expressroute/expressroute-howto-set-global-reach
74+
75+
<!-- LINKS - internal -->
76+

‎articles/azure-vmware/concepts-private-clouds-clusters.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
title: Concepts - private clouds and clusters in Azure VMware Solution (AVS) by Virtustream
3+
description: Learn about the key capabilities of Azure VMware software-defined data centers and vSphere clusters in VMware Solution on Azure by VMware.
4+
services:
5+
author: v-jetome
6+
7+
ms.service: vmware-virtustream
8+
ms.topic: conceptual
9+
ms.date: 07/29/2019
10+
ms.author: v-jetome
11+
ms.custom:
12+
13+
---
14+
15+
# Azure VMware Solution by Virtustream private cloud and cluster concepts
16+
17+
The Azure VMware Solution (AVS) by Virtustream delivers VMware-based private clouds in Azure. The private clouds are built from clusters of dedicated bare-metal hosts and are deployed and managed through the Azure portal. Clusters in private clouds are provisioned with VMware vSphere, vCenter, vSAN, and NSX software. AVS by Virtustream private cloud hardware and software deployments are fully integrated and automated in Azure.
18+
19+
There's a logical relationship between Azure subscriptions, AVS by Virtustream private clouds, vSAN clusters, and hosts. In the diagram, two private clouds in a single Azure subscription are shown. The private clouds represent a development and a production environment, each with their own private cloud. In each of those private clouds there are two clusters. To show the lower potential needs of a development environment, smaller clusters with lower capacity hosts are used in that environment. All of these concepts are described in the sections below.
20+
21+
![Image of two private clouds in a customer subscription](./media/hosts-clusters-private-clouds-final.png)
22+
23+
## Private clouds
24+
25+
Private clouds contain vSAN clusters that are built with dedicated, bare-metal Azrure hosts. Each private cloud can have multiple clusters, all managed by the same vCenter server, and NSX-T manager. You can deploy and manage private clouds in the portal, from the CLI, or with PowerShell. As with other resources, private clouds are installed and managed from within an Azure subscription.
26+
27+
The number of private clouds within a subscription is scalable. Initially, there's a limit of one private cloud per subscription.
28+
29+
## Clusters
30+
31+
You'll create at least one vSAN cluster in each private cloud. When you create a private cloud, there's one cluster by default. You can add additional clusters to a private cloud using the Azure portal or through the API. All clusters have a default size of three hosts and can be scaled from 3 to 16 hosts. The type of hosts used in a cluster must be the same type. The hosts types are described in the next section.
32+
33+
Trial clusters are available for evaluation and they're limited to three hosts and a single trial cluster per private cloud. You can scale a trial cluster by a single host during the evaluation period.
34+
35+
You create, delete, and scale clusters through the portal or API. You still use vSphere and NSX-T Manager to manage most other aspects of cluster configuration or operation. All local storage of each host in a cluster is under control of vSAN.
36+
37+
## Hosts
38+
39+
Hyper-converged, bare-metal infrastructure nodes are used AVS by Virtustream private cloud clusters. There are two types of hosts, and clusters are built using only one type of host. The RAM, CPU, and disk capacities of both types the host types is provided in the table below.
40+
41+
| Host Type | CPU | RAM (GB) | vSAN NVMe cache Tier (TB, raw) | vSAN SSD capacity tier (TB, raw) |
42+
| :--- | :---: | :---: | :---: | :---: |
43+
| High-End (HE) | dual Intel 18 core 2.3 GHz | 576 | 3.2 | 15.20 |
44+
| General-Purpose (GP) | dual Intel 10 core 2.2 GHz | 192 | 1.6 | 7.68 |
45+
46+
Multiple types of hosts provide you with the flexibility to match hosts and cluster specifications to workload and business requirements.
47+
48+
Hosts that are used to build or scale clusters are allocated from an isolated pool of hosts. Those hosts have passed hardware tests and have had all data securely deleted from the flash disks. When you remove a host from a cluster, the internal disks are securely wiped and the hosts are placed into the isolated pool of hosts. When you add a host to a cluster, a sanitized host from the isolated pool is used.
49+
50+
## VMware software versions
51+
52+
The current software versions of the VMware software used in AVS by Virtustream private cloud clusters are:
53+
54+
| Software | Version |
55+
| :--- | :---: |
56+
| VCSA / vSphere / ESXi | 6.7 U2 |
57+
| ESXi | 6.7 U2 |
58+
| vSAN | 6.7 U2 |
59+
| NSX-T | 2.3 |
60+
61+
For any new cluster in a private cloud, the version of software will match what is currently running in the private cloud. For any new private cloud in a customer subscription, the latest version of the software stack is installed.
62+
63+
The general upgrade policies and processes for the AVS by Virtustream platform software is described in the Upgrades Concepts document.
64+
65+
## Host maintenance and lifecycle management
66+
67+
Host maintenance and lifecycle management are done without impact on the capacity or performance of private cloud clusters. Examples of automated host maintenance include firmware upgrades and hardware repair or replacement.
68+
69+
## Backup and restoration
70+
71+
Private cloud vCenter and NSX-T configurations are backed up hourly. Backups are kept for three days. Restoration from a backup is requested through a Service Request in the Azure portal.
72+
73+
## Next steps
74+
75+
The next step is to learn [networking and interconnectivity concepts](concepts-networking.md).
76+
77+
<!-- LINKS - internal -->
78+
79+
<!-- LINKS - external-->
80+
[VCSA versions]: https://kb.vmware.com/s/article/2143838
81+
[ESXi versions]: https://kb.vmware.com/s/article/2143832
82+
[vSAN versions]: https://kb.vmware.com/s/article/2150753
83+

0 commit comments

Comments
 (0)