{"id":9082,"date":"2016-10-12T19:20:17","date_gmt":"2016-10-12T17:20:17","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/how-to-install-mirantis-openstack-9-0-using-virtualbox-part-1-3\/"},"modified":"2016-10-12T19:20:17","modified_gmt":"2016-10-12T17:20:17","slug":"how-to-install-mirantis-openstack-9-0-using-virtualbox-part-1-3","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/how-to-install-mirantis-openstack-9-0-using-virtualbox-part-1-3\/","title":{"rendered":"How to install Mirantis OpenStack 9.0 using VirtualBox \u2013 part 3"},"content":{"rendered":"

In the two first blogs, I installed the Fuel environment and deployed OpenStack in the Fuel slave nodes and all of that from the Fuel Master node<\/em><\/strong>.<\/p>\n

In this blog, I will show you\u00a0 all the steps to follow in order to create an instance in OpenStack. All is going to be done via the Command Line Interface and not via Horizon – the OpenStack Dashboard (I will explain this in an other blog) .<\/p>\n

 <\/p>\n

Let’s begin!<\/p>\n

First of all let’s connect to the Fuel Master node and list all the nodes :<\/p>\n

[root@fuel ~]# fuel2 node list\n+----+------------+--------+-------------+-----------------+-----------+-------------------+---------+---------------+--------+\n| id | name | status | os_platform | roles | ip | mac | cluster | platform_name | online |\n+----+------------+--------+-------------+-----------------+-----------+-------------------+---------+---------------+--------+\n| 1 | Storage | ready | ubuntu | [u'cinder'] | 10.20.0.5 | 08:00:27:80:04:e8 | 1 | None | True |\n| 2 | Compute | ready | ubuntu | [u'compute'] | 10.20.0.4 | 08:00:27:cc:85:69 | 1 | None | True |\n| 3 | Controller | ready | ubuntu | [u'controller'] | 10.20.0.3 | 08:00:27:35:b0:77 | 1 | None | True |\n+----+------------+--------+-------------+-----------------+-----------+-------------------+---------+---------------+--------+<\/pre>\n
 <\/p>\n
Now, I connect to the controller node<\/em><\/strong><\/p>\n
[root@fuel ~]# ssh 10.20.0.3\nWarning: Permanently added '10.20.0.3' (ECDSA) to the list of known hosts.\nWelcome to Ubuntu 14.04.5 LTS (GNU\/Linux 3.13.0-98-generic x86_64)\n\n* Documentation:  https:\/\/help.ubuntu.com\/\nLast login: Tue Oct 11 09:55:54 2016 from 10.20.0.2\nroot@node-3:~#<\/pre>\n
 <\/p>\n
Let’s put an alias for each of the Fuel slave nodes\u00a0 :<\/p>\n
[root@fuel ~]# cat \/etc\/hosts\n127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1         localhost localhost.localdomain localhost6 localhost6.localdomain6\n10.20.0.2       fuel.domain.tld fuel\n10.20.0.3       fuel.domain.tld controller\n10.20.0.4       fuel.domain.tld compute\n10.20.0.5       fuel.domain.tld storage<\/pre>\n
 <\/p>\n
Now I can connect with the aliases:<\/p>\n
[root@fuel ~]# ssh controller\nThe authenticity of host 'controller (10.20.0.3)' can't be established.\nECDSA key fingerprint is 01:b5:15:22:03:d0:f9:bb:86:3a:06:a7:8c:19:bd:22.\nAre you sure you want to continue connecting (yes\/no)? yes\nWarning: Permanently added 'controller,10.20.0.3' (ECDSA) to the list of known hosts.\nWelcome to Ubuntu 14.04.5 LTS (GNU\/Linux 3.13.0-98-generic x86_64)\n\n* Documentation: https:\/\/help.ubuntu.com\/\nLast login: Tue Oct 11 10:12:34 2016 from 10.20.0.2\nroot@node-3:~# exit\nlogout<\/pre>\n
 <\/p>\n
Repeat this step for the two left nodes (compute & storage<\/strong><\/em>)<\/p>\n
I connect to the controller node<\/strong><\/em> :<\/p>\n
[root@fuel ~]# ssh controller\nWelcome to Ubuntu 14.04.5 LTS (GNU\/Linux 3.13.0-98-generic x86_64)\n\n* Documentation:  https:\/\/help.ubuntu.com\/\nLast login: Tue Oct 11 11:24:16 2016 from 10.20.0.2\nroot@node-3:~#<\/pre>\n
 <\/p>\n
I\u00a0 try to enter an OpenStack Command Line (list the instances for example) :<\/p>\n
root@node-3:~# nova list\n ERROR (CommandError): You must provide a username or user ID via --os-username, --os-user-id, env[OS_USERNAME] or env[OS_USER_ID]\n root@node-3:~#<\/pre>\n
It is normal because using OpenStack Clients Command Line\u00a0 requires before to get a token from Keystone<\/strong><\/em>.<\/p>\n
In order to do that, you have to specify where the controller node<\/strong><\/em> can reach Keystone and get the required informations from the\u00a0 OpenStack API’s. Because it is an authentification process you will also need to specify a username<\/strong><\/em> and a password<\/strong><\/em>.<\/p>\n
But doing this at each time you use the OpenStack Command Lines clients can\u00a0 quickly become inconvenient<\/em><\/strong>. Hopefully, in OpenStack, there is a way to avoid this. The solution is to create a file with all environments variables that need to be exported for getting this token from Keystone<\/strong><\/em>.<\/p>\n
Mirantis creates this file for us:<\/p>\n
root@node-3:~# ls\nopenrc<\/pre>\n
Let’s see what this file contains :<\/p>\n
root@node-3:~# cat openrc\n#!\/bin\/sh\nexport OS_NO_CACHE='true'\nexport OS_TENANT_NAME='admin'\nexport OS_PROJECT_NAME='admin'\nexport OS_USERNAME='admin'\nexport OS_PASSWORD='admin'\nexport OS_AUTH_URL='http:\/\/192.168.0.2:5000\/'\nexport OS_DEFAULT_DOMAIN='Default'\nexport OS_AUTH_STRATEGY='keystone'\nexport OS_REGION_NAME='RegionOne'\nexport CINDER_ENDPOINT_TYPE='internalURL'\nexport GLANCE_ENDPOINT_TYPE='internalURL'\nexport KEYSTONE_ENDPOINT_TYPE='internalURL'\nexport NOVA_ENDPOINT_TYPE='internalURL'\nexport NEUTRON_ENDPOINT_TYPE='internalURL'\nexport OS_ENDPOINT_TYPE='internalURL'\nexport MURANO_REPO_URL='http:\/\/storage.apps.openstack.org\/'\nexport MURANO_PACKAGES_SERVICE='glance'<\/pre>\n
 <\/p>\n
I source the file to export the environment variables :<\/p>\n
root@node-3:~# source openrc<\/pre>\n
 <\/p>\n
I check if the variables were exported. It is via the OS_AUTH_URL that the controller node can reach Keystone<\/em><\/strong><\/p>\n
root@node-3:~# echo $OS_USERNAME\nadmin\nroot@node-3:~# echo $OS_PASSWORD\nadmin\nroot@node-3:~# echo $OS_AUTH_URL\nhttp:\/\/192.168.0.2:5000\/<\/pre>\n
 <\/p>\n
Now I can list if there are some instances running :<\/p>\n
root@node-3:~# nova list\n+----+------+--------+------------+-------------+----------+\n| ID | Name | Status | Task State | Power State | Networks |\n+----+------+--------+------------+-------------+----------+\n+----+------+--------+------------+-------------+----------+<\/pre>\n
 <\/p>\n
 <\/p>\n
Let’s create the first instance<\/h4>\n
In order to create this instance, I need :<\/p>\n