Re: [openstack-dev] [all] Reminder: User Committee Nominations Start Today!

[Melvin Hillsman]

For our non-US community members, a gentle reminder.

On Mon, Jul 31, 2017 at 10:12 AM, Melvin Hillsman 
wrote:

> Hey everyone,
>
> Just a friendly reminder that the UC elections are now open for candidates
> to be peer- or self-nominated. In order to do so please send an email to
> the user-commit...@lists.openstack.org mailing list and include the
> phrase "UC Candidacy" in the subject line. More details can be found at the
> following - https://governance.openstack.org/uc/reference/uc-election-
> aug2017.html#candidates
>
> --
> Kind regards,
>
> OpenStack User Committee
> (Jon, Shilla, Shamail, Edgar, Melvin)
>



-- 
Kind regards,

OpenStack User Committee
(Jon, Shilla, Shamail, Edgar, Melvin)
__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Tony Breeds]

On Mon, Jul 31, 2017 at 09:09:52PM -0500, Matt Riedemann wrote:
> On 7/31/2017 5:21 PM, Tony Breeds wrote:
> > We need a +1 from the release team (are they okay to accept a late
> > release of glance_store); and a +1 from glance (are they okay to do said
> > release)
> 
> Glance doesn't actually need this minimum version bump for os-brick, the fix
> is for some attached volume extend stuff, which isn't related to Glance, so
> does having the minimum bump in glance* matter?

Maybe it doesn't I can't think of a scenario where someone will end up
with 1.15.1 if the mix glance and nova.

If glance_store doesn't take the bump of os-brick before we release
pike then they're going to be faced with breaking the "we don't bump
minimums on stable branches" or opting out of requirements management for
that branch aren't they?

Yours Tony.


signature.asc
Description: PGP signature
__
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] [Elections] Candidacy for I18n PTL (Queens)

[Frank Kloeker]

Good morning!

Today I would like to announce my candidacy as I18n PTL in Queens cycle.

I've been in the OpenStack Community since 2015, active as a translator 
in the
German team. I participated in my first OpenStack Summit in Tokyo and 
met the
I18n team for the first time at the Design Summit. It was an exciting 
moment to

meet people from all over the world working on the same thing.
It is not just translations, but working with different cultures, views 
and ...

time zones. These are the magical dimensions and challenges.
After Tokyo we had virtual midcycle sprint to develop the translation 
check

site, one of the tools to help translators in their work.
I met more people during Barcelona Summit and sank deeper and deeper 
into the
work of OpenStack and I18n. In Boston we had our own session to show the 
work of
the I18n team. We prepared a workshop also which was not so successful, 
but the

preparation was great and we can repeat it at any time.

At this point I would like to thank Ianychoi for his excellent work in 
the past
as PTL. He is tireless, full of energy, and brought I18n far forward. He 
was for
me in the last weeks a kind of mentor to learn all the things related to 
I18n

and PTL.  Nevertheless, I still need support from the entire team to
successfully manage this task.

What goals have I set for myself for Queens:
1. Completion of the translation check site. I have been involved in 
this

project since 2015 and now it has to be finished :-)
2. Automate all the things. We have some manual work in I18n and our 
tools that

are to automate to make the work easier.
3. Aquire more people to the team. We have great teams that do a lot. 
But we
also get more work through translate new OpenStack projects or the User 
Survey.


I hope I have given a good overview. Contact me directly if you have any
questions or requests. On good cooperation in a new cycle of OpenStack!

kind regards

Frank

Email: eu...@arcor.de
IRC: eumel8
Twitter: eumel_8

OpenStack Profile:
https://www.openstack.org/community/members/profile/45058/frank-kloeker


__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Walter Boring]

Do it +1

On Mon, Jul 31, 2017 at 7:37 AM, Sean McGinnis 
wrote:

> I am requesting a library release of os-brick during the feature freeze
> in order to fix an issue with the recently landed online volume extend
> feature across Nova and Cinder.
>
> Patches have landed in both projects to add this feature. It wasn't until
> later that Matt was able to get tempest tests in that found an issue with
> some of the logic in the os-brick library. That has now been fixed in the
> stable/pike branch in os-brick with this patch:
>
> https://review.openstack.org/#/c/489227/
>
> We can get a new library release out as soon as the freeze is over, but
> due to the fact that we do not raise global requirements for stable
> branches after release, there could be some deployments that would still
> use the old ("broken") lib. We would need to get this release out before
> the final pike branching of Cinder and Nova to be able to raise G-R to
> make sure the new release is used with this fix.
>
> I see this change as a low risk for other regression, and it would allow
> us to not ship a broken feature.
>
> 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] [tripleo] Proposing Saravanan KR core

[Saravanan KR]

Thank you for your support.

Regards,
Saravanan KR

On Mon, Jul 31, 2017 at 7:19 PM, Emilien Macchi  wrote:
> On Fri, Jul 21, 2017 at 8:01 AM, Emilien Macchi  wrote:
>> Saravanan KR has shown an high level of expertise in some areas of
>> TripleO, and also increased his involvement over the last months:
>> - Major contributor in DPDK integration
>> - Derived parameter works
>> - and a lot of other things like improving UX and enabling new
>> features to improve performances and networking configurations.
>>
>> I would like to propose Saravanan part of TripleO core and we expect
>> his particular focus on t-h-t, os-net-config and tripleoclient for now
>> but we hope to extend it later.
>>
>> As usual, we'll vote :-)
>
> Votes were positive, it's done now.
> Saravanan has now +2 and we expect him to use it on THT, os-net-config
> and tripleoclient for now.
>
> Thanks,
> --
> Emilien Macchi
>
> __
> 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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Matthew Thode]

On 17-07-31 21:09:52, Matt Riedemann wrote:
> On 7/31/2017 5:21 PM, Tony Breeds wrote:
> > We need a +1 from the release team (are they okay to accept a late
> > release of glance_store); and a +1 from glance (are they okay to do said
> > release)
> 
> Glance doesn't actually need this minimum version bump for os-brick, the 
> fix is for some attached volume extend stuff, which isn't related to 
> Glance, so does having the minimum bump in glance* matter?
> 
> -- 
> 
> Thanks,
> 
> Matt
> 
> __
> 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

For co-installability between projects it'd be good to be in sync.  The
same could be said to many of the bumps that go through the requirements
project.  One of the things we've been working on is divergent
requirements, where the goal is to keep making sure all projects test
against one set of upper-constraints, but allow each project to manage
their requirements outside of that.

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Matt Riedemann]

On 7/31/2017 5:21 PM, Tony Breeds wrote:

We need a +1 from the release team (are they okay to accept a late
release of glance_store); and a +1 from glance (are they okay to do said
release)


Glance doesn't actually need this minimum version bump for os-brick, the 
fix is for some attached volume extend stuff, which isn't related to 
Glance, so does having the minimum bump in glance* matter?


--

Thanks,

Matt

__
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] [oslo][barbican][sahara] start RPC service before launcher wait?

[Adam Spiers]

Ken Giusti  wrote:

On Mon, Jul 31, 2017 at 10:01 AM, Adam Spiers  wrote:

I recently discovered a bug where barbican-worker would hang on
shutdown if queue.asynchronous_workers was changed from 1 to 2:

   https://bugs.launchpad.net/barbican/+bug/1705543

resulting in a warning like this:

   WARNING oslo_messaging.server [-] Possible hang: stop is waiting for
start to complete

I found a similar bug in Sahara:

   https://bugs.launchpad.net/sahara/+bug/1546119

where the fix was to call start() on the RPC service before making the
launcher wait() on it, so I ported the fix to Barbican, and it seems
to work fine:

   https://review.openstack.org/#/c/485755

I noticed that both projects use ProcessLauncher; barbican uses
oslo_service.service.launch() which has:

   if workers is None or workers == 1:
   launcher = ServiceLauncher(conf, restart_method=restart_method)
   else:
   launcher = ProcessLauncher(conf, restart_method=restart_method)

However, I'm not an expert in oslo.service or oslo.messaging, and one
of Barbican's core reviewers (thanks Kaitlin!) noted that not many
other projects start the task before calling wait() on the launcher,
so I thought I'd check here whether that is the correct fix, or
whether there's something else odd going on.

Any oslo gurus able to shed light on this?


As far as an oslo.messaging server is concerned, the order of operations is:

server.start()
# do stuff until ready to stop the server...
server.stop()
server.wait()

The final wait blocks until all requests that are in progress when stop()
is called finish and cleanup.


Thanks - that makes sense.  So the question is, why would
barbican-worker only hang on shutdown when there are multiple workers?
Maybe the real bug is somewhere in oslo_service.service.ProcessLauncher
and it's not calling start() correctly?

__
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] [tricircle]

[joehuang]

Hello, Meher,

For the second node, the devstack configuration file local.conf should be 
configured carefully, especially for the keystone part(sample file 
https://github.com/openstack/tricircle/blob/master/devstack/local.conf.node_2.sample):

HOST_IP=10.250.201.25
REGION_NAME=RegionTwo
KEYSTONE_REGION_NAME=RegionOne
SERVICE_HOST=$HOST_IP
KEYSTONE_SERVICE_HOST=10.250.201.24
KEYSTONE_AUTH_HOST=10.250.201.24

HOST_IP is the second node's IP, KEYSTONE_SERVICE_HOST/KEYSTONE_AUTH_HOST 
should be configured with the first node's IP.

Best Regards
Chaoyi Huang (joehuang)

From: meher.h...@orange.com [meher.h...@orange.com]
Sent: 31 July 2017 21:31
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

Hello everybody,

I just installed Tricirle on a single node. Now I'm trying to install it on two 
nodes (two VMs), everything was fine with the first node, Tricirle is well 
installed, on the second node, at the end of the script install it stops on An 
error "Failed to discover available versions when contacting 
http://192.168.123.129/identity. Attempting to parse version from URL.”

So it seems that there is a connection problem with the keystone service on the 
first machine, as far as the connectivity between the 2 nodes is concerned, it 
is perfect.

I am sending you this mail to find out if anyone can help me on this. I thank 
you in advance!

Regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank 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

Re: [openstack-dev] [release]need help for python-tricircleclient

[joehuang]

Hello,

Very sorry for the deadline missing even if it's few hours, and won't let it 
happen next time.

I was waiting for one patch about pagination support in tricircle ( not 
python-tricircleclient). If pagination
for resource routing and job have not been supported well in tricircle, it's 
not good to publish these features
in python-tricircleclient:

python-tricircleclient will list resource routing and job from Tricircle Admin 
API, if there are huge amount of
resource routing and job records, without pagination support, a query will 
easily lead to the db server keep in busy status: the
list operation will make db server eat too much resources, even make the db 
server stopping response for other request.

Because the patch is almost done, so extra few hours were paid to this patch, 
so that python-tricircleclient can include these
useful features in pike, otherwise only pod management feature can be included 
in python-tricircleclient.

Best Regards
Chaoyi Huang (joehuang)


From: Thierry Carrez [thie...@openstack.org]
Sent: 31 July 2017 21:04
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [release]need help for python-tricircleclient

joehuang wrote:
> The patch [1] is to add a tag for python-tricircleclient after new
> features were added to it since last release. But unfortunately, a
> branch called "stable/pike" was there in Apr., and lead to the patch can
> not pass the gate test.

This release request missed the deadline for client libraries releases
(if only by a few hours), so we already created the stable/pike branch
from the last available Pike release (0.1.1 from April 2017).

Given (1) that the deadline was not missed by much, (2) that the last
available release was quite old, and (3) that no other project depends
on python-tricircleclient, damage would be limited in cutting 0.2.0 now
and recreating stable/pike from it. We'll coordinate with infra to make
it happen.

Next time, please don't miss the deadline and create additional work for
the release team !

--
Thierry Carrez (ttx)

__
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] [all][Elections] Nominations for OpenStack PTLs (Project Team Leads) are now open

[Kendall Nelson]

Hello Everyone :)

Nominations for OpenStack PTLs (Program Team Leads) are now open and will
remain open until August 9th, 2017 23:45 UTC.

All candidates must be submitted as a text file to the openstack/election
repository as explained at
http://governance.openstack.org/election/#how-to-submit-your-candidacy
Please make sure to follow the new candidacy file naming convention:
$cycle_name/$project_name/$ircname.txt.

In order to be an eligible candidate (and be allowed to vote) in a given
PTL election, you need to have contributed an accepted patch to one of the
corresponding program's projects[0] during the Ocata-Pike timeframe
(September, 2016 23:59 UTC to August 3rd, 2017 23:59 UTC).

Additional information about the nomination process can be found here:
https://governance.openstack.org/election/

As the election officials approve candidates, they will be listed here:
https://governance.openstack.org/election/#queens-ptl-candidates

The electorate is requested to confirm their email address in gerrit,
review.openstack.org > Settings > Contact Information >  Preferred Email,
prior to August 5th, 2017 23:59 UTC so that the emailed ballots are mailed
to the correct email address.

Happy running,

-Kendall Nelson(diablo_rojo)

[0]
http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
__
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] [sahara] New core reviewers

[Telles Nobrega]

Hi all, last week I proposed adding Jeremy, Luigi and Evgeny to the sahara
core team.

I'm happy to annouce that I just added all three to the core team.

Thanks to all on the great work you have been doing and now there will be
more.

Thanks and congractulations!!!
-- 

TELLES NOBREGA

SOFTWARE ENGINEER

Red Hat I 

tenob...@redhat.com

TRIED. TESTED. TRUSTED. 
__
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] [neutron] FFE for midonet v2 plugin removal

[Takashi Yamamoto]

hi,

I'm not sure if changes like this requires an FFE, but just in case.
I'd like to request an FFE for midonet v2 plugin removal.

- patches are ready for review: https://review.openstack.org/#/c/486790/
- https://bugs.launchpad.net/networking-midonet/
- this is a removal of an already-deprecated plugin
- the replacement code (midonet drivers for ml2) covers the most or
probably all functionalities provided by the plugin being removed
- the change is local to networking-midonet

__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Tony Breeds]

On Mon, Jul 31, 2017 at 03:00:16PM -0500, Sean McGinnis wrote:
> > I am requesting a library release of os-brick during the feature freeze
> > in order to fix an issue with the recently landed online volume extend
> > feature across Nova and Cinder.
> > 
> 
> New os-brick 1.15.2 release has been requested here:
> 
> https://review.openstack.org/489370

From a requirements POV I'm fine with that.  It affects:

Package  : os-brick [os-brick>=1.15.1] (used by 8 projects)
Also affects : 8 projects
openstack/cinder  [tc:approved-release]
openstack/compute-hyperv  []
openstack/freezer []
openstack/fuxi[]
openstack/glance_store[]
openstack/nova[tc:approved-release]
openstack/nova-lxd[]
openstack/python-brick-cinderclient-ext   []

The one that is *most* problematic is glance_store  We already have an
FFE for glance_store it's probably ok.

We need a +1 from the release team (are they okay to accept a late
release of glance_store); and a +1 from glance (are they okay to do said
release)

Yours Tony.


signature.asc
Description: PGP signature
__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Sean McGinnis]

> I am requesting a library release of os-brick during the feature freeze
> in order to fix an issue with the recently landed online volume extend
> feature across Nova and Cinder.
> 

New os-brick 1.15.2 release has been requested here:

https://review.openstack.org/489370

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

Re: [openstack-dev] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Ivan Kolodyazhny]

Sounds reasonable for me too.


Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/

On Mon, Jul 31, 2017 at 5:40 PM, Davanum Srinivas  wrote:

> I'd support this Sean. +1
>
> Thanks,
> Dims
>
> On Mon, Jul 31, 2017 at 10:37 AM, Sean McGinnis 
> wrote:
> > I am requesting a library release of os-brick during the feature freeze
> > in order to fix an issue with the recently landed online volume extend
> > feature across Nova and Cinder.
> >
> > Patches have landed in both projects to add this feature. It wasn't until
> > later that Matt was able to get tempest tests in that found an issue with
> > some of the logic in the os-brick library. That has now been fixed in the
> > stable/pike branch in os-brick with this patch:
> >
> > https://review.openstack.org/#/c/489227/
> >
> > We can get a new library release out as soon as the freeze is over, but
> > due to the fact that we do not raise global requirements for stable
> > branches after release, there could be some deployments that would still
> > use the old ("broken") lib. We would need to get this release out before
> > the final pike branching of Cinder and Nova to be able to raise G-R to
> > make sure the new release is used with this fix.
> >
> > I see this change as a low risk for other regression, and it would allow
> > us to not ship a broken feature.
> >
> > 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
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> 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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Matthew Thode]

Yep, please submit the review refrencing this thread, lgtm.

On 17-07-31 10:40:10, Davanum Srinivas wrote:
> I'd support this Sean. +1
> 
> Thanks,
> Dims
> 
> On Mon, Jul 31, 2017 at 10:37 AM, Sean McGinnis  wrote:
> > I am requesting a library release of os-brick during the feature freeze
> > in order to fix an issue with the recently landed online volume extend
> > feature across Nova and Cinder.
> >
> > Patches have landed in both projects to add this feature. It wasn't until
> > later that Matt was able to get tempest tests in that found an issue with
> > some of the logic in the os-brick library. That has now been fixed in the
> > stable/pike branch in os-brick with this patch:
> >
> > https://review.openstack.org/#/c/489227/
> >
> > We can get a new library release out as soon as the freeze is over, but
> > due to the fact that we do not raise global requirements for stable
> > branches after release, there could be some deployments that would still
> > use the old ("broken") lib. We would need to get this release out before
> > the final pike branching of Cinder and Nova to be able to raise G-R to
> > make sure the new release is used with this fix.
> >
> > I see this change as a low risk for other regression, and it would allow
> > us to not ship a broken feature.
> >
> > 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
> 
> 
> 
> -- 
> Davanum Srinivas :: https://twitter.com/dims
> 
> __
> 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

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
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] [os-upstream-institute] Meeting reminder

[Ildiko Vancsa]

Hi Training Team,

This is a friendly reminder that we are having our meeting in less than an hour 
(2000 UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó



__
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] [cinder] String freeze exception request

[Jay S Bryant]

Lucian,

I talked to Sean about this and we agreed the change was small enough to 
allow.  So, it has been accepted.


Thanks!

Jay



On 7/31/2017 12:08 PM, Lucian Petrut wrote:

Hi,

I'd like to request a string freeze exception for a small SMB driver
change: https://review.openstack.org/#/c/484423/1

We'd need it in order to remain backwards compatible with some old
driver specific config options, which are validated by the driver. The
exception messages include the config option names, which now have to
be updated.

Thanks,
Lucian Petrut
__
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] this week's priorities and subteam reports

[Yeleswarapu, Ramamani]

Hi,

We are glad to present this week's priorities and subteam report for Ironic. As 
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)


1. Docs due to the docs re-org - See 
http://lists.openstack.org/pipermail/openstack-dev/2017-July/119221.html
1.1. Ironic - 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:doc-migration
1.2. ironic-inspector - 
https://review.openstack.org/#/q/status:open+project:openstack/ironic-inspector+branch:master+topic:doc-migration
1.3. bifrost: 
https://review.openstack.org/#/q/status:open+project:openstack/bifrost+branch:master+topic:doc-migration
2. Booting from volume:
2.1. Functional tests: https://review.openstack.org/#/c/473717/
2.2. api-ref for volumes API: https://review.openstack.org/#/c/478798/
3. Rolling upgrades:
3.1.  'Add new dbsync command with first online data migration': 
https://review.openstack.org/#/c/408556/
4. Physnet awareness:
4.1. Refactoring: 
https://review.openstack.org/#/q/topic:refactor-vif-attach-mixin
5. IPA API versioning:
5.1. IPA part: https://review.openstack.org/#/c/364834/


Bugs (dtantsur, vdrok, TheJulia)

- Stats (diff between 24 Jul 2017 and 31 Jul 2017)
- Ironic: 257 bugs (-2) + 259 wishlist items (-1). 30 new (-1), 207 in progress 
(-4), 0 critical, 30 high (-2) and 31 incomplete
- Inspector: 13 bugs (-1) + 28 wishlist items. 3 new (+2), 10 in progress (-2), 
0 critical, 2 high (-2) and 3 incomplete
- Nova bugs with Ironic tag: 18 (+1). 0 new, 0 critical, 1 high (+1)
- added https://bugs.launchpad.net/nova/+bug/1706772

Essential Priorities


CI refactoring and missing test coverage

- not considered a priority, it's a 'do it always' thing
- Standalone CI tests (vsaienk0)
- next patch to be reviewed, needed for 3rd party CI: 
https://review.openstack.org/#/c/429770/
- Missing test coverage (all)
- portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476
- local boot with partition images: TODO 
https://bugs.launchpad.net/ironic/+bug/1531149
- adoption: https://review.openstack.org/#/c/344975/
- should probably be changed to use standalone tests
- root device hints: TODO

Generic boot-from-volume (TheJulia, dtantsur)
-
- specs and blueprints:
- 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/volume-connection-information.html
- code: https://review.openstack.org/#/q/topic:bug/1526231
- 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/boot-from-volume-reference-drivers.html
- code: https://review.openstack.org/#/q/topic:bug/1559691
- https://blueprints.launchpad.net/nova/+spec/ironic-boot-from-volume
- code: 
https://review.openstack.org/#/q/topic:bp/ironic-boot-from-volume
- status as of 31 Jul 2017:
- Patch/note tracking etherpad: https://etherpad.openstack.org/p/Ironic-BFV
Ironic Patches:
https://review.openstack.org/#/c/466333/ - Devstack changes or Boot 
from Volume - MERGED
https://review.openstack.org/#/c/484032/ -- Create boot.ipxe upon 
start-up - MERGED
https://review.openstack.org/#/c/472740/ - Tempest test scenario 
for BFV - MERGED
as soon as this merges, we need to promote the CI job to 
non-voting check
https://review.openstack.org/#/c/486853/ - minor nits - APPROVED
https://review.openstack.org/#/c/479326/ - BFV deploy follow-up - 
Requires revision
Nova:
https://review.openstack.org/#/c/215385 - Ironic: Support boot from 
cinder volume - MERGED
https://review.openstack.org/#/c/468353 - Ironic: Get IP address 
for volume connector - --NOT REQUIRED FOR PIKE-- - Is a follow-up to the first 
nova patch to allow
Project-Config:
https://review.openstack.org/#/c/480332 - Add experimental gate job 
for BFV MERGED

Rolling upgrades and grenade-partial (rloo, jlvillal)
-
- spec approved; code patches: 
https://review.openstack.org/#/q/topic:bug/1526283
- status as of most recent weekly meeting:
- last big code patch, ready for reviews:
- 'Add new dbsync command with first online data migration': 
https://review.openstack.org/#/c/408556/
- this is the last critical code patch for this feature
- to address restarting services after unpinning, spec ready for reviews: 
'SIGHUP restarts services with updated configs': 
https://review.openstack.org/474309
- Testing work: done as per spec, but rloo wants to ask vasyl whether we 
can improve. grenade test will do upgrade so we have old API sending requests 
to old and/or new conductor, but rloo 

Re: [openstack-dev] [oslo][barbican][sahara] start RPC service before launcher wait?

[Ken Giusti]

On Mon, Jul 31, 2017 at 10:01 AM, Adam Spiers  wrote:

> Hi all,
>
> I recently discovered a bug where barbican-worker would hang on
> shutdown if queue.asynchronous_workers was changed from 1 to 2:
>
>https://bugs.launchpad.net/barbican/+bug/1705543
>
> resulting in a warning like this:
>
>WARNING oslo_messaging.server [-] Possible hang: stop is waiting for
> start to complete
>
> I found a similar bug in Sahara:
>
>https://bugs.launchpad.net/sahara/+bug/1546119
>
> where the fix was to call start() on the RPC service before making the
> launcher wait() on it, so I ported the fix to Barbican, and it seems
> to work fine:
>
>https://review.openstack.org/#/c/485755
>
> I noticed that both projects use ProcessLauncher; barbican uses
> oslo_service.service.launch() which has:
>
>if workers is None or workers == 1:
>launcher = ServiceLauncher(conf, restart_method=restart_method)
>else:
>launcher = ProcessLauncher(conf, restart_method=restart_method)
>
> However, I'm not an expert in oslo.service or oslo.messaging, and one
> of Barbican's core reviewers (thanks Kaitlin!) noted that not many
> other projects start the task before calling wait() on the launcher,
> so I thought I'd check here whether that is the correct fix, or
> whether there's something else odd going on.
>
> Any oslo gurus able to shed light on this?
>
> Thanks!
> Adam
>
> __
> 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
>


As far as an oslo.messaging server is concerned, the order of operations is:

server.start()
# do stuff until ready to stop the server...
server.stop()
server.wait()

The final wait blocks until all requests that are in progress when stop()
is called finish and cleanup.

-K


-- 
Ken Giusti  (kgiu...@gmail.com)
__
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-Ansible] Not running for Queens PTL

[Amy Marrich]

Andy,

You'll be missed you did a great job(as did Kevin and Jesse before you)!
Glad you'll be around still as you'd definitely be missed.

Amy (spotz)

On Mon, Jul 31, 2017 at 4:48 AM, Andy McCrae  wrote:

> Following on from last week's meeting - I've had 2 cycles as PTL for OSA,
> which has been a really great experience - we've achieved a lot and built
> on the strong base we had, which I'm really proud of. I strongly believe
> that inviting a fresh perspective and new ideas as PTL is a winning
> strategy - it's served us well so far, and in line with previous PTLs I
> won't be standing for a 3rd cycle.
>
> Looking forward to assisting the next PTL, and helping to continue to
> mature and improve the project!
>
> Thanks!
> Andy
>
> __
> 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-Ansible] Not running for Queens PTL

[Carter, Kevin]

Andy,

The last couple of cycles have been great and we appreciate all you've done
for the community.

--

Kevin Carter
IRC: Cloudnull

On Mon, Jul 31, 2017 at 4:48 AM, Andy McCrae  wrote:

> Following on from last week's meeting - I've had 2 cycles as PTL for OSA,
> which has been a really great experience - we've achieved a lot and built
> on the strong base we had, which I'm really proud of. I strongly believe
> that inviting a fresh perspective and new ideas as PTL is a winning
> strategy - it's served us well so far, and in line with previous PTLs I
> won't be standing for a 3rd cycle.
>
> Looking forward to assisting the next PTL, and helping to continue to
> mature and improve the project!
>
> Thanks!
> Andy
>
> __
> 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] [cinder] String freeze exception request

[Lucian Petrut]

Hi,

I'd like to request a string freeze exception for a small SMB driver
change: https://review.openstack.org/#/c/484423/1

We'd need it in order to remain backwards compatible with some old
driver specific config options, which are validated by the driver. The
exception messages include the config option names, which now have to
be updated.

Thanks,
Lucian Petrut
__
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] [nova][qa][placement] more gabbi with tempest

[Chris Dent]

Over the weekend I spent some time working on my experiments using
gabbi[1] with tempest. I had previously got gabbi-tempest[2]
working, based on some work by sileht, but it was only addressing a
single service at a time. For the sake of placement-related tests,
it's useful to be able to talk to the compute api and the placement
api at the same time. Now it does.

I've just now used it to confirm a placement bug [3] with this gabbi
file:

https://github.com/cdent/gabbi-tempest/blob/master/gabbi_tempest/tests/scenario/gabbits/multi/base.yaml

It's still rough around the edges, but it has proven useful and
should be doubly so in the face of multiple nodes. Especially useful
to me is how visible it makes the various APIs and the interactions
thereof. Writing the tests without a client is _very_ informative.

If you'd like to help make it better, find me or just go ahead and
make a pull request. At some point it may be interesting to explore
the option of "put a gabbit in dir X" and tempest will run it for
you.

[1] https://gabbi.readthedocs.io/en/latest/
[2] https://github.com/cdent/gabbi-tempest
[3] https://bugs.launchpad.net/nova/+bug/1707252

--
Chris Dent  ┬──┬◡ﾉ(° -°ﾉ)   https://anticdent.org/
freenode: cdent tw: @anticdent__
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] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

[Bogdan Dobrelya]

On 31.07.2017 15:51, Emilien Macchi wrote:
> On Fri, Jul 21, 2017 at 7:55 AM, Emilien Macchi  wrote:
>> Hi,
>>
>> Bogdan (bogdando on IRC) has been very active in Containerization of
>> TripleO and his quality of review has increased over time.
>> I would like to give him core permissions on container work in TripleO.
>> Any feedback is welcome as usual, we'll vote as a team.
> 
> Votes were positive, it's done now.
> Bogdan has now +2 and we expect him to use it on patches related to
> container work.
> 
> Thanks,
> 

Thank you for your votes!

-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] Make sure your project's links are all added to the docs repo

[Chason]

Hello everyone,

We have already started to migrated docs for some time. Currently, it looks 
like going well. Thanks to all of us taking part in this work!

There are still some essential work require project developers to confirm 
whether it has been done. we have a few projects [1] who have landed docs but 
not updated the flags in the manuals repo. we strongly encourage the project to 
complete it by themselves. Please make sure the links are all added to the docs 
repo. To start doing it on your own, following the instructions in our 
contributor guide [2].

Thanks for your attention！:)

Cheers,

Chason


[1] http://paste.openstack.org/show/616995/ 

[2] https://docs.openstack.org/contributor-guide/index.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-dev] Make sure your project's links are all added to the docs repo

[Chason]

Hello everyone,

We have already started to migrated docs for some time. Currently, it looks 
like going well. Thanks to all of us taking part in this work!

There are still some essential work require project developers to confirm 
whether it has been done. we have a few projects who have landed docs but not 
updated the flags in the manuals repo. 


[1] http://paste.openstack.org/show/616995/ 
__
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] [puppet] Meeting tomorrow Aug 1, 2017 @ 1500 UTC

[Alex Schultz]

Just as a reminder, we do have a meeting tomorrow.  If you would like
to talk about anything, please make sure it's on the agenda[0].

Thanks,
-Alex

[0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170801

__
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] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

[Doug Hellmann]

Excerpts from Doug Hellmann's message of 2017-07-31 10:02:19 -0400:
> Excerpts from Doug Hellmann's message of 2017-07-27 19:10:32 -0400:
> > Excerpts from Doug Hellmann's message of 2017-07-27 19:05:16 -0400:
> > > Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +:
> > > > On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote:
> > > > [...]
> > > > > Are we over-emphasizing the scale of the discovery problem?
> > > > > 
> > > > > When I search for how to install a package on Ubuntu (or Red Hat
> > > > > or Debian for that matter), I find all sorts of references all over
> > > > > the web (including on the sites for those distros) and I have to
> > > > > sift through it all to find right command or package name to use
> > > > > for my version.  Usually the easiest way to do that is to put the
> > > > > version in the search query.
> > > > > 
> > > > > Are our users incapable of finding the right version of a document
> > > > > if we clearly mark the version to which each document applies? Every
> > > > > URL now has a release series name or version tag in the path. The
> > > > > docs theme inserts the version number into every page as well. Is
> > > > > that sufficient to help a reader understand what version the info
> > > > > they're view is for?
> > > > > 
> > > > > That's not to say we shouldn't do some work to make newer docs easy
> > > > > to find. If we can modify the sitemap to make them appear earlier
> > > > > in search results, that's good. The docs theme allows a project to
> > > > > include links to several older versions to switch between them,
> > > > > too, so users who land on the "wrong" version can switch. We could
> > > > > update that to include branches as well as tags, so that someone
> > > > > can easily move to the series they need without knowing the version
> > > > > number.
> > > > [...]
> > > > 
> > > > The biggest liability is people not realizing there are multiple
> > > > "versions" of OpenStack finding an old install doc and using it
> > > > because they don't know it's out of date, then seeking support
> > > > upstream or just generally contributing to the number of deployments
> > > > unnecessarily stuck on obsolete software. The current solution of
> > > > not publishing installation guides for EOL releases seems like a
> > > > good enough compromise there to me.
> > > 
> > > That content will now live in the project trees. Perhaps part of marking
> > > branches in those repos EOL needs to include deleting the install tree
> > > from the docs? Now that the docs are in a standard location, that could
> > > be part of an EOL script (although it means 2 phases, since we have to
> > > land the patch and let the docs rebuild before we remove the branch).
> > > 
> > > We could also update the openstack-manuals tree to not publish links
> > > to the install guides (either removing the page or replacing it
> > > with a placeholder that explains they should be trying to use a
> > > newer version).
> > > 
> > > Doug
> > > 
> > 
> > Today we're publishing series-specific (e.g., newton) and
> > version-specific (e.g., 10.0.0) docs. I wonder if we should stop
> > publishing docs when we tag repositories, and just stick to the
> > series? There's no way to go back and update those version-specific
> > builds after the fact, so we can't remove the installation guides
> > and we can't rebuild them easily if there are security issues with
> > the content.
> > 
> > Doug
> > 
> 
> I've proposed https://review.openstack.org/489231 to update
> project-config to stop publishing docs when we tag releases.
> 
> Doug
> 

And here's the theme change to show series names instead of version
numbers:

https://review.openstack.org/489252

__
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] [glance] priorities for this week (07/31 - 08/03)

[Brian Rosmaita]

Congratulations for getting P-3 tagged, and version 2.8.0 of the
glanceclient released!

As you know, we have one FFE for Pike, namely Erno's proposal to add
"copy-from" to the new image import process.  Erno is headed out for a
well-deserved vacation in a few days, so the priority for this week is
to review quickly any patches he gets up around copy-from.

Other than that, your usual dutiful attention to current patches and
bugfixes is appreciated.

Also, if you'd like to attend the PTG but aren't sure about funding,
the travel grant program is open until August 6.  Details are at the
bottom of the PTG planning etherpad:
https://etherpad.openstack.org/p/glance-queens-ptg-planning

Have a good week!
brian

__
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] Reminder: User Committee Nominations Start Today!

[Melvin Hillsman]

Hey everyone,

Just a friendly reminder that the UC elections are now open for candidates
to be peer- or self-nominated. In order to do so please send an email to
the user-commit...@lists.openstack.org mailing list and include the phrase
"UC Candidacy" in the subject line. More details can be found at the
following -
https://governance.openstack.org/uc/reference/uc-election-aug2017.html#candidates

-- 
Kind regards,

OpenStack User Committee
(Jon, Shilla, Shamail, Edgar, Melvin)
__
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] [glance] Pike Feature Freeze Exception

[Brian Rosmaita]

Hello Glancers,

As you are aware, the Feature Freeze happened at the time of P-3
tagging.  As discussed at the Glance weekly meeting on 27 July 2017,
the Glance team has decided to recognize exactly one FFE, namely,
Erno's request to add a "copy-from" capability to the Pike image
import functionality.  Given Erno's vacation schedule, this will have
to land within the next day or two if it's going to land at all, so if
it does land, we'll have plenty of time to test and make sure the
feature is stable.

cheers,
brian

__
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] [tripleo] pike-3 released - now focusing on pike-rc1

[Emilien Macchi]

On Mon, Jul 31, 2017 at 7:26 AM, Emilien Macchi  wrote:
[...]

> We also released pike milestone 3 for all other TripleO projects.

I forgot to share some numbers about Pike 3:

22 blueprints were implemented and 173 bugs fixed.

Good work everyone!
-- 
Emilien Macchi

__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Davanum Srinivas]

I'd support this Sean. +1

Thanks,
Dims

On Mon, Jul 31, 2017 at 10:37 AM, Sean McGinnis  wrote:
> I am requesting a library release of os-brick during the feature freeze
> in order to fix an issue with the recently landed online volume extend
> feature across Nova and Cinder.
>
> Patches have landed in both projects to add this feature. It wasn't until
> later that Matt was able to get tempest tests in that found an issue with
> some of the logic in the os-brick library. That has now been fixed in the
> stable/pike branch in os-brick with this patch:
>
> https://review.openstack.org/#/c/489227/
>
> We can get a new library release out as soon as the freeze is over, but
> due to the fact that we do not raise global requirements for stable
> branches after release, there could be some deployments that would still
> use the old ("broken") lib. We would need to get this release out before
> the final pike branching of Cinder and Nova to be able to raise G-R to
> make sure the new release is used with this fix.
>
> I see this change as a low risk for other regression, and it would allow
> us to not ship a broken feature.
>
> 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



-- 
Davanum Srinivas :: https://twitter.com/dims

__
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] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

[Sean McGinnis]

I am requesting a library release of os-brick during the feature freeze
in order to fix an issue with the recently landed online volume extend
feature across Nova and Cinder.

Patches have landed in both projects to add this feature. It wasn't until
later that Matt was able to get tempest tests in that found an issue with
some of the logic in the os-brick library. That has now been fixed in the
stable/pike branch in os-brick with this patch:

https://review.openstack.org/#/c/489227/

We can get a new library release out as soon as the freeze is over, but
due to the fact that we do not raise global requirements for stable
branches after release, there could be some deployments that would still
use the old ("broken") lib. We would need to get this release out before
the final pike branching of Cinder and Nova to be able to raise G-R to
make sure the new release is used with this fix.

I see this change as a low risk for other regression, and it would allow
us to not ship a broken feature.

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-dev] [tripleo] pike-3 released - now focusing on pike-rc1

[Emilien Macchi]

Folks,

Here's a short term agenda for action items in TripleO team:

## Last week
We released python-tripleoclient and stable/pike will be created
for this project.
If you're working on a bug that is candidate for backport, please tag
it "pike-backport-potential".
Priority has to be critical or high to be backported.
We also released pike milestone 3 for all other TripleO projects.
From now


## This week until August 28th
Preparing RC & final releases.
Feature & CI freeze just started.
During this time, folks should focus on upgrades from Ocata to Pike,
fixing bugs [1].
Please do the FFE (including CI changes) requests on openstack-dev [tripleo].

Please let us know any concern or feedback, it's always welcome!

[1] https://launchpad.net/tripleo/+milestone/pike-rc1

Thanks,
-- 
Emilien Macchi

__
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] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

[Doug Hellmann]

Excerpts from Doug Hellmann's message of 2017-07-27 19:10:32 -0400:
> Excerpts from Doug Hellmann's message of 2017-07-27 19:05:16 -0400:
> > Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +:
> > > On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote:
> > > [...]
> > > > Are we over-emphasizing the scale of the discovery problem?
> > > > 
> > > > When I search for how to install a package on Ubuntu (or Red Hat
> > > > or Debian for that matter), I find all sorts of references all over
> > > > the web (including on the sites for those distros) and I have to
> > > > sift through it all to find right command or package name to use
> > > > for my version.  Usually the easiest way to do that is to put the
> > > > version in the search query.
> > > > 
> > > > Are our users incapable of finding the right version of a document
> > > > if we clearly mark the version to which each document applies? Every
> > > > URL now has a release series name or version tag in the path. The
> > > > docs theme inserts the version number into every page as well. Is
> > > > that sufficient to help a reader understand what version the info
> > > > they're view is for?
> > > > 
> > > > That's not to say we shouldn't do some work to make newer docs easy
> > > > to find. If we can modify the sitemap to make them appear earlier
> > > > in search results, that's good. The docs theme allows a project to
> > > > include links to several older versions to switch between them,
> > > > too, so users who land on the "wrong" version can switch. We could
> > > > update that to include branches as well as tags, so that someone
> > > > can easily move to the series they need without knowing the version
> > > > number.
> > > [...]
> > > 
> > > The biggest liability is people not realizing there are multiple
> > > "versions" of OpenStack finding an old install doc and using it
> > > because they don't know it's out of date, then seeking support
> > > upstream or just generally contributing to the number of deployments
> > > unnecessarily stuck on obsolete software. The current solution of
> > > not publishing installation guides for EOL releases seems like a
> > > good enough compromise there to me.
> > 
> > That content will now live in the project trees. Perhaps part of marking
> > branches in those repos EOL needs to include deleting the install tree
> > from the docs? Now that the docs are in a standard location, that could
> > be part of an EOL script (although it means 2 phases, since we have to
> > land the patch and let the docs rebuild before we remove the branch).
> > 
> > We could also update the openstack-manuals tree to not publish links
> > to the install guides (either removing the page or replacing it
> > with a placeholder that explains they should be trying to use a
> > newer version).
> > 
> > Doug
> > 
> 
> Today we're publishing series-specific (e.g., newton) and
> version-specific (e.g., 10.0.0) docs. I wonder if we should stop
> publishing docs when we tag repositories, and just stick to the
> series? There's no way to go back and update those version-specific
> builds after the fact, so we can't remove the installation guides
> and we can't rebuild them easily if there are security issues with
> the content.
> 
> Doug
> 

I've proposed https://review.openstack.org/489231 to update
project-config to stop publishing docs when we tag releases.

Doug

__
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] [oslo][barbican][sahara] start RPC service before launcher wait?

[Adam Spiers]

Hi all,

I recently discovered a bug where barbican-worker would hang on
shutdown if queue.asynchronous_workers was changed from 1 to 2:

   https://bugs.launchpad.net/barbican/+bug/1705543

resulting in a warning like this:

   WARNING oslo_messaging.server [-] Possible hang: stop is waiting for start 
to complete

I found a similar bug in Sahara:

   https://bugs.launchpad.net/sahara/+bug/1546119

where the fix was to call start() on the RPC service before making the
launcher wait() on it, so I ported the fix to Barbican, and it seems
to work fine:

   https://review.openstack.org/#/c/485755

I noticed that both projects use ProcessLauncher; barbican uses
oslo_service.service.launch() which has:

   if workers is None or workers == 1:
   launcher = ServiceLauncher(conf, restart_method=restart_method)
   else:
   launcher = ProcessLauncher(conf, restart_method=restart_method)

However, I'm not an expert in oslo.service or oslo.messaging, and one
of Barbican's core reviewers (thanks Kaitlin!) noted that not many
other projects start the task before calling wait() on the launcher,
so I thought I'd check here whether that is the correct fix, or
whether there's something else odd going on.

Any oslo gurus able to shed light on this?

Thanks!
Adam

__
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] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

[Emilien Macchi]

On Fri, Jul 21, 2017 at 7:55 AM, Emilien Macchi  wrote:
> Hi,
>
> Bogdan (bogdando on IRC) has been very active in Containerization of
> TripleO and his quality of review has increased over time.
> I would like to give him core permissions on container work in TripleO.
> Any feedback is welcome as usual, we'll vote as a team.

Votes were positive, it's done now.
Bogdan has now +2 and we expect him to use it on patches related to
container work.

Thanks,
-- 
Emilien Macchi

__
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] [tripleo] Proposing Saravanan KR core

[Emilien Macchi]

On Fri, Jul 21, 2017 at 8:01 AM, Emilien Macchi  wrote:
> Saravanan KR has shown an high level of expertise in some areas of
> TripleO, and also increased his involvement over the last months:
> - Major contributor in DPDK integration
> - Derived parameter works
> - and a lot of other things like improving UX and enabling new
> features to improve performances and networking configurations.
>
> I would like to propose Saravanan part of TripleO core and we expect
> his particular focus on t-h-t, os-net-config and tripleoclient for now
> but we hope to extend it later.
>
> As usual, we'll vote :-)

Votes were positive, it's done now.
Saravanan has now +2 and we expect him to use it on THT, os-net-config
and tripleoclient for now.

Thanks,
-- 
Emilien Macchi

__
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][python-ironicclient][keystoneauth] Getting rid of a custom HTTPClient implementation

[Pavlo Shchelokovskyy]

Hi Vlad,

On Fri, Jul 21, 2017 at 9:09 PM, Vladyslav Drok  wrote:

> Greetings!
>
> I have a patch [0] to deprecate the custom HTTPClient implementation that
> we have in python-ironicclient. Currently it is used when the 'ironic'
> command is issued in a standalone mode, that is, with '--ironic-url' and
> '--os-auth-token' parameters,
>

recently released keystoneauth 3.1.0 has a new 'none' auth plugin that can
be used for standalone mode together with endpoint_override Adapter option
instead of 'admin_token' auth plugin [1]. Maybe that would allow you to
simplify the code a bit. Note that the bump to ironicclient reguirements re
keystoneauth is not merged yet [2].

[1]
https://git.openstack.org/cgit/openstack/keystoneauth/tree/keystoneauth1/noauth.py
[2] https://review.openstack.org/#/c/488117/


> or when a client is instantiated through the following module [1] directly
> without passing the session object, or even directly calling HTTPClient
> constructor at [2]. In other cases, keystoneauth's SessionClient derivative
> object is used. [0] will basically substitute the HTTPClient with the
> SessionClient (by using the 'admin_token' auth plugin). It seems like a
> breaking change, as most likely some HTTP error codes and exceptions thrown
> may be different, so I think we'll need the major client library version
> bump. We'll also make it clear in the docs that the only "true" way for
> instantiating the client is through 'get_client' method in [3].
>
> After that, we'll need to remove the HTTPClient class completely, and here
> a question is, whether we should have another major version bump? Or can we
> remove it right away, and single major version bump should be enough? (as
> the HTTPClient defined in [2] was not something we advertised as a part of
> our public python API)
>

There are actually more reasons for a major version  bump - we've reached
feature parity of our OSC plugin with 'ironic' CLI and should start to
phase the latter out (and drop OSC from hard client requirements).
So I'd vote for las minor version release with many deprecations warnings,
and clean up HTTPClient and officially deprecate 'ironic' CLI in the next
release that would be a major version bump.


> Any suggestions welcome :)
>
> -Vlad
>
> [0] https://review.openstack.org/359061
> [1] https://github.com/openstack/python-ironicclient/
> blob/master/ironicclient/v1/client.py
> [2] https://github.com/openstack/python-ironicclient/
> blob/master/ironicclient/common/http.py
> [3] https://github.com/openstack/python-ironicclient/
> blob/master/ironicclient/client.py
>
> __
> 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
>
>

Cheers,
-- 
Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com
__
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] [tricircle]

[meher.hihi]

Hello everybody,

I just installed Tricirle on a single node. Now I'm trying to install it on two 
nodes (two VMs), everything was fine with the first node, Tricirle is well 
installed, on the second node, at the end of the script install it stops on An 
error "Failed to discover available versions when contacting 
http://192.168.123.129/identity. Attempting to parse version from URL."

So it seems that there is a connection problem with the keystone service on the 
first machine, as far as the connectivity between the 2 nodes is concerned, it 
is perfect.

I am sending you this mail to find out if anyone can help me on this. I thank 
you in advance!

Regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank 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

Re: [openstack-dev] [release] nominating Sean McGinnis for releases-core

[Sean McGinnis]

> 
> As all of the feedback has been positive, I went ahead and added Sean
> to the releases-core group in gerrit today.
> 
> Doug
> 

Thank you Doug and team. I will do my best to help in whatever way I can.

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

Re: [openstack-dev] [release]need help for python-tricircleclient

[Thierry Carrez]

joehuang wrote:
> The patch [1] is to add a tag for python-tricircleclient after new
> features were added to it since last release. But unfortunately, a
> branch called "stable/pike" was there in Apr., and lead to the patch can
> not pass the gate test.

This release request missed the deadline for client libraries releases
(if only by a few hours), so we already created the stable/pike branch
from the last available Pike release (0.1.1 from April 2017).

Given (1) that the deadline was not missed by much, (2) that the last
available release was quite old, and (3) that no other project depends
on python-tricircleclient, damage would be limited in cutting 0.2.0 now
and recreating stable/pike from it. We'll coordinate with infra to make
it happen.

Next time, please don't miss the deadline and create additional work for
the release team !

-- 
Thierry Carrez (ttx)

__
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-Infra] Announcing Gertty 1.5.0

[Flavio Percoco]

On 30/07/17 08:08 -0700, James E. Blair wrote:

Thanks to the following people whose changes are included in this
release:

 Jim Rollenhagen
 Kevin Benton
 Masayuki Igawa
 Matthew Thode


Thank you all! <3 Gertty
Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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-Ansible] Not running for Queens PTL

[Major Hayden]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/31/2017 04:48 AM, Andy McCrae wrote:
> Following on from last week's meeting - I've had 2 cycles as PTL for OSA, 
> which has been a really great experience - we've achieved a lot and built on 
> the strong base we had, which I'm really proud of. I strongly believe that 
> inviting a fresh perspective and new ideas as PTL is a winning strategy - 
> it's served us well so far, and in line with previous PTLs I won't be 
> standing for a 3rd cycle.
> 
> Looking forward to assisting the next PTL, and helping to continue to mature 
> and improve the project!

We're so thankful that you've put up with us for these past two cycles! :)

You've been a beacon for quality within the project and you've carefully 
fostered a ton of new development within OpenStack-Ansible.  Thanks for your 
efforts!

- --
Major Hayden
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEG/mSZJWWADNpjCUrc3BR4MEBH7EFAll/ITQACgkQc3BR4MEB
H7FWYg//UEAtlNPu9puvbi9P2rR46Yy9DlKYN7Xs/YJOjEXFRh5cLAHNIJ8OJIB9
f3WcQV8kL7WgXBaMoMFP3dR5ciNxD8MUYJtu4JecyRVOkI14HhVxuphKpiv0EXeW
N6eIO8k3GBRO5XjjhMJ8HqCyj2Ijg3vRtpK/SCMgXBV7UmJ/hXcSWRzpHgjsbe39
kvyNrxwJhSBmiBBPWfVefy59dQDxoQMhn13rsmz9WgB7DsioLpo59FC8WQOHB3EG
MF7NOesHfRyAWeQuRsmicueCsXgkeN24oea3Ymxe0i7UQXW73Db2UoyF3qKlwg6Z
nkzbbm1QkzKfOrGdzunl+XCtekUF16epdxFzP00i4KyNmbjKWfkTf1P5PyU82f6I
X/c89Wq0HmKbRjzzLKHrXACjdkB3hskiNQRSRVCHf+01uPiDNwFFBdGFU+Q0Pl3x
/k2+/NygkGsil919abt5SRyx8xnUxfZIwA+8GrrfbwavrB46uWZfWcGssqFl6QXB
dwf9e9w0oDAM7QdBO0BpHOMi4X7ZC4qmv3DVW3pmYujMpRbD/tMwsmca2XV/Bodm
yHofdDT4tJx663pIoX3AFjOsrBCDFunEoI48v1EOkeyG6CDwkZydrjWbc75SpBvP
WTzSftscID2rUwd6XMZpQyLf1JQQHy2mv7uqUy4Sg0d8oiLhXDE=
=iyd7
-END PGP SIGNATURE-

__
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][ptl][stable][release] stable/pike branches created for most libraries

[Doug Hellmann]

Excerpts from Dmitry Tantsur's message of 2017-07-29 20:06:18 +0200:
> On 07/28/2017 11:13 PM, Doug Hellmann wrote:
> > As Thierry mentioned in his countdown email today, the release team has
> > now created the stable branches for most deliverables with type
> > "library".
> > 
> > We have 3 exceptions:
> > 
> > 1. python-neutronclient had a late release, so I will be branching it
> > shortly.
> > 2. python-barbicanclient was skipped until they have a chance to resolve
> > the critical bug they are working on.
> > 3. tempest doesn't branch (we should probably reclassify that as
> > something other than a library to avoid issues with the automation)
> > 
> > All libraries should have had updates for the .gitreview file in the new
> > branch, the constraints URL in the tox.ini file, and the reno
> > configuration (in master, if the project uses reno).
> > 
> > Landing any of the patches in the stable/pike branch will trigger a new
> > documentation build publishing to docs.o.o/$project/pike.
> > 
> > Please take over any of the bot-created patches that do not pass your
> > validation jobs and fix them so that they can land as soon as possible.
> 
> Just to clarify: we cannot land the tox.ini change until the requirements 
> repo 
> is actually branched, right?

Good point. The tests for those patches are passing for some projects in
CI, but when the patches are landed it will make it a little harder for
anyone to run the tests for the branch elsewhere because the
requirements repo has not yet been branched.

So, yes, hold off on landing the constraint URL changes.

Doug

__
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] [tripleo] Proposing Saravanan KR core

[Jiri Tomasek]

+1

On Mon, Jul 24, 2017 at 10:32 AM, Dougal Matthews  wrote:

> +1!
>
> On 21 July 2017 at 16:01, Emilien Macchi  wrote:
>
>> Saravanan KR has shown an high level of expertise in some areas of
>> TripleO, and also increased his involvement over the last months:
>> - Major contributor in DPDK integration
>> - Derived parameter works
>> - and a lot of other things like improving UX and enabling new
>> features to improve performances and networking configurations.
>>
>> I would like to propose Saravanan part of TripleO core and we expect
>> his particular focus on t-h-t, os-net-config and tripleoclient for now
>> but we hope to extend it later.
>>
>> As usual, we'll vote :-)
>> Thanks,
>> --
>> Emilien Macchi
>>
>> 
>> __
>> 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

[openstack-dev] [neutron] - FFE for security-group logging requested

[Furukawa, Yushiro]

Hi Kevin(PTL)/all,

I would like to request an exception for 'Logging feature' for Pike.
Following patches are ready for review, it includes functional tests and docs
update.  In next cycle, we need to add more tests.

The RFE:
  
The Patches:
01. - Driver manager for logging 
plugin
02. - Validator for logging plugin
03. - Logging agent extension
04. - RPC stuff
05. - OVS firewall logging driver
06. - OSC plugin
07. - Networking guide
08. - Functional test
09. - API test
10. - Devstack plugin

Best regards,


Yushiro FURUKAWA

From: Kevin Benton [mailto:ke...@benton.pub] 
Sent: Monday, July 31, 2017 3:53 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] - FFE requests for Pike

Hi all,

If you have any Neutron-related FFE requests for Pike please send an email to 
the dev list with [neutron] in the tag and FFE in the subject like in [1]. We 
will discuss them in the drivers meetings.


1. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120310.html

Thanks,
Kevin Benton
__
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] [OpenStack-Ansible] Not running for Queens PTL

[Andy McCrae]

Following on from last week's meeting - I've had 2 cycles as PTL for OSA,
which has been a really great experience - we've achieved a lot and built
on the strong base we had, which I'm really proud of. I strongly believe
that inviting a fresh perspective and new ideas as PTL is a winning
strategy - it's served us well so far, and in line with previous PTLs I
won't be standing for a 3rd cycle.

Looking forward to assisting the next PTL, and helping to continue to
mature and improve the project!

Thanks!
Andy
__
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] [nova]notification update week 31

[Balazs Gibizer]

Hi,

Here is the status update / focus setting mail about notification work
for week 31.

Bugs

[Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications
use nova-api as binary name instead of nova-osapi_compute
Agreed not to change the binary name in the notifications. Instead we
make an enum for that name to show that the name is intentional.
The patch was split to two parts:
* https://review.openstack.org/#/c/487126 rename binary to source in 
versioned notifications
* https://review.openstack.org/#/c/476538 Use enum value instead of 
string service name


[Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault
notification is never emitted
Still no response on the ML thread about the way forward.
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118639.html

[High] https://bugs.launchpad.net/nova/+bug/1706563 
TestRPC.test_cleanup_notifier_null fails with timeout
[High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error: 
Cannot recover from stack overflow. - in py35 unit test job
The first bug is just a duplicate of the second. It seems the TetRPC 
test suite has a way to end up in an infinite recusion. Can we somehow 
tell python not to truncate the stack trace in this case to see where 
the infinite recursion starts?


[Undecided] https://bugs.launchpad.net/nova/+bug/1706533 
TestInstanceNotificationSample.test_rebuild_server_exc fails with 
testtools.matchers._impl.MismatchError: 2 != 1
Yet another notification sample test instability. Fix is under review: 
https://review.openstack.org/#/c/487382/



Versioned notification transformation
-
As Pike FF happened I will open a new bp for Queens to track the 
remaining work there.


Searchlight integration
---
I will open a follow up bp for Queens. There are follow up patches to 
be moved there:
* There are a set of patches for the BDM addition to optimize the 
payload generation but these are not mandatory for the functionality 
https://review.openstack.org/#/c/483324/
* There was a late request from Searchlight to provide 'status' field 
in the instance notifications as well. See the discussion on the ML 
http://lists.openstack.org/pipermail/openstack-dev/2017-July/119891.html 
There is WIP patch with the solution but we are running out of time 
with that https://review.openstack.org/#/c/485525/


Small improvements
--
These improvements are test and doc generation only so probably not 
affected by the FF.


* https://review.openstack.org/#/c/428199/ Improve assertJsonEqual 
error reporting.


* https://review.openstack.org/#/q/topic:refactor-notification-samples
Factor out duplicated notification sample data
This is a start of a longer patch series to deduplicate notification
sample data. The third patch already shows how much sample data can be
deleted from nova tree. We added a minimal hand rolled json ref
implementation to notification sample test as the existing python json
ref implementations are not well maintained.


Weekly meeting
--
As Pike FF happened I suggest to skip this week's meeting. Please 
disagree in a reply if you have items to discuss.


Cheers,
gibi




__
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] [nova-lxd] Broken nova-lxd

[James Page]

Morning

On Thu, 27 Jul 2017 at 23:58 Michael Still  wrote:

> Hi,
>
> I'm cc'ing openstack-dev because your email is the same as the comment you
> made on the relevant review, and I think getting visibility with the wider
> Nova team is a good idea.
>
> Unfortunately this is a risk of having an out of tree Nova driver, which
> has never been the recommended path for implementing drivers for Nova.
> Being out of tree isn't forbidden, but it does come with the cost of
> staying up to date with Nova and handling changes as they occur.
>

Agreed - and we've felt this from time-to-time since the nova-lxd driver
was started.

Maybe the Queens cycle might be a good time to review our out-of-tree-ness
and see whether the Nova team would be prepared to accept the LXD driver
in-tree.

I'm more comfortable now with where we are with regards to devstack tempest
testing in the gate for the LXD driver, although we do still have some
feature gaps compared to the libvirt driver (specifically boot from volume)
which results in a large-ish skip list.


> In this case, if you look at the review chain you'll see that the move is
> a pre-cursor to moving this code to use oslo.privsep. Unless lxd is going
> to move to privsep in lockstep with nova, your best bet would be to
> duplicate this utility method in the nova-lxd codebase.
>

We'll duplicate right now (see [0]) to unblock the current problem and take
a look at the work to move lockstep with nova to use oslo.privsep.

Cheers

James

[0] https://review.openstack.org/#/c/488254/
__
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] [neutron] - FFE requests for Pike

[Kevin Benton]

Hi all,

If you have any Neutron-related FFE requests for Pike please send an email
to the dev list with [neutron] in the tag and FFE in the subject like in
[1]. We will discuss them in the drivers meetings.


1. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120310.html

Thanks,
Kevin Benton
__
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] [tc] Technical Committee Status update, July 28th

[Flavio Percoco]

On 28/07/17 10:50 +0200, Thierry Carrez wrote:

Hi!

This is the weekly update on Technical Committee initiatives. You can
find the full list of all open topics at:

https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee


== Recently-approved changes ==

* Declare plainly the current state of PostgreSQL in OpenStack [1]
* Clean up remaining 'big tent' mention in Licensing requirements [2]
* Queens goals updates: octavia
* New repositories: charm-deployment-guide
* Repositories moved to legacy: api-site, faafo
* Removed repositories: deb-mistral-dashboard

[1] https://review.openstack.org/#/c/427880/
[2] https://review.openstack.org/484607

The big item of the week is the final merge, after almost 6 months of
discussion, of the resolution declaring plainly the state of PostgreSQL
in OpenStack:

https://governance.openstack.org/tc/resolutions/20170613-postgresql-status.html

Additionally, the governance repository was tagged in preparation for
the PTL elections, to clearly define the teams and associated
repositories that will be considered.


== Open discussions ==

Flavio's resolution about allowing teams to host meetings in their own
IRC channels is still in the early days of discussion, and is likely to
need a few iterations to iron out:

https://review.openstack.org/485117



I'll update this patch asap. Heads up, I'll be out most of this week so expect
an update by next week (unless I get to it today).



== TC member actions for the coming week(s) ==

Flavio still needs to incorporate feedback in the "Drop TC meetings"
proposal and produce a new patchset, or abandon it since we pretty much
already implemented the described change.


ditto! :D

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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