installing-vsphere-6-0-esxi-hosts-nested-preconfiguration

Introduction

After covering the installing of the vCSA in the last article, we now care about the ESXi 6.0 Hosts installation and integration. I need to run the ESXi hosts nested as virtual machines themselves as this will be a testing environment. All systems installed are based on an existing physical environment running vSphere 5.5. The process of deploying on physical hosts instead on virtual machines may vary at some points.

Existing Situation

The base for the installation is an existing vSphere 5.5 using a Microsoft Windows based vCenter and several physical ESXi-Hosts (based on Cisco UCS).

The vCenter for the nested test environment is already installed in form of the vCSA 6.0 (vCenter Server Appliance 6.0). If you want to know how to install the vCSA 6.0 please read my previous article. In summary I’m going to deploy 3 ESXi-hosts to cover two different scenarios. One scenario having 2 hosts in a cluster and one scenario having a single host without a cluster.

Requirements

For each installation of a nested ESXi-hosts the requirements are: 2 vCPUs, 6GB Memory (4GB is the minimum), 15GB Storage (4GB is the minimum), at least 1 IP address + DNS entries (if you want to). The ESXi 6.0 installation medium can be found on the VMware portal, after you logged in

HowTo

To keep in mind for the installation process:

  • I’m logged in to the productive MS Windows vCenter 5.5 using RDP
  • I’m using Firefox on the vCenter to connect to the local vSphere VMware WebClient

Working this way enables me to deploy everything locally in our datacenter instead of having to use my small bandwidth connection to the datacenter. For the installation I will start creating an empty virtual machine and deploy the ESXi to this VM.

Creating the VM for the installation

Since there is no official existing template nor an existing .ovf for the deploy of an ESXi Hosts nested. If you are ok with unofficial releases you should check for the vGhetto Nested ESXi Template Content Library in vSphere 6.0

I will have to create a new virtual machine and install ESXi to this VM. My way of creating a VM is just to go to the host of my choice and click Actions > New virtual Machine…

vSphere 6 new virtual machine

Select a creation type

Since there is nothing to re-use, the only way to get the ESXi up and running for me is to Create a new virtual machine New Virtual Machine vSphere 6

Edit Settings

I’ll call it esxqa6_1 and place it to the folder vSphere6.0 and select a host and a datastore with sufficient resources

New Virtual Machine vSphere 6

Compatibility

The Compatibility with ESXi 5.5 and later is fine in my case, but you need to think about your migration possibilities and how they get limited. That’s the same as selecting the latest version of virtual hardware (10) on this installation as it is running on vSphere 5.5.

New VM vSphere 6

Since there is no Guest-OS nested vSphere 6, the guest-os type is other 64-bit with the Guest OS Name ESXi 6.0.

New VM OS type vSphere 6

The configuration is pretty straightforward:

  • 2 vCPUs (2 CPU is the minimum requirement)
  • 6GB of memory (4 GB is minimum, 8 GB and more is recommended for productive infrastructures)
  • 15GB of disk-space as a single hard disk
  • vmxnet 3 for the network adapter type

  New VM Hardware setup vSphere 6 ESXi Hosts nested

Finish

If the summary screen shows all the correct settings hit Finish to deploy the VM and start the advanced settings.

Advanced settings of the VM

After creating the empty VM I have to change some advanced settings to to have ESXi 6.0 running smoothly. CPU Hardware virtualization should be set to “Expose hardware assisted virtualization to the guest OS” to have full virtualization support on the CPU enabled.

VM advanced settings to run nested ESXi Expose hardware assisted virtualization to the guest OS)

And second to make sure to enable the Failed Boot Recovery option. Using this option the VM reboots frequently when no boot device is found. So it’s looping reboots till the .iso is attached to the system. This is only necessary for the installation process and can be unchecked when the installation is complete.

more VM advanced settings to run nested ESXi Failed Boot Recovery option

Installation of ESXi within the VM

You are ready now to install ESXi Hosts nested. The installation itself will be covered in the next article.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.