Crm I Can Install On Kvm Free Download
Crm I Can Install On Kvm Free Fire
Crm I Can Install On Kvm Free Online

If you have just virtualized the VMware ESXi server on top of KVM, the next step will be to install vCenter for its centralized control and additional feature set and management capabilities.

In my last article we took KVM running on bare metal and deployed an ESXi host on top of it.

In this article, we will deploy the vCenter Server Appliance (vcsa) on top of the ESXi server as its own virtualized guest OS.

This will be done with the help of a staging KVM Linux guest (‘inst1’) where we will mount the vsca ISO downloaded from vmware.com and run the vcsa CLI installer.

Prerequisites

ESXi

The first prerequisite is obviously an instance of ESXi. In this series of articles I am virtualizing on top of KVM. You can install KVM on your Ubuntu host and then install ESXi on top of KVM.

The free trial version of Sales Organizer comes with all the CRM features you can ask for and more; all you need to do is plug it into a scanner and start compiling. All premium features are included in the trial version; purchase order, tax specific items, bar code scanning and printing. KVM Over IP is especially advantageous for MSPs who manage technology infrastructure for their clients. Rather than send a technician to a site, MSPs can manage virtually all PC tasks remotely. A single admin can manage PCs across an enterprise with endpoints distributed around the globe. Safer work environments.

Take note that the vcsa installer even in ‘tiny’ mode mandates the ESXi host have 10Gb of memory and 2 vCPU. This can be decreased later for lab environments.

VCSA ISO

Download an evaluation version of vCenter, which comes as a 3.4Gb ISO file. You will need a VMware account.

Ubuntu host for deploying vcsa

The vcsa install can be done from either a Windows or Linux 64 bit host with network connectivity to ESXi. We are going to use a KVM virtualized Ubuntu host named ‘inst1’ to mount the vCenter ISO as the CDROM, and run the command line installer.

Understand this is a throwaway VM only being used to install vcsa, after which it can be discarded.

First, download the Ubuntu network installer named “mini.iso” to your Downloads directory. Then create a small KVM guest OS named “inst1”.

Go through the full Ubuntu installation process accepting all defaults in order to build a basic Ubuntu guest OS. When you get to Software selection, choose “Basic Ubuntu server” and “OpenSSH server”. This whole process should take around 15-30 minutes.

When it gets to the end of the installation process, and asks you to eject the CDROM and restart, go ahead and run the following virsh commands at a console before pressing <ENTER> on the Ubuntu installer screen.

Wait for Ubuntu to stop the guest OS, then start the ‘inst1’ guest OS back up using virsh.

After a minute you should be greeted with a console based login prompt. Login with the credentials you used during the Ubuntu setup.

Prepare DNS for vcsa installation

One of the most important prerequisites before installing vcsa is ensuring that you have full DNS resolution AND reverse lookup for both the ESXi host and the yet to be created vCenter host. I can’t stress this point enough, there are various cryptic errors you will get during the install process if FQDN and IP lookup are not configured.

You could set this resolution up on your router, or a global instance of dnsmasq on your host, or you can use the dnsmasq instance that runs for your default libvirt virtual network.

For this article, since all host are being built in the libvirt default 192.168.122.0 virtual network, I’ll modify that specific dnsmasq instance for DNS resolution.

I’m going to assume the ESXi host is at 192.168.122.133 and is named “esxi1.home.lab”. And the yet to be installed vCenter server will be 192.168.122.51 and named “vcenter.home.lab”.

Use virsh to edit the default network:

And add the following content right before the <ip> element:

Then restart the default virtual network.

And test both name and reverse lookup for the names and IP addresses.

Because we’ve used the virtual network dnsmasq instance, this resolution will not work from your host browser or console by default. If you need these exposed in a larger context, you can setup a service instance of dnsmasq on your host.

Run installation from temporary host

Now let’s use the temporary staging VM ‘inst1’ to install vcsa. This guest holds no purpose other than to run the vcsa installer.

Attach ISO to CDROM device

Mount CDROM within OS

Validate DNS resolution

Because it is so important to the install process, we need to ensure we have full name and IP resolution from this host. If you have DNS configured as suggested using the dnsmasq for the default virtual network, then “/etc/resolv.conf” should be pointing at 192.168.122.1.

JSON configuration

The cli installer is driven by values you set on a json file. The full list of templates available is located on the ISO at “vcsa-cli-installer/templates/install”, the template we are basing this article on is “embedded_vCSA_on_ESXi.json”

Download this json from my github project and place it into the home directory of inst1.

The “esxi” section is pointing to the target ESXi host, credentials, and network/datastore names. The “appliance” section is the name of the appliance that will be created. The “network” section lists the network details of the appliance including name, IP, DNS server, and FQDN of the appliance. The “os” section provides configuration details of the appliance including default password. And the “sso” section provides the single sign-on domain and password (“vsphere.local” domain is the default).

Run the installer

Finally we are at the point where we can run the installer. Go into the “vcsa-cli-installer directory and run the installer like below, specifying our json file in the home directory.

The install will take 20+ minutes, and there will be lots of output to the console, but in the end you should see output similar to below.

If you see certificate or thumbprint errors, the most common problem is DNS not being both name and reverse resolvable.

Validate Install

vCenter Appliance Administration Interface

The first validation of the vcsa install can be done by pulling up the vCenter Appliance Administration interface (VAMI). The VAMI can accessed at port 5480 and provides basic administration of the appliance itself.

Depending on where you have configured DNS, it can be reached either by its FQDN or IP address.

https://vcenter.home.lab:5480 OR https://192.168.122.51:5480

user/pass=Administrator@vsphere.local/ExamplePass@456

vSphere Web Client

The next validation is of the vCenter web interface. Depending on where you have configured DNS, it can be reached either by its FQDN or IP address.

https://vcenter.home.lab OR https://192.168.122.51

user/pass=Administrator@vsphere.local/ExamplePass@456

vCenter Configuration

The first thing you will want to do is create a new datacenter and then add the ESXi instance to the datacenter.

New datacenter

Right-click on the main root node in the left hand tree view “vcenter.home.lab” and select “New Datacenter” with the name “mydc1”.

Add ESXi host

Crm I Can Install On Kvm Free Download

Then right-click on “mydc1” from the left hand tree view and select “Add Host”. Enter the hostname of the ESXi host “esxi1.home.lab”, the credentials to connect to ESXi (user=root) accepting any host certificates. Assign the evaluation license, lockdown mode disabled, and “Finish” the wizard dialog.

This should provide you a basic setup as shown below.

Note that you will see “vcenter” listed as a host under “esxi1.home.lab”. This is the virtualized vcenter appliance you just installed.

REFERENCES

https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-vcenter-server-67-installation-guide.pdf (pdf official)

https://xenappblog.com/2018/automatically-deploy-vmware-vcsa/ (sample json)

vcsa sample json: sample json and sample json

https://s3.amazonaws.