As discussed in the Basic Guide, networking between instances in the Rapid Access Cloud is straight-forward, as each instance is assigned a private IPv4 address that can be used to communicate with each other. For networking instances with the public internet each instance is assigned a public IPv6 address, however if IPv6 can’t be used for any reason it is possible to allocate a single IPv4 address to your project.
When launching an instance in the Rapid Access Cloud, it is automatically configured to be on the "default" network provided that this is the only network available. This is the network which provides one private IPv4 address and one public IPv6 address.
In addition to the default network, you have the ability to create one or more of your own networks. This enables you to create a hierarchy of networks for your instances to do such things as create private network communication between instances or to dedicate traffic to certain networks (for example: a network that will only transmit database traffic).
To create a network, click on the Network panel in the Rapid Access Cloud dashboard:
Next, click on Create Network and follow the wizard.
You can also create and manage networks using the OpenStack command-line tool:
$ openstack network create mynetwork $ openstack subnet create mysubnet --network mynetwork --subnet-range 192.168.100.0/24 $ openstack network delete mynetwork
Once you create your own network, you will always have to specify a network when launching an instance. Instances will no longer launch on the "default" network by default.
Once your networks have been created, you can now launch instances on those networks. Choose which networks your instance will be attached to by going to the Networks tab in the Launch Wizard and select both the default and mynetwork options.
Once you have created one or more networks, you will always have to specify which networks to launch your instances on. If you have not created any self-service networks, your instance will launch on the "default" network by default. When creating instances with more than one network, it is recommended to always have "default" listed at the top.
You cannot attach networks to instances that have already been created.
In addition to creating self-service networks, you can also create your own routers to connect these networks. To create a router, click on the Network panel in the Rapid Access Cloud dashboard and click on Routers.
Next, click on Create Router and follow the wizard.
Once a router is created, it is connected to the network as specified during the setup. In order to connect it to another network, click on the router just created under Routers and navigate to the Interfaces tab. There you will be able to add an interfaces to your router. This can also be done through the Network Topology (see below).
You can also create and manage routers using the OpenStack command-line tool:
$ openstack network create mynetwork_1 $ openstack subnet create mysubnet_1 --network mynetwork_1 --subnet-range 192.168.100.0/24 $ openstack network create mynetwork_2 $ openstack subnet create mysubnet_2 --network mynetwork_2 --subnet-range 192.168.200.0/24 $ openstack router create myrouter $ openstack router add subnet myrouter mysubnet_1 $ openstack router add subnet myrouter mysubnet_2
Once the above steps are done, you can return to the dashboard and see the networks, subnets, and router in the Network Topology:
At this time it is not possible to attach a router to the "default" network. Unfortunately there is not an easy way of bridging self-service networks to the public Internet. This is currently in development and we will send a notification when this feature is available.
If you create a security group, by default it will be empty and not permit any traffic in or out. The default security group contains several rules to allow your instance to connect to the outside world that we strongly recommend adding to any security group you create if you do not plan on also including the default security group. Certain services (such as the metadata service for ssh key injection, and obtaining your IPv6 address require outbound access in order to function correctly).
Using the Command Line Tools, you can add these rules as follows:
openstack security group rule create --egress --protocol any --ethertype IPv6 <security group name> openstack security group rule create --egress --protocol any --ethertype IPv4 <security group name> # Optionally - allow all within each instance in the group openstack security group rule create --ingress --protocol any --ethertype IPv6 --remote-group <security group name> <security group name> openstack security group rule create --ingress --protocol any --ethertype IPv4 --remote-group <security group name> <security group name>