Communicating with Networking Resources

Your Metacloud Networking service accommodates multiple communication configurations for virtual machines (VMs) or instances. Access to an instance depends on the security rules defined in the security group. The default security group may not have the protocols defined for sufficient access. See Configuring Access and Security for Instances.

The following networking scenarios use simplified steps and the Metacloud Network Topology to illustrate the example connection and the minimal requirements for a successful connection. To understand how to launch an instance properly, see the guided workflow in Preparing to Launch Instances.

Security
Access to instances requires SSH and ICMP (ping) protocols defined in the security group rules.

Communicating on the Same Network

When you launch an instance, the Networking service assigns the instance a fixed IP address from the subnet of the private network used in the create request. You can simply ping the fixed IP address.

To prepare two VMs to communicate on the same network:

  1. Create a private network.
  2. Create or update a security group with the protocols required to access the instance.
  3. Use the private network and the security group to launch two instances.

VM to VM on the same network

Communicating using Different Networks

There are two configurations for instances on different networks to communicate: using fixed IP addresses and a shared router or using floating IP addresses and routing through a shared gateway.

To prepare two VMs on different networks to communicate using fixed IP addresses:

  1. Create two private networks.
  2. Create a router. It is not necessary to set a public gateway.
  3. Create an interface from the router to each private network.
  4. Create or update a security group with the protocols required to access the instance.
  5. Launch an instance on each private network.

VM to VM on different networks same router

To prepare two VMs on different networks to communicate using floating IP addresses:

  1. Create two private networks.
  2. Create two routers, setting the public gateway for each router.
  3. Create an interface from each router to each separate, private network.
  4. Create or update a security group with the protocols required to access the instance.
  5. Launch an instance on each private network.
  6. Create and associate a floating IP address to each instance.

VM to VM on different networks and routers

Communicating Outside the Network

When you want your instances to communicate outside of your project (tenant), you must attach a router to the public network on an internal interface and set the gateway on the public network.

Security
Remote access requires SSH (22/tcp) or RDP (3389/tcp) protocols.

To prepare a VM to communicate through a gateway to the Internet:

  1. Create a private network.
  2. Create a router and set the public gateway.
  3. Create an interface from the router to the private network.
  4. Create or update a security group with the protocols required to access the instance.
  5. Launch an instance on the private network.

VM to the web