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] [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. > >

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

[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

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,

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] 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] [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

[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

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] [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

[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] 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] [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] [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

[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:

[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

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

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, 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] [kolla][kubernetes] One repo vs two

Paul, Just to be clear, we are not putting master on pause for 4-6 weeks to split apart the repos to enable kubernetes development. The option on the table at this point are A) kolla repo as it exists today and empty repo for k8s B) kolla repo as it exists today with kubernetes integrated A

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

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 you use SELECT .. FOR UPDATE, or a stored procedure, the lock is not distributed, and

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] Timeframe for naming the P release?

Here are other ideas? Paul-Revere https://en.wikipedia.org/wiki/Paul_Revere Peabody A town north east of Boston. No special reason except saying the name personally makes me chuckle Patriots https://en.wikipedia.org/wiki/New_England_Patriots -Original

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

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] Leadership training dates - please confirm attendance

On Fri, Apr 22, 2016 at 7:57 AM, Colette Alexander wrote: > On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann wrote: >> >> Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700: >> >> > >> > Hi everyone, >> > >> > Just checking in

[openstack-dev] [tc] supporting Go

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 http://governance.openstack.org/resolutions/20150901-programming-languages.html to include Go as a supported language in OpenStack

[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

Re: [openstack-dev] [magnum][all] Build unified abstraction for all COEs

Hi all, According to the decision in the design summit [1], we are going to narrow the scope of the Magnum project [2]. In particular, Magnum will focus on COEs deployment and management. The efforts of building unified container abstraction will potentially go into a new project. My role here

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

I +1 for split the kolla-k8s repo, too. Here is the reason: 1. Kolla will be split into several repo in the future: kolla-docker, kolla-ansible. So if we use one repo for k8s, we will split it again. It will be more painful to do this. 2. Normally, the kolla-docker, kolla-ansible and

[openstack-dev] [neutron] neutron-qos meeting cancelled this week

All, Because many of us are still recovering from the summit or on vacation, we are cancelling the neutron-qos meeting for tomorrow. We will resume with the next meeting, on May 18th. Thanks, --N. __ OpenStack Development

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

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

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] [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: > > > > > >>

[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,

[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

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 api-site/api-ref/source/: https://review.openstack.org/#/c/311596/ There

[openstack-dev] [puppet] complete this 1 minute survey if you're Puppet OpenStack user

http://goo.gl/forms/7VYibKHx1c We would like to gather feedback of what our users are running, so we can improve our CI and update the versions of Puppet / Ruby / Operating Systems that we're gating. Thanks a lot for your time, -- Emilien Macchi

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 3, 2016 at 8:39 AM, Sheel Rana Insaan wrote: > Hi Anne, > > Sure, I will pick for cinder. > > Thanks!! > > Thank you! I added your name to the wiki page: https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan Meant to add that to my email

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

Excerpts from Matt Fischer's message of 2016-05-02 16:39:02 -0700: > On Mon, May 2, 2016 at 5:26 PM, Clint Byrum wrote: > > > Hello! I enjoyed very much listening in on the default token provider > > work session last week in Austin, so thanks everyone for participating > > in

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

Hi Anne, Sure, I will pick for cinder. Thanks!! Best Regards, Sheel Rana On Tue, May 3, 2016 at 6:59 PM, 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

Re: [openstack-dev] [nova] Austin summit cells v2 session recap

Thanks for the summary, this is great. Comments inline. On Mon, May 2, 2016, at 09:32 PM, Matt Riedemann wrote: > Andrew Laski led a double session for cells v2 on Wednesday afternoon. > The full session etherpad is here [1]. > > Andrew started with an overview of what's done and what's in

Re: [openstack-dev] [nova] Austin summit versioned notification

> On May 3, 2016, at 8:58 AM, Matt Riedemann wrote: > > On 5/3/2016 3:10 AM, Balázs Gibizer wrote: >> Hi, >> >> Last week Friday in Austin we discussed the way forward with the versioned >> notification transformation in Nova. >> >> We agreed that when we separate

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

Hi, I would like to propose adding Shinobu Kinjo to the Tricircle core reviewer team. Shinobu has been a highly valuable reviewer to Tricircle for the past few months. His contribution covers each patch submitted, document, etherpad discussion, and always give valueable, meaningful and

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

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 "others" category. Is there any new rule in

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

On Mon, May 2, 2016 at 6:26 PM, Clint Byrum wrote: > Hello! I enjoyed very much listening in on the default token provider > work session last week in Austin, so thanks everyone for participating > in that. I did not speak up then, because I wasn't really sure of this > idea

Re: [openstack-dev] [nova] Austin summit versioned notification

On 5/3/2016 3:10 AM, Balázs Gibizer wrote: Hi, Last week Friday in Austin we discussed the way forward with the versioned notification transformation in Nova. We agreed that when we separate the object model use for notifications from the nova object model we still use the NovaObject as a base

Re: [openstack-dev] [nova] FYI: Citrix XenServer CI is disabled from voting

The failure rate was indeed 100%; there were some requirements on packages not installed in our CI environment (libssl-dev libffi-dev) which were causing all failures. This is now fixed and the CI is back to voting on passing changes. I have re-queued all jobs which failed in less than 6

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

On 05/03/2016 09:55 AM, Clint Byrum wrote: Excerpts from Steve Martinelli's message of 2016-05-02 19:56:15 -0700: Comments inline... On Mon, May 2, 2016 at 7:39 PM, Matt Fischer wrote: On Mon, May 2, 2016 at 5:26 PM, Clint Byrum wrote: Hello! I

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] [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] [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

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

[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

[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]

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

[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] [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 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] [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

[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] [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

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] [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

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] [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". >

<    1   2