Log in to the dashboard at https://dashboard.cloud.catalyst.net.nz/
We need to create a router and network/subnet.
Navigate to the “Routers” section and click “Create Router”:
Name the router “border-router”, select admin state “UP” and select “public-net” as the external network:
Navigate to the “Networks” section and click “Create Network”:
Name your network “private-net”, select create subnet and click “Next”:
Name your subnet “private-subnet”, choose an address for your subnet in CIDR notation and click “Next”:
Specify additional attributes for the subnet including enabling DHCP, specifying the DNS Name Servers for your region and optionally defining an allocation pool:
Click on the router name in the router list:
Select the “Interfaces” tab and click “+Add Interface”:
Select the correct subnet:
You should now have a network topology this looks like this:
We need to create a security group and rule for our instance.
Navigate to the “Security Groups” tab of the “Access & Security” section and click “Create Security Group”:
Enter a name and description and click “Create Security Group”:
Now click on “Manage Rules” for the group we have created:
Click on “Add Rule”:
Create a rule to allow RDP access. This can be selected from the Rule drop down menu, leave the defaults for the other fields. Click “Add”.
Note that by using the CIDR 0.0.0.0/0 as a remote, you are allowing access from any IP to your compute instance on the port and protocol selected. This is often desirable when exposing a web server (eg: allow HTTP and HTTPs access from the Internet), but is insecure when exposing other protocols, such as SSH, Telnet and FTP. We strongly recommend you to limit the exposure of your compute instances and services to IP addresses or subnets that are trusted.
We are now ready to launch our first instance, select launch instance from the instances list:
When creating a windows instance you need to select the windows-server-2012r2-x86_64 image from the image list first, then select “Yes” to create new volume. An alert symbol will appear alongside the Size(GB) selector. If you hover the mouse on this it will show the minimum size of the volume required to host the windows image. Set an appropriate volume size, select “No” to Delete Volume on Terminate then click “Next”.
For a windows instance the recommended minimum flavor is c1.c2r2, select this from the list and click “Next”:
Select the private-net network from the list and click “Next”:
Select the first-instance-sg security group from the list and click “Next”:
No key pair is required for a windows instance, click “Next”:
Your instance will now be built, you will see the Status, Task and Power State change during this process which will take a few seconds. When the process is complete the status will be “Active”. We now have a running instance but there are a few more steps required before we can login.
To associate a floating IP you need to navigate to the “Floating IPs” tab of the “Access & Security” section.
If you do not have an IP allocated, first click on “Allocate IP to Project” to obtain a public IP. Then, select an IP that is not currently mapped and click on “Associate”:
Select the port you wish to be associated with the floating IP. Ports are equivalent to virtual network interfaces of compute instances, and are named after the compute instance that owns it.
In this example, select the “first-instance” port and click “Associate”:
First you need to set the Administrator password. To do this go to the “Instances” section, click on first-instance under “Instance Name” and select the “Console” tab.
Once the following screen loads, click on OK to continue.
You will then be prompted by the following screen to create a new administator password.
Once this step has been completed it will be possible to connect to this instance with an RDP application via the floating public IP that we associated with our instance in the previous step. This address is visible in the Instances list or under the Floating IPs tab in Access & Security.