Recent updates
-
Lab 10 - Working with Containers
Updated onArticleContainers are semi-isolated environments in which applications, or parts of applications, can run. Unlike VMs which run entirely separate OSes, containers directly share resources with the OS of the server that hosts the containers. This makes containers more efficient than VMs because each containerized environment does not require a complete guest OS.
Moreover, containers are isolated at the process level from other containers, as well as non-containerized processes that run on the server. This isolation makes containers more secure than multiple applications that run directly on a host server. Each container can have different environment parameters, rather than all containers sharing a common configuration.
Technology to deploy applications inside containers has existed since the introduction of the Unix chroot call in the 1970s. Containers became massively popular in the mid-2010s with the introduction of Docker and Kubernetes, which provided tooling that made it easier for developers to create and manage containerized applications.
RETIRED CONTENT Day 4
-
Tanzu Setup
Updated onArticle- Log into the VMCEXPERT VCDR Org assigned to your workshop (VMCEXPERT1-VCDR01, VMCEXPERT2-VCDR01, VMCEXPERT3-VCDR01)
- username: [email protected]
- password: {assigned_password}
- Click View Details
- Confirm the following:
- There are 4 Nodes deployed in the SDDC
- Tanzu Service Activated Successfully
(If the service is not activated you can activate manually or contact us in the Slack Channel). - The SDDC has Large Appliances
RETIRED CONTENT
- Log into the VMCEXPERT VCDR Org assigned to your workshop (VMCEXPERT1-VCDR01, VMCEXPERT2-VCDR01, VMCEXPERT3-VCDR01)
-
VCDR Setup
Updated onArticleSteps to Prepare VCDR for Student Labs
RETIRED CONTENT
-
Lab 09 - DRaaS with VMware Cloud Disaster Recovery (Part2)
Updated onArticleVMware Cloud Disaster Recovery is an on-demand disaster recovery service that provides an easy-to-use Software-as-a-Service (SaaS) solution and offers cloud economics to keep your disaster recovery costs under control.
You can use VMware Cloud Disaster Recovery to protect your vSphere virtual machines (VMs) by replicating them to the cloud, and recovering them as needed to a target VMware Cloud Software Defined Data Center (SDDC) on VMware Cloud on AWS. You can create the target "recovery" SDDC immediately prior to performing a recovery, and it does not need to be provisioned to support replications in a steady state.
Using VMware Cloud Disaster Recovery you can protect your On-premises and/or VMC on AWS SDDCs and recover them into the cloud.
VMware Cloud Disaster Recovery lets you deploy a recovery SDDC in VMware Cloud on AWS (or add an existing SDDC) to use for recovery and testing of your DR plans. You can add hosts, clusters, new networks, request public IP addresses, configure NAT rules, and also delete the recovery SDDC. In the event of a disaster or planned recovery operation, you can recover VMs from your protected site to your recovery SDDC.
RETIRED CONTENT Day 4
-
Lab 11 - Deploy Tanzu Services and Application
Updated onArticleVMware Cloud on AWS enables your IT and Operations teams to add value to your investments in AWS by extending your on-premises VMware vSphere environments to the AWS cloud. VMware Cloud on AWS is an integrated cloud offering jointly developed by Amazon Web Services (AWS) and VMware. It is optimized to run on dedicated, elastic, bare-metal Amazon Elastic Compute Cloud (Amazon EC2) infrastructure.
By running VMware Tanzu within the same infrastructure as the general VM workloads organizations can immediately start their modern application development strategy without incurring additional costs. For example, you can use SDDC spare capacity to run Tanzu Kubernetes Grid to enable next-generation application modernization, or compute power not used by disaster recovery can be used for Tanzu Kubernetes Grid clusters.
VMC on AWS Labs Day 4
-
Lab 10 - Working with Containers
Updated onArticleContainers are semi-isolated environments in which applications, or parts of applications, can run. Unlike VMs which run entirely separate OSes, containers directly share resources with the OS of the server that hosts the containers. This makes containers more efficient than VMs because each containerized environment does not require a complete guest OS.
Moreover, containers are isolated at the process level from other containers, as well as non-containerized processes that run on the server. This isolation makes containers more secure than multiple applications that run directly on a host server. Each container can have different environment parameters, rather than all containers sharing a common configuration.
Technology to deploy applications inside containers has existed since the introduction of the Unix chroot call in the 1970s. Containers became massively popular in the mid-2010s with the introduction of Docker and Kubernetes, which provided tooling that made it easier for developers to create and manage containerized applications.
VMC on AWS Labs Day 4
-
Lab 09 - DRaaS with VMware Cloud Disaster Recovery (Part2)
Updated onArticleVMware Cloud Disaster Recovery is an on-demand disaster recovery service that provides an easy-to-use Software-as-a-Service (SaaS) solution and offers cloud economics to keep your disaster recovery costs under control.
You can use VMware Cloud Disaster Recovery to protect your vSphere virtual machines (VMs) by replicating them to the cloud, and recovering them as needed to a target VMware Cloud Software Defined Data Center (SDDC) on VMware Cloud on AWS. You can create the target "recovery" SDDC immediately prior to performing a recovery, and it does not need to be provisioned to support replications in a steady state.
Using VMware Cloud Disaster Recovery you can protect your On-premises and/or VMC on AWS SDDCs and recover them into the cloud.
VMware Cloud Disaster Recovery lets you deploy a recovery SDDC in VMware Cloud on AWS (or add an existing SDDC) to use for recovery and testing of your DR plans. You can add hosts, clusters, new networks, request public IP addresses, configure NAT rules, and also delete the recovery SDDC. In the event of a disaster or planned recovery operation, you can recover VMs from your protected site to your recovery SDDC.
VMC on AWS Labs Day 4
-
Lab 08 - DRaaS with VMware Cloud Disaster Recovery (Part 1)
Updated onArticleVMware Cloud Disaster Recovery is an on-demand disaster recovery service that provides an easy-to-use Software-as-a-Service (SaaS) solution and offers cloud economics to keep your disaster recovery costs under control.
You can use VMware Cloud Disaster Recovery to protect your vSphere virtual machines (VMs) by replicating them to the cloud, and recovering them as needed to a target VMware Cloud Software Defined Data Center (SDDC) on VMware Cloud on AWS. You can create the target "recovery" SDDC immediately prior to performing a recovery, and it does not need to be provisioned to support replications in a steady state.
Using VMware Cloud Disaster Recovery you can protect your On-premises and/or VMC on AWS SDDCs and recover them into the cloud.
VMware Cloud Disaster Recovery lets you deploy a recovery SDDC in VMware Cloud on AWS (or add an existing SDDC) to use for recovery and testing of your DR plans. You can add hosts, clusters, new networks, request public IP addresses, configure NAT rules, and also delete the recovery SDDC. In the event of a disaster or planned recovery operation, you can recover VMs from your protected site to your recovery SDDC.
VMC on AWS Labs Day 3
-
Lab 08 - DRaaS with VMware Cloud Disaster Recovery (Part 1)
Updated onArticleVMware Cloud Disaster Recovery is an on-demand disaster recovery service that provides an easy-to-use Software-as-a-Service (SaaS) solution and offers cloud economics to keep your disaster recovery costs under control.
You can use VMware Cloud Disaster Recovery to protect your vSphere virtual machines (VMs) by replicating them to the cloud, and recovering them as needed to a target VMware Cloud Software Defined Data Center (SDDC) on VMware Cloud on AWS. You can create the target "recovery" SDDC immediately prior to performing a recovery, and it does not need to be provisioned to support replications in a steady state.
Using VMware Cloud Disaster Recovery you can protect your On-premises and/or VMC on AWS SDDCs and recover them into the cloud.
VMware Cloud Disaster Recovery lets you deploy a recovery SDDC in VMware Cloud on AWS (or add an existing SDDC) to use for recovery and testing of your DR plans. You can add hosts, clusters, new networks, request public IP addresses, configure NAT rules, and also delete the recovery SDDC. In the event of a disaster or planned recovery operation, you can recover VMs from your protected site to your recovery SDDC.
RETIRED CONTENT Day 3
-
L07 - SDDC Migration with HCX (Part 2)
Updated onArticleVMware Cloud on AWS provides a reliable, elastic, and highly scalable solution for customers who want to extend their workloads into the cloud.
However, when it comes to migration or bi-directional workload mobility, software and network incompatibilities between on-premises and cloud environments can complicate your migration process.
VMware Hybrid Cloud Extension (HCX) helps overcome those challenges by building an abstraction layer on top of existing site-specific implementations, allowing you to extend their networks and environments to the cloud seamlessly without the need for extensive reconfiguration and upgrades.
Here are some key benefits of HCX:
- Ability to migrate workloads across different versions of vSphere (6.0 or later).
- WAN optimization, compression, and de-duplication enable high throughput for faster migrations.
- Network extension enables stretching layer 2 networks between on-premises and VMware Cloud on AWS without the need for complex network reconfiguration. Virtual machines (VM) can be moved between on-premises and cloud environments with no need the change or re-assign IP addresses.
HCX is a software-as-a-service (SaaS) offering, available at no extra cost for VMware Cloud on AWS customers.
The HCX solution is built out of several component services, each supporting a specific function within the overall solution.
- HCX Enterprise Manager: System management component on the on-premises side, which is always deployed as a “source.”
- HCX Cloud Manager: System management component on the cloud side and is always deployed as “destination.”
- HCX-IX Interconnect Appliance: Provides replication and vMotion-based migration capabilities.
- HCX WAN Optimization Service: Provides improved network performance by using techniques such as de-duplication and compression to help speed up migrations.
- HCX Network Extension Service: Provides layer 2 extension capabilities, enabling VMs to migrate between on-premises and cloud without the need to re-IP.
RETIRED CONTENT Day 3