Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

[Kekane, Abhishek]

Sorry for wrong auto-correction :)

Congratulations Dharini, All the best. .

Abhishek
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: Sunday, January 29, 2017 8:39 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance 
core

Congratulations Sharing. .
All the best.

Abhishek

Sent from OWA on Android

From: Brian Rosmaita 
>
Sent: Thursday, January 26, 2017 8:56:30 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance 
core

Having heard only affirmative responses, I've added Dharini Chandrasekar
to the Glance core group, with all the rights and privileges pertaining
thereto.

Welcome to the Glance core team, Dharini!

On 1/24/17 8:36 AM, Brian Rosmaita wrote:
> I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance
> core.  She has been an active reviewer and contributor to the Glance
> project during the Newton and Ocata cycles, has contributed to other
> OpenStack projects, and has represented Glance in some interactions with
> other project teams.  Additionally, she recently jumped in and saw
> through to completion a high priority feature for Newton when the
> original developer was unable to continue working on it.  Plus, she's
> willing to argue with me (and the other cores) about points of software
> engineering.  She will be a great addition to the Glance core reviewers
> team.
>
> If you have any concerns, please let me know.  I plan to add Dharini to
> the core list after this week's Glance meeting.
>
> thanks,
> 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

__
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.

__
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

Re: [openstack-dev] [all][elections] PTL nomination period is now over

[Kendall Nelson]

Yes of course :) Did you want to schedule a meeting or just discuss here
more?

I've seen some discussion about making UX to a working group?

-Kendall (diablo_rojo)

On Sun, Jan 29, 2017, 7:46 PM Lana Brindley 
wrote:

> Hi Kendall,
>
> I'd like to discuss the future of the UX project with you, if that's OK?
>
> Lana
>
> On 30/01/17 11:05, Kendall Nelson wrote:
> > Hello All!
> >
> > PTL Nomination is now over. The official candidate list is available on
> the election website[0].
> >
> > There is only 1project without candidates, so according to this
> resolution[1], the TC we'll have to appoint a new PTL for OpenStack UX.
> >
> > There are 5projects that will have an election: Ironic, Keystone,
> Neutron, Quality Assurance and Stable Branch Maintenance.The details for
> those will be posted shortly after we setup the CIVS system.
> >
> > Thank you,
> >
> > [0]: http://governance.openstack.org/election/# <
> http://governance.openstack.org/election/#pike-ptl-candidates>pike <
> http://governance.openstack.org/election/#pike-ptl-candidates>-ptl-candidates
> 
> > [1]:
> http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.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
> >
>
> --
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
> http://lanabrindley.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 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] Supporting our global community

[Lana Brindley]

Jonathon, Mark, Lauren, and the rest of the Foundation staff,

Thank you for this important note.

Is Foundation able to provide some concrete assurance that they will continue 
to ensure that availability of visas is to be prioritised for future OpenStack 
events? Additionally, that you will not run events in countries that do not 
reflect OpenStack values of diversity?

Lana

On 30/01/17 04:34, Jonathan Bryce wrote:
> OpenStack is a global open source community. The OpenStack Foundation serves 
> members in 180 countries focused on advancing the capabilities and 
> accessibility of open infrastructure everywhere. We fundamentally believe 
> diversity and collaboration are a powerful force for innovation, and it has 
> been amazing to see the product of tens of thousands of people around the 
> world over the last 6+ years.
> 
> Lauren, Mark and I disagree with the executive order issued by President 
> Trump that targets individuals from 7 countries. The order restricts the 
> travel and movement of people in a discriminatory way that  results in a 
> restriction on access to talent and ideas. It is still unclear how the 
> policies will play out and be enforced, but we will be watching, advocating 
> for and supporting our community members to the best of our ability. 
> 
> This executive order will not impact the governance of the Foundation or the 
> way the community operates globally. We will continue to support user groups 
> and community members that are active in the seven countries named by the 
> executive order, alongside our 120+ user groups around the world. However, we 
> have two scheduled events in the United States within the next six months 
> that will attract a global audience: the PTG (Project Teams Gathering) in 
> Atlanta, Feb 20-24, a smaller event that will bring together hundreds of 
> upstream contributors, and the OpenStack Summit in Boston, May 8-11, our 
> larger event that happens every six months. 
> 
> This executive order could impact some community members' ability to travel 
> to Atlanta and Boston, but unfortunately it is too late at this point to 
> change the location of these events. The following three OpenStack Summits, 
> however, are now scheduled to occur outside of the United States. The next 
> Summit will be in November 2017 in Sydney, Australia and we are working to 
> finalize the details so we can announce the following two Summit locations 
> soon.
> 
> We’ve already heard from one community member, Mohammed Naser, who is 
> concerned that his plans to travel from Canada to Atlanta to attend the PTG 
> may be restricted, simply because he a dual citizen of Canada and Iraq.  
> Mohammed has been contributing code to OpenStack since 2011 and is the CEO 
> and Founder of Vexxhost. Blocking his travel would serve no purpose and rob 
> the community of a valuable contributor during an important event. If you are 
> concerned about the impact or have any questions, please don't hesitate to 
> reach out to me at jonat...@openstack.org.
> 
> Political actions like this highlight the importance of our collective 
> values. The Four Opens, the founding principles of our community, exist to 
> ensure the free flow of talent and ideas, across geographic, national, 
> organizational or other lines that might divide us. We believe in humanity. 
> We believe in opportunity. We believe in the power of collaboration across 
> borders, and we will continue to carry forward our mission.
> 
> We also posted this online: 
> https://www.openstack.org/blog/2017/01/supporting-our-global-community/
> 
> Jonathan Bryce
> Mark Collier
> Lauren Sell
> 
> 
> 
> __
> 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
> 

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com



signature.asc
Description: OpenPGP digital 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] [ux] Future of the OpenStack UX team

[Lana Brindley]

Hi Thierry,

Sorry for not noticing this thread and replying earlier.

I've now reviewed the minutes from the meeting, and I support thingee's 
suggestion of having a UX working group. This way, UX can get the attention it 
rightly deserves. Without the research and guidelines provided by the UX team, 
user-facing projects (such as Docs) will be poorer. I believe that it's in 
Foundations best interests to ensure that UX work is ongoing, and adequately 
supported, in the same way as Marketing and other user outreach services. 

I am happy to work with Foundation (on behalf of the Docs team) to determine 
how this would work in practice.

Thanks,
Lana

On 05/01/17 00:43, Thierry Carrez wrote:
> Hi everyone,
> 
> Piet recently reached out to me to explain that he won't be able to
> continue in his role as OpenStack UX team's PTL. Since he created the
> team and spent a lot of time coordinating its activities, that raises
> the question of the future of the OpenStack UX team.
> 
> The situation was discussed at the TC meeting yesterday[1] and the
> general feeling was that there was a lot of value in a separate team
> centralizing things like Persona definition and facilitating
> properly-conducted UX surveys. That said, if nobody is able to dedicate
> the time that effort needs, we could also disband the centralized team
> and encourage every project to adopt the tools and techniques that were
> built and introduced by the UX team in the past years.
> 
> So... What are your thoughts on those options ? Do we have a volunteer
> (or more than one) to take over UX PTLship ?
> 
> [1]
> http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-03-20.00.log.html#l-404
> 

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com



signature.asc
Description: OpenPGP digital 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] [vitrage] New Vitrage project mascot

[Renat Akhmerov]

Looks cool :)

Renat Akhmerov
@Nokia

> On 29 Jan 2017, at 19:23, Yujun Zhang  wrote:
> 
> Not remembering the original design. 
> 
> This one looks good to me :-)
> 
> On Sun, Jan 29, 2017 at 8:18 PM Afek, Ifat (Nokia - IL)  > wrote:
> Hi,
> 
>  
> 
> This is the new draft of our Giraffe mascot. The illustrators tried to make 
> its skin look more like stained glass.
> 
> What do you think?
> 
>  
> 
> Ifat.
> 
>  
> 
> 
> 
>  
> 
>  
> 
> 
> 
> 
> __
> 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][elections] PTL nomination period is now over

[Lana Brindley]

On 30/01/17 14:15, Steve Martinelli wrote:
> On Sun, Jan 29, 2017 at 8:05 PM, Kendall Nelson  > wrote:
> 
> PTL Nomination is now over. The official candidate list is available on 
> the election website[0].
> 
> 
> It's great to see only 1 project was without a PTL!
>  
> 
> There is only 1project without candidates, so according to this 
> resolution[1], the TC we'll have to appoint a new PTL for OpenStack UX.
> 
> 
> The UX project was briefly discussed at a recent TC meeting (see the end of 
> the log) [1], with Piet stepping down there was some discussion about whether 
> or not it needs to be a standalone project, or can turn into a working group 
> (like the API working group).
> 
> Oh, Thierry sent something out to the mailing list already [2], no replies :(
> 
> [1] 
> http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-03-20.00.log.html
> [2] 
> http://lists.openstack.org/pipermail/openstack-dev/2017-January/109622.html
> 

Ah, thanks Steve. I'll digest this and then reply on that thread :)

Lana

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com



signature.asc
Description: OpenPGP digital 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][elections] PTL nomination period is now over

[Steve Martinelli]

On Sun, Jan 29, 2017 at 8:05 PM, Kendall Nelson 
wrote:

> PTL Nomination is now over. The official candidate list is available on
> the election website[0].
>

It's great to see only 1 project was without a PTL!


> There is only 1 project without candidates, so according to this
> resolution[1], the TC we'll have to appoint a new PTL for OpenStack UX.
>

The UX project was briefly discussed at a recent TC meeting (see the end of
the log) [1], with Piet stepping down there was some discussion about
whether or not it needs to be a standalone project, or can turn into a
working group (like the API working group).

Oh, Thierry sent something out to the mailing list already [2], no replies
:(

[1]
http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-03-20.00.log.html
[2]
http://lists.openstack.org/pipermail/openstack-dev/2017-January/109622.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

Re: [openstack-dev] [nova] The status of servers API's filters

[Ghanshyam Mann]

On Sun, Jan 29, 2017 at 10:12 AM, Alex Xu  wrote:

>
>
> 2017-01-29 1:31 GMT+08:00 Matt Riedemann :
>
>> On 1/27/2017 3:37 AM, Alex Xu wrote:
>>
>>> The patches about validation the filters and sorts for servers API are
>>> merged [0]. But we still have something left [1].
>>>
>>> The left is about the proposal of introducing the new rule
>>> 'os_compute_api:servers:all_tenants_visible' which is soft enforcement.
>>> The new rule will instead of the old hard enforcement rule
>>> "os_compute_api:servers:index:get_all_tenants".
>>>
>>> In the discussion of nova API meeting, Join pointed out that the change
>>> from hard enforcement to soft enforcement needs Microversion. The API
>>> used to return 403 when user didn't have permission of all_tenants
>>> parameter. But now the API returns 200 with the own instances when no
>>> permission of all_tenants parameter. So the proposal should be separated
>>> to two parts:
>>>
>>> i. rename the policy from "get_all_tenants" to the "all_tenants_visible"
>>> ii. change the enforcement from hard to soft by Microversion.
>>>
>>> In the old microversion, the rule keeps as hard enforcement.
>>>
>>> So in Ocata, "get_all_tenants" will be deprecated. If the deployer have
>>> overriden rule in the policy file, the old rule still will be enforced,
>>> and the warning message will be emit to notice that the user needs to
>>> move their custom rule to the new rule 'all_tenants_visiable'. And if
>>> the API user requests with new microversion, the rule will become soft
>>> enforcement.
>>>
>>> So if that sounds make sense, there also have another question about
>>> whether we have enough time to merge it. I think Matt will make a call
>>> on it.
>>>
>>> And due to holidays in China, both I and Kevin are in vacation.  And
>>> really really appreciate Ghanshyam take care on those patches! The
>>> spec[3] and the patch[1] already updated by him.
>>>
>>> AnywayHappy Chinese New Year to everyone(yea, new year again \o/).
>>>
>>> Thanks
>>> Alex
>>>
>>> [0] https://review.openstack.org/408571
>>> 
>>> and https://review.openstack.org/415142
>>> 
>>> [1] https://review.openstack.org/#/q/status:open+project:opensta
>>> ck/nova+branch:master+topic:bp/add-whitelist-for-server-list
>>> -filter-sort-parameters
>>> >> ack/nova+branch:master+topic:bp/add-whitelist-for-server-lis
>>> t-filter-sort-parameters>
>>> [3] https://review.openstack.org/425533
>>> 
>>>
>>>
>>>
>>> 
>>> __
>>> 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
>>>
>>>
>> My immediate question is, does this need to happen in Ocata or can we
>> defer the all_tenants_visible policy change to Pike? Is there anything we
>> merged in Ocata that is now broken, or weird, or blocks us from doing
>> something later, etc if we don't get this done now?
>>
>
> I didn't see any broken or blocks without the all_tenants_visiable policy
> change. The policy change is just part of vision of how filters should be
> looks like between admin user and non-admin user.
>
>
>>
>> Honestly I never really understood why the all_tenants policy change was
>> being lumped in with the server sort/filter whitelist blueprint, except
>> maybe just because of convenience?
>>
>
> Emm..I didn't remember any discussion about why we should put all of them
> into one spec or not.
>
>
>> Anyway, this seems like something we can defer to Pike unless I'm missing
>> something.
>
>
> I'm ok with that, due to I didn't have any critical reason. The only thing
> is we need one more cycle to remove a old policy rule. But currently the
> new proposal without more discussion, and we only have 1 week left for spec
> change and patches. It isn't worth to take that risk I guess.
>

​Ok, I was thinking if we could get new policy and old policy deprecation​
in Ocata and behavior change in Pike but yes that needs spec update and
review which is little bit tight for Ocata.

I am also ok to defer this in Pike.



>
> Anyway, Matt, thanks for your response.
>
>
>>
>>
>> --
>>
>> Thanks,
>>
>> Matt Riedemann
>>
>> 
>> __
>> 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
> 

Re: [openstack-dev] [all][elections] PTL nomination period is now over

[Lana Brindley]

Hi Kendall,

I'd like to discuss the future of the UX project with you, if that's OK?

Lana

On 30/01/17 11:05, Kendall Nelson wrote:
> Hello All!
> 
> PTL Nomination is now over. The official candidate list is available on the 
> election website[0].
> 
> There is only 1project without candidates, so according to this 
> resolution[1], the TC we'll have to appoint a new PTL for OpenStack UX.
> 
> There are 5projects that will have an election: Ironic, Keystone, Neutron, 
> Quality Assurance and Stable Branch Maintenance.The details for those will be 
> posted shortly after we setup the CIVS system.
> 
> Thank you,
> 
> [0]: http://governance.openstack.org/election/# 
> pike 
> -ptl-candidates
>  
> [1]: 
> http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.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
> 

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com



signature.asc
Description: OpenPGP digital 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] [all][elections] PTL nomination period is now over

[Kendall Nelson]

Hello All!

PTL Nomination is now over. The official candidate list is available on the
election website[0].

There is only 1 project without candidates, so according to this
resolution[1], the TC we'll have to appoint a new PTL for OpenStack UX.

There are 5 projects that will have an election: Ironic, Keystone, Neutron,
Quality Assurance and Stable Branch Maintenance. The details for those will
be posted shortly after we setup the CIVS system.

Thank you,

[0]: http://governance.openstack.org/election/#
pike

-ptl-candidates

[1]:
http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.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

Re: [openstack-dev] Supporting our global community

[Anita Kuno]

On 2017-01-29 01:34 PM, Jonathan Bryce wrote:

OpenStack is a global open source community. The OpenStack Foundation serves 
members in 180 countries focused on advancing the capabilities and 
accessibility of open infrastructure everywhere. We fundamentally believe 
diversity and collaboration are a powerful force for innovation, and it has 
been amazing to see the product of tens of thousands of people around the world 
over the last 6+ years.

Lauren, Mark and I disagree with the executive order issued by President Trump 
that targets individuals from 7 countries. The order restricts the travel and 
movement of people in a discriminatory way that  results in a restriction on 
access to talent and ideas. It is still unclear how the policies will play out 
and be enforced, but we will be watching, advocating for and supporting our 
community members to the best of our ability.

This executive order will not impact the governance of the Foundation or the 
way the community operates globally. We will continue to support user groups 
and community members that are active in the seven countries named by the 
executive order, alongside our 120+ user groups around the world. However, we 
have two scheduled events in the United States within the next six months that 
will attract a global audience: the PTG (Project Teams Gathering) in Atlanta, 
Feb 20-24, a smaller event that will bring together hundreds of upstream 
contributors, and the OpenStack Summit in Boston, May 8-11, our larger event 
that happens every six months.

This executive order could impact some community members' ability to travel to 
Atlanta and Boston, but unfortunately it is too late at this point to change 
the location of these events. The following three OpenStack Summits, however, 
are now scheduled to occur outside of the United States. The next Summit will 
be in November 2017 in Sydney, Australia and we are working to finalize the 
details so we can announce the following two Summit locations soon.

We’ve already heard from one community member, Mohammed Naser, who is concerned 
that his plans to travel from Canada to Atlanta to attend the PTG may be 
restricted, simply because he a dual citizen of Canada and Iraq.  Mohammed has 
been contributing code to OpenStack since 2011 and is the CEO and Founder of 
Vexxhost. Blocking his travel would serve no purpose and rob the community of a 
valuable contributor during an important event. If you are concerned about the 
impact or have any questions, please don't hesitate to reach out to me at 
jonat...@openstack.org.


An update: Canada's Immigration Minister held a press conference saying 
that Canadians with dual citizenship won't be affected: 
http://www.cbc.ca/news/politics/canada-hussen-reaction-to-trump-travel-restrictions-1.3957515 
Now that should make things easier for Mohammed Naser but it doesn't 
solve the larger problem affecting the whole community.


Also in the above linked article, the Canadian government will accept 
those travelers refused entry by the United States due to this order, if 
you find yourself in a situation where that information might be of help 
to you.


As I already shared with Jonathan in private, I'm Canadian and plan on 
avoiding as much travel to the US as I am able for the next four years, 
so people not from the 7 named countries are also making choices as a 
consequence of this action.


Confident we can collectively envision a productive future for all of us,
Anita.



Political actions like this highlight the importance of our collective values. 
The Four Opens, the founding principles of our community, exist to ensure the 
free flow of talent and ideas, across geographic, national, organizational or 
other lines that might divide us. We believe in humanity. We believe in 
opportunity. We believe in the power of collaboration across borders, and we 
will continue to carry forward our mission.

We also posted this online: 
https://www.openstack.org/blog/2017/01/supporting-our-global-community/

Jonathan Bryce
Mark Collier
Lauren Sell




__
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] Proposing Amy Marrich for core

[Mike Carden]

On Sat, Jan 28, 2017 at 1:29 AM, Alexandra Settle 
wrote:

> Hi OpenStack-Ansible team,
>
>
>
> I would like to propose Amy Marrich for the core team for
> OpenStack-Ansible.
>
>
>
+1I wholeheartedly agree.

-- 
MC
__
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][Oslo] Huge number of deprecation warnings in functional tests

[Davanum Srinivas]

Graham,

I've turned it essentially into a no-op now. i'll let the original
authors debate the full revert and other implications.

Thanks,
Dims

On Sun, Jan 29, 2017 at 3:42 PM, Hayes, Graham  wrote:
> On 29/01/2017 15:45, Davanum Srinivas wrote:
>> Graham, Sławek, Joshua,
>>
>> Please take a look at my attempt:
>> https://review.openstack.org/#/c/426576/
>>
>> Thanks,
>> Dims
>>
>
> At this point, a full revert seems like the right idea.
>
> There is a few problem with the warning, not just the amount of them.
>
> Previously we have gone out of our way to avoid these issues in
> libraries. (e.g. [1])
>
> The stack level also seems wrong to me - it is pointing at the
> consuming project not the oslo.context library.
>
> 1 - https://review.openstack.org/#/c/275914/ specifically
> https://review.openstack.org/#/c/275914/3/oslo_versionedobjects/fields.py
> L311.
>
>> On Sun, Jan 29, 2017 at 7:56 AM, Hayes, Graham  wrote:
>>> On 29/01/17 00:53, Davanum Srinivas wrote:
 Graham, Sławek,

 Have you seen this?

 Neutron has/uses a WarningFixture:
 http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
 http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70

 Which uses filterwarnings:
 http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80

 Where "always" is being used:
 https://docs.python.org/2/library/warnings.html

 Which prints warnings every single time.

 So, can we please "fix" it in there quickly?

 Thanks,
 Dims
>>>
>>> This is still a broken release - previously in oslo libraries we have
>>> been careful with issuing multiple warnings for a deprecation.
>>>
>>> This is still an issue, with glance-api [0] and I assume others (e.g. we
>>> have not had a designate CI run with the new oslo.context yet)
>>>
>>> Seen as we are going into RC week, it seems very risky to keep it.
>>>
>>> 0 -
>>> http://logstash.openstack.org/#dashboard/file/logstash.json?query=_id%3A%5C%22AVnnYuy3QVJYkPlRPEJH%5C%22
>>>
 On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  
 wrote:
> Hello,
>
> Thanks. I just filled bug report to oslo project:
> https://bugs.launchpad.net/oslo.context/+bug/1660088
>
> --
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
>
> On Sat, 28 Jan 2017, Hayes, Graham wrote:
>
>> On 28/01/17 20:54, Sławek Kapłoński wrote:
>>> Hello,
>>>
>>> I pushed today patch in Neutron to gerrit [1] and I noticed that 
>>> functional
>>> tests are failing. In logs there is huge number of deprecation warnings
>>> displayed [2]. Tests are failing because of global timeout is reached 
>>> and IMO
>>> reason of this timeout is this huge amount of deprecation warnings.
>>> I checked that those warnings are disaplyed when oslo.context==2.12.0 is
>>> installed. With oslo.context==2.11.0 all is fine.
>>> Should it be reported as bug in Neutron or in Oslo project? Or maybe You
>>> already know about it and there is some patch to fix it but I couldn't 
>>> find it?
>>
>> Its an oslo.context bug - I can't see one filed for it yet.
>>>
>>> [1] https://review.openstack.org/#/c/426429/
>>> [2] 
>>> http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
>>>
>>
>> It looks like the warnings function was miss used - this should be set
>> as a once only message. The stack trace level seems suspect, as it
>> points as neutron/context.py as the one sending out the notice, not
>> oslo.contexts base class.
>>
>> [3] seems to the cause - I would suggest reverting this commit and
>> doing a 2.13.0 release. This is going to be *really* noisy. (logstash
>> has 2.5 million items for this string in the last 24 hours)
>>
>> 3 -
>> https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
>>
>> __
>> 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: 

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

My patch [1] to fix it in Neutron is now merged. Thx Ihar and Kevin for
so fast review :)
It looks that now functional tests are working fine.

[1] https://review.openstack.org/#/c/426550/

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sun, 29 Jan 2017, Sławek Kapłoński wrote:

> Hello,
> 
> I made small patch to Neutron to fix [1] this issue. It looks that
> functional tests are fine with it [2].
> Please review it if it makes sense for You :)
> 
> [1] https://review.openstack.org/#/c/426550/
> [2] 
> http://logs.openstack.org/50/426550/1/check/gate-neutron-dsvm-functional-ubuntu-xenial/4b56e71/console.html
> 
> -- 
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
> 
> On Sun, 29 Jan 2017, Sławek Kapłoński wrote:
> 
> > Hello,
> > 
> > Thanks for explaining that. I'm don't know this part well and that's why
> > I asked here if it's oslo or neutron issue.
> > So it looks like it is issue in Neutron nor Oslo.context, right?
> > 
> > -- 
> > Best regards / Pozdrawiam
> > Sławek Kapłoński
> > sla...@kaplonski.pl
> > 
> > On Sat, 28 Jan 2017, Joshua Harlow wrote:
> > 
> > > Yup, all that should be needed is to read the docs and adjust it.
> > > 
> > > "once" - print only the first occurrence of matching warnings, regardless 
> > > of
> > > location
> > > 
> > > "always" - always print matching warnings
> > > 
> > > Changing it to 'once' should gather less repeated logs; IMHO 'always' 
> > > should
> > > never be used, so that was probably just a mistake for whoever committed
> > > that fixture with it set like that.
> > > 
> > > -Josh
> > > 
> > > Davanum Srinivas wrote:
> > > > Graham, Sławek,
> > > > 
> > > > Have you seen this?
> > > > 
> > > > Neutron has/uses a WarningFixture:
> > > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> > > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> > > > 
> > > > Which uses filterwarnings:
> > > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> > > > 
> > > > Where "always" is being used:
> > > > https://docs.python.org/2/library/warnings.html
> > > > 
> > > > Which prints warnings every single time.
> > > > 
> > > > So, can we please "fix" it in there quickly?
> > > > 
> > > > Thanks,
> > > > Dims
> > > > 
> > > > On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  
> > > > wrote:
> > > > > Hello,
> > > > > 
> > > > > Thanks. I just filled bug report to oslo project:
> > > > > https://bugs.launchpad.net/oslo.context/+bug/1660088
> > > > > 
> > > > > --
> > > > > Best regards / Pozdrawiam
> > > > > Sławek Kapłoński
> > > > > sla...@kaplonski.pl
> > > > > 
> > > > > On Sat, 28 Jan 2017, Hayes, Graham wrote:
> > > > > 
> > > > > > On 28/01/17 20:54, Sławek Kapłoński wrote:
> > > > > > > Hello,
> > > > > > > 
> > > > > > > I pushed today patch in Neutron to gerrit [1] and I noticed that 
> > > > > > > functional
> > > > > > > tests are failing. In logs there is huge number of deprecation 
> > > > > > > warnings
> > > > > > > displayed [2]. Tests are failing because of global timeout is 
> > > > > > > reached and IMO
> > > > > > > reason of this timeout is this huge amount of deprecation 
> > > > > > > warnings.
> > > > > > > I checked that those warnings are disaplyed when 
> > > > > > > oslo.context==2.12.0 is
> > > > > > > installed. With oslo.context==2.11.0 all is fine.
> > > > > > > Should it be reported as bug in Neutron or in Oslo project? Or 
> > > > > > > maybe You
> > > > > > > already know about it and there is some patch to fix it but I 
> > > > > > > couldn't find it?
> > > > > > Its an oslo.context bug - I can't see one filed for it yet.
> > > > > > > [1] https://review.openstack.org/#/c/426429/
> > > > > > > [2] 
> > > > > > > http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
> > > > > > > 
> > > > > > It looks like the warnings function was miss used - this should be 
> > > > > > set
> > > > > > as a once only message. The stack trace level seems suspect, as it
> > > > > > points as neutron/context.py as the one sending out the notice, not
> > > > > > oslo.contexts base class.
> > > > > > 
> > > > > > [3] seems to the cause - I would suggest reverting this commit and
> > > > > > doing a 2.13.0 release. This is going to be *really* noisy. 
> > > > > > (logstash
> > > > > > has 2.5 million items for this string in the last 24 hours)
> > > > > > 
> > > > > > 3 -
> > > > > > https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
> > > > > > 
> > > > > > __
> > > > > > 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][Oslo] Huge number of deprecation warnings in functional tests

[Hayes, Graham]

On 29/01/2017 15:45, Davanum Srinivas wrote:
> Graham, Sławek, Joshua,
>
> Please take a look at my attempt:
> https://review.openstack.org/#/c/426576/
>
> Thanks,
> Dims
>

At this point, a full revert seems like the right idea.

There is a few problem with the warning, not just the amount of them.

Previously we have gone out of our way to avoid these issues in
libraries. (e.g. [1])

The stack level also seems wrong to me - it is pointing at the
consuming project not the oslo.context library.

1 - https://review.openstack.org/#/c/275914/ specifically
https://review.openstack.org/#/c/275914/3/oslo_versionedobjects/fields.py 
L311.

> On Sun, Jan 29, 2017 at 7:56 AM, Hayes, Graham  wrote:
>> On 29/01/17 00:53, Davanum Srinivas wrote:
>>> Graham, Sławek,
>>>
>>> Have you seen this?
>>>
>>> Neutron has/uses a WarningFixture:
>>> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
>>> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
>>>
>>> Which uses filterwarnings:
>>> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
>>>
>>> Where "always" is being used:
>>> https://docs.python.org/2/library/warnings.html
>>>
>>> Which prints warnings every single time.
>>>
>>> So, can we please "fix" it in there quickly?
>>>
>>> Thanks,
>>> Dims
>>
>> This is still a broken release - previously in oslo libraries we have
>> been careful with issuing multiple warnings for a deprecation.
>>
>> This is still an issue, with glance-api [0] and I assume others (e.g. we
>> have not had a designate CI run with the new oslo.context yet)
>>
>> Seen as we are going into RC week, it seems very risky to keep it.
>>
>> 0 -
>> http://logstash.openstack.org/#dashboard/file/logstash.json?query=_id%3A%5C%22AVnnYuy3QVJYkPlRPEJH%5C%22
>>
>>> On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  
>>> wrote:
 Hello,

 Thanks. I just filled bug report to oslo project:
 https://bugs.launchpad.net/oslo.context/+bug/1660088

 --
 Best regards / Pozdrawiam
 Sławek Kapłoński
 sla...@kaplonski.pl

 On Sat, 28 Jan 2017, Hayes, Graham wrote:

> On 28/01/17 20:54, Sławek Kapłoński wrote:
>> Hello,
>>
>> I pushed today patch in Neutron to gerrit [1] and I noticed that 
>> functional
>> tests are failing. In logs there is huge number of deprecation warnings
>> displayed [2]. Tests are failing because of global timeout is reached 
>> and IMO
>> reason of this timeout is this huge amount of deprecation warnings.
>> I checked that those warnings are disaplyed when oslo.context==2.12.0 is
>> installed. With oslo.context==2.11.0 all is fine.
>> Should it be reported as bug in Neutron or in Oslo project? Or maybe You
>> already know about it and there is some patch to fix it but I couldn't 
>> find it?
>
> Its an oslo.context bug - I can't see one filed for it yet.
>>
>> [1] https://review.openstack.org/#/c/426429/
>> [2] 
>> http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
>>
>
> It looks like the warnings function was miss used - this should be set
> as a once only message. The stack trace level seems suspect, as it
> points as neutron/context.py as the one sending out the notice, not
> oslo.contexts base class.
>
> [3] seems to the cause - I would suggest reverting this commit and
> doing a 2.13.0 release. This is going to be *really* noisy. (logstash
> has 2.5 million items for this string in the last 24 hours)
>
> 3 -
> https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>>
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Supporting our global community

[Jonathan Bryce]

OpenStack is a global open source community. The OpenStack Foundation serves 
members in 180 countries focused on advancing the capabilities and 
accessibility of open infrastructure everywhere. We fundamentally believe 
diversity and collaboration are a powerful force for innovation, and it has 
been amazing to see the product of tens of thousands of people around the world 
over the last 6+ years.

Lauren, Mark and I disagree with the executive order issued by President Trump 
that targets individuals from 7 countries. The order restricts the travel and 
movement of people in a discriminatory way that  results in a restriction on 
access to talent and ideas. It is still unclear how the policies will play out 
and be enforced, but we will be watching, advocating for and supporting our 
community members to the best of our ability. 

This executive order will not impact the governance of the Foundation or the 
way the community operates globally. We will continue to support user groups 
and community members that are active in the seven countries named by the 
executive order, alongside our 120+ user groups around the world. However, we 
have two scheduled events in the United States within the next six months that 
will attract a global audience: the PTG (Project Teams Gathering) in Atlanta, 
Feb 20-24, a smaller event that will bring together hundreds of upstream 
contributors, and the OpenStack Summit in Boston, May 8-11, our larger event 
that happens every six months. 

This executive order could impact some community members' ability to travel to 
Atlanta and Boston, but unfortunately it is too late at this point to change 
the location of these events. The following three OpenStack Summits, however, 
are now scheduled to occur outside of the United States. The next Summit will 
be in November 2017 in Sydney, Australia and we are working to finalize the 
details so we can announce the following two Summit locations soon.

We’ve already heard from one community member, Mohammed Naser, who is concerned 
that his plans to travel from Canada to Atlanta to attend the PTG may be 
restricted, simply because he a dual citizen of Canada and Iraq.  Mohammed has 
been contributing code to OpenStack since 2011 and is the CEO and Founder of 
Vexxhost. Blocking his travel would serve no purpose and rob the community of a 
valuable contributor during an important event. If you are concerned about the 
impact or have any questions, please don't hesitate to reach out to me at 
jonat...@openstack.org.

Political actions like this highlight the importance of our collective values. 
The Four Opens, the founding principles of our community, exist to ensure the 
free flow of talent and ideas, across geographic, national, organizational or 
other lines that might divide us. We believe in humanity. We believe in 
opportunity. We believe in the power of collaboration across borders, and we 
will continue to carry forward our mission.

We also posted this online: 
https://www.openstack.org/blog/2017/01/supporting-our-global-community/

Jonathan Bryce
Mark Collier
Lauren Sell



__
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] [trove] status of the gate

[Amrith Kumar]

All:

There are at least a couple of issues that are currently impacting the trove
gate and I'm getting to the bottom of it. The currently known problems are
being handled in a single commit[1].

This currently emcompasses the issues identified in three independent
commits, none of which will be able to merge by themselves [2], [3], and
[4].

There is at least one more issue that I have to wrestle to the ground and it
appears to be some change to the structure of oslo_context that isn't
immediately apparent (at least that's the current hunch).

In the meanwhile, rechecks and changes to trove, and python-troveclient will
merely fail after taking up some useless time in the gate.

I'll try and get this resolved soon, sorry for the delay.

-amrith 

[1] https://review.openstack.org/#/c/426535/
[2] https://review.openstack.org/#/c/425857/
[3] https://review.openstack.org/#/c/423086/
[4] https://review.openstack.org/#/c/412497/


--
Amrith Kumar
GPG: 0x5e48849a9d21a29b



smime.p7s
Description: S/MIME cryptographic 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-Infra] [infra] Pike PTG Etherpad

[Paul Belanger]

On Wed, Jan 25, 2017 at 11:44:46PM +, Jeremy Stanley wrote:
> Just a heads-up I've been meaning to send for a while... as
> discussed in the last month of Infra meetings we've got a pad here
> for people to pitch ideas of things they want to collaborate on in
> the Infra team space at the PTG on Monday and Tuesday:
> 
> https://etherpad.openstack.org/p/infra-ptg-pike
> 
> It's pretty much a free-for-all; as long as there are at least two
> people who want to work together on a topic and it's Infra-related
> we'll do our best to accommodate. It's also listed with all the
> others so you don't need to remember the pad name:
> 
> https://wiki.openstack.org/wiki/PTG/Pike/Etherpads
> 
> I'm looking forward to seeing lots of you in a few weeks! I and a
> number of other Infra team members will be around for the full week
> so if there's any related discussions you want to have with your own
> teams just give us a heads up and we can try to have someone with
> some Infra-sense pop in and help.
> -- 
> Jeremy Stanley

I've added 2 items I'd like to talk about:

 - Zuulv3: JJB to ansible playbook (onetime) converter.
 - Control plan upgrades to Xenial.

> ___
> OpenStack-Infra mailing list
> openstack-in...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


__
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][Oslo] Huge number of deprecation warnings in functional tests

[Davanum Srinivas]

Graham, Sławek, Joshua,

Please take a look at my attempt:
https://review.openstack.org/#/c/426576/

Thanks,
Dims

On Sun, Jan 29, 2017 at 7:56 AM, Hayes, Graham  wrote:
> On 29/01/17 00:53, Davanum Srinivas wrote:
>> Graham, Sławek,
>>
>> Have you seen this?
>>
>> Neutron has/uses a WarningFixture:
>> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
>> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
>>
>> Which uses filterwarnings:
>> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
>>
>> Where "always" is being used:
>> https://docs.python.org/2/library/warnings.html
>>
>> Which prints warnings every single time.
>>
>> So, can we please "fix" it in there quickly?
>>
>> Thanks,
>> Dims
>
> This is still a broken release - previously in oslo libraries we have
> been careful with issuing multiple warnings for a deprecation.
>
> This is still an issue, with glance-api [0] and I assume others (e.g. we
> have not had a designate CI run with the new oslo.context yet)
>
> Seen as we are going into RC week, it seems very risky to keep it.
>
> 0 -
> http://logstash.openstack.org/#dashboard/file/logstash.json?query=_id%3A%5C%22AVnnYuy3QVJYkPlRPEJH%5C%22
>
>> On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  
>> wrote:
>>> Hello,
>>>
>>> Thanks. I just filled bug report to oslo project:
>>> https://bugs.launchpad.net/oslo.context/+bug/1660088
>>>
>>> --
>>> Best regards / Pozdrawiam
>>> Sławek Kapłoński
>>> sla...@kaplonski.pl
>>>
>>> On Sat, 28 Jan 2017, Hayes, Graham wrote:
>>>
 On 28/01/17 20:54, Sławek Kapłoński wrote:
> Hello,
>
> I pushed today patch in Neutron to gerrit [1] and I noticed that 
> functional
> tests are failing. In logs there is huge number of deprecation warnings
> displayed [2]. Tests are failing because of global timeout is reached and 
> IMO
> reason of this timeout is this huge amount of deprecation warnings.
> I checked that those warnings are disaplyed when oslo.context==2.12.0 is
> installed. With oslo.context==2.11.0 all is fine.
> Should it be reported as bug in Neutron or in Oslo project? Or maybe You
> already know about it and there is some patch to fix it but I couldn't 
> find it?

 Its an oslo.context bug - I can't see one filed for it yet.
>
> [1] https://review.openstack.org/#/c/426429/
> [2] 
> http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
>

 It looks like the warnings function was miss used - this should be set
 as a once only message. The stack trace level seems suspect, as it
 points as neutron/context.py as the one sending out the notice, not
 oslo.contexts base class.

 [3] seems to the cause - I would suggest reverting this commit and
 doing a 2.13.0 release. This is going to be *really* noisy. (logstash
 has 2.5 million items for this string in the last 24 hours)

 3 -
 https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea

 __
 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



-- 
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

Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

[Kekane, Abhishek]

Congratulations Sharing. .
All the best.

Abhishek

Sent from OWA on Android

From: Brian Rosmaita 
Sent: Thursday, January 26, 2017 8:56:30 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance 
core

Having heard only affirmative responses, I've added Dharini Chandrasekar
to the Glance core group, with all the rights and privileges pertaining
thereto.

Welcome to the Glance core team, Dharini!

On 1/24/17 8:36 AM, Brian Rosmaita wrote:
> I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance
> core.  She has been an active reviewer and contributor to the Glance
> project during the Newton and Ocata cycles, has contributed to other
> OpenStack projects, and has represented Glance in some interactions with
> other project teams.  Additionally, she recently jumped in and saw
> through to completion a high priority feature for Newton when the
> original developer was unable to continue working on it.  Plus, she's
> willing to argue with me (and the other cores) about points of software
> engineering.  She will be a great addition to the Glance core reviewers
> team.
>
> If you have any concerns, please let me know.  I plan to add Dharini to
> the core list after this week's Glance meeting.
>
> thanks,
> 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

__
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

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

[Afek, Ifat (Nokia - IL)]

On 26/01/2017, 20:09, "Julien Danjou"  wrote:

> On Thu, Jan 26 2017, gordon chung wrote:
> 
> > On 26/01/17 11:41 AM, Julien Danjou wrote:
>
> > and vitrage would be an alarm orchestrator?
> 
> Yup, something like that. It could be the one driving Zabbix and
> creating alarms for Zabbix in Aodh when a new host is plugged for
> example.

Vitrage could be enhanced to become an alarm orchestrator. 
The question is – do you want Vitrage to be one? 
And how would you describe the role of an alarm orchestrator/manager? 


__
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][Oslo] Huge number of deprecation warnings in functional tests

[Hayes, Graham]

On 29/01/17 00:53, Davanum Srinivas wrote:
> Graham, Sławek,
> 
> Have you seen this?
> 
> Neutron has/uses a WarningFixture:
> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> 
> Which uses filterwarnings:
> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> 
> Where "always" is being used:
> https://docs.python.org/2/library/warnings.html
> 
> Which prints warnings every single time.
> 
> So, can we please "fix" it in there quickly?
> 
> Thanks,
> Dims

This is still a broken release - previously in oslo libraries we have
been careful with issuing multiple warnings for a deprecation.

This is still an issue, with glance-api [0] and I assume others (e.g. we
have not had a designate CI run with the new oslo.context yet)

Seen as we are going into RC week, it seems very risky to keep it.

0 -
http://logstash.openstack.org/#dashboard/file/logstash.json?query=_id%3A%5C%22AVnnYuy3QVJYkPlRPEJH%5C%22

> On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  wrote:
>> Hello,
>>
>> Thanks. I just filled bug report to oslo project:
>> https://bugs.launchpad.net/oslo.context/+bug/1660088
>>
>> --
>> Best regards / Pozdrawiam
>> Sławek Kapłoński
>> sla...@kaplonski.pl
>>
>> On Sat, 28 Jan 2017, Hayes, Graham wrote:
>>
>>> On 28/01/17 20:54, Sławek Kapłoński wrote:
 Hello,

 I pushed today patch in Neutron to gerrit [1] and I noticed that functional
 tests are failing. In logs there is huge number of deprecation warnings
 displayed [2]. Tests are failing because of global timeout is reached and 
 IMO
 reason of this timeout is this huge amount of deprecation warnings.
 I checked that those warnings are disaplyed when oslo.context==2.12.0 is
 installed. With oslo.context==2.11.0 all is fine.
 Should it be reported as bug in Neutron or in Oslo project? Or maybe You
 already know about it and there is some patch to fix it but I couldn't 
 find it?
>>>
>>> Its an oslo.context bug - I can't see one filed for it yet.

 [1] https://review.openstack.org/#/c/426429/
 [2] 
 http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html

>>>
>>> It looks like the warnings function was miss used - this should be set
>>> as a once only message. The stack trace level seems suspect, as it
>>> points as neutron/context.py as the one sending out the notice, not
>>> oslo.contexts base class.
>>>
>>> [3] seems to the cause - I would suggest reverting this commit and
>>> doing a 2.13.0 release. This is going to be *really* noisy. (logstash
>>> has 2.5 million items for this string in the last 24 hours)
>>>
>>> 3 -
>>> https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
>>>
>>> __
>>> 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-dev] [Senlin] PTL candidacy

[Qiming Teng]

The election of Pike PTL is happening during the Chinese Spring
Festival, so many developers from China are not reachable on radar.

As a community, we have done a lot of amazing work during the Ocata
cycle:

- Versioning everything, especially the engine RPCs
- Support status added to profile type, policy type
- Unified notification for message and event format
- Improved support to health policy
- Improved support to container profile
- and many others

It has been an unusual cycle because it is *very* short. It has been an
amazing cycle for the team because we have more hands working on
different things and we have identified quite some new requirements
for the team to contribute.

In the coming cycle, I'd like to again serve as the team facilitator,
which is called the PTL sometimes. My vision for the Pike cycle is as
follows:

- A mature, supported health policy implementation.
- A better management of the container clusters.
- A better support to the NFV use cases.
- A more comprehensive feature support in the dashboard project.
- A stronger team to take the Senlin project to its next level.

These are just things on top of my head. All ideas are welcomed.

- Qiming Teng


__
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] [vitrage] New Vitrage project mascot

[Yujun Zhang]

Not remembering the original design.

This one looks good to me :-)

On Sun, Jan 29, 2017 at 8:18 PM Afek, Ifat (Nokia - IL) 
wrote:

> Hi,
>
>
>
> This is the new draft of our Giraffe mascot. The illustrators tried to
> make its skin look more like stained glass.
>
> What do you think?
>
>
>
> Ifat.
>
>
>
>
>
>
>
>
>
> __
> 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] [vitrage] New Vitrage project mascot

[Afek, Ifat (Nokia - IL)]

Hi,

This is the new draft of our Giraffe mascot. The illustrators tried to make its 
skin look more like stained glass.
What do you think?

Ifat.

[cid:image001.png@01D27A3A.128CB9B0]




__
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] [Zun] Propose a change of the Zun core team membership

[Qiming Teng]

+1 to both.

On Mon, Jan 23, 2017 at 10:56:00PM +, Hongbin Lu wrote:
> Hi Zun cores,
> 
> I proposed a change of Zun core team membership as below:
> 
> + Kevin Zhao (kevin-zhao)
> - Haiwei Xu (xu-haiwei)
> 
> Kevin has been working for Zun for a while, and made significant 
> contribution. He submitted several non-trivial patches with high quality. One 
> of his challenging task is adding support of container interactive mode, and 
> it looks he is capable to handle this challenging task (his patches are under 
> reviews now). I think he is a good addition to the core team. Haiwei is a 
> member of the initial core team. Unfortunately, his activity dropped down in 
> the past a few months.
> 
> According to the OpenStack Governance process [1], we require a minimum of 4 
> +1 votes from Zun core reviewers within a 1 week voting window (consider this 
> proposal as a +1 vote from me). A vote of -1 is a veto. If we cannot get 
> enough votes or there is a veto vote prior to the end of the voting window, 
> this proposal is rejected.
> 
> [1] https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess
> 
> Best regards,
> Hongbin
> 

> __
> 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] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

I made small patch to Neutron to fix [1] this issue. It looks that
functional tests are fine with it [2].
Please review it if it makes sense for You :)

[1] https://review.openstack.org/#/c/426550/
[2] 
http://logs.openstack.org/50/426550/1/check/gate-neutron-dsvm-functional-ubuntu-xenial/4b56e71/console.html

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sun, 29 Jan 2017, Sławek Kapłoński wrote:

> Hello,
> 
> Thanks for explaining that. I'm don't know this part well and that's why
> I asked here if it's oslo or neutron issue.
> So it looks like it is issue in Neutron nor Oslo.context, right?
> 
> -- 
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
> 
> On Sat, 28 Jan 2017, Joshua Harlow wrote:
> 
> > Yup, all that should be needed is to read the docs and adjust it.
> > 
> > "once" - print only the first occurrence of matching warnings, regardless of
> > location
> > 
> > "always" - always print matching warnings
> > 
> > Changing it to 'once' should gather less repeated logs; IMHO 'always' should
> > never be used, so that was probably just a mistake for whoever committed
> > that fixture with it set like that.
> > 
> > -Josh
> > 
> > Davanum Srinivas wrote:
> > > Graham, Sławek,
> > > 
> > > Have you seen this?
> > > 
> > > Neutron has/uses a WarningFixture:
> > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> > > 
> > > Which uses filterwarnings:
> > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> > > 
> > > Where "always" is being used:
> > > https://docs.python.org/2/library/warnings.html
> > > 
> > > Which prints warnings every single time.
> > > 
> > > So, can we please "fix" it in there quickly?
> > > 
> > > Thanks,
> > > Dims
> > > 
> > > On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  
> > > wrote:
> > > > Hello,
> > > > 
> > > > Thanks. I just filled bug report to oslo project:
> > > > https://bugs.launchpad.net/oslo.context/+bug/1660088
> > > > 
> > > > --
> > > > Best regards / Pozdrawiam
> > > > Sławek Kapłoński
> > > > sla...@kaplonski.pl
> > > > 
> > > > On Sat, 28 Jan 2017, Hayes, Graham wrote:
> > > > 
> > > > > On 28/01/17 20:54, Sławek Kapłoński wrote:
> > > > > > Hello,
> > > > > > 
> > > > > > I pushed today patch in Neutron to gerrit [1] and I noticed that 
> > > > > > functional
> > > > > > tests are failing. In logs there is huge number of deprecation 
> > > > > > warnings
> > > > > > displayed [2]. Tests are failing because of global timeout is 
> > > > > > reached and IMO
> > > > > > reason of this timeout is this huge amount of deprecation warnings.
> > > > > > I checked that those warnings are disaplyed when 
> > > > > > oslo.context==2.12.0 is
> > > > > > installed. With oslo.context==2.11.0 all is fine.
> > > > > > Should it be reported as bug in Neutron or in Oslo project? Or 
> > > > > > maybe You
> > > > > > already know about it and there is some patch to fix it but I 
> > > > > > couldn't find it?
> > > > > Its an oslo.context bug - I can't see one filed for it yet.
> > > > > > [1] https://review.openstack.org/#/c/426429/
> > > > > > [2] 
> > > > > > http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
> > > > > > 
> > > > > It looks like the warnings function was miss used - this should be set
> > > > > as a once only message. The stack trace level seems suspect, as it
> > > > > points as neutron/context.py as the one sending out the notice, not
> > > > > oslo.contexts base class.
> > > > > 
> > > > > [3] seems to the cause - I would suggest reverting this commit and
> > > > > doing a 2.13.0 release. This is going to be *really* noisy. (logstash
> > > > > has 2.5 million items for this string in the last 24 hours)
> > > > > 
> > > > > 3 -
> > > > > https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
> > > > > 
> > > > > __
> > > > > 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
> > 

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

Thanks for explaining that. I'm don't know this part well and that's why
I asked here if it's oslo or neutron issue.
So it looks like it is issue in Neutron nor Oslo.context, right?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sat, 28 Jan 2017, Joshua Harlow wrote:

> Yup, all that should be needed is to read the docs and adjust it.
> 
> "once" - print only the first occurrence of matching warnings, regardless of
> location
> 
> "always" - always print matching warnings
> 
> Changing it to 'once' should gather less repeated logs; IMHO 'always' should
> never be used, so that was probably just a mistake for whoever committed
> that fixture with it set like that.
> 
> -Josh
> 
> Davanum Srinivas wrote:
> > Graham, Sławek,
> > 
> > Have you seen this?
> > 
> > Neutron has/uses a WarningFixture:
> > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> > 
> > Which uses filterwarnings:
> > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> > 
> > Where "always" is being used:
> > https://docs.python.org/2/library/warnings.html
> > 
> > Which prints warnings every single time.
> > 
> > So, can we please "fix" it in there quickly?
> > 
> > Thanks,
> > Dims
> > 
> > On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński  
> > wrote:
> > > Hello,
> > > 
> > > Thanks. I just filled bug report to oslo project:
> > > https://bugs.launchpad.net/oslo.context/+bug/1660088
> > > 
> > > --
> > > Best regards / Pozdrawiam
> > > Sławek Kapłoński
> > > sla...@kaplonski.pl
> > > 
> > > On Sat, 28 Jan 2017, Hayes, Graham wrote:
> > > 
> > > > On 28/01/17 20:54, Sławek Kapłoński wrote:
> > > > > Hello,
> > > > > 
> > > > > I pushed today patch in Neutron to gerrit [1] and I noticed that 
> > > > > functional
> > > > > tests are failing. In logs there is huge number of deprecation 
> > > > > warnings
> > > > > displayed [2]. Tests are failing because of global timeout is reached 
> > > > > and IMO
> > > > > reason of this timeout is this huge amount of deprecation warnings.
> > > > > I checked that those warnings are disaplyed when oslo.context==2.12.0 
> > > > > is
> > > > > installed. With oslo.context==2.11.0 all is fine.
> > > > > Should it be reported as bug in Neutron or in Oslo project? Or maybe 
> > > > > You
> > > > > already know about it and there is some patch to fix it but I 
> > > > > couldn't find it?
> > > > Its an oslo.context bug - I can't see one filed for it yet.
> > > > > [1] https://review.openstack.org/#/c/426429/
> > > > > [2] 
> > > > > http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
> > > > > 
> > > > It looks like the warnings function was miss used - this should be set
> > > > as a once only message. The stack trace level seems suspect, as it
> > > > points as neutron/context.py as the one sending out the notice, not
> > > > oslo.contexts base class.
> > > > 
> > > > [3] seems to the cause - I would suggest reverting this commit and
> > > > doing a 2.13.0 release. This is going to be *really* noisy. (logstash
> > > > has 2.5 million items for this string in the last 24 hours)
> > > > 
> > > > 3 -
> > > > https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
> > > > 
> > > > __
> > > > 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


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