Re: [openstack-dev] [ironic] Stepping down as core

[John Villalovos]

Sorry to see you go Sam. You were a big asset to the community! Good luck
for the future.

John

On Thu, Oct 11, 2018 at 4:41 AM Sam Betts (sambetts) 
wrote:

> As many of you will have seen on IRC, I've mostly been appearing AFK for
> the last couple of development cycles. Due to other tasks downstream most
> of my attention has been drawn away from upstream Ironic development. Going
> forward I'm unlikely to be as heavily involved with the Ironic project as I
> have been in the past, so I am stepping down as a core contributor to make
> way for those more involved and with more time to contribute.
>
> That said I do not intend to disappear, Myself and my colleagues plan to
> continue to support the Cisco Ironic drivers, we just won't be so heavily
> involved in core ironic development and its worth noting that although I
> might appear AFK on IRC because my main focus is on other things, I always
> have an ear to the ground and direct pings will generally reach me.
>
> I will be in Berlin for the OpenStack summit, so to those that are
> attending I hope to see you there.
>
> The Ironic project has been (and I hope continues to be) an awesome place
> to contribute too, thank you
>
> Sam Betts
> sambetts
>
>
> __
> 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-dev] Stepping down from Ironic core

[John Villalovos]

Good morning Ironic,

I have come to realize that I don't have the time needed to be able to
devote the attention needed to continue as an Ironic core.

I'm hopeful that in the future I will work on Ironic or OpenStack again! :)

The Ironic (and OpenStack) community has been a great one and I have really
enjoyed my time working on it and working with all the people. I will still
be hanging around on IRC and you may see me submitting a patch here and
there too :)

Thanks again,
John
__
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

Re: [openstack-dev] [ironic] Stepping down from Ironic core

[John Villalovos]

Very sorry to see you go :( You have been a great contributor to Ironic!
And a pleasure to work with.

Best of luck for you and your future :)

John

On Fri, Feb 23, 2018 at 1:02 AM, Vasyl Saienko 
wrote:

> Hey Ironic community!
>
> Unfortunately I don't work on Ironic as much as I used to any more, so i'm
> stepping down from core reviewers.
>
> So, thanks for everything everyone, it's been great to work with you
> all for all these years!!!
>
>
> Sincerely,
> Vasyl Saienko
>
> __
> 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

Re: [openstack-dev] [ironic] Nominating Hironori Shiina for ironic-core

[John Villalovos]

+1

On Mon, Feb 5, 2018 at 10:12 AM, Julia Kreger 
wrote:

> I would like to nominate Hironori Shiina to ironic-core. He has been
> working in the ironic community for some time, and has been helping
> over the past several cycles with more complex features. He has
> demonstrated an understanding of Ironic's code base, mechanics, and
> overall community style. His review statistics are also extremely
> solid. I personally have a great deal of trust in his reviews.
>
> I believe he would make a great addition to our team.
>
> Thanks,
>
> -Julia
>
> __
> 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

Re: [openstack-dev] [glance][oslo][requirements] [ironic]oslo.serialization fails with glance

[John Villalovos]

I have updated the bug with info I found out:
https://bugs.launchpad.net/oslo.serialization/+bug/1728368

Also I did a test patch with a proposed change:
https://review.openstack.org/#/c/535166/

This patch causes the unit tests to work.

As a note there is a deprecation warning in the current code (without my
patch) that says in the future it will raise a ValueError() as can be seen
in a recently merged patch:
http://logs.openstack.org/72/533872/6/check/openstack-tox-py27/4709e32/job-output.txt.gz#_2018-01-16_13_10_38_931593

The test patch gets rid of that deprecation warning for the exceptions.

Though I did see another warning about the "Response" object:
http://logs.openstack.org/66/535166/2/check/openstack-tox-py35/33d0827/job-output.txt.gz#_2018-01-18_05_13_52_603162

But that is for someone else to figure out :)



On Wed, Jan 17, 2018 at 7:13 PM, ChangBo Guo  wrote:

> add Ironic team  in the loop
>
> the revert patch got -1 from  ironic folks , more details  please see the
> comments in https://review.openstack.org/534736
> The possible solution is to figure out why  the change break Glance's unit
> test.  which side should be fixed.
>
>
>
> 2018-01-17 20:14 GMT+08:00 ChangBo Guo :
>
>> I dig a little.  It shows success when updating constraint to 2.21.2 [1]
>> but failure when updating constraint to 2.22.0 [2].   according to release
>> information [3].
>> It means 2.21.1 works with glance test but  2.21.2 doesn't work well with
>> glance. The only issue patch is https://github.com/openstack/o
>> slo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8.
>>
>>
>> [1] https://review.openstack.org/514833
>> [2] https://review.openstack.org/#/c/525136
>> [3] https://github.com/openstack/releases/blob/master/deliverabl
>> es/queens/oslo.serialization.yaml
>>
>>
>> Actions:
>>
>> Block  oslo.serialization  version  2.21.2,  2.22.0, 2. 23.0in
>> https://review.openstack.org/534739
>> Revert c1a7079c26d27a2e46cca26963d3d9aa040bdbe8 in
>> https://review.openstack.org/534736
>>
>>
>>
>>
>> 2018-01-16 23:35 GMT+08:00 Matthew Thode :
>>
>>> On 18-01-16 19:12:16, ChangBo Guo wrote:
>>> > What's the issue for Glance,  any bug link ?
>>> >
>>> > 2018-01-16 0:12 GMT+08:00 Matthew Thode :
>>> >
>>> > > On 18-01-13 00:41:28, Matthew Thode wrote:
>>> > > > https://review.openstack.org/531788 is the review we are seeing
>>> it in,
>>> > > > but 2.22.0 failed as well.
>>> > > >
>>> > > > I'm guessing it was introduced in either
>>> > > >
>>> > > > https://github.com/openstack/oslo.serialization/commit/
>>> > > c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
>>> > > > or
>>> > > > https://github.com/openstack/oslo.serialization/commit/
>>> > > cdb2f60d26e3b65b6370f87b2e9864045651c117
>>> > >
>>> > > bamp
>>> > >
>>>
>>> The best bug for this is
>>> https://bugs.launchpad.net/oslo.serialization/+bug/1728368 and we are
>>> currently getting test fails in https://review.openstack.org/531788
>>>
>>> --
>>> Matthew Thode (prometheanfire)
>>>
>>
>>
>>
>> --
>> ChangBo Guo(gcb)
>> Community Director @EasyStack
>>
>
>
>
> --
> ChangBo Guo(gcb)
> Community Director @EasyStack
>
> __
> 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-dev] [Ironic] ironic tempest plugin code has been moved to openstack/ironic-tempest-plugin/

[John Villalovos]

The ironic tempest plugin code that was in openstack/ironic and
openstack/ironic-inspector has been moved to
openstack/ironic-tempest-plugin/

As of 10-Jan-2018 (Wednesday) the plugin code was deleted from
openstack/ironic and openstack/ironic-inspector. All users of the tempest
plugin code need to be using it from the openstack/ironic-tempest-plugin
repository now.

We believe that all of the 3rd Party CIs have already made this change.
Thanks to everyone working on this!

Thanks,
John
__
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

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

[John Villalovos]

Note: I am proposing in the next Ironic meeting (
https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting )
that we move forward on removing the tempest plugin code from
openstack/ironic and openstack/ironic-inspector. It will have been over
three weeks since the initial email in this thread (15-Dec-2017) about
removing the code.

Thanks,
John

On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <openstack@sodarock.com
> wrote:

> I wanted to send out a note to any 3rd Party CI or other users of the
> tempest plugin code inside either openstack/ironic or
> openstack/ironic-inspector. That code has been migrated to the
> openstack/ironic-inspector-plugin repository. We have been busily (
> https://review.openstack.org/#/q/topic:ironic-tempest-plugin ) migrating
> all of the projects to use this new repository.
>
> If you have a 3rd Party CI or something else that is depending on the
> tempest plugin code please migrate it to use openstack/ironic-tempest-
> plugin.
>
> We plan to remove the tempest plugin code on Tuesday 19-Dec-2017 from
> openstack/ironic and openstack/ironic-tempest-plugin. And then after that
> doing backports of those changes to the stable branches.
>
> openstack/ironic Removal patch
> https://review.openstack.org/527733
>
> openstack/ironic-inspector Removal patch
> https://review.openstack.org/527743
>
__
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

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

[John Villalovos]

Please feel free to reach out to me (jlvillal) on IRC (#openstack-ironic)
or here if anyone has questions on how to transition over. For our Ironic
jobs it was about a 4 line change per job.

See the openstack/ironic patch here:
https://review.openstack.org/#/c/527730/

Basically need to bring in the openstack/ironic-tempest-plugin project

And then change TEMPEST_PLUGINS references to /opt/stack/new/ironic to
/opt/stack/new/ironic-tempest-plugin:

-export DEVSTACK_LOCAL_CONFIG+=$'\n'"TEMPEST_PLUGINS+='
/opt/stack/new/ironic'"
+export DEVSTACK_LOCAL_CONFIG+=$'\n'"TEMPEST_PLUGINS+='
/opt/stack/new/ironic-tempest-plugin'"


On Tue, Dec 19, 2017 at 7:50 AM,  wrote:

> *Dell - Internal Use - Confidential *
>
> Dell Ironic Ci is failing on this patch because of that. With holidays and
> many on vacation, would appreciate some additional time to make the switch.
>
> Thanks
>
> Rajini
>
>
>
> *From:* Ruby Loo [mailto:opensr...@gmail.com]
> *Sent:* Tuesday, December 19, 2017 8:48 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Ironic] Removal of tempest plugin code
> from openstack/ironic & openstack/ironic-inspector
>
>
>
>
>
>
>
> On Mon, Dec 18, 2017 at 11:29 PM,  wrote:
>
> Thanks for response.
> My recommendation is:
> 1. only allow patches into openstack/ironic-tempest-plugin
> 2. Give Ironic CI owners time period (3 weeks?) to switch their setup to
> only use openstack/ironic-tempest-plugin and not master and report back
> to Ironic CI team if it works for them. If yes, go ahead and switch if not,
> report back.
> 3. At the end of that time, if majority of Ironic CI site complete their
> transition to ironic-tempest-plugin we switch.
>
> Thanks,
> Arkady
>
>
>
> I think this is reasonable. I cringe at knowingly doing something that
> will most likely break the third party CI when people are away and cannot
> address it. Also, apart from the danger that the third party CIs are
> running old versions of the tempest plugins (I doubt that we'll be doing
> major overhaul of that in the next 2+ weeks), the reason we have 3rd party
> CI is to make sure patches work against those HW. Having most or all of
> them being unavailable due to this breakage means that there won't be any
> feedback that someone's code would have broken 3rd party CI outside of the
> tempest changes.
>
>
>
> John, don't you have a patch that removes the tempest plugin from master?
> Do most/all of the 3rd party CIs fail due to that? (Or is it not as simple
> as that?) Ah, yes, https://review.openstack.org/#/c/527733/ shows that
> all the 3rd party CI fail (although I don't know if it is due to that patch
> or if they were already failing prior to that).
>
>
>
> --ruby
>
> __
> 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

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

[John Villalovos]

One issue is that development is going to move forward on
openstack/ironic-tempest-plugin. No new code will go into the tempest
plugin code in either openstack/ironic or openstack/ironic-inspector.

And actually I almost think the holiday time is the best time since the
fewest number of people are going to care. But maybe I'm wrong. I do wonder
if nobody is around to watch a 3rd Party CI for two weeks, how likely is it
to still be working when they get back?

I'm not vehemently opposed to delaying, but somewhat opposed.

Thoughts?
John

On Mon, Dec 18, 2017 at 11:19 AM, <arkady.kanev...@dell.com> wrote:

> John,
>
> Should we give all Ironic CI maintainers to do the migration before
> pulling the code from master?
>
> Especially that close to holiday season when a lot of folks are out.
>
> We want to avoid Ironic CI not being functional for several weeks.
>
> Thanks,
>
> Arkady
>
>
>
> *From:* John Villalovos [mailto:openstack@sodarock.com]
> *Sent:* Monday, December 18, 2017 10:59 AM
> *To:* openstack-dev <openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Ironic] Removal of tempest plugin code
> from openstack/ironic & openstack/ironic-inspector
>
>
>
> To hopefully make things more clear.
>
> All of the ironic related projects that were using the tempest-plugin code
> from either openstack/ironic or openstack/ironic-inspector have been
> migrated to use the tempest-plugin code in openstack/ironic-tempest-plugin.
> This includes master and stable branches. Previously all branches (master
> and stable) were pulling from the master branch of openstack/ironic and/or
> openstack/ironic-inspector to get the tempest-plugin code. Now they all
> pull from the master branch of openstack/ironic-tempest-plugin. Note:
> openstack/ironic-tempest-plugin will NOT have any stable branches, only
> master.
>
> We will be removing all the tempest-plugin code from the master branch of
> openstack/ironic and openstack/ironic-inspector on Tuesday 19-Dec-2017. We
> will NOT be removing the tempest-plugin code from any stable branches. We
> (Ironic) didn't/don't use that code but since downstream consumers may we
> will leave it in place.
>
> Any 3rd Party CI that are testing using the tempest-plugin code pulled
> from master will need to update their CI to now use
> openstack/ironic-tempest-plugin
>
> Again we will be removing all the tempest-plugin code from the master
> branch of openstack/ironic and openstack/ironic-inspector on Tuesday
> 19-Dec-2017. If your CI depends on that code, please update to use the new
> openstack/ironic-tempest-plugin repository.
>
>
>
>
>
> On Mon, Dec 18, 2017 at 8:33 AM, John Villalovos <
> openstack@sodarock.com> wrote:
>
>
>
>
>
> On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <
> openstack@sodarock.com> wrote:
>
> I wanted to send out a note to any 3rd Party CI or other users of the
> tempest plugin code inside either openstack/ironic or
> openstack/ironic-inspector. That code has been migrated to the
> openstack/ironic-inspector-plugin repository. We have been busily (
> https://review.openstack.org/#/q/topic:ironic-tempest-plugin ) migrating
> all of the projects to use this new repository.
>
> If you have a 3rd Party CI or something else that is depending on the
> tempest plugin code please migrate it to use openstack/ironic-tempest-
> plugin.
>
> We plan to remove the tempest plugin code on Tuesday 19-Dec-2017 from
> openstack/ironic and openstack/ironic-tempest-plugin. And then after that
> doing backports of those changes to the stable branches.
>
>
>
> After discussion on IRC in regards to back-porting to the stable branches.
> We will NOT backport the removal of the tempest plugin code as it could
> break distros and other consumers.
>
>
>
>
>
>
>
> __
> 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

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

[John Villalovos]

To hopefully make things more clear.

All of the ironic related projects that were using the tempest-plugin code
from either openstack/ironic or openstack/ironic-inspector have been
migrated to use the tempest-plugin code in openstack/ironic-tempest-plugin.
This includes master and stable branches. Previously all branches (master
and stable) were pulling from the master branch of openstack/ironic and/or
openstack/ironic-inspector to get the tempest-plugin code. Now they all
pull from the master branch of openstack/ironic-tempest-plugin. Note:
openstack/ironic-tempest-plugin will NOT have any stable branches, only
master.

We will be removing all the tempest-plugin code from the master branch of
openstack/ironic and openstack/ironic-inspector on Tuesday 19-Dec-2017. We
will NOT be removing the tempest-plugin code from any stable branches. We
(Ironic) didn't/don't use that code but since downstream consumers may we
will leave it in place.

Any 3rd Party CI that are testing using the tempest-plugin code pulled from
master will need to update their CI to now use
openstack/ironic-tempest-plugin

Again we will be removing all the tempest-plugin code from the master
branch of openstack/ironic and openstack/ironic-inspector on Tuesday
19-Dec-2017. If your CI depends on that code, please update to use the new
openstack/ironic-tempest-plugin repository.


On Mon, Dec 18, 2017 at 8:33 AM, John Villalovos <openstack@sodarock.com
> wrote:

>
>
> On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <
> openstack@sodarock.com> wrote:
>
>> I wanted to send out a note to any 3rd Party CI or other users of the
>> tempest plugin code inside either openstack/ironic or
>> openstack/ironic-inspector. That code has been migrated to the
>> openstack/ironic-inspector-plugin repository. We have been busily (
>> https://review.openstack.org/#/q/topic:ironic-tempest-plugin ) migrating
>> all of the projects to use this new repository.
>>
>> If you have a 3rd Party CI or something else that is depending on the
>> tempest plugin code please migrate it to use openstack/ironic-tempest-plugi
>> n.
>>
>> We plan to remove the tempest plugin code on Tuesday 19-Dec-2017 from
>> openstack/ironic and openstack/ironic-tempest-plugin. And then after
>> that doing backports of those changes to the stable branches.
>>
>
> After discussion on IRC in regards to back-porting to the stable branches.
> We will NOT backport the removal of the tempest plugin code as it could
> break distros and other consumers.
>
>
>
__
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

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

[John Villalovos]

On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <openstack@sodarock.com
> wrote:

> I wanted to send out a note to any 3rd Party CI or other users of the
> tempest plugin code inside either openstack/ironic or
> openstack/ironic-inspector. That code has been migrated to the
> openstack/ironic-inspector-plugin repository. We have been busily (
> https://review.openstack.org/#/q/topic:ironic-tempest-plugin ) migrating
> all of the projects to use this new repository.
>
> If you have a 3rd Party CI or something else that is depending on the
> tempest plugin code please migrate it to use openstack/ironic-tempest-
> plugin.
>
> We plan to remove the tempest plugin code on Tuesday 19-Dec-2017 from
> openstack/ironic and openstack/ironic-tempest-plugin. And then after that
> doing backports of those changes to the stable branches.
>

After discussion on IRC in regards to back-porting to the stable branches.
We will NOT backport the removal of the tempest plugin code as it could
break distros and other consumers.
__
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-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

[John Villalovos]

I wanted to send out a note to any 3rd Party CI or other users of the
tempest plugin code inside either openstack/ironic or
openstack/ironic-inspector. That code has been migrated to the
openstack/ironic-inspector-plugin repository. We have been busily (
https://review.openstack.org/#/q/topic:ironic-tempest-plugin ) migrating
all of the projects to use this new repository.

If you have a 3rd Party CI or something else that is depending on the
tempest plugin code please migrate it to use
openstack/ironic-tempest-plugin.

We plan to remove the tempest plugin code on Tuesday 19-Dec-2017 from
openstack/ironic and openstack/ironic-tempest-plugin. And then after that
doing backports of those changes to the stable branches.

openstack/ironic Removal patch
https://review.openstack.org/527733

openstack/ironic-inspector Removal patch
https://review.openstack.org/527743
__
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

Re: [openstack-dev] removing screen from devstack - RSN

[John Villalovos]

Does this mean we can now get more user friendly names for the log files?

Currently I see names like:
screen-dstat.txt.gz
screen-etcd.txt.gz
screen-g-api.txt.gz
screen-g-reg.txt.gz
screen-ir-api.txt.gz
screen-ir-cond.txt.gz
screen-keystone.txt.gz
screen-n-api-meta.txt.gz
screen-n-api.txt.gz
screen-n-cauth.txt.gz
screen-n-cond.txt.gz
screen-n-cpu.txt.gz
screen-n-novnc.txt.gz
screen-n-sch.txt.gz
screen-peakmem_tracker.txt.gz
screen-placement-api.txt.gz
screen-q-agt.txt.gz
screen-q-dhcp.txt.gz
screen-q-l3.txt.gz
screen-q-meta.txt.gz
screen-q-metering.txt.gz
screen-q-svc.txt.gz
screen-s-account.txt.gz
screen-s-container.txt.gz
screen-s-object.txt.gz
screen-s-proxy.txt.gz

People new to OpenStack don't really know that 'q' means neutron.



On Thu, Sep 7, 2017 at 5:45 AM, Sean Dague  wrote:

> On 08/31/2017 06:27 AM, Sean Dague wrote:
> > The work that started last cycle to make devstack only have a single
> > execution mode, that was the same between automated QA and local, is
> > nearing it's completion.
> >
> > https://review.openstack.org/#/c/499186/ is the patch that will remove
> > screen from devstack (which was only left as a fall back for things like
> > grenade during Pike). Tests are currently passing on all the gating jobs
> > for it. And experimental looks mostly useful.
> >
> > The intent is to merge this in about a week (right before PTG). So, if
> > you have a complicated devstack plugin you think might be affected by
> > this (and were previously making jobs pretend to be grenade to keep
> > screen running), now is the time to run tests against this patch and see
> > where things stand.
>
> This patch is in the gate and now merging, and with it devstack now has
> a single run mode, using systemd units, which is the same between test
> and development.
>
> Thanks to everyone helping with the transition!
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> 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-dev] [infra][ironic] Patch needed to merge to fix ironic-inspector grenade job

[John Villalovos]

Hi Infra,

We were hoping to get a review of:
https://review.openstack.org/483059
Add the ironic-inspector services to features.yaml
openstack-infra/devstack-gate

As it is needed to fix the ironic-inspector grenade job.

Thanks,
John
__
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

Re: [openstack-dev] [ironic] [stable] another ironic-stable-maint update proposal

[John Villalovos]

I don't get a real vote but +1 from me :)

John

On Fri, Jun 30, 2017 at 9:10 AM, Dmitry Tantsur  wrote:

> Hi all!
>
> I'd like to propose another round of changes to the ironic-stable-maint
> group [0]:
>
> 1. Add Julia Kreger (TheJulia) to the group. Julia is one of the top
> reviewers in Ironic, and she is quite active on stable branches as well [1].
>
> 2. Remove Jim Rollenhagen (sigh..) as he no longer works on OpenStack.
>
> So for those on the team already, please reply with a +1 or -1 vote.
> I'll also need somebody to apply this change, as I don't have ACL for that.
>
> [0] https://review.openstack.org/#/admin/groups/950,members
> [1] https://review.openstack.org/#/q/(project:openstack/ironic+O
> R+project:openstack/ironic-python-agent+OR+project:openstack
> /ironic-lib)+NOT+branch:master+reviewer:%22Julia+
> Kreger+%253Cjuliaashleykreger%2540gmail.com%253E%22
>
> __
> 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-dev] [hacking] Propose removal of cores

[John Villalovos]

I am proposing that the following people be removed as core reviewers from
the hacking project: https://review.openstack.org/#/admin/groups/153,members

Joe Gordon
James Carey


Joe Gordon:
Has not done a review in OpenStack since 16-Feb-2017
http://stackalytics.com/?release=all_id=jogo

Has not done a review in hacking since 23-Jan-2016:
http://stackalytics.com/?module=hacking_id=jogo=all


James Carey
Has not done a review in OpenStack since 9-Aug-2016
http://stackalytics.com/?release=all_id=jecarey

Has not done a review in hacking since 9-Aug-2016:
http://stackalytics.com/?module=hacking=all_id=jecarey


And maybe this project needs more core reviewers as there have been six
total reviews by four core reviewers so far in the Pike cycle:
http://stackalytics.com/?release=pike=hacking
__
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

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

[John Villalovos]

Just getting back from vacation and I read this :(

So sorry to see you go. Thank you for all your help over the years with
Ironic and helping me with Ironic!

Best of luck with your new work. Your new employer is very lucky!

John

On Thu, Jun 8, 2017 at 5:45 AM, Jim Rollenhagen 
wrote:

> Hey friends,
>
> I've been mostly missing for the past six weeks while looking for a new
> job, so maybe you've forgotten me already, maybe not. I'm happy to tell you
> I've found one that I think is a great opportunity for me. But, I'm sad to
> tell you that it's totally outside of the OpenStack community.
>
> The last 3.5 years have been amazing. I'm extremely grateful that I've
> been able to work in this community - I've learned so much and met so many
> awesome people. I'm going to miss the insane(ly awesome) level of
> collaboration, the summits, the PTGs, and even some of the bikeshedding.
> We've built amazing things together, and I'm sure y'all will continue to do
> so without me.
>
> I'll still be lurking in #openstack-dev and #openstack-ironic for a while,
> if people need me to drop a -2 or dictate old knowledge or whatever, feel
> free to ping me. Or if you just want to chat. :)
>
> <3 jroll
>
> P.S. obviously my core permissions should be dropped now :P
>
> __
> 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

Re: [openstack-dev] [Ironic] Stepping down from core

[John Villalovos]

No!!!

Thanks for everything Lucas. Always a pleasure working with you and thanks
for all your help. Especially when I first joined Ironic.

Good luck for the future!

John

On Tue, May 9, 2017 at 7:15 AM, Lucas Alvares Gomes 
wrote:

> Hi all,
>
> This is a difficult email to send. As some of you might already know,
> lately I've been focusing on the OVS/OVN (and related) projects and I
> don't have much time left to dedicate on reviewing patches in Ironic,
> at least for now.
>
> My biggest priority for this cycle was to create a basic Redfish
> driver and now that the patches are merged and a -nv job is running in
> the gate I feel like it would be a good time to step down from the
> core team. If needed, I could still help out as core reviewer on some
> small projects which I'm very familiar with such as Sushy and
> VirtualBMC, those doesn't take much time and the review queue is
> usually short.
>
> Also, this is not a good-bye email, I'm still very interested in
> Ironic and I will continue to follow the project closely as well as be
> around in the #openstack-ironic IRC channel at all times (-:
>
> So, thanks for everything everyone, it's been great to work with you
> all for all these years!!!
>
> Cheers,
> Lucas
>
> __
> 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

Re: [openstack-dev] [ironic] Goodbye ironic o/

[John Villalovos]

Mario,

So sorry you won't be working with us on Ironic anymore :( You have been an
great part of Ironic and I'm glad I got to know you.

Hopefully I will get to work with you again. Best of luck for the future!

John

On Fri, Apr 28, 2017 at 9:12 AM, Mario Villaplana <
mario.villapl...@gmail.com> wrote:

> Hi ironic team,
>
> You may have noticed a decline in my upstream contributions the past few
> weeks. Unfortunately, I'm no longer being paid to work on ironic. It's
> unlikely that I'll be contributing enough to keep up with the project in my
> new job, too, so please do feel free to remove my core access.
>
> It's been great working with all of you. I've learned so much about open
> source, baremetal provisioning, Python, and more from all of you, and I
> will definitely miss it. I hope that we all get to work together again in
> the future someday.
>
> I am not sure that I'll be at the Forum during the day, but please do ping
> me for a weekend or evening hangout if you're attending. I'd love to show
> anyone who's interested around the Boston area if our schedules align.
>
> Also feel free to contact me via IRC/email/carrier pigeon with any
> questions about work in progress I had upstream.
>
> Good luck with the project, and thanks for everything!
>
> Best wishes,
> Mario Villaplana
>
> __
> 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

Re: [openstack-dev] [ironic] [stable] ironic-stable-maint update proposal

[John Villalovos]

Not sure if I get a vote but +1 for Ruby! :)

Sorry to hear about the removals :(

John

On Thu, Apr 27, 2017 at 7:21 AM, Dmitry Tantsur  wrote:

> Hi all!
>
> I'd like to propose the following changes to the ironic-stable-maint group
> [0]:
>
> 1. Add Ruby Loo (rloo) to the group. Ruby does not need introduction in
> the Ironic community, she has been with the project for really long time
> and is well known for her high-quality and thorough reviews. She has been
> pretty active on stable branches as well [1].
>
> 2. Remove Jay Faulkner (sigh..) per his request at [2].
>
> 3. Remove Devananda (sigh again..) as he's no longer active on the project
> and was removed from ironic-core several months ago [3].
>
> So for those on the team already, please reply with a +1 or -1 vote.
> I'll also need somebody to apply this change, as I don't have ACL for that.
>
> [0] https://review.openstack.org/#/admin/groups/950,members
> [1] https://review.openstack.org/#/q/project:openstack/ironic+NO
> T+branch:master+reviewer:%22Ruby+Loo+%253Cruby.loo%2540intel.com%253E%22
> [2] http://lists.openstack.org/pipermail/openstack-dev/2017-Apri
> l/115968.html
> [3] http://lists.openstack.org/pipermail/openstack-dev/2017-Febr
> uary/112442.html
>
> __
> 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

Re: [openstack-dev] [ironic] Resigning as a core reviewer

[John Villalovos]

Very sad to have you go Jay :(  Big loss for the Ironic team. Best of luck
with the future. Hope to keep chatting with you in #openstack-ironic

Thanks for all of your help with Ironic. You helped me a lot!

John

On Wed, Apr 26, 2017 at 12:42 PM, Jay Faulkner  wrote:

> Hi all,
>
>
> As most of you know, I'm no longer being paid to work on OpenStack Ironic.
> Working with you all has been an amazing part of my career, an I've learned
> more than you'll ever know. I'll still be in #openstack-ironic, willing to
> answer any questions about something I'm an expert in. However, as I won't
> be actively participating in the project, or reviewing code anymore, I'd
> like to request my core reviewer access be removed.
>
>
> Thanks for everything! I wish for nothing but the best for everyone in the
> OpenStack community who have always treated me with kindness and patience.
>
>
> Sincerely,
>
> Jay Faulkner
>
> __
> 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

Re: [openstack-dev] [ironic] New mascot design

[John Villalovos]

+1. Reminds me a lot of our current logo. I like this version the best of
the official stylized logos. Thanks.

On Fri, Mar 10, 2017 at 8:28 AM, Heidi Joy Tretheway  wrote:

> Hi Ironic team,
> Here’s an update on your project logo. Our illustrator tried to be as true
> as possible to your original, while ensuring it matched the line weight,
> color palette and style of the rest. Thanks for your patience as we worked
> on this! Feel free to direct feedback to me; we really want to get this
> right for you.
>
>
>
> __
> 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

Re: [openstack-dev] [ironic] End-of-Ocata core team updates

[John Villalovos]

+1 to both Vasyl and Mario.

Hopefully Deva will be able to come back again to Ironic in the future.

On Fri, Feb 17, 2017 at 10:42 AM, Julia Kreger 
wrote:

> Thank you Dmitry!
>
> I’m +1 to all of these actions. Vasyl and Mario will be great additions.
> As for Devananda, it saddens me but I agree and I hope to work with him
> again in the future.
>
> -Julia
>
> > On Feb 17, 2017, at 4:40 AM, Dmitry Tantsur  wrote:
> >
> > Hi all!
> >
> > I'd like to propose a few changes based on the recent contributor
> activity.
> >
> > I have two candidates that look very good and pass the formal barrier of
> 3 reviews a day on average [1].
> >
> > First, Vasyl Saienko (vsaienk0). I'm pretty confident in him, his stats
> [2] are high, he's doing a lot of extremely useful work around networking
> and CI.
> >
> > Second, Mario Villaplana (mariojv). His stats [3] are quite high too, he
> has been doing some quality reviews for critical patches in the Ocata cycle.
> >
> > Active cores and interested contributors, please respond with your +-1
> to these suggestions.
> >
> > Unfortunately, there is one removal as well. Devananda, our team leader
> for several cycles since the very beginning of the project, has not been
> active on the project for some time [4]. I propose to (hopefully temporary)
> remove him from the core team. Of course, when (look, I'm not even saying
> "if"!) he comes back to active reviewing, I suggest we fast-forward him
> back. Thanks for everything Deva, good luck with your current challenges!
> >
> > Thanks,
> > Dmitry
> >
> > [1] http://stackalytics.com/report/contribution/ironic-group/90
> > [2] http://stackalytics.com/?user_id=vsaienko=marks
> > [3] http://stackalytics.com/?user_id=mario-villaplana-j=marks
> > [4] http://stackalytics.com/?user_id=devananda=marks
> >
> > 
> __
> > 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

Re: [openstack-dev] [ironic] New mascot design

[John Villalovos]

Of the proposed logos, I do like the latest version the best. It appears
friendly and fun. So I'm +1 on it.

On Wed, Feb 1, 2017 at 12:43 PM, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com> wrote:

> Hi,
>
> +1 to Jay, the 3.0 version looks ok - it is friendly and rocking :)
>
> Cheers,
>
> Dr. Pavlo Shchelokovskyy
> Senior Software Engineer
> Mirantis Inc
> www.mirantis.com
>
> On Wed, Feb 1, 2017 at 10:38 PM, Jay Faulkner  wrote:
>
>> Of the options presented, I think the new 3.0 version most brings to mind
>> a rocking bear.  It’s still tough to be OK with a new logo, given that
>> pixie boots is beloved by our team partially because Lucas took the time to
>> make us one — but it seems like not accepting a new logo created by the
>> foundation would lead to Ironic getting less marketing and resources, so
>> I’m not keen to go down that path. With that in mind, I’m +1 to version 3.0
>> of the bear.
>>
>> -Jay
>>
>> > On Feb 1, 2017, at 12:05 PM, Heidi Joy Tretheway <
>> heidi...@openstack.org> wrote:
>> >
>> > Hi Ironic team,
>> >
>> > I’m sorry our second proposal again missed the mark. It wasn’t the
>> illustrator’s intention to mimic the Bear Surprise painting that gained
>> popularity in Russia as a meme. Our illustrator created a face-forward bear
>> with paws shaped as if it had index and ring “fingers" down, like a hand
>> gesture popular at a heavy metal concert. It was not meant to mimic the
>> painting of a side-facing bear with paws and all “fingers" up to surprise.
>> That said, once it’s seen, it’s tough to expect the community to un-see it,
>> so we’ll take another approach.
>> >
>> > The issue with your old mascot is twofold: it doesn’t fit the
>> illustration style for the entire suite of 60+ mascots, and it contains a
>> human-made element (drumsticks). As part of our overall guidelines,
>> human-made objects and symbols were not allowed, and we applied these
>> standards to all projects.
>> >
>> > Your team told us you want a heavy metal bear, so we used the Kiss
>> band-style makeup and the hand gesture to suggest metal without using an
>> instrument or symbol. We tried to mimic your original logo’s expression.
>> After releasing v1, we listened to your team’s comment that the first
>> version was too angry looking, so you’ll see a range of expressions from
>> fierce to neutral to happy.
>> >
>> >
>> > 
>> > I’d love to find a compromise with your team that will be in keeping
>> with the style of the project logo suite. I’ll watch your ML for additional
>> concerns about this proposed v3:
>> > 
>> >
>> > Our illustration team’s next step is to parse the community feedback
>> from the Ironic team (note that there is a substantial amount of
>> conflicting feedback from 21 members of your team) and determine if we have
>> majority support for a single direction.
>> >
>> > While new project logos are optional, virtually every project asked be
>> represented in our family of logos. Only logos in this new style will be
>> used on the project navigator and in other promotional ways.
>> >
>> > Feel free to join me for a quick chat tomorrow at 9:30 a.m. Pacific:
>> > Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/5038169769
>> > Or iPhone one-tap (US Toll): +16465588656,5038169769# or +14086380968,
>> 5038169769#
>> > Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US
>> Toll)
>> > Meeting ID: 503 816 9769
>> > International numbers available: https://zoom.us/zoomconference
>> ?m=E5Gcj6WHnrCsWmjQRQr7KFsXkP9nAIaP
>> >
>> >
>> >
>> >
>> >
>> > Heidi Joy Tretheway
>> > Senior Marketing Manager, OpenStack Foundation
>> > 503 816 9769 | Skype: heidi.tretheway
>> >
>> >
>> >
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.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:unsubscrib
>> e
>> 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

Re: [openstack-dev] [ironic] New mascot design

[John Villalovos]

I prefer our current homegrown logo. I wish we could just keep using that.

On Wed, Feb 1, 2017 at 9:40 AM, Jay Faulkner  wrote:

> I concur with most of the other comments on the thread. I have a strong
> preference for our existing mascot, and don’t think the new one is an
> improvement.
>
> Thanks,
> Jay
>
> > On Jan 31, 2017, at 12:49 PM, Jim Rollenhagen 
> wrote:
> >
> > Hey ironic-ers,
> >
> > The foundation has passed along a new version of our mascot (attached)
> to us, and would like your feedback on it.
> >
> > They're hoping to have all mascot-related things ready in time for the
> PTG, so please do send your thoughts quickly, if you have them. :)
> >
> > // jim
> > ___
> ___
> > 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

Re: [openstack-dev] [all][py3][swift][devstack] USE_PYTHON3 works! (well somewhat)

[John Villalovos]

On Mon, Jan 2, 2017 at 1:06 PM, Davanum Srinivas  wrote:

> Folks,
>
> Other teams:
> Please consider adding DSVM jobs with USE_PYTHON3=True for your
> projects. This will hopefully help us get to our Pike goal for Python
> 3.x [10]
>
>
As a note the variable name for DSVM jobs has been changed to:
DEVSTACK_GATE_USE_PYTHON3=True
__
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

Re: [openstack-dev] [all] Using \ for multiline statements

[John Villalovos]

On Fri, Dec 23, 2016 at 1:11 PM, Monty Taylor  wrote:

> I think this is the most important point. We have automated style tools.
> Humans should not be doing code review on code style. Humans should be
> doing code review on logic and intent and whether a design is a good
> idea or whether their colleague may have missed an error case or what
> have you.
>
> We have tools for enforcing things like tests running and code style
> conforming. Let the tools do their job so the humans can focus on being
> human.
>
>
I'll somewhat disagree. If code style impacts code readability then I think
it is useful to review that. I don't want unreadable code to land because
the automated style checkers don't complain. Basically use common sense.

This passes code style checks:
if 'f'\
'e'\
'e'\
'l'\
'i'\
'n'\
'g'\
== \
'feeling':
print("hello")
__
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

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

[John Villalovos]

We believe the error is caused by a bad wheel for lxml 3.7.0 that was
pushed today to PyPi

Thanks to everyone working together on this issue in #openstack-infra !

A patch is proposed to blacklist that release and we are testing it now.
__
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-dev] [all] Intermittent gate failures across multiple projects

[John Villalovos]

Gate jobs seem to be intermittently broken across all of OpenStack.

Bug filed:
https://bugs.launchpad.net/openstack-gate/+bug/1652186

They appear during the keystone phase of devstack and look like this:

http://logs.openstack.org/39/414339/2/check/gate-tempest-
dsvm-ironic-ipa-partition-pxe_snmp-tinyipa-ubuntu-xenial-nv/
1d5e63d/logs/devstacklog.txt.gz#_2016-12-22_22_25_10_787

2016-12-22 22:25:08.607

| 2016-12-22 22:25:08.606 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created domain
default2016-12-22 22:25:08.637

| 2016-12-22 22:25:08.637 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created project
admin2016-12-22 22:25:08.657

| 2016-12-22 22:25:08.656 31714 DEBUG passlib.registry
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] registered
'sha512_crypt' handler:  register_crypt_handler
/usr/local/lib/python2.7/dist-packages/passlib/registry.py:2942016-12-22
22:25:08.684 

| 2016-12-22 22:25:08.684 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created user
admin2016-12-22 22:25:08.700

| 2016-12-22 22:25:08.699 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created role
admin2016-12-22 22:25:08.714

| 2016-12-22 22:25:08.714 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Granted admin on
admin to user admin.2016-12-22 22:25:08.731

| 2016-12-22 22:25:08.730 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created region
RegionOne2016-12-22 22:25:08.763

| 2016-12-22 22:25:08.763 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created admin
endpoint http://15.184.67.84/identity_admin2016-12-22 22:25:08.775

| 2016-12-22 22:25:08.774 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created internal
endpoint http://15.184.67.84/identity2016-12-22 22:25:08.787

| 2016-12-22 22:25:08.787 31714 INFO keystone.cmd.cli
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created public
endpoint http://15.184.67.84/identity2016-12-22 22:25:08.793

| 2016-12-22 22:25:08.793 31714 INFO keystone.assignment.core
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Creating the
default role 9fe2ff9ee4384b1894a90878d3e92bab because it does not
exist.2016-12-22 22:25:08.923

| + ./stack.sh:main:1065 :
create_keystone_accounts2016-12-22 22:25:08.927

| + lib/keystone:create_keystone_accounts:371 :   local
admin_project2016-12-22 22:25:08.931

Re: [openstack-dev] [all] Using \ for multiline statements

[John Villalovos]

I for one do not like \ continuation lines. I think they look ugly and
prefer using () and formatting code to avoid them.

On Thu, Dec 22, 2016 at 3:28 PM, Sean McGinnis 
wrote:

> Looking for input from everyone, particularly those with more in-depth
> Python knowledge.
>
> In Cinder for some time we have been trying to enforce using () or
> reformatting code to avoid using \ to have statements span multiple
> lines. I'm not sure when this actually started, but I think it may
> be one of those things where someone got a review disagreement, so
> then that person started downvoting on it, then the next person, etc.
>
> I've seen some allusions to the use of \ having some issues, but I
> can't find any concrete examples where this can cause problems. I do
> seem to remember trying to write a hacking check or a code parsing
> tool to do something that choked on these, but it's long enough ago
> that I don't remember the details, and I could very well be mixing
> that up with something else.
>
> So my question is - is there a technical reason for enforcing this
> rule, or is this just a bad downvote that's gotten out of control?
>
> Thanks!
>
> Sean
>
>
> __
> 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

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

[John Villalovos]

On Mon, Dec 12, 2016 at 2:45 AM, Thierry Carrez 
wrote:

> There was a thread in the past discussing renaming -alt to -2 but it
> concluded that it was not worth the hassle (losing the 489 people
> hanging there).
>

I was thinking maybe #openstack-meeting-alt could be dedicated in the
future to "ALTernating" meetings. Just a random thought :)
__
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

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

[John Villalovos]

On Wed, Dec 7, 2016 at 5:29 AM, Thierry Carrez 
wrote:

> So how about:
> - we enable an #openstack-meeting-5 to instantly relieve scheduling
> pressure
>

Any reason it isn't #openstack-meeting-2 ?

The -2 channel is owned by openstackinfra.
__
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

Re: [openstack-dev] [Openstack] [all][infra][requirements] Odd cases in requirements?

[John Villalovos]

Ah, thanks a lot for that info :) I think that is what I need.

On Wed, Nov 9, 2016 at 7:36 AM, Jeremy Stanley <fu...@yuggoth.org> wrote:

> On 2016-11-09 07:19:04 -0800 (-0800), John Villalovos wrote:
> > Sort of related, what is the plan for supporting requirements which are
> > Python 3 only packages?
> >
> > In particular the package: mypy-lang
> > https://pypi.python.org/pypi/mypy-lang
> [...]
>
> If you only want mypy-lang installed when the interpreter is Python
> 3.3 or later (what their trove classifiers seem to imply for
> supported versions), use the following environment marker syntax:
>
> mypy-lang;python_version>='3.3'
>
> (see dnspython3 in global-requirements.txt for a similar example)
>
> https://pip.pypa.io/en/stable/reference/pip_install/#
> requirement-specifiers
> https://www.python.org/dev/peps/pep-0426/#environment-markers
> --
> Jeremy Stanley
>
> __
> 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

Re: [openstack-dev] [Openstack] [all][infra][requirements] Odd cases in requirements?

[John Villalovos]

Sort of related, what is the plan for supporting requirements which are
Python 3 only packages?

In particular the package: mypy-lang
https://pypi.python.org/pypi/mypy-lang

I was considering adding some type hints to the ironic-lib project in the
future. But it needs to run the mypy program to do the type hint checking
and it is a Python 3 only program. Current workaround is to put it into
tox.ini.

Thanks,
John
__
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-dev] [Ironic][QA] Static type hint checking

[John Villalovos]

I have added an RFE about starting work on adding static type hint checking
to Ironic:
https://bugs.launchpad.net/ironic-lib/+bug/1633756

And a starting patch to openstack/ironic-lib:
https://review.openstack.org/#/c/386892/

A patch to add the 'typing' package to openstack/requirements/global-
requirements.txt:
https://review.openstack.org/386944

Issues:
I tried adding the 'mypy-lang' package to global-requirements but the tool
'generate-constraints' does not handle "Python 3 only" packages. Or I don't
know how to make it handle "Python 3 only" packages.

So I added the dep for 'mypy-lang' as a local dep requirement in the
tox.ini file.

Very interested to hear if anybody else has started working on static type
hint checking in their projects.

Thanks,
John
__
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

Re: [openstack-dev] [neutron] clean up your git checkout!

[John Villalovos]

On Fri, Sep 30, 2016 at 12:12 PM, Amrith Kumar  wrote:
> :)
>
> Clark ...
>
> If I git clone a brand new repository and edit the tox.ini with the proposed 
> change:
>
>> > PYTHONDONTWRITEBYTECODE = 1
>
> I had assumed that no .pyc's would get created.

That is correct for 'tox' runs. Doing a: tox -e py27
Should not generate any *.pyc files.

Feel free to post a paste.openstack.org of your modified tox.ini file.

__
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

Re: [openstack-dev] [neutron] clean up your git checkout!

[John Villalovos]

Projects may want to add to their tox.ini something like this:

https://github.com/openstack/ironic/blob/c445c19285c2f3ee6a099f9f7473dd6fe087116b/tox.ini#L10

Basically add:
PYTHONDONTWRITEBYTECODE = 1

On Fri, Sep 30, 2016 at 7:20 AM, Ihar Hrachyshka  wrote:
> Michał Dulko  wrote:
>
>> On 09/30/2016 04:06 PM, Ihar Hrachyshka wrote:
>>>
>>> Ihar Hrachyshka  wrote:
>>>
 Hi all,

 today we landed https://review.openstack.org/#/c/269658/ (huge!) that
 removed neutron/objects/network/ directory and replaced it with
 neutron/objects/network.py file. Though it makes python that sees old
 .pyc files sad:

 Failed to import test module: neutron.tests.unit.objects.test_network
 Traceback (most recent call last):
   File

 "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 456, in _find_test_path
 module = self._get_module_from_name(name)
   File

 "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name
 __import__(name)
   File "neutron/tests/unit/objects/test_network.py", line 23, in
 
 obj_test_base.BaseObjectIfaceTestCase):
   File "neutron/tests/unit/objects/test_network.py", line 24, in
 NetworkPortSecurityIfaceObjTestCase
 _test_class = network.NetworkPortSecurity
 AttributeError: 'module' object has no attribute 'NetworkPortSecurity'
 The test run didn't actually run any tests

 Please run git clean -f -x in your checkout to remove all .pyc files.
 This should solve any import issues you may experience due to the new
 patch.
>>>
>>>
>>> I hear that -f -x is not enough. Please add -d too:
>>>
>>> $ git clean -f -x -d
>>>
>>> Ihar
>>
>>
>> Isn't ``find . -name \*.pyc -delete`` enough? That way you won't remove
>> anything else. In Cinder we have that in tox.ini [1].
>>
>> [1]
>>
>> https://github.com/openstack/cinder/blob/792108f771607b75a25e9c4cfaaa26e5039d1748/tox.ini#L21-L21
>
>
> Actually not, because empty directories won’t be cleaned by the command you
> suggested.
>
> Ihar
>
>
> __
> 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

Re: [openstack-dev] Spain Visa for Indian contributors

[John Villalovos]

On that page they seem to list a contact email:

eventv...@openstack.org

Hopefully they can help with the issue.

John

On Wed, Sep 14, 2016 at 9:24 PM, Kekane, Abhishek
<abhishek.kek...@nttdata.com> wrote:
> Hi John,
>
> I have read the information given at 
> https://www.openstack.org/summit/barcelona-2016/travel/#visa
> and got the invitation letter but it's in English language. Problem is that 
> Visa centers in India are demanding this invitation letter in English as well 
> as Spanish language.
>
> Thank you,
>
> Abhishek Kekane
>
> -Original Message-
> From: John Villalovos [mailto:openstack@sodarock.com]
> Sent: Thursday, September 15, 2016 9:45 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] Spain Visa for Indian contributors
>
> There is information on the Visa process at:
> https://www.openstack.org/summit/barcelona-2016/travel/#visa
>
> Not sure if you have already read that information.
>
> They talk about the steps needed to get an invitation letter.
>
> Good luck!
>
>
> On Wed, Sep 14, 2016 at 8:51 PM, Kekane, Abhishek 
> <abhishek.kek...@nttdata.com> wrote:
>> Hi Devs, Stackers,
>>
>>
>>
>> While applying visa from Pune (India), I came to know that Invitation
>> letter is required in Spanish language and its mandatory.
>>
>> Has anyone from India has faced similar kind of issue while applying
>> for visa?
>>
>>
>>
>> If not please let me know from which city you have applied for the Visa.
>>
>>
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Abhishek Kekane
>>
>>
>> __
>> Disclaimer: This email and any attachments are sent in strictest
>> confidence for the sole use of the addressee and may contain legally
>> privileged, confidential, and proprietary data. If you are not the
>> intended recipient, please advise the sender by replying promptly to
>> this email and then delete and destroy this email and any attachments
>> without any further use, copying or forwarding.
>>
>> __
>>  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
>
> __
> Disclaimer: This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data. If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding.
>
> __
> 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

Re: [openstack-dev] Spain Visa for Indian contributors

[John Villalovos]

There is information on the Visa process at:
https://www.openstack.org/summit/barcelona-2016/travel/#visa

Not sure if you have already read that information.

They talk about the steps needed to get an invitation letter.

Good luck!


On Wed, Sep 14, 2016 at 8:51 PM, Kekane, Abhishek
 wrote:
> Hi Devs, Stackers,
>
>
>
> While applying visa from Pune (India), I came to know that Invitation letter
> is required in Spanish language and its mandatory.
>
> Has anyone from India has faced similar kind of issue while applying  for
> visa?
>
>
>
> If not please let me know from which city you have applied for the Visa.
>
>
>
>
>
> Thank you,
>
>
>
> Abhishek Kekane
>
>
> __
> Disclaimer: This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data. If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding.
>
> __
> 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

Re: [openstack-dev] [infra] Reliable way to filter CI in gerrit spam?

[John Villalovos]

On Wed, Aug 31, 2016 at 11:58 AM, Jeremy Stanley  wrote:
> No, as I understand it, since we set capability.emailReviewers="deny
> group Third-Party CI" in the global Gerrit configuration it should
> avoid sending E-mail for any of their comments.
> https://review.openstack.org/Documentation/access-control.html#capability_emailReviewers
> I guess we should troubleshoot that.


I also see emails from at least the Cisco CI:

Cisco CI has posted comments on this change.

Change subject: Allow suppressing ramdisk logs collection
..


Patch Set 2:

Build failed. For help on isolating this failure, please contact
cisco-openstack-neutron...@cisco.com. To re-run, post a
'cisco-ironic-recheck' comment.

- tempest-dsvm-ironic-pxe_iscsi_cimc
http://192.133.158.2:8080/job/tempest-dsvm-ironic-pxe_iscsi_cimc/3269
: FAILURE in 2h 02m 36s
- tempest-dsvm-ironic-pxe_ucs
http://192.133.158.2:8080/job/tempest-dsvm-ironic-pxe_ucs/2684 :
FAILURE in 1h 55m 32s

__
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

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

[John Villalovos]

On Fri, Aug 26, 2016 at 9:48 AM, Clark Boylan  wrote:
> As someone that semi frequently has to reproduce gate results my current
> setup involves semi frequently building the infra test images locally
> using openstack-infra/project-config/tools/build-image.sh then booting
> this image on my workstation using kvm. With that I can easily run a
> devstack-gate reproduce.sh or tox -e whatever and have a high degree of
> confidence that my setup mirrors the gate's.

Nice to know about that! Thanks.

Just curious how does someone reproduce a multi-node devstack-gate
job. I have selfish reasons for wanting to know :)

__
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

Re: [openstack-dev] [all][infra] Binary Package Dependencies - not only for Python

[John Villalovos]

On Fri, Aug 12, 2016 at 10:31 AM, Andreas Jaeger  wrote:

> TL;DR: Projects can use bindep.txt to document in a programmatic way
> their binary dependencies
>
>
Maybe I missed it, but it would be nice if the documentation had some
sample commented bindep.txt files.

Thanks,
John
__
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

Re: [openstack-dev] [ironic][tests] approach to functional/integration tests

[John Villalovos]

I personally like Option #1 as an additional goal is to make it easy for
developers to also run the functional tests with 'tox -efunctional'.  And
also run the functional tests as part of a normal tox run.

On Mon, Jan 11, 2016 at 6:54 AM, Serge Kovaleff 
wrote:

> Option 3 - to concentrate on Tempest tests
> https://review.openstack.org/#/c/253982/
>
> Cheers,
> Serge Kovaleff
> http://www.mirantis.com
> cell: +38 (063) 83-155-70
>
> On Mon, Jan 11, 2016 at 4:49 PM, Serge Kovaleff 
> wrote:
>
>> Hi All,
>>
>> Last week I had a noble goal to write "one-more" functional test in
>> Ironic.
>> I did find a folder "func" but it was empty.
>>
>> Friends helped me to find a WIP patch
>> https://review.openstack.org/#/c/235612/
>>
>> and here comes the question of this email: what approach we would like to
>> implement:
>> Option 1 - write infrastructure code that starts/configure/stops the
>> services
>> Option 2 - rely on installed DevStack and run the tests over it
>>
>> Both options have their Cons and Pros. Both options are implemented
>> across the OpenStack umbrella.
>> Option 1 - Glance, Nova, the patch above
>> Option 2 - HEAT and my favorite at the moment.
>>
>> Any ideas?
>>
>> Cheers,
>> Serge Kovaleff
>> http://www.mirantis.com
>> cell: +38 (063) 83-155-70
>>
>
>
> __
> 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

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

[John Villalovos]

Me too :)

+1 for trying a virtual midcycle

On Thu, Nov 19, 2015 at 8:55 AM, Lucas Alvares Gomes 
wrote:

> Hi,
>
> > I sent a new idea to openstack-dev, and nobody has opinions? :P
> >
> > I'd like to get consensus on this soon, please do reply if you have
> > thoughts on this.
> >
>
> Sorry for the delay...
>
> Yeah, I've no problem giving this virtual midcycle idea a go, so +1
>
> __
> 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

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

[John Villalovos]

My order of preference would be:

1. Coordinated regional mid-cycles
2. Normal mid-cycle
3. Virtual mid-cycle
4. No mid-cycle

Thanks,
John

On Tue, Nov 10, 2015 at 10:45 AM, Lucas Alvares Gomes  wrote:

> Hi,
>
> In the last Ironic meeting [1] we started a discussion about whether
> we need to have a mid-cycle meeting for the Mitaka cycle or not. Some
> ideas about the format of the midcycle were presented in that
> conversation and this email is just a follow up on that conversation.
>
> The ideas presented were:
>
> 1. Normal mid-cycle
>
> Same format as the previous ones, the meetup will happen in a specific
> venue somewhere in the world.
>
> 2. Virtual mid-cycle
>
> People doing a virtual hack session on IRC / google hangout /
> others... Something like virtual sprints [2].
>
> 3. Coordinated regional mid-cycles
>
> Having more than one meetup happening in different parts of the world
> with a preferable time overlap between them so we could use video
> conference for some hours each day to sync up what was done/discussed
> on each of the meetups.
>
> 4. Not having a mid-cycle at all
>
>
> So, what people think about it? Should we have a mid-cycle for the
> Mitaka release or not? If so, what format should we use?
>
> Other ideas are also welcome.
>
> [1]
> http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-09-17.00.log.html
> [2] https://wiki.openstack.org/wiki/VirtualSprints
>
> Cheers,
> Lucas
>
> __
> 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-dev] [Ironic] Weekly Ironic QA/testing/3rd party CI meeting

[John Villalovos]

We have just started a weekly meeting to discuss Ironic QA, testing, and
3rd party CI

More info here:
https://wiki.openstack.org/wiki/Meetings/Ironic-QA

Weekly meeting on Wednesdays at 1700 UTC on #openstack-meeting
__
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

Re: [openstack-dev] [Ironic] OpenStack Ironic dinner

[John Villalovos]

Did we come to a decision on what day for the Ironic dinner?

On Mon, Oct 12, 2015 at 11:07 AM, Lucas Alvares Gomes  wrote:

> Since many of us is going to be in Tokyo for the summit, who's interested
> in an OpenStack Ironic dinner?
>
> Let's first decide what day of the week suits most people, so please vote
> here: http://doodle.com/poll/2nqbemmrdd9a5ypd
>
> if you have any food requirements or restrictions please add it to the
> "comments" section in the doodle pool.
>
> Cheers,
> Lucas
>
> __
> 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

Re: [openstack-dev] [ironic] Nominating two new core reviewers

[John Villalovos]

I also would like to say thank you for the nomination and support. I am
honored and humbled to be chosen. Thank you to all of you for this vote of
confidence and I will do my best to maintain it.

And congrats to Vlad, it is well deserved :)

John

On Sun, Oct 11, 2015 at 11:27 AM, Vladyslav Drok <vd...@mirantis.com> wrote:

> Thank you all for the nomination and support! It is a big responsibility
> to be a member of the core team, and I'll do my best to justify your trust.
>
> Vlad
> On Oct 11, 2015 20:33, "Jim Rollenhagen" <j...@jimrollenhagen.com> wrote:
>
>> On Thu, Oct 08, 2015 at 02:47:01PM -0700, Jim Rollenhagen wrote:
>> > Hi all,
>> >
>> > I've been thinking a lot about Ironic's core reviewer team and how we
>> might
>> > make it better.
>> >
>> > I'd like to grow the team more through trust and mentoring. We should be
>> > able to promote someone to core based on a good knowledge of *some* of
>> > the code base, and trust them not to +2 things they don't know about.
>> I'd
>> > also like to build a culture of mentoring non-cores on how to review, in
>> > preparation for adding them to the team. Through these pieces, I'm
>> hoping
>> > we can have a few rounds of core additions this cycle.
>> >
>> > With that said...
>> >
>> > I'd like to nominate Vladyslav Drok (vdrok) for the core team. His
>> reviews
>> > have been super high quality, and the quantity is ever-increasing. He's
>> > also started helping out with some smaller efforts (full tempest, for
>> > example), and I'd love to see that continue with larger efforts.
>> >
>> > I'd also like to nominate John Villalovos (jlvillal). John has been
>> > reviewing a ton of code and making a real effort to learn everything,
>> > and keep track of everything going on in the project.
>> >
>> > Ironic cores, please reply with your vote; provided feedback is
>> positive,
>> > I'd like to make this official next week sometime. Thanks!
>>
>> It appears all cores have responded positively; I've added both
>> Vladyslav and John to the ironic-core group in Gerrit.
>>
>> Note that your browser cache may prevent you from seeing the +2 option.
>> If this happens, just do a hard refresh (ctrl-shift-r) and it should
>> work itself out.
>>
>> Congrats to both of you, and welcome to the team! :)
>>
>> // jim
>>
>> __
>> 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

Re: [openstack-dev] [Ironic] Stepping down from IPA core

[John Villalovos]

Sorry to see you go Josh :( Always great working with you.

Best of luck with the new job!

John

On Mon, Sep 21, 2015 at 8:49 AM, Josh Gachnang 
wrote:

> Hey y'all, it's with a heavy heart I have to announce I'll be stepping
> down from the IPA core team on Thurs, 9/24. I'm leaving Rackspace for a
> healthcare startup (Triggr Health) and won't have the time to dedicate to
> being an effective OpenStack reviewer.
>
> Ever since the OnMetal team proposed IPA all the way back in the
> Icehouse midcycle, this community has been welcoming, helpful, and all
> around great. You've all helped me grow as a developer with your in depth
> and patient reviews, for which I am eternally grateful. I'm really sad I
> won't get to see everyone in Tokyo.
>
> I'll still be on IRC after leaving, so feel free to ping me for any reason
> :)
>
> - JoshNang
>
> __
> 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

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

[John Villalovos]

On Sat, May 9, 2015 at 3:10 AM, John Garbutt j...@johngarbutt.com wrote:
 On 6 May 2015 at 19:04, John Villalovos openstack@sodarock.com wrote:
 JohnG,

 I work on Ironic and would be willing to be a cross project liaison for Nova
 and Ironic.  I would just need a little info on what to do from the Nova
 side.  Meetings to attend, web pages to monitor, etc...

 I assume I would start with this page:
 https://bugs.launchpad.net/nova/+bugs?field.tag=ironic

 And try to work with the Ironic and Nova teams on getting bugs resolved.

 I would appreciate any other info and suggestions to help improve the
 process.

 Thank you for stepping up to help us here.

 I have added your name on this list:
 https://wiki.openstack.org/wiki/Nova#People
 (if you can please add your IRC handle for me, that would be awesome)

 In terms of whats required, thats really up to what works for you.

 The top things that come to mind:
 * Raise ironic questions to nova in nova-meetings (and maybe v.v.)
 * For ironic features that need exposing in Nova, track those
 * Help triage Nova's ironic bugs into Nova bugs and Ironic bugs
 * Try to find folks to fix important ironic bugs

 But fundamentally, lets just see what works, and evolve the role to
 match what works for you.

 I hope that helps.

JohnG,

Thanks for the info.

I have added my IRC nick to:
https://wiki.openstack.org/wiki/Nova#People

I have added the Nova meetings to my calendar.  So I will start attending them.

Thanks,
John





 Thanks,
 John

 John

 On Wed, May 6, 2015 at 2:55 AM, John Garbutt j...@johngarbutt.com wrote:

 On 6 May 2015 at 09:39, Lucas Alvares Gomes lucasago...@gmail.com wrote:
  Hi
 
  I noticed last night that there are 23 bugs currently filed in nova
  tagged as ironic related. Whilst some of those are scheduler issues, a
  lot of them seem like things in the ironic driver itself.
 
  Does the ironic team have someone assigned to work on these bugs and
  generally keep an eye on their driver in nova? How do we get these
  bugs resolved?
 
 
  Thanks for this call out. I don't think we have anyone specifically
  assigned to keep an eye on the Ironic
  Nova driver, we would look at it from time to time or when someone ask
  us to in the Ironic channel/ML/etc...
  But that said, I think we need to pay more attention to the bugs in
  Nova.
 
  I've added one item about it to be discussed in the next Ironic
  meeting[1]. And in the meantime, I will take a
  look at some of the bugs myself.
 
  [1]
  https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting

 Thanks to you both for raising this and pushing on this.

 Maybe we can get a named cross project liaison to bridge the Ironic
 and Nova meetings. We are working on building a similar pattern for
 Neutron. It doesn't necessarily mean attending every nova-meeting,
 just someone to act as an explicit bridge between our two projects?

 I am open to whatever works though, just hoping we can be more
 proactive about issues and dependencies that pop up.

 Thanks,
 John

 __
 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

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

[John Villalovos]

JohnG,

I work on Ironic and would be willing to be a cross project liaison for
Nova and Ironic.  I would just need a little info on what to do from the
Nova side.  Meetings to attend, web pages to monitor, etc...

I assume I would start with this page:
https://bugs.launchpad.net/nova/+bugs?field.tag=ironic

And try to work with the Ironic and Nova teams on getting bugs resolved.

I would appreciate any other info and suggestions to help improve the
process.

John

On Wed, May 6, 2015 at 2:55 AM, John Garbutt j...@johngarbutt.com wrote:

 On 6 May 2015 at 09:39, Lucas Alvares Gomes lucasago...@gmail.com wrote:
  Hi
 
  I noticed last night that there are 23 bugs currently filed in nova
  tagged as ironic related. Whilst some of those are scheduler issues, a
  lot of them seem like things in the ironic driver itself.
 
  Does the ironic team have someone assigned to work on these bugs and
  generally keep an eye on their driver in nova? How do we get these
  bugs resolved?
 
 
  Thanks for this call out. I don't think we have anyone specifically
  assigned to keep an eye on the Ironic
  Nova driver, we would look at it from time to time or when someone ask
  us to in the Ironic channel/ML/etc...
  But that said, I think we need to pay more attention to the bugs in Nova.
 
  I've added one item about it to be discussed in the next Ironic
  meeting[1]. And in the meantime, I will take a
  look at some of the bugs myself.
 
  [1]
 https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting

 Thanks to you both for raising this and pushing on this.

 Maybe we can get a named cross project liaison to bridge the Ironic
 and Nova meetings. We are working on building a similar pattern for
 Neutron. It doesn't necessarily mean attending every nova-meeting,
 just someone to act as an explicit bridge between our two projects?

 I am open to whatever works though, just hoping we can be more
 proactive about issues and dependencies that pop up.

 Thanks,
 John

 __
 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

Re: [openstack-dev] [Ironic] *ED states strike back

[John Villalovos]

Ruby,

What you say makes sense to me.  On keeping things consistent.  So sounds
good to me to always use them and not have them be optional.

John

On Thu, Feb 19, 2015 at 9:32 AM, Ruby Loo rlooya...@gmail.com wrote:

 I think that if there is a use case for an *ED state, then we should have
 it. And if we have one *ED state, I think it makes sense (and is
 consistent) to have them for all the active states.

 If we have *ED states, I would prefer that we add them in when the active
 state is added. So add stateING, stateED, stateFAIL. If a particular
 driver has nothing it wants to do in an *ED state, it can cause a
 transition from the *ED state to the passive/stable state.

 I don't want the *ED states to be optional because that puts the onus on
 the developer that needs the *ED state, to add it in (assuming they are
 aware that this is possible) and put in whatever plumbing might be needed.
 Which may mean that they'd have to modify code in another driver, that
 didn't need *ED in the first place. (If an *ED state is added, all drivers
 using that active state should handle the *ED state too because it is in
 the state machine and I'd rather not complicate things by having state-ING
 - state-ED - stable-state and state-ING - stable-state.

 --ruby

 __
 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

Re: [openstack-dev] [Ironic] *ED states strike back

[John Villalovos]

Can the *ED states be optional?  If a state would be a NO-OP, then don't
use it.  But if it is useful then use it.

It seems ugly to me to just have two 'change state' calls to move it
through the *ED state.

If an *ED state needs to be added later I think it could be added without
too much difficulty and the code will be cleaner without having 'no-op'
states.

WDYT?

John

On Thu, Feb 19, 2015 at 7:25 AM, Dmitry Tantsur dtant...@redhat.com wrote:

 Hi everyone!

 On one of our meetings [1] we agreed on keeping *ED states (DELETED,
 INSPECTED, CLEANED, etc) as no-ops for now. Since then, however, the
 inspection patch [2] got several comments from cores requesting removal of
 INSPECTED state. That was done by Nisha.

 Today we decided to approve [2] and bring the discussion here. We can
 always add the state later, and blocking this patch again would be a bit
 unfair IMO. We'll create a follow-up to [2] if we decide that we need
 INSPECTED state.

 So now, are we keeping/adding these *ED states to our state machine? I
 personally agree with what was discussed on the meeting, namely:
 1. Keep *ED states
 2. Make them no-ops, so that code that does INSPECTING - MANAGEABLE right
 now will do INSPECTING - INSPECTED - MANAGEABLE instead.

 Having INSPECTED is also useful for distinguish between OOB case (when
 inspect_hardware returns after having everything done) and in-band case
 (when inspect_hardware returns after initializing inspection). We could use
 return value of inspect_hardware being INSPECTING or INSPECTED.

 WDYT?

 Dmitry.

 [1] http://eavesdrop.openstack.org/meetings/ironic/2015/
 ironic.2015-02-09-17.00.log.html starting 17:47
 [2] https://review.openstack.org/#/c/147857/

 __
 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

Re: [openstack-dev] Unable to sign ICLA (OpenStack Individual Contributor License Agreement)

[John Villalovos]

Thanks.  I will try these solutions.  I think it is because I have not yet
joined the foundation.

John

On Tue, Feb 3, 2015 at 9:40 AM, Abhishek L abhishek.lekshma...@gmail.com
wrote:

 Hi

 On Tue, Feb 3, 2015 at 10:47 PM, John Villalovos
 openstack@sodarock.com wrote:
 
  I have attempted over the last two days to sign the ICLA (
  OpenStack Individual Contributor License Agreement)
 
  Each time I do it I get the following error:
 
  Code Review - Error
  Server Error
  Cannot store contact information

 Have you already created a profile with same email id on openstack
 https://www.openstack.org/profile/
 IIRC I faced the same issue when I registered, however the problems
 seemed to have gone away after creating a profile in openstack

 
 
  Any ideas who I can contact to fix this?
 
  Thanks,
  John
 

 Regards
 Abhishek

 __
 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-dev] Unable to sign ICLA (OpenStack Individual Contributor License Agreement)

[John Villalovos]

I have attempted over the last two days to sign the ICLA (
OpenStack Individual Contributor License Agreement)

Each time I do it I get the following error:

Code Review - Error
Server Error
Cannot store contact information


Any ideas who I can contact to fix this?

Thanks,
John
__
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