Migrating to Yandex Cloud with Hystax Acura
You can use Hystax Acura to migrate your cloud infrastructure to Yandex Cloud from another platform. To do so, you will need to create a Hystax Acura VM in your cloud. This VM will manage the migration process, while another VM running Hystax Acura Cloud Agent will migrate your third-party platform VMs to your cloud. Before the migration starts, the system will create VM replicas for infrastructure deployment during the migration process.
To perform the migration:
- Get your cloud ready.
- Create a service account and authorized key.
- Configure the network traffic permissions.
- Create a VM with Hystax Acura.
- Configure Hystax Acura.
- Prepare the Hystax Acura Cloud Agent.
- Create VM replicas.
- Create a migration plan.
- Start migration.
If you no longer need the resources you created, delete them.
Get your cloud ready
Sign up for Yandex Cloud and create a billing account:
- Go to the management console
and log in to Yandex Cloud or create an account if you do not have one yet. - On the Yandex Cloud Billing
page, make sure you have a billing account linked and it has theACTIVE
orTRIAL_ACTIVE
status. If you do not have a billing account, create one.
If you have an active billing account, you can go to the cloud page
Learn more about clouds and folders.
Required paid resources
Note
Note that both the infrastructure for Hystax Acura and the cloud agent as well as all migrated VMs will be charged and counted against the quotas
- A VM for Hystax Acura uses 8 vCPUs, 16 GB of RAM, and a 200-GB disk.
- A Hystax Acura Cloud Agent VM uses 2 vCPUs, 4 GB of RAM, and an 8-GB disk.
The cost of resources for Hystax Acura Migration includes:
- Fee for disks and continuously running VMs (see Yandex Compute Cloud pricing).
- Fee for storing images (see Compute Cloud pricing).
- Fee for a dynamic or static public IP address (see Yandex Virtual Private Cloud pricing).
- Fee for each completed migration (see product description in Cloud Marketplace).
Create a service account and authorized key
Hystax Acura Migration will run under a service account:
- Create a service account named
hystax-acura-account
with theeditor
andmarketplace.meteringAgent
roles. - Create a service account authorized key.
Save the following details since you will need them in the next steps:
- Service account ID.
- Service account authorized key ID.
- Service account private authorized key.
Configure network traffic rules
Configure network traffic rules for the default security group. If it is unavailable, it will allow any inbound or outbound VM traffic.
If the default security group is available, add the following rules to it:
Traffic direction |
Description | Port range | Protocol | Source / Destination name |
CIDR blocks |
---|---|---|---|---|---|
Inbound | http |
80 |
TCP |
CIDR |
0.0.0.0/0 |
Inbound | https |
443 |
TCP |
CIDR |
0.0.0.0/0 |
Inbound | https |
4443 |
TCP |
CIDR |
0.0.0.0/0 |
Inbound | vmware |
902 |
TCP |
CIDR |
0.0.0.0/0 |
Inbound | vmware |
902 |
UDP |
CIDR |
0.0.0.0/0 |
Inbound | iSCSI |
3260 |
TCP |
CIDR |
0.0.0.0/0 |
Inbound | udp |
12201 |
UDP |
CIDR |
0.0.0.0/0 |
Inbound | tcp |
15000 |
TCP |
CIDR |
0.0.0.0/0 |
Outbound | http |
80 |
TCP |
CIDR |
0.0.0.0/0 |
Outbound | https |
443 |
TCP |
CIDR |
0.0.0.0/0 |
Outbound | vmware |
902 |
TCP |
CIDR |
0.0.0.0/0 |
Outbound | vmware |
902 |
UDP |
CIDR |
0.0.0.0/0 |
Outbound | iSCSI |
3260 |
TCP |
CIDR |
0.0.0.0/0 |
Outbound | udp |
12201 |
UDP |
CIDR |
0.0.0.0/0 |
Save the security group ID You will need it when creating the Hystax Acura VM.
Create a VM with Hystax Acura
Create a VM with a boot disk from the Hystax Acura Migration in Yandex Cloud image.
-
In the management console
, select the folder where you want to create your VM. -
From the list of services, select Compute Cloud.
-
In the left-hand panel, select
Virtual machines. -
Click Create virtual machine.
-
Under Boot disk image:
- Go to the Marketplace tab.
- Click Show all Marketplace products.
- In the list of public images, select Hystax Acura Migration in Yandex Cloud and click Use.
-
Under Location, select an availability zone where your VM will reside.
-
Under Disks and file storages, specify the boot disk size:
200 GB
. -
Under Computing resources, select the
8 vCPU
and16 GB
configuration. -
Under Network settings:
-
In the Subnet field, enter the ID of a subnet in the new VM’s availability zone. Alternatively, select a cloud network from the list.
-
Each network must have at least one subnet. If there is no subnet, create one by selecting Create subnet.
-
If you do not have a network, click Create network to create one:
- In the window that opens, enter the network name and select the folder to host the network.
- Optionally, enable the Create subnets setting to automatically create subnets in all availability zones.
- Click Create network.
-
-
If a list of Security groups is available, select the one whose network traffic permissions you previously configured. If this list is not there, all inbound and outbound traffic will be enabled for the VM.
-
-
Under Access, select SSH key and specify the VM access credentials:
- In the Login field, enter a username, e.g.,
yc-user
. -
In the SSH key field, select the SSH key saved in your organization user profile.
If there are no saved SSH keys in your profile, or you want to add a new key:
- Click Add key.
- Enter a name for the SSH key.
- Upload or paste the contents of the public key file. You need to create a key pair for the SSH connection to a VM yourself.
- Click Add.
The SSH key will be added to your organization user profile.
If users cannot add SSH keys to their profiles in the organization, the added public SSH key will only be saved to the user profile of the VM being created.
- In the Login field, enter a username, e.g.,
-
Under General information, specify the VM name:
hystax-acura-vm
. -
Under Additional, select the
hystax-acura-account
service account. -
Click Create VM.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder through the --folder-name
or --folder-id
parameter.
Run this command in the terminal:
yc compute instance create \
--name hystax-acura-vm \
--zone <availability_zone> \
--cores 8 \
--memory 16 \
--network-interface subnet-id=<subnet_ID>,nat-ip-version=ipv4,security-group-ids=<security_group_ID_if_group_set_up_previously> \
--create-boot-disk name=hystax-acura-disk,size=200,image-id=<Hystax_Acura_image_ID> \
--service-account-id <service_account_ID> \
--ssh-key ~/.ssh/id_ed25519.pub
Where:
-
name
: VM name, e.g.,hystax-acura-vm
. -
zone
: Availability zone, e.g.,ru-central1-a
. -
cores
: Number of vCPUs. -
memory
: RAM size. -
network-interface
: VM network interface description:-
subnet-id
: VM subnet.You can get the list of subnets using the
yc vpc subnet list
CLI command. -
nat-ip-version=ipv4
: Use a public IP address. -
security-group-ids
: Security groups.You can get the security group list using the
yc vpc security-group list
command. If you skip this parameter, the system will assign the default security group to the VM.
-
-
create-boot-disk
: Create a new VM disk:-
name
: Disk name, e.g.,hystax-acura-disk
. -
size
: Disk size. -
image-id
: Disk image ID.For this example, use
image_id
from the Cloud Marketplace product description.
-
-
service-account-id
: ID of the previously created service account.You can get the list of accounts using the
yc vpc security-group list
command. -
ssh-key
: Path to the public SSH key file.
Configure Hystax Acura
-
In the management console
, open thehystax-acura-vm
VM page and find its public IP address. -
Enter the
hystax-acura-vm
VM public IP address in your browser address bar. This will open the Hystax Acura initial setup screen.Note
Booting the Hystax Acura Migration VM for the first time will trigger an installation process which may take over 20 minutes.
-
By default, a Hystax Acura VM has a self-signed certificate.
-
When the setup prompts you to fill out the user profile data, use the values below:
- Organization: Name of your organization.
- Admin user login: Email address you will use as the admin username.
- Password: Admin password.
- Confirm password: Re-enter the admin password.
-
Click Next.
-
Specify the Yandex Cloud connection settings:
-
Service account ID: ID of the service account.
-
Key ID: Service account authorized key ID.
-
Private key: Service account private key.
Note
If you obtained the ID and private key in a JSON file, e.g., when creating an authorized key via the CLI, remove the line break characters (
\n
) from the ID and the private key. -
Default folder ID: Your folder ID.
-
Availability zone:
hystax-acura-vm
VM availability zone. -
Hystax Service Subnet:
hystax-acura-vm
VM subnet ID. -
Public IP address of the Hystax Acura control panel: Public IP address of
hystax-acura-vm
you got in step 1. -
Additional parameters: Do not edit this field.
-
-
Click Next.
Hystax Acura will automatically check whether it can access your cloud. If everything is correct, you will be able to log in to the Hystax control panel with the email address and password you set previously.
Prepare and install migration agents
You need to install migration agents on the VMs you will be migrating to Yandex Cloud. To download and install the agent, do the following:
-
If you are migrating from VMware ESXi, Microsoft Hyper-V, or any other hypervisor different from KVM, install virtio drivers on the VM before the migration.
-
In the Hystax Acura control panel, select the Download agent tab.
-
Select one of the agent types depending on your OS:
- VMware
- Windows
- Linux
Click Next.
-
Download and install the agent on the VMs you are migrating:
VMwareWindowsLinux-
Select New VMware vSphere and fill out these fields:
- Platform name: Name of your platform.
- Host IP address: IP address of the VMware ESXi host where you will deploy the replication agent.
- Login: Your login.
- Password: Your password.
Click Next.
-
Click Download agent and wait for the download to complete.
-
Unpack the downloaded OVA file to the VMs in your cluster.
-
Start the VMs with the agent.
- Click Next.
- Click Download agent and wait for the download to complete.
- Unpack the archive and run
hwragent.msi
on the VMs you want to migrate.
- Select Linux distribution:
- CentOS/RHEL (.rpm package): CentOS or Red Hat-based.
- Debian/Ubuntu (.deb package).
- Select the driver installation method:
- Pre-built: Install a driver binary.
- DKMS: Compile the modules during installation.
- Click Next.
- You will get agent installation commands you can run following the instructions for your distribution and installation method.
-
The VM will appear in the target group a few minutes after the agent is installed.
Create VM replicas
Alert
When replication starts, Hystax Acura will create a new Hystax Acura Cloud Agent VM to run operations in your cloud.
Start replication:
- Click the Hystax logo.
- Under Machines Groups, select the virtual machines to replicate.
- You can specify additional parameters for the
network-ssd
volume in the replication editing menu. - Click Bulk actions and in the menu that opens, select Start replication.
A VM replica will include all original VM data; therefore, replication can take around 40 minutes. You will be able to see the replication status in the Status column under Instance groups. Wait for the status to change to Synced
and check whether there are VM replicas in the Compute Cloud list in your folder.
Create a migration plan
When the VMs you are replicating switch to Synced
, you can create a migration plan. The migration plan defines the list of VMs to migrate and the order in which they will start in your cloud.
- Click Add Migration plan.
- Specify the migration plan name:
YC Migration
. - Under Devices & Ranks, click
. In the menu that opens, click Add machine, select the instance group and then the VM you want to add to the migration plan. Repeat the steps for all VMs you are going to migrate. - In the Subnet ID and the CIDR fields, specify the ID and CIDR of the subnet where the VMs will get connected after migration.
- Expand the device description and specify the new VM parameters in the Flavor name field in this format:
<platform>-<cpu>-<ram>-<core_fraction>
, e.g.,2-8-16-100
. - In the Port ip field, specify a new IP from the current subnet for the VM.
- Click Save.
Start migration
Perform the migration according to the plan:
- Open the Migrate tab.
- Select the
YC Migration
plan and click Next. - Specify
CloudSite
in the Cloud Site Name field. - Make sure all required resources are in the list and click Run migration.
The migration process may take about 10 minutes. You can see the status of the VMs being migrated in the Status column under Machines. Wait for the status to change to Running
, then make sure all the resources have been transferred and your applications are ready to run. If the migrated infrastructure is working correctly, click Detach on the CloudSite page and confirm the detach action.
How to delete the resources you created
To stop paying for the migration infrastructure:
If you reserved a public static IP address, delete it.