newton openstack-keystone service not created on Centos7

[Scott W]

I am attempting to install the newton version of keystone on Centos 7. After the install, the openstack-keystone.service is not found:
$ sudo systemctl status openstack-keystone
â— openstack-keystone.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Here are the particulars of my install:
CentOS Linux release 7.2.1511 (Core)
3.10.0-327.36.2.el7.x86_64 #1 SMP

I enabled the cloud repo at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-newton/ by installing centos-release-openstack-newton-1-1.el7.noarch.rpm. I then ran sudo yum install openstack-keystone httpd mod_wsgi to install.

rpm -q openstack-keystone shows "openstack-keystone-10.0.0-1.el7.noarch"

The /etc/keystone/ dir was created and populated.

sudo find /etc -name openstack-keystone* does not return anything
sudo find /etc -name *.service does not return openstack-keystone.service in the list

/var/log/keystone/keystone.conf is empty.
---------edit--------------
I should also add I am attempting to install keystone on a 3-node Pacemaker/Corosync/HAPproxy cluster that will be a HA controller implementation. The cluster was previously configured as the LB front-end for a 3-node Galera cluster.

[Adam Young (ayoung)]

THe Keystone RPM does not populate the Service entry. This is documented. It is up to the installer to perform all Service entries; both Packstack and Tripleo do this. Older documentation had this explicitly stated, but may have bit rotted:

 https://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_18#Configure_Keystone

[Scott W (cswcloud)]

Adam,

The link you provided gives no guidance on how to set up the openstack-keystone.service entry.

Can you explain the difference between the RPM and the "installer" in your statement?

I have been thru the majority of OpenStack configuration on Ubuntu 16.04 with Mitaka. I used the OpenStack configuration documentation, did all the work myself, and did not use any accelerator package like PackStack or TripleO. When I installed openstack-keystone, I did not have to do anything to manually create the openstack-keystone.service entry. I simply had to enable and start the service. How is this different?

On a more general point - how is it that an RPM package that installs an application that runs as a service does not create the service? Is that not an important part of the RPM package's job? What good is throwing down binaries if you don't create the necessary system components to properly run the binaries?

Please do not think that I am flaming you. I am simply asking what I believe to be fundamental questions about the the purpose of RPMs in general, and the Newton openstack-keystone-10.0.0-1.el7.noarch RPM in particular.

Perhaps I am misunderstanding. If so, please supply me with more information to help me gain clarity.

Regards,

Scott

[Steve Martinelli (stevemar)]

Hi Scott, I manage the keystone queue for launchpad, it's meant for keystone bugs, the issue you're having (IIUC) is related to the RPM package. I don't want to simply mark the bug as invalid and leave you in a lurch. So I'll provide some pointers:

The red hat published install guide can be seen here: http://docs.openstack.org/newton/install-guide-rdo/keystone-install.html#install-and-configure-components

I think the hiccup here is that keystone is one of the few openstack services that does not use eventlet, we use apache httpd (or another web server) to host the application. I'm not sure if a service is installed now, i'm not familiar enough with what the various OS packagers are doing, but it looks like you're install httpd as well, so restarting httpd should be sufficient to restart keystone.

And if you're still having trouble, you can file a bug with the packaging team: https://bugzilla.redhat.com/buglist.cgi?component=openstack-keystone&product=RDO

I'm marking the bug as discussion. Hopefully I've pointed you in the right direction.

[Scott W (cswcloud)]

This reply is to Steve Martinelli and Zarco Cvetojevic:
Steve - Thanks for the note on Apache. I will try that when I have time. unfortunately, work has overwhelmed my personal openstack development track the last month+. I will check on the httpd daemon once I get back to my openstack work.

Zarco - if you are running into the same problem I am, try Steve's advice above about checking to see if Apache httpd package/service is installed, and go from there. I will post any knowledge I gain on the subject to this thread.

If you gain any useful tips/knowledge, please post them to this thread.