[Rdo-list] Fwd: RDO installation
by Dave Neary
Hi Ahmed,
I can't really answer questions through personal email - not only
because it doesn't scale, but because your email is going to get lost,
and also because (as in this case) I often don't know the answer.
Theer are many experts on rdo-list (CCed) and on the forum. I suggest
you ask your question there.
Thanks,
Dave.
-------- Original Message --------
Subject: RDO installation
Date: Thu, 20 Jun 2013 16:31:31 +0200
From: ahmed ali <ahmedali27491(a)gmail.com>
To: nearyd(a)gmail.com
Hi dneary ,
I want your help , while installing RDO openstack this error appear can
you help me please .Inline image 1
11 years, 5 months
[Rdo-list] Notes for setting up NFS share to store nova instances
by Kashyap Chamarthy
Heya,
I just saw a question on RDO forum related to $subject. Just posting some notes here, as
this was in my drafts anyhow. (Will point a link to this on the Forum. Also, thanks to
Giulio Fidente for reminding me on the qemu.conf bit below).
NFS share to store nova instances
---------------------------------
If you have an NFS share to store images, you could add it the below
way. The default location where instances are stored --
`/var/lib/nova/instances`
First, on the NFS server side :
$ cat /etc/exports
/home/kashyap *(rw,syn,no_root_squash)
Mount an nfs share w/ nova specific SELinux context :
$ mount --verbose -t nfs xx.yy.www.zzz:/home/kashyap \
/mnt -o "context=unconfined_u:object_r:nova_var_lib_t:s0"
# Set correct permissions on mount point
$ chown -R nova: /mnt/nova/
$ chgrp -R qemu /mnt/nova/instances/
$ chmod -R g+w /mnt/nova/instances
Ensure to have nova own the QEMU instances invoked by :
$ grep nova /etc/libvirt/qemu.conf
user = "nova"
group = "nova"
Restart all 'running' OpenStack services :
$ for j in `for i in $(ls -1 /etc/init.d/openstack-*) ; \
do $i status | grep running ; done | awk '{print $1}'`; \
do service $j restart ; done
Later, ensure, your instances are indeed owned by nova ::
$ ps -ef | grep -i qemu-kvm | grep -i nova
--
/kashyap
11 years, 5 months
[Rdo-list] Why use yum priority in rdo-release repo file?
by Sandro "red" Mathys
Even though RDO is supposed to always being ahead of RHEL and EPEL, it
enforces a higher priority (lower priority=N) than the default. Why?
Enforcing priorities should really only ever happen if absolutely necessary
and will often cause pain to users.
For example I'm trying to manage my RDO installation with Puppet but EPEL
and RDO only have Puppet 2.6 which is EOL and it has been decided that
puppet-openstack will no longer support it effective immediately. But to
install puppet 3.2 from puppetlabs' repo, I first have to scrap the
priority from RDO's repo file manually.
As a (former) developer for Packstack I understand it requires a specific
Puppet version but I think we all agree most (non proof of concept)
installations are not using Packstack to set up or maintain their OpenStack
cloud.
-- Sandro
11 years, 5 months