Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Excerpts from Geoff O'Callaghan's message of 2016-05-24 15:31:28 +1000: > > > On 24 May 2016, at 3:13 PM, Clint Byrum wrote: > > > > > [snip] > > > those other needs. Grab a python developer, land some code, and your > > feature is there. &g

Re: [openstack-dev] [ironic][neutron] bonding?

Excerpts from Jim Rollenhagen's message of 2016-05-24 07:51:21 -0400: > Hi, > > There's rumors floating around about Neutron having a bonding model in > the near future. Are there any solid plans for that? > > For context, as part of the multitenant networking work, ironic has a > portgroup conce

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

(Top posting as a general reply to the thread) Bugs are precious data. As much as it feels like the bug list is full of cruft that won't ever get touched, one thing that we might be missing in doing this is that the user who encounters the bug and takes the time to actually find the bug tracker an

Re: [openstack-dev] [TripleO][diskimage-builder] Proposing Stephane Miller to dib-core

Excerpts from Gregory Haynes's message of 2016-06-01 12:50:19 -0500: > Hello everyone, > > I'd like to propose adding Stephane Miller (cinerama) to the > diskimage-builder core team. She has been a huge help with our reviews > for some time now and I think she would make a great addition to our >

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

Excerpts from Brant Knudson's message of 2016-06-03 15:16:20 -0500: > On Fri, Jun 3, 2016 at 2:35 PM, Lance Bragstad wrote: > > > Hey all, > > > > I have been curious about impact of providing performance feedback as part > > of the review process. From what I understand, keystone used to have a

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Excerpts from Kris G. Lindgren's message of 2016-06-06 20:44:26 +: > Hi ironic folks, > As I'm trying to explore how GoDaddy can use ironic I've created the > following in an attempt to document some of my concerns, and I'm wondering if > you folks could help myself identity ongoing work to s

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Excerpts from Joshua Harlow's message of 2016-06-07 08:46:28 -0700: > Clint Byrum wrote: > > Excerpts from Kris G. Lindgren's message of 2016-06-06 20:44:26 +: > >> Hi ironic folks, > >> As I'm trying to explore how GoDaddy can use ironic I'

Re: [openstack-dev] Reasoning behind my vote on the Go topic

Excerpts from Michael Barton's message of 2016-06-09 14:01:11 -0500: > On Thu, Jun 9, 2016 at 9:58 AM, Ben Meyer wrote: > > > > > uvloop (first commit 2015-11-01) is newer than Swift's hummingbird > > (2015-04-20, based on > > > > https://github.com/openstack/swift/commit/a0e300df180f7f4ca64fc1ea

Re: [openstack-dev] Reasoning behind my vote on the Go topic

Excerpts from Michael Barton's message of 2016-06-09 15:59:24 -0500: > On Thu, Jun 9, 2016 at 2:49 PM, Clint Byrum wrote: > > > > Agreed it isn't done in uvloop. But it is done in libuv and the uvloop > > devs agree it should be done. So this is the kind of th

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > On further reflection, it seems to me that we can never simply enable either > of these approaches in a single release. Even a v4.0 version of the API > doesn’t help - since presumably a sever supporting v4 would want to be able

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

Excerpts from Dolph Mathews's message of 2016-06-13 20:11:57 +: > On Fri, Jun 10, 2016 at 12:20 PM Clint Byrum wrote: > > > Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > > > On further reflection, it seems to me that we can never si

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

Excerpts from Steven Hardy's message of 2016-06-09 15:03:51 +0100: > Also, while reviewing the core group[2] I noticed the following members who > are no longer active and should probably be removed: > > - Radomir Dopieralski > - Martyn Taylor > - Clint Byrum > > I

[openstack-dev] [all] Proposal: Architecture Working Group

ar·chi·tec·ture ˈärkəˌtek(t)SHər/ noun noun: architecture 1. the art or practice of designing and constructing buildings. synonyms:building design, building style, planning, building, construction; formalarchitectonics "modern architecture" the style in which a buil

Re: [openstack-dev] Version header for OpenStack microversion support

Excerpts from Henry Nash's message of 2016-06-18 13:14:17 +0100: > > On 18 Jun 2016, at 11:32, Jamie Lennox wrote: > > > > Quick question: why do we need the service type or name in there? You > > really should know what API you're talking to already and it's just > > something that makes it mo

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

Excerpts from Joshua Harlow's message of 2016-06-17 15:04:38 -0700: > Hi folks, > > I was noticing that its possible to do something like: > > $ nova meta josh-testr3 set "e=f" > > Then inside the VM I can do the following to eventually see that this > changes shows up in the instance metadata

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56 -0600: > So, it sounds like you’ve just described the job of the TC. And they have so > far refused to define OpenStack, leading to a series of derivative decisions > that seem … inconsistent over time. > > How is this body going to be

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Michael Krotscheck's message of 2016-06-20 15:26:20 +: > I like the idea in principle, but am bullish on the implementation. > As you should be, and we all must be. It's not going to happen if we just dream it. That's kind of the point. Let's write down a design _for the group t

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jesse Cook's message of 2016-06-20 16:58:48 +: > +1 > > The points about the PWG and TC are worth some consideration. > > From my perspective, I think it would make sense for the PWG to define the > expected behaviors of the system, which would be an input to the > architecture

Re: [openstack-dev] [all] Proposal: Architecture Working Group

d prioritize efforts as part of the first few meetings. [1] http://specs.openstack.org/openstack/openstack-specs/specs/chronicles-of-a-dlm.html > -Josh > > Clint Byrum wrote: > > ar·chi·tec·ture > > ˈärkəˌtek(t)SHər/ > > noun > > noun: architecture > > &g

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: > Hi dib-gurus, > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd > error. Hoping someone has some ideas... > > The command I am runni

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Ahh derp, that's not an ARM CPU. I read "A8" and "APU" and my brain immediately lept to that. Ignore me. Excerpts from Clint Byrum's message of 2016-06-20 15:12:23 -0700: > Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: > > Hi dib-gurus, > > > > I'm trying to build a simple ubunt

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Gregory Haynes's message of 2016-06-20 17:24:28 -0500: > On Mon, Jun 20, 2016, at 03:52 PM, Jay Pipes wrote: > > Hi dib-gurus, > > > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd >

Re: [openstack-dev] Version header for OpenStack microversion support

Excerpts from Edward Leafe's message of 2016-06-20 20:41:56 -0500: > On Jun 18, 2016, at 9:03 AM, Clint Byrum wrote: > > > Whatever API version is used behind the compute API is none of the user's > > business. > > Actually, yeah, it is. > > If I wri

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 09:10:00 -0400: > The amount of wsgi glue above Routes / Paste is pretty minimal (after > you get rid of all the extensions facilities). > > Templating and Session handling are things we don't need. We're not a > webapp, we're a REST service. Saying

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: > On 06/21/2016 07:39 AM, Jay Pipes wrote: > > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: > >> Le 21/06/2016 10:04, Chris Dent a écrit : > >>> On Mon, 20 Jun 2016, Jay Pipes wrote: > >>> > Flask seems to be the most widely used

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Chris Dent's message of 2016-06-21 09:25:44 +0100: > On Mon, 20 Jun 2016, Doug Wiegley wrote: > > > So, it sounds like you’ve just described the job of the TC. And they > > have so far refused to define OpenStack, leading to a series of > > derivative decisions that seem … inconsiste

Re: [openstack-dev] [all] Proposal: Architecture Working Group

t Mailing List (not for usage questions) > > Subject:  Re: [openstack-dev] [all] Proposal: Architecture Working Group > > > On Mon, Jun 20, 2016 at 10:59 AM Clint Byrum wrote: > > > > > > > > As you should be, and we all must be. It's not going to happe

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jay Pipes's message of 2016-06-21 13:29:32 -0400: > On 06/21/2016 12:53 PM, Doug Wiegley wrote: > > Don’t get me wrong, I welcome this initiative. I find it mildly > > disconcerting that the folks that I thought we were electing to fill > > this role will instead be filled by others,

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jay Pipes's message of 2016-06-21 12:47:46 -0400: > On 06/21/2016 04:25 AM, Chris Dent wrote: > > However, I worry deeply that it could become astronauts with finger > > paints. > > Yes. This. > > I will happily take software design suggestions from people that > demonstrate with c

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Jay Pipes's message of 2016-06-21 14:20:07 -0400: > On 06/21/2016 02:01 PM, Andre Florath wrote: > > Hello Jay, > > > > Yes - the partition alignment is a problem: > > grub2 needs at least 63 blocks between the MBR and the first > > partition. Here for you the partition directly star

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

Excerpts from Joshua Harlow's message of 2016-06-21 15:12:09 -0700: > Agreed, it appears supported right-now (whether intentional or not), > > So the question at that point is what can we do to make it better... > > I think we all agree that the config-drive probably shouldn't have the > equival

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Amrith Kumar's message of 2016-06-22 13:15:03 +: > Clint, > > In your original email, you proposed "So, with that, I'd like to propose the > creation of an Architecture Working Group. This group's charge would not be > design by committee, but a place for architects to share th

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Excerpts from Doug Hellmann's message of 2016-06-23 08:37:04 -0400: > Excerpts from Doug Hellmann's message of 2016-06-13 15:11:17 -0400: > > I'm trying to pull together some information about contributions > > that OpenStack community members have made *upstream* of OpenStack, > > via code, docs,

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: > > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Thursday, June 23, 2016 5:16 PM > > To: openstack-dev > > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Zhipeng Huang's message of 2016-06-24 18:15:30 +0200: > Hi Clint and Amrith, > > Are you guys already working on the proposal ? Is there any public access > to see the first draft ? > I've started writing something up, and I hope to submit it for review next week.

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Thanks everyone for participating and remaining positive and focused on improving OpenStack. I've posted a review, and I'd like to encourage everyone to move any future discussion of the Architecture Working group to that review. https://review.openstack.org/335141 Excerpts from Clint Byrum's mes

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > On 11:31 Jun 20, Clint Byrum wrote: > > Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > > > Thanks for getting this started Clint, > > > > > > I'm happy and

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Mike Perez's message of 2016-06-30 14:10:30 -0700: > On 09:02 Jun 30, Clint Byrum wrote: > > Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > > > On 11:31 Jun 20, Clint Byrum wrote: > > > > Excerpts from Joshua Harlo

Re: [openstack-dev] New Python35 Jobs coming

Excerpts from Henry Gessau's message of 2016-07-03 15:26:23 -0400: > Clark Boylan wrote: > > The infra team is working on taking advantage of the new Ubuntu Xenial > > release including running unittests on python35. The current plan is to > > get https://review.openstack.org/#/c/336272/ merged ne

Re: [openstack-dev] [grenade] upgrades vs rootwrap

Excerpts from Matthew Treinish's message of 2016-07-06 11:55:53 -0400: > On Wed, Jul 06, 2016 at 10:34:49AM -0500, Matt Riedemann wrote: > > On 6/27/2016 6:24 AM, Sean Dague wrote: > > > On 06/26/2016 10:02 PM, Angus Lees wrote: > > > > On Fri, 24 Jun 2016 at 20:48 Sean Dague > > >

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

Excerpts from Nikhil Komawar's message of 2016-04-06 10:46:28 -0700: > Need a inline clarification. > > On 4/6/16 10:58 AM, Flavio Percoco wrote: > > On 06/04/16 08:26 -0400, Sean Dague wrote: > >> On 04/06/2016 04:13 AM, Markus Zoeller wrote: > >>> +1 for deprecation and removal > >>> > >>> To be

Re: [openstack-dev] [TripleO] FreeIPA integration

Excerpts from Adam Young's message of 2016-04-05 19:02:58 -0700: > On 04/05/2016 11:42 AM, Fox, Kevin M wrote: > > Yeah, and they just deprecated vendor data plugins too, which > > eliminates my other workaround. :/ > > > > We need to really discuss this problem at the summit and get a viable > >

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > There is also disincentive in +1ing a change that you don't understand > and is wrong and then a core comes along and -1s it (you get dinged for > the disagreement). And there is disincentive in -1ing a change for the > wrong

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

Excerpts from Morgan Fainberg's message of 2016-04-10 16:47:28 -0700: > On Sun, Apr 10, 2016 at 4:37 PM, Clint Byrum wrote: > > > Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > > > There is also disincentive in +1ing a change that you don&

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Excerpts from Douglas Mendizábal's message of 2016-04-13 10:01:21 -0700: > Hash: SHA512 > > Hi Reza, > > The Barbican team has already abstracted python-barbicanclient into a > general purpose key-storage library called Castellan [1] > > There are a few OpenStack projects that have planned to in

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Excerpts from Clayton O'Neill's message of 2016-04-13 07:37:16 -0700: > On Wed, Apr 13, 2016 at 10:26 AM, rezroo wrote: > > Hi Kevin, > > > > I understand that this is how it is now. My question is how bad would it be > > to wrap the Barbican client library calls in another class and claim, for >

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Michał Jastrzębski's message of 2016-04-18 10:29:20 -0700: > What I meant is if you have liberty Nova and liberty Cinder, and you > want to upgrade Nova to Mitaka, you also upgrade Oslo to Mitaka and > Cinder which was liberty either needs to be upgraded or is broken, > therefore duri

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Matthew Thode's message of 2016-04-18 11:22:38 -0700: > On 04/18/2016 12:33 PM, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: > >> On 04/18/2016 08:24 AM, Hayes, Graham wrote: > >>> On 18/04/2016 13:51, Sean Dague wrote: > On 04/18/2

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Thomas Goirand's message of 2016-04-19 05:59:19 -0700: > On 04/19/2016 01:01 PM, Chris Dent wrote: > > We also, however, need to consider what the future might look like and > > at least for some people and situations > > I agree. > > > the future does not involve > > debs or rpms o

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Thierry Carrez's message of 2016-04-21 09:22:53 -0700: > Michael Krotscheck wrote: > > So, HPE is seeking sponsors to continue the core party. The reasons are > > varied - internal sponsors have moved to other projects, the Big Tent > > has drastically increased the # of cores, and th

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Chivers, Doug's message of 2016-04-22 10:17:45 -0700: > The Vancouver core party was a fantastic opportunity to meet some very smart > people and learn a lot about the projects they worked on. It was probably one > of the most useful parts of the summit, certainly more so than the g

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

Excerpts from Andrew Laski's message of 2016-04-22 14:32:59 -0700: > > On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote: > > OK, so I know that Friday afternoons are usually the worst times to > > write a blog post and start an email discussion, and that the Friday > > immediately before a Summit

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

Excerpts from Jay Pipes's message of 2016-04-28 13:09:29 -0500: > On 04/28/2016 08:44 AM, Edward Leafe wrote: > > On Apr 24, 2016, at 3:28 PM, Robert Collins > > wrote: > >> For instance, the things I think are essential for a distributed > >> database based datastore: > >> - good single-machine

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

Excerpts from Mike Bayer's message of 2016-04-28 22:16:54 -0500: > > On 04/28/2016 08:25 PM, Edward Leafe wrote: > > > Your own tests showed that a single RDBMS instance doesn’t even break a > > sweat > > under your test loads. I don’t see why we need to shard it in the first > > place, especial

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

Excerpts from Matt Riedemann's message of 2016-04-29 05:38:17 -0700: > > So, we're all here in person this week (with 1 day left). The Nova team > has a meetup session all day (Salon A in the Hilton). Clint/Ed, can you > guys show up to that and bring these issues up in person so we can > actua

Re: [openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

Excerpts from Roman Podoliaka's message of 2016-04-29 12:04:49 -0700: > Hi Bogdan, > > Thank you for sharing this! I'll need to familiarize myself with this > Jepsen thing, but overall it looks interesting. > > As it turns out, we already run Galera in multi-writer mode in Fuel > unintentionally

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

Excerpts from Mike Bayer's message of 2016-05-02 08:51:58 -0700: > > Well IMO that's actually often a problem. My goal across Openstack > projects in general is to allow them to make use of SQL more effectively > than they do right now; for example, in Neutron I am helping them to > move a blo

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

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 bouncing around in my head, but now I think it's the case and we sho

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

Excerpts from Jay Pipes's message of 2016-05-02 10:43:21 -0700: > On 05/02/2016 11:51 AM, Mike Bayer wrote: > > On 05/02/2016 07:38 AM, Matthieu Simonin wrote: > >> As far as we understand the idea of an ORM is to hide the relational > >> database with an Object oriented API. > > > > I actually dis

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

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 o

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

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

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

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

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

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

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 inquisit

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

Excerpts from Hayes, Graham's message of 2016-05-05 07:26:26 -0700: > On 04/05/2016 00:32, Hayes, Graham wrote: > > On 03/05/2016 17:03, John Dickinson wrote: > >> TC, > >> > >> In reference to > >> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html > >> and Thierry's reply,

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

Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > On Mon, 9 May 2016 09:06:02 -0400 > Rayson Ho wrote: > > > Since the Go toolchain is pretty self-contained, most people just follow > > the official instructions to get it installed... by a one-step: > > > > # tar -C /usr/local

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

Excerpts from Hayes, Graham's message of 2016-05-09 11:58:38 -0700: > On 09/05/2016 19:39, Ben Swartzlander wrote: > > On 05/09/2016 02:15 PM, Clint Byrum wrote: > >> Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > >>> On Mon, 9 May 20

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

Excerpts from Edward Leafe's message of 2016-05-09 12:17:40 -0700: > On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: > > > This is not a "Go seems cool - lets go try that" decision from us - we > > know we have a performance problem with one of our components, and we > > have come to the conclus

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

Excerpts from Rayson Ho's message of 2016-05-10 07:19:23 -0700: > On Tue, May 10, 2016 at 2:42 AM, Tim Bell wrote: > > I hope that the packaging technologies are considered as part of the TC > evaluation of a new language. While many alternative approaches are > available, a language which could n

Re: [openstack-dev] Reg: Blueprint -- add-compute-node-on-the-go

Excerpts from Atul Ag's message of 2015-12-10 06:50:05 -0800: > Hi, > > I have added the blue print > https://blueprints.launchpad.net/nova/+spec/add-compute-node-on-the-go. > Can you please let me know the feasibility, and accept the blueprint. > Hi Atul, welcome, and thanks for your interes

Re: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

Excerpts from ELISHA, Moshe (Moshe)'s message of 2015-12-07 08:29:44 -0800: > Hi all, > > The current bugfix I am working on[1] have unveiled / created a bug. > Test "WorkflowResumeTest.test_resume_different_task_states" sometimes fails > because "task4" is executed twice instead of once (See uni

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Excerpts from Fox, Kevin M's message of 2015-12-15 09:07:02 -0800: > My $0.02: > > heat as it is today, requires all users to be devops, and to carefully craft > the templates launched specific to the cloud and the particular app they are > trying to write. Making sharing code between heat users

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Hi! Can I offer a counter point? Quotas are for _real_ resources. Memory, CPU, disk, bandwidth. These are all _closely_ tied to things that cost real money and cannot be conjured from thin air. As such, the user being able to allocate 1 billion or 2 containers is not limited by Magnum, but by rea

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Excerpts from Fox, Kevin M's message of 2015-12-15 17:21:13 -0800: > the one thing as an Op I'd like to see avoided is having the template > language be Turing complete. When I'm provisioning heat-engines its much > easier if you know how many you need when the user can't force them to spin > i

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

Excerpts from James Penick's message of 2015-12-15 17:19:19 -0800: > > getting rid of the raciness of ClusteredComputeManager in my > >current deployment. And I'm willing to help other operators do the same. > > You do alleviate race, but at the cost of complexity and > unpredictability. Breakin

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

Excerpts from Jim Rollenhagen's message of 2015-12-16 08:03:22 -0800: > Nobody is talking about running a compute per flavor or capability. All > compute hosts will be able to handle all ironic nodes. We *do* still > need to figure out how to handle availability zones or host aggregates, > but I ex

Re: [openstack-dev] [ironic][neutron][keystone] how to reauth the token

Excerpts from Pavlo Shchelokovskyy's message of 2015-12-16 07:59:42 -0800: > Hi all, > > I'd like to start discussion on how Ironic is using Neutron when Keystone > is involved. > > Recently the patch [0] was merged in Ironic to fix a bug when the token > with which to create the neutronclient is

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Fox, Kevin M's message of 2015-12-16 12:19:59 -0800: > keypairs are real though. they consume database resource at the moment. You > don't want a user blowing out your db. Quota's should be for things that ops > will get sad over, if the users consume too many of them. > Limit ev

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Adrian Otto's message of 2015-12-16 12:35:10 -0800: > Clint, > > > On Dec 16, 2015, at 11:56 AM, Tim Bell wrote: > > > >> -Original Message- > >> From: Clint Byrum [mailto:cl...@fewbar.com] > >> Sent: 15 December 2

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Fox, Kevin M's message of 2015-12-16 16:05:29 -0800: > Yeah, as an op, I've run into a few things that need quota's that just have > basically hardcoded values. heat stacks for example. its a single global in > /etc/heat/heat.conf:max_stacks_per_tenant=100. Instead of being able to

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Adrian Otto's message of 2015-12-16 16:56:39 -0800: > Clint, > > I think you are categorically dismissing a very real ops challenge of how to > set correct system limits, and how to adjust them in a running system. I have > been stung by this challenge repeatedly over the years. As

Re: [openstack-dev] [openstack][magnum][heat] Quota for Magnum Resources

M, Lee Calcote > >> wrote: > >> > >> Food for thought - there is a cost to FIPs (in the case of public IP > >> addresses), security groups (to a lesser extent, but in terms of the > >> computation of many hundreds of them), etc. Administrators may wish to

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Excerpts from Dougal Matthews's message of 2015-12-22 07:36:02 -0800: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly today. > After working with the code that came out of the deployment library spec[2] > I > had some concerns with how we are storing the templates.

Re: [openstack-dev] Nova scheduler startup when database is not available

Excerpts from Jay Pipes's message of 2015-12-23 10:32:27 -0800: > On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: > > I've been looking into the startup constraints involved when launching > > Nova services with systemd using Type=notify (which causes systemd to > > wait for an explicit notific

Re: [openstack-dev] Nova scheduler startup when database is not available

Excerpts from Jay Pipes's message of 2015-12-28 09:45:39 -0800: > On 12/24/2015 02:30 PM, Clint Byrum wrote: > > This is entirely philosophical, but we should think about when it is > > appropriate to adopt which mode of operation. > > > > There are basically two

Re: [openstack-dev] How to add feature to diskimage-builder

Excerpts from George Shuklin's message of 2015-12-29 09:16:52 -0800: > Hello. > > I'm trying add a small feature to one of the elements in > diskimage-builder (https://github.com/openstack/diskimage-builder/pull/10/) > > I have experience with gerrit and openstack bugfix workflow, but I have >

Re: [openstack-dev] [heat] Client checking of server version

Excerpts from Jay Dobies's message of 2016-01-04 12:53:07 -0800: > I ran into an issue in a review about moving environment resolution from > client to server [1]. It revolves around clients being able to access > older versions of servers (that's a pretty simplistic description; see > [2] for t

Re: [openstack-dev] Service password storage

Excerpts from Levin's message of 2016-01-11 02:37:09 -0800: > Dear openstack developers, > I installed openstack via devstack recently, and I found out that the > admin passwords for services like cinder and nova are stored in plain > text in their /etc/*/*.conf files. These files are rw--r--r-- by

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

Excerpts from Thomas Goirand's message of 2016-01-16 22:36:23 -0800: > On 01/16/2016 10:16 PM, Jeremy Stanley wrote: > > On 2016-01-16 12:14:20 +0800 (+0800), Thomas Goirand wrote: > > [...] > >> I've just asked this very point with the same example to the FTP > >> masters. Let's see what they say.

Re: [openstack-dev] [glance][ironic][cinder][nova] 'tar' as an image disk_format

Excerpts from Brian Rosmaita's message of 2016-01-23 06:54:26 -0800: > Please provide feedback about a proposal to add 'tar' as a new Glance > disk_format.[0] > > The Ironic team is adding support for "OS tarball images" in Mitaka. This is > a compressed tar archive of a / (root filesystem). Th

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > So I haven't weighed in on this yet, in part because I was on > > vacation > > when it was first proposed and missed a lot of the initial > > discussion, > > and also because I

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Excerpts from Jiri Tomasek's message of 2016-01-25 06:09:33 -0800: > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > >> On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > >>> So I haven

Re: [openstack-dev] [docs][all] Software design in openstack

Excerpts from Nick Yeates's message of 2016-02-03 21:18:08 -0800: > Josh, thanks for pointing this out and in being hospitable to an outsider. > > Oslo is definitely some of what I was looking for. As you stated, the fact > that there is an extensive review system with high participation, that th

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

Excerpts from Thierry Carrez's message of 2016-02-10 08:35:19 -0800: > Chris Dent wrote: > > [...] > > Observing this thread and "the trouble with names"[1] one I get > > concerned that we're trending in the direction of expecting > > projects/servers/APIs to be done and perfect before they will ev

Re: [openstack-dev] [gate] RFC dropping largeops tests

Excerpts from Sean Dague's message of 2016-02-10 04:33:44 -0800: > The largeops tests at this point are mostly finding out that some of our > new cloud providers are slow - http://tinyurl.com/j5u4nf5 > > This is fundamentally a performance test, with timings having been tuned > to pass 98% of the

<    4   5   6   7   8   9   10   11   12   13   >