Re: [openstack-dev] [Tacker][OSC] Command naming specs

Hi Jay- Thanks for the suggestions, we have improved this to an extent [1]. For 'openstack vnf service function chain create' we agreed to go with, 'openstack nfv chain create' or 'openstack vnf chain create' For ' openstack vnf forwardinggraph create' , you suggestion sounds good. We are

[openstack-dev] [cinder][stable] Deprecation notice: Cinder Driver for NetApp E-Series

Developers and Operators, NetApp’s various Cinder drivers currently provide platform integration for ONTAP powered systems, SolidFire, and E/EF-Series systems. Per systems-provided telemetry and discussion amongst our user community, we’ve learned that when E/EF-series systems are deployed with

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 4/14/2017 7:12 PM, Rochelle Grober wrote: I just happened to be in a meeting with an associate who is on the TSC of Open Daylight. After the meeting he asked me about the release schedules of OpenStack and whether the recent change was a one off or , would now be offset like the last or..

Re: [openstack-dev] [tc] [elections] Available time and top priority

On Fri, Apr 14, 2017 at 7:12 PM, Rochelle Grober wrote: > Part 1: tldr; publish the resolutions to the key MLs at least when they are > approved. This was done for a time via blog posts, I recall talk about resurrecting that, this may help increate the priority of following up on that thought.

Re: [openstack-dev] [tc] [elections] Available time and top priority

Matt Riedemann, Monday, April 10, 2017 1:41 PM On 4/10/2017 2:55 PM, Dean Troyer wrote: > > The TC meetings are held in IRC and that may somewhat mitigate the > issue for non-native English speakers, but I've had problems myself > keeping up at times with the flurry of comments. In any case, I

Re: [openstack-dev] [shade] help wanted - tons to do, not enough people

On April 14, 2017 1:23 PM Jay Pipes wrote: On 04/12/2017 02:15 PM, Sean Dague wrote: > On 04/12/2017 01:38 PM, Monty Taylor wrote: >> On 04/12/2017 11:21 AM, Joshua Harlow wrote: >>> Just a question, not meant as anything bad against shade, >>> >>> But would effort be better spent on openstacksdk

Re: [openstack-dev] [nova] Usability question for the server migrations API

On 4/14/2017 4:09 PM, Chet Burgess wrote: On Fri, Apr 14, 2017 at 2:01 PM, Matt Riedemann mailto:mriede...@gmail.com>> wrote: On 4/14/2017 3:36 PM, Mathieu Gagné wrote: Can I assume some form of advanced filtering will be proposed to ensure an instance doesn't end up with 1

Re: [openstack-dev] [nova] Usability question for the server migrations API

On Fri, Apr 14, 2017 at 2:01 PM, Matt Riedemann wrote: > On 4/14/2017 3:36 PM, Mathieu Gagné wrote: > >> >> Can I assume some form of advanced filtering will be proposed to >> ensure an instance doesn't end up with 1k records? >> One suggestion would be filtering by date or limiting the number of

Re: [openstack-dev] [nova] Usability question for the server migrations API

On 4/14/2017 3:36 PM, Mathieu Gagné wrote: Can I assume some form of advanced filtering will be proposed to ensure an instance doesn't end up with 1k records? One suggestion would be filtering by date or limiting the number of records returned. The normal pagination filters could be implement

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Does reversion of deps get handled? Thats the primary concern I have. I don't think pip/pbr handle it as deps are external to the package. Containers have deps bundled into the actual build, so need to be accounted for somehow in the tag. Thanks, Kevin Fro

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Or you could use pbr's strategy, which tags based on git tags and revision history: https://docs.openstack.org/developer/pbr/#version "If the currently checked out revision is not tagged, then we take the last tagged version number and increment it to get a minimum target version." Best, -j

Re: [openstack-dev] [nova] Usability question for the server migrations API

On Fri, Apr 14, 2017 at 1:27 PM, Matt Riedemann wrote: > The GET /servers/{server_id}/migrations API only lists in-progress live > migrations. This is an artifact of when it was originally introduced as the > os-migrations API which was tightly coupled with the API operation to > cancel a live mi

Re: [openstack-dev] [nova] Usability question for the server migrations API

The proposal looks reasonable. This could greatly help operation team if a migration no longer vanishes from the API once completed. Can I assume some form of advanced filtering will be proposed to ensure an instance doesn't end up with 1k records? One suggestion would be filtering by date or limi

[openstack-dev] [nova] Usability question for the server migrations API

The GET /servers/{server_id}/migrations API only lists in-progress live migrations. This is an artifact of when it was originally introduced as the os-migrations API which was tightly coupled with the API operation to cancel a live migration. There is a spec [1] which is now approved which pro

Re: [openstack-dev] [shade] help wanted - tons to do, not enough people

On 04/12/2017 02:15 PM, Sean Dague wrote: On 04/12/2017 01:38 PM, Monty Taylor wrote: On 04/12/2017 11:21 AM, Joshua Harlow wrote: Just a question, not meant as anything bad against shade, But would effort be better spent on openstacksdk? tl;dr - great in practice, falls apart in the details

Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

On Tue, Apr 11, 2017 at 06:48:52PM -0400, Paul Belanger wrote: > On Tue, Apr 04, 2017 at 01:02:59PM -0400, Paul Belanger wrote: > > Greetings, > > > > Recently we've been running into some issues keeping our EPEL mirror > > properly > > sync'd. We are working to fix this, however we'd also like t

Re: [openstack-dev] [Tacker][OSC] Command naming specs

On 04/12/2017 03:08 AM, Trinath Somanchi wrote: Hi OSC team- While implementing tacker-cli commands as OSC plugins [1], We are struck in command naming specifications. Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the prefix. It's not *all* of NFV, though. This problem,

Re: [openstack-dev] [libvirt] Whether kvm supports NVIDIA VGPU

On 04/12/2017 10:53 PM, 文峰sx-9149 wrote: Will the openstack or libvirt (kvm) support NVIDIA VGPU? I am here to see a mail introduction libvirt kvm support VGPU. But I do not know the current development situation of this f

[openstack-dev] [glance] priorities for the coming week (04/14-04/20)

I'm going to keep the list light this week. Use your reviewing time as you see fit and hopefully we can show some love to non-priority items that have been sitting a while for glance_store and python-glanceclient. Additionally: 1. Spec freeze extension: as you saw in an earlier email, the spec f

[openstack-dev] [ironic] Save the date: Ironic virtual meetup on Apr 25

Hi all! The voting for the meetup date is over. There was a tie with 4 days all having 13 votes each, so I've just picked the closest one. There were not enough people for the 00:00 UTC timeslot, so we ended up with only one: Apr 25 (Tue): 15:00 UTC - 19:00 UTC We'll use conference room 777

[openstack-dev] [ironic] [third-party-ci] pkvmci ironic job breakage details

Hey ironic-ers, So our third party CI job for ironic has been, and remains, broken. I was able to do some investigation today and here's a summary of what we're seeing. I'm hoping someone might know the root of the problem. For reference, please see this paste and the logs of the job that I w

[openstack-dev] [nova][deployment] FYI: changes to cells v2 setup guide (pike only)

Nova is working on adding multi-cell aware support to the compute API. A side effect of this is we can now have a chicken-and-egg situation during deployment such that if your tooling is depending on the compute API to list compute hosts, for example, before running the discover_hosts command,

Re: [openstack-dev] [tc][elections]questions about one platform vision

On Fri, Apr 14, 2017 at 9:50 AM, Dean Troyer wrote: > [0] https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/ > [1] > https://governance.openstack.org/tc/reference/principles.html#one-openstack Rats, I missed the UC charter: [2] https://governance.openstack.org/uc/reference/char

Re: [openstack-dev] [tc][elections]questions about one platform vision

On Fri, Apr 14, 2017 at 3:34 AM, Thierry Carrez wrote: > Like all analogies, this one is not perfect (in particular it horribly > fails to capture the "open" nature of the stack), but I think it's still > useful to inform on what OpenStack is. On the other hand I do think it captures the common f

Re: [openstack-dev] [all][elections] Voting for the TC Election is now open

Hello Again, It seems there is a small issue with the name of the poll that was sent out. It's been misnamed 'OpenStack Technical Committee (TC) Election - October 2016' where it should have been named 'OpenStack Technical Committee (TC) Election - April 2017'. However, all other information about

Re: [openstack-dev] [neutron][l3] Conntrackd in L3 HA ?

On Fri, Apr 14, 2017 at 3:16 AM, zhi wrote: > hi, all. > > I have a question about conntrackd in L3 HA. I read document about L3 HA > at [1] and I find " conntrack " in L3 HA diagram . Does neutron L3 HA > support conntrackd currently? If so, how > can I find the conntrack info? > It does not.

Re: [openstack-dev] [all] [tc] Technical Committee Vision draft

On Fri, Apr 14, 2017 at 12:55 PM, Jeremy Stanley wrote: > It's intentionally ambitious, yes, because we want to inspire and be > inspired to great achievements. I generally don't think that that approach works for a large community, except in the rare cases of where you have both an utterly awe-i

Re: [openstack-dev] [all] [tc] Technical Committee Vision draft

On 04/14/2017 06:55 AM, Jeremy Stanley wrote: > On 2017-04-14 12:32:50 +0200 (+0200), Florian Haas wrote: > [...] >> I am not sure whether Gerrit is the appropriate place to make >> the following comment, so I'm taking the liberty to post this here. > > We are paying attention pretty much everywhe

Re: [openstack-dev] [nova] placement/resource providers update 19

On Fri, 14 Apr 2017, Chris Dent wrote: # Other Code/Specs Missed one: * https://review.openstack.org/#/c/455710/ A fix to some issues with CONTENT_LENGTH and CONTENT_TYPE when running under nginx+uwsgi. -- Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/ freenode: cd

Re: [openstack-dev] [all] [tc] Technical Committee Vision draft

On 2017-04-14 12:32:50 +0200 (+0200), Florian Haas wrote: [...] > I am not sure whether Gerrit is the appropriate place to make > the following comment, so I'm taking the liberty to post this here. We are paying attention pretty much everywhere, so comments where and when feels most appropriate to

Re: [openstack-dev] [all] [tc] Technical Committee Vision draft

On Wed, Apr 5, 2017 at 11:46 AM, Thierry Carrez wrote: > Hi everyone, > > Last year in Ann Arbor, a group of OpenStack community members > (including 6 current TC members) attended a Servant Leadership training > at ZingTrain organized by Colette Alexander and funded by the OpenStack > Foundation.

[openstack-dev] [nova] placement/resource providers update 19

Here's the 19th placement and resource providers update. As usual, if I've left anything out, please followup with that information. # What Matters Most Discussion continues on the spec for claims being done during scheduling. Getting this worked out and implemented is a high priority. Links be

[openstack-dev] [release] Release countdown for week R-19, R-18 and R-17, April 17 - May 5

Welcome to our regular release countdown email! Development Focus - With the Pike-1 milestone behind us, teams should be focused on feature development and completion of release goals. Actions --- Now is a good time to review stable/newton and stable/ocata branches for any n

Re: [openstack-dev] [tc][elections]questions about one platform vision

Ildiko Vancsa wrote: >> […] >> What's the one platform will be in your own words? What's your >> proposal and your focus to help one platform vision being achieved? > > In my view it means that OpenStack contains the blocks to build > platforms that can serve as a base for different use cases and

Re: [openstack-dev] [tc] version document for project navigator

Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-04-13 18:03:41 +0200: >> Monty Taylor wrote: >>> On 04/13/2017 08:28 AM, Jimmy McArthur wrote: Just checking on the progress of this. :) >>> >>> Unfortunately a good portion of the TC was away this week at the >>> leadership

[openstack-dev] [neutron][l3] Conntrackd in L3 HA ?

hi, all. I have a question about conntrackd in L3 HA. I read document about L3 HA at [1] and I find " conntrack " in L3 HA diagram . Does neutron L3 HA support conntrackd currently? If so, how can I find the conntrack info? Many Thanks Zhi Chang [1]: https://wiki.openstack.org/wiki/Neutron/L3