Esra Celik <celik.e...@tubitak.gov.tr> wrote on 12/04/2015 02:08:50 PM:
> From: Esra Celik <celik.e...@tubitak.gov.tr>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Date: 12/04/2015 02:09 PM
> Subject: Re: [openstack-dev] [nova] Contribution to improve Nova's
> config option space
>
> Thanks Markus,
>
> I started with image_file_url opts in /nova/image/download/file.py
> however there is note out there
>
> # NOTE(jbresnah) because the group under which these options are added
is
> # dyncamically determined these options need to stay out of global space
> # or they will confuse generate_sample.sh
>
> Is it still sensible to move those opts out to nove/conf directory or
> will I only move the filesystems opt?
> Actually is there a faster way to ask you questions about the issue?
>
> Regards,
> Esra Çelik
Oh, great, that looks like it needs special handling... sorry.
Better start with the options at nova/virt/configdrive.py
For realtime communication: IRC helps a lot. If you don't have a local
client (I use XChat) you can use your browser:
http://webchat.freenode.net/?channels=openstack-nova
My nick is "markus_z". More info about IRC at:
* https://wiki.openstack.org/wiki/UsingIRC
* https://wiki.openstack.org/wiki/IRC
> Kimden: "Markus Zoeller" <mzoel...@de.ibm.com>
> Kime: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Gönderilenler: 4 Aralık Cuma 2015 11:37:43
> Konu: Re: [openstack-dev] [nova] Contribution to improve Nova's
> config option space
>
> Esra Celik <celik.e...@tubitak.gov.tr> wrote on 12/03/2015 07:58:36 PM:
>
> > From: Esra Celik <celik.e...@tubitak.gov.tr>
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev@lists.openstack.org>
> > Date: 12/03/2015 07:59 PM
> > Subject: Re: [openstack-dev] [nova] Contribution to improve Nova's
> > config option space
> >
> > OK, got it
> >
> > Do you have a generic IDE for remote debugging of nova, like pycharm?
> > Or how do you actually debug the code?
> >
> > Regards
> >
> > Esra ÇELİK
> > www.bilgem.tubitak.gov.tr
> > celik.e...@tubitak.gov.tr
>
> Personally, I use Eclipse with the PyDev plugin but also give PyCharm
> a try. Just choose what you feel comfortable with. The Nova code has a
> lot of unit tests which are the best documentation how the code should
> behave. They are also easier and faster to execute than to start a whole
> system and debug it remotely. The Nova docs explain how to do it with
> the tool *tox* [1].
>
> [1] http://docs.openstack.org/developer/nova/unit_tests.html
>
> Regards, Markus Zoeller (markus_z)
>
>
> > Kimden: "Markus Zoeller" <mzoel...@de.ibm.com>
> > Kime: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev@lists.openstack.org>
> > Gönderilenler: 3 Aralık Perşembe 2015 20:11:08
> > Konu: Re: [openstack-dev] [nova] Contribution to improve Nova's config
> > option space
> >
> > Esra Celik <celik.e...@tubitak.gov.tr> wrote on 12/03/2015 06:50:49
PM:
> >
> > > From: Esra Celik <celik.e...@tubitak.gov.tr>
> > > To: "OpenStack Development Mailing List (not for usage questions)"
> > > <openstack-dev@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.e...@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" <mzoel...@de.ibm.com>
> > > Kime: "OpenStack Development Mailing List (not for usage questions)"
> > > <openstack-dev@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-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
> >
>
__________________________________________________________________________
> > 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
>
__________________________________________________________________________
> 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
