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.

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

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

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

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.

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

[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

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

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

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

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

[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

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

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

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

On May 3, 2016 1:53 AM, "Davanum Srinivas" wrote: > > Sorry for top-post... > > There's a third option : Using Feature branch for Kubernetes with a > custom gerrit group > > * Feature branch can be sync'ed from Master periodically > * Feature branch can have it's own separate

Re: [openstack-dev] [TripleO] Summit Summary?

On 03/05/16 04:35, Jason Rist wrote: > Hey Everyone - Forgive me if this has already been sent out - I looked > through all of my emails and didn't see something yet. Can someone > provide a summary of TripleO from the summit, for instance some of the > output from the design sessions like the

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

On 05/02/2016 05:53 PM, Jeff Peeler wrote: On Mon, May 2, 2016 at 9:50 AM, Andreas Jaeger wrote: On 05/02/2016 03:05 PM, Steven Dake (stdake) wrote: Swapnil, I gather this is what people want but this cannot be done with git and maintain history. To do this, we would have to

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

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 to br-ext bridge. One interface to access the host, one interface for east-west networking

Re: [openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters:

On 04/22/2016 09:51 AM, Shinobu Kinjo wrote: Hi TripleO Team, If you could take care of ${subject}, it would be nice. [1] https://review.openstack.org/#/c/247669 ack, I liked revision 6 more than 7 but it might not work as interpolation always returns a string and we need a dict there

Re: [openstack-dev] [Swift] going forward

John Dickinson wrote: At the summit last week, the Swift community spent a lot of time discussing the feature/hummingbird branch. (For those who don't know, the feature/hummingbird branch contains some parts of Swift which have been reimplemented in Go.) As a result of that summit discussion,

Re: [openstack-dev] [nova] next min libvirt?

On Fri, Apr 29, 2016 at 03:16:56PM -0500, Matt Riedemann wrote: > On 4/29/2016 10:28 AM, Daniel P. Berrange wrote: > >On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > >>We've just landed the libvirt min to bump us up to 1.2.1 required. It's > >>probably a good time consider the

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

Thanks Matt That really surprised me. On 2016年05月03日 17: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 node's instance_dir should be same? Yes. This

Re: [openstack-dev] [TripleO] Summit Summary?

On Mon, May 02, 2016 at 07:35:47PM -0600, Jason Rist wrote: > Hey Everyone - Forgive me if this has already been sent out - I looked > through all of my emails and didn't see something yet. Can someone > provide a summary of TripleO from the summit, for instance some of the > output from the

Re: [openstack-dev] [tripleo] composable roles team

On 05/02/2016 07:47 PM, Brent Eagles wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/2016 08:01 PM, Emilien Macchi wrote: If a feature can't land without disruption, then why not using a special branch to be merged once the feature is complete ? The problem is that during

[openstack-dev] [Nova] Live migration meeting today

First live migration meeting to kick off after the summit will be today, see: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] next min libvirt?

On Sat, Apr 30, 2016 at 10:28:23AM -0500, Thomas Bechtold wrote: > Hi, > > On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > > probably a good time consider the appropriate bump for Otaca. > > > > By that

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

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 class to avoid change in the wire format

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

Having read through the full thread I'm still in support of separate repos. I think the explanations Jeff Peeler and Adam Young have put forward summarise my thoughts very well. One of the main arguments I seem to be hearing for a single repo is Git tooling which I don't think is a good one;

Re: [openstack-dev] [Nova] Libvirt version requirement

On Mon, May 02, 2016 at 11:27:01AM +0800, ZhiQiang Fan wrote: > Hi Nova cores, > > There is a spec[1] submitted to Telemetry project for Newton release, > mentioned that a new feature requires libvirt >= 1.3.4 , I'm not sure if > this will have bad impact to Nova service, so I open this thread

Re: [openstack-dev] [tripleo] composable roles team

On Fri, Apr 29, 2016 at 03:27:29PM -0500, Emilien Macchi wrote: > Hi, > > One of the most urgent tasks we need to achieve in TripleO during > Newton cycle is the composable roles support. > So we decided to build a team that would focus on it during the next weeks. Note that there is some

Re: [openstack-dev] [octavia] amphora flavour and load balancer topology

On Tue, May 3, 2016 at 10:30 AM, Michael Johnson wrote: > Hi Lingxian, > > On #2, we would like to enable neutron flavors to support the > selection of topology. For example, "bronze" flavor may be > standalone, "silver" would be active/standby. However, that > capability

Re: [openstack-dev] [Nova] Could you tell me the best way to develop openstack in Windows?

I agree. It is a lot easier to just develop on a Linux environment. You could set-up a Linux VM using VirtualBox or VMware tools to do this on Windows. You would then be aligned with tools and documentation in the community and hence better able to get up and running. Regards, Martin From:

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

On Fri, Apr 29, 2016 at 10:32:09PM +, Murray, Paul (HP Cloud) wrote: > The following summarizes status of the main topics relating to live migration > after the Newton design summit. Please feel free to correct any inaccuracies > or add additional information. > Post copy > > The spec to add

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

On Fri, Apr 29, 2016 at 2:47 AM, Eli Qiao wrote: > hi team, > > Is there any require that all compute node's instance_dir should be same? > Yes. This is assumed in many places, certainly in cold migration/resize. Matt -- Matthew Booth Red Hat Engineering, Virtualisation

Re: [openstack-dev] [Nova] Libvirt version requirement

Glad to hear the news. Thanks, Daniel and Michael. On Tue, May 3, 2016 at 5:19 PM, Daniel P. Berrange wrote: > On Mon, May 02, 2016 at 11:27:01AM +0800, ZhiQiang Fan wrote: > > Hi Nova cores, > > > > There is a spec[1] submitted to Telemetry project for Newton release, > >

[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

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

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

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

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

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

[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] [magnum] Notes for Magnum design summit

Hi. On Mon, May 2, 2016 at 7:11 PM, Cammann, Tom wrote: > Thanks for the write up Hongbin and thanks to all those who contributed to > the design summit. A few comments on the summaries below. > > 6. Ironic Integration: >

Re: [openstack-dev] [nova] next min libvirt?

On Tue, May 03, 2016 at 10:08:06AM +0100, Daniel P. Berrange wrote: > On Sat, Apr 30, 2016 at 10:28:23AM -0500, Thomas Bechtold wrote: > > Hi, > > > > On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > > > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > > >

Re: [openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?

On Mon, May 02, 2016 at 03:10:56PM -0700, Kevin Benton wrote: > This patch removed the ./rejoin-stack.sh script: > https://review.openstack.org/#/c/291453/ > > I relied on this heavily in my development VM which sees lots of restarts > because of various things (VM becomes unresponsive in load

[openstack-dev] [Smaug]- IRC Meeting today (05/03) - 1400 UTC SM

Hi All, We will hold our bi-weekly IRC meeting today (Tuesday, 05/03) at 1400 UTC in #openstack-meeting Please review the proposed meeting agenda here: https://wiki.openstack.org/wiki/Meetings/smaug Please feel free to add to the agenda any

Re: [openstack-dev] [kuryr] Question for Antoni Puimedon about load balancers and overlay networks

On Mon, May 2, 2016 at 8:11 PM, Mike Spreitzer wrote: > I am looking at > https://www.openstack.org/videos/video/project-kuryr-docker-delivered-kubernetes-next, > around 28:00. You have said that overlay networks are involved, and are > now talking about load balancers. Is

[openstack-dev] [nova] driver review dashboards

One of the ideas that came up was a morning review dashboard which would list each driver, and some criteria to indicate it was ready to merge. This could either be a star by a contact person, or a +1 by some specific person. I think it's probably also a good idea to filter by "passes specific

[openstack-dev] [puppet] weekly meeting #80

Hi, If you have any topic that you would like to discuss, please add it to the topic list: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160503 If we don't have topics, we'll probably cancel the meeting this week. I'm currently working on a summary of what happened during

Re: [openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?

On Mon, May 2, 2016 at 5:10 PM, Kevin Benton wrote: > Now am I correct in understanding that when this happens there is no way > to restart the services in a simple manner without blowing away everything > and starting over? Unless I'm missing some way to run ./stack.sh without

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

cc'ing Travis and Steve directly, since they will likely be very interested in this effort from the Project Searchlight perspective. :) On 05/03/2016 04:10 AM, Balázs Gibizer wrote: Hi, Last week Friday in Austin we discussed the way forward with the versioned notification transformation in

Re: [openstack-dev] [nova] driver review dashboards

Hi Sean, > [section "XenServer"] > query = label:Code-Review>=1,bob.b...@citrix.com file:xenserver I believe this should be file:xenapi? Can you match multiple files here? Most files are under the xenapi trees, but it would miss some files in plugins/xenserver and not in

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

On 02/05/16 18:43, Jay Pipes 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 abstracts over RDBMSes and Cassandra. That's a big abstraction, over two quite different systems, and it would be

Re: [openstack-dev] [glance] Interest in contributing to OpenStack

Hello Nikhil, Thanks, for the reply. I would really love to make some substantial contribution to Glance. I would put in some time familiarizing myself with the codebase and I have already assigned myself to a bug (https://bugs.launchpad.net/glance/+bug/1569937), so I can start working on it.

[openstack-dev] [StoryBoard] Meetings (and meetup) info

Hi all! At the summit, a few people asked us about StoryBoard meetings (and the next StoryBoard meetup). So here are the details: IRC Meetings (text shamelessly copied from wiki): - StoryBoard holds public weekly meetings in #openstack-meeting,

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

-Original Message- From: Ricardo Rocha [mailto:rocha.po...@gmail.com] Sent: Tuesday, May 03, 2016 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, Cammann,

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

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: May 03, 2016 15:58 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] Austin summit versioned notification > > On 5/3/2016 3:10 AM, Balázs Gibizer wrote: > > Hi, > > > > Last

[openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

Hi, First of all, I wanted to thank again to all the participants in the fruitful Aodh-Vitrage design session in Austin :) I wanted to show in this email, the problem that we have when creating 2 event alarms with the same name. Here is what I got in the command line:

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

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. On Tue, May 3, 2016 at 9:21 AM, Adam Young wrote: > On 05/03/2016

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

On 05/03/2016 08: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] Timeframe for naming the P release?

On 05/03/2016 09:29 AM, Jonathan D. Proulx wrote: On Tue, May 03, 2016 at 12:09:40AM -0400, Adam Young wrote: :On 05/02/2016 08:07 PM, Rochelle Grober wrote: :>But, the original spelling of the landing site is Plimoth Rock. There were still highway signs up in the 70's directing folks to

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

On Tue, May 03 2016, Weyl, Alexey (Nokia - IL) wrote: > Do you think it is possible to drop the uniqueness of the alarm name in Aodh > (for the Vitrage use cases that we talked about in the design session)? Should be doable yeah, it's really just a (badly written) check in the API. Shoot us a

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

Alarm name unique constraint is only applied to each project, I don't remember the original cause, but in our customer's environment, alarm will be showed in the portal, with their name, no uuid, because user will be confused about such a random like string, then if alarm name can be duplicated,

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

> -Original Message- > From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > Sent: May 03, 2016 16:10 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] Austin summit versioned notification > > > > On May 3, 2016, at 8:58 AM,

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

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 abstracts > over RDBMSes and Cassandra. That's a big abstraction, over two

Re: [openstack-dev] [glance] Interest in contributing to OpenStack

Sounds good, Djimeli. Best way to get to know the team might be to join us during one of the weekly meetings http://eavesdrop.openstack.org/#Glance_Team_Meeting Alternatively, you can join Glare update meeting to meet a few of us, if that time is more convenient to you

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

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 to do during Newton cycle [2]: Ubuntu 16.04 LTS Make Puppet OpenStack modules

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

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 enjoyed very much listening in

Re: [openstack-dev] Timeframe for naming the P release?

On Tue, May 03, 2016 at 12:09:40AM -0400, Adam Young wrote: :On 05/02/2016 08:07 PM, Rochelle Grober wrote: :>But, the original spelling of the landing site is Plimoth Rock. There were still highway signs up in the 70's directing folks to "Plimoth Rock" There are trill signs with both

Re: [openstack-dev] Timeframe for naming the P release?

Dell - Internal Use - Confidential Providence -Original Message- From: Monty Taylor [mailto:mord...@inaugust.com] Sent: Tuesday, May 03, 2016 9:38 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Timeframe for naming the P release? On 05/03/2016 09:29 AM, Jonathan D.

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

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

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

[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

  1   2   >