Perfect, thank you Alex.

I'll depend the update review on it.

Best regards,
  Alex Levine


On 12/15/15 4:03 PM, Alex Xu wrote:
Hi, Alexandre,

we discussed this on api meeting http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-12-15-12.00.log.html

Finally people agreement on merge os-user-data into servers. I will submit a patch up for this merge.

Thanks
Alex

2015-12-14 21:24 GMT+08:00 Alex Xu <sou...@gmail.com <mailto:sou...@gmail.com>>:

    Hi, Alexandre,

    Yes, I think we need pass the version into `server_update`
    extension point. My irc nick is alex_xu, let me know if you have
    any trouble with this.

    Thanks
    Alex

    2015-12-13 2:34 GMT+08:00 Alexandre Levine
    <alexandrelev...@gmail.com <mailto:alexandrelev...@gmail.com>>:

        Hi all,

        os-user-data extension implements server_create method to add
        user_data for server creation. No Controller is used for this,
        only "class UserData(extensions.V21APIExtensionBase)".

        I want to add server_update method allowing to update the
        user_data. Obviously I have to add it as a microversioned
        functionality.

        And here is the problem: there is no information about the
        incoming request version in this code. It is available for
        Controllers only. But checking the version in controller would
        be too late, because the instance is already updated
        (non-generator extensions are post-processed).

        Can anybody guide me how to resolve this collision?

        Would it be possible to just retroactively add the user_data
        modification for the whole 2.1 version skipping the
        microversioning? Or we need to change nova so that request
        version is passed through to extension?

        Best regards,
          Alex Levine

        P.S. Sorry for the second attempt - previous letter went with
        [openstack] instead of [openstack-dev] in the Subject.



        
__________________________________________________________________________
        OpenStack Development Mailing List (not for usage questions)
        Unsubscribe:
        openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
        <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to