Re: [Rdo-list] Fwd: [OpenStack-docs] [install-guide] (not that much) progress with Kilo install on RHEL/Centos 7

Many thanks for addressing this, Lars (and Steve for raising this to the RDO list). A few comments: - it would seem that I have the wrong environment; my rdo-release.repo doesn't contain anything about Kilo. This should explain the packaging problems I experienced. - the yum part of the draft install guide has not yet been written and is pure Juno right now. It's to write that part that I am trying to install Kilo. - I will work with my OpenStack docs team mates on the glance problems - perhaps they will go away when my repo configuration is fixed. When I hit problems after using the right repositories, I will raise my flag again, or just file bugs. Cheers, Bernd -----Original Message----- From: Lars Kellogg-Stedman [mailto:lars@redhat.com] Sent: Tuesday, April 14, 2015 3:54 AM To: Steve Gordon Cc: rdo-list; berndbausch(a)gmail.com Subject: Re: [Rdo-list] Fwd: [OpenStack-docs] [install-guide] (not that much) progress with Kilo install on RHEL/Centos 7 openstack-selinux is generally available for RHEL and CentOS, but not for Fedora. On Fedora in particular, selinux related issues are supposed to be reported directly against selinux-policy. When using RDO Kilo with CentOS 7, the openstack-selinux package comes from the rdo-juno repository. Note that installing https://repos.fedorapeople.org/repos/openstack/openstack-kilo/rdo-release-ki lo-0.noarch.rpm configures two repositories on your system: [openstack-juno] name=OpenStack Juno Repository baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/ enabled=1 skip_if_unavailable=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RDO-Juno [openstack-kilo] name=Temporary OpenStack Kilo new deps baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-kilo/epel-7/ skip_if_unavailable=0 gpgcheck=0 enabled=1 I notice that the draft Kilo install guide still points at the Juno packages: [from http://docs-draft.openstack.org/92/167692/13/gate/gate-openstack-manuals-tox -doc-publish-checkbuild/31c1ab2//publish-docs/trunk/install-guide/install/yu m/content/ch_basic_environment.html#basics-prerequisites] As of last week, there were still selinux bugs open against RDO Juno. I'm not sure what the state of the Kilo packages are at this opint, but it seems likely that there may be issues there as well. If you're seeing this on a RHEL or Fedora system, you should open a bug in bugzilla so we can track this issue and maybe come up with an appropriate solution. /etc/rabbitmq/rabbitmq.config. There's a bug open on that for RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1134956 We should probably clone that to RDO as well. You shouldn't require COPR repositories for anything. If you encounter a repeatable packaging error, make sure to open a bugzilla so that folks are aware of the issue. On CentOS 7 right now, I am able to install both python-keystoneclient and openstack-keystone without any errors, using only the base, RDO, and EPEL repositories. help. I suspect the answer to all of the above is, "because legacy". v3 support has only recently been showing up in all of the services, and many folks still aren't familiar with the newer APIs. The admin/non-admin port separation is another historical oddity that we have to live with. With Keystone v2, at least, there are some features only available through the admin api on the admin port. There is a known problem that has been corrected in the latest Kilo packages. There was no corresponding bz filed (via apevec, irc). Debugging this will probably require someone looking over your shoulder at your glance configuration. -- Lars Kellogg-Stedman <lars(a)redhat.com&gt; | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/