yahoo-eng-team team mailing list archive

[netproducts <1735192@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The HA guide over at

https://docs.openstack.org/ha-guide/controller-ha-identity.html

recommends downloading an OCF resource agent from git. This OCF resource
agent is now about 18 months old, dating from early 2016. It still uses
the commands 'keystone-all' and 'keystone'. Both executables no longer
exist, so the resource agent does not work as-is.

The newer commands are 'keystone-manage' and 'openstack'

In addition, 'keystone user-list' is wrong syntax, it should now be 'openstack user list'
Here's a diff of the changes I made; 

38c38
< OCF_RESKEY_binary_default="keystone-manage"
---
> OCF_RESKEY_binary_default="keystone-all"
42c42
< OCF_RESKEY_client_binary_default="openstack"
---
> OCF_RESKEY_client_binary_default="keystone"
250c250
<         user list > /dev/null 2>&1
---
>         user-list > /dev/null 2>&1

While this fixes errors in the resource agent, It's still impossible for
me to run keystone via the OCF, simply because, since those commands
were removed, there's no way for me to stop keystone from running via
whatever weird mechanism my debian installed it to run as.

It's not systemd, it's not sysv, it's not ocf either. But keystone is
running and working, and I can't seem to stop it. Which I need to do to
turn my keystone that runs on each node induvidually into a cloned
pacemaker/corosync resource as instructed by the HA guide.

In addition, I can't help but notice the HA guide only speaks about RHEL
and SUSE. Where's the Ubuntu section for Keystone HA? It's there for the
other components...

ps aux | grep keystone

returns 10 lines like these;

keystone 10173  0.0  1.8 409096 111612 ?       Sl   06:25   0:17 (wsgi
:keystone-pu -k start

The real problem the deprecation of the keystone management tools is;
How do I add whatever-this-weird-process-method-is to be managed by
corosync? I'm not writing my own OCF scripts, turns out this is hard to
get it right.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1735192

Title:
  OCF resource agent out of date or HA guide incorrect.

Status in OpenStack Identity (keystone):
  New

Bug description:
  The HA guide over at

  https://docs.openstack.org/ha-guide/controller-ha-identity.html

  recommends downloading an OCF resource agent from git. This OCF
  resource agent is now about 18 months old, dating from early 2016. It
  still uses the commands 'keystone-all' and 'keystone'. Both
  executables no longer exist, so the resource agent does not work as-
  is.

  The newer commands are 'keystone-manage' and 'openstack'

  In addition, 'keystone user-list' is wrong syntax, it should now be 'openstack user list'
  Here's a diff of the changes I made; 

  38c38
  < OCF_RESKEY_binary_default="keystone-manage"
  ---
  > OCF_RESKEY_binary_default="keystone-all"
  42c42
  < OCF_RESKEY_client_binary_default="openstack"
  ---
  > OCF_RESKEY_client_binary_default="keystone"
  250c250
  <         user list > /dev/null 2>&1
  ---
  >         user-list > /dev/null 2>&1

  While this fixes errors in the resource agent, It's still impossible
  for me to run keystone via the OCF, simply because, since those
  commands were removed, there's no way for me to stop keystone from
  running via whatever weird mechanism my debian installed it to run as.

  It's not systemd, it's not sysv, it's not ocf either. But keystone is
  running and working, and I can't seem to stop it. Which I need to do
  to turn my keystone that runs on each node induvidually into a cloned
  pacemaker/corosync resource as instructed by the HA guide.

  In addition, I can't help but notice the HA guide only speaks about
  RHEL and SUSE. Where's the Ubuntu section for Keystone HA? It's there
  for the other components...

  ps aux | grep keystone

  returns 10 lines like these;

  keystone 10173  0.0  1.8 409096 111612 ?       Sl   06:25   0:17 (wsgi
  :keystone-pu -k start

  The real problem the deprecation of the keystone management tools is;
  How do I add whatever-this-weird-process-method-is to be managed by
  corosync? I'm not writing my own OCF scripts, turns out this is hard
  to get it right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1735192/+subscriptions