Ubuntu 14.04.2 lts qcow2 how to#
Ubuntu 14.04.2 lts qcow2 install#

To verify use manila service-list ~]# manila service-list.

Start and enable manila ~]# systemctl start ~]# systemctl start ~]# systemctl enable ~]# systemctl enable ~]# systemctl start ~]# systemctl enable openstack-manila-share.

Ubuntu 14.04.2 lts qcow2 install#

In order to arrive at the right configuration parameters we had to refer to the Packstack based install with manila and modify it according to our multi-node setup. # yum install openstack-manila-share python-manilaДЇor reference of configuration files nf and api-paste.ini: Openstack-manila-share service will run on the compute node. Installed required packages on compute node.# yum install openstack-manila python-manila python-manilaclient Openstack-manila-api and openstack-manila-scheduler services will run on the controller node. Install required packages on controller node.Now follow below steps to install Manila: Manila Installation and configurationДЇirst upload the official manila service image to glance: ~]# wget ~]# glance image-create -name 'manila-service-image-new' -file manila-service-image.qcow2 -disk-format qcow2 -container-format bare -visibility public ~]# glance image-list You might want to restart openstack-cinder-volume service on the storage server after you do this change. Please create this directory beforehand and make sure cinder user and group are set on it. PS: One thing to note is that when manila creates a cinder volume and tries to attach it to the service VM it would fail if there is no /var/lock/cinder on the cinder-volume node (aka network node also in our case). If you are able to successfully attach the new volume (and its visible inside the instance as a raw block device) to the instance launched it means everything is working fine on cinder side, let's configure manila. To launch instance and attach volume to it follow Openstack Guide. | ID | Status | Name | Size | Volume Type | Bootable | Attached to | | cinder-volume | | nova | enabled | up | T13:31:33.000000 | None |Д¬reate a volume of 1 GB and attach it to nova instance to verify if cinder is working correctly: ~]# cinder create -name demo-volume1 ~]# cinder list | cinder-scheduler | controller | nova | enabled | up | T13:31:36.000000 | None | | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | We installed cinder-volume on network node as we have cinder-api and cinder-scheduler services running on controller node.

Refer Openstack kilo documentation for cinder installation. We installed cinder-volume on network node.

In the last blog post we did not configure cinder so here we will first configure cinder. The manila backend would be openstack cinder. Network (this will also run cinder-volume) 10.104.10.45 System details used in setup: controller (this will also run manila-api and manila-scheduler) 10.104.10.22Д¬ompute (this will also run manila-share) 10.104.1.210 We hope you enjoyed reading that blog post.

Ubuntu 14.04.2 lts qcow2 how to#

In previous blog post ( First Steps with Openstack Kilo) we described how to install openstack kilo on 3 CentOS 7.1 x86_64 sserver. This is a step by step guide to install and configure openstack manila service on multi-node openstack kilo setup. Menu Openstack Manila Multi-Node setup 11 July 2015