Open Stack

Esra Celik <celik.esra at tubitak.gov.tr> wrote on 12/03/2015 06:50:49 PM:

> From: Esra Celik <celik.esra at tubitak.gov.tr>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev at lists.openstack.org>
> Date: 12/03/2015 06:51 PM
> Subject: Re: [openstack-dev] [nova] Contribution to improve Nova's 
> config option space
> 
> Hi Markus,
> 
> This seems to be a good one for me to start contributing to nova.
> And happily it will be useful for me as an openstack operator too.
> 
> I couldn't find you at IRC, maybe a little late.. 
> Where do you think should I start? I can see a list for config options
> at etherpad.
> 
> Thanks in advance
> 
> Esra ÇELİK
> www.bilgem.tubitak.gov.tr
> celik.esra at tubitak.gov.tr

Hi Esra,

there are some "good for starters" comments in the mentioned etherpad.
Just pick one of those. Maybe the 'filesystems' option. Thanks for your
help!

Regards, Markus Zoeller 


> Kimden: "Markus Zoeller" <mzoeller at de.ibm.com>
> Kime: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev at lists.openstack.org>
> Gönderilenler: 3 Aralık Perşembe 2015 18:10:48
> Konu: [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 
the 
> operators don't have to read code to understand what they are 
configuring.
> 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
> 
__________________________________________________________________________
> 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