Openstack Installation Guide

Transcription

1 Openstack Installation Guide Installation Steps Step1: Making the Host Machine ready f Installation Step2: Configuring the Host Machine Interfaces Step3: Checkout the Installation Scripts Step4: Installing the Controller Step5: Uploading an Image Step6: Testing the Controller Step7: Installing a Compute Node Nova Environment Cleaning and Restarting all over Add Nova Volume Stage User Data Injection Accessing Metadata Infmation from within instances Adding Floating ip to instances Moniting Openstack Troubleshooting Cannot ping to the instance created Cannot ssh to the instance When installing nova essex into a new box dpkg err occur and then mysql configuration take long time and fail Your applications deployed in instances cannot be accessed Cannot shutdown the instance Err returned when creating the very first instance Timeout: Timeout while waiting on RPC response Successfully added compute node but cannot create instances in that node Disaster Recovery References

2 In this guide I explain how to install Openstack in two machines. In one machine I install the nova controller and a compute node. In the other machine I install a compute node. So the setup has one controller and two compute nodes. The steps below can be followed using two physical machines two Oracle Virtualbox virtual machines. The installation is done on physical machines with interface cards each. In virtualbox with three netwk cards each. - virtualbox Ubuntu LTS 64 bit - Nova Essex as of September 2012 First I will explain the common configuration setup needed f both machines. F each virtual instance do the following: Get two 64bit physical machines with two interface cards each. In virtualbox create an instance f linux, 64bit. Add two host only interface adapts Then install Ubuntu LTS 64bit version. Please refer to a good virtualbox guide available in the internet. Installation Steps Step1: Making the Host Machine ready f Installation %apt-get update %apt-get install openssh-server(to ssh into instance) Step2: Configuring the Host Machine Interfaces edit /etc/netwk/interfaces In physical Machines auto eth0 iface eth0 inet static address netmask gateway auto eth1

3 iface eth1 inet manual up ifconfig eth1 up %ifup eth0 %ifup eth1 Note that it is not necessary to have two interfaces f compute node hosts. Only one is enough. However if you need to access that machine using a public interface, then you need another one. In Virtualbox auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address netmask netwk broadcast auto eth2 iface eth2 inet manual up ifconfig eth2 up %ifup eth1 %ifup eth2 If eth1 has already got an ip then give the same netwk info as above with inet static Note: Above configuration f the second VM should have instead of Then %ifconfig eth1 down %ifconfig eth1 up %reboot Note also that in Virtualbox do the following setup f the first interface(eth1) Click file->preferences and then Netwk button. Edit the interface as following

4 IPV4 address: IPV4 netwk mask : Step3: Checkout the Installation Scripts %apt-get -y install git %git clone %cd OpenStackInstaller/ %git checkout essex %svn co Now we will first install the nova controller in one of the machines Step4: Installing the Controller %sudo -i %cd OpenStackInstaller Modify oscontrollerinstall.sh as per your requirements and execute. F example. Also modify the OSinstall.sh to add following configuration that would go into nova.conf --rpc_response_timeout=<new timeout in seconds> Give a sufficient response timeout to avoid timeout errs. %./OSinstall.sh -T all -F /24 -f /16 -s 512 -P eth1 -p eth2 -t demo -v lxc Note that I use -T all options since I install in this server both controller and a compute node. With -F parameter we give the floating ip range f the project. With -f parameter we give the fixed ip range f the project. We use eth2 as private interface. eth1 as public interface. F the public ips(floating ips) we should give an valid range from the netwk where the host machine took IP. In this example virtual box has ip f eth1 which can be accessed from the host machine(where host machine hosted) So a valid floating ip subnet would be /24. You can calculate such an range from the subnet calculat in link [1]

5 A valid fixed ip subnet would be /16. Note that OSinstall.sh script associate an floaing ip f each instance it create. So if the floating ip s are exhausted, then there will be errs and instance would not be created. To avoid this situation, make sure that you allocate as many as floating ips, at least, as the fixed ips. Step5: Uploading an Image From this step on you can execute the commands as nmal user. You need to upload an ubuntu image to glance. F lxc containers download the image preciseserver-cloudimg-amd64.tar.gz from F kvm virtual machines download the image precise-server-cloudimg-amd64-disk1.img and create /root/upload folder and copy the image into it. Modify uploadimage.sh and execute Eg: %imageupload.sh -a admin -p openstack -t demo -C x amd64 -y ubuntu -w z ubuntu server-cloudimg-amd64.tar.gz -n ubuntu server-cloudimg-amd64 to upload the image. Here is the ip of the openstack nova controller. In this case it is the ip of the eth1 inteface. Or you can put an entry in the /etc/hosts file and put that name instead of the ip. F example you can put s2demo.wso2.com In /etc/hosts file and use that in the above command instead of Execute %nova image-list command to see whether your newly uploaded image appear in the image list. Step6: Testing the Controller %cd OpenStackInstaller %source./demc Now add a keypair. It is highly recommended that you use your own keypairs when creating instances. F example suppose you create an instance as nmal user, using a keypair owned by root user. You may succeed in creating your instance. But you will get permission denied

6 exception when trying to ssh to that instance. %euca-add-keypair demo > demo.pem %nova keypair-add demo > demo.pem Set permission f the private key %chmod 0600 demo.pem You can see the created key listed %nova keypair-list Allow needed pts f the default security group. %nova secgroup-add-rule default icmp /0 %nova secgroup-add-rule default tcp /0 %nova secgroup-add-rule default tcp /0 %nova secgroup-add-rule default tcp /0 %nova secgroup-add-rule default tcp /0 %nova secgroup-add-rule default tcp /0 %euca-authize default -P tcp -p 22 -s /0 %euca-authize default -P tcp -p 80 -s /0 %euca-authize default -P tcp -p 443 -s /0 %euca-authize default -P tcp -p s /0 %euca-authize default -P tcp -p s /0 %euca-authize default -P icmp -t -1:-1 Now list the images %euca-describe-images %nova image-list look f the image id. %euca-run-instances -k demo -n 1 -g default -t m1.tiny ami f /root/client/payload.zip %nova boot --key_name=nova-key --flav=1 --image=<image id> --user_data=/root/client/payload.zip <instance name> Now see whether your instance is up and running. Look f the running instances ip.

7 %euca-describe-instances %nova list Now copy the demo.pem file from the vbox instance into the vbox host machine(your laptop?) %ssh -i demo.pem If you can access the virtual machine instance then you have successfully created a controller with a compute node in it. Next we add a one me compute node into the picture. Befe that log into the nova mysql database running in the controller machine and verify that there is a compute node entry in the compute_nodes table. %mysql -uroot -popenstack mysql>use nova mysql>select id, created_at from compute_nodes; Your should see one compute node entry in the table. Step7: Installing a Compute Node Make sure that you give a host name f the compute node server instead of the default hostname %vi /etc/hostname and change the host entry f example to mycompute-node. Then reboot the machine. Now log into controller node and add an host entry in /etc/hosts file mycompute-node Now log into the compute node and %sudo -i %cd OpenStackInstaller %./OSinstall.sh -T compute -C f /16 -s 512 -P eth1 -p eth2 -t demo -v lxc After the installation comment the following lines in /etc/nova/nova.conf, if you don t want vnc access to your nodes in compute nodes.

8 #--novncproxy_base_url= #--vncserver_proxyclient_address= #--vncserver_listen= If you need vnc access then change vncserver_proxyclient_address and vncserver_listen to local address on each compute nodes accdingly. Once this is installed, log into the mysql database in the controller again and verify that there are two entries in the compute_nodes table which means your new compute node is now active in the setup. When I try to add an already setup nova compute node to the controller, by adding the compute node entry in the controllers /etc/hosts file and then restarting the nova services in the compute node, in the mysql database s compute_nodes table I could see an new entry f the new compute node. I could even create instances in that node. However I could not ping to those instances from controller node n compute node. So I completely removed the compute node. Following are the steps how I removed the compute node. 1. Stop the nova services of the compute node 2. Remove the /etc/hosts entry f the controller node 3. Remove the database entry delete from compute_nodes where id=<id of the compute node> 4. Restart the nova services of the controller node Then I did a clean install of openstack compute node(including os reinstall). Then it wked. Now from your controller node s /root/openstackinstaller folder you can start playing with creating/deleting your new instances. first list your uploaded image by %euca-describe-images Then using the image id there, create an new instance %euca-run-instances -k demo -n 1 -g default -t m1.tiny ami You can list your created instances by %nova list %euca-describe-instances You can monit the /var/log/nova/nova-compute.log in both servers(controller node and compute node) to see the status of creating the nodes.

9 Now you can start creating me instances and verify that in both compute nodes, instances are created, until you see a sht, undescriptive message that basically say your quota has exceeded. This blog[4] is the basis f this documentation.this screencast[2] is the basis f this documentation. [3] also provide a me err free version. Nova Environment In the following sections, some additional infmation on Openstack Nova environment is explained. Cleaning and Restarting all over If you mess up with your installation and need to start it all over again follow these steps. Note: do the changes in the script accding to your environment. Refer to the settings in your oscontrollerinstall.sh oscomputeinstall.sh. cd /root/openstackinstaller Comment out the following two lines #apt-get remove nova-compute nova-netwk nova-api nova-objectste keystone glance nova-scheduler #apt-get autemove %OSuninstall.sh %osreinstall.sh You may need to restart the instance if problems occur during script running. Now upload the image. %uploadimage.sh Sometime deleting the instances is enough to get rid of the mess. In such cases delete using the following script(you may need to change the mysql credentials in the script). %dbclean.sh If still does not wk do install os again and do a clean install of nova essex. Creating a image from a running instance

10 Execute the following command to create an image from an running instance. nova image-create <instance id> <mysql image name> This command will create the image and upload it to the glance server. You can check whether it is uploaded by calling nova image-list command. Add Nova Volume Stage To create instances with persistent stage we need to add nova volume stage. Shutdown the virtualbox instance(controller) and add sata stage. If you add IDE stage there will be boot problems. Now log into controller and execute %fdisk -l This will show undefined partition most probably /dev/sdb %fdisk /dev/sdb Command (m f help): n Partition type: p primary (0 primary, 0 extended, 4 free) e extended Select (default p): p Partition number (1-4, default 1): 1 First sect ( , default 2048): Using default value 2048 Last sect, +sects +size{k,m,g} ( , default ): Using default value Command (m f help): w The partition table has been altered! %apt-get install lvm2 %fdisk -l Now you can create /dev/sdb1 %pvcreate -ff /dev/sdb1 %vgcreate nova-volumes /dev/sdb1 %apt-get install nova-volume Now you can boot up instances with persistent stage attach persistent stage to already running instances.

11 To add an instance type %nova-manage flav create --name=m1.wso2 --memy=128 --cpu=1 --root_gb=2 --ephemeral_gb=0 --flav=6 -- swap=0 --rxtx_fact=1 To create an instance using that instance type %euca-run-instances ami k demo -t m1.wso2 ami can be seen from executing %euca-describe-instances %nova list User Data Injection From openstack nova essex that ship with Ubuntu LTS the instances created from cloud images are ready to get infmation such as user-data, public ip, keys etc from the metadata service. user data data can be passed to the instance at startup like %euca-run-instances ami k demo -t m1.tiny -g default -f /root/client/payload.zip %nova boot --key_name=nova-key --flav=1 --image=<image id> --user_data=/root/client/payload.zip <instance name> At instance startup, nova copy the zip file into the instance as /var/lib/cloud/instance/userdata.txt. Accessing Metadata Infmation from within instances We can get the public ip from the metadata server %wget Now public-iv4 file contain the public ip Adding Floating ip to instances We can add floating ip s to the instances automatically when spawned later

12 F automatically assiginint ip when instance spawn, add the following line into /etc/nova.conf and restart nova services --auto_assign_floating_ip To add a floating ip first allocate one using the following command % nova floating-ip-create % nova add-floating-ip <instance id> <floating ip> % nova remove-floating-ip <instance id> <floating ip> % nova floating-ip-delete <floating ip> To list the floating ips % nova floating-ip-list Moniting Openstack To see how much memy an lxc container is using cat /sys/fs/cgroup/memy/libvirt/lxc/instance d/memy.stat at look at rss entries /sys/fs/cgroup/memy/libvirt/lxc/instance d/memy.usage_in_bytes In /sys/fs/cgroup/memy/libvirt/lxc/instance d/ folder you can see several other memy related files Some of the other folders that contain files regarding resources are./blkio/libvirt/lxc/instance d./freezer/libvirt/lxc/instance d./devices/libvirt/lxc/instance d./memy/libvirt/lxc/instance d./cpuacct/libvirt/lxc/instance d./cpu/libvirt/lxc/instance d./cpuset/libvirt/lxc/instance d

13 Troubleshooting Cannot ping to the instance created Make sure you have enabled icmp Using the nova command-line tool: $ nova secgroup-add-rule default icmp s /0 Cannot ssh to the instance Make sure you have enabled tcp pt Using the nova command-line tool: $ nova secgroup-add-rule default tcp s /0 If you still cannot ping SSH your instances after issuing the nova secgroup-add-rule commands, look at the number of dnsmasq processes that are running. If you have a running instance, check to see that TWO dnsmasq processes are running. If not, perfm the following as root: % killall dnsmasq % service nova-netwk restart When installing nova essex into a new box dpkg err occur and then mysql configuration take long time and fail This happen when you fget to do an apt-get update befe starting to install nova essex. This could not be crected until doing a fresh installation again. Your applications deployed in instances cannot be accessed Make sure you have enabled your application pt Using the nova command-line tool: $ nova secgroup-add-rule default tcp s /0 Note that you need to replace 8080 above with the pt your application is running.

14 Cannot shutdown the instance Sometimes even after terminate command is executed on an instance it is not terminated but go to shutoff state. At such moments try restarting nova services. Err returned when creating the very first instance Make sure that you public and private interfaces up Eg: sudo ifconfig eth1 up Timeout: Timeout while waiting on RPC response Sometimes when creating instances you get the response timeout err. The default request timeout f nova is 60seconds. To increase this add following entry to /etc/nova.conf and restart nova services --rpc_response_timeout=<new timeout in seconds> Successfully added compute node but cannot create instances in that node When instances are created in that node the instance state is in ERROR. In the compute node log we have libvirterr: Unable to read from monit: Connection reset by peer To avoid this make sure that you have commented out the following three entries in the compute nodes /etc/nova.conf #--novncproxy_base_url= #--vncserver_proxyclient_address= #--vncserver_listen= If not comment them out and restart nova services in the compute node. Disaster Recovery Nova instances can be rebooted using % nova reboot <instance id> % euca-reboot-instances <instance id> Note that nova-reboot-instance <instance name/id> command has a bug and does not wk f lxc instances. We also noticed that logging to the lxc instance and rebooting does not wk as well. In this case we can ping to the instance but connection is refused when ssh to it.

15 When a host machine is restarted, all vm s go into shutoff state. You can reboot the instances to get them started again. References [1] [2] [3] [4]