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 o

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 I'll

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,

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

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 is not yet implemented.

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:

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

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

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 appropr

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 time

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

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; w

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 Team Phone: +442070094

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, > > mentioned that a new f

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 confusi

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 is assumed in many place

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 desig

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 this Neutron LBaaS?

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

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

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 h

[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

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

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 > losing previous

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 No

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 plugins/xenserver/xen

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: > https://etherpad.openstack.org/p/newton-magnum-ironic-integration > - Sta

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

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

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

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

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 minut

[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

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 http://eavesdrop.openstack.

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

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 -- if you are interested i

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 that. I did not spe

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 information from within your repo. > Get a

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 that has been bouncin

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] [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 on the default token provider > >> work s

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 prog

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 the object model use for noti

[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] [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 enjoyed very much listening in on the defaul

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

[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: stack@ubuntu-devstack:/et

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 "Plimo

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

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 09:55 AM, Clint Byrum wr

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

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 pa

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

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

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

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 quite > different sy

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] [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] [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 on this - if you're a current or past member of the

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 Mes

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 paus

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

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 thus

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 kolla-k8

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

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 currently dra

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 c

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 abstracts > > over

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

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

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

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 a distro is di

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 diligenc

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

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". > M

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 wa

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 mailto:zhang.lei@gmail.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, May 3, 2016 at 9:12 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Kolla] l

[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, > > Recently, the ubuntu 16.04 is out

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

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

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 to do during Newton c

[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: openstack-dev-requ...@lists.open

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] [Neutron] Neutron client and plan to > transition to OpenStack client > > thanks to ric

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. How is accepting what w

[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] [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 to the Cinder core team.

[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. https://www.openstack.org/summit/austin-2016/summit-sche

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

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 formatting rules (ensur

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

  1   2   >