Windows instance using the web interface

Log in to the dashboard at https://dashboard.cloud.catalyst.net.nz/

As a new user to the Catalyst Cloud, your initial cloud project will come with a pre-configured private network and a router connected to the internet. If you have deleted this, or would like to create additional networks then please see Creating the required network elements for details on how to do that.

Otherwise, let’s proceed with building your first instance.

Configure Instance Security Group

You will add a security group and a rule for your instance so that it can be accessed using SSH.

Navigate to the “Security Groups” tab of the “Access & Security” section and click “Create Security Group”:

../_images/fi-security-group-create-1.png


Enter a name and description and click “Create Security Group”:

../_images/fi-security-group-create-2.png


Now click on “Manage Rules” for the group you have created:

../_images/fi-security-group-rules-manage.png


Click on “Add Rule”:

../_images/fi-security-group-rule-add.png


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”.

../_images/fi-rdp-rule.png


Warning

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 limit the exposure of your compute instances and services to IP addresses or subnets that are trusted.

Booting an Instance

We are now ready to launch your first instance. Select launch instance from the instances list:

../_images/fi-instance-launch.png


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 a 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”.

../_images/fi-windows-volume.png


For a Windows instance the recommended minimum flavor is c1.c2r2. Select this from the list and click “Next”:

../_images/fi-windows-flavor.png


Select the private-net network from the list and click “Next”:

../_images/fi-launch-instance-networks.png


Select the first-instance-sg security group from the list and click “Next”:

../_images/fi-launch-instance-security-groups.png


No key pair is required for a Windows instance. Click “Next”:

It will take a few seconds for your instance to build. You will see the Status, Task and Power State change during this process. When complete, the status will be “Active”. You now have a running instance, but there are a few more steps required before you can log in.

Allocate a Floating IP

To associate a floating IP with your instance, you need to navigate to the “Floating IPs” tab of the “Access & Security” section.

If an IP address has not yet been allocated, click on “Allocate IP to Project” to obtain a public IP. Then, select an IP that is not currently mapped and click on “Associate”:

../_images/fi-floating-ip.png


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 them.

In this example, select the “first-instance” port and click “Associate”:

../_images/fi-floating-ip-associate.png


Connect to the new Instance

First you must 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.

../_images/fi-windows-login.png


You will then be prompted by the following screen to create a new administator password.

../_images/fi-windows-login-2.png


Upon completion of this step, it will be possible to connect to this instance with an RDP application. Connect via the floating public IP that you associated with your instance in the previous step. This address is visible in the Instances list and under the Floating IPs tab in Access & Security.