[openstack-dev] [glance] [cross-project] Austin summit summary: Microversions

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 various stakeholders need to be aware of. * The discussion in this session was informatory on what's existing today in the API_WG

[openstack-dev] [glance] [interop] [defcore] [tempest] [refstack] [docs] Austin summit summary: Import refactor implementation and updates

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 various stakeholders need to be aware of. * The team agreed to implement the refactor in 3 major steps. We will start with a MVP that

[openstack-dev] [tricircle] A number of dummy functions

Team, How many dummy, fake function does the Tricircle have? I understood that we are now in pre-production, and will be in production hopefully soon! But I don't need surprise any more -; e.g., # ./tricircle/cinder_apigw/controllers/volume.py 337 def _convert_header(self, t_release,

[openstack-dev] [kolla][kubernetes] kolla-kubernetes underway

Hey folks, There was a majority vote result on the separate repository vote and as a result voting was closed early. We have voted to proceed with a separate repository for kolla-kubernetes. The kolla-kubernetes repository is in progress of creation and being added to the governance

Re: [openstack-dev] [User-committee] [app-catalog] App Catalog IRC meeting Thursday May 5th

For this who have not used IRC previously, here is a quick guide to get your started: http://docs.openstack.org/upstream-training/06-irc-meetings.html#1 Don't be afraid to ask questions as IRC is good fun in a meeting room as to get to use the meeting room robot! More than just tech, a reality

Re: [openstack-dev] [app-catalog] [glare] [murano] [mistral] Austin summit summary: Community App Catalog

Cool, feel free to communicate with us on adding Mistral assets into the catalog. Renat Akhmerov @Nokia > On 05 May 2016, at 06:43, Nikhil Komawar wrote: > > Thanks Christopher for a really nice summary! > > > On 5/4/16 7:37 PM, Christopher Aedo wrote: >> Hello! At

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

> On 05 May 2016, at 01:49, Mehdi Abaakouk wrote: > > > Le 2016-05-04 10:04, Renat Akhmerov a écrit : >> No problem. Let’s not call it RPC (btw, I completely agree with that). >> But it’s one of the messaging patterns and hence should be under >> oslo.messaging I guess, no?

[openstack-dev] [swift] specs are dead. long live ideas

If you're working on an idea for Swift, you've probably already spent a lot of time thinking deeply about it. Working with other people in the community to further develop your idea is wonderful, and by the time we're all reviewing the code, it's really important that we all think deeply about

[openstack-dev] [horizon] Angular form framework

Hello everybody, I sent a message about this direclty to a couple of people for their quick thoughts. It looks like there is enough interest that I should have just sent it to the whole ML from the start. I’d like to keep folks in the loop, so, I’m copying it all below with all of the

[openstack-dev] [swift] [searchlight] Swift Searchlight Integration Austin Summit Recap

Hello Swift team, I sent out a summary of what I believe was discussed at our joint session to just [searchlight] and wanted to copy it to the [swift] thread so that we are on the same page. Please take a look and reply with any comments, corrections, questions, etc. Thanks! Swift

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On May 4, 2016, at 3:53 PM, Jay Pipes wrote: > My position is that if it's an HTTP API (as opposed to something like a > sqlalchemy-migrate sync command) then it belongs in a client that speaks the > OpenStack HTTP APIs. That is OSC as far as I can tell. I don't see a >

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

Thanks for these notes, Matt. Couple of comments inline. On 5/2/16, 7: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

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

Hi Darek, Thanks your information, but the BGP commands are not list in here https://etherpad.openstack.org/p/osc-neutron-support :( Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

As we discussed at summit, (and consistent with all of the comments) we should move ahead with the project to advance the image builder for Trove and make it easier to build guest images for Trove by leveraging the DIB elements that we have in trove-integration. To that end, the infra [1] and

[openstack-dev] [tricircle]PTL election of Tricircle for Newton release

Hello, As discussed in yesterday weekly meeting, PTL nomination period from May 9 ~ May 13, election from May 16 ~ May 20 if more than one nomination . If you want to be the PTL for Newton release of Tricircle, please send your self nomination letter in the mail-list. You can refer to the

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

On Thursday morning the Nova and Cinder teams got together for a cross-project design summit session. The full etherpad is here [1]. This was all about volume multi-attach. A subset of people from both teams were actually meeting weekly for four weeks leading up to the summit to hash out some

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

+1. He is experienced and helps me a lot. He is qualified to be a core reviewer. Best regards, Yipei __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

On 05/04/2016 08:25 PM, Tom Fifield wrote: > On 04/05/16 01: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 drafting a TC resolution to update >>

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

On 04/05/16 01: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 drafting a TC resolution to update http://governance.openstack.org/resolutions/20150901-programming-languages.html to

[openstack-dev] [Neutron] Development track: completing the Mitaka backlog - report

Hi Neutrinos, During session [1] we went over the following items: a) specs in the backlog b) any item that was targeted for M and rolled over automatically to N-1 c) RFE that were either approved, or expired The objective of the session was to ensure that we took a moment to focus on the stuff

Re: [openstack-dev] [kolla] xenial or trusty

FYI all blockers that we have in puppet CI: https://etherpad.openstack.org/p/puppet-openstack-xenial HTH On Wed, May 4, 2016 at 4:20 PM, Carlos Cesario - Tecnomega wrote: > Hi folks, > > Based in that request, it follows a proposed patch to add support to Ubuntu >

Re: [openstack-dev] [app-catalog] [glare] [murano] [mistral] Austin summit summary: Community App Catalog

Thanks Christopher for a really nice summary! On 5/4/16 7:37 PM, Christopher Aedo wrote: > Hello! At the summit I was excited to have many conversations with > folks who are already using the Community App Catalog regularly, and > many others who plan to increase their level of participation in

[openstack-dev] [app-catalog] [glare] [murano] [mistral] Austin summit summary: Community App Catalog

Hello!  At the summit I was excited to have many conversations with folks who are already using the Community App Catalog regularly, and many others who plan to increase their level of participation in the months to come - I'm really happy to see the continued interest in this effort.  For those

[openstack-dev] [puppet] Switch our CI to deploy on Ubuntu Xenial (new LTS)

Hi, I started to try deploying OpenStack on Ubuntu Xenial using our Puppet modules and I hit a lot of issues, referenced in this etherpad: https://etherpad.openstack.org/p/puppet-openstack-xenial We need to solve them all as soon as possible, because we're going to gate on Xenial starting from

[openstack-dev] [app-catalog] App Catalog IRC meeting Thursday May 5th

Join us Thursday for our weekly meeting, scheduled for May 5th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to get something on the agenda: https://wiki.openstack.org/wiki/Meetings/app-catalog Looking forward to seeing you there tomorrow!

Re: [openstack-dev] [neutron][stable] - exception for stable/kilo DVR back-ports

So I was doing some testing and this looks like it will happen very quickly after an agent restarts. The rule priorities are stored as a set and are allocated from by calling .pop(). In local testing, it looks like that pretty consistently pulls the first priority off of the range.

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

+100 Jay On Wed, May 4, 2016 at 4:53 PM, Jay Pipes wrote: > On 05/04/2016 01:08 PM, Chris Dent wrote: > >> >> The plans for generic resource pools[1] include a suite of new >> commands for creating and updating resource pools. In today's Nova >> API meeting[2] and afterwards

Re: [openstack-dev] [neutron][stable] - exception for stable/kilo DVR back-ports

On 4 May 2016 at 14:26, Assaf Muller wrote: > On Wed, May 4, 2016 at 4:54 PM, Kevin Benton wrote: > > Hello, > > > > I would like to propose a freeze exception for > > https://review.openstack.org/#/c/312253/ and > > https://review.openstack.org/#/c/312254/ .

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

I think part of the problem with the whole Swift situation is that it does something most other OpenStack projects don't do. Its both a control plane and a data plane. For example, Cinder provides a unified api and provides plugins to allow vendors to plug in their particular special sauce in.

[openstack-dev] [release] prioritizing our task list for newton

Team, I've taken a stab at adding milestone-based priorities to our task list in https://etherpad.openstack.org/p/newton-relmgt-plan by prepending N1, N2, or N3 to the TODO items that I think we need to finish by one of those milestones. This is a continuation of the discussion we started Friday

Re: [openstack-dev] [neutron][stable] - exception for stable/kilo DVR back-ports

On Wed, May 4, 2016 at 4:54 PM, Kevin Benton wrote: > Hello, > > I would like to propose a freeze exception for > https://review.openstack.org/#/c/312253/ and > https://review.openstack.org/#/c/312254/ . They address a bug in DVR that > causes floating IPs to eventually break

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

Sweet. Thanks Jim (and everyone else that made this happen). I do want to make sure there is one "source of truth" to the API documentation. We are already generating REST API documentation at http://docs.openstack.org/developer/ironic/webapi/v1.html. The info for this comes from docstrings etc

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

Hey y'all, I did the push this week to move the api-ref into our tree, and it's now publishing. \o/ The docs are here: http://developer.openstack.org/api-ref/baremetal/ The source is here: http://git.openstack.org/cgit/openstack/ironic/tree/api-ref/source I know devananda is doing a push to

[openstack-dev] [neutron][stable] - exception for stable/kilo DVR back-ports

Hello, I would like to propose a freeze exception for https://review.openstack.org/#/c/312253/ and https://review.openstack.org/#/c/312254/ . They address a bug in DVR that causes floating IPs to eventually break after an L3 agent has been restarted. It's a serious bug but it's very subtle

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 05/04/2016 01:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with

Re: [openstack-dev] [ironic] Newton priorities and primary contacts

On Wed, May 04, 2016 at 02:29:34PM -0400, Ruby Loo wrote: > Hi, > > At the Austin summit, we had a session where we discussed and decided on > what the top priorities would be for ironic, in the newton development > cycle. The etherpad [1] captures that discussion, and there is a patch up > to

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Comments inline. On 5/4/16 2:58 PM, Tim Bell wrote: > > On 04/05/16 20:35, "Nikhil Komawar" wrote: > >> >> On 5/4/16 2:09 PM, Tim Bell wrote: >>> On 04/05/16 19:41, "Nikhil Komawar" wrote: >>> Thanks for the summary and taking care of the

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

Excerpts from Fox, Kevin M's message of 2016-05-04 16:49:42 +: > Ok. Sure. More generically then. There are OpenStack compatible API > implementations existing in the world, deployed by a not insignificant number > of production clouds, that are currently outside the big tent that may have

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

The way I see this, these are the 2 main concerns I have been hearing regarding image building in Trove: 1) making the process simple and easy for users 2) addressing the issue of security I dont think there is any argument regarding the benefits of moving the database elements to a seperate

Re: [openstack-dev] [kolla] xenial or trusty

Hi folks, Based in that request, it follows a proposed patch to add support to Ubuntu Xenial - 16.04. For while, instead to locking distro version in branches this can be used, since Mitaka version is supported by Ubuntu Trusty and Xenial versions. http://paste.openstack.org/show/496142/

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

+1 for me too. -- Kevin Carter IRC: cloudnull From: Matthew Thode Sent: Tuesday, May 3, 2016 1:50 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

> -Original Message- > From: Gregory Haynes [mailto:g...@greghaynes.net] > Sent: Wednesday, May 04, 2016 3:52 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] > discussion of image building in Trove > > On Wed, May 4,

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

+1 Walt 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

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 10:33 AM, Peter MacKinnon wrote: > > Well, certainly one downside in the case of Trove (and probably > elsewhere) with DIB is the src tree matrix of datastore-by-distro > elements required to support various guest image combinations, leading > to a proliferation of

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

On 05/04/2016 01:31 PM, Fox, Kevin M wrote: Explicitly, no. I agree. Implicitly... ? Why bother to even propose joining when you know the rules clearly state that its not acceptable? I don't claim to know what has gone on internally in such teams. I'm just saying just because there hasn't

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

On 05/04/2016 11:49 AM, Fox, Kevin M wrote: Ok. Sure. More generically then. There are OpenStack compatible API implementations existing in the world, deployed by a not insignificant number of production clouds, that are currently outside the big tent that may have not considered proposing

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On Wed, May 4, 2016 at 1:54 PM, Sean Dague wrote: > Given these constraints it was as much of an ask as anything else. Can > OSC handle this? Should it handle it from a best practices perspective? > How are commands exposed / hidden based on user permissions? The fact > that

[openstack-dev] [Neutron] meeting topics for 5/5/2016 networking-sfc project IRC meeting

Hi everyone, Here are some topics I have for this week's project meeting discussion(The meeting time is not changed, still UTC 1700 Thursday). Feel free to add more. You can also find the meeting topics in the project wiki page.

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 04/05/16 20:54, "Sean Dague" wrote: >On 05/04/2016 02:16 PM, Dean Troyer wrote: >> On Wed, May 4, 2016 at 12:08 PM, Chris Dent > > wrote: >> >> Since then the spec has been updated to reflect using OSC but the

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 2016-05-04 09:52:20 -0700 (-0700), Gregory Haynes wrote: [...] > One of the biggest issues I see users of DIB hit is ease of use > for 'just make me an image, I don't care about twiddling knobs'. A > wrapper script in trove is one way to help with this [...] For example, in

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 04/05/16 20:35, "Nikhil Komawar" wrote: > > >On 5/4/16 2:09 PM, Tim Bell wrote: >> >> On 04/05/16 19:41, "Nikhil Komawar" wrote: >> >>> Thanks for the summary and taking care of the setup, Vilobh! >>> >>> Pretty meticulously written on what was

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 05/04/2016 02:16 PM, Dean Troyer wrote: > On Wed, May 4, 2016 at 12:08 PM, Chris Dent > wrote: > > Since then the spec has been updated to reflect using OSC but the > question of whether this is in fact the right place for this

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

Le 2016-05-04 10:04, Renat Akhmerov a écrit : No problem. Let’s not call it RPC (btw, I completely agree with that). But it’s one of the messaging patterns and hence should be under oslo.messaging I guess, no? Yes and no, we currently have two APIs (rpc and notification). And personally I

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 09:57 AM, Ethan Gafford wrote: > > Sahara has support for several image generation-related cases: > 1) Packing an image pre-cluster spawn in Nova. > 2) Building clusters from a "clean" OS image post-Nova spawn, by >downloading and installing

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 5/4/16 2:09 PM, Tim Bell wrote: > > On 04/05/16 19:41, "Nikhil Komawar" wrote: > >> Thanks for the summary and taking care of the setup, Vilobh! >> >> Pretty meticulously written on what was agreed at the session. Kudos! >> >> I wanted to add some points that were

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

Explicitly, no. I agree. Implicitly... ? Why bother to even propose joining when you know the rules clearly state that its not acceptable? I don't claim to know what has gone on internally in such teams. I'm just saying just because there hasn't been visible signs here of exclusion doesn't mean

[openstack-dev] [ironic] Newton priorities and primary contacts

Hi, At the Austin summit, we had a session where we discussed and decided on what the top priorities would be for ironic, in the newton development cycle. The etherpad [1] captures that discussion, and there is a patch up to add the newton priorities to our specs [2]. Everyone, and in particular

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

> On May 4, 2016, at 6:10 AM, Na Zhu wrote: > > Hi Richard, > > I read the contents in the link, I think the discussion in Austin summit have > not updated to the webpage. > But from here > https://etherpad.openstack.org/p/newton-neutron-future-neutron-client >

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

Excerpts from Mark Doffman's message of 2016-05-03 17:05:54 -0700: > This thread has been a depressing read. > First, I apologize if any of my actions have caused you any undue stress. > I understand that the content is supposed to be distributed databases > but for me it has become an

Re: [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

Hi all – I think this might’ve gotten buried a bit in the pre-summit and summit madness. I just wanted to kick the thread – I think this is a really good idea. Dogpiling all plugins into a single LP project makes it really difficult to pick out which bugs affect which plugins – and the

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

On Wed, May 4, 2016 at 6:10 AM, Na Zhu wrote: > I found Dean Troyer set the *[Blueprint neutron-client] implement neutron > commands*state to obsolete, does the OSC transition continue move along? Other BPs are being used to track the specific work being performed, that BP

Re: [openstack-dev] [kolla] xenial or trusty

On Wed, May 4, 2016 at 1:52 PM, Jeffrey Zhang wrote: > I'd like to lock the tag version in certain branch. One branch only support > one > distro release. > > For example, the mitaka branch only build on Trusty and the master/newton > branch > only build on Xenial. > >

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 5/4/2016 12:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On Wed, May 4, 2016 at 12:08 PM, Chris Dent wrote: > Since then the spec has been updated to reflect using OSC but the > question of whether this is in fact the right place for this style > of commands remains open. Not just for this situation, but > generally. > This

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 04/05/16 19:41, "Nikhil Komawar" wrote: >Thanks for the summary and taking care of the setup, Vilobh! > >Pretty meticulously written on what was agreed at the session. Kudos! > >I wanted to add some points that were asked during the Glance >contributors' meetup: > >*

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

On Tue, 3 May 2016 22:37:30 + "Fox, Kevin M" wrote: > RadosGW has been excluded from joining the OpenStack community in part > due to its use of c++. Sounds like sheer lunacy. Nothing like that ever happened, AFAIK. -- Pete

Re: [openstack-dev] [kolla] xenial or trusty

I'd like to lock the tag version in certain branch. One branch only support one distro release. For example, the mitaka branch only build on Trusty and the master/newton branch only build on Xenial. So, the branch and OS matrix should like ( fix me and the ?) Ubuntu CentOS

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

On 04/05/16 11:38 +0200, Thierry Carrez wrote: Hayes, Graham wrote: [...] Designate is looking to move a single component of ours to Go - and we were wondering what was the best way to do it. The current policy does allow for the TC to bless different languages on a case by case basis - do we

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Thanks for the summary and taking care of the setup, Vilobh! Pretty meticulously written on what was agreed at the session. Kudos! I wanted to add some points that were asked during the Glance contributors' meetup: * The quota limits will be set on the tables in the service that maintains the

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 04/05/16 09:46 -0700, Clark Boylan wrote: On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: On 04/05/16 15:05 +, Amrith Kumar wrote: >I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. > >TL;DR > >One of the most frequent

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

On Tue, 3 May 2016 22:11:06 + "Fox, Kevin M" wrote: > If we let go in, and there are no pluggable middleware, where does > RadosGW and other Swift api compatible implementations then stand? They remain where they are now. > Should we bless c++ too? As I understand it,

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 5/4/16 12:52 PM, Gregory Haynes wrote: On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: On 04/05/16 15:05 +, Amrith Kumar wrote: I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions

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

Thanks, Jay! We’re looking through everything and will be attending these meetings moving forward. -Travis On 5/3/16, 6:17 AM, "Jay Pipes" wrote: >cc'ing Travis and Steve directly, since they will likely be very >interested in this effort from the Project Searchlight

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

On 04/05/16 19:00, "Edward Leafe" wrote: >On May 3, 2016, at 7:05 PM, Mark Doffman wrote: > >> 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

[openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Hi All, For people who missed the design summit session on Delimiter - Cross project Quota enforcement library here is a gist of what we discussed. Etherpad [1] captures the details. 1. Delimiter will not be responsible for rate-limiting. 2. Delimiter will not maintain data for the projects. 3.

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

On 5/4/2016 12:00 PM, Edward Leafe wrote: On May 3, 2016, at 7:05 PM, Mark Doffman wrote: 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. Thanks

Re: [openstack-dev] [nova] solving API case sensitivity issues

On 02/24/2016 07:48 AM, Sean Dague wrote: > We have a specific bug around aggregrate metadata setting in Nova which > exposes a larger issue with our mysql schema. > https://bugs.launchpad.net/nova/+bug/1538011 > > On mysql the following will explode with a 500: > >> nova aggregate-create agg1

[openstack-dev] [kolla] xenial or trusty

Which will be the default when kolla begin to support xenial? Xenial or Trusty? One proposal is to support both, at least in this beginning and just do some checks to get which version that the user is using. Regards, __

[openstack-dev] [nova][osc] Use of openstack client for admin commands

The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with resource pools is eventually going to be

Re: [openstack-dev] [magnum] Add support for using Keystone in k8s bay

+1. Thanks for starting the discussion. We may need a spec for it. The support in k8s currently is marked experimental (thankfully) and is insufficient. It currently only supports username/password authentication via keystone v2. There's an issue in the works to fix it in k8s:

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

On May 3, 2016, at 7:05 PM, Mark Doffman wrote: > 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. Thanks for bringing this up, and I feel a lot

[openstack-dev] [nova] Austin summit API session recap

On Thursday morning Sean Dague led a double session for work in the Nova API. The full etherpad is here [1]. There were four main focus areas for discussion: 1. Policy defaults in code 2. Policy discoverability 3. api-ref documentation 4. Deprecating/deleting things from the API Policy

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016 at 11:55 AM, Flavio Percoco wrote: > On 04/05/16 15:05 +, Amrith Kumar wrote: > >> I'm emailing the ML on the subject of a review ongoing in the Trove >> project regarding image building[1]. >> >> TL;DR >> >> One of the most frequent questions that new

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 05/04/2016 11:46 AM, Clark Boylan wrote: On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: On 04/05/16 15:05 +, Amrith Kumar wrote: I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions

[openstack-dev] [stable] Requesting exception for stable/kilo

Hi Stable Maintainers, We have a critical bug impacting customers production network. This is a minor fix. I would like to request an exception so that the customers do not have to baby sit this patch. https://review.openstack.org/#/c/309653/ Please allow this to be merged. Thanks -Sukhdev

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: > On 04/05/16 15:05 +, Amrith Kumar wrote: > >I'm emailing the ML on the subject of a review ongoing in the Trove project > >regarding image building[1]. > > > >TL;DR > > > >One of the most frequent questions that new users of Trove ask

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

Ok. Sure. More generically then. There are OpenStack compatible API implementations existing in the world, deployed by a not insignificant number of production clouds, that are currently outside the big tent that may have not considered proposing joining the community because of the past

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: > On 04/05/16 15:05 +, Amrith Kumar wrote: > >I'm emailing the ML on the subject of a review ongoing in the Trove project > >regarding image building[1]. > > > >TL;DR > > > >One of the most frequent questions that new users of Trove ask

[openstack-dev] [designate] Reminder - IRC meeting postponed this week

As discussed in the design summit - we are skipping the IRC meeting today. Talk to you all in a week / #openstack-dns - Graham __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 04/05/16 15:05 +, Amrith Kumar wrote: I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions that new users of Trove ask is how and where to get guest images with which to experiment with Trove,

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

+1. Michal will be a great addition to the core team. Thanks, Xing > On May 3, 2016, at 2:19 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

Re: [openstack-dev] [infra][neutron][nova] publish and update Gerrit dashboard link automatically

Hi all, in case you are wondering what's the progress of this, I am happy to say that we finally have a link in reviewday [1] that points to the Neutron dashboard that it's constantly updated. It took some effort to get there, thanks to the infra team for the help and especially to AJaeger. Now

[openstack-dev] [magnum] Add support for using Keystone in k8s bay

Hi team, Based on requests, I propose to add support for Keystone authentication for k8s bay. A blueprint was created for that: https://blueprints.launchpad.net/magnum/+spec/keystone-for-k8s-bay A goal is to enable other OpenStack services to access the APIs of k8s bays. So far, I received a

[openstack-dev] [release] summit fishbowl summary

Last week we had a retrospective for the Mitaka release and a planning session for the Newton release. The notes are in the etherpad [1], and this email is a summary based on those notes. As usual, if I've left out something important or mis-remembered something, please post a follow-up. Doug

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

I agree with your approach Jeffrey, although this is not ideal, this is an approach already used in kolla. 2016-05-04 12:01 GMT-03:00 Jeffrey Zhang : > Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the > globals.yml file. > Because there is no chance

Re: [openstack-dev] [dib][trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Adding [dib] to the subject line. -amrith > -Original Message- > From: Amrith Kumar [mailto:amr...@tesora.com] > Sent: Wednesday, May 04, 2016 11:05 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev]

[openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions that new users of Trove ask is how and where to get guest images with which to experiment with Trove, and how to build these images for themselves.

[openstack-dev] [kolla] better solution for the non-ini format configure file

Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the globals.yml file. Because there is no chance to change the horizon/apache configure file now. The root cause is that: Kolla do not support non-ini format configure file. for the ini-format file, we use a merge_config module[1]

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

> From: Doug Hellmann > To: openstack-dev > Date: 05/03/2016 07:04 PM > Subject: 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: >

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

Hi Bob, Thanks for reaching out! We're in the process of finalizing the API and the team is working hard on getting the code ready; atm with near to complete functionality WIP patches. Please be mindful of the fact that there is currently an experimental API in glance and code that will change

  1   2   >