Using Public IP Settings

Transcription

1 Using Public IP Settings Interoute Virtual Data Centre Peter Farmer VDC Appliance Development Manager Interoute 01

2 Using Public IP Settings The Interoute Virtual Data Centre (VDC) Public IP Settings allow you to allocate Internet routable IP addresses to your account. Via the portal you can forward various ports into your virtual machines to allow services to be available on the Internet. In the following, we ll setup a small tiered load balancer and webserver farm and give the Internet access to it. 2

3 Login to the Interoute hub and select Public IP Settings. Then select a suitable RFC 1918 subnet you wish to use for your DMZ and enter the Gateway address you wish to use. Find out more Stand 531 3

4 Allocate two Public IP addresses and then go to the VDC Control Centre. 4

5 Once in the Control Centre navigate to the Virtual Datacenters tab, and select the Virtual Datacenter you used for the Public IP Settings page, and add a new Virtual Appliance (vapp). 5

6 Once you click Accept the new vapp should open automatically and deploy a Windows 2008 Enterprise Server. This will act as a management server for the setup. Then click the save icon. 6

7 Once the vapp has saved, click the cog icon for the new VM to set it up. 7

8 The Configuration dialog box will now open. Choose the Network tab and then click the plus sign to add a network interface. 8

9 The Assign new Network Interface dialog will then open. Select the External tab and the DMZ network. Then select an IP address from the list. Please note that the gateway IP Address is not shown because this has been allocated to Interoute s infrastructure. Click Accept. 9

10 Now you are back on the Configuration dialogue box where you can click on the Save button. 10

11 Change the default gateway to the gateway of the DMZ network, (in this example ) and then click Save. 11

12 Now delete NIC 0, by selecting it and clicking the minus icon. 12

13 Click the Save button and then you can Close. 13

14 Now deploy the vapp, by clicking the deploy button in the top right hand corner of the Virtual Appliance pane. 14

15 Now return to the Public IP Settings to setup the port forwarding for RDP to the Management Server. Click on the Port Mapping tab. Select the first Public IP Address from the Public IP dropdown, enter 3389 into the Public Port and then enter the fourth part of the IP address you allocated to your Management Server (in this example it is 2 ). Then click Add Port Mapping. 15

16 Now move to the Access Control tab. Please note that both of the Public IP addresses are in the Policy: Deny box. This means that we need to add explicit Access Control rules in order to allow access to them. 16

17 We have two options, either move the IP address to the Policy: Allow box, or add an explicit rule allowing access from your IP address. To do the former, click the arrow pointing towards the Policy: Allow box. 17

18 To do the latter, add the details to rule dialog, select Allow and then click Add Access Rule: 18

19 Now click Save This will push your new rules to the firewall system for validation, and update the firewall configuration. 19

20 You should now be able to login to the Management Server. 20

21 Now let s deploy some servers to run a service on. Go back to the VDC Control Centre and navigate to the vapp which contains your Management Server. Once there, we are for this example going to deploy a Stingray Load Balancer. The Stingray Load Balancer is available in the Interoute CloudStore for use in VDC. Drag one onto the vapp, and click the save icon. 21

22 Configure the Stingray by clicking on its cog icon. Then select the network tab and add a new network interface on the DMZ network. 22

23 Change the default gateway and delete the network interface 0. Don t forget to click Save between each action. 23

24 Now we need to create a Private network for the web servers to live on. So, close the vapp, select the Network tab for the VDC and add a new Private Network. Then click Accept. 24

25 Return to the vapp, and add a new Network Interface to the load balancer. 25

26 Once the configuration is complete, drag two Ubuntu LAMP images onto the vapp and click save. 26

27 Configure the networking for each LAMP server via the cog icon. Then put them both on the Private network we created earlier. You will need to add the new interface and change the gateway before you can delete the default interface. 27

28 Now, to make life easy, let s add the management server to the backend network. First, select the machine and power if off. 28

29 Then click the cog icon for the machine and add the new network interface, but don t change the default gateway. 29

30 Power the management machine back on. 30

31 Now click Update Running Appliance to deploy the Stingray Load Balancers and the Ubuntu LAMP servers. 31

32 Login to the Management Server, and then load Internet Explorer and browse to the Load Balancer on the DMZ network, (in this example the IP address is ) 32

33 Now, login to the Load Balancer. 33

34 Here we will do a very basic setup on the Stingray. Click the top Services tab and then lower Traffic IP Groups tab. 34

35 Add a new Traffic IP Group and click Create Traffic IP Group. 35

36 Now click the Pools lower tab, and create a new Pool. A pool is group of servers which will take traffic for a particular service, fill in the details, and in nodes put the Backend IP addresses for the LAMP servers with :80 denoting the TCP port for HTTP. 36

37 Next, click the Virtual Servers lower tab, and create a new Virtual Server. 37

38 Now click the Home tab, and you will see that HTTP_DEMO Virtual Server is currently Stopped. Click the Play icon to start it up. 38

39 The Virtual Server has now started. 39

40 All we need to do now is forward traffic into the Virtual Server. So, navigate back to the Public IP Settings page on the hub. 40

41 Select the Port Mapping tab, and then select the second Public IP address and configure a port forward for port 80 to the load balancer. Then click Add Port Mapping. 41

42 Now select the Access Control tab. This time, because we want the whole world to access our new web service, move the second IP address into the Policy: Allow box. Then click the Save button to load the rules onto the firewall. 42

43 Now browsing to brings up the standard It Works! web page for Apache on the Ubuntu Server. 43

44 To find out more please visit CloudStore.Interoute.com or contact the CloudStore team Live Chat: Thank you! 44