The year 2021 has just begun, and we already have the next updates to the CROC Cloud ready.
This release offers such highly-demanded functionality as connecting a virtual machine to multiple subnets and tagging support for VPCs and subnets in the Web console. Now in more details.
Connecting VM to Multiple Subnets
Now, instances in CROC Cloud can connect to subnets via several network interfaces. This feature is extremely usefull when you need to deploy virtual network appliances, separate data and control traffic, and provide different services on different interfaces.
Each instance can have up to 16 interfaces. In addition to an internal IP address, an external Elastic IP address can be assigned to a network interface, while each network interface can be assigned its own security groups (up to 5). Preconfigured interfaces can be attached to a running instance on the fly. All interfaces should be in different subnets of the same Availability Zone in VPC.
We have prepared a set of utilities (c2-ec2-netutils) to help you automatically configure VM interfaces. It is preinstalled in CROC Cloud templates marked as [Cloud Image] and can be used out of the box. This package was tested for compatibility with Debian 8, 9, and 10, CentOS 7.5, 7.8, and 8.2, and with Ubuntu 18.04 and 20.04. For other Linux and Windows builds, you will have to configure interfaces manually (you can also use c2-ec2-netutils with other Linux instances, but their operation is not guaranteed).
The Instance Wizard now features a new Network step where you can add an existing network interface or create a new one. The new interface can be configured immediately: subnet, Private IP, security groups, and a description are specified at this point. You can also assign an Elastic IP to the main network interface here. If any additional interface also requires an external IP address, you can assign it, for example, on the interface page.
All the information about network settings and security groups for each interface can now be found on a dedicated Network and Security tab of the instance page. If necessary, you can attach interfaces, assign Elastic IP, enable source/destination check, and change security groups here.
Tags for VPCs and subnets
Now in the web interface you can tag VPCs and subnets along with instances and disks. Besides the reserved
Name key, you can define your own keys for tags.
Description for VPC has been transformed to a
Name Tag. Now the
Name column is shown instead of the
Description column in the VPC table. To display it, if required, it is necessary to move the
Name block to the visible columns section in the table settings.
Deprecation of the Description for the VPC also resulted in the following changes in API methods: the CreateVpc and DescribeVpc methods no longer support the
Description parameter, and the ModifyVpcAttribute method no longer supports the
Description.Value parameter. From January 19, 2021, instead of the
Description parameter, use the tag with the
Name key from the
tagSet parameter to identify the VPC. The
tagSet parameter contains a set of all the tags associated with the resource.