installing-vsphere-6-0-esxi-hosts-nested-install-2

Installing ESXi to the VM

Installing vSphere 6.0 ESXi using the .iso file that contains the ESXi-Installation has to be attached to the VM. To attach it the VM has to be powered on. After powering on the virtual machine you can add the .iso using the VM Summary Tab->VM Hardware CD/DVD drive one has to be set to the .iso file using Connect to CD/DVD image on a local disk.

Installing vSphere 6

Since the system is rebooting frequently when no boot media is found it will restart till the .iso is attached successfully.

When opening the console it should already greet you with the ESXi-6.0.0 –standard Boot Menu.

Installing vSphere 6.0 ESXi

The boot menu automatically boots the installer after 10 seconds are count down.

After the installer is started, the first step is to Agree to the EULA.

Then the installer is searching automatically for devices to bring up a window that lists all available storage devices for the installation. Since I only added a single harddisk to the VM, there is not much choice in my case.

ESXi 6 Installation device

Afterwards set the keyboard to your needs – in my case German, you might have guessed.

Please note: When you are using a Mac OS X to access virtual machines via the webclient console of the VM and you are having either a German, Turkish, French, Swiss or Austrian keyboard locale on your computer there is a very annoying bug. It makes it nearly impossible to handle systems via console because it is not possible to type important characters like /, ., -, ;, @, $ and many more. For me switching the locale on my Mac to en_US  as a workaround. Please note also that this bug might transfer from your workstation when accessing the VMware webclient via RDP, i. e. a websession using Gotomeeting or WebEx!

For more information please visit the VMware KB http://kb.vmware.com/kb/2071245

Setting the root-password 

If you’re using this guide to create you own test-infrastructure, please make sure to save your passwords somewhere (maybe you got a password-safe or something similar.). As it’s unlikely to connect to every entity of this type of infrastructure daily, it’s very likely to forget passwords.

Point of no return

Now the ESXi 6.0.0 installer is Scanning the system and starting the installation, asking to partition the disk. In my case it is brand new virtual disk and no data is on this disk – so all good. Especially when you work on a real environment with DAS, SAN or more than the system disks attached, please act very carefully. It might happen that you format your VMFS with the running disks (locking mechanism will get formatted)

install ESXi on disk

When the progress bar hits 100% the Installations is done and the only task left for the installation is to remove the disc (aka .iso file) and agree to reboot afterwards.

Remove Disc before reboot

To remove the .iso file just go to the configuration and click the button next to the CD/DVD drive 1 and click Disconnect.

Disconnect VM Disc

Last step to finish installing vSphere 6.0 ESXi is to head back to the console and hit Enter to reboot the system using the freshly installed ESXi.

Next Task is the configuration of the ESXi 6.0

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.