grizzly: ServiceGroup monitoring APIs

Bug #1084500 reported by Tom Fifield
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Medium
Tom Fifield

Bug Description

If https://review.openstack.org/#/c/10903/ is merged, it adds new APIs for ServiceGroup Monitoring.

    Summary:
    * provide a pluggable ServiceGroup monitoring API
    * refactor the old DB-based implementation to the new API

    Currently nova compute nodes periodically write to the database (every
    10 seconds by default) to report their liveness. This implementation
    factors out this functionality and make it a set of abstract internal
    APIs with a pluggable backend implementation. Currently it's named as
    ServiceGroup APIs.

    With this effort, we are hopeful to see the following benefits:

     * We expect to see more backend implementations in addition to the
    default database-based one, such as ZooKeeper (as described in
    blueprint zk-service-heartbeat) or rabbitmq heartbeat based.

     * We expect the code to live in openstack-common so projects other
    than Nova can take advantage of the internal APIs.

     * Lay the foundations to use lower overhead heartbeat mechanisms
    which scale better.

     * Other than reporting whether a node in a service group is up or
    down, the code may also be used to query for members. Other parts of
    the code could also take advantage of the new APIs. One noteable
    example is the MatchMaker in the rpc library, which may even become
    redundant. We have been working with Eric at Cloudscaling to see how
    this fits with the matchmaker. It is likely that this code will need
    to be used, at least by the peer-to-peer based RPC mechanisms, to
    implement the new create_worker method.

    DocImpact: new config options

Revision history for this message
Tom Fifield (fifieldt) wrote :

Patch is merged

Changed in openstack-api-site:
milestone: none → grizzly
Changed in openstack-manuals:
milestone: none → grizzly
Changed in openstack-api-site:
status: New → Confirmed
Changed in openstack-manuals:
status: New → Confirmed
Changed in openstack-api-site:
importance: Undecided → Medium
Changed in openstack-manuals:
importance: Undecided → Medium
tags: added: nova
Revision history for this message
Tom Fifield (fifieldt) wrote :

cfg.StrOpt('servicegroup_driver',
   32 default=_default_driver,
   33 help='The driver for servicegroup service.')

Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Confirmed → In Progress
assignee: nobody → Tom Fifield (fifieldt)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/21044

Revision history for this message
Tom Fifield (fifieldt) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/21044
Committed: http://github.com/openstack/openstack-manuals/commit/882f733856d949448a6e4d1d445b478b2a425abb
Submitter: Jenkins
Branch: master

commit 882f733856d949448a6e4d1d445b478b2a425abb
Author: Tom Fifield <email address hidden>
Date: Sat Feb 2 19:54:33 2013 +1100

    Add servicegroup_driver config option

    fixes bug 1084500

    Grizzly introduced the ServiceGroup APIs in nova - a set of abstract
    internal APIs with pluggable backend to deal with the reporting of
    'aliveness' by nova- services

    Change-Id: I2a0d14da08a0d9143bb15db4b292b8ef2db688fb

Changed in openstack-manuals:
status: In Progress → Fix Released
Ladquin (ladquin)
Changed in openstack-api-site:
assignee: nobody → Laura Alves (ladquin)
Tom Fifield (fifieldt)
tags: added: compute-api
removed: nova
Tom Fifield (fifieldt)
tags: added: grizzly
Changed in openstack-api-site:
milestone: grizzly → none
assignee: Ladquin (ladquin) → nobody
Anne Gentle (annegentle)
no longer affects: openstack-api-site
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.