Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

Thanks for the investigation. I see two things: * I have forgotten than pushing tag will build the tarball automatically. * I have thought I should do the tagging manually because of [1] For the second point, if I was wrong and we should continue to use the release repo, I have prepared two re

[openstack-dev] Boston Forum Schedule Online

Hello all, The schedule for our the Forum is online: https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 ==> Session moderators, please start advertising your sessions & starting pre-discussions, to get the best, most well-informed people there possible! ==> Anyone els

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

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 feature. Who can tell me about VGPU in  Openstack?Thanks.

Re: [openstack-dev] [tripleo][deployment][helm][kolla][openstack-ansible] paunch - a library/tool for yaml driven docker configuration

[adding more tags to make sure folks can see this thread] What we would like to hear from Deployment projects (Kolla, OSA, Helm, etc) is: 1) Is there any overlap with some ongoing efforts? 2) Would you be interested by contributing to this effort? Any feedback is welcome, Thanks. On Wed, Apr 12

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

networking-sfc has many overlapping areas with tacker and the command names can conflict, so I believe it is worth shared in this thread. networking-sfc team is now implementing OSC commands (as neutronclient OSC plugin). Their command name proposal can be found at https://review.openstack.org/#/c

[openstack-dev] [tripleo] paunch - a library/tool for yaml driven docker configuration

This is just a heads-up that in a week or so I intend to propose a new git repo to be hosted by OpenStack and adopted by the TripleO project. paunch [1] is a python library and CLI tool which forklifts the logic of the docker-cmd heat-agents hook[2] into its own project. The change to switch the

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

On Thu, Apr 13, 2017 at 10:59 AM, Michał Jastrzębski wrote: > My dear Kollegues, > > Today we had discussion about how to properly name/tag images being > pushed to dockerhub. That moved towards general discussion on revision > mgmt. > > Problem we're trying to solve is this: > If you build/push

Re: [openstack-dev] [tc][election] Questions for Candidates

On Thu, Apr 13, 2017 at 2:19 AM, Kendall Nelson wrote: > Hello Candidates! > > You all have proven yourselves to be crucial parts of the community and I > just wanted to say good luck to each one of you in the upcoming election! > > Also though, I thought it might be good to ask a few more questi

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

+1, yay! :-) On Thu, Apr 13, 2017 at 2:46 AM, Doug Hellmann wrote: > Excerpts from Monty Taylor's message of 2017-04-12 08:14:31 -0500: > > Hey all, > > > > As I'm sure you all know, pbr is both our most pervasively used > > dependency and our least well understood. Nobody ever wants to look at

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

On Wed, Apr 12, 2017 at 05:27:13PM -0500, Jay S Bryant wrote: > I also didn't receive an e-mail. :-( > I don't think we need to perpetuate this thread for everybody that didn't get it. I think it's safe to see that a large number of folks have not recieved the email. (Me included) :) __

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

Interesting to know the idea considering OpenStack as group of constellations. Does it mean even Nova/Cinder/Neutron are not necessary to be tied together in some user cases? Seems that "one platform" has not been got consensus yet. But the marketing material of OpenStack is claiming "one platf

Re: [openstack-dev] [tc][election] Questions for Candidates

On Wed, Apr 12, 2017 at 04:19:55PM +, Kendall Nelson wrote: > Hello Candidates! > > You all have proven yourselves to be crucial parts of the community and I > just wanted to say good luck to each one of you in the upcoming election! > > Also though, I thought it might be good to ask a few mo

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Apr 12, 2017 at 02:27:22PM +, gordon chung wrote: > i imagine you can EOL python-aodhclient and ceilometermiddleware. thanks Thanks I've added those repos/projects. Yours Tony. signature.asc Description: PGP signature

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Apr 12, 2017 at 04:06:36PM +0200, Andreas Jaeger wrote: > Please add openstack-manuals to the list for EOL, Thanks Added! Yours Tony. signature.asc Description: PGP signature __ OpenStack Development Mailing List (n

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote: > Please EOL the Puppet OpenStack projects that have the stable/mitaka branch. Thanks Alex! I've added: openstack/puppet-aodh openstack/puppet-ceilometer openstack/puppet-cinder openstack/puppet-designate openstack/puppet-glance opens

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

On Wed, Apr 12, 2017 at 07:05:42PM +0900, Ildiko Vancsa wrote: > > As a version of this idea, I was thinking of an #openstack-tc IRC channel, > but wanted to give it another thought before bringing it up. :) While I don’t > have the intention to necessarily increase the number of IRC channels we

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

On 4/12/2017 3:40 PM, Steven Dake (stdake) wrote: Matt, Thanks for the response. It is helpful. Regards -steve -Original Message- From: Matt Riedemann Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, April 12, 2017 at 4:36 PM To: "openstack-

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

But if we don’t prefix, then we are afraid we might confuse users with command names and conflict with other projects. Example, ‘network-service’ if we follow the existing way, then $> openstack network service create might confuse the user in context that it’s a neutron/net

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

+1 to revision information in tags. If you don't have it, depending on when containers start, you could have different versions of software with/without bug fixes running on the same cluster without an easy way to know. We've seen this with libvirt versions being 1.x in some builds and 2.x in f

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

My dear Kollegues, Today we had discussion about how to properly name/tag images being pushed to dockerhub. That moved towards general discussion on revision mgmt. Problem we're trying to solve is this: If you build/push images today, your tag is 4.0 if you do it tomorrow, it's still 4.0, and wil

Re: [openstack-dev] [kolla][all][tc] Starting a core reviewer mentorship program for Kolla deliverables

I was also thinking of having "cores just for single thing" in Kolla, but I think that won't really work as most of our code is variation of other parts with very little unique things to this, it's tuning up details that takes most of our work (aside of already split kolla-ansible and kolla-kuberne

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

I also didn't receive an e-mail. :-( On 4/12/2017 1:33 PM, Kevin Benton wrote: I haven't received one either. Perhaps Monty has simply embraced the 'cattle not pets' approach and we were the unlucky ones. :) On Apr 12, 2017 07:49, "Lance Bragstad" > wrote:

Re: [openstack-dev] [nova] Contributing support for Netronome Agilio adaptors

Hi, Apologies for leaving this to the very last minute. The blueprint and spec has been submitted for your consideration to: https://blueprints.launchpad.net/nova/+spec/netronome-smartnic-enablement https://review.openstack.org/#/c/456386/ We're in the final steps of getting the permission to

Re: [openstack-dev] [TripleO][Heat] Conditionally passing properties in Heat

On 04/12/2017 01:22 PM, Thomas Herve wrote: > On Wed, Apr 12, 2017 at 9:00 PM, Dan Sneddon wrote: >> I'm implementing predictable control plane IPs for spine/leaf, and I'm >> running into a problem implementing this in the TripleO Heat templates. >> >> I have a review in progress [1] that works, b

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

Matt, Thanks for the response. It is helpful. Regards -steve -Original Message- From: Matt Riedemann Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, April 12, 2017 at 4:36 PM To: "openstack-dev@lists.openstack.org" Subject: Re: [openstack-de

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

On 4/12/2017 11:59 AM, Steven Dake (stdake) wrote: Hey folks, In today’s Kolla team meeting, the idea was proposed of adopting nova’s “protocore” mentorship program for Kolla. We would like to know what nova has learned from this effort. In today’s Kolla meeting we had broad consensus on t

Re: [openstack-dev] Ocata - Ubuntu 16.04 - OVN does not work with DPDK

On 11 April 2017 at 11:08, Russell Bryant wrote: > > > On Mon, Apr 10, 2017 at 4:49 PM, Martinx - ジェームズ < > thiagocmarti...@gmail.com> wrote: > >> >> >> On 8 April 2017 at 00:37, Martinx - ジェームズ >> wrote: >> >>> Guys, >>> >>> I manage to deploy Ocata on Ubuntu 16.04 with OVN for the first time

Re: [openstack-dev] [TripleO][Heat] Conditionally passing properties in Heat

On Wed, Apr 12, 2017 at 9:00 PM, Dan Sneddon wrote: > I'm implementing predictable control plane IPs for spine/leaf, and I'm > running into a problem implementing this in the TripleO Heat templates. > > I have a review in progress [1] that works, but fails on upgrade, so I'm > looking for an alter

Re: [openstack-dev] [nova][cinder] Can all non-Ironic compute drivers handle volume size extension?

On Wed, Apr 12, 2017 at 2:54 PM, Matt Riedemann wrote: > > Correct, I thought about this yesterday too. And this should be a detail in > the Cinder spec for sure, but Cinder should probably have a specific policy > check for attempting to extend an attached volume. Having said this, I see > that C

Re: [openstack-dev] [tc][election] Questions for Candidates

On Wed, 12 Apr 2017, Kendall Nelson wrote: -What is one trait you have that makes it difficult to work in groups like the TC and how do you counteract it? There are many, I'm sure. But one that is frequent and embarrassing is that I have a serious problem with homophones, contractions (or word

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

On 04/12/2017 01: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

[openstack-dev] [TripleO][Heat] Conditionally passing properties in Heat

I'm implementing predictable control plane IPs for spine/leaf, and I'm running into a problem implementing this in the TripleO Heat templates. I have a review in progress [1] that works, but fails on upgrade, so I'm looking for an alternative approach. I'm trying to influence the IP address that i

Re: [openstack-dev] [nova][cinder] Can all non-Ironic compute drivers handle volume size extension?

On 4/12/2017 12:30 PM, Mathieu Gagné wrote: Thanks for starting this discussion. There is a lot to cover/answer. On Tue, Apr 11, 2017 at 6:35 PM, Matt Riedemann wrote: This is not discoverable at the moment, for the end user or cinder, so I'm trying to figure out what the failure mode looks l

Re: [openstack-dev] [keystone] Adding foreign keys between subsystems

On 12-Apr 15:25, Rodrigo Duarte wrote: > On Wed, Apr 12, 2017 at 2:47 PM, David Stanek wrote: > > > On 12-Apr 14:30, Rodrigo Duarte wrote: > > > Just to illustrate the discussion, we have a bug fix that currently tries > > > to drop a FK between the federation and identity subsystems [1]. > > > >

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

I haven't received one either. Perhaps Monty has simply embraced the 'cattle not pets' approach and we were the unlucky ones. :) On Apr 12, 2017 07:49, "Lance Bragstad" wrote: > > On Wed, Apr 12, 2017 at 9:42 AM, Amrith Kumar > wrote: > >> Hmm, all the cool kids didn’t receive the email but I

Re: [openstack-dev] [keystone] Adding foreign keys between subsystems

On Wed, Apr 12, 2017 at 2:47 PM, David Stanek wrote: > On 12-Apr 14:30, Rodrigo Duarte wrote: > > Just to illustrate the discussion, we have a bug fix that currently tries > > to drop a FK between the federation and identity subsystems [1]. > > > > [1] https://review.openstack.org/#/c/445505/ > >

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

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 > > I don't think so - but it w

Re: [openstack-dev] [tc][election] Questions for Candidates

On Apr 12, 2017, at 11:19 AM, Kendall Nelson wrote: > -What is one trait you have that makes it difficult to work in groups like > the TC and how do you counteract it? My natural tendency is to speak bluntly, which can often come across as dismissive of other points of view. As I've gotten old

Re: [openstack-dev] [Release-job-failures][tricircle] Release of openstack/python-tricircleclient failed

Tricircle team, The client library release 0.1.0 had a build failure that left the release artifacts in an indeterminate state. I have retagged the same commit as 0.1.1 and am processing the new release right now. I will monitor the jobs to ensure they all succeed, or that we address any failures.

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

Excerpts from Doug Hellmann's message of 2017-04-12 13:49:54 -0400: > Gnocchi team, > > The client release you tagged had a build failure. It looks like > the tag was pushed directly, so I will relay the results of the > debugging work but let you decide how to deal with it. > > Clark determined

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

Gnocchi team, The client release you tagged had a build failure. It looks like the tag was pushed directly, so I will relay the results of the debugging work but let you decide how to deal with it. Clark determined that the files on PyPI do not exactly match the files on our tarballs server. One

Re: [openstack-dev] [keystone] Adding foreign keys between subsystems

On 12-Apr 14:30, Rodrigo Duarte wrote: > Just to illustrate the discussion, we have a bug fix that currently tries > to drop a FK between the federation and identity subsystems [1]. > > [1] https://review.openstack.org/#/c/445505/ I think this highlights one of my problems with the current archit

[openstack-dev] [keystone] pike-1 release

I've proposed keystone's pike-1 release [0]. If there is anything that we need to wait on for pike-1 that hasn't merged yet, please let me know at your earliest convenience. [0] https://review.openstack.org/#/c/456319/ __ Ope

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

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 I don't think so - but it was an original thought, so it's certainly a reasonable que

Re: [openstack-dev] [keystone] Adding foreign keys between subsystems

Just to illustrate the discussion, we have a bug fix that currently tries to drop a FK between the federation and identity subsystems [1]. The previous fix for this bug (which has been merged and had the backport abandoned) took advantage of the FK in order to cascade delete federated users when a

Re: [openstack-dev] [nova][cinder] Can all non-Ironic compute drivers handle volume size extension?

Thanks for starting this discussion. There is a lot to cover/answer. On Tue, Apr 11, 2017 at 6:35 PM, Matt Riedemann wrote: > > This is not discoverable at the moment, for the end user or cinder, so I'm > trying to figure out what the failure mode looks like. > > This all starts on the cinder sid

Re: [openstack-dev] [tc][election] Questions for Candidates

-What is one trait you have that makes it difficult to work in groups like the TC and how do you counteract it? I am probably overly fascinated by new technology and would be the first to re-invent the wheel. I am probably in good company with that at the TC but I have internalized the lean star

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

Hi Monty I would be interested in working for this. The p On Wed, Apr 12, 2017 at 5:47 PM, Monty Taylor wrote: > Hey everybody! > > This isn't the most normal thing I've done, but whatever. > > We've got this great library, shade, which people love to use to interact > with their OpenStack clou

Re: [openstack-dev] [nova][cinder] Can all non-Ironic compute drivers handle volume size extension?

On Wed, Apr 12, 2017 at 12:58 PM, Matt Riedemann wrote: > > I guess we also have the instance action events. So we could avoid putting > the instance into ERROR state but record an instance action event that the > extend volume event failed on the compute, so at least the user/admin could > figure

[openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

Hey folks, In today’s Kolla team meeting, the idea was proposed of adopting nova’s “protocore” mentorship program for Kolla. We would like to know what nova has learned from this effort. In today’s Kolla meeting we had broad consensus on the following: 1) Kolla has participants that wan

Re: [openstack-dev] [nova][cinder] Can all non-Ironic compute drivers handle volume size extension?

On 4/11/2017 5:35 PM, Matt Riedemann wrote: I'm reading through mgagne's spec to support attached volume size extension callbacks in Nova [1] and the question that comes up is what happens when the backend compute does not support this, either because it's too old (Ocata) or the virt driver does

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

On Wed, Apr 12, 2017 at 4:07 AM, Thierry Carrez wrote: > One idea I've been considering is eliminating the one and only sacred > one-hour weekly TC meeting, and encouraging ad-hoc discussions (on > #openstack-dev for example) between change proposers and smaller groups > of TC members present in t

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

Excerpts from Monty Taylor's message of 2017-04-12 08:14:31 -0500: > Hey all, > > As I'm sure you all know, pbr is both our most pervasively used > dependency and our least well understood. Nobody ever wants to look at > the code (sorry, I can write ugly code sometimes - but also wow > setuptoo

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

On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi wrote: > Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the > prefix. > Note that OSC itself does not use 'command prefixes', it names resources with enough specificity to make them unique. Sometimes that looks like a proefix,

[openstack-dev] [glance] reminder: spec freeze happens Friday!

All Glance, python-glanceclient, and glance_store specs must be merged into the glance-specs repository by 23:59 on Friday 14 April 2017. I've just updated the etherpad with the status of the various patches: https://etherpad.openstack.org/p/glance-pike-specs-review If you're a glance core, ple

[openstack-dev] [nova] What is the difference between default_schedule_zone and default_availability_zone?

I'm hoping someone more learned can teach me. These two options sound very similar, and are thus very confusing. They are also both in the [DEFAULT] config option group, but defined in different places [1][2]. The help text for one says: "This option determines the availability zone to be used

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

Just a question, not meant as anything bad against shade, But would effort be better spent on openstacksdk? Take the good parts of shade and just move it to openstacksdk, perhaps as a 'higher level api' available in openstacksdk? Then ansible openstack components (which I believe use shade) c

[openstack-dev] [tc][election] Questions for Candidates

Hello Candidates! You all have proven yourselves to be crucial parts of the community and I just wanted to say good luck to each one of you in the upcoming election! Also though, I thought it might be good to ask a few more questions. It's easy to talk about what you all want to champion on the T

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

+1 On 04/12/2017 08:14 AM, Monty Taylor wrote: Hey all, As I'm sure you all know, pbr is both our most pervasively used dependency and our least well understood. Nobody ever wants to look at the code (sorry, I can write ugly code sometimes - but also wow setuptools) or dig in to figure out what

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

Hey everybody! This isn't the most normal thing I've done, but whatever. We've got this great library, shade, which people love to use to interact with their OpenStack clouds (even when they don't know they're using it, like when they're using Ansible) - and which we use in Infra behind nodep

[openstack-dev] [keystone] policy meeting 2017-4-12

Just a reminder that we will be having the policy meeting in 45 minutes in #openstack-meeting-cp [0]. It was cancelled last week due to tight schedules. See you there! [0] https://etherpad.openstack.org/p/keystone-policy-meeting ___

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

On Apr 12, 2017, at 9:44 AM, gordon chung wrote: >> If there was ONE thing, one >> initiative, one change you will actively push in the six months between >> this election round and the next, what would it be ? > > this is a really good question! if we're all honest with ourselves, most > of the

Re: [openstack-dev] [tripleo] pike-1 was released - thank you

On 04/11/2017 09:32 PM, Emilien Macchi wrote: > Just a heads-up (while it was mentioned during the TripleO weekly meeting): > > We managed to release TripleO pike-1 early this week. This is really > awesome to see the progress we have made and that we continue to do on > the release side. We are co

Re: [openstack-dev] [keystone] Adding foreign keys between subsystems

On Wed, Apr 12, 2017 at 9:28 AM, David Stanek wrote: > [tl;dr I want to remove the artificial restriction of not allowing FKs > between > subsystems and I want to stop FK enforcement in code.] > > The keystone code architecture is pretty simple. The data and > functionality are > divided up into

[openstack-dev] [all][infra] Upcoming changes to nodepool images

Greetings, As you have likely seen over the last few days, openstack-infra has slowly started making some changes to our nodepool images we use for jobs. With the help of cmurphy, we've started removing the puppet dependency from the images. For the most part, this should be seamless for your pro

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

On Wed, Apr 12, 2017 at 9:42 AM, Amrith Kumar wrote: > Hmm, all the cool kids didn’t receive the email but I did. Now I feel bad > ☹ > > > > -amrith > > > > *From:* Morgan Fainberg [mailto:morgan.fainb...@gmail.com] > *Sent:* Wednesday, April 12, 2017 9:53 AM > *To:* OpenStack Development Mailing

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Hmm, all the cool kids didn’t receive the email but I did. Now I feel bad ☹ -amrith From: Morgan Fainberg [mailto:morgan.fainb...@gmail.com] Sent: Wednesday, April 12, 2017 9:53 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Emails for Op

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

On 10/04/17 05:16 AM, Thierry Carrez wrote: > If there was ONE thing, one > initiative, one change you will actively push in the six months between > this election round and the next, what would it be ? this is a really good question! if we're all honest with ourselves, most of the rhetoric in

[openstack-dev] [trove] weekly meeting canceled today

I've not seen anything new on the agenda and I have a late scheduling conflict today. Let's catch up on IRC if there is anything that needs discussing. -- Amrith Kumar amrith.ku...@gmail.com __ OpenStack Development Maili

[openstack-dev] [keystone] Adding foreign keys between subsystems

[tl;dr I want to remove the artificial restriction of not allowing FKs between subsystems and I want to stop FK enforcement in code.] The keystone code architecture is pretty simple. The data and functionality are divided up into subsystems. Each subsystem can be configured to use a different back

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 12/04/17 02:47 AM, Tony Breeds wrote: > Please look over both lists by 2017-04-17 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing > and > why. Note doing this will amost certainly reduce the testing coverage you > have in the ga

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

I have read very good ideas in this thread but I somehow can’t shake the feeling that people who are quite comfortable with the irc meeting are looking for a solution for people who are not. So, before we do any changes I would send out a survey and see what the developers we are serving actual

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Please add openstack-manuals to the list for EOL, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 3

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

Hi, Though I haven’t attended the operator summit in person a them which has been mentioned to me is that we need to offer better reference architectures. I use the plural here on purpose because I don’t think there will be one architecture/combination of projects which works for everybody. As

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Apr 12, 2017 at 12:47 AM, Tony Breeds wrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects that meet one or more

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

I also have not received a poll email. On Apr 12, 2017 6:13 AM, "Neil Jerram" wrote: > Nor me. > > On Wed, Apr 12, 2017 at 1:55 PM Doug Hellmann > wrote: > >> Excerpts from Dulko, Michal's message of 2017-04-12 12:09:30 +: >> > On Wed, 2017-04-12 at 06:57 -0500, Monty Taylor wrote: >> > > O

Re: [openstack-dev] [nova] Removes the extra URL routes in Nova API

On 3/30/2017 12:22 AM, Alex Xu wrote: Currently I'm working on removing the stevedore [0], and move the URL routes mapping into a plain list [1]. But actually, the original URL mappings which Nova created [2] are more than that list. Due to the interface 'routes.Mapper.resources' create a set ro

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

+1, we really need more people who know pbr well :-) 2017-04-12 21:14 GMT+08:00 Monty Taylor : > Hey all, > > As I'm sure you all know, pbr is both our most pervasively used dependency > and our least well understood. Nobody ever wants to look at the code > (sorry, I can write ugly code sometimes

[openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

Hey all, As I'm sure you all know, pbr is both our most pervasively used dependency and our least well understood. Nobody ever wants to look at the code (sorry, I can write ugly code sometimes - but also wow setuptools) or dig in to figure out what happened when things break. Recently Stephe

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Nor me. On Wed, Apr 12, 2017 at 1:55 PM Doug Hellmann wrote: > Excerpts from Dulko, Michal's message of 2017-04-12 12:09:30 +: > > On Wed, 2017-04-12 at 06:57 -0500, Monty Taylor wrote: > > > On 04/06/2017 07:34 AM, Monty Taylor wrote: > > > > > > > > Hey all! > > > > > > > > I've started th

[openstack-dev] [release] pausing releases due to pypi upload issues

Earlier today several of the release jobs failed when uploading artifacts to PyPI. We're going to hold off tagging any other releases until we've confirmed that the problem is resolved. Doug __ OpenStack Development Mailing L

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Excerpts from Dulko, Michal's message of 2017-04-12 12:09:30 +: > On Wed, 2017-04-12 at 06:57 -0500, Monty Taylor wrote: > > On 04/06/2017 07:34 AM, Monty Taylor wrote: > > > > > > Hey all! > > > > > > I've started the R Release Name poll and currently am submitting > > > everyone's email add

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

On Wed, 12 Apr 2017, joehuang wrote: Can all these efforts lead us to one platform vision? We have to think over the question. 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? These are tough questions. It's gre

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

On Wed, 2017-04-12 at 06:57 -0500, Monty Taylor wrote: > On 04/06/2017 07:34 AM, Monty Taylor wrote: > > > > Hey all! > > > > I've started the R Release Name poll and currently am submitting > > everyone's email address to the system. In order to not make our fine > > friends at Carnegie Mellon (

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

On Mon, Apr 10, 2017 at 11:16:57AM +0200, Thierry Carrez wrote: > Hi everyone, > > New in this TC election round, we have a few days between nominations > and actual voting to ask questions and get to know the candidates a bit > better. I'd like to kick off this new "campaigning period" with a bas

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

On 04/06/2017 07:34 AM, Monty Taylor wrote: Hey all! I've started the R Release Name poll and currently am submitting everyone's email address to the system. In order to not make our fine friends at Carnegie Mellon (the folks who run the CIVS voting service) upset, I have a script that submits t

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

On 12/04/17 11:07 +0200, Thierry Carrez wrote: Ildiko Vancsa wrote: On 2017. Apr 12., at 3:18, Monty Taylor mailto:mord...@inaugust.com>> wrote: [...] Email allows someone to compose an actual structured narrative, and for replies to do the same. Some of us are loquatious and I imagine can be ha

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

On 12 April 2017 at 12:04, Davanum Srinivas wrote: > On Wed, Apr 12, 2017 at 6:51 AM, John Garbutt wrote: >> On 12 April 2017 at 03:54, joehuang 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? >> >>

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

On 12 April 2017 at 10:07, Thierry Carrez wrote: > Ildiko Vancsa wrote: >>> On 2017. Apr 12., at 3:18, Monty Taylor >> > wrote: >>> [...] >>> Email allows someone to compose an actual structured narrative, and >>> for replies to do the same. Some of us are loquatious a

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

On Wed, Apr 12, 2017 at 6:51 AM, John Garbutt wrote: > On 12 April 2017 at 03:54, joehuang 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? > > The more I think about this, the less I like the phrase "o

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

On 11 April 2017 at 09:58, Thierry Carrez wrote: > Matt Riedemann wrote: >> Lots of projects have alternating meeting times to accommodate >> contributors in different time zones, especially Europe and Asia. >> >> The weekly TC meeting, however, does not. >> >> I have to assume this has come up be

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

On 12 April 2017 at 03:54, joehuang 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? The more I think about this, the less I like the phrase "one platform". I like to think of OpenStack as group of const

Re: [openstack-dev] [nova][api] quota-class-show not sync toquota-show

ok, thanks for the info, I will submit the spec and wait for more response from the spec Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82451493 Address: 3/F Ring Building, ZhongGuanCun Software P

Re: [openstack-dev] [heat] New resource implementation workflow

> > I also remember that Heat has smth like 'hidden' in resource plugin > declaration. Usually it is used to hide deprecated resource types so that > new stacks with those can not be created but old ones can be at least > deleted. May be you could use that flag while developing until you think > th

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

> […] > One idea I've been considering is eliminating the one and only sacred > one-hour weekly TC meeting, and encouraging ad-hoc discussions (on > #openstack-dev for example) between change proposers and smaller groups > of TC members present in the same timezone. That would give us a good > fee

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Hi, > I think (a) is also good from TaaS dashboard. This opinion is agreed as a TaaS project. Regards, Kaz From: "SUZUKI, Kazuhiro" Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects? Date: Wed, 12 Apr

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

joehuang 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? OpenStack is "one platform", one open infrastructure platform. It can provide various resources (VMs, bare metal machines, container orches

Re: [openstack-dev] [tripleo][ui] another i18n proposal for heat templates 'description' help strings

Hi Julie,   Please see the comments in line. On Mon, 2017-04-10 at 16:13 +0100, Julie Pichon wrote: > Hi Peng, > > I added some thoughts in-line, let me know what you think. > > On 10 April 2017 at 08:10, Peng Wu wrote: > > Hi, > > > >   In TripleO UI project users requested translation of t

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

Ildiko Vancsa wrote: >> On 2017. Apr 12., at 3:18, Monty Taylor > > wrote: >> [...] >> Email allows someone to compose an actual structured narrative, and >> for replies to do the same. Some of us are loquatious and I imagine >> can be hard to follow even with time to r

[openstack-dev] [tricircle]weekly meeting of Apr.12

Hello, team, Agenda of Apr.12 weekly meeting: 1. feature implementation review 2. Pike-1.5 (May.2) preparation 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 14:00. If you have other topic

  1   2   >