Re: [openstack-dev] [nova] Should be instance_dir in all nova compute node same ?

I can't think of a reason. In fact its a bit warty because we've changed the way we name the instance directories at least once. Its just how this code was written back in the day. Cleaning this up would be a fair bit of work though. Is it really worth the effort just so people can have different

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

[openstack-dev] [tricircle]weekly meeting of May. 4

Hi, In last virtual design summit meeting, some feature was identified blocking the tempest. So let's discuss the these topics in the weekly meeting: Virtual design summit: https://etherpad.openstack.org/p/TricircleNeutonDesignSummit IRC meeting:

Re: [openstack-dev] [Kolla] lock the distro version in the stable branch

On Wed, May 4, 2016 at 1:30 AM, Hui Kang wrote: > This commit fixes the tag: > > https://github.com/openstack/kolla/commit/e2fa75fce6f90de8b2766070bb65d0b80bcad8c8 > ​ that fix is just a workaround. the end-user know nothing about this ​ and will be confused about the

Re: [openstack-dev] [kolla][kolla-k8s] Core team

agree. at the beginning, the kolla-k8s core team should accept new core reviewers in the very high frequency, for example 1-2 member every 1 week, which will be helpful for the growth of the core team. On Wed, May 4, 2016 at 12:48 AM, Michał Jastrzębski wrote: > Hello, > >

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Hi, Shinobu, Correct, this is not the normal deployment scenario and the way of testbed setup. Cheers BR Chaoyi Huang ( joehuang ) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 04 May 2016 9:38 To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

On Wed, May 4, 2016 at 10:38 AM, Shinobu Kinjo wrote: > Hi Chaoyi, > > I didn't consider Ronghui's environment which I have no idea about. Anyhow this is my bad -; Sorry for that! Cheers, S > >> That's why Zhiyuan proposed hacking way to do it. > > Considering such a

[openstack-dev] [neutron][taas] cancel meeting

considering trip recovery and japanese holiday, this week's taas meeting is cancelled. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer

+1, Shinobu has given me many suggestions in my patches. On 4 May 2016 at 07:57, Zhipeng Huang wrote: > +1, still remember Shinobu getting started from basic concept of > tricircle, and now becoming a maester of multisite openstack :) > > On Tue, May 3, 2016 at 9:03 PM,

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Hi Chaoyi, I didn't consider Ronghui's environment which I have no idea about. > That's why Zhiyuan proposed hacking way to do it. Considering such a limited situation, I understood this solution is for particular situation which is not usual for cascaded stack environment. Is it same of what

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Hi, Shinobu, I think Zhiyuan's suggestion is mainly for Ronghui's environment, for his environment has very limited network infterfaces, it's difficult to experiment N-S feature. It would be recommended to use VMs for setting up Tricircle test bed with two bottom pods, so it's much more easier

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

Definitely a +1 from me On Tue, May 3, 2016 at 6:10 PM, Patrick East wrote: > +1, Michal has done some awesome work on Cinder! > > -Patrick > > On Tue, May 3, 2016 at 11:16 AM, Sean McGinnis > wrote: > >> Hey everyone, >> >> I would like to

Re: [openstack-dev] OpenStack's stackalytics is gummed up?

On 2016-05-04 10:52:56 +1000 (+1000), Michael Still wrote: > The instance of stackalytics run by the openstack-infra team seems to be > gummed up. [...] As is likely noted elsewhere, stackalytics.com is not run by the Infra team but rather by Mirantis. There is a stackalytics.openstack.org

Re: [openstack-dev] OpenStack's stackalytics is gummed up?

On Wed, May 4, 2016 at 11:03 AM, Davanum Srinivas wrote: > Michael, > > The stackalytics bots do not have access to gerrit at the moment. We > noticed it last friday and talked to infra folks: > >

Re: [openstack-dev] OpenStack's stackalytics is gummed up?

Michael, The stackalytics bots do not have access to gerrit at the moment. We noticed it last friday and talked to infra folks: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-04-29.log.html#t2016-04-29T14:24:07 Ilya Shakat helps a lot with the existing instance

[openstack-dev] OpenStack's stackalytics is gummed up?

The instance of stackalytics run by the openstack-infra team seems to be gummed up. It alleges that the last time there was a nova code review was April 17, which seems... unlikely. Who looks after this thing so I can ping them gently? Thanks, Michael -- Rackspace Australia

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

On Tue, May 3, 2016 at 3:46 PM, Clint Byrum wrote: > Excerpts from Morgan Fainberg's message of 2016-05-03 11:13:38 -0700: > > On Tue, May 3, 2016 at 10:28 AM, Monty Taylor > wrote: > > > > > On 05/03/2016 11:47 AM, Clint Byrum wrote: > > > > > >>

[openstack-dev] [nova] Austin summit "getting started in Nova" session recap

On Wednesday afternoon Sean Dague led a session on getting started in Nova. The full etherpad is here [1]. In this session we discussed a lot of the bulk work items we have in Nova right now, and how we can get newer people to the project involved in helping on these as an introduction, and

[openstack-dev] [Neutron] - Summit session on Future of Neutron API

Hi all, We had a session discussion the future of the Neutron API. The etherpad is available here: https://etherpad.openstack.org/p/newton-neutron-future-neutron-api The first two topics were Keystone V3 and Pecan. Both of those were relatively straight-forward. For the switch to Keystone V3,

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

+1, Michal has done some awesome work on Cinder! -Patrick On Tue, May 3, 2016 at 11:16 AM, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions

Re: [openstack-dev] [nova] Distributed Database

This thread has been a depressing read. I understand that the content is supposed to be distributed databases but for me it has become an inquisition of cellsV2. Our question has clearly become "Should we continue efforts on cellsV2?", which I will address head-on. We shouldn't be afraid

Re: [openstack-dev] [tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer

+1, still remember Shinobu getting started from basic concept of tricircle, and now becoming a maester of multisite openstack :) On Tue, May 3, 2016 at 9:03 PM, joehuang wrote: > Hi, > > I would like to propose adding Shinobu Kinjo to the Tricircle core > reviewer team. > >

[openstack-dev] [Neutron] neutron-lib report from the summit

At the Newton summit in Austin we held a session on the next steps for neutron-lib. Here is a report on what was discussed at the session. Etherpad: https://etherpad.openstack.org/p/newton-neutron-lib-next-steps Progress so far --- The package is on PyPI and sub-projects should be

[openstack-dev] [Neutron] User feedback track: end user and operator pain points - report

Hi all, We had a productive session with operators at the summit [1]. I wanted to be sure to go over the notes while they were fresh in my mind. Some of the issues still need some discussion... Probably the most contentious issue was that of creating HA routers when there aren't enough agents

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

On 03/05/2016 17:03, John Dickinson wrote: > TC, > > In reference to > http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html and > Thierry's reply, I'm currently drafting a TC resolution to update >

Re: [openstack-dev] [stackalytics]many projects missing in the "others" category

On 05/03/2016 09:11 AM, joehuang wrote: > Hello, > > Very sad to know that some projects are missing again in the "others" > category. When I want to cite some statistic data for Tricircle core reviewer > nomination, can't find the data for many "others" projects which usually are > listed

Re: [openstack-dev] [stackalytics]many projects missing in the "others" category

AFAIK the Tricircle is one of them. [1] How can we fix it out? [1] http://stackalytics.com/report/contribution/tricircle/90 Cheers, S On Tue, May 3, 2016 at 10:11 PM, joehuang wrote: > Hello, > > Very sad to know that some projects are missing again in the "others" >

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Andrew Laski's message of 2016-05-03 14:46:08 -0700: > > On Mon, May 2, 2016, at 01:13 PM, Edward Leafe wrote: > > On May 2, 2016, at 10:51 AM, Mike Bayer wrote: > > > > >> Concretely, we think that there are three possible approaches: > > >> 1) We can use

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

On Tue, May 3, 2016 at 1:46 PM, Clint Byrum wrote: > Excerpts from Morgan Fainberg's message of 2016-05-03 11:13:38 -0700: > > On Tue, May 3, 2016 at 10:28 AM, Monty Taylor > wrote: > > > > > On 05/03/2016 11:47 AM, Clint Byrum wrote: > > > > > >>

Re: [openstack-dev] [nova] Should be instance_dir in all nova compute node same ?

Is there any specific reason why this is require that way? or just a "feature"? Ghe Rivero On 03/05/16 11:42, Matthew Booth wrote: On Fri, Apr 29, 2016 at 2:47 AM, Eli Qiao > wrote: hi team, Is there any require that all compute

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Vega, On Tue, May 3, 2016 at 5:49 PM, Vega Cai wrote: > Hi all, > > Just would like to share a way to test Tricircle north-south L3 networking > without requiring the third interface. > > In the Tricircle readme, it is said that you need to add an interface in > your host

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

> On May 3, 2016, at 14:47, Truman, Travis > wrote: > > Major has made an incredible number of contributions of code and reviews to > the OpenStack-Ansible community. Given his role as the primary author of the > openstack-ansible-security project, I can

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

RadosGW has been excluded from joining the OpenStack community in part due to its use of c++. Now that we're talking about alternate languages, that may be on the table now? Thanks, Kevin From: Doug Hellmann [d...@doughellmann.com] Sent: Tuesday, May 03,

[openstack-dev] [release] release hiatus for 2-6 May

Because some of the release team is traveling this week, and the infrastructure team is also dealing with some issues that may make building releases unreliable, we're going to hold off on publishing any releases this week. We will check with the infra team on 9 May and resume publishing releases

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

Excerpts from John Dickinson's message of 2016-05-03 15:05:08 -0700: > > On 3 May 2016, at 14:50, Doug Hellmann wrote: > > > Excerpts from John Dickinson's message of 2016-05-03 13:01:28 -0700: > >> > >> On 3 May 2016, at 12:19, Monty Taylor wrote: > >> > >>> On 05/03/2016 01:45 PM, Michael

[openstack-dev] [searchlight] OpenStack Newton Austin Summit

Hello everybody, Below is my summary of the Searchlight related discussions and results from the Austin Summit. I apologize for the length, but just decided to include all the session summaries in a single email. As always, please correct, add, etc! 5 Sessions (3 Searchlight Session, 1 joint

Re: [openstack-dev] [devstack][neutron] VMWare NSX CI - voting on devstack changes long after plugin decomposition

There is a job which has been turned on again by mistake and I'm working on ensuring it's put to sleep again (for good this time). If you can avoid disabling the whole account it would be great as the same credentials are used by the still-voting nova CI. Cheers, Salvatore On 3 May 2016 at

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

Excerpts from Fox, Kevin M's message of 2016-05-03 22:11:06 +: > If we let go in, and there are no pluggable middleware, where does RadosGW > and other Swift api compatible implementations then stand? Should we bless > c++ too? As I understand it, there are a lot of clouds deployed with the

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

On 05/03/2016 03:14 AM, Daniel P. Berrange wrote: There are currently many options for live migration with QEMU that can assist in completion Given this I've spent the last week creating an automated test harness for QEMU upstream which triggers migration with an extreme guest CPU load and

Re: [openstack-dev] [kolla][gate] Add a gating check job for precheck

Hi, Lei and Steve, I think what Lei said makes sense. When I look at the other proposed gate jobs [1], the function can be tested against the service. However, for the precheck roles, it depends on the deployment. If the deployment task could not pass the precheck phase, the job should be stopped.

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

If we let go in, and there are no pluggable middleware, where does RadosGW and other Swift api compatible implementations then stand? Should we bless c++ too? As I understand it, there are a lot of clouds deployed with the RadosGW but Refstack rejects them. Thanks, Kevin

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

Excerpts from Doug Hellmann's message of 2016-05-03 16:45:47 -0500: > Excerpts from Joshua Harlow's message of 2016-05-03 14:24:13 -0700: > > 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

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

On 3 May 2016, at 14:50, Doug Hellmann wrote: > Excerpts from John Dickinson's message of 2016-05-03 13:01:28 -0700: >> >> On 3 May 2016, at 12:19, Monty Taylor wrote: >> >>> On 05/03/2016 01:45 PM, Michael Krotscheck wrote: On Tue, May 3, 2016 at 9:03 AM John Dickinson

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

Excerpts from John Dickinson's message of 2016-05-03 13:01:28 -0700: > > On 3 May 2016, at 12:19, Monty Taylor wrote: > > > On 05/03/2016 01:45 PM, Michael Krotscheck wrote: > >> On Tue, May 3, 2016 at 9:03 AM John Dickinson >> > wrote: > >> > >> > >> As a

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

Hi Joshua. I think than Mistral have already fast solution - they customised oslo.messaging rpc to achieve ack-after-process in Mistral code base About solution in oslo.messaging code base… I plan to write spec for new oslo.messaging driver interface soon as was agreed during design session

Re: [openstack-dev] [nova] Distributed Database

On Mon, May 2, 2016, at 01:13 PM, Edward Leafe wrote: > On May 2, 2016, at 10:51 AM, Mike Bayer wrote: > > >> Concretely, we think that there are three possible approaches: > >> 1) We can use the SQLAlchemy API as the common denominator between a > >> relational and

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

Excerpts from Joshua Harlow's message of 2016-05-03 14:24:13 -0700: > 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 > that project move forward in their desire to have some kind

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

On 05/03/2016 10:34 AM, 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 detail on some of these topics either via > subsequent more focussed threads an/or some blog posts

[openstack-dev] [fuel] Release notes with reno

To follow up one of the points brought up in the fuel-plugins [1] session. We briefly discussed using reno [2]. The system appears to be quite clean and concise and will work for this need, and should work for general release notes. I'd propose that we start using reno to catalog changes to the

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

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 that project move forward in their desire to have some kind of process than ack (vs the existing ack then process) in there usage of

Re: [openstack-dev] [kolla][kolla-k8s] Core team

On 3 May 2016 at 14:36, Martin André wrote: > On Tue, May 3, 2016 at 6:48 PM, Michał Jastrzębski wrote: >> Hello, >> >> Since it seems that we have voted for separation of kolla-k8s repos >> (yay!) I would like to table another discussion (but let's wait

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Morgan Fainberg's message of 2016-05-03 11:13:38 -0700: > On Tue, May 3, 2016 at 10:28 AM, Monty Taylor wrote: > > > On 05/03/2016 11:47 AM, Clint Byrum wrote: > > > >> Excerpts from Monty Taylor's message of 2016-05-03 07:59:21 -0700: > >> > >>> On 05/03/2016

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mike Bayer's message of 2016-05-03 09:04:00 -0700: > > On 05/02/2016 01:48 PM, Clint Byrum wrote: > >> > > > > FWIW, I agree with you. If you're going to use SQLAlchemy, use it to > > take advantage of the relational model. > > > > However, how is what you describe a win? Whether

Re: [openstack-dev] [glance] [glare] [heat] [tosca] [tacker] [murano] [magnum] [app-catalog] Austin summit summary: Generic cataloging and Glare v1 API

I believe this model polarizes the community a bit as far as picking reviews go. We voted to remove it in Mitaka and I was hoping we would workout a way to bring the community together in the Glare reviews. My goal is to have champions for each module that is being worked on in Newton

[openstack-dev] [nova] api-ref docs cleanup review sprint 5/9 and 5/11

We discussed at the summit a need for a review sprint on the api-ref docs cleanup effort that's going on. See Sean's email on that from a few weeks ago [1]. So we plan to do a review sprint next Monday 5/9 and Wednesday 5/11. The series to review is here [2]. [1]

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

On 3 May 2016, at 12:19, Monty Taylor wrote: > On 05/03/2016 01:45 PM, Michael Krotscheck wrote: >> On Tue, May 3, 2016 at 9:03 AM John Dickinson > > wrote: >> >> >> As a starting point, what would you like to see addressed in the >> document I'm

Re: [openstack-dev] [glance] [glare] [heat] [tosca] [tacker] [murano] [magnum] [app-catalog] Austin summit summary: Generic cataloging and Glare v1 API

Comment inline. On 5/3/16 3:21 PM, Flavio Percoco wrote: > On 02/05/16 19:09 -0400, Nikhil Komawar wrote: > >> Added a few more tags to the subject line. >> >> >> >> On 5/2/16 7:05 PM, Nikhil Komawar wrote: >> >>> Hello everyone, >>> >>> >>> >>> Just wanted to send a brief summary of the

Re: [openstack-dev] [magnum] Notes for Magnum design summit

> -Original Message- > From: Ricardo Rocha [mailto:rocha.po...@gmail.com] > Sent: May-03-16 8:34 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit > > Hi. > > On Mon, May 2, 2016 at 7:11 PM,

Re: [openstack-dev] [kolla][kolla-k8s] Core team

On Tue, May 3, 2016 at 6:48 PM, Michał Jastrzębski wrote: > Hello, > > Since it seems that we have voted for separation of kolla-k8s repos > (yay!) I would like to table another discussion (but let's wait till > its official). > > Core Team. > > We need to build up new core team

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

On Tue, 3 May 2016 12:16:24 -0400 Rayson Ho wrote: > I like Go! However, Go does not offer binary compatibility between point > releases. For those who install from source it may not be a big issue, but > for commercial distributions that pre-package & pre-compile

[openstack-dev] [keystone] newton release deadlines

A few keystone specific dates and definitions: - May 30-03 -> R-18 -> **Spec proposal freeze** - Specs must be available for review by this week - keystone newton-1 will be released this week - Jul 04-06 -> R-13 -> **Spec freeze** - Specs must be merged by this week - Jul 11-15 -> R-12 ->

Re: [openstack-dev] [magnum] Notes for Magnum design summit

> -Original Message- > From: Cammann, Tom [mailto:tom.camm...@hpe.com] > Sent: May-02-16 1:12 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit > > Thanks for the write up Hongbin and thanks to

Re: [openstack-dev] [glance] [glare] [heat] [tosca] [tacker] [murano] [magnum] [app-catalog] Austin summit summary: Generic cataloging and Glare v1 API

On 02/05/16 19:09 -0400, Nikhil Komawar wrote: Added a few more tags to the subject line. On 5/2/16 7:05 PM, Nikhil Komawar wrote: Hello everyone, Just wanted to send a brief summary of the discussions at the summit. This list is not holistic however, it covers the relevant aspects that

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

On 05/03/2016 01:45 PM, Michael Krotscheck wrote: On Tue, May 3, 2016 at 9:03 AM John Dickinson > wrote: As a starting point, what would you like to see addressed in the document I'm drafting? I'm going through this project with JavaScript right now.

Re: [openstack-dev] [neutron] OSC transition

I've asked about the conclusion here [1]. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html Na Zhu/China/IBM wrote on 05/01/2016 09:11:43 PM: > From: Na Zhu/China/IBM@IBMCN > To: rth...@us.ibm.com > Cc: openstack-dev@lists.openstack.org > Date: 05/01/2016 09:11 PM >

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

On 05/03/2016 02: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 [0] and code contributions [1] have > been significant for some time now. > > His persistence with versioned objects has

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

On 3 May 2016 at 11:01, Richard Theis wrote: > Steve Martinelli wrote on 04/22/2016 05:49:32 PM: > > > From: Steve Martinelli > > To: "OpenStack Development Mailing List (not for usage questions)" > >

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

On 05/03/2016 01:47 PM, Truman, Travis wrote: > Major has made an incredible number of contributions of code and reviews > to the OpenStack-Ansible community. Given his role as the primary author > of the openstack-ansible-security project, I can think of no better > addition to the core reviewer

[openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

Major has made an incredible number of contributions of code and reviews to the OpenStack-Ansible community. Given his role as the primary author of the openstack-ansible-security project, I can think of no better addition to the core reviewer team. Travis Truman

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

On Tue, May 3, 2016 at 9:03 AM John Dickinson wrote: > > As a starting point, what would you like to see addressed in the document > I'm drafting? > I'm going through this project with JavaScript right now. Here's some of the things I've had to address: - Common language

[openstack-dev] [Neutron] stadium evolution - report

Hi Neutrinos, For those who could not attend or be in Austin for session [2], we've had some recent discussions [1] and past ones in [3]. I am trying to get to a closure on this topic, and I followed up with a spec proposal on [4]. I am open to suggestions on how to improve the proposal and how

[openstack-dev] [infra] [fuel] [javascript] Supporting ES6

TL/DR: Should we support EcmaScript 6? Discussions I've had on the topic: Vancouver: - Browser support is not yet broad enough, so no- we shouldn't support ES6. - TypeScript is too closely tied to Corporations (tm), not really an open standard. Do not support TypeScript. Austin: - Fuel is using

[openstack-dev] [Congress] Austin recap

Hi all, Here’s a quick summary of the Congress activities in Austin. Everyone should feel free to chime in with corrections and things I missed. 1. Talks Masahito gave a talk on applying Congress for fault recovery in the context of NFV.

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

Even though I am not a core member, but I would like to vote for Michal as he truely deserves it... Huge acceptance from my side.. +1 Best Regards, Sheel Rana On Tue, May 3, 2016 at 11:46 PM, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko

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

Hey everyone, I would like to nominate Michał Dulko to the Cinder core team. Michał's contributions with both code reviews [0] and code contributions [1] have been significant for some time now. His persistence with versioned objects has been instrumental in getting support in the Mitaka release

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

On Tue, May 3, 2016 at 10:28 AM, Monty Taylor wrote: > On 05/03/2016 11:47 AM, Clint Byrum wrote: > >> Excerpts from Monty Taylor's message of 2016-05-03 07:59:21 -0700: >> >>> On 05/03/2016 08:55 AM, Clint Byrum wrote: >>> Perhaps we have different perspectives.

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

Steve Martinelli wrote on 04/22/2016 05:49:32 PM: > From: Steve Martinelli > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 04/22/2016 05:52 PM > Subject: Re: [openstack-dev]

[openstack-dev] [keystone] weekly meeting canceled on 5/3

sorry for the late notice - there are no items on the agenda and i think most are still decompressing from the summit __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [puppet] Austin summit sessions recap

On Tue, May 3, 2016 at 6:38 AM Emilien Macchi wrote: > Here's a summary of Puppet OpenStack sessions [1] during Austin summit. > > * General feedback is excellent, things are stable, no major changes > are coming during the next cycle. > * We discussed about the work we want

[openstack-dev] [devstack][neutron] VMWare NSX CI - voting on devstack changes long after plugin decomposition

When the VMWare plugin was decomposed from the main Neutron tree (https://review.openstack.org/#/c/160463/) it appears that the CI system was left turned on. http://208.91.1.172/logs/neutron/168438/48/423669-large-ops/logs/q-svc.log.2016-05-03-085740 2016-05-03 09:21:00.577 21706 ERROR

Re: [openstack-dev] [api] [docs] [cinder] [swift] [glance] [keystone] [ironic] [trove] [neutron] [heat] [senlin] [manila] [sahara] RST + YAML files ready for pick up from WADL migration

On Tue, May 03, 2016 at 08:29:16AM -0500, Anne Gentle wrote: > Hi all, > This patch contains all the RST + YAML for projects to bring over to their > repos to begin building API reference information from within your repo. > Get a copy of this patch, and pick up the files for your service in >

Re: [openstack-dev] [Kolla] lock the distro version in the stable branch

This commit fixes the tag: https://github.com/openstack/kolla/commit/e2fa75fce6f90de8b2766070bb65d0b80bcad8c8 But I think fixing the tag in dockerfile of base container image is better - Hui On Tue, May 3, 2016 at 12:12 PM, Jeffrey Zhang wrote: > Hey guys, > >

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

On 05/03/2016 11:47 AM, Clint Byrum wrote: Excerpts from Monty Taylor's message of 2016-05-03 07:59:21 -0700: On 05/03/2016 08:55 AM, Clint Byrum wrote: Perhaps we have different perspectives. How is accepting what we previously emitted and told the user would be valid sneaky or wrong? Sounds

[openstack-dev] [nova] Newton mid-cycle meetup RSVP

We're doing the Nova mid-cycle meetup for Newton at the Intel campus in Hillsboro, OR on July 19-21. I have an RSVP form here: http://goo.gl/forms/MxrriHsABq If you plan on attending, or think you might be able to (or are trying to), please fill that out. I'd like to have RSVPs completed by

Re: [openstack-dev] [Kolla] lock the distro version in the stable branch

From: Jeffrey Zhang > Reply-To: OpenStack Development Mailing List > Date: Tuesday, May 3, 2016 at 9:12 AM To: OpenStack Development Mailing List

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Adam Young's message of 2016-05-03 07:21:52 -0700: > On 05/03/2016 09:55 AM, Clint Byrum wrote: > > When the operator has configured a new token format to emit, they should > > also be able to allow any previously emitted formats to be validated to > > allow users a smooth transition

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Lance Bragstad's message of 2016-05-03 07:42:43 -0700: > If we were to write a uuid/fernet hybrid provider, it would only be > expected to support something like stable/liberty to stable/mitaka, right? > This is something that we could contribute to stackforge, too. > If done the

Re: [openstack-dev] [oslo] config: deduce related options for config generator?

Excerpts from Markus Zoeller's message of 2016-05-03 18:26:50 +0200: > While working on [1] I came across a config option ("pybasedir") > which gets used as a base for many other options, for example > "state_path". The option "state_path" shows then a default value > "state_path = $pybasedir". >

[openstack-dev] [kolla][kolla-k8s] Core team

Hello, Since it seems that we have voted for separation of kolla-k8s repos (yay!) I would like to table another discussion (but let's wait till its official). Core Team. We need to build up new core team that will guard the gates on our brand new repo (when it arrives). One of ideas Steven

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Monty Taylor's message of 2016-05-03 07:59:21 -0700: > On 05/03/2016 08:55 AM, Clint Byrum wrote: > > > > Perhaps we have different perspectives. How is accepting what we > > previously emitted and told the user would be valid sneaky or wrong? > > Sounds like common sense due

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

On Tue, May 3, 2016 at 12:24 PM, John Dickinson wrote: > That's an interesting point. I'm not very familiar with Golang itself yet, > and I haven't yet had to manage any Golang projects in prod. These sorts of > questions are great! > > See: https://golang.org/doc/go1compat > If

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

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 detail on some of these topics either via subsequent more focussed threads an/or some blog posts but what follows is an overview of our summit sessions[1]

[openstack-dev] [neutron][nova][SR-IOV] SR-IOV meeting May 3 2016 - update

Hi, I just wanted to give a short update regarding SR-IOV/PCI Passthrough /NFV meeting. * We decide to change the meeting frequency to every week, until PCI/SR-IOV/NUMA will be more stable see [1] * Improving SR-IOV/PCI Passthrough /NFV testing o With the help of

[openstack-dev] [oslo] config: deduce related options for config generator?

While working on [1] I came across a config option ("pybasedir") which gets used as a base for many other options, for example "state_path". The option "state_path" shows then a default value "state_path = $pybasedir". My question here is, is it possible/reasonable to enhance oslo.config to add an

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

That's an interesting point. I'm not very familiar with Golang itself yet, and I haven't yet had to manage any Golang projects in prod. These sorts of questions are great! If a distro is distributing pre-compiled binaries, isn't the compatibility issue up to the distros? OpenStack is not

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

That's a good question, and I'll be sure to address it. Thanks. In the context of "golang code in swift", any discussion around a "goslo" library would be up to the oslo team, I think. The proposed functionality that would be in golang in swift does not currently depend on any oslo library. In

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Edward Leafe's message of 2016-05-03 08:20:36 -0700: > On May 3, 2016, at 6:45 AM, Miles Gould wrote: > > >> This DB could be an RDBMS or Cassandra, depending on the deployer's > >> preferences > > AFAICT this would mean introducing and maintaining a layer that

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

I like Go! However, Go does not offer binary compatibility between point releases. For those who install from source it may not be a big issue, but for commercial distributions that pre-package & pre-compile everything, then the compiled Go libs won't be compatible with old/new releases of the Go

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

John, How would Oslo like functionality be included ? Would the aim be to produce equivalent libraries ? Tim On 03/05/16 17:58, "John Dickinson" wrote: >TC, > >In reference to >http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html and >Thierry's reply, I'm

[openstack-dev] [Kolla] lock the distro version in the stable branch

Hey guys, Recently, the ubuntu 16.04 is out and it crashed kolla when using ubuntu:lastest to build the images. even though kolla support multi base-tag, the kolla will failed when using other base-tag except for centos:7, ubuntu:14.04, rhel:7. And it is also hard to support all kind of the

  1   2   >