Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Julien Danjou's message of 2016-07-19 09:30:36 +0200: > On Mon, Jul 18 2016, Joshua Harlow wrote: > > > Thus why I think the starting of the architecture working group is a good > > thing; because I have a believe that people are forgetting among all of this > > that such a group hol

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Fox, Kevin M's message of 2016-07-19 21:59:29 +: > Yeah. I'm not saying any project has done it out of malice. Everyone's just > doing whats best for their project. But it does not seem like there is an > overarching entity watching over the whole or (pushing, encouraging, > en

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from James Bottomley's message of 2016-07-20 08:31:34 -0700: > So this is where the Open Source method takes over. Change is produced > by those people who most care about it because they're invested. To > take your Cinder example, you're unlikely to find them within Cinder > because any

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Fox, Kevin M's message of 2016-07-20 20:12:48 +: > And maybe this raises an interesting defininition mismatch in the > conversation. > > There is archetectural stuff like, do we support 7 different web frameworks, > or do we standardize on flask... python vs go. > Yeah meh, t

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Ed Leafe's message of 2016-07-27 10:59:06 -0500: > On Jul 27, 2016, at 10:51 AM, Joshua Harlow wrote: > > >> Whether to have competing projects in the big tent was debated by the TC > >> at the time and my recollection is that we decided that was a good thing > >> -- if someone want

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Fox, Kevin M's message of 2016-07-27 21:51:15 +: > Its a standard way of launching a given openstack service container with > specified config regardless if its backed with a redhat or ubuntu or source > based package set that the Operator can rely on having a standardized > in

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Fox, Kevin M's message of 2016-07-27 22:56:56 +: > I think that would be true, if the container api was opinionated. for > example, trying to map only a subset of the openstack config options to > docker environment variables. This would make the containers specific to what > y

Re: [openstack-dev] [all][tc] establishing project-wide goals

Excerpts from Jay Pipes's message of 2016-08-01 10:23:57 -0400: > On 08/01/2016 08:33 AM, Sean Dague wrote: > > On 07/29/2016 04:55 PM, Doug Hellmann wrote: > >> One of the outcomes of the discussion at the leadership training > >> session earlier this year was the idea that the TC should set some

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Excerpts from Tim Bell's message of 2016-08-04 15:55:48 +: > > On 04 Aug 2016, at 17:27, Mikhail Fedosin > mailto:mfedo...@mirantis.com>> wrote: > > > > Hi all, > > > > after 6 months of Glare v1 API development we have decided to continue > > our work in a separate project in the "openstack

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Excerpts from Fox, Kevin M's message of 2016-08-04 19:20:43 +: > I disagree. I see glare as a superset of the needs of the image api and one > feature I need thats image related was specifically shot down as "the > artefact api will solve that". > > You have all the same needs to version/cat

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Excerpts from Jay Pipes's message of 2016-08-04 18:14:46 -0400: > On 08/04/2016 05:30 PM, Clint Byrum wrote: > > Excerpts from Fox, Kevin M's message of 2016-08-04 19:20:43 +: > >> I disagree. I see glare as a superset of the needs of the image api and > &g

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200: > On 05/08/16 21:48, Ricardo Rocha wrote: > > Hi. > > > > Quick update is 1000 nodes and 7 million reqs/sec :) - and the number > > of requests should be higher but we had some internal issues. We have > > a submission for barcelon

Re: [openstack-dev] [nova] Nova mascot

Excerpts from Matt Riedemann's message of 2016-08-08 14:35:12 -0500: > Not to be a major curmudgeon but I think we'd basically decided at the > midcycle (actually weeks before) that Nova wasn't doing the mascot thing. > Could you maybe summarize the reason for this decision? Seems like everybod

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Excerpts from Ricardo Rocha's message of 2016-08-08 11:51:00 +0200: > Hi. > > On Mon, Aug 8, 2016 at 1:52 AM, Clint Byrum wrote: > > Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200: > >> On 05/08/16 21:48, Ricardo Rocha wrote: > >> >

Re: [openstack-dev] [ironic] About third-party CI

Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400: > 2) A number of drivers do not have third-party CI up, let alone reporting >on patches. Unless someone moves quickly, I strongly suspect the following >drivers will be dropped from our tree before the end of Newton. Thes

Re: [openstack-dev] [ironic] About third-party CI

Excerpts from Jim Rollenhagen's message of 2016-08-10 13:21:11 -0400: > On Wed, Aug 10, 2016 at 1:05 PM, Clint Byrum wrote: > > Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400: > >> 2) A number of drivers do not have third-party CI up, let alone

Re: [openstack-dev] [nova] os-capabilities library created

Excerpts from Jay Pipes's message of 2016-08-03 19:47:37 -0400: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

Excerpts from John Dickinson's message of 2016-08-12 13:02:59 -0700: > > On 12 Aug 2016, at 7:28, Doug Hellmann wrote: > > > Excerpts from John Dickinson's message of 2016-08-11 15:00:56 -0700: > >> > > > >> I agree with Hongbin Lu's comments that the resulting goals might fit > >> into the inter

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

Excerpts from Joshua Harlow's message of 2016-08-13 20:04:13 -0700: > The larger issue here IMHO is that there is now a API > around locking that might be better suited targeting an actual lock > management system (say redis or zookeeper or etcd or ...). The more I look at this, the more I thin

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

Excerpts from Sean Dague's message of 2016-08-16 10:35:11 -0400: > On 08/16/2016 05:36 AM, Thierry Carrez wrote: > > John Dickinson wrote: > Excerpts from John Dickinson's message of 2016-08-12 16:04:42 -0700: > > [...] > > The proposed plan has a lot of good in it, and I'm really happ

Re: [openstack-dev] [bifrost] Question about the "nics" argument provide to ansible os_ironic module.

Excerpts from hu.zhijiang's message of 2016-08-24 11:11:04 +0800: > Hi Bifrost Team, > > From the code study about Bifrost and Shade I found that the "nics" > argument provide to ansible's os_ironic module is used for creating ports > for a bare metal. I think it is related to neutron. But for b

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Mike Bayer's message of 2016-08-26 11:50:24 -0400: > > On 08/25/2016 01:13 PM, Steve Martinelli wrote: > > The keystone team is pursuing a trigger-based approach to support > > rolling, zero-downtime upgrades. The proposed operator experience is > > documented here: > > > > http://

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Mike Bayer's message of 2016-08-30 14:56:15 -0400: > > On 08/30/2016 09:57 AM, Clint Byrum wrote: > >> > > > > As someone else brought up, this is an unnecessarily bleak view of how > > database > > migrations work. > > We aren&#x

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Mike Bayer's message of 2016-08-30 18:15:14 -0400: > > On 08/30/2016 04:43 PM, Clint Byrum wrote: > >> > > > > Correct, it is harder for development. Since the database server has all > > of the potential for the worst problems, being a state

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Excerpts from Duncan Thomas's message of 2016-08-31 12:42:23 +0300: > On 31 August 2016 at 11:57, Bogdan Dobrelya wrote: > > > I agree that RPC design pattern, as it is implemented now, is a major > > blocker for OpenStack in general. It requires a major redesign, > > including handling of corner

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Excerpts from Ian Wells's message of 2016-08-31 12:30:45 -0700: > On 31 August 2016 at 10:12, Clint Byrum wrote: > > > Excerpts from Duncan Thomas's message of 2016-08-31 12:42:23 +0300: > > > On 31 August 2016 at 11:57, Bogdan Dobrelya > > wrote: > >

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Robert Collins's message of 2016-09-01 20:45:22 +1200: > On 31 August 2016 at 01:57, Clint Byrum wrote: > > > > > > It's simple, these are the holy SQL schema commandments: > > > > Don't delete columns, ignore them. > > Don&#x

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Excerpts from Ken Giusti's message of 2016-09-02 11:05:51 -0400: > On Thu, Sep 1, 2016 at 4:53 PM, Ian Wells wrote: > > On 1 September 2016 at 06:52, Ken Giusti wrote: > >> > >> On Wed, Aug 31, 2016 at 3:30 PM, Ian Wells wrote: > > > >> > I have opinions about other patterns we could use, but I

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Mike Bayer's message of 2016-09-02 17:58:42 -0400: > > On 09/02/2016 01:53 PM, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2016-09-02 12:15:33 +0200: > >> Sean Dague wrote: > >>> Putting DB trigger failure analysis into the toolkit required to manage > >>> an u

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Excerpts from Flavio Percoco's message of 2016-09-05 12:08:04 +0200: > On 02/09/16 10:56 -0700, Clint Byrum wrote: > >Excerpts from Ken Giusti's message of 2016-09-02 11:05:51 -0400: > >> On Thu, Sep 1, 2016 at 4:53 PM, Ian Wells wrote: > >> > On 1 Se

[openstack-dev] [architecture] Architecture WG Meeting time proposed - Thursdays, 1900 UTC [poppy]

Hi! We still have not landed the arch-wg spec [1] just yet, but there seems to be broad base consensus. So I believe it is time to start having regular IRC meetings to keep forward momentum. I've proposed [2] that we have meetings on Thursdays at 1900 UTC. I noticed that Poppy was scheduled to mee

[openstack-dev] [architecture] First meeting happened -- Regularly scheduled Thursdays at 1900

FYI, we had our first Architecture WG meeting this past Thursday. I want to thank everyone who was able to make it. I hope that we'll see increased attendance and be able to begin selecting specifications to discuss and work on starting with our next meeting. The agenda is available here: https:/

Re: [openstack-dev] [tc][all] CD tangent - was: A culture change (nitpicking)

Quoting Sean McGinnis (2018-05-31 09:54:46) > On 05/31/2018 03:50 AM, Thierry Carrez wrote: > > Right... There might be a reasonable middle ground between "every > > commit on master must be backward-compatible" and "rip out all > > testing" that allows us to routinely revert broken feature commi

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Jeremy Stanley's message of 2016-11-29 21:10:35 +: > On 2016-11-29 21:00:06 + (+), Sam Betts (sambetts) wrote: > [...] > > Additionally, being “official” indicates a level of maturity which > > benefits us as a project by improving the public perception of our > > drivers,

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Jeremy Stanley's message of 2016-11-29 21:52:35 +: > On 2016-11-29 13:40:56 -0800 (-0800), Clint Byrum wrote: > > Excerpts from Jeremy Stanley's message of 2016-11-29 21:10:35 +: > [...] > > > I also feel very strongly that those alone wou

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Excerpts from Tony Breeds's message of 2016-12-02 15:26:40 +1100: > On Thu, Dec 01, 2016 at 08:41:54AM -0800, Joshua Harlow wrote: > > Keen, Joe wrote: > > > I¹ll look into testing the newest version of kafka-python and see if it > > > meets our needs. If it still isn¹t stable and performant enoug

[openstack-dev] [architecture] Updates from the Architecture Working Group

Greetings! We've had a slow couple of months since Barcelona, and I expect we'll continue to go very slow for the rest of 2016, but we definitely don't want to lose momentum, so here is what we've been up to and where we're going in the immediate future: * arch-wg repo is live - This is the repo

[openstack-dev] [architecture][api][Nova][Neutron][Cinder] nova-compute's architecture/API

So, I've been quietly ranting in hallways about this for a while. I may be way way off base here. I want to kick the discussion off, so I've submitted a proposal to the arch-wg about it. Please if you're interested in how Nova/Neutron/Cinder interact with nova-compute, I think it might be worthwhil

[openstack-dev] [architecture] Return of the Arch-WG meeting -- Two proposals up for discussion

https://wiki.openstack.org/wiki/Meetings/Arch-WG With the US holidays over and people returning to their IRC clients, we'll be holding another Architecture Working Group meeting this Thursday at 2000 UTC. In preparation, I thought I'd put this out there so people can come armed with information so

Re: [openstack-dev] 答复: [heat] glance v2 support?

Excerpts from Zane Bitter's message of 2017-01-10 15:28:04 -0500: > On 10/01/17 14:17, Tim Bell wrote: > > > >> On 10 Jan 2017, at 17:41, Zane Bitter >> > wrote: > >> > >> On 10/01/17 05:25, Flavio Percoco wrote: > >>> > >>> > I'd recommend Heat to not use locations

Re: [openstack-dev] 答复: [heat] glance v2 support?

Excerpts from Thomas Herve's message of 2017-01-10 22:15:45 +0100: > On Tue, Jan 10, 2017 at 9:28 PM, Zane Bitter wrote: > > On 10/01/17 14:17, Tim Bell wrote: > >> > >> > >>> On 10 Jan 2017, at 17:41, Zane Bitter >>> > wrote: > >>> > >>> On 10/01/17 05:25, Flavio Perco

Re: [openstack-dev] 答复: [heat] glance v2 support?

Excerpts from Thomas Herve's message of 2017-01-11 08:50:19 +0100: > On Tue, Jan 10, 2017 at 10:41 PM, Clint Byrum wrote: > > Excerpts from Zane Bitter's message of 2017-01-10 15:28:04 -0500: > >> location is a required property: > >> > >> http://do

Re: [openstack-dev] [neutron] Confusion around the complexity

Excerpts from Joshua Harlow's message of 2017-01-12 22:38:46 -0800: > Kevin Benton wrote: > > If you don't want users to specify network details, then use the get me > > a network extension or just have them boot to a public (or other > > pre-created) network. > > > > In your thought experiment, wh

Re: [openstack-dev] PTG? / Was (Consistent Versioned Endpoints)

Excerpts from Fox, Kevin M's message of 2017-01-13 19:44:23 +: > Don't want to hijack the thread too much but... when the PTG was being sold, > it was a way to get the various developers in to one place and make it > cheaper to go to for devs. Now it seems to be being made into a place where

Re: [openstack-dev] [neutron] Confusion around the complexity

Excerpts from Armando M.'s message of 2017-01-13 11:39:33 -0800: > On 13 January 2017 at 10:47, Clint Byrum wrote: > > > Excerpts from Joshua Harlow's message of 2017-01-12 22:38:46 -0800: > > > Kevin Benton wrote: > > > > If you don't want users

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

Excerpts from Dave McCowan (dmccowan)'s message of 2017-01-18 15:58:19 +: > > On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco > mailto:sigmaviru...@gmail.com>> wrote: > Hi everyone, > > I've seen a few nascent projects wanting to implement their own secret > storage to either replace Barbican

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

Excerpts from Morgan Fainberg's message of 2017-01-18 15:33:00 -0800: > On Wed, Jan 18, 2017 at 11:23 AM, Brant Knudson wrote: > > > > > > > On Wed, Jan 18, 2017 at 9:58 AM, Dave McCowan (dmccowan) < > > dmcco...@cisco.com> wrote: > > > >> > >> On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco > >>

Re: [openstack-dev] [nova] To rootwrap or piggyback privsep helpers?

Excerpts from Thierry Carrez's message of 2017-01-26 10:08:52 +0100: > Michael Still wrote: > > I think #3 is the right call for now. The person we had working on > > privsep has left the company, and I don't have anyone I could get to > > work on this right now. Oh, and we're out of time. > > Yes

Re: [openstack-dev] [ironic] New mascot design

I'm only barely an Ironic contributor these days, but what about having the bear do David Lee Roth's famous jump? http://www.vhnd.com/wp-content/uploads/2015/01/kick_fb.jpg Doesn't require props, and no hand gestures. Alternatively, you could have the bear playing air guitar... if that can be ca

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

Excerpts from Matt Riedemann's message of 2017-02-04 16:09:56 -0600: > On 2/2/2017 4:01 PM, Sean Dague wrote: > > > > The only services that are running on Apache in standard gate jobs are > > keystone and the placement api. Everything else is still the > > oslo.service stack (which is basically ru

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600: > Hi everyone - from the Congress standalone installation guide > (http://docs.openstack.org/developer/congress/README.html#installing-congress): > > --- > To use RabbitMQ with Congress, set the transport_url in the “From > oslo.m

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Roman Podoliaka's message of 2017-02-03 17:16:36 +0200: > On Fri, Feb 3, 2017 at 4:41 PM, Mike Bayer wrote: > > Not sure if people on the list are seeing that we are simultaneously talking > > about getting rid of Postgresql in the efforts to support only "one > > database", while at

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

Excerpts from Jay Pipes's message of 2017-02-06 16:23:51 -0500: > On 02/06/2017 04:09 PM, Aimee Ukasick wrote: > > Thanks, Clint, for your quick response. Questions inline. > > On 02/06/2017 01:32 PM, Clint Byrum wrote: > >> Excerpts from Aimee Ukasick's me

Re: [openstack-dev] [All] IRC Mishaps

Excerpts from Mark Voelker's message of 2017-02-09 15:41:33 +: > I work with lots of different clouds and any time I switch focus to a > terminal I have to figure out which cloud it’s environment is set up to use. > My terminal emulator has the same color scheme as my IRC client, so I’ve >

Re: [openstack-dev] [designate] Status of the project

Excerpts from Joshua Harlow's message of 2017-02-10 11:07:29 -0800: > Fox, Kevin M wrote: > > I'd say kube-dns and designate are very different technologies. > > > > kube-dns is a service discovery mechanism for kubernetes intend to provide > > internal k8s resolution. The fact it uses dns to impl

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Excerpts from Brian Rosmaita's message of 2017-02-10 12:39:11 -0500: > I want to give all interested parties a heads up that I have scheduled a > session in the Macon room from 9:30-10:30 a.m. on Thursday morning > (February 23). > > Here's what we need to discuss. This is from my perspective as

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Excerpts from Mikhail Fedosin's message of 2017-02-13 18:23:19 +0300: > Hello! > > > Let me quickly describe my vision of the problem. I asked this question to > Brian last Friday, because it is evident that the projects have the > intersection in functionality. For this reason, I proposed to bri

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Excerpts from Ian Cordasco's message of 2017-02-13 15:15:12 -0500: > -Original Message- > From: Clint Byrum > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: February 13, 2017 at 13:41:00 > To: openstack-dev > Subject:  Re: [

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100: > All this to say that, unless someone wants to hire me for it (which > would be the best outcome, but I fear this wont happen), or if someone > steps in (this seems unlikely at this point), both the packaging-deb and > the faith

Re: [openstack-dev] [keystone]PKI token VS Fernet token

Excerpts from 王玺源's message of 2017-02-17 14:08:30 +: > Hi David: > > We have not find the perfect solution to solve the fernet performance > issue, we will try the different crypt strength setting with fernet in > future. > One important thing: did you try throwing more hardware at Keystone

[openstack-dev] [architecture][nova][neutron][cinder][ceilometer][ironic] PTG stuff -- Arch-WG nova-compute-api fact-gathering session Tuesday 10:30 Macon

Hello, I'm looking forward to seeing many of you next week in Atlanta. We're going to be working on Arch-WG topics all day Tuesday, and if you'd like to join us for that in general, please add your topic here: https://etherpad.openstack.org/p/ptg-architecture-workgroup I specifically want to call

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Michael Still's message of 2017-02-18 09:41:03 +1100: > We have had this discussion several times in the past for other reasons. > The reality is that some people will never deploy the metadata API, so I > feel like we need a better solution than what we have now. > > However, I woul

Re: [openstack-dev] [architecture][nova][neutron][cinder][ceilometer][ironic] PTG Arch-WG

I've been told that the original subject of this broke some mail clients. Hopefully this gets past their brokenness and you can all see the content now. :) Excerpts from Clint Byrum's message of 2017-02-17 10:16:05 -0800: > Hello, I'm looking forward to seeing many of you next week in Atlanta. > W

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-17 01:54:55 +0100: > On 02/16/2017 05:55 PM, Clint Byrum wrote: > > Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100: > >> All this to say that, unless someone wants to hire me for it (which > >

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Dean Troyer's message of 2017-02-18 08:21:29 -0600: > On Sat, Feb 18, 2017 at 7:11 AM, Artom Lifshitz wrote: > > In reply to Michael: > > I hadn't even thought of the security implication. That's a very good > > point, there's no way to persist admin_pass in securely. We'll have to >

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Artom Lifshitz's message of 2017-02-18 08:11:10 -0500: > In reply to Clint: > > > Agreed. What if we simply have a second config drive that is for "things > > that change" and only rebuild that one on reboot? > > We've already set the precedent that there's a single config drive > w

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100: > On 02/18/2017 07:59 AM, Clint Byrum wrote: > > Indeed, DPMT uses all the worst choices for maintaining most of the > > python module packages in Debian. However, something will need to be > >

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Artom Lifshitz's message of 2017-02-20 08:23:09 -0500: > Config drive over read-only NFS anyone? > > > A shared filesystem so that both Nova and the guest can do IO on it at the > same time is indeed the proper way to solve this. But I'm afraid of the > ramifications in terms of liv

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Jay Pipes's message of 2017-02-20 10:00:06 -0500: > On 02/17/2017 02:28 PM, Artom Lifshitz wrote: > > Early on in the inception of device role tagging, it was decided that > > it's acceptable that the device metadata on the config drive lags > > behind the metadata API, as long as it

Re: [openstack-dev] [architecture][nova][neutron][cinder][ceilometer][ironic] PTG stuff -- Arch-WG nova-compute-api fact-gathering session Tuesday 10:30 Macon

Excerpts from Dmitry Tantsur's message of 2017-02-18 18:54:59 +0100: > 2017-02-17 19:16 GMT+01:00 Clint Byrum : > > > Hello, I'm looking forward to seeing many of you next week in Atlanta. > > We're going to be working on Arch-WG topics all day Tuesday, and if &

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-21 00:50:35 +0100: > On 02/19/2017 08:43 PM, Clint Byrum wrote: > > Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100: > >> On 02/18/2017 07:59 AM, Clint Byrum wrote: > >>> Indeed, DPMT us

[openstack-dev] [kolla][nova] Safe guest shutdowns with kolla?

Greetings! We've been deploying with Kolla on CentOS 7 now for a while, and we've recently noticed a rather troubling behavior when we shutdown hypervisors. Somewhere between systemd and libvirt's systemd-machined integration, we see that guests get killed aggressively by SIGTERM'ing all of the qe

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Henry Nash's message of 2016-09-15 00:29:44 +0100: > Jay, > > I agree with your distinction - and when I am referring to rolling upgrades > for keystone I am referring to when you are running a cluster of keystones > (for performance and/or redundancy), and you want to roll the upg

Re: [openstack-dev] [nova] Question about fixing missing soft deleted rows

Excerpts from Matt Riedemann's message of 2016-09-14 20:21:09 -0500: > I'm looking for other input on a question I have in this change: > > https://review.openstack.org/#/c/345191/4/nova/db/sqlalchemy/api.py > > We've had a few patches like this where we don't (soft) delete entries > related to

Re: [openstack-dev] [all] Ocata Design Summit - Proposed slot allocation

Excerpts from Thierry Carrez's message of 2016-09-15 09:37:47 +0200: > Emilien Macchi wrote: > > On Wed, Sep 14, 2016 at 1:51 PM, wrote: > >> Also if you don't plan to use all of your > >>> > >>> allocated slots, let us know so that we can propose them to other teams. > >>> > >> Just so that we a

Re: [openstack-dev] [all] Ocata Design Summit - Proposed slot allocation

Excerpts from Thierry Carrez's message of 2016-09-15 09:50:51 +0200: > Clint Byrum wrote: > > Excerpts from Thierry Carrez's message of 2016-09-15 09:37:47 +0200: > >> Emilien Macchi wrote: > >>> On Wed, Sep 14, 2016 at 1:51 PM, wrote: > >

[openstack-dev] [diskimage-builder] Stepping down as diskimage-builder core

It's been my honor to be included with the core reviewer group on diskimage-builder, but my focus has changed quite a bit and I'm not able to keep up with the review load. As a result, I've lost most of the context and struggle to understand patches enough to +2 them. Given that, I'm laying down m

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200: > Hello, > > it's definately our bad that we missed elections in OpenStackSalt > project. Reason is similar to Rob's - we are active on different > channels (mostly IRC as we keep regular meetings) and don't used to > reading mail

Re: [openstack-dev] [nova] Is there any reason we shouldn't remove nova.image.s3 now?

Excerpts from Matt Riedemann's message of 2016-09-21 18:43:06 -0500: > The s3 image configuration options were deprecated for removal in newton > [1]. > > Clint has a patch up to remove the boto dependency from nova [2] which > is only used in the nova.image.s3 module. > > Rather than remove th

Re: [openstack-dev] os-loganalyze, project log parsing, or ...

Excerpts from Andrew Laski's message of 2016-09-27 11:36:07 -0400: > Hello all, > > Recently I noticed that people would look at logs from a Zuul née > Jenkins CI run and comment something like "there seem to be more > warnings in here than usual." And so I thought it might be nice to > quantify t

[openstack-dev] TC candidacy

, I will build a wall, and make Go pay for it. ... Ok if you're still reading and you don't take things too seriously, then hello. I'm Clint Byrum, known as "SpamapS" on IRC, and I want to serve you on the OpenStack Technical Committee. You may recognize me from various scalabi

Re: [openstack-dev] [tc] open question to the candidates

Excerpts from gordon chung's message of 2016-10-03 15:30:56 +: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the > can

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Edward Leafe's message of 2016-10-03 11:46:41 -0500: > So the period of self-nominations for the Technical Committee seats has > ended, and the voting has begun. I've been a very close observer of this > process for several cycles, and I have some ideas I'd like to share. Full > di

[openstack-dev] [Architecture] APAC friendly meeting time for Architecture Working Group proposed

Hello, we want to get as much broad participation as possible with the Architecture Working Group, so I've proposed an alternating odd/even schedule change here: https://review.openstack.org/379768 I'm hoping the proposed time is convenient and can be attended by those in time zones very far ahea

Re: [openstack-dev] [mistral] Who's interested in attending PTG?

Excerpts from Renat Akhmerov's message of 2016-10-06 19:21:40 +0700: > Hi, > > As you likely know, the summit format will change after Barcelona. There will > be two events now: PTG (Project Team Gathering) for design sessions and > OpenStack Summit which is more customer/promotion oriented . Th

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Matt Riedemann's message of 2016-10-06 11:33:35 -0500: > This is just a follow up email to the discussion about nova's > participation in the Project Team Gathering (PTG) in February right > after the Ocata release. > > I had asked because the OpenStack Foundation is getting early

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Thierry Carrez's message of 2016-10-07 10:20:51 +0200: > Doug Hellmann wrote: > > Excerpts from Matt Riedemann's message of 2016-10-06 13:52:09 -0500: > >> Sorry yeah I screwed that up. I re-read the PTG email and the first two > >> days are cross-project things, and Wed-Fri are meet

Re: [openstack-dev] [all][elections] Results of the TC Election

Excerpts from Zane Bitter's message of 2016-10-10 11:10:53 -0400: > On 09/10/16 19:58, Tony Breeds wrote: > > On Mon, Oct 10, 2016 at 10:49:12AM +1100, Tony Breeds wrote: > >> Please join me in congratulating the 6 newly elected members of the TC. > >> > >> Doug Hellmann (dhellmann) > >> Emilien Ma

Re: [openstack-dev] [all][elections] Results of the TC Election

Excerpts from Tony Breeds's message of 2016-10-10 10:49:12 +1100: > Please join me in congratulating the 6 newly elected members of the TC. > > Doug Hellmann (dhellmann) > Emilien Macchi (emilienm) > Jeremy Stanley (fungi) > Monty Taylor (mordred) > Sean Dague (sdague) > Steve Martinelli (stevemar

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Matt Riedemann's message of 2016-10-10 11:51:36 -0500: > On 10/10/2016 8:59 AM, Sean McGinnis wrote: > > On Mon, Oct 10, 2016 at 08:37:53AM -0400, Doug Hellmann wrote: > >>> > >> > >> We had a lot of feedback that the unstructured discussion time from > >> the Friday "meetups" at the

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Thierry Carrez's message of 2016-10-11 14:04:55 +0200: > Clint Byrum wrote: > > > Whatever we do, please consider dismantling the silos, rather than > > reinforcing them. > > We do dismantle the silos. (1) the upstream silos between vertical and >

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Steven Dake (stdake)'s message of 2016-10-12 06:42:43 +: > Tom, > > No flame, just observation about the reality of these changes. > > I think we missed this communication on the mailing list or in the FAQs or > somewhere else. I think most engineering-focused organizations ar

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Chris Dent's message of 2016-10-12 15:08:48 +0100: > On Wed, 12 Oct 2016, Clint Byrum wrote: > > > So, while I do want to make sure enough of our architects and designers > > go to the summit to truly understand user needs, I also think it has > > be

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Jaesuk Ahn's message of 2016-10-12 15:08:24 +: > It can be cheap if you are in the US. However, for Asia folks, it is not > that cheap considering it is all overseas travel. In addition, all-in-one > event like the current summit makes us much easier to get the travel fund > from

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Dmitry Tantsur's message of 2016-10-13 10:30:44 +0200: > On 10/12/2016 08:47 PM, Clint Byrum wrote: > > Excerpts from Jaesuk Ahn's message of 2016-10-12 15:08:24 +: > >> It can be cheap if you are in the US. However, for Asia folks, it is not > >

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Eoghan Glynn's message of 2016-10-14 05:08:44 -0400: > > > > > Excerpts from Jaesuk Ahn's message of 2016-10-12 15:08:24 +: > > > >> It can be cheap if you are in the US. However, for Asia folks, it is > > > >> not > > > >> that cheap considering it is all overseas travel. In ad

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Jay Pipes's message of 2016-10-14 16:55:39 -0400: > Alex, so sorry for the long delayed response! :( This just crept to > the back of my inbox unfortunately. Answer inline... > > On 09/14/2016 07:24 PM, Bashmakov, Alexander wrote: > >> Glance and Keystone do not participate in a roll

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Chris Dent's message of 2016-10-17 10:38:25 +0100: > On Mon, 17 Oct 2016, Renat Akhmerov wrote: > > > If you are a developer, of course, PTG is an important event to > > attend. But… Being a developer, I would also love to attend summits > > also. For a bunch of reasons like catching

[openstack-dev] [architecture] Cancelling next two Architecture Working Group IRC meetings

With many preparing to travel to the summit, and our summit fishbowl session next week [1] we're going to go ahead and cancel this week and next week's Architecture WG IRC meetings. For those attending the summit, I hope to see you all there with your proposals for Architecture WG topics. And for

Re: [openstack-dev] [FaaS] Function as a service in OpenStack

Excerpts from Lingxian Kong's message of 2016-11-02 15:20:45 +1300: > Hi, all, > > Recently when I was talking with some customers of our OpenStack based > public cloud, some of them are expecting to see a service similar to AWS > Lambda in OpenStack ecosystem (so such service could be invoked by

<    8   9   10   11   12   13   14   >