Comment 3 for bug 1493816

Reviewed: https://review.openstack.org/224079
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=db9ddd39d3f3d854d38e4b05655ebddd98f1a727
Submitter: Jenkins
Branch: master

commit db9ddd39d3f3d854d38e4b05655ebddd98f1a727
Author: Grzegorz Grasza <email address hidden>
Date: Wed Sep 16 15:12:42 2015 +0200

    Implement indirection_api

    During a rolling upgrade, ironic conductor and api services are running
    with different versions. When an object is received in an incompatible
    version, IncompatibleObjectVersion is raised. Implementation of the
    indirection API allows the object to be backported to a supported version
    by the conductor (conductor has to be the first service to be upgraded).

    This change enables backporting of objects from Mitaka. This lays the
    foundation to be able to do rolling upgrades from Liberty (or from this
    patch onwards) to Mitaka. There may still be other issues that will need
    fixing in Mitaka before we will be able to do a full rolling upgrade.

    Enabling the indirection_api causes all object methods decorated with
    the remotable or remotable_classmethod to do RPC from ironic-api to
    ironic-conductor service. To keep the current behavior, I'm removing all
    remotable decorators on object methods and thus not enabling object RPC
    calls in this patch. These calls caused random timeouts on the CI gates
    (probably due to a race in which Nova calls the ironic-api service before
    ironic-conductor is up). RPC calls made via the indirection_api should
    be enabled one-by-one, when the implications are fully understood.

    Change-Id: Ia381348da93f95d764c83f3ec2a2ed5a1db5ad6d
    Closes-Bug: 1493816
    Depends-On: I81400305f166d62aa4612aab54602abb8178b64c