[openstack-dev] [cross-project] The Future of Meetings

Hey all, When we first discussed the future of cross-project meetings at the Tokyo summit, we walked out with the idea of beginning to have ad-hoc meetings instead of one big meeting with all big tent projects. Now that we have some process in place [1] (unfortunately still under review), we can

[openstack-dev] [all][stable] Moving stable/liberty branches to Phase II support

Hi all, Liberty was released on 2015-10-15 which puts the end of Phase I[1] support at 2016-04-15. I'd like all stable teams to transition to Phase II support "Critical bugfixes and security patches only" as of 2016-05-15. This basically means that we have this work week to assess the open

Re: [openstack-dev] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

I don't see that we need a new role for this because it would need to be added to all the admin users. I was thinking just admin or target.project_id==token.project_id. Hopefully in future this would get better because we can get nova to send the service token as well and enforce that it came from

Re: [openstack-dev] [tc] supporting Go

On Tue, 10 May 2016 at 05:19 Edward Leafe wrote: > On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: > > > This is not a "Go seems cool - lets go try that" decision from us - we > > know we have a performance problem with one of our components, and we > >

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Hi Yipei, On Tue, May 10, 2016 at 10:59 AM, Yipei Niu wrote: > Hi, all, > > I think I understand how does tricircle schedule pods. Based on the flavor > extra_specs or volume extra_specs tags, tricircle queries the pod table for > the records in which resource_affinity_tag is

[openstack-dev] [Infra] Meeting Tuesday May 10th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday May 10th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [Neutron] L2gw

On 9 May 2016 at 18:03, Gary Kotton wrote: > Hi, > Are there plans to cut a a stable/mitaka version for the l2gw? > https://github.com/openstack/networking-l2gw > Thanks > Gary > I know Sukhdev was working on it. > >

Re: [openstack-dev] [tc] supporting Go

On 10 May 2016 at 06:58, Hayes, Graham wrote: > From a deck about "the rise and fall of Bind 10" [0] - > >"Python is awesome, but too damn slow for DNS" That slide deck doesn't provide any analysis on *what* that means - latency? requests per second?

Re: [openstack-dev] [Neutron] L2gw

Good catch! Cheers, S On Tue, May 10, 2016 at 10:03 AM, Gary Kotton wrote: > Hi, > Are there plans to cut a a stable/mitaka version for the l2gw? > https://github.com/openstack/networking-l2gw > Thanks > Gary > >

[openstack-dev] [Neutron] L2gw

Hi, Are there plans to cut a a stable/mitaka version for the l2gw? https://github.com/openstack/networking-l2gw Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [tc] supporting Go

On Mon, May 9, 2016 at 8:21 PM, Ben Swartzlander wrote: > > > If you think Perl is "nice" or "easy" you better get you head checked. > Each language has its strength and weakness, so just use the right tool for the job. In fact the system at the investment bank worked

Re: [openstack-dev] Team blogs

On 05/09/2016 07:33 PM, Robert Collins wrote: > On 10 May 2016 at 10:55, Anita Kuno wrote: >> On 05/09/2016 06:45 PM, Robert Collins wrote: >>> IIRC mediawiki provides RSS of changes... maybe just using the wiki >>> more would be a good start, and have zero infra costs? >>>

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 07:43 PM, Rayson Ho wrote: On Mon, May 9, 2016 at 2:35 PM, Ben Swartzlander > wrote: >> >> Perhaps for mature languages. But go is still finding its way, and that >> usually involves rapid changes that are needed faster than

Re: [openstack-dev] [tc] supporting Go

On 10 May 2016 at 10:54, John Dickinson wrote: > On 9 May 2016, at 13:16, Gregory Haynes wrote: >> >> This is a bit of an aside but I am sure others are wondering the same >> thing - Is there some info (specs/etherpad/ML thread/etc) that has more >> details on the bottleneck you're

Re: [openstack-dev] Easing contributions to central documentation

Matt Kassawara wrote: > At each summit, I speak with a variety of developers from different projects > about the apparent lack of contributions to the central documentation. At > previous summits, the most common complaint involved using DocBook. After > converting most of

Re: [openstack-dev] [tc] supporting Go

On Mon, May 9, 2016, at 03:54 PM, John Dickinson wrote: > On 9 May 2016, at 13:16, Gregory Haynes wrote: > > > > This is a bit of an aside but I am sure others are wondering the same > > thing - Is there some info (specs/etherpad/ML thread/etc) that has more > > details on the bottleneck you're

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 09:51 PM, Clint Byrum wrote: > There are all kinds of reasons to pick languages, but I think it would > be foolish of OpenStack to ignore the phenomenon of actual deployers > choosing Go to address OpenStack's shortcomings. Whether they're right, > I'm not sure, but I do know that

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 01:33 PM, Hayes, Graham wrote: > On 08/05/2016 10:21, Thomas Goirand wrote: >> On 05/04/2016 01:29 AM, Hayes, Graham wrote: >>> On 03/05/2016 17:03, John Dickinson wrote: TC, In reference to http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html

[openstack-dev] [RefStack] IRC Meeting Tuesday May 10th

Just a reminder that we will have RefStack weekly meeting tomorrow ( May 10th) at 19:00 UTC in #openstack-meeting-alt . This will be our first meeting after moving weekly meeting from Monday to Tuesday. The agenda can be found at https://wiki.openstack.org/wiki/Meetings/Refstack. Please feel

Re: [openstack-dev] [Heat] Summit recap

On 09/05/16 09:44, Julien Danjou wrote: On Mon, May 09 2016, Thomas Herve wrote: […] Using DLM We managed to not talk about ZooKeeper too much :). We want to remove the database locks that we have and use tooz instead. The key is to provide a nice upgrade path, so starting

Re: [openstack-dev] Team blogs

On 05/09/2016 06:53 PM, Monty Taylor wrote: > On 05/09/2016 05:45 PM, Robert Collins wrote: >> IIRC mediawiki provides RSS of changes... maybe just using the wiki >> more would be a good start, and have zero infra costs? > > We'd actually like to start using the wiki less, per the most recent >

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Mark, This is exactly the kind of discussion I was hoping for during Austin. I agree with pretty much all your statements. I think if Kolla can define what it would expect in the inventory provided by a bare metal provisioner, and we can make an ABI around that, then this becomes a lot more

Re: [openstack-dev] Team blogs

On 9 May 2016, at 15:53, Monty Taylor wrote: > On 05/09/2016 05:45 PM, Robert Collins wrote: >> IIRC mediawiki provides RSS of changes... maybe just using the wiki >> more would be a good start, and have zero infra costs? > > We'd actually like to start using the wiki less, per the most recent

Re: [openstack-dev] Team blogs

Excerpts from Joshua Harlow's message of 2016-05-09 15:37:23 -0700: > After seeing the amount of summit recaps and the scattered nature of > these (some on the ML, some on etherpads, some on personal blogs); I am > starting to wonder if we should again bring up the question of having > infra

Re: [openstack-dev] [heat]Provides different stack quota to tenant

On 09/05/16 12:36, Sylvernass Arthas wrote: Excerpts from Sylvernass Arthas's message of 2016-05-08 05:33:13 -0700: Hi, guys Now, all tenant share the public config "max_stacks_per_tenant" which decides maximum number of stacks any one tenant may have active at one time, the default

Re: [openstack-dev] Team blogs

On 05/09/2016 06:45 PM, Robert Collins wrote: > IIRC mediawiki provides RSS of changes... maybe just using the wiki > more would be a good start, and have zero infra costs? > > -Rob Well we are actually moving away from the wiki. Currently new accounts are closed due to spammers using new

Re: [openstack-dev] [tc] supporting Go

On 9 May 2016, at 13:16, Gregory Haynes wrote: > > This is a bit of an aside but I am sure others are wondering the same > thing - Is there some info (specs/etherpad/ML thread/etc) that has more > details on the bottleneck you're running in to? Given that the only > clients of your service are the

Re: [openstack-dev] Team blogs

On 05/09/2016 05:45 PM, Robert Collins wrote: > IIRC mediawiki provides RSS of changes... maybe just using the wiki > more would be a good start, and have zero infra costs? We'd actually like to start using the wiki less, per the most recent summit. Also, the wiki currently has new accounts

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

Sorry for the slow response here ... +1 Michal, Thank you for all you have contributed recently. Welcome to the team! Jay On 05/03/2016 01:16 PM, Sean McGinnis wrote: Hey everyone, I would like to nominate Michał Dulko to the Cinder core team. Michał's contributions with both code reviews

Re: [openstack-dev] Team blogs

IIRC mediawiki provides RSS of changes... maybe just using the wiki more would be a good start, and have zero infra costs? -Rob On 10 May 2016 at 10:37, Joshua Harlow wrote: > After seeing the amount of summit recaps and the scattered nature of these > (some on the ML,

[openstack-dev] Team blogs

After seeing the amount of summit recaps and the scattered nature of these (some on the ML, some on etherpads, some on personal blogs); I am starting to wonder if we should again bring up the question of having infra (and I guess the foundation?) support/provide a place for team blogs...

Re: [openstack-dev] [nova] api-ref sprint today & wed

Currently it's really hard to tell (at least to me) which files have patches against them and which don't. I've had to manually make a spreadsheet because it's not obvious to me, at a glance, from the current commit messages, and I've accidentally started work on several files that already have

[openstack-dev] [ironic] Midcycle: virtual or physical?

Hey all, In this morning's meetings we discussed having a virtual midcycle again this cycle, versus a physical midcycle. Pros of virtual: * More people can attend (we'd be missing a significant portion of our core team at a physical midcycle) * Lower cost for employers * It went very well

Re: [openstack-dev] [puppet] roadmap proposal for puppet-ceph

Update: On Fri, May 6, 2016 at 4:52 PM, Emilien Macchi wrote: > Hi, > > Here's a roadmap proposal for puppet-ceph: > > 1) Release 1.0.0 > 1.0.0 will be the first release, we'll also create stable/hammer since > it was the release that was tested in our CI. >

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

On Mon, May 9, 2016 at 11:03 AM, Mooney, Sean K wrote: > Hi > > > > If we choose to use bifrost to deploy ironic standalone I think combining > kevins previous > > suggestion of modifying the bifrost install playbook with Steve Dake’s > suggestion of creating a series >

[openstack-dev] [nova][ironic] Specs matcher and its journey through time

Hi all, Recently jroll proposed the following into oslo.utils https://review.openstack.org/#/c/308398/ This moves the spec matching (if that's what u can call it) to oslo.utils so that it can be shared by nova and ironic (which I think is a fair thing to do, although personally I don't like

[openstack-dev] [ironic] Summit recap

Hey all, I wrote a recap of the summit on my blog: http://jroll.ghost.io/newton-summit-recap/ I hope this covers everything that folks missed or couldn't remember. As always, questions/comments/concerns welcome. // jim __

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

From: "Mooney, Sean K" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Monday, May 9, 2016 at 11:03 AM To: "OpenStack

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

On Fri, May 6, 2016 at 1:16 PM, Fox, Kevin M wrote: > I was under the impression bifrost was 2 things, one, an > installer/configurator of ironic in a stand alone mode, and two, a > management tool for getting machines deployed without needing nova using > ironic. > "Bifrost

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Are we (as the Kolla community) open to other bare metal provisioners? The austin discussion was titled generic bare metal, but very quickly turned into bifrost-only discourse. The initial survey showed cobbler/maas/OoO as alternatives people use today. So if the bifrost strategy is,

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

From: Devananda van der Veen > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Monday, May 9, 2016 at 1:05 PM To: "OpenStack

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

From: Devananda van der Veen > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Monday, May 9, 2016 at 1:12 PM To: "OpenStack

[openstack-dev] Easing contributions to central documentation

At each summit, I speak with a variety of developers from different projects about the apparent lack of contributions to the central documentation. At previous summits, the most common complaint involved using DocBook. After converting most of the documentation to RST, the most common complaint at

[openstack-dev] OpenStack Developer Mailing List Digest April 23 - May 6

HTML version: http://www.openstack.org/blog/2016/05/openstack-developer-mailing-list-digest-20160506/ Success Bot Says * Sdague: nova-network is deprecated [1] * Ajaeger: OpenStack content on Transifex has been removed, Zanata on translate.openstack.org has proven to be stable

Re: [openstack-dev] [neutron] Re: [stable] Requesting exception for stable/kilo

Hi Akihito, I think from the requirements.txt point of view, we are good. Thanks -Sukhdev On Mon, May 9, 2016 at 2:11 PM, Akihiro Motoki wrote: > Hi Sukhdev, Dave, > > I think this backport is acceptable. > > In Kilo release, neutron is in a middle way of splitting

Re: [openstack-dev] [Neutron] Diagnostics & troubleshooting design summit summary and next steps

On Mon, May 9, 2016 at 1:28 PM, Boden Russell wrote: > Assaf, thanks for driving this session. > > As a newbie to the design sessions, I think presenting a brief "context" > up-front is helpful. IMO the key word here is "brief" (5 min or less for > example) and furthermore

Re: [openstack-dev] config options: current state (R-21)

On Tue, May 10, 2016 at 2:12 AM, Markus Zoeller wrote: > We're close to have all options moved to "nova/conf/". At the bottom > is a list of the remaining options and their open reviews. > > The documentation of the options in "nova/conf/" is done for ~ 150 > options. Which

Re: [openstack-dev] [neutron] Re: [stable] Requesting exception for stable/kilo

Hi Dave, I will get on it right away. Let me find Neutron Cores to review it. Please stand by -Sukhdev On Mon, May 9, 2016 at 12:46 PM, Dave Walker wrote: > > > On 4 May 2016 at 17:55, Sukhdev Kapur wrote: > >> Hi Stable Maintainers, >> >> We have

Re: [openstack-dev] [tc] supporting Go

Hayes, Graham wrote: > Sure - the Designate team could maintain 2 copies of our DNS server, > one in python as a reference, and one externally in Golang / C / C++ / > Rust / $language, which would in reality need to be used by anything > over a medium size deployment. > > That seems less than

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

On 9 May 2016 9:48 p.m., Mike Spreitzer wrote: > > "Hayes, Graham" wrote on "Hayes, Graham" wrote on 05/09/2016 04:08:07 PM: > ... > On 09/05/2016 20:55, Mike Spreitzer wrote: > ... > > Oh, right, the network gets to specify

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On Fri, May 06, 2016 at 09:18:03AM -0400, Paul Belanger wrote: > On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote: > > Hi all, > > > > Some folks have requested a summary of our summit sessions, as has been > > provided for some other projects. > > > > I'll probably go into more

[openstack-dev] [nova][glance] Austin summit nova/glance cross-project session recap

On Thursday afternoon of the design summit the nova and glance teams had a cross-project session. The full etherpad is here [1]. This was all about glance v2 integration in nova, the spec for which is here [2]. We agreed to add an immediately deprecated use_glancev2 config option per Sean

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

"Hayes, Graham" wrote on 05/09/2016 04:08:07 PM: > ... > On 09/05/2016 20:55, Mike Spreitzer wrote: > ... > > Oh, right, the network gets to specify the rest of the FQDN. In my case > > I am interested in Neutron Ports on tenant networks. So with a per-port > >

Re: [openstack-dev] [tc] supporting Go

Clint Byrum wrote: Excerpts from Edward Leafe's message of 2016-05-09 12:17:40 -0700: On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: This is not a "Go seems cool - lets go try that" decision from us - we know we have a performance problem with one of our components,

Re: [openstack-dev] [tc] supporting Go

On Mon, May 9, 2016, at 01:01 PM, Hayes, Graham wrote: > On 09/05/2016 20:46, Adam Young wrote: > > On 05/09/2016 02:14 PM, Hayes, Graham wrote: > >> On 09/05/2016 19:09, Fox, Kevin M wrote: > >>> I think you'll find that being able to embed a higher performance > >>> language inside python will

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

On Fri, May 6, 2016 at 10:56 AM, Steven Dake (stdake) wrote: > Sean, > > Thanks for taking this on :) I didn't know you had such an AR :) > > From: "Mooney, Sean K" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < >

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Hi folks, It's a shame that etherpad was down during the ODS kolla/bifrost session. My recollection is that we agreed *not* to re-invent it Bifrost in containers, but to just stick with running it in a VM (as it is today) because that is the quickest path, and allows the Kolla community to

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

On 09/05/2016 20:55, Mike Spreitzer wrote: > "Hayes, Graham" wrote on 05/09/2016 03:00:34 PM: > > > From: "Hayes, Graham" > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Date:

Re: [openstack-dev] [tc] supporting Go

On 09/05/2016 20:46, Adam Young wrote: > On 05/09/2016 02:14 PM, Hayes, Graham wrote: >> On 09/05/2016 19:09, Fox, Kevin M wrote: >>> I think you'll find that being able to embed a higher performance language >>> inside python will be much easier to do for optimizing a function or two >>> rather

Re: [openstack-dev] [tc] supporting Go

On May 9, 2016, at 2:52 PM, Clint Byrum wrote: >> Whenever I hear claims that Python is “too slow for X”, I wonder what’s so >> special about X that makes it so much more demanding than, say, serving up >> YouTube. YouTube is written nearly entirely in Python, and has been

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

"Hayes, Graham" wrote on 05/09/2016 03:00:34 PM: > From: "Hayes, Graham" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 05/09/2016 03:05 PM > Subject: Re: [openstack-dev] [neutron]

Re: [openstack-dev] [tc] supporting Go

Excerpts from Edward Leafe's message of 2016-05-09 12:17:40 -0700: > On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: > > > This is not a "Go seems cool - lets go try that" decision from us - we > > know we have a performance problem with one of our components, and we > >

Re: [openstack-dev] [tc] supporting Go

Excerpts from Hayes, Graham's message of 2016-05-09 11:58:38 -0700: > On 09/05/2016 19:39, Ben Swartzlander wrote: > > On 05/09/2016 02:15 PM, Clint Byrum wrote: > >> Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > >>> On Mon, 9 May 2016 09:06:02 -0400 > >>> Rayson Ho

[openstack-dev] [neutron] Re: [stable] Requesting exception for stable/kilo

On 4 May 2016 at 17:55, Sukhdev Kapur wrote: > Hi Stable Maintainers, > > We have a critical bug impacting customers production network. This is a > minor fix. > I would like to request an exception so that the customers do not have to > baby > sit this patch. > >

[openstack-dev] [neutron] Re: [stable] Requesting exception for stable/kilo

On 4 May 2016 at 17:55, Sukhdev Kapur wrote: > Hi Stable Maintainers, > > We have a critical bug impacting customers production network. This is a > minor fix. > I would like to request an exception so that the customers do not have to > baby > sit this patch. > >

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 02:14 PM, Hayes, Graham wrote: On 09/05/2016 19:09, Fox, Kevin M wrote: I think you'll find that being able to embed a higher performance language inside python will be much easier to do for optimizing a function or two rather then deal with having a separate server have to be

[openstack-dev] [release][sahara] sahara-tests 0.2.0 release

We are glad to announce the release of: sahara-tests 0.2.0: Sahara tests With source available at: https://git.openstack.org/cgit/openstack/sahara-tests For more details, please see below. 0.2.0 ^ Discovery of data sources with relative paths is now fixed. Fix default resource

Re: [openstack-dev] [TripleO][CI] Elastic recheck bugs

On Mon, May 9, 2016, at 10:22 AM, Sagi Shnaidman wrote: > Hi, all > > I'd like to enable elastic recheck on TripleO CI and have submitted > patches > for refreshing the tracked logs [1] (please review) and for timeout case > [2]. > But according to Derek's comment behind the timeout issue could

Re: [openstack-dev] [tc] supporting Go

Go static linking/portability is something of a misnomer too. Last I looked Go only statically linked Go code, so any system libraries used still were dynamic. So it gets you somewhat to the use case of container level portability but not all the way unless you can do literally everything in

[openstack-dev] [release][stable][winstackers] os-win 0.4.2 release (mitaka)

We are overjoyed to announce the release of: os-win 0.4.2: Windows / Hyper-V library for OpenStack projects. This release is part of the mitaka stable release series. With source available at: http://git.openstack.org/cgit/openstack/os-win With package available at:

[openstack-dev] [designate] Summit Recap

I started writing this on a plane on the way home from Austin, TX where we just finished up the Newton design summit for OpenStack, and finished it a few days later - please excuse any weirdness in syntax or flow :) 6 Months On: Where are we = One of the things I did

Re: [openstack-dev] [tc] supporting Go

On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: > This is not a "Go seems cool - lets go try that" decision from us - we > know we have a performance problem with one of our components, and we > have come to the conclusion that Go (or something like it) is the > solution.

Re: [openstack-dev] [tc] supporting Go

Excerpts from Tim Simmons's message of 2016-05-09 18:29:30 +: > > The point here though, is that the versions of Python that OpenStack > > has traditionally supported have been directly tied to what the Linux > > distributions carry in their repositories (case in point, Python 2.6 > > was

[openstack-dev] [Tacker][NFV] Tacker - Weekly IRC Meeting - new time

Tackers, We are resuming Tacker IRC weekly meeting at a new time slot (an hour earlier) and at a new channel. When: Tuesday 1600 UTC Where: #openstack-meeting Duration: 1hr Here is the agenda for tomorrow's meeting,

Re: [openstack-dev] Ansible inventory - Would you need another inventory system for your openstack cloud and how would you like it to be?

On 9 May 2016 at 15:27, Jean-Philippe Evrard wrote: > I am using ansible for some time now, and I think the current default > Ansible inventory system is lacking a few features, at least when working > on an OpenStack cloud - whether it's for its deployment, its support

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

On 09/05/2016 19:21, Mike Spreitzer wrote: > I just read > http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.htmland, > unless > I missed something, it seems to be describing something that is not > multi-tenant. I am focused on FQDNs for Neutron Ports. For those, only > the

Re: [openstack-dev] [tc] supporting Go

On 09/05/2016 19:39, Ben Swartzlander wrote: > On 05/09/2016 02:15 PM, Clint Byrum wrote: >> Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: >>> On Mon, 9 May 2016 09:06:02 -0400 >>> Rayson Ho wrote: >>> Since the Go toolchain is pretty

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 02:15 PM, Clint Byrum wrote: Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: On Mon, 9 May 2016 09:06:02 -0400 Rayson Ho wrote: Since the Go toolchain is pretty self-contained, most people just follow the official instructions to get it

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 01:15 PM, Clint Byrum wrote: > Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: >> On Mon, 9 May 2016 09:06:02 -0400 >> Rayson Ho wrote: >> >>> Since the Go toolchain is pretty self-contained, most people just follow >>> the official

Re: [openstack-dev] [tc] supporting Go

Ah. ok. Yeah, using Go for that use case wouldn't be too bad then. Thanks, Kevin From: Hayes, Graham [graham.ha...@hpe.com] Sent: Monday, May 09, 2016 11:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [tc] supporting Go

On 9 May 2016, at 11:14, Hayes, Graham wrote: > On 09/05/2016 19:09, Fox, Kevin M wrote: >> I think you'll find that being able to embed a higher performance language >> inside python will be much easier to do for optimizing a function or two >> rather then deal with having a separate server

Re: [openstack-dev] [ironic] API docs now publishing from our tree

Works for me. The api-ref stuff is much easier to maintain, review, and the resulting docs are infinitely more usable for developers. I'm already working on getting api-ref up to date; the current docs there are sorely out of date and wrong. I'd like to land these patches quickly and iterate on

[openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

I just read http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.html and, unless I missed something, it seems to be describing something that is not multi-tenant. I am focused on FQDNs for Neutron Ports. For those, only the "hostname" part (the first label, in official DNS

Re: [openstack-dev] [TripleO][CI] Elastic recheck bugs

Sorry, missed the mentioned patches: [1] Refresh log files for tripleo project: https://review.openstack.org/#/c/312985/ [2] Add bug for TripleO timeouts: https://review.openstack.org/#/c/313038/ On Mon, May 9, 2016 at 8:22 PM, Sagi Shnaidman wrote: > Hi, all > > I'd like

Re: [openstack-dev] [tc] supporting Go

Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > On Mon, 9 May 2016 09:06:02 -0400 > Rayson Ho wrote: > > > Since the Go toolchain is pretty self-contained, most people just follow > > the official instructions to get it installed... by a one-step: > >

Re: [openstack-dev] [tc] supporting Go

On 09/05/2016 19:09, Fox, Kevin M wrote: > I think you'll find that being able to embed a higher performance language > inside python will be much easier to do for optimizing a function or two > rather then deal with having a separate server have to be created, > authentication be added between

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Hi If we choose to use bifrost to deploy ironic standalone I think combining kevins previous suggestion of modifying the bifrost install playbook with Steve Dake's suggestion of creating a series of supervisord configs for running each of the service is a reasonable approch. I am currently

Re: [openstack-dev] [tc] supporting Go

I think you'll find that being able to embed a higher performance language inside python will be much easier to do for optimizing a function or two rather then deal with having a separate server have to be created, authentication be added between the two, and marshalling/unmarshalling the data

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

Paul, There is no request from the Kolla community to churn the images. I don't see that as adding any value. We can just document the reality of the situation, which is only BTRFS works well as a graph driver with 14.04. Regards -steve On 5/9/16, 10:48 AM, "Paul Belanger"

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

On Sun, May 08, 2016 at 09:55:58AM -0500, Monty Taylor wrote: > On 05/08/2016 03:45 AM, Steve Kowalik wrote: > >On 08/05/16 08:11, lương hữu tuấn wrote: > >>Hi, > >> > >>@Robert: I was successful to update the kernel without change the image. > > > >But that was Robert's point entirely. Installing

[openstack-dev] [Neutron] Team meeting this Tuesday at 1400 UTC

Hi neutrinos, Just a reminder that from this week, we'll resume the usual schedule for the weekly team meeting. Many thanks, Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Neutron] Diagnostics & troubleshooting design summit summary and next steps

Assaf, thanks for driving this session. As a newbie to the design sessions, I think presenting a brief "context" up-front is helpful. IMO the key word here is "brief" (5 min or less for example) and furthermore should not open the floor for digression given the short time-frame we have per

Re: [openstack-dev] [kolla] CentOS binary and source gate failed due to the rabbitmq

The ubuntu gate deploy failed too; that is awkward. http://logs.openstack.org/05/314205/1/check/gate-kolla-dsvm-deploy-ubuntu-source/766ee43/console.html#_2016-05-09_16_58_39_411 - Hui On Mon, May 9, 2016 at 1:48 AM, Jeffrey Zhang wrote: > I deploy the Kolla by using

[openstack-dev] [TripleO][CI] Elastic recheck bugs

Hi, all I'd like to enable elastic recheck on TripleO CI and have submitted patches for refreshing the tracked logs [1] (please review) and for timeout case [2]. But according to Derek's comment behind the timeout issue could be multiple issues and bugs, so I'd like to clarify - what are criteria

Re: [openstack-dev] [heat]Provides different stack quota to tenant

Excerpts from Sylvernass Arthas's message of 2016-05-08 05:33:13 -0700: > Hi, guys > > Now, all tenant share the public config "max_stacks_per_tenant" which > decides maximum number of stacks any one tenant may have active at one time, > the default value is 1000. > Should heat provides

Re: [openstack-dev] [kolla] OpenPower support

Franck, It's coming from Nova: http://codesearch.openstack.org/?q=ServiceTooOld=nope==nova Check the nova configuration files for a rpc version mismatch -- Dims On Mon, May 9, 2016 at 12:17 PM, Franck Barillaud wrote: > all, > > We have a Mitaka/Kolla control plane

[openstack-dev] [kolla] OpenPower support

all, We have a Mitaka/Kolla control plane deployed on x86 in our lab with an OpenPower (Habanero system from Tyan) compute node attached to it and it works like a charm :-). Under SoftLayer we also have a Mitaka/Kolla control plane deployed on x86 and we are trying to attach a Power8 system

[openstack-dev] config options: current state (R-21)

We're close to have all options moved to "nova/conf/". At the bottom is a list of the remaining options and their open reviews. The documentation of the options in "nova/conf/" is done for ~ 150 options. Which means ~ 450 are missing. This means there are still around 80 changes necessary to

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Dmitry Tantsur wrote: On 05/07/2016 01:00 AM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help

[openstack-dev] [release][oslo] taskflow 1.31.0 release (newton)

We are chuffed to announce the release of: taskflow 1.31.0: Taskflow structured state management library. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at:

  1   2   >