F5 Pool Monitoring in Kilo

Bug #1399382 reported by Ian Cordasco
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
High
Evan Callicoat

Bug Description

Opened by claco on 2014-11-21 17:26:37+00:00 at https://github.com/rcbops/ansible-lxc-rpc/issues/607

------------------------------------------------------------

Filing this now, before we forget to do something about it in Kilo times.

XML is deprecated in Juno Keystone, and will be removed in Kilo. The F5 currently uses the xml output to grab the token and monitor the nodes in the various api pools.

The python on the F5 is 2.4 and read only, with no json support. We will have to devise an alternative for the Kilo release.

The script: #605
Related: #140

Tags:

====================== COMMENTS ============================

no longer affects: openstack-ansible/next
Changed in openstack-ansible:
milestone: none → next
Changed in openstack-ansible:
importance: Undecided → Wishlist
Changed in openstack-ansible:
importance: Wishlist → High
Changed in openstack-ansible:
assignee: nobody → Evan Callicoat (apsu-2)
Revision history for this message
Kevin Carter (kevin-carter) wrote :

this is a hold over issue from the rcbops github migration. this issue should be moved to rpc-extras (https://github.com/rcbops/rpc-extras)

Changed in openstack-ansible:
status: New → Invalid
Revision history for this message
Evan Callicoat (diopter) wrote :
Changed in openstack-ansible:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.