28 Jun 2022
Resources:
The ability to configure vCenter with multiple vNICs, this can make it accessible to multiple networks without routing.
The maximum number of vNICs per VM is 4, their roles are as follows:
To add additional network adaptors, edit the settings of a VM.
Primary Network Identifier (PNID) is how vCenter identifies itself and is formed by the Fully Qualified Domain Name (FQDN).
vCenter 7 changes the behaviour to whenever the FQDN is changed the PNID is also changed, therefore all custom certificates need to be regenerated. Furthermore, vCenter HA will also need to be reconfigured and if vCenter is connected to Active Directory that to will need to be rejoined.
It is recommended to create a snapshot and file based backup.
Server profiles are similar to Host profiles. It allows for a standard configure between vCenter server appliances. The server profiles are written in a JSON format and can be configured with the following settings:
Possible use cases for server profiles include:
Dynamic DNS (DDNS) is a method of automatically updating a name server in the Domain Name System. vSphere once every 24 hours sends a keepalive to the DNS server updating its record.
Use cases include:
Home timing options available are:
Time configuration and the PTP need to be configured.
Then the VM can add a new precision clock.
Allow to easily create a cluster with additional configurations, which include:
Warning: When creating a cluster all ESXi hosts will be placed into Maintenance Mode, make sure that vCenter is running outside of these ESXi hosts, otherwise it will become unavailable.
Create a new cluster, then navigate to Quick Start. The Quick Start process is split into 3 stages.
A cluster is created in accordance with a VMware Validated Design.
The following steps are include within the “Configure Cluster” wizard:
Monolithic Application describes a single-tiered software application in which the user interface and data access code are combined into a single program from a single platform.
Microservices arranges an Monolithic application as a collection of loosely-coupled services, which communicate together using APIs. The benefits of Microservices over Monolithic include:
Containers include the complete runtime environment including; Applications, Dependencies, Libraries, Configuration Files etc. Benefits of using containers include:
VMware suggests the follow user application stack for each section of Kubernetes.
Containers are temporary in nature, they can start and stop on demand due to their performance compared to VMs. Containers are also destroyed and re-created when updating, as the images are updated and redeployed.
Supervisor cluster - A cluster that has Kubernetes configured.
Spherelets are based on Kubelets and manage the ESXi host by polling for changes.
Automation
Kubernetes Namespace
They are similar to resource pools and can provide a “sandbox” environment to a team. Available resources are configured and compute can be isolated using NSX-T for microsegmentation.
Each namespace can have unique configurable permissions.
Tanzu Kubernetes Grid Cluster
Automatic deployment of Kubernetes cluster, running Photon OS container host.
Tanzu runs VMs on an ESXi host, they do not run directly on top of vSphere.
Use cases of Tanzu: