Thanks Alan, I was able to pick & install the manilaclient packages from the copr link. Going ahead, i was able to start the manila-api service but manila-scheduler and manila-share service errored out *First things first, looks like m-sch errored due as the manila DB is not present.* *Who/Which package is responsible for creating the manila db and its associated tables in the mysql ?* Pls see the debug info below taken from my setup: [root@rhsdev1 packstack(keystone_admin)]# systemctl start openstack-manila-scheduler.service [root@rhsdev1 packstack(keystone_admin)]# systemctl status openstack-manila-scheduler.service openstack-manila-scheduler.service - OpenStack Manila Scheduler Loaded: loaded (/usr/lib/systemd/system/openstack-manila-scheduler.service; enabled) Active: failed (Result: exit-code) since Fri 2015-01-16 11:39:15 IST; 20s ago Process: 8302 ExecStart=/usr/bin/manila-scheduler --config-file /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf --logfile /var/log/manila/scheduler.log (code=exited, status=1/FAILURE) Main PID: 8302 (code=exited, status=1/FAILURE) CGroup: /system.slice/openstack-manila-scheduler.service Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 199, in raise_from_cause Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila reraise(type(exception), exception, tb=exc_tb) Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 951, in _execute_context Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila context) Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 436, in do_execute Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila cursor.execute(statement, parameters) Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila OperationalError: (OperationalError) no such table: services u'SELECT services.created_at AS services_creat...d, services.id Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com systemd[1]: openstack-manila-scheduler.service: main process exited, code=exited, status=1/FAILURE Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit openstack-manila-scheduler.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | cinder | | glance | | keystone | | mysql | | neutron | | nova | | performance_schema | | test | +--------------------+ 9 rows in set (0.00 sec) MariaDB [(none)]> ================================================== On a related note: there were some warnings & errors from the -api and -share service respectively (i guess these can be handled once the DB issue is resolved?) [root@rhsdev1 packstack(keystone_admin)]# systemctl status openstack-manila-api.service openstack-manila-api.service - OpenStack Manila API Server Loaded: loaded (/usr/lib/systemd/system/openstack-manila-api.service; disabled) Active: active (running) since Fri 2015-01-16 11:36:54 IST; 32s ago Main PID: 8075 (manila-api) CGroup: /system.slice/openstack-manila-api.service └─8075 /usr/bin/python2 /usr/bin/manila-api --config-file /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf --logfile /var/log/manila/api.log Jan 16 11:36:54 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Started OpenStack Manila API Server. Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token [-] This middleware module is deprecated as of v0.10.0 in favor of keystonemiddl...leware package. Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead. Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token [-] Configuring auth_uri to point to the public identity endpoint is required; c... admin endpoint Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.325 8075 WARNING keystoneclient.middleware.auth_token [-] signing_dir mode is 0755 instead of 0700 Hint: Some lines were ellipsized, use -l to show in full. [root@rhsdev1 packstack(keystone_admin)]# systemctl status openstack-manila-share.service openstack-manila-share.service - OpenStack Manila Share Service Loaded: loaded (/usr/lib/systemd/system/openstack-manila-share.service; enabled) Active: failed (Result: exit-code) since Fri 2015-01-16 11:39:20 IST; 50s ago Process: 8317 ExecStart=/usr/bin/manila-share --config-file /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf --logfile /var/log/manila/share.log (code=exited, status=1/FAILURE) Main PID: 8317 (code=exited, status=1/FAILURE) Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila File "/usr/lib/python2.7/site-packages/manila/openstack/common/importutils.py", line 38, in import_object Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila return import_class(import_str)(*args, **kwargs) Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila File "/usr/lib/python2.7/site-packages/manila/share/drivers/generic.py", line 116, in *init* Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila self.db, driver_config=self.configuration)) Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila File "/usr/lib/python2.7/site-packages/manila/share/drivers/service_instance.py", line 133, in *init* Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila raise exception.ServiceInstanceException(_('Service instance user ' Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila ServiceInstanceException: Service instance user is not specified Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com systemd[1]: openstack-manila-share.service: main process exited, code=exited, status=1/FAILURE Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit openstack-manila-share.service entered failed state. thanx, deepak On Tue, Jan 13, 2015 at 5:07 PM, Alan Pevec <apevec(a)gmail.com&gt; wrote: > > I am new to RDO, any idea when would that next refresh be ? > > There aren't scheduled refreshes, we push updates when they pass > rdopkg CI update process [1]. > This is currently running on internal RHT systems and we're working on > opening it up for external contributors, tasks are tracked on a public > board [2] > Haikel's manilaclient has passed Phase1 and Phase2 will run today on > queued updates. > I'll update this thread when updates hit the public repo. In the > meantime, you can grab the el7 package from Copr [3] > > > Cheers, > Alan > > > [1] http://apevec.github.io/rdo-intro.html#8 > [2] https://trello.com/b/HhXlqdiu/rdo > [3] > https://copr-be.cloud.fedoraproject.org/results/jruzicka/rdo-juno-epel-7/... >