Appliances

Overview

Sharing, provisioning and consuming cloud images is one of the main concerns when deploying Cloud. HyperCX marketplaces allow users to quickly get the necessary templates to instantiate new Virtual Machines. These marketplaces can be seen as external data stores, their purpose is to offer several pre-configured applications such as CRM, ERP, Online Billing, Wikis, Online Stores, Development Tools, among many more and Operating Systems ready to be used. Download the appliances that suit you, click on it, wait a few minutes to deploy the VM and VOILA! You will immediately have a preconfigured template waiting to be initiated.

Operating Systems can be installed from scratch inside HyperCX, or be installed locally and the virtual disk uploaded after to be used in one or many VMs, but this approach is not recommended. Instead, Virtalus recommends it's users to use the existing appliances on the provided marketplaces. These appliances are optimized and contextualized to work with HyperCX.

Getting Started

Importing an appliance

With HyperCX GUI existing appliances can be easily downloaded

  1. Appliances can be accessed under Storage 🡪 Apps.

  1. Once in the Apps UI select an existing appliance and click on the appliance to view its description.

  2. Now click on icon to start the template creation process.

  3. Enter the template name, its Image name and click on.

  4. Wait for the Image to be downloaded. It’s status can be checked by:

C:\Users\Cloudsynergi\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Appliances2.png

  1. Accessing Storage -> Images.

  2. The status of the image will be LOCKED while the download is in progress.

  3. Once the image is downloaded its status is changed from LOCKED to READY, only then this appliance can be instantiated on the cluster.

Click here to learn more about templates and images.

Every time a marketplace appliance is downloaded, a new image and template will be created.

Appliance categories

Appliances offered by HyperCX can be catalogued into 4 main groups:

Open Source Operating Systems for Virtual Machines

HyperCX provides the most common Linux Operating Systems already pre-installed and contextualized so they can integrate with the platform. Operating systems in this category use the KVM hypervisor, so they are considered Virtual Machines. These are the existing open source distributions available on the marketplace as VMs:

  • Debian
  • Ubuntu
  • CentOS
  • Fedora
  • Devuan
  • Alpine Linux
  • OpenSUSE
  • Ttylinux
  • FreeBSD

Note

Although root password can be modified on the template (or during instantiation) for HyperCX open source operating systems, both in VMs and containers (described below), this is not a recommended approach. Instead, users are encouraged to configure their public key(s) on the user's settings and connect via passwordless ssh to the VM. It is recommended to change the default password after the first login.

Open Source Operating Systems for containers

Some of the previously mentioned operating systems are also available as containers. These appliances will use the LXD hypervisor and can only be deployed on HyperCX clusters with support for containers. These are the existing open source distributions available on the marketplace as containers:

  • ubuntu_xenial-LXD
  • ubuntu_bento-LXD
  • debian_buster-LXD
  • centos_7-LXD
  • centos_8-LXD
  • alpine_3.11-LXD

They can be easily recognized since they have the LXD sufix.

Note

For Linux VMs and containers, when the VNC is launched, the console will appear on the login screen. In case of containers, the "login" command is used for this. This does not work on Centos containers due to limitations of this OS and LXD containers so it is disabled. If you open the VNC terminal from HyperCX Web Portal on a Centos container, it will send you directly to a sheell (no login is asked).

Windows Virtual Machines

Some Windows versions are also available on the marketplace. These appliances will provide a trial period between 4 to 6 month, but the license is to be configured by the end user. Currently, the following versions of Windows can be found on the marketplace:

  • Microsoft Windows 10

  • Microsoft Windows Server 2012

  • Microsoft Windows Server 2016

  • Microsoft Windows Server 2019

Note

While configuring a root password for open source appliances is optional and not recommended, it is mandatory in Windows appliances.

Open Source Appliances

HyperCX is fully integrated with Turnkey GNU/Linux. Turnkey GNU/Linux is a free Debian based library of system images that pre-integrates and polishes the best free software components into secure, easy to use solutions. Thanks to this integration, HyperCX leverages the biggest Open Source appliances repository, accessible through the Virtalus marketplace, preconfigured on every Bento cluster. The following link can be checked for a complete list of Turnkey appliances available on the marketplace.

For each appliance, an URL can be found on the appliance's description that points to the appliance's configuration guide.

Example:

Users

After the appliance is instantiated for the first time, an automatic setup will be launched. This setup will query the user with some basic configuration aspects of the service (like passwords). This setup can only be seen by launching the VNC console from HyperCX's web page. After the appliance is properly configured, all the services and how to access them will be shown.

HyperCX context service, pre-installed on every appliance, will take priority over any OS configuration. This means that, if you set an IP or a password via template, and you change it later on on the OS, it will revert back after the VM is rebooted (because it will trigger the contextualization service during start up. This implies some basic recommendations:

  • Although password can be set on the template, it is recommended to leave it blank since the appliance will ask for one and configure it when the appliance is launched for the first time.
  • Network is configured from HyperCX, but some appliances will ask for a network configuration because it is needed to configure it's service. In this cases, you will need to use the same configuration provided by HyperCX (assigned IP, netmask, gateway, etc). This information is shown on the network tab of the VM.

If a public key is configured in the user's settings, these VMs will allow to ssh without password to the root account. They also have a pre-installed web console that can be used to log in with the root password configured during the first deployment.

FAQs

Q: No network on the VM that was created using a downloaded appliance.

A: The template must be updated in order to add network. Click here to learn more about how to attach an NIC (Network Interface Card). Templates are preconfigured but they are designed in a way that it works with every HyperCX platform that Virtalus offers. The Virtual Network can also be selected during instatiation.