Add rpc client side version control

Bug #1197657 reported by Tom Fifield
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
High
Sina Sadeghi

Bug Description

https://review.openstack.org/32721

Log:
commit 2bcdb2057188a1a1bd1731ff713631e8a30e4f20
Author: Russell Bryant <email address hidden>
Date: Mon Jun 10 21:18:37 2013 -0400

    Add rpc client side version control.

    This is a first pass at client side version control for rpc. It allows
    you to configure a max version of messages that clients are allowed to
    send. You can find one example of how clients need to adapt in the
    conductor rpcapi. All other changes in rpc apis since the grizzly
    release are not applicable to this.

    Some future improvements to this could be reporting the versions
    supported by running services and having that be discoverable via the
    API. We could also consider allow setting these client side version
    caps via the API. For now, recommended values for these config
    options while attempting a rolling upgrade will just have to be documented.

    The config options allow specifying specific rpc api version numbers if
    desired, but an alias of 'grizzly' is also supported. So typically at
    the start of a rolling upgrade you'd have:

        [upgrade_levels]
        compute=grizzly
        conductor=grizzly
        scheduler=grizzly
        ... etc ...

    And as you update all instances of a service, you would remove that bit
    from your configuration across the deployment using your config management
    system of choice.

    DocImpact

    Implements blueprint rpc-version-control.

Tags: nova
Tom Fifield (fifieldt)
Changed in openstack-manuals:
importance: Undecided → Medium
status: New → Confirmed
milestone: none → havana
tags: added: nova
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/35726
Committed: http://github.com/openstack/openstack-manuals/commit/eae9f5b9b5509a6988d2900038c05dab14d2e573
Submitter: Jenkins
Branch: master

commit eae9f5b9b5509a6988d2900038c05dab14d2e573
Author: Tom Fifield <email address hidden>
Date: Fri Jul 5 11:07:55 2013 +1000

    Add Autogenerate-config-doc code to tools

    This patch brings the auto-generate-config doc tool into
    the openstack-manuals repo, where it can be used to update
    the configuration option tables.

    patchset2 fixes obvious things noted by reviewers, likely
    needs more fixing.

    patchset 4 adds update feature, fixes pep8

    patchset 5 removes debugging print

    patchset 6 adds warning to tables regarding their
               automatically generated nature

    patchset 7 updated nova flagmappings for H2 and
               adds updated nova tables

    patchset 8 adds a seciton in the readme with a worked example
               from a recent use of the script

    patchset 10 fixes for cinder
    patchset 11 testing, fixing
    patchset 12 testing, fixing
    patchset 13 adds categories to cinder.flagmappings, generates
                docbook tables for cinder
    patchset 14 adds mappings for neutron, and generates docbook
                tables based on these

    patchset 15 adds list of bugs this patch will fix

    patchset 16 fixes whitespace error in automatically generated tables :(

    fixes bug 1192225
    Partial-Bug 1207550
    Partial-Bug 1207549
    fixes bug 1206827
    Partial-Bug 1206336
    fixes bug 1204484
    Partial-Bug 1204205
    fixes bug 1202260
    fixes bug 1201710
    fixes bug 1200794
    Partial-Bug 1200740
    Partial-Bug 1200418
    Partial-Bug 1200047
    Partial-Bug 1199209
    Partial-Bug 1197657
    fixes bug 1197653
    fixes bug 1197295
    Partial-Bug 1197088
    Partial-Bug 1195900
    fixes bug 1195560
    fixes bug 1195433
    Partial-Bug 1192752
    fixes bug 1187278
    Partial-Bug 1106428
    Change-Id: Icd3f4496850c375c9359a10eddb25ab5c722595e
    bp:autogenerate-config-tables

Tom Fifield (fifieldt)
Changed in openstack-manuals:
importance: Medium → High
milestone: havana → juno
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to operations-guide (master)

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

Changed in openstack-manuals:
assignee: nobody → Sina Sadeghi (sina-sa)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to operations-guide (master)

Reviewed: https://review.openstack.org/105336
Committed: https://git.openstack.org/cgit/openstack/operations-guide/commit/?id=ed9826bf102ad44be5de414a84748cb8507956c2
Submitter: Jenkins
Branch: master

commit ed9826bf102ad44be5de414a84748cb8507956c2
Author: Sina Sadeghi <email address hidden>
Date: Tue Jul 8 12:36:54 2014 +1000

    Add subsection for nova upgrade levels.

    This patch adds a subsection to the operations guide to provide a
    summary of what nova upgrade levels are and brief explanation of
    their utility in live upgrades, along with a small configuration
    example.

    Change-Id: I55f24ab0ad3945d601882faac09a7fc479424975
    Closes-Bug: 1197657

Changed in openstack-manuals:
status: In Progress → Fix Released
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.