Skip to content

Commit 3f6857a

Browse files
starkilla2003Bernd LoehleinASchwarz1984stabet04
authored
AzureVMWareSolutionMicroHack (#158)
* First set of updates and structure created * Lab deployment scripts * Lab deployment scripts * adjusted links to Microhack repo * Adjusted script references * Fixed typo * First task description * Task 2 added content * Task 2 added * Challenge 3 added * Challenge 3 created * Fixed path for Challenge 3 * Challenge 4 added * Challenge 5 added * Challenge 6 added * Challenge 7 added * Challenge 8 added * Challenge 9 added * Challenge 10 added * Challenge 11 added * Fixed typos * Challenge 12 added * Challenge 13 added * Rest of challenges added * Added HCX deployment and draft for cleanup script * Linked solution guide to challenge * Update for Microhack and adjustements for first delivery * Small fixes * Fixes * little fixed * fixed * fixed * Added architecture overview and fix of little mispellings * Typo change * Minor typos and prerequisites updates * Minor changes in read me, pre-requisites and challenge 1 --------- Co-authored-by: Bernd Loehlein <[email protected]> Co-authored-by: Andreas Schwarz <[email protected]> Co-authored-by: stabet04 <[email protected]>
1 parent dc70f54 commit 3f6857a

File tree

177 files changed

+7067
-2
lines changed

Some content is hidden

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

177 files changed

+7067
-2
lines changed

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/00-Pre-Reqs.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Getting started
2+
3+
**[Home](../Readme.md)** - [Challenge One](./01-NSX-DHCP.md)
4+
5+
## Pre-requisites for Challenges
6+
7+
### 1. Deploying AVS
8+
9+
10+
Azure VMware Solution delivers VMware-based private clouds in Azure and is available for EA and CSP customers. Customers need to request a quota and register the Microsoft.AVS resource provider prior to deploying:
11+
12+
[Request host quota for Azure VMware Solution - Azure VMware Solution | Microsoft Docs](https://docs.microsoft.com/en-us/azure/azure-vmware/request-host-quota-azure-vmware-solution)
13+
14+
[Deploy and configure Azure VMware Solution - Azure VMware Solution | Microsoft Docs](https://docs.microsoft.com/en-us/azure/azure-vmware/deploy-azure-vmware-solution?tabs=azure-portal)
15+
16+
As the service isn’t available in all regions yet please check for local coverage in the required regions:
17+
18+
[Azure Products by Region | Microsoft Azure](https://azure.microsoft.com/en-us/global-infrastructure/services/?regions=all&products=azure-vmware)
19+
20+
Each private cloud will have a minimum of one vSAN cluster that consists of three hosts. Additional hosts, clusters or even private clouds can be added to your Azure subscription depending on your requirements and available host quotas.
21+
22+
There is also the option of a trial cluster, these are limited to three hosts and one month duration. After the trial period those hosts will be converted to regular AVS hosts.
23+
24+
25+
### 2. Setting up the environment
26+
27+
#### Connecting to Jumpbox
28+
29+
To connect to NSX-T you need to connect to the Jumpbox virutal machine using Bastion.
30+
31+
- Jumpbox VM: AVS-SDDC-FOM-Jumpbox
32+
- VM username: avsjump
33+
- VM password: can be found in Key Vault
34+
35+
36+
## Learning resources
37+
38+
[Concepts - Private clouds and clusters - Azure VMware Solution | Microsoft Docs](https://docs.microsoft.com/en-us/azure/azure-vmware/concepts-private-clouds-clusters)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/01-NSX-DHCP.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# NSX DHCP
2+
3+
[Previous Challenge](./00-Pre-Reqs.md) - **[Home](../Readme.md)** - [Next Challenge](./02-NSX-Add-Segment.md)
4+
5+
## Introduction
6+
7+
In this challenge we will configure a NSX-T DHCP server.
8+
9+
## Challenge
10+
11+
In this challenge, you will perform the following tasks:
12+
13+
1. Create a DHCP server
14+
2. Check the DHCP configuration in NSX-T
15+
16+
As a part of this challenge you are expected to <u>log on to the AVS Private cloud within Azure Portal</u> assigned to your team and to deploy a DHCP server, such that we can provide dynamic IPs to VMs when they need.
17+
18+
### Use Case Tip
19+
20+
VMs within the AVS environment will recieve IP from various sources
21+
22+
1. Some VMs may be migrated and they will retain their IPs from On-Prem to AVS if they are on an extended L2 stretch
23+
2. Some VMs may be migrated and they will need new IP from AVS if they are on a non-extended VLAN. in such cases the VM will get a new IP (DHCP based) or static IP
24+
3. Some VMs may be created locally within AVS and thats then they will either be provided static or dynamic IP
25+
26+
Feel free to reach out to your facilitator in case you have any questions regarding the tabs within the AVS Private Cloud.
27+
28+
Please carefully follow the instructions provided by your facilitator.
29+
30+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server and the NSX Manager.
31+
32+
Applications and workloads running in an Azure VMware Solution private cloud environment require name resolution and DHCP services (optionally) for lookup and IP address assignments. A proper DHCP and DNS infrastructure are required to provide these services. You can configure a virtual machine to provide these services in your private cloud environment.
33+
34+
## Success Criteria
35+
36+
When you login to the NSX Manager in AVS the DHCP server should be configured and running. It should be attached to the Tier 1 gateway.
37+
38+
## Learning resources
39+
40+
[Configure DHCP for Azure VMware Solution](https://learn.microsoft.com/en-us/azure/azure-vmware/configure-dhcp-azure-vmware-solution)
41+
42+
### Solution - Spoilerwarning
43+
44+
[Solution Steps](../Solutionguide/01-NSX-DHCP.md)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/02-NSX-Add-Segment.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# NSX Add Segment
2+
3+
[Previous Challenge](./01-NSX-DHCP.md) - **[Home](../Readme.md)** - [Next Challenge](./03-NSX-Add-DNS-Forwarder.md)
4+
5+
## Introduction
6+
7+
In this challenge we will configure a NSX-T Segment.
8+
9+
## Challenge
10+
11+
In this challenge, you will perform the following tasks:
12+
13+
1. Add a Network Segment
14+
2. Attach a Virtual Machine to the Network Segment
15+
16+
As a part of this challenge you are also expected to <u>log on to the jump server assigned to your user</u> and create a network segment from NSX and then a DHCP range will be defined within that segment. When a virtual machine will be connected to that segment they VM will automatically obtain the IP from the DHCP range.
17+
18+
### Note
19+
20+
An AVS segment can be created both in the NSX portal and AVS portal
21+
22+
## Use Case Tip
23+
24+
VMs within the AVS environment can be easily segmented into multiple subnets etc. without the need for physical routers and switches
25+
26+
Customers can easily achieve data center segmentation with a few simple steps without changing any of the underlying physical network configurations with VMware NSX and vSphere
27+
28+
Please carefully follow the instructions provided by your facilitator.
29+
30+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server and the NSX Manager.
31+
32+
## Success Criteria
33+
34+
The virtual machine attached to the segments should be getting an IP from the DHCP.
35+
36+
## Learning resources
37+
38+
### Solution - Spoilerwarning
39+
40+
[Solution Steps](../Solutionguide/02-NSX-Add-Segment.md)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/03-NSX-Add-DNS-Forwarder.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# NSX Add Segment
2+
3+
[Previous Challenge](./02-NSX-Add-Segment.md) - **[Home](../Readme.md)** - [Next Challenge](./04-HCX-Manager-Appliance.md)
4+
5+
## Introduction
6+
7+
By default, Azure VMware Solution management components such as vCenter can only resolve name records available through Public DNS. However, certain hybrid use cases require Azure VMware Solution management components to resolve name records from privately hosted DNS to properly function, including customer-managed systems such as vCenter and Active Directory.
8+
9+
Private DNS for Azure VMware Solution management components lets you define conditional forwarding rules for the desired domain name to a selected set of private DNS servers through the NSX-T DNS Service.
10+
11+
This capability uses the DNS Forwarder Service in NSX-T. A DNS service and default DNS zone are provided as part of your private cloud. To enable Azure VMware Solution management components to resolve records from your private DNS systems, you must define an FQDN zone and apply it to the NSX-T DNS Service. The DNS Service conditionally forwards DNS queries for each zone based on the external DNS servers defined in that zone.
12+
13+
## Challenge
14+
15+
In this challenge, you will perform the following tasks:
16+
17+
1. Configure a DNS forwarder within NSX such that the On Prem FQDN can be resolved from AVS itself
18+
19+
Since the default DNS is preconfigured with AVS, to test DNS we are using a feature where we need name resolution
20+
21+
As a part of this challenge you are also expected to <u>log on to the AVS Private cloud assigned to your team</u> and create a DNS forwarder within NSX such that the On Prem FQDN can be resolved from AVS itself. You can use this to also import images from On Prem to AVS using a content library which is configured On Prem
22+
23+
## Success Criteria
24+
25+
By the end of this challenge you should independantly be able to answer the following questions
26+
27+
1. What benefits does DNS forwarder get here?
28+
2. How can you resolve AVS On-Prem FQDN on AVS?
29+
3. How will you go about configuring LDAP integration for NSX?
30+
31+
## Learning resources
32+
33+
### Solution - Spoilerwarning
34+
35+
[Solution Steps](../Solutionguide/03-NSX-Add-DNS-Forwarder.md)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/04-HCX-Manager-Appliance.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# HCX Manager Appliance
2+
3+
[Previous Challenge](./04-NSX-Firewall.md) - **[Home](../Readme.md)** - [Next Challenge](./05-HCX-Site-Pair.md)
4+
5+
## Introduction
6+
7+
1. Customer migration is often driven by a need to move a known set of existing applications to a new infrastructure. The most common use case for HCX is migration from On-Prem to Azure VMware Service (AVS).
8+
2. Customer wants to realize value faster for new AVS environments while driving down operational costs.
9+
3. Due to time constraint choosing HCX proves to be beneficial as parallel migration scenarions like bulk migrations as well as live non-disruptive migrations to and from On-Prem to AVS.
10+
11+
## HCX Deployment view
12+
13+
![](./Images/04-HCX-Manager-Appliance/HCXLayered.png)
14+
15+
## Challenge
16+
17+
In this challenge, you will perform the following tasks:
18+
19+
1. Configure HCX Manager Appliance On-Prem
20+
21+
As a part of this challenge you are also expected to <u>log on to the On Prem and AVS vCenter servers from the jumpbox assigned to your user</u>. You will also be expected to log on to the AVS portal to retrieve the HCX activation key for On-Prem HCX appliance.
22+
23+
Please carefully follow the instructions provided by your facilitator. Incorrectly deploying the HCX may result in multiple forthcoming steps not operating as expected.
24+
25+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server.
26+
27+
### Note
28+
29+
The HCX Manager VM within the On Prem vCenter server was deployed through an OVA (appliance) that we downloaded from AVS HCX. This step was done during the environment preparation to save time.
30+
31+
You can ask your coach to show you how this step was done
32+
33+
## Success Criteria
34+
35+
You can login to the HCX Manager UI and see the HCX Manager Appliance is up and running.
36+
37+
## Learning resources
38+
39+
### Solution - Spoilerwarning
40+
41+
[Solution Steps](../Solutionguide/04-HCX-Manager-Appliance.md)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/05-HCX-Site-Pair.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# HCX Site Pair
2+
3+
[Previous Challenge](./04-HCX-Manager-Appliance.md) - **[Home](../Readme.md)** - [Next Challenge](./06-HCX-Network-Profiles.md)
4+
5+
## Introduction
6+
7+
In this challenge we will configure a site pair using HCX.
8+
9+
## Challenge
10+
11+
In this challenge, you will perform the following tasks:
12+
13+
1. Configure Site Pair
14+
15+
As a part of this challenge you are expected to <u>log on to the On Prem and AVS vCenter servers. You will also be expected to log on to HCX manager and configure HCX from On Prem</u> and connect it with AVS and deploy the interconnect and network extension appliances such that migration and network extension related activities can be achieved
16+
17+
Please carefully follow the instructions provided by your facilitator. Incorrectly deploying the HCX may result in multiple forthcoming steps not operating as expected.
18+
19+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server.
20+
21+
## Configure Site Pairing
22+
23+
Now you're ready to add a site pairing, create a network and compute profile, and enable services such as migration and network extension.
24+
25+
## Success Criteria
26+
27+
The VMware HCX Cloud Manager in AVS and the On-Prem VMware HCX Connector are connected (paired).
28+
29+
## Learning resources
30+
31+
### Solution - Spoilerwarning
32+
33+
[Solution Steps](../Solutionguide/05-HCX-Site-Pair.md)
34+

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/06-HCX-Network-Profiles.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
# HCX Network Profiles
2+
3+
[Previous Challenge](./05-HCX-Site-Pair.md) - **[Home](../Readme.md)** - [Next Challenge](./07-HCX-Compute-Profiles.md)
4+
5+
## Introduction
6+
7+
1. Network Profiles can be pre-created in the Network Profile tab or they can be created during the Compute Profile configuration. A Network Profile contains:
8+
9+
2. One underlying vSphere Port Group (VSS or VDS) or NSX-based network.
10+
11+
3. IP address information: The gateway IP, the network prefix and MTU, and DNS.
12+
13+
4. A pool of IP addresses reserved for HCX to use during Service Mesh deployments.
14+
15+
## Characteristics of Network Profiles
16+
17+
1. Network Profile configurations are only used during Service Mesh deployments (IP addresses assigned to the IX and NE, and OSAM appliances).
18+
19+
2. The HCX Manager only uses a Management interface, it does not use other Network Profile networks.
20+
21+
3. A Compute Profile will always include one or more Network Profile.
22+
23+
4. When Service Mesh is deployed, every Network Profile that is included in the Compute Profile configuration is used.
24+
25+
5. When a Network Profile network is used in a Service Mesh, the HCX appliance will consume a single IP address out of the configured IP pool.
26+
27+
6. When a Network Profile is assigned to a specific HCX traffic type (the traffic types are explained in the next section), a single IP address is used. For example, if the same Network Profile is assigned for HCX Management and HCX Uplink, one IP address is used, not two.
28+
29+
7. A Network Profile can be used with multiple Compute Profiles.
30+
31+
### Example network profile in a customer environment
32+
33+
![](./Images/06-HCX-Network-Profiles/HCXNetworkProfileImage.png)
34+
35+
## Challenge
36+
37+
In this challenge, you will perform the following tasks:
38+
39+
1. Create Network Profile
40+
41+
As a part of this challenge you are also expected to <u>log on to the On Prem vCenter server and go to HCX Manager plugin on the vCenter</u> to configure the Network Profile
42+
43+
Please carefully follow the instructions provided by your facilitator. Incorrectly deploying the HCX may result in multiple forthcoming steps not operating as expected.
44+
45+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server.
46+
47+
## Success Criteria
48+
49+
The created network profiles will be avaiable to be used by Interconnect and Network Enxtension appliances within the Service Mesh.
50+
51+
## Learning resources
52+
53+
### Solution - Spoilerwarning
54+
55+
[Solution Steps](../Solutionguide/06-HCX-Network-Profiles.md)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/07-HCX-Compute-Profiles.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# HCX Configure Compute Profile
2+
3+
[Previous Challenge](./06-HCX-Network-Profiles.md) - **[Home](../Readme.md)** - [Next Challenge](./08-HCX-Service-Mesh.md)
4+
5+
## Introduction
6+
7+
A Compute Profile configuration is required for Service Mesh deployments. It defines deployment parameters of interconnect and network extension appliances within On Prem
8+
9+
## Characteristics of Compute Profiles
10+
11+
1. An HCX Manager system must have one Compute Profile.
12+
13+
2. Compute Profile references clusters and inventory within the vCenter Server that is registered in HCX Manager (other vCenter Servers require their own HCX Manager).
14+
15+
3. Creating a Compute Profile does not deploy the HCX appliances (Compute Profiles can be created and not used).
16+
17+
4. Creating a Service Mesh deploys appliances using the settings defined in the source and destination Compute Profiles.
18+
19+
5. A Compute Profile is considered "in use" when it is used in a Service Mesh configuration.
20+
21+
6. Changes to a Compute Profile profile are not effected in the Service Mesh until a Service Mesh a Re-Sync action is triggered.
22+
23+
## Challenge
24+
25+
In this challenge, you will perform the following tasks:
26+
27+
1. Create Compute Profile
28+
29+
As a part of this challenge you are also expected to <u>log on to the On Prem vCenter server and HCX Manager plugin in the On-Prem vCenter</u> to configure the Compute Profile
30+
31+
Please carefully follow the instructions provided by your facilitator. Incorrectly deploying the HCX may result in multiple forthcoming steps not operating as expected.
32+
33+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server.
34+
35+
## Success Criteria
36+
37+
The Compute Profile is created and can be used.
38+
39+
## Learning resources
40+
41+
### Solution - Spoilerwarning
42+
43+
[Solution Steps](../Solutionguide/07-HCX-Compute-Profiles.md)

‎03-Azure/01-03-Infrastructure/05_Azure_VMware_Solution/Challenges/08-HCX-Service-Mesh.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# HCX Service Mesh
2+
3+
[Previous Challenge](./07-HCX-Compute-Profiles.md) - **[Home](../Readme.md)** - [Next Challenge](./09-HCX-Network-Extension.md)
4+
5+
## Introduction
6+
7+
When HCX Migration, Disaster recovery, Network Extension, and WAN Optimization services are activated, HCX deploys Virtual Appliances in the source site and corresponding "peer" virtual appliances on the destination site. The Multi-Site Service Mesh activates the configuration, deployment, and serviceability of these Interconnect virtual appliance pairs.
8+
9+
## Challenge
10+
11+
In this challenge, you will perform the following tasks:
12+
13+
1. Deploy a Service Mesh
14+
15+
As a part of this challenge you are also expected to <u>log on to the On Prem vCenter server and HCX Manager plugin in the On-Prem vCenter</u> to deploy the interconnect and network extension appliances as a part of Service Mesh
16+
17+
Please carefully follow the instructions provided by your facilitator. Incorrectly deploying the HCX may result in multiple forthcoming steps not operating as expected.
18+
19+
Work with the instructor to ensure your VMware environment has the required permissions to access your AVS vCenter Server.
20+
21+
## Success Criteria
22+
23+
The service mesh between AVS and On-Prem is established.
24+
25+
## Learning resources
26+
27+
### Solution - Spoilerwarning
28+
29+
[Solution Steps](../Solutionguide/08-HCX-Service-Mesh.md)

0 commit comments

Comments
 (0)