[Rdo-list] RDO
by Allen Efienokwu
*Hello all,*
*Below is the steps I use to install OpenStack on Ubuntu and it never
worked for me. It started well and in Step 1 but got stocked in Step2. I
also tried in Fedora and CentOS. Got stock in step 2. Please help me out.
Thanks*
Step 1: Software repositories
sudo yum update -y
sudo yum install -y https://rdo.fedorapeople.org/rdo-release.rpm
Step 2: Install Packstack Installer sudo yum install -y
openstack-packstack Step
3: Run Packstack to install OpenStack
Packstack takes the work out of manually setting up OpenStack. For a single
node OpenStack deployment, run the following command.
packstack --allinone
*OpenStack {Ubuntu 14.04 LTS} Installation Steps*
*OpenStack for ubuntu # sudo apt-get update # sudo apt-get install git #
git clone **https://www.github.com/openstack-dev/devstack.git*
<https://www.github.com/openstack-dev/devstack.git>
* -b stable/juno # ls # cd devstack # ls # sudo apt-get install vim #
apt-get installl libvirt-bin # sudo vim stackrc under "Base GIT Repo URL
add '**https://www.github.com* <https://www.github.com/>
* # under /devstack directory # ls # ./stack.sh*
*Allen EfienokwuAnd we know that all things work together as fitting into a
plan for us who love God and have been called according to his
purpose-Rm8:28*
9 years, 10 months
[Rdo-list] List of pending RDO updates as of Jan 20, 2015
by Alan Pevec
> * apevec will post update on what's in the queue until RDO CI goes public
CI is not public yet, here's an update as of Jan 20, 2015
( Reference for CI stages http://apevec.github.io/rdo-intro.html#8 )
* PHASE1 - updates passed smoke test
openstack-cinder-2014.2.1-2
python-taskflow-0.5.0-1
---
Missing requirements in openstack-cinder 2014.2.1 (RHBZ #1174760
#1175368 #1179060)
updates/p656.yml by Haikel Guemar <hguemar(a)fedoraproject.org>
openstack-glance-2014.1.3-3.fc21 @ koji -> icehouse / fedora-20
openstack-glance-2014.1.3-3.el6 @ copr-jruzicka -> icehouse / epel-6
openstack-glance-2014.1.3-3.el7 @ copr-jruzicka -> icehouse / epel-7
---
fix CVE-2014-9493 openstack-glance - unrestricted path traversal flaw (RHBZ
* STAGE
openstack-glance-2014.2.1-2
fix CVE-2014-9493 openstack-glance - unrestricted path traversal flaw (RHBZ
openstack-heat-gbp-2014.2-1
openstack-neutron-gbp-2014.2-1
python-django-horizon-gbp-2014.2-1
python-gbpclient-0.9.0-1
Neutron Group Based Policy 2014.2 from rkukura
python-glanceclient-0.15.0-1
Latest glanceclient for Juno
openstack-packstack-2014.2-0.14.dev1401.gdd19d48
Update packstack to fix rhbz#1172241
python-manilaclient-1.0.1-3
initial import in RDO Juno of python-manila
python-glance-store-0.1.10-2
New upstream version (fixes RHBZ #1169145 #1175419)
python-oslo-messaging-1.4.1-3
Fix reconnect exception handler (Dan Smith) rhbz#1175685
9 years, 10 months
[Rdo-list] Query regarding RDO Juno-1 install on CentOS7
by Deepak Shetty
Hi,
I was able to install 3-node RDO juno-1 (rdo-release-juno-1.noarch) over
CentOS7, but at the end of install it gave me this ...
Questions prefixed with Q: inline below:
Additional information:
* Time synchronization installation was skipped. Please note that
unsynchronized time on server instances might be problem for some OpenStack
components.
*Q: Do i need to sue ntpd to ensure all my systems are in sync, whats the
recommended way here ?*
* Warning: NetworkManager is active on <IP1>, <IP2> and <IP3>. OpenStack
networking currently does not work on systems that have the Network Manager
service enabled.
*Q: Do i need to disable NetworkManager.service on all or is it safe to
ignore this? What exactly doesn't work with NetworkManager ?For my system
it looks like below :[root@rhsdev1 packstack]# systemctl status
NetworkManager.service NetworkManager.service - Network Manager Loaded:
loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active:
active (running) since Wed 2014-12-24 23:45:56 IST; 4 days ago Main PID:
2002 (NetworkManager)[root@rhsdev1 packstack]# systemctl status
network.service network.service - LSB: Bring up/down networking Loaded:
loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code)
since Wed 2014-12-24 23:45:57 IST; 4 days ago*
thanx,
deepak
9 years, 10 months
[Rdo-list] RDO/OpenStack meetups coming up (January 19, 2015)
by Rich Bowen
The following are the meetups I'm aware of in the coming week where RDO
enthusiasts are likely to be present. If you know of others, please let
me know, and/or add them to http://openstack.redhat.com/Events
If there's a meetup in your area, please consider attending. It's the
best way to find out what interesting things are going on in the larger
community, and a great way to make contacts that will help you solve
your own problems in the future.
And don't forget to blog about it, tweet about it, G+ about it.
--Rich
* Monday, January 19 in San Francisco, CA, US: Come Join Us to Hear
About HyperFast OpenStack Storage with CloudFounders! -
http://www.meetup.com/openstack/events/219308937/
* Monday, January 19 in München, DE: OpenStack Meetup Nürnberg -
http://www.meetup.com/OpenStack-Munich/events/219374402/
* Monday, January 19 in Guadalajara, MX: Implementaciónes de OpenStack,
consideraciones basicas -
http://www.meetup.com/OpenStack-GDL/events/219763969/
* Tuesday, January 20 in Tel Aviv-Yafo, IL: OpenStack 3 Days Training -
http://www.meetup.com/IGTCloud/events/218924765/
* Tuesday, January 20 in Austin, TX, US: State of the Cloudy Union -
http://www.meetup.com/CloudAustin/events/218793700/
* Tuesday, January 20 in Chesterfield, MO, US: January Openstack meetup
- http://www.meetup.com/OpenStack-STL/events/219684702/
* Tuesday, January 20 in Paris, FR: Meetup #13 Ops : Comment gérer une
production OpenStack -
http://www.meetup.com/OpenStack-France/events/219689511/
* Wednesday, January 21 in Mountain View, CA, US: Online Meetup:
Introduction into Ceph storage for OpenStack -
http://www.meetup.com/Cloud-Online-Meetup/events/219855488/
* Wednesday, January 21 in Shanghai, CN: 1/21 Afternoon Meet w/ You @
Shanghai JiaoTong University -
http://www.meetup.com/Shanghai-OpenStack-Meetup/events/219803691/
* Wednesday, January 21 in Oslo, NO: January: The Future of Storage and
PaaS Case Study. - http://www.meetup.com/RedHatOslo/events/219061905/
* Wednesday, January 21 in Berlin, DE: 7th OpenStack User Group Berlin -
http://www.meetup.com/OpenStack-User-Group-Berlin/events/218681700/
* Wednesday, January 21 in Washington, DC, US: OpenStackDC Meetup #18 -
http://www.meetup.com/OpenStackDC/events/218827000/
* Wednesday, January 21 in San Francisco, CA, US: Breaking the Neutron
Barrier: Delivering Heterogenous Clouds -
http://www.meetup.com/openstack/events/219067928/
* Thursday, January 22 in Mountain View, CA, US: Online Meetup: An
Introduction to Platform-as-a-Service (PaaS) on OpenStack -
http://www.meetup.com/Cloud-Online-Meetup/events/219851567/
* Thursday, January 22 in Raleigh, NC, US: January Red Hat Convergence
Event - http://www.meetup.com/Raleigh-Red-Hat-User-Group/events/215314042/
* Thursday, January 22 in Helsinki, FI: Ceph & Gluster FS - Software
Defined Storage Meetup -
http://www.meetup.com/RedHatFinland/events/218774694/
* Thursday, January 22 in Henrico, VA, US: OpenStack Richmond Meetup #1
- http://www.meetup.com/OpenStack-Richmond/events/219346809/
* Thursday, January 22 in New York, NY, US: Using Ansible to Deploy
OpenStack - http://www.meetup.com/Ansible-NYC/events/219791589/
* Thursday, January 22 in San Francisco, CA, US: South Bay OpenStack
Meetup, Beginner track - http://www.meetup.com/openstack/events/219341335/
* Thursday, January 22 in San Francisco, CA, US: SFBay OpenStack
Hackathon #OSSFO - http://www.meetup.com/openstack/events/176812172/
* Thursday, January 22 in Pasadena, CA, US: A DevOps State of Mind.
OpenStack L.A. January '15 Meetup -
http://www.meetup.com/OpenStack-LA/events/219699801/
* Thursday, January 22 in Herriman, UT, US: Monthly Meetup -
http://www.meetup.com/openstack-utah/events/219336902/
* Thursday, January 22 in Whittier, CA, US: A DevOps State of Mind with
Red Hat OpenShift -
http://www.meetup.com/Greater-Los-Angeles-Area-Red-Hat-User-Group-RHUG/ev...
* Saturday, January 24 in Palo Alto, CA, US: How OpenStack does
Continuous Integration -
http://www.meetup.com/cloudcomputing/events/219651605/
* Saturday, January 24 in Beijing, CN: OpenStack计算与虚拟化 -
http://www.meetup.com/China-OpenStack-User-Group/events/219849812/
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
9 years, 10 months
[Rdo-list] RDO Bug triage day tomorrow [19JAN2015]
by Kashyap Chamarthy
Heya!
Tomorrow (3rd Tuesday of the month), 19JAN2015, is the monthly RDO bug
triage day. If you have some spare cycles, please join in helping triage
bugs/root-cause analysis in your area of expertise. Here's some details
to get started[1] with bug triaging.
Briefly, current state[2] of RDO bugs as of today:
- NEW, ASSIGNED, ON_DEV : 219
- MODIFIED, POST, ON_QA : 140
- VERIFIED : 14
A good number of bugs are installer components (openstack-packstack,
packstack-puppet-modules, openstack-foreman-installer), so it'd be nice
if we can get to close some of those.
[1] Bugzilla queries -- https://openstack.redhat.com/RDO-BugTriage#Bugzilla_queries
[2] All bugs and their descriptions in plain text --
https://kashyapc.fedorapeople.org/virt/openstack/rdo-bug-status/2015/all-...
--
/kashyap
9 years, 10 months
[Rdo-list] Glance filesystem_store_datadir
by Afshar, Brian
Can somebody provide an example of how we can specify multiple directories for Filesystem_store_datadir in glance-api.conf file?
The section for "Filesystem Store Options" indicates the following:
# Directory that the Filesystem backend store writes image data to filesystem_store_datadir=/var/lib/glance/images/
# A list of directories where image data can be stored.
# This option may be specified multiple times for specifying multiple store directories. Either one of filesystem_store_datadirs or # filesystem_store_datadir option is required. A priority number may be given after each directory entry, separated by a ":".
Is this a correct format?
/var/lib/glance/images/: /var/lib/glance/images1/. If this is incorrect please provide the correct format.
Regards,
-Brian
9 years, 10 months
[Rdo-list] "Manual" installation of Juno
by Nux!
Hi guys,
I'm looking to install Openstack Juno from the RDO RPMs, but without packstack/puppet/foreman.
Are there any "usable" docs for this?
Cheers,
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
9 years, 10 months
Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
by Walter Valenti
I've tried to compile it, the same version of
Centos7 package: 1.5.3
but there's a problem:
qumu 1.5.3 requires glib-2.12, but on Centos7
there's 2.36.3
Which version of qemu are you compiled?
Thanks
Walter
----- Messaggio originale -----
> Da: Pascal Bernier <Pascal.Bernier(a)ormuco.com>
> A: Walter Valenti <waltervalenti(a)yahoo.it>
> Cc:
> Inviato: Giovedì 15 Gennaio 2015 18:05
> Oggetto: RE: [Rdo-list] Problem with Cinder (Juno) and Ceph
>
> Hi Walter,
>
> I faced the same issue. The maintainers of the package for CentOS didn't
> compiled it with rbd support. I recompiled it with the rbd option and it was
> working propery. You also need to use the CentOSPlus repo for rbd kernel
> support.
>
>
> Pascal Bernier
>
> ________________________________________
>
> From: rdo-list-bounces(a)redhat.com [rdo-list-bounces(a)redhat.com] on behalf of
> Walter Valenti [waltervalenti(a)yahoo.it]
> Sent: Thursday, January 15, 2015 11:29 AM
> To: Yogev Rabl
> Cc: rdo-list(a)redhat.com
> Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
>
> I've followed directly the ceph documentation.
> Reading the RDO documentation, at point 4 of
> "Install Virtualization for Ceph Block Devices" tells:
> Older releases of RHEL and CentOS don't provide the rbd format required for
> use with Ceph.
> Now, I think: Centos7 isn't a older release.
> But the execution of "qemu-img -f", give me:
> vvfat vpc vmdk vhdx vdi sheepdog sheepdog sheepdog raw host_cdrom host_floppy
> host_device file qed qcow2 qcow parallels nbd nbd nbd iscsi gluster gluster
> gluster gluster dmg cow cloop bochs blkverify blkdebug
> There isn't "rdb".... Why ????
>
> Walter
>
>
>
>
>
>
>
> ----- Messaggio originale -----
>> Da: Yogev Rabl <yrabl(a)redhat.com>
>> A: Walter Valenti <waltervalenti(a)yahoo.it>
>> Cc: rdo-list(a)redhat.com
>> Inviato: Giovedì 15 Gennaio 2015 16:53
>> Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
>>
>> Did you go through 4th point in section, Install Virtualization for Ceph
> Block
>> Devices, in this manual:
>> https://openstack.redhat.com/Using_Ceph_for_block_storage_with_RDO ?
>>
>> Yogev
>>
>> ----- Original Message -----
>>> From: "Walter Valenti" <waltervalenti(a)yahoo.it>
>>> To: "Yogev Rabl" <yrabl(a)redhat.com>
>>> Cc: rdo-list(a)redhat.com
>>> Sent: Thursday, January 15, 2015 5:42:03 PM
>>> Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
>>>
>>>
>>>
>>> Yes, I've installed.
>>>
>>>
>>>
>>>
>>>
>>> ----- Messaggio originale -----
>>> > Da: Yogev Rabl <yrabl(a)redhat.com>
>>> > A: Walter Valenti <waltervalenti(a)yahoo.it>
>>> > Cc:
>>> > Inviato: Giovedì 15 Gennaio 2015 16:30
>>> > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
>>> >
>>> > did you install ceph-common & python-ceph?
>>> >
>>> >
>>> > ----- Original Message -----
>>> >> From: "Walter Valenti"
> <waltervalenti(a)yahoo.it>
>>> >> To: "Yogev Rabl" <yrabl(a)redhat.com>
>>> >> Sent: Thursday, January 15, 2015 5:08:51 PM
>>> >> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) and
> Ceph
>>> >>
>>> >> Yes, with enabled_backends = rbd,
>>> >> Cinder-Volume tries to use Ceph, but now I've
>>> >> got the following error:
>>> >>
>>> >> WARNING cinder.volume.manager [-] Unable to update volume
>> replication
>>> > status,
>>> >> RBDDriver -1.1.0 (config name rbd) driver is uninitialized.
>>> >>
>>> >>
>>> >>
>>> >> Walter
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ----- Messaggio originale -----
>>> >> > Da: Yogev Rabl <yrabl(a)redhat.com>
>>> >> > A: waltervalenti(a)yahoo.itYe
>>> >> > Cc:
>>> >> > Inviato: Giovedì 15 Gennaio 2015 14:18
>>> >> > Oggetto: Fwd: [Rdo-list] Problem with Cinder (Juno) and
> Ceph
>>> >> >
>>> >> > Hi Walter,
>>> >> >
>>> >> > You this configuration is incorrect from what I know.
>>> >> >
>>> >> > try this:
>>> >> >
>>> >> > [DEFAULT]
>>> >> >
>>> >> > enabled_backends = rbd
>>> >> >
>>> >> > [rbd]
>>> >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver
>>> >> > rbd_pool=volumes
>>> >> > rbd_ceph_conf=etc/ceph/ceph.conf
>>> >> > rbd_flatten_volume_from_snapshot=false
>>> >> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747
>>> >> > rbd_max_clone_depth=5
>>> >> > rbd_store_chunk_size=4
>>> >> > rados_connect_timeout=-1
>>> >> >
>>> >> >
>>> >> > In addition, I've just finish to write a small tool
> in
>> python that
>>> >> > configures Ceph in Openstack components configuration
> files
>> (and set
>>> > the
>>> >> > pools +
>>> >> > keyrings in the Ceph server).
>>> >> > You can have a look at it in github:
>>> >> > https://github.com/yorabl/Openstack-Ceph
>>> >> >
>>> >> > Good luck,
>>> >> > Yogev Rabl
>>> >> > Quality Engineer,
>>> >> > RHOS storage
>>> >> > Red Hat
>>> >> >
>>> >> >> ----- Forwarded Message -----
>>> >> >> From: "Walter Valenti"
>> <waltervalenti(a)yahoo.it>
>>> >> >> To: rdo-list(a)redhat.com
>>> >> >> Sent: Thursday, January 15, 2015 1:04:58 PM
>>> >> >> Subject: [Rdo-list] Problem with Cinder (Juno) and
> Ceph
>>> >> >>
>>> >> >> Hi,
>>> >> >> we're trying Juno with Ceph (Giant)
> integration on
>> Centos7.RBDDriver -1.1.0 (config name rbd) driver is uninitialized
>>
>>> >> >>
>>> >> >> The problem is that Cinder-Volume ignores, the
>> directives
>>> >> >> for use rbd protocol, but every uses LVM.
>>> >> >>
>>> >> >> This is our rbd configuration in cinder.conf:
>>> >> >>
>>> >> >> [DEFAULT]
>>> >> >>
>>> >> >> volume_driver=cinder.volume.drivers.rbd.RBDDriver
>>> >> >> [rbd]
>>> >> >> rbd_pool=volumes
>>> >> >> rbd_user=cinder
>>> >> >> rbd_ceph_conf=etc/ceph/ceph.conf
>>> >> >> rbd_flatten_volume_from_snapshot=false
>>> >> >>
> rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471
>>> >> >> rbd_max_clone_depth=5
>>> >> >> rbd_store_chunk_size=4
>>> >> >> rados_connect_timeout=-1
>>> >> >>
>>> >> >> We also tried with all configuration in
> "rdb"
>> section,
>>> > and
>>> >> >> with all configuration in DEFAULT section, but the
>> problem is the
>>> > same.
>>> >> >>
>>> >> >>
>>> >> >> Any ideas??
>>> >> >>
>>> >> >> Thanks
>>> >> >> Walter
>>> >> >>
>>> >> >> _______________________________________________
>>> >> >> Rdo-list mailing list
>>> >> >> Rdo-list(a)redhat.com
>>> >> >> https://www.redhat.com/mailman/listinfo/rdo-list
>>> >> >>
>>> >> >
>>> >>
>>> >
>>>
>>
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
9 years, 10 months
Re: [Rdo-list] [Manila] Unable to start Manila scheduler [ was: Don't see python-manilaclient package]
by Deepak Shetty
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> 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/...
>
9 years, 10 months
