Re: [openstack-dev] 答复: [heat] glance v2 support?

On 12/01/17 08:11 -0500, Zane Bitter wrote: On 11/01/17 10:01, Thomas Herve wrote: On Wed, Jan 11, 2017 at 3:34 PM, Emilien Macchi wrote: On Wed, Jan 11, 2017 at 2:50 AM, Thomas Herve wrote: I think this is going where I thought it would: let's not do

Re: [openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

+1 2017-01-21 3:07 GMT+04:00 Emilien Macchi : > plus one > > On Fri, Jan 20, 2017 at 12:19 PM, Alex Schultz > wrote: > > Hey Puppet Cores, > > > > I would like to nominate Zhong Shengping as a Core reviewer for the > > Puppet OpenStack modules. He is an

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

On 19/01/17 12:48 +0300, Mikhail Fedosin wrote: Hi Matt! This should be discussed, for sure, but there is a lot of potential. In general, it depends on how far we are willing to go. In the minimum approximation we can seamlessly replace Glance with Glare and operators simply get additional

Re: [openstack-dev] [ironic-pyhon-agent][DIB] IPA failed to start on Ubuntu because of modprobe path

Ian Wienand said on Mon, Jan 23, 2017 at 02:26:36PM +1100: This should be just "/sbin"; I've proposed [1]. There may be even better ways to do this which anyone is welcome to propose :) +1 The problem with distributions not following anymore the FHS closely (and not working jointly on it to

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

Thanks John for the info. I am going through the spec in detail. And before that, I had few thoughts about how I wanted to approach this, which I have drafted in https://etherpad.openstack.org/p/tripleo-derive-params. And it is not 100% ready yet, I was still working on it. As of now, there are

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Hi Kris, Thanks for the feedback, I think everyone involved in kolla-ansible should take the time to read through it, as it definitely highlights some areas that we need to improve. There's a lot of questions here, so I haven't gone into too much detail on any specific one; my hope is that

[openstack-dev] [cloudkitty] [ptl] Candidacy for cloudkitty PTL

Hello everyone, I would like to announce my candidacy for PTL of Cloudkitty. During the Ocata cycle we have been able open up our community with the integration of some new contributors and new cores from different companies (which was a key from my point of view). We also have been to add

Re: [openstack-dev] [yaql] Yaql validating performance

Hi Renat, For more details, i will go to check on the CBAM machine and hope it is not deleted yet since we have done it for around a week. Another thing is Jinja2 showed us that it run 2-3 times faster with the same test with YAQL. More information i will also provide it later. Br, Tuan On

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

On 01/23/2017 11:07 AM, Saravanan KR wrote: > Thanks John for the info. > > I am going through the spec in detail. And before that, I had few > thoughts about how I wanted to approach this, which I have drafted in > https://etherpad.openstack.org/p/tripleo-derive-params. And it is not > 100%

[openstack-dev] [all] PTG deadline reminders

Hi everyone, The PTG is less than a month away ! We have two deadlines coming up this week. First, if you haven't registered yet but intend to come, you should probably book now. There are less than 65 tickets left as of this morning, so it is very likely to sell out soon. Prices will also

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

Yes, to do it differently we need to add the microversion support patch that you are working on, and make use of it, or write a patch that has equivalent functionality. On Fri, Jan 20, 2017 at 6:57 PM, Rob Cresswell wrote: > Just a thought: With the way we

Re: [openstack-dev] [Performance][Shaker]

Hi Sai, In UDP testing PPS represents packets sent by iperf client to server. Loss is the percentage of packets that were not received by server (more specifically the server tracks packets and sums gaps between of them, https://github.com/esnet/iperf/blob/3.0.7/src/iperf_udp.c#L64). While

Re: [openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

+1 2017-01-23 5:49 GMT-03:00 Ivan Berezovskiy : > +1 > > 2017-01-21 3:07 GMT+04:00 Emilien Macchi : > >> plus one >> >> On Fri, Jan 20, 2017 at 12:19 PM, Alex Schultz >> wrote: >> > Hey Puppet Cores, >> > >> > I would like to

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

Le 23/01/2017 15:11, Jay Pipes a écrit : > On 01/22/2017 04:40 PM, Sylvain Bauza wrote: >> Hey folks, >> >> tl;dr: should we GET /resource_providers for only the related resources >> that correspond to enabled filters ? > > No. Have administrators set the allocation ratios for the resources

Re: [openstack-dev] [tripleo] tripleoclient release : January 26th

Reminder: we'll release tripleoclient this week. Please let us know any blocker! Thanks, On Mon, Jan 16, 2017 at 9:32 AM, Emilien Macchi wrote: > One day I'll read calendars correctly :-) > Client releases are next week, so we'll release tripleoclient by January 26th. > >

[openstack-dev] [keystone]Error while setting up a keystone development environment

Hello, I'm new to all this and I am in need of help to find out where I went wrong. This is a bit lengthy, I have left a blank space between the text and the error messages I received. I first set up and activated a virtual environment then cloned the keystone project into that environment. I

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

On 01/22/2017 04:40 PM, Sylvain Bauza wrote: Hey folks, tl;dr: should we GET /resource_providers for only the related resources that correspond to enabled filters ? No. Have administrators set the allocation ratios for the resources they do not care about exceeding capacity to a very high

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

On Wed, 18 Jan 2017, Chris Dent wrote: The review starts with the original text. The hope is that commentary here in this thread and on the review will eventually lead to the best document. https://review.openstack.org/#/c/421846 There's been a bit of commentary on the review which I'll

Re: [openstack-dev] [tripleo] Atlanta PTG

On 01/21/2017 05:37 AM, Michele Baldessari wrote: > Hi Emilien, > > while not a design session per se, I would love to propose a short slot > for TripleO CI Q, if we have some time left. In short, I'd like to be > more useful around CI failures, but I lack the understanding of a few > aspects

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

Le 22/01/2017 22:40, Sylvain Bauza a écrit : > Hey folks, > > tl;dr: should we GET /resource_providers for only the related resources > that correspond to enabled filters ? Explanation below why even if I > know we have a current consensus, maybe we should discuss again about it. > > > I'm

Re: [openstack-dev] [Neutron] PTL Candidacy

On 01/22/2017 09:35 PM, Kevin Benton wrote: I would like to propose my candidacy for the Neutron PTL. I have been contributing to Neutron since the Havana development cycle working for a network vendor and then a distribution vendor. I have been a core reviewer since the Kilo development cycle

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

On 01/23/2017 08:11 AM, Chris Dent wrote: > On Wed, 18 Jan 2017, Chris Dent wrote: > >> The review starts with the original text. The hope is that >> commentary here in this thread and on the review will eventually >> lead to the best document. > > https://review.openstack.org/#/c/421846 >

[openstack-dev] [charms][ptl] PTL candidacy

Hi All I would like to announce my candidacy for PTL of the OpenStack Charms project. Over the Ocata cycle, we've been incubating the community of developers around the Charms, with new charms for Murano, Trove, Mistral and CloudKitty all due to be included in the release in February. We've

Re: [openstack-dev] [congress] ocata client causes feature regression with pre-ocata server

At some point the client sometimes made multiple API calls. I think (c) seems right too. Tim On Sun, Jan 22, 2017 at 1:15 AM Monty Taylor wrote: > On 01/21/2017 04:07 AM, Eric K wrote: > > Hi all, > > > > I was getting ready to request release of congress client, but I >

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

On 01/21/2017 03:00 AM, Marco Marino wrote: Really thank you!! It's difficult for me find help on cinder and I think this is the right place! @Duncan, if my goal is to speeding up bootable volume creation, I can avoid to use thin provisioning. I can use image cache and in this way the "retrieve

Re: [openstack-dev] [ocatvia]Newton Octavia lbaas creation error

Santhosh, >From the traceback below it looks like the neutron process is unable to access >keystone. 2017-01-22 12:21:51.569 14448 ERROR neutron.api.v2.resource DriverError: Driver error: Unable to establish connection to http://127.0.0.1:5000/v2.0/tokens:

Re: [openstack-dev] [octavia] Nominating German Eichberger for Octavia core reviewer

With that vote we have quorum. Welcome back German! Michael From: Kosnik, Lubosz [mailto:lubosz.kos...@intel.com] Sent: Sunday, January 22, 2017 12:24 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [ocatvia]Newton Octavia lbaas creation error

Thanks Michael, After adding service_auth section in neutron.conf I was able overcome this error. Now I am getting new exception Unable to retrieve ready devices. Here is the stacktrace. http://paste.openstack.org/show/596019/ Any clue to resolve this issue. Thanks, Santhosh On Mon, Jan 23,

[openstack-dev] [Magnum] Feature freeze coming today

Team, I will be starting our feature freeze today. We have a few more patches to consider for merge before we enter the freeze. I’ll let you all know when each has been considered, and we are ready to begin the freeze. Thanks, Adrian

Re: [openstack-dev] [containers][magnum] Magnum team at Summit?

Hi Adrian, I'm unlikely to attend the PTG myself but James Page and other members of our team will be there who can help cover. Certainly we'd like to better understand what the cluster drivers need from the underlying operating system and what we need to do to make sure Ubuntu does all those

[openstack-dev] [octavia] PTL candidacy for Pike series

Hello Octavia folks, I wanted to let you know that I am running for the PTL position again for Pike. My candidacy statement is available here: https://git.openstack.org/cgit/openstack/election/plain/candidates/pike/Octa via/johnsom.txt Thank you for your consideration, Michael

Re: [openstack-dev] [keystone]Error while setting up a keystone development environment

why not use devstack [1] with a minimal local.conf (used to specify which components to install) ? [1] http://docs.openstack.org/developer/devstack/ minimal local.conf: [[local|localrc]] RECLONE=yes # Credentials DATABASE_PASSWORD=openstack ADMIN_PASSWORD=openstack SERVICE_PASSWORD=openstack

Re: [openstack-dev] [yaql] Yaql validating performance

Hi guys, I am provide some information about the result of testing YAQL performance on my devstack stable/newton with RAM of 6GB. The workflow i created is below: # input: - size - number_of_handovers tasks: generate_input:

[openstack-dev] [vitrage] Vitrage Hands-On Webinar

Hi, Nokia is hosting a Webinar about Vitrage, tomorrow January 24th at 10:00 a.m. EDT/ 5:00 pm, Northern Europe Time. This will be a hands-on lab, where Dan Offek (a Vitrage core developer) will present an overview of what Vitrage is all about, and guide you through the process of installing,

[openstack-dev] [nova] Announcing my PTL candidacy for Pike

Hi everyone, This is my self-nomination to continue running as Nova PTL for the Pike cycle. If elected, this would be a third term for me as Nova PTL. In Ocata I thought that I did a better job of keeping on top of a broader set of efforts than I was able to in Newton, including several

Re: [openstack-dev] [nova] Announcing my PTL candidacy for Pike

+1 to "mentoring people that are newer to Nova but are stepping into leadership positions" Matt. Thanks, Dims On Mon, Jan 23, 2017 at 1:54 PM, Matt Riedemann wrote: > Hi everyone, > > This is my self-nomination to continue running as Nova PTL for the Pike > cycle. > >

[openstack-dev] [tc][swg] Sessions for Atlanta PTG - writing a TC Vision/Other options

Hello Stackers, As we move into the last four weeks of work before the PTG in Atlanta, I wanted to check in to talk about what the Stewardship Working Group has planned and what we're looking to accomplish during our one day (Monday) at the gathering. Currently, discussing among SWG members has

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

An alternative could also be, for Newton and earlier, to release a note saying that operators should not run the code against ENFORCING galera mode. What are the reasons to enable that mode in OpenStack scope that would not allow operators to live without it for another cycle? Ihar On Mon, Jan

[openstack-dev] [tripleo] Update TripleO core members

Greeting folks, I would like to propose some changes in our core members: - Remove Jay Dobies who has not been active in TripleO for a while (thanks Jay for your hard work!). - Add Flavio Percoco core on tripleo-common and tripleo-heat-templates docker bits. - Add Steve Backer on

[openstack-dev] [neutron] grenade failures in the gate

Hi neutrinos, We spotted [1] in the gate. Please wait for its resolution until pushing patches into the merge queue. Thanks, Armando [1] https://bugs.launchpad.net/neutron/+bug/1658806 __ OpenStack Development Mailing List

[openstack-dev] [cinder][nova] Cinder-Nova API changes meeting

Hi All, Unfortunately our current meeting slot (every Monday 1700UTC) is in collision for several of the regular attendees. In an attempt to find a new slot I checked the available meeting channels for the same time slot over the week and we have at least on available currently for each day.

Re: [openstack-dev] [Neutron] PTL Candidacy

On 18:35 Jan 22, Kevin Benton wrote: > I would like to propose my candidacy for the Neutron PTL. > > I have been contributing to Neutron since the Havana development > cycle working for a network vendor and then a distribution vendor. > I have been a core reviewer since the Kilo development cycle

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

[I'm on vacation, so can't look into this too deeply, sorry] I'm not sure I follow Rob's point here. Does the patch https://review.openstack.org/#/c/410337 just check the version to see if it's >= 2.40 and take action appropriately? I don't see how it changes anything to force requesting 2.40

Re: [openstack-dev] [Performance][Shaker]

Thanks Ilya! On Mon, Jan 23, 2017 at 6:56 AM, Ilya Shakhat wrote: > Hi Sai, > > In UDP testing PPS represents packets sent by iperf client to server. Loss > is the percentage of packets that were not received by server (more > specifically the server tracks packets and

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are jittery 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. nova patch for

Re: [openstack-dev] [tripleo] Update TripleO core members

On 01/23/2017 12:03 PM, Emilien Macchi wrote: > Greeting folks, > > I would like to propose some changes in our core members: > > - Remove Jay Dobies who has not been active in TripleO for a while > (thanks Jay for your hard work!). > - Add Flavio Percoco core on tripleo-common and

Re: [openstack-dev] [neutron] grenade failures in the gate

On 2017-01-23 13:38:58 -0800 (-0800), Armando M. wrote: > We spotted [1] in the gate. Please wait for its resolution until pushing > patches into the merge queue. https://review.openstack.org/424323 seems to be the fix, and will hopefully merge shortly along with its dependency (they're at the

[openstack-dev] [openstack-ansible] [ptl] PTL Candidacy for Pike

Hi All, I'm once again running for the PTL position for OpenStack-Ansible during the Pike cycle. Here is my candidacy statement: https://review.openstack.org/#/c/424348/ Thanks for all your support during the Ocata cycle, and looking forward to Pike! Andy

[openstack-dev] [magnum] PTL nomination is open until Jan 29

Hi all, I sent this email to encourage you to run for the Magnum PTL for Pike [1]. I think most of the audience are in this ML so I sent the message to here. First, I would like to thank for your interest in the Magnum project. It is great to work with you to build the project and make it

[openstack-dev] Sabari Murugesan stepping down from Glance core

Sabari Murugesan has communicated to me that he's no longer able to commit time to working on Glance, and he's stepping down from the core reviewers' team. This message isn't all bad news, however: I'm particularly grateful that Sabari has agreed to continue as the VMware driver maintainer for

Re: [openstack-dev] [Zun] Propose a change of the Zun core team membership

＋1 for the change. 2017-01-24 6:56 GMT+08:00 Hongbin Lu : > 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

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

Le 23/01/2017 15:18, Sylvain Bauza a écrit : > > > Le 23/01/2017 15:11, Jay Pipes a écrit : >> On 01/22/2017 04:40 PM, Sylvain Bauza wrote: >>> Hey folks, >>> >>> tl;dr: should we GET /resource_providers for only the related resources >>> that correspond to enabled filters ? >> >> No. Have

[openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Hi community, I created a loadbalancer with a listener with protocol as "TERMINATED_HTTPS" and specify --default-tls-container-ref with a ref of secret container from Barbican. However, after I deleted the listener, the lbaas wasn't removed from barbican container consumer list. $openstack

Re: [openstack-dev] [neutron] grenade failures in the gate

On 23 January 2017 at 13:50, Jeremy Stanley wrote: > On 2017-01-23 13:38:58 -0800 (-0800), Armando M. wrote: > > We spotted [1] in the gate. Please wait for its resolution until pushing > > patches into the merge queue. > > https://review.openstack.org/424323 seems to be the

Re: [openstack-dev] [Zun] Propose a change of the Zun core team membership

+1 for this change. -- Eli Qiao Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Tuesday, 24 January 2017 at 6:56 AM, 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) > >

Re: [openstack-dev] [congress] ocata client causes feature regression with pre-ocata server

Thanks Tim and Monty! I also agree with ( c ). Here’s a simple patch doing that: https://review.openstack.org/#/c/424385/ From: Tim Hinrichs Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday, January 23,

Re: [openstack-dev] [tricircle]Pike design topics discussion

Hello, (Repost) As what's discussed during the weekly meeting, let's discuss what's to do in Pike in etherpad next Tuesday morning UTC 1:30 am (9:30am Beijing time, 10:30 Korea/Japan time, Monday 5:30pm PST time) The etherpad link https://etherpad.openstack.org/p/tricircle-pike-design-topics

[openstack-dev] [Zun] Propose a change of the Zun core team membership

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

[openstack-dev] [tripleo] Release notes for THT (need help)

I've made progress on Ocata release notes for TripleO Heat Templates: https://review.openstack.org/424365 I need some help to add some features that I wasn't sure about wording, please help (in a patch on top of it or in review), asap please. I'm looking at containers,

[openstack-dev] [nova][bugs] Nova Bugs Team Meeting this Tuesday Cancelled

I've had a scheduling conflict and need to cancel the next Nova Bugs Team meeting. If anyone is interested in running the meeting in my place since it's been awhile, please feel free to reach out to me via email or IRC. -- Augustina Ragwitz Señora Software Engineer --- Waiting for your change to

[openstack-dev] [storlets][ptl] PTL candidacy

Hi All, I have been leading the Storlets project from its infancy days as a research project in IBM to its infancy days as a big-tent project :-) This would not have been possible without the small yet top and seasoned developers in our community. There is still very much I would like to do:

Re: [openstack-dev] [yaql] Yaql validating performance

Ok, thanks. That looks more clear now. Renat Akhmerov @Nokia > On 24 Jan 2017, at 14:15, lương hữu tuấn wrote: > > Hi Renat, > > In short, it is the expression: output: <% $.data %> > > I would like to post the workflow too since it would make more sense to >

Re: [openstack-dev] [yaql] Yaql validating performance

Hi Renat, In short, it is the expression: output: <% $.data %> I would like to post the workflow too since it would make more sense to understand the whole picture(IMHO :)). In this case, it would be that the data is too big, AFAIK is around 2MB. Therefore i would just wanna know more

Re: [openstack-dev] [ python-novaclient][ python-glanceclient][ python-cinderclient][ python-neutronclient] Remove x-openstack-request-id logging code as it is logged twice

Hi Dims, Thank you for the update. As of now patches for updating requirements.txt in individual clients has been proposed by bot, out of which patch for python-novaclient is already merged. Following patches are still in review queue: Python-glanceclient:

Re: [openstack-dev] [yaql] Yaql validating performance

While I’m in the loop regarding how this workflow works others may not be. Could please just post your expression and data that you use to evaluate this expression? And times. Workflow itself has nothing to do with what we’re discussing. Renat Akhmerov @Nokia > On 23 Jan 2017, at 21:44, lương

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

Thanks Giulio for adding it to PTG discussion pad. I am not yet sure of my presence in PTG. Hoping that things will fall in place soon. We have spent a considerable about of time in moving from static roles to composable roles. If we are planning to introduce static profiles, then after a while

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

What I don't understand is why the OOM killer is being invoked when there is almost no swap space being used at all. Check out the memory output when it's killed:

Re: [openstack-dev] [Zun] Propose a change of the Zun core team membership

+1, welcome Kevin. I appreciate your work. On Tuesday, January 24, 2017, Yanyan Hu wrote: > ＋1 for the change. > > 2017-01-24 6:56 GMT+08:00 Hongbin Lu >: > >> Hi Zun cores, >> >> >> >> I

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

At the moment I have: volume_clear=zero volume_clear_size=30 <-- MBR will be deleted here! with tick provisioning I think this can be a good solution in my case. Let me know what do you think about this. Thank you Marco 2017-01-23 17:21 GMT+01:00 Chris Friesen : >

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

On 01/23/2017 11:29 AM, Marco Marino wrote: At the moment I have: volume_clear=zero volume_clear_size=30 <-- MBR will be deleted here! with tick provisioning I think this can be a good solution in my case. Let me know what do you think about this. If security is not a concern then that's fine.

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Hi Paul, Thanks for responding. > The fact gathering on every server is a compromise taken by Kolla to > work around limitations in Ansible. It works well for the majority of > situations; for more detail and potential improvements on this please > have a read of this post: >

[openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Hello everyone! Guys in our team faced an issue when they try to run alembic migrations on Galera with ENFORCING mode. [1] This was an issue with Alembic [2], which was quickly fixed by Mike Bayer (many thanks!) and new version of alembic was resealed [3]. The global requirements are updated