[openstack-dev] [nova] Contribution to improve Nova's config option space

Markus Zoeller mzoeller at de.ibm.com
Thu Dec 10 18:21:11 UTC 2015

In case you are one of the people who are already working on patches
for this, you might have observed a merge conflict with your patches
in the last days. Ed Leafe and I are working on a approach to reduce
that. It's basically a list of placeholders in the file 
"nova/conf/__init__.py" in the form of comments like this:
    # import nova.conf.configdrive
    # import nova.conf.rdp
    # import nova.conf.spice
    # import nova.conf.keymgr
When you rebase your changes on that patch and remove the appropriate
comment sign you should be saver for merge conflicts. We are still
working on that patch and aim for the next few days. Ping me in IRC
if you have questions (I'm not around at Dec. 11th(FRI) + 15th (TUE)).

Regards and thanks for your efforts, Markus Zoeller (markus_z)

Markus Zoeller/Germany/IBM at IBMDE wrote on 12/03/2015 05:10:48 PM:

> From: Markus Zoeller/Germany/IBM at IBMDE
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev at lists.openstack.org>
> Date: 12/03/2015 05:12 PM
> Subject: [openstack-dev] [nova] Contribution to improve Nova's config 
> option space
> Who
> ===
> If you are a new contributor and are still searching for a way to
> contribute to Nova, this mail is for you. If you are not a newbie
> but have a bit bandwidth available, you're welcome too :)
> Why
> ===
> Why you should bother?
> * It's an easy way to start contributing
> * I can offer you to help with:
>     * pushing patches, 
>     * debugging the gate,
>     * dealing with reviews
>     * and learning the general workflow
> * you will learn about different functional areas and can give back
>   to the community
> What
> ====
> There is effort ongoing to improve the way Nova offers its configuration
> options to the operators [1]. In short, you have to read and understand 
> code and describe the impact of config options as a black box so that 
> operators don't have to read code to understand what they are 
> At the end it will look like these two patches:
> * https://review.openstack.org/#/c/244177/
> * https://review.openstack.org/#/c/246465/
> How
> ===
> The organization is done with an etherpad [2] which contains:
> * what needs to be done
> * how it has to be done
> Just ping me (markus_z) in the #openstack-nova channel (I'm in the
> UTC+1 timezone) or grab something out of the etherpad [2] and give
> it a try.
> References
> ==========
> [1] blueprint "centralize config options":
> http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/
> centralize-config-options.html
> [2] https://etherpad.openstack.org/p/config-options
> Regards, Markus Zoeller (markus_z)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list