Re: [openstack-dev] [oslo.config] Centralized config management

Excerpts from Nachi Ueno's message of 2014-01-13 10:35:07 -0800: > Hi Clint > > 2014/1/10 Clint Byrum : > > Excerpts from Nachi Ueno's message of 2014-01-10 13:42:30 -0700: > >> Hi Flavio, Clint > >> > >> I agree with you guys. > >>

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Excerpts from Walls, Jeffrey Joel (Cloud OS R&D)'s message of 2014-01-13 06:54:11 -0800: > > From: Jaromir Coufal [mailto:jcou...@redhat.com] > >> On 2014/10/01 19:02, Dougal Matthews wrote: > > > > - If I remove some instances, do I as the administrator need to care > > > which are removed? Do w

Re: [openstack-dev] [heat] Sofware Config progress

Hey Steve, it has taken me about a month to get enough time to go through this. Thanks for doing it, comments in-line. Excerpts from Steve Baker's message of 2013-12-13 15:46:48 -0800: > I've been working on a POC in heat for resources which perform software > configuration, with the aim of implem

Re: [openstack-dev] [heat] Sofware Config progress

Excerpts from Prasad Vellanki's message of 2014-01-13 23:23:15 -0800: > On Thu, Jan 9, 2014 at 6:14 AM, Steven Dake wrote: > > > that > > > Steve > Thanks for detailed email. Apologize for the delayed response but we have > been thinking about how does software config fit into configuring netwo

Re: [openstack-dev] [heat] Sofware Config progress

Excerpts from Prasad Vellanki's message of 2014-01-14 18:41:46 -0800: > Steve > > I did not mean to have custom solution at all. In fact that would be > terrible. I think Heat model of software config and deployment is really > good. That allows configurators such as Chef, Puppet, Salt or Ansible

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Excerpts from Vitaly Kramskikh's message of 2014-01-14 12:35:43 -0800: > Hi Jaromir, > > 2014/1/13 Jaromir Coufal > > > So what we can do at the moment (until there is some way to specify which > > node to remove) is to inform user, which nodes were removed in the end... > > at least. > > > > In

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Excerpts from Jaromir Coufal's message of 2014-01-15 02:05:52 -0800: > > 1) Check for an already deleted server before deleting any. This is > > related to stack convergence: > > > > https://blueprints.launchpad.net/heat/+spec/stack-convergence > > > > This will allow users to just delete a server

Re: [openstack-dev] [Ironic] [TripleO] [Tuskar] Deployment Management section - Wireframes

Excerpts from Jiří Stránský's message of 2014-01-13 07:45:53 -0800: > On 13.1.2014 11:43, Jaromir Coufal wrote: > > On 2014/10/01 21:17, Jay Dobies wrote: > >> Another question: > >> > >> - A Role (sounds like we're moving away from that so I'll call it > >> Resource Category) can have multiple Nod

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Excerpts from Walls, Jeffrey Joel (Cloud OS R&D)'s message of 2014-01-15 07:04:48 -0800: > > -Original Message- > > From: James Slagle [mailto:james.sla...@gmail.com] > > Sent: Wednesday, January 15, 2014 5:52 AM > > To: OpenStack Development Mailing List (not for usage questions) > > Subj

Re: [openstack-dev] [TripleO][Tuskar] Editing Nodes

Excerpts from James Slagle's message of 2014-01-15 05:07:08 -0800: > I'll start by laying out how I see editing or updating nodes working > in TripleO without Tuskar: > > To do my initial deployment: > 1. I build a set of images for my deployment for different roles. The > images are different ba

Re: [openstack-dev] [Nova] why don't we deal with "claims" when live migrating an instance?

Hi Chris. Your thread may have gone unnoticed as it lacked the Nova tag. I've added it to the subject of this reply... that might attract them. :) Excerpts from Chris Friesen's message of 2014-01-15 12:32:36 -0800: > When we create a new instance via _build_instance() or > _build_and_run_instanc

Re: [openstack-dev] Proposal for dd disk i/o performance blueprint of cinder.

Excerpts from Alan Kavanagh's message of 2014-01-15 19:11:03 -0800: > Hi Paul > > I posted a query to Ironic which is related to this discussion. My thinking > was I want to ensure the case you note here (1) " a tenant can not read > another tenants disk.." the next (2) was where in Ironic y

Re: [openstack-dev] Proposal for dd disk i/o performance blueprint of cinder.

Excerpts from Fox, Kevin M's message of 2014-01-16 09:29:14 -0800: > Yeah, I think the evil firmware issue is separate and should be solved > separately. > > Ideally, there should be a mode you can set the bare metal server into where > firmware updates are not allowed. This is useful to more fo

Re: [openstack-dev] Proposal for dd disk i/o performance blueprint of cinder.

Excerpts from CARVER, PAUL's message of 2014-01-16 05:21:24 -0800: > > Alan Kavanagh wrote: > > >I posted a query to Ironic which is related to this discussion. My thinking > >was I want to ensure the case you note here (1) " a >tenant can not read > >another tenants disk.." the next (2) w

Re: [openstack-dev] [TripleO] milestone-proposed branches

Note that tripleo-incubator is special and should not be released. It is intentionally kept unfrozen and unreleased to make sure there is no illusion of stability. If there are components in it that need releasing, they should be moved into relevant projects or forked into their own projects. Exc

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

Excerpts from Jay Pipes's message of 2014-01-12 11:40:41 -0800: > On Fri, 2014-01-10 at 10:28 -0500, Jay Dobies wrote: > > >> So, it's not as simple as it may initially seem :) > > > > > > Ah, I should have been clearer in my statement - my understanding is that > > > we're scrapping concepts like

Re: [openstack-dev] Proposal for dd disk i/o performance blueprint of cinder.

Excerpts from Alan Kavanagh's message of 2014-01-16 20:28:05 -0800: > +1makes sense to me. I will write up a Blueprint for this for review in > Ironic and we take it from their. > > I don't see this as evil firmware, more a good process we need to automate as > part of sanity checks before

Re: [openstack-dev] [TripleO] milestone-proposed branches

tl;dr: You're right, it would be useful. Points on what is blocking it below: Excerpts from James Slagle's message of 2014-01-17 05:18:01 -0800: > On Thu, Jan 16, 2014 at 7:29 PM, Clint Byrum wrote: > > Note that tripleo-incubator is special and should not be released. It &

Re: [openstack-dev] [Neutron] Relationship between Neutron LBaaS and Libra

Excerpts from Jay Pipes's message of 2014-01-18 11:02:12 -0800: > Cutting to the chase... have there been any discussions about the > long-term direction of Libra and Neutron LBaaS. I see little point > having two OpenStack endpoints that implement the same basic load > balancing functionality. >

Re: [openstack-dev] [Neutron] Relationship between Neutron LBaaS and Libra

Excerpts from Thomas Herve's message of 2014-01-19 01:52:56 -0800: > > > Hi, > > > > I haven’t read through those (need to go spend time with family so replying > > quickly) but given the dates the planning phases for Quantum/Neutron LBaaS > > and Libra LBaaS were at the same time. > > > > There

Re: [openstack-dev] Unified Guest Agent, PoC for os-collect-config

Excerpts from Dmitry Mescheryakov's message of 2014-01-21 09:30:17 -0800: > Hello folks, > > At the end of the previous discussion on the topic [1] I've decided to make > a PoC based on oslo.messaging. Clint suggested and I agreed to make it for > os-collect-config. Actually I've made a PoC for Sa

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Dan Prince's message of 2014-01-22 09:17:24 -0800: > I've been thinking a bit more about how TripleO updates are developing > specifically with regards to compute nodes. What is commonly called the > "update story" I think. > > As I understand it we expect people to actually have to

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Dan Prince's message of 2014-01-22 10:15:20 -0800: > > - Original Message - > > From: "Clint Byrum" > > To: "openstack-dev" > > Sent: Wednesday, January 22, 2014 12:45:45 PM > > Subject: Re: [openstack-dev] [Tri

Re: [openstack-dev] [TripleO] our update story: can people live with it?

15 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [TripleO] our update story: can people live > with it? > > - Original Message - > > From: "Clint Byrum" > > To: "openstack-dev&

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Jay Pipes's message of 2014-01-22 10:53:14 -0800: > On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote: > > > > - Original Message - > > > From: "Clint Byrum" > > > To: "openstack-dev" > > > Sent: Wednes

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Fox, Kevin M's message of 2014-01-22 12:19:56 -0800: > I think most of the time taken to reboot is spent in bringing down/up the > services though, so I'm not sure what it really buys you if you do it all. It > may let you skip the crazy long bootup time on "enterprise" hardware, bu

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Keith Basil's message of 2014-01-22 12:27:50 -0800: > On Jan 22, 2014, at 1:53 PM, Jay Pipes wrote: > > > On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote: > >> > >> - Original Message - > >>> From: "Clint Byrum"

Re: [openstack-dev] Changes coming in gate structure

Excerpts from Jay Pipes's message of 2014-01-22 13:43:41 -0800: > On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote: > > > > == > > Executive Summary > > == > > To summarize, the effects of these changes will be: > > > > - 1) Decrease the impact

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Angus Thomas's message of 2014-01-23 04:57:20 -0800: > On 22/01/14 20:54, Clint Byrum wrote: > >> > > >> >I don't understand the aversion to using existing, well-known tools to > >> >handle this? > >> > > > These

Re: [openstack-dev] [TripleO] our update story: can people live with it?

; image, at least on disk. The running state would differ and that still > requires some design and implementation to figure out. > > Cheers, > -- > Chris Jones > > > On 23 Jan 2014, at 12:57, Angus Thomas wrote: > > > > On 22/01/14 20:54, Clint Byrum wrote: &g

Re: [openstack-dev] [Murano] Repositoris re-organization

Excerpts from Alexander Tivelkov's message of 2014-01-21 11:55:34 -0800: > Hi folks, > > As we are moving towards incubation application, I took a closer look at > what is going on with our repositories. > An here is what I found. We currently have 11 repositories at stackforge: > >- murano-a

Re: [openstack-dev] [heat] question on proposed software config

Excerpts from Prasad Vellanki's message of 2014-01-24 00:21:06 -0800: > I have a question on agent as part of cfninit that communicates with heat > about config done state indication or config tool agent such as chef or > puppet communicating with chef server. > > Since the VM resides on the data

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Excerpts from Justin Santa Barbara's message of 2014-01-24 07:43:23 -0800: > Good points - thank you. For arbitrary operations, I agree that it would > be better to expose a token in the metadata service, rather than allowing > the metadata service to expose unbounded amounts of API functionality.

Re: [openstack-dev] MariaDB support

Excerpts from Tim Bell's message of 2014-01-24 10:32:26 -0800: > > We are reviewing options between MySQL and MariaDB. RHEL 7 beta seems to have > MariaDB as the default MySQL-like DB. > > Can someone summarise the status of the OpenStack in terms of > > > -What MySQL-flavor is/are cur

Re: [openstack-dev] MariaDB support

Excerpts from Steven Dake's message of 2014-01-24 11:05:25 -0800: > On 01/24/2014 11:47 AM, Clint Byrum wrote: > > Excerpts from Tim Bell's message of 2014-01-24 10:32:26 -0800: > >> We are reviewing options between MySQL and MariaDB. RHEL 7 beta seems to > >&

Re: [openstack-dev] [Ironic] File Injection (and the lack thereof)

Excerpts from Devananda van der Veen's message of 2014-01-24 06:15:12 -0800: > In going through the bug list, I spotted this one and would like to discuss > it: > > "can't disable file injection for bare metal" > https://bugs.launchpad.net/ironic/+bug/1178103 > > There's a #TODO in Ironic's PXE d

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Day, Phil's message of 2014-01-24 04:39:10 -0800: > > On 01/22/2014 12:17 PM, Dan Prince wrote: > > > I've been thinking a bit more about how TripleO updates are developing > > specifically with regards to compute nodes. What is commonly called the > > "update story" I think. > > > >

Re: [openstack-dev] [TripleO] our update story: can people live with it?

Excerpts from Day, Phil's message of 2014-01-24 04:24:11 -0800: > > > > > > Cool. I like this a good bit better as it avoids the reboot. Still, this > > > is a rather > > large amount of data to copy around if I'm only changing a single file in > > Nova. > > > > > > > I think in most cases trans

Re: [openstack-dev] MariaDB support

Excerpts from Chuck Short's message of 2014-01-24 11:46:47 -0800: > On Fri, Jan 24, 2014 at 2:05 PM, Steven Dake wrote: > > > On 01/24/2014 11:47 AM, Clint Byrum wrote: > > > >> Excerpts from Tim Bell's message of 2014-01-24 10:32:26 -0800: > >> &g

Re: [openstack-dev] MariaDB support

Excerpts from Tim Bell's message of 2014-01-24 11:55:02 -0800: > > This is exactly my worry... at what point can I consider moving to MariaDB > with the expectation that the testing confidence is equivalent to that which > is currently available from MySQL ? > > The on-disk format is not so muc

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Excerpts from Justin Santa Barbara's message of 2014-01-24 12:29:49 -0800: > Clint Byrum wrote: > > > > > Heat has been working hard to be able to do per-instance limited access > > in Keystone for a while. A trust might work just fine for what you want. > >

Re: [openstack-dev] [Ironic] File Injection (and the lack thereof)

Excerpts from Joshua Harlow's message of 2014-01-24 14:17:38 -0800: > Cloud-init 0.7.5 (not yet released) will have the ability to read from an > ec2-metadata server using SSL. > > In a recent change I did we now use requests which correctly does SSL for > the ec2-metadata/ec2-userdata reading. >

Re: [openstack-dev] [Ironic] File Injection (and the lack thereof)

n der Veen's message of 2014-01-24 14:41:44 -0800: > Awesome! But, Ironic will still need a way to inject the SSL cert into the > instance, eg. config-drive over virtual media, or something. > > -D > On Jan 24, 2014 2:32 PM, "Clint Byrum" wrote: > > > Excerpt

Re: [openstack-dev] [Ironic] Node groups and multi-node operations

Excerpts from Devananda van der Veen's message of 2014-01-22 16:44:01 -0800: > > 1: physical vs. logical grouping > - Some hardware is logically, but not strictly physically, grouped. Eg, 1U > servers in the same rack. There is some grouping, such as failure domain, > but operations on discrete no

Re: [openstack-dev] [Ironic] Node groups and multi-node operations

Excerpts from Robert Collins's message of 2014-01-24 18:48:41 -0800: > On 25 Jan 2014 15:11, "Clint Byrum" wrote: > > > > Excerpts from Devananda van der Veen's message of 2014-01-22 16:44:01 > -0800: > > > > What Tuskar wants to do is layer work

Re: [openstack-dev] [Ironic] Node groups and multi-node operations

Excerpts from Robert Collins's message of 2014-01-25 02:47:42 -0800: > On 25 January 2014 19:42, Clint Byrum wrote: > > Excerpts from Robert Collins's message of 2014-01-24 18:48:41 -0800: > > >> > However, in looking at how Ironic works and interacts with Nova,

Re: [openstack-dev] [Neutron] Relationship between Neutron LBaaS and Libra

Excerpts from Vishvananda Ishaya's message of 2014-01-21 12:16:12 -0800: > > On Jan 19, 2014, at 8:19 AM, Clint Byrum wrote: > > > Excerpts from Thomas Herve's message of 2014-01-19 01:52:56 -0800: > >> > >>> Hi, > >>> > >>&

Re: [openstack-dev] [Ironic] Node groups and multi-node operations

Excerpts from Devananda van der Veen's message of 2014-01-26 10:27:36 -0800: > On Sat, Jan 25, 2014 at 7:11 AM, Clint Byrum wrote: > > > > Excerpts from Robert Collins's message of 2014-01-25 02:47:42 -0800: > > > On 25 January 2014 19:42, Clint Byrum w

Re: [openstack-dev] [TripleO] State preserving upgrades working, next MVP selection?

Excerpts from Dan Prince's message of 2014-01-27 09:22:21 -0800: > > - Original Message - > > From: "Robert Collins" > > To: "OpenStack Development Mailing List" > > Sent: Sunday, January 26, 2014 3:30:22 PM > > Subject: [openstack-dev] [TripleO] State preserving upgrades working, >

Re: [openstack-dev] [Ceilometer] [TripleO] adding process/service monitoring

Excerpts from Richard Su's message of 2014-01-27 17:59:34 -0800: > Hi, > > I have been looking into how to add process/service monitoring to > tripleo. Here I want to be able to detect when an openstack dependent > component that is deployed on an instance has failed. And when a failure > has occu

Re: [openstack-dev] [Heat] About LaunchConfiguration and Autoscaling

Excerpts from Thomas Herve's message of 2014-01-30 03:01:38 -0800: > Hi all, > > While talking to Zane yesterday, he raised an interesting question about > whether or not we want to keep a LaunchConfiguration object for the native > autoscaling resources. > > The LaunchConfiguration object basi

Re: [openstack-dev] [Heat] About LaunchConfiguration and Autoscaling

Excerpts from Zane Bitter's message of 2014-01-30 07:38:38 -0800: > On 30/01/14 06:01, Thomas Herve wrote: > > Hi all, > > > > While talking to Zane yesterday, he raised an interesting question about > > whether or not we want to keep a LaunchConfiguration object for the native > > autoscaling re

Re: [openstack-dev] [TripleO] devtest thoughts

Excerpts from Ben Nemec's message of 2014-01-30 11:08:44 -0800: > On 2014-01-30 09:28, James Slagle wrote: > > devtest, our TripleO setup, has been rapidly evolving. We've added a > > fair amount of configuration options for stuff like using actual > > baremetal, and (soon) HA deployments by defaul

Re: [openstack-dev] [TripleO] devtest thoughts

Excerpts from James Slagle's message of 2014-01-30 07:28:01 -0800: > devtest, our TripleO setup, has been rapidly evolving. We've added a > fair amount of configuration options for stuff like using actual > baremetal, and (soon) HA deployments by default. Also, the scripts > (which the docs are gen

Re: [openstack-dev] [Heat] How to model resources in Heat

Excerpts from Mark Washenberger's message of 2014-01-30 12:41:40 -0800: > On Wed, Jan 29, 2014 at 5:03 PM, Zane Bitter wrote: > > (I'm not touching the question of whether Heat should have a Glance Image > > resource at all, which I'm deeply ambivalent about.) > > > > Maybe I'm just missing the u

Re: [openstack-dev] [Heat] How to model resources in Heat

Excerpts from Zane Bitter's message of 2014-01-30 19:30:40 -0800: > On 30/01/14 16:54, Clint Byrum wrote: > > I'm pretty sure it is useful to model images in Heat. > > > > Consider this scenario: > > > > > > resources: > >

Re: [openstack-dev] [Heat] How to model resources in Heat

Excerpts from Hugh Brock's message of 2014-01-31 04:53:11 -0800: > > On Jan 31, 2014, at 1:30 AM, Clint Byrum wrote: > > > > Excerpts from Zane Bitter's message of 2014-01-30 19:30:40 -0800: > >>> On 30/01/14 16:54, Clint Byrum wrote: > >>>

Re: [openstack-dev] [TripleO] [Ironic] Roadmap towards heterogenous hardware support

Excerpts from Jaromir Coufal's message of 2014-02-02 11:19:25 -0800: > On 2014/30/01 23:33, Devananda van der Veen wrote: > > I was responding based on "Treat similar hardware configuration as > > equal". When there is a very minor difference in hardware (eg, 1TB vs > > 1.1TB disks), enrolling them

[openstack-dev] [Heat] [TripleO] Rolling updates spec re-written. RFC

So, I wrote the original rolling updates spec about a year ago, and the time has come to get serious about implementation. I went through it and basically rewrote the entire thing to reflect the knowledge I have gained from a year of working with Heat. Any and all comments are welcome. I intend to

Re: [openstack-dev] [Heat] [TripleO] Rolling updates spec re-written. RFC

Excerpts from Robert Collins's message of 2014-02-03 10:47:06 -0800: > Quick thoughts: > > - I'd like to be able to express a minimum service percentage: e.g. I > know I need 80% of my capacity available at anyone time, so an > additional constraint to the unit counts, is to stay below 20% down a

Re: [openstack-dev] [Heat] [TripleO] Rolling updates spec re-written. RFC

Excerpts from Thomas Herve's message of 2014-02-03 12:46:05 -0800: > > So, I wrote the original rolling updates spec about a year ago, and the > > time has come to get serious about implementation. I went through it and > > basically rewrote the entire thing to reflect the knowledge I have > > gain

Re: [openstack-dev] Ugly Hack to deal with multiple versions

Excerpts from Jesse Noller's message of 2014-02-04 11:55:57 -0800: > > On Feb 4, 2014, at 1:28 PM, Sean Dague wrote: > > > On 02/05/2014 01:50 AM, Jesse Noller wrote: > >> > >> On Feb 4, 2014, at 10:31 AM, Sean Dague wrote: > >> > >>> On 02/05/2014 01:09 AM, Dean Troyer wrote: > On Tue,

Re: [openstack-dev] [Heat] [TripleO] Rolling updates spec re-written. RFC

Excerpts from Zane Bitter's message of 2014-02-04 16:14:09 -0800: > On 03/02/14 17:09, Clint Byrum wrote: > > Excerpts from Thomas Herve's message of 2014-02-03 12:46:05 -0800: > >>> So, I wrote the original rolling updates spec about a year ago, and the > >

Re: [openstack-dev] why do we put a license in every file?

Excerpts from Greg Hill's message of 2014-02-05 08:29:20 -0800: > I'm new, so I'm sure there's some history I'm missing, but I find it bizarre > that we have to put the same license into every single file of source code in > our projects. In my past experience, a single LICENSE file at the root-

Re: [openstack-dev] [Heat] [TripleO] Rolling updates spec re-written. RFC

Excerpts from Steven Dake's message of 2014-02-05 07:35:37 -0800: > On 02/04/2014 06:34 PM, Robert Collins wrote: > > On 5 February 2014 13:14, Zane Bitter wrote: > > > > > >> That's not a great example, because one DB server depends on the other, > >> forcing them into updating serially anyway. >

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Excerpts from Monty Taylor's message of 2014-02-05 14:57:33 -0800: > On 01/27/2014 11:02 AM, Day, Phil wrote: > >> -Original Message- > >> From: Clint Byrum [mailto:cl...@fewbar.com] > >> Sent: 24 January 2014 21:09 > >> To: openstack-dev

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Excerpts from Day, Phil's message of 2014-01-27 03:02:17 -0800: > > -Original Message- > > From: Clint Byrum [mailto:cl...@fewbar.com] > > Sent: 24 January 2014 21:09 > > To: openstack-dev > > Subject: Re: [openstack-dev] [Nova] bp proposal: discovery of

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Excerpts from Murray, Paul (HP Cloud Services)'s message of 2014-01-27 04:14:44 -0800: > Hi Justin, > > My though process is to go back to basics. To perform discovery there is no > getting away from the fact that you have to start with a well-known address > that your peers can access on the n

Re: [openstack-dev] [heat] Sofware Config progress [for appliances]

thanks > > prasadv > > > > > On Wed, Jan 15, 2014 at 7:53 PM, Steven Dake wrote: > > On 01/14/2014 09:27 PM, Clint Byrum wrote: > > Excerpts from Prasad Vellanki's message of 2014-01-14 18:41:46 -0800: > > Steve > > > > I did not mean to

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

All due respect to Zane who created the scheduler. We simply could not do what we do without it (and I think one of the first things I asked for was parallel create ;). IMO it is the single most confusing thing in Heat whenever one has to deal with it. If we could stick to a threading model instea

Re: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

Curse you Randall for taking first post! +1 Excerpts from Randall Burt's message of 2014-02-09 14:47:39 -0800: > Very +1 > > Original message > From: Steve Baker > Date:02/09/2014 4:41 PM (GMT-06:00) > To: OpenStack Development Mailing List > Subject: [openstack-dev] [heat] Nom

[openstack-dev] [Heat] in-instance update hooks

Hi, so in the previous thread about rolling updates it became clear that having in-instance control over updates is a more fundamental idea than I had previously believed. During an update, Heat does things to servers that may interrupt the server's purpose, and that may cause it to fail subsequent

Re: [openstack-dev] [Heat] in-instance update hooks

Excerpts from Thomas Spatzier's message of 2014-02-11 00:38:53 -0800: > Hi Clint, > > thanks for writing this down. This is a really interesting use case and > feature, also in relation to what was recently discussed on rolling > updates. > > I have a couple of thoughts and questions: > > 1) The

Re: [openstack-dev] [Heat] in-instance update hooks

Excerpts from Steven Dake's message of 2014-02-11 07:19:19 -0800: > On 02/10/2014 10:22 PM, Clint Byrum wrote: > > Hi, so in the previous thread about rolling updates it became clear that > > having in-instance control over updates is a more fundamental idea than > >

Re: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack

Excerpts from Andrey Danin's message of 2014-02-11 08:42:46 -0800: > Hi Openstackers, > > We are working on link aggregation support in Fuel. We wonder what are the > most desirable types of bonding now in datacenters. We had some issues (see > below) with OVS bond in LACP mode, and it turned out

Re: [openstack-dev] [Heat] in-instance update hooks

> are complete. Wait for it. This could be a long long time. > * Destroy or update the node > > Thanks, > Kevin > ____ > From: Clint Byrum [cl...@fewbar.com] > Sent: Tuesday, February 11, 2014 8:13 AM > To: openstack-dev

Re: [openstack-dev] [Heat] [TripleO] in-instance update hooks

Excerpts from James Slagle's message of 2014-02-12 05:18:31 -0800: > On Tue, Feb 11, 2014 at 12:22 AM, Clint Byrum wrote: > > Hi, so in the previous thread about rolling updates it became clear that > > having in-instance control over updates is a more fundamental idea than

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

Excerpts from Julien Vey's message of 2014-02-13 05:18:19 -0800: > Hi, > > I have some concerns about using Zuul in Solum > > I agree gating is a great feature but it is not useful for every project > and as Adrian said, not understood by everyone. > I think many Solum users, and PaaS users in ge

Re: [openstack-dev] "bad" default values in conf files

Excerpts from David Kranz's message of 2014-02-13 06:38:52 -0800: > I was recently bitten by a case where some defaults in keystone.conf > were not appropriate for real deployment, and our puppet modules were > not providing better values > https://bugzilla.redhat.com/show_bug.cgi?id=1064061. J

Re: [openstack-dev] [TripleO] consistency vs packages in TripleO

Excerpts from Robert Collins's message of 2014-02-13 13:27:20 -0800: > So progressing with the 'and folk that want to use packages can' arc, > we're running into some friction. > > I've copied -operators in on this because its very relevant IMO to operators > :) > > So far: > - some packages us

Re: [openstack-dev] "bad" default values in conf files

Excerpts from Jay Pipes's message of 2014-02-13 07:19:18 -0800: > * Identify settings that need to scale with the size of the underlying > VM or host capabilities, and provide patches to the configuration file > comments that clearly indicate a recommended scaling factor. Remember > that folks writ

Re: [openstack-dev] [Openstack-operators] [TripleO] consistency vs packages in TripleO

Excerpts from Dan Prince's message of 2014-02-15 06:05:30 -0800: > > - Original Message - > > From: "Robert Collins" > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Cc: openstack-operat...@lists.openstack.org > > Sent: Friday, February 14, 2014 11:12:12 PM

Re: [openstack-dev] [TripleO] consistency vs packages in TripleO

Excerpts from James Slagle's message of 2014-02-15 13:02:36 -0800: > On Fri, Feb 14, 2014 at 11:12 PM, Robert Collins > wrote: > > On 15 February 2014 08:42, Dan Prince wrote: > >> > > > >> Option B is we make our job easy by strong arming everyone into the same > >> defaults of our "upstream" c

Re: [openstack-dev] [Murano] Need a new DSL for Murano

Excerpts from Alexander Tivelkov's message of 2014-02-14 18:17:10 -0800: > Hi folks, > > Murano matures, and we are getting more and more feedback from our early > adopters. The overall reception is very positive, but at the same time > there are some complaints as well. By now the most significan

[openstack-dev] [Heat] [TripleO] Better handling of lists in Heat - a proposal to add a map function

Since picking up Heat and trying to think about how to express clusters of things, I've been troubled by how poorly the CFN language supports using lists. There has always been the Fn::Select function for dereferencing arrays and maps, and recently we added a nice enhancement to HOT to allow refere

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

Excerpts from Imre Farkas's message of 2014-02-20 15:24:17 +: > On 02/20/2014 03:57 PM, Tomas Sedovic wrote: > > On 20/02/14 15:41, Radomir Dopieralski wrote: > >> On 20/02/14 15:00, Tomas Sedovic wrote: > >> > >>> Are we even sure we need to store the passwords in the first place? All > >>> th

Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

Excerpts from Alexander Tivelkov's message of 2014-02-28 03:52:52 -0800: > Hi Charles, > > If you are looking for the analogues of Juju in OpenStack, you probably may > take a look at Murano Project [1]. It is an application catalog backed with > a powerful workflow execution engine, which is buil

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

Excerpts from Jay Pipes's message of 2014-02-28 14:26:26 -0800: > On Fri, 2014-02-28 at 13:10 -0800, Mark Washenberger wrote: > > > > On Fri, Feb 28, 2014 at 10:39 AM, Henry Nash > > wrote: > > Hi Mark, > > > > > > So we would not modify any existing IDs, so no m

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

Excerpts from Robert Collins's message of 2014-03-01 14:26:57 -0800: > On 1 March 2014 13:28, Clint Byrum wrote: > > > +1. A Keystone record belongs to Keystone, and it should have a Keystone > > ID. External records that are linked should be linked separately. > >

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

Excerpts from Adam Young's message of 2014-03-03 23:06:58 -0800: > On 03/03/2014 02:32 PM, Jay Pipes wrote: > > On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote: > >> On Mar 3, 2014, at 6:48 AM, Jay Pipes wrote: > >> > >>> On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote: >

Re: [openstack-dev] [heat]Policy on upgades required config changes

Excerpts from Steven Hardy's message of 2014-03-04 09:39:21 -0800: > Hi all, > > As some of you know, I've been working on the instance-users blueprint[1]. > > This blueprint implementation requires three new items to be added to the > heat.conf, or some resources (those which create keystone use

Re: [openstack-dev] [all] Scale out bug-triage by making it easier for people to contribute

Excerpts from Flavio Percoco's message of 2014-11-17 08:46:19 -0800: > Greetings, > > Regardless of how big/small bugs backlog is for each project, I > believe this is a common, annoying and difficult problem. At the oslo > meeting today, we're talking about how to address our bug triage > process

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

Excerpts from Mike Bayer's message of 2014-11-19 10:05:35 -0800: > > > On Nov 18, 2014, at 1:38 PM, Eugene Nikanorov > > wrote: > > > > Hi neutron folks, > > > > There is an ongoing effort to refactor some neutron DB logic to be > > compatible with galera/mysql which doesn't support locking

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

Excerpts from Anant Patil's message of 2014-11-30 23:02:29 -0800: > On 27-Nov-14 18:03, Murugan, Visnusaran wrote: > > Hi Zane, > > > > > > > > At this stage our implementation (as mentioned in wiki > > ) achieves your > > design goals. >

[openstack-dev] [TripleO] mid-cycle details final draft

Hello! I've received confirmation that our venue, the HP offices in downtown Seattle, will be available for the most-often-preferred least-often-cannot week of Feb 16 - 20. Our venue has a maximum of 20 participants, but I only have 16 possible attendees now. Please add yourself to that list _now_

Re: [openstack-dev] [Heat] Using Job Queues for timeout ops

Excerpts from Zane Bitter's message of 2014-12-01 13:05:42 -0800: > On 13/11/14 13:59, Clint Byrum wrote: > > I'm not sure we have the same understanding of AMQP, so hopefully we can > > clarify here. This stackoverflow answer echoes my understanding: > > > &g

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

Excerpts from James Slagle's message of 2014-11-28 11:27:20 -0800: > On Thu, Nov 27, 2014 at 1:29 PM, Sullivan, Jon Paul > wrote: > >> -Original Message- > >> From: Ben Nemec [mailto:openst...@nemebean.com] > >> Sent: 26 November 2014 17:03 > >> To: OpenStack Development Mailing List (not

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

Excerpts from Danny Choi (dannchoi)'s message of 2014-12-02 08:34:07 -0800: > Hi Andrea, > > Though both interfaces come up, only one will response to the ping from the > neutron router. > When I disable it, then the second one will response to ping. > So it looks like only one interface is usefu

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

Excerpts from Anant Patil's message of 2014-12-02 10:37:31 -0800: > Yes, that's the synchronization block for which we use the stack lock. > Currently, a thread spin waits to acquire the lock to enter this critical > section. > > I don't really know how to do application level transaction. Is ther

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

Excerpts from Ian Wienand's message of 2014-12-02 11:22:31 -0800: > On 12/02/2014 03:46 PM, Clint Byrum wrote: > > 1) Conform all o-r-c scripts to the logging standards we have in > > OpenStack, or write new standards for diskimage-builder and conform > > them to th

<    1   2   3   4   5   6   7   8   9   10   >