3.2. Deploying Hystax Acura Solution on Virtuozzo Hybrid Infrastructure

At this stage we will log in to our Acura Service Project, create an overlay network and a router which will be configured to enable SNAT for the Acura Instance. We will then have the necessary resources to deploy the Hystax Acura migration Solution and assign a Floating IP to the instance.

  1. Login to the Acura Service Project from the self-service portal using the URL https://fqdn:8800.

  2. Create a Network. This will be a virtual network, which later will be attached to the Hystax Acura Solution instance. Networks > Create Virtual Network. We will name this network vm-network in this example.

  3. Create a Router. This router will Allow us to provide SNAT (Outbound access) to the Hystax Acura Solution instance. Please note how we connect the physical external network named “public” with the newly created virtual network named vm-network.

  4. Deploy an instance using the Hystax Acura golden image downloaded. Remember to attach a keypair, this will grant you access to the Acura instance. Create the instance with the following info:

    • 8 vCPUs, 16 GB RAM, 100 GB disk (Xlarge flavour).

    • Image Hystax_Acura_VA_MGR_Virtuozzo_X_XXX

    • Use the Default Security Group.

    • Image Hystax_Acura_VA_MGR_Virtuozzo_X_XX

    • Add a network interface, in this case we will add the vm-network to this instance.

    • Add your SSH key pair to the instance.



    Adding a key pair is highly recommended to provide you with SSH access to the machine. Although Hystax Engineering team will be able to perform maintenance checks and troubleshooting (as long as the network is reachable and your security groups allow the corresponding traffic), it is better to have your own means of accessing the Acura instance.

    It takes from 10 to 20 minutes for the services to start and the Web UI to become available.

  5. Assing a floating IP to the newly created Hystax Acura instance. Logged to the self-service portal https://your-fqdn-vhi.com:8800. And login to the Acura Service domain using the user defined for this domain. Go to Floating IPs, click on add. Note that we are using Private IPs, but in a real scenario this should be a Public IP.

  6. Troubleshooting tip: The web UI for the Hystax Acura Solution instance, will take from 10 to 20 minutes to bring all the services up. Hystax Acura uses Kubernetes to manage the services inside the instance. If after 20 minutes you still have no access to the web UI, SSH in to the Acura instance and check the status of the services. SSH with the user “user” and execute the command kubectl get pods (This command will gather information about pod(services) status). When you see all the pods in Running status (except for four that will be in completed status) the web UI will be available.


    If after 20 minutes, instead of getting the pod status you get a connection refused message, please contact us.

  7. Open a web browser and go to https://<ip_address of the machine>/. You will be redirected to the Hystax Setup Wizard. After you perform all the steps, the installation will be complete, and you will be able to start using Hystax Acura.

    1. Step 1: Enter the organization name, you can enter here your company name, this step creates the login user and password and associates it to whatever organization name you wish to provide. Add the Admin user login and Password. This will be the user account for logging in to Hystax Acura Control Panel and managing the system. If there are any errors, the system will notify you.

    2. Step 2: Fill in your Hystax License key that was supposed to be shared with you in advance as well as the settings for accessing your mail server, which will be used to send notifications from Acura and generate periodic reports.


      SMTP server with TLS/SSL encryption is required to proceed with deployment.

      If you prefer a public SMTP server associated with your email address (gmail, yahoo etc.), please find its settings online. In the case of a private SMTP server, contact your network administrator for further details.

      A sample notification will be sent to the specified “Test email” to verify the functionality when you click “Next”.

    3. Step 3: Fill in all the fields by providing cloud configuration details. Use question mark icons to get hints on the fields. After you click “Next”, the Setup Wizard will validate the entered data and notify you in case of an error.


      Step 3 of the configuration wizard goal, is to configure what we refer to as target cloud. We are configuring our customer target project, where the replicated workloads will be migrated to.

      • The Keystone API endpoint URL, is the fqdn of your Virtuozzo Hybrid infrastructure Admin panel listening on port 5000 (make sure the compute API traffic type is on the public network) will be used to authenticate for authentication.

      • User Domain, this field refers to the domain name the user is part of. Remember in our example, the domain for our customer is Ringo-Cloud then we created the project named migration-infra and a user migration-user which was assigned to the project and belongs to the Ringo-Cloud domain.

      • Username, the user we created an associated to the target project migration-infra as Project Member. In this case the user is migration-user.

      • Target Project Domain, this is the customer domain, the same as the User Domain and is the domain where we created the project. In our example the name is Ringo-Cloud.

      • Target Project ID, the UID for the project migration-project. The Target project ID, can be found by logging in to your Virtuozzo Hybrid Infrastructure Admin Panel > Projects and Users > Click on the Domain > Click on the Target Project and the ID will be visible on the left-hand side sliding panel that will appear.

      • Hystax Service Network, Network that will be used for Hystax Cloud Agent machines. Should be the same or routable to the network in which a Hystax Acura instance is located. In our case we have already prepared a physical external network type named public for this purpose in previous steps.

      • Floating IP network, this is the name of the network you wish to use to provide floating IPs to your migrated instances. In our case is the same physical external network named public.

      • Hystax Acura Control Panel Public IP, Public IP that will be used to access the Hystax Control Panel via web browser and by replication agents.

      • Additional Parameters, add additional parameters to customize integration.

      Example information gathering form:




      Keystone API Endpoint

      VHI Keystone Auth URL


      User Domain

      User domain name to access VHI



      Username to access VHI Project



      Password to access VHI


      Target Project Domain

      Target VHI project domain name


      Target Project ID*

      Target VHI project ID where replicated workloads will be spun up

      c57dd14c08bc4d6780ab17 87774fd6e8

      Hystax Service Network

      Network that will be used for Hystax Cloud Agent machines.


      Floating IP Network

      External network that will be used to attach Floating IPs to migrated machines


      Hystax Acura Control Panel Public IP

      Public IP that will be used to access the Hystax Control Panel via web browser and by replication agents

      Public IP

      Additional Parameters

      p2v - Sets type of Physical to Virtual to integration (Virtuozzo)
      Extends cloud site timeout (adds support for virtuozzo cinder (vstorage))

      {“p2v_type”: “virtuozzo”, “cloud_site_timeout_min”: 2880}

      The specified Virtuozzo Hybrid Infrastructure Platform user should have the following rights for Hystax Acura to operate correctly.

      • Import image

      • Launch instance

      • Create volume

      • Attach volume to instance

      • Detach volume from instance

      • Create volume snapshot

      • Create volume from snapshot

      • Remove snapshot

      • Remove volume

      • Manage networks

      The user we created had the assigned role “Project Member” which include all of the above.

    4. Step 4: Installation is complete, and you can now log in to the system using credentials entered in the previous step.