Amazon EC2 classic EIP zone

1. Overview

Amazon EC2 is the well-known and maybe the most popular public cloud in the world; in EC2 classic, users can create a VM instance with a private IP address, and acquire an elastic IP(EIP) that is usually a public IP and can be dynamically bound to the VM. If there are more than one VMs, users can unbind and bind the EIP to VMs on demand.

In this example, we will create a deployment that has a public network a private network, and that allows users to bind an EIP created from the public network to VM nics that are on the private network.

2. Prerequisites

We assume you have followed installation guide to install ZStack on a single Linux machine, and the ZStack management node is up and running. To access the web UI, type below URL in your browser (Please use latest Chrome or Firefox browser.):

http://your_machine_ip:5000/

To make things simple, we assume you have only one Linux machine with one network card that can access the internet; besides, there are some other requirements:

  • At least 20G free disk that can be used as primary storage and backup storage
  • Several free IPs that can access the internet
  • NFS server is enabled on the machine (see end of this section for automatically setup NFS)
  • SSH credentials for user root

Configure root user

The KVM host will need root user credentials of SSH, to allow Ansible to install necessary packages and to give the KVM agent full control of the host. As this tutorial use a single machine for both ZStack management node and KVM host, you will need to configure credentials for the root user.
CentOS:
sudo su
passwd root

Based on those requirements, we assume below setup information:

  • ethernet device name: eth0
  • eth0 IP: 192.168.0.212
  • free IP range: 192.168.0.230 ~ 192.168.0.240
  • primary storage folder: /usr/local/zstack/nfs_root
  • backup storage folder: /backupStorage

Slow VM stopping due to lack of ACPID:

Though we don't show the example of stopping VM, you may find stopping a VM takes more than 60s. That's because the VM image doesn't support ACPID that receives KVM's shutdown event, ZStack has to wait for 60 seconds timeout then destroy it. It's not a problem for regular Linux distributions which have ACPID installed.

3. LogIn

open browser with URL(http://your_machine_ip:5000/) and login with admin/password:

4. Create Zone

click 'Hardware' in the left sidebar and then click 'Zone'to enter the zone page:

click button 'Create Zone' to open the dialog:

name your first zone as 'ZONE1' and click button 'OK':

5. Create Cluster

click 'Cluster' in the left sidebar to enter the cluster page:

click button 'Create Cluster' to open the dialog:

name the cluster as 'CLUSTER1' then click button 'OK':

6. Add Host

click 'Host' in the left sidebar to enter host page:

click 'Create Host' button to open the dialog:

  1. name the host as 'HOST1'
  2. select cluster(CLUSTER1) you just created
  3. input the host IP(172.20.11.45)
  4. input the ssh port(22)
  5. the most important thing: give SSH credentials for user root
  6. click 'OK' button

A little slow when first time adding a host

It may take a few minutes to add a host because Ansible will install all dependent packages, for example, KVM, on the host.

7. Add Primary Storage

click 'PrimaryStorage' in the left slider to enter primary storage page:

click button 'Adc PrimaryStorage' to open the dialog:

  1. name the primary storage as 'PS1'
  2. select type 'LocalStorge'
  3. input url(/zstack_ps)
  4. select cluster 'CLUSTER1'
  5. click button 'OK'

Format of URL

The format of URL is exactly the same to the one used by Linux mount command.

It's actually multiple API calls

You will see two API finishing notification because it actually calls two APIs: addPrimaryStorage and attachPrimaryStorageToCluster.

8. Add Backup Storage

click 'BackupStorage' in left sidebar to enter backup storage page:

click button 'Add BackupStorage' to open the dialog:

  1. name the backup storage as 'BS1'
  2. choose type 'Sftp'
  3. input IP(172.20.11.45) in host IP
  4. input URL '/zstack_bs' which is the folder that will store images

Input ssh port(22), input SSH credentials for user root, and click button 'OK':

9. Add Image

click 'Resource Pool' in left sidebar and click 'Image' to enter image page:

click button 'Add Image' to open the dialog:

  1. name the image as 'Image1'
  2. select media type 'Image'
  3. select platform 'Linux'
  4. input URL http://cdn.zstack.io/product_downloads/images/zstack-image.qcow2
  5. select BackupStorage 'BS1'
  6. click button 'OK'

this image will be used as user VM image.

10. Create L2 Network

click 'Network' in left sidebar and click 'L2Network' to enter L2 network page:

click button 'Create L2Network' to open the dialog:

  1. name the L2 network as 'L2Network-public'
  2. choose type 'L2NoVlanNetwork'
  3. input physical interface as 'eth0'
  4. select cluster 'CLUSTER1'
  5. click button 'OK'

click 'Create L2Network' again to create the private L2 network:

  1. name the L2 network as 'L2Network-private'
  2. choose type 'L2VlanNetwork'
  3. input vlan as '100'
  4. input physical interface as 'eth0'
  5. select cluster(CLUSTER1) to attach
  6. click button 'OK':

11. Create L3 Network

click 'L3Network' in left sidebar to enter L3 network page:

click 'Public Network' in sidebar to enter L3 public network page:

click button 'Create Public Network' to open the dialog:

Name the L3 network as 'L3Neywork-public' and select L2Network 'L2Network-private'

  1. choose method 'IP Range'
  2. input start IP as '10.121.9.20'
  3. input end IP as '10.121.9.200'
  4. input netmask as '255.0.0.0'
  5. input gateway as '10.0.0.1'

Input DNS as '8.8.8.8' and click button 'OK'

No network services needed for PUBLIC-MANAGEMENT-L3'

No user VMs will be created on the public L3 network in this tutorial, so we don't specify any network services for it.

12. Create Router Image

click 'Virtual Router' in left sidebar and click 'Virtual Router Image' to enter virtual router image page:

click button 'Add Virtual Router Image' to open the dialog:

  1. name the virtual router image as 'Virtualrouterimage1'
  2. input URL http://cdn.zstack.io/product_downloads/vrouter/zstack-vrouter-2.0.0.qcow2
  3. seclect BackupStorage 'BS1'
  4. click button 'OK'

Fast link for users of Mainland China

................................. 
http://cdn.zstack.io/product_downloads/vrouter/zstack-vrouter-2.0.0.qcow2

Cache images in your local HTTP server

The virtual router image is about 432M that takes a little of time to download. We suggest you use a local HTTP server to storage it and images created by yourself.

13. Create Virtual Router Offering

click 'Virtual Router Offering' in the left sidebar to enter virtual router offering page:

click 'Create Virtual Router Offering' to open the dialog:

  1. name the virtual router offering as 'VR-offering1'
  2. input CPU NUM as '2'
  3. input CPU speed as '2'
  4. choose image 'Virtualrouterimage1'

Choose management L3 network 'L3Network-public' , choose public L3 network 'L3Network-public' and click button 'OK'

14. Create Private Network

click 'Network' in the left sidebar, click 'L3Network' and click 'Private Network' to enter L3Network private network page:

click 'Create Private Network' button again to create the private L3 network:

  1. name the L3 network as 'L3Network-private'
  2. choose L2Network 'L2Network-private'
  3. choose type 'V Router'

  1. choose Virtual Router Offering 'VR-offering1'
  2. choose method 'CIDR'
  3. input network CIDR as '192.168.1.0/24'
  4. input DNS as '8.8.8.8'
  5. click button 'OK'

15. Create Instance Offering

click 'Resource Pool' in the left sidebar and click 'InstanceOffering' to enter instance offering page:

click button 'Create InstanceOffering' to open the dialog:

  1. input name as 'IO1'
  2. input CPU as '1'
  3. input Memory as '1'
  4. click button 'OK'

16. Create Virtual Machine

click 'Resource Pool' in the left sidebar and click 'VmInstance' to enter VM instance page:

click button 'Create VmInstance' to open the dialog:

  1. choose Type 'Single'
  2. input name as 'VM1'
  3. choose instance offering 'IO1'
  4. choose network 'L3Network-private'
  5. click button 'OK'

The first user VM takes more time to create

For the first user VM, ZStack needs to download the image from the backup storage to the primary storage and create a virtual router VM on the private L3 network, so it takes about 1 ~ 2 minutes to finish.

once the VM is created successfully, click button 'VM1' and then click button 'VMInstance Actions',finnally click item 'Console' to open VM's console:

in the popup window, login the VM by username: root and ping google.com, it should ping successfully:

and by the 'ifconfig' command, you should see the private IP address:

17. Create EIP

click 'Network' in the left sidebar, click 'Network Service' and then click 'EIP' to enter the EIP page:

click button 'Create EIP' to open the dialog:

  1. name EIP as 'EIP1'
  2. choose VIP method 'Create New VIP'
  3. choose Network 'L3Network-public'
  4. click button 'OK'

  1. choose VMInstance 'VM1'
  2. click button 'OK'

once it finishes, you should be able to see the result in EIP page; in our case, the EIP is '10.121.9.98':

use on machine that can reach subnet 192.168.1.0/24 to SSH the IP '10.121.9.98', you should be able to login the VM:

18. Rebind The EIP To Another VM

follow instructions in section 11. Create Virtual Machine to create another VM(VM2) on the private L3 network:

Subsequent VMs are created extremely fast

As the image has been downloaded to the image cache of the primary storage and the virtual router VM has been created, new VMs will be created extremely fast, usually less than 3 seconds.

go to EIP page, select the EIP1 and click button 'Action'; then in the dropdown box, click item 'Detach' and confirm:

after detaching, click button 'Action' again and select item 'Attach', in the dialog, choose VM2 this time and click button 'Attach':

SSH login to the EIP '10.121.9.98' again and run command 'hostname', you should see the hostname 'vm2', which proves the EIP has been successfully rebound to VM2.

Your feedback is invaluable, please let us know your thoughts.