Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

Hi Vish, I’m jumping in slightly late on this, but I also have an interest in this. I’m going to preface this by saying that I have not read this whole thread yet, so I apologize if I repeat things, say anything that is addressed by previous posts, or doesn’t jive with what you’re looking for.

Re: [openstack-dev] [Ironic] January review redux

> > So, I'd like to nominate the following two additions to the ironic-core > team: > > Max Lobur > > https://review.openstack.org/#/q/reviewer:mlobur%2540mirantis.com+project:openstack/ironic,n,z > > Roman Prykhodchenko > > https://review.openstack.org/#/q/reviewer:rprikhodchenko%2540mirantis.com+

Re: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because of a nova patch

On Tue, Feb 04 2014, Joe Gordon wrote: > Ceilometer running a plugin in nova is bad (for all the reasons > previously discussed), Well, I partially disagree. Are you saying that nobody is allowed to run a plugin in Nova? So what are these plugins in the first place? Or if you're saying that Ceilo

Re: [openstack-dev] [TripleO] [Ironic] mid-cycle meetup?

On 5 February 2014 11:02, Mark Washenberger wrote: > I'd like to attend as well, since it is close for me and some upcoming > Glance efforts might be relevant. But I'm definitely more of a "chicken" > than a "pig" for this gathering so let me know if that kind of participation > is not really desi

[openstack-dev] [rally] Proposing changes in Rally core team

Hi stackers, I would like to: 1) Nominate Hugh Saunders to Rally core, he is doing a lot of good reviews (and always testing patches=) ): http://stackalytics.com/report/reviews/rally/30 2) Remove Alexei from core team, because unfortunately he is not able to work on Rally at this moment. Thank y

Re: [openstack-dev] [Ironic] January review redux

On 02/04/2014 09:42 PM, Devananda van der Veen wrote: So, I'd like to nominate the following two additions to the ironic-core team: Max Lobur https://review.openstack.org/#/q/reviewer:mlobur%2540mirantis.com+project:openstack/ironic,n,z Roman Prykhodchenko https://review.openstack.org/#/q/rev

Re: [openstack-dev] [TripleO] [Tuskar] [UX] Infrastructure Management UI - Icehouse scoped wireframes

On 05/02/14 03:58, Jaromir Coufal wrote: Hi to everybody, based on the feedback from last week [0] I incorporated changes in the wireframes so that we keep them up to date with latest decisions: http://people.redhat.com/~jcoufal/openstack/tripleo/2014-02-05_tripleo-ui-icehouse.pdf Changes: *

Re: [openstack-dev] [rally] Proposing changes in Rally core team

+1 for Hugh, but IMO no need to rush with Alexei's removalHi stackers, I would like to:1) Nominate Hugh Saunders to Rally core, he is doing a lot of good reviews (and always testing patches=) ):http://stackalytics.com/report/reviews/rally/30 2) Remove Alexei from core team, because unfortunately h

Re: [openstack-dev] [Neutron] backporting database migrations to stable/havana

Ralf Haferkamp wrote: > I am currently trying to backport the fix for > https://launchpad.net/bugs/1254246 to stable/havana. The current state of that > is here: https://review.openstack.org/#/c/68929/ > > However, the fix requires a database migration to be applied (to add a unique > constraint t

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

Hi Vish, You're approach looks very interesting. I especially like the idea of 'walking the tree of parent projects, to construct the set of roles'. Here are some issues that came to my mind: Regarding policy rules enforcement: Considering the following projects: * orga * orga.projecta * orga

Re: [openstack-dev] [Nova] os-migrateLive not working with neutron in Havana (or apparently Grizzly)

On 4 February 2014 19:16, Jonathan Proulx wrote: > HI all, > > Trying to get a little love on bug > https://bugs.launchpad.net/nova/+bug/1227836 > > Short version is the instance migrates, but there's an RPC time out > that keeps nova thinking it's still on the old node mid-migration. > Informal

Re: [openstack-dev] [Ironic] January review redux

+1 for both:) On Wed, Feb 5, 2014 at 6:08 PM, Yuriy Zveryanskyy wrote: > On 02/04/2014 09:42 PM, Devananda van der Veen wrote: > > So, I'd like to nominate the following two additions to the ironic-core > team: > > Max Lobur > https://review.openstack.org/#/q/reviewer:mlobur%2540mirantis.com+pro

Re: [openstack-dev] [Openstack-docs] Conventions on naming

Steve Gordon wrote: >> From: "Anne Gentle" >> Based on today's Technical Committee meeting and conversations with the >> OpenStack board members, I need to change our Conventions for service names >> at >> https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names >> . >>

Re: [openstack-dev] [rally] Proposing changes in Rally core team

+1 for Hugh, he's doing excellent job moving the project forward. -- Best regards, Oleg Gelbukh On Wed, Feb 5, 2014 at 2:22 PM, Sergey Skripnick wrote: > > +1 for Hugh, but IMO no need to rush with Alexei's removal > > Hi stackers, > > I would like to: > > 1) Nominate Hugh Saunders to Rally cor

Re: [openstack-dev] [TripleO] [Tuskar] [UX] Infrastructure Management UI - Icehouse scoped wireframes

Hi Tomas, thanks for the questions, I am replying inline. On 2014/05/02 11:19, Tomas Sedovic wrote: On 05/02/14 03:58, Jaromir Coufal wrote: Hi to everybody, based on the feedback from last week [0] I incorporated changes in the wireframes so that we keep them up to date with latest decisions

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

Hi, Chris Behrens wrote: > Interesting thread. I have been working on a side project that is a > gevent/eventlet replacement [1] that focuses on thread-safety and > performance. This came about because of an outstanding bug we have with > eventlet not being Thread safe. (We cannot safely enable th

Re: [openstack-dev] [Neutron] backporting database migrations to stable/havana

On Wed, Feb 05, 2014 at 11:31:55AM +0100, Thierry Carrez wrote: > Ralf Haferkamp wrote: > > I am currently trying to backport the fix for > > https://launchpad.net/bugs/1254246 to stable/havana. The current state of > > that > > is here: https://review.openstack.org/#/c/68929/ > > > > However, th

[openstack-dev] Agenda for todays ML2 Weekly meeting

Hi- Kindly share me the agenda for today weekly meeting on Neutron/ML2. Best Regards, -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

" By the way, I'm wondering if it wouldn't be DRYer to centralize the RBAC and Quotas logic in a unique service (Keystone?). Openstack services (Nova, Cinder, ...) would just have to ask this centralized access management service whether an action is authorized for a given token?" I agree on ce

Re: [openstack-dev] [TripleO] [Tuskar] [UX] Infrastructure Management UI - Icehouse scoped wireframes

1. Are we doing node tags (page 4) for the first iteration? Where are they going to live? Yes, it's very easy to do, already part of Ironic. Cool! 2. There are multiple node profiles per role on pages 11, 12, 17. Is that just an oversight or do you intend on keeping those in? I though the

Re: [openstack-dev] [rally] Proposing changes in Rally core team

+1 for Hugh On Wed, Feb 5, 2014 at 2:22 PM, Sergey Skripnick wrote: > > +1 for Hugh, but IMO no need to rush with Alexei's removal > > Hi stackers, > > I would like to: > > 1) Nominate Hugh Saunders to Rally core, he is doing a lot of good reviews > (and always testing patches=) ): > http://stac

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

On Feb 5, 2014, at 2:38 AM, Florent Flament wrote: > Hi Vish, > > You're approach looks very interesting. I especially like the idea of > 'walking the tree of parent projects, to construct the set of roles'. > > Here are some issues that came to my mind: > > > Regarding policy rules enforc

[openstack-dev] [Climate] 0.1.0 release

Hi, folks! Today Climate has been released first time and I'm really glad to say that :) This release implements following use cases: - User wants to reserve virtual machine and use it later. He/she asks Nova to create server, passing special hints, describing information like lease sta

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

On Feb 5, 2014, at 12:27 AM, Chris Behrens wrote: > > Hi Vish, > > I’m jumping in slightly late on this, but I also have an interest in this. > I’m going to preface this by saying that I have not read this whole thread > yet, so I apologize if I repeat things, say anything that is addressed

Re: [openstack-dev] [Climate] 0.1.0 release

Great progress! My congratulations. On Wed, Feb 5, 2014 at 3:36 PM, Dina Belova wrote: > Hi, folks! > > Today Climate has been released first time and I'm really glad to say that > :) > > This release implements following use cases: > >- User wants to reserve virtual machine and use it lat

Re: [openstack-dev] [Neutron] backporting database migrations to stable/havana

Hi, On Tue, Feb 04, 2014 at 12:36:16PM -0500, Miguel Angel Ajo Pelayo wrote: > > > Hi Ralf, I see we're on the same boat for this. > >It seems that a database migration introduces complications > for future upgrades. It's not an easy path. > >My aim when I started this backport was try

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

victor stinner wrote: > [...] > The problem is that the asyncio module was written for Python 3.3, whereas > OpenStack is not fully Python 3 compatible (yet). To easy the transition I > have ported asyncio on Python 2, it's the new Trollis project which supports > Python 2.6-3.4: >https://bi

Re: [openstack-dev] [OpenStack-Infra] [cinder][neutron][nova][3rd party testing] Gerrit Jenkins plugin will not fulfill requirements of 3rd party testing

Hi Jay, it's really very easy to setup Zuul for it (we're using one for Savanna CI). There are some useful links: * check pipeline as an example of zuul layout configuration - https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/zuul/layout.yaml#L5 * zuul docs -

Re: [openstack-dev] [Climate] 0.1.0 release

Congrats to all Climate team members who made it happen, great job! -- Oleg Gelbukh On Wed, Feb 5, 2014 at 3:36 PM, Dina Belova wrote: > Hi, folks! > > Today Climate has been released first time and I'm really glad to say that > :) > > This release implements following use cases: > >- User

Re: [openstack-dev] savann-ci, Re: [savanna] Alembic migrations and absence of DROP column in sqlite

Agreed, let's move on to the MySQL for savanna-ci to run integration tests against production-like DB. On Wed, Feb 5, 2014 at 1:54 AM, Andrew Lazarev wrote: > Since sqlite is not in the list of "databases that would be used in > production", CI should use other DB for testing. > > Andrew. > > >

Re: [openstack-dev] [savanna] Specific job type for streaming mapreduce? (and someday pipes)

I like the dot-separated name. There are several reasons for it: * it'll not require changes in all Savanna subprojects; * eventually we'd like to use not only Oozie for EDP (for example, if we'll support Twitter Storm) and this new tools could require additional 'subtypes'. Thanks for catching t

Re: [openstack-dev] [savanna] Undoing a change in the alembic migrations

Just to clarify, new migration scripts should be added. You can find details on how to do it here - https://github.com/openstack/savanna/blob/master/savanna/db/migration/alembic_migrations/README On Thu, Jan 30, 2014 at 8:16 AM, Alexander Ignatov wrote: > Yes, you need create new migration scrip

Re: [openstack-dev] savann-ci, Re: [savanna] Alembic migrations and absence of DROP column in sqlite

I'm currently working on moving on the MySQL for savanna-ci On Wed, Feb 5, 2014 at 3:53 PM, Sergey Lukjanov wrote: > Agreed, let's move on to the MySQL for savanna-ci to run integration tests > against production-like DB. > > > On Wed, Feb 5, 2014 at 1:54 AM, Andrew Lazarev wrote: > >> Since sql

Re: [openstack-dev] [Openstack-docs] Conventions on naming

On Wed, 2014-02-05 at 11:52 +0100, Thierry Carrez wrote: > Steve Gordon wrote: > >> From: "Anne Gentle" > >> Based on today's Technical Committee meeting and conversations with the > >> OpenStack board members, I need to change our Conventions for service names > >> at > >> https://wiki.openstack.

Re: [openstack-dev] savann-ci, Re: [savanna] Alembic migrations and absence of DROP column in sqlite

Hi I'm currently working on moving on the MySQL for savanna-ci We are working on same task in ceilometer so maybe you could use some of our patches as reference: https://review.openstack.org/#/c/59489/ https://review.openstack.org/#/c/63049/ Regards, Alexei On 02/05/2014 02:06 PM, Sergey Ko

Re: [openstack-dev] [rally] Proposing changes in Rally core team

but IMO no need to rush with Alexei's removal I'm not working actively on rally at this moment and already far behind of the current code base. Cause of this I'm ok to step down from core. Regards, On 02/05/2014 01:17 PM, Ilya Kharin wrote: +1 for Hugh On Wed, Feb 5, 2014 at 2:22 PM, Sergey

Re: [openstack-dev] [rally] Proposing changes in Rally core team

Hugh, welcome to Rally core team! Best regards, Boris Pavlovic On Wed, Feb 5, 2014 at 3:17 PM, Ilya Kharin wrote: > +1 for Hugh > > > On Wed, Feb 5, 2014 at 2:22 PM, Sergey Skripnick > wrote: > >> >> +1 for Hugh, but IMO no need to rush with Alexei's removal >> >> Hi stackers, >> >> I woul

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

Hi, Thierry Carrez wrote: > > The problem is that the asyncio module was written for Python 3.3, whereas > > OpenStack is not fully Python 3 compatible (yet). To easy the transition I > > have ported asyncio on Python 2, it's the new Trollis project which > > supports Python 2.6-3.4: > >https:

Re: [openstack-dev] [rally] Proposing changes in Rally core team

Thanks Boris, Sergey, Oleg & Ilya, Rally can be hard to keep up with (rebase, rebase, rebase, merge) but that development pace also makes it exciting, each time you run rally, something will have improved! This morning I was awed by Pierre's atomic actions patches - great! Thanks for appointing me

Re: [openstack-dev] [rally] Proposing changes in Rally core team

Thank you hugh and congratulations for your new assignment as core reviewer, you're doing a great job! Regards, Pierre. 2014-02-05 Hugh Saunders : > Thanks Boris, Sergey, Oleg & Ilya, > Rally can be hard to keep up with (rebase, rebase, rebase, merge) but that > development pace also makes it ex

Re: [openstack-dev] [savanna] Specific job type for streaming mapreduce? (and someday pipes)

Okay, Thanks. I'll make a draft CR that sets up Savanna for dotted names, and one that uses dotted names with streaming. Best, Trevor On Wed, 2014-02-05 at 15:58 +0400, Sergey Lukjanov wrote: > I like the dot-separated name. There are several reasons for it: > > > * it'll not require change

Re: [openstack-dev] [Openstack-docs] Conventions on naming

On 02/05/2014 01:09 PM, Mark McLoughlin wrote: > On Wed, 2014-02-05 at 11:52 +0100, Thierry Carrez wrote: >> Steve Gordon wrote: From: "Anne Gentle" Based on today's Technical Committee meeting and conversations with the OpenStack board members, I need to change our Conventions for

Re: [openstack-dev] [neutron][ml2] Port binding information, transactions, and concurrency

Bob, this is fantastic, I really appreciate all the detail. A couple of questions ... On Wed, Feb 05, at 2:16 am, Robert Kukura wrote: > A couple of interrelated issues with the ML2 plugin's port binding have > been discussed over the past several months in the weekly ML2 meetings. > These effec

Re: [openstack-dev] savann-ci, Re: [savanna] Alembic migrations and absence of DROP column in sqlite

It's about integration tests that aren't db-specific, so, just DATABASE/connection should be fixed ;) On Wed, Feb 5, 2014 at 4:33 PM, Alexei Kornienko wrote: > Hi > > > I'm currently working on moving on the MySQL for savanna-ci > > We are working on same task in ceilometer so maybe you could

[openstack-dev] [TripleO][Tuskar] Icehouse Requirements

Hi, In parallel to Jarda's updated wireframes, and based on various discussions over the past weeks, here are the updated Tuskar requirements for Icehouse: https://wiki.openstack.org/wiki/TripleO/TuskarIcehouseRequirements Any feedback is appreciated. Thanks! Tzu-Mainn Chen _

Re: [openstack-dev] [savanna] Choosing provisioning engine during cluster launch

It sounds little useful for dev/testing, I'm not really think that it's needed, but not -1 such addition to the REST API. On Thu, Jan 30, 2014 at 7:52 PM, Trevor McKay wrote: > My mistake, it's already there. I missed the distinction between set on > startup and set per cluster. > > Trev > > O

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

On 02/05/14 at 03:30am, Vishvananda Ishaya wrote: On Feb 5, 2014, at 2:38 AM, Florent Flament wrote: Hi Vish, You're approach looks very interesting. I especially like the idea of 'walking the tree of parent projects, to construct the set of roles'. Here are some issues that came to my mi

Re: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because of a nova patch

> We don't have to add a new notification, but we have to add some > new datas in the nova notifications. At least for the delete > instance notification to remove the ceilometer nova notifier. > > A while ago, I have registered a blueprint that explains which > datas are missing in the current no

Re: [openstack-dev] olso.config error on running Devstack

On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > On 2014-01-08 12:14, Doug Hellmann wrote: > > > > > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > >> On 2014-01-08 11:16, Sean Dague wrote: >> >>> On 01/08/2014 12:06 PM, Doug Hellmann wrote: >>> >>> Yeah, that's what made me start

[openstack-dev] update an instance IP address in openstack

I am writing a virtualization driver on my own. And i need to change the instance public IP address in the code? Is there any way I can go about it? And also, how do I use the nova db package and also add a column into the nova instance table? is there any way? Any help is highly appreciated. Rega

Re: [openstack-dev] The simplified blueprint for PCI extra attributes and SR-IOV NIC blueprint

Hi John and all, Yunhong's email mentioned about the SR-IOV NIC support BP: https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov I'd appreciate your consideration of the approval of both BPs so that we can have SR-IOV NIC support in Icehouse. Thanks, Robert On 2/4/14 1:36 AM, "Jia

Re: [openstack-dev] about the bp cpu-entitlement

Re: [openstack-dev] about the bp cpu-entitlement Oshrit Feder to: openstack-dev 05/02/2014 03:58 PM Hi Sahid, Thank you for your interest in the cpu entitlement feature. As Paul mentioned, we are joining the extensible resource effort and will integrate it on top of it. Will be glad to ke

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

On Tue, Feb 4, 2014 at 6:39 PM, Joe Gordon wrote: > On Tue, Feb 4, 2014 at 8:19 AM, Sean Dague wrote: > > On 02/05/2014 12:37 AM, Mark McLoughlin wrote: > >> On Mon, 2014-01-13 at 16:49 +, Sahid Ferdjaoui wrote: > >>> Hello all, > >>> > >>> It looks 100% of the pep8 gate for nova is failing

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

First, I don't think RollingUpdatePattern and CanaryUpdatePattern should be 2 different entities. The second just looks like a parametrization of the first (growth_factor=1?). Perhaps they can just be one. Until I find parameters which would need to mean something different, I'll just use Upda

Re: [openstack-dev] [TripleO] [Tuskar] [UX] Infrastructure Management UI - Icehouse scoped wireframes

Hi Steve! I would say that we finally got to sort of stabilized state of wireframes [0]. I am sure there will appear slight changes (as it is always like this), but there shouldn't be bigger change of direction. We are looking forward to see some high-fidelity mockups if you are willing to he

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

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. I have to say that even in general, this whole idea about applying update policies to

Re: [openstack-dev] [neutron][ml2] Port binding information, transactions, and concurrency

Hi, thanks for this great proposal On Wed, Feb 5, 2014 at 3:10 PM, Henry Gessau wrote: > Bob, this is fantastic, I really appreciate all the detail. A couple of > questions ... > > On Wed, Feb 05, at 2:16 am, Robert Kukura wrote: > >> A couple of interrelated issues with the ML2 plugin's port

[openstack-dev] [nova] Reconfiguring devices when boot from instance snapshot

There is a task - device reconfiguration when boot instance from instance snapshot. For example, one may want to change shutdown behaviour by nova boot ... --image --block_device device=/dev/vda,shutdown=false when originally shutdown attribute for /dev/vda is 'remove' in the instance snapshot. N

Re: [openstack-dev] Agenda for todays ML2 Weekly meeting

On 02/05/2014 06:06 AM, trinath.soman...@freescale.com wrote: > Hi- > > > > Kindly share me the agenda for today weekly meeting on Neutron/ML2. I just updated https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_February_5.2C_2014. Mestery has a conflict for today's meeting. -Bob > > > >

[openstack-dev] [Trove] Backup/Restore encryption/decryption issue

Goodday, OpenStack DВaaS community. I'd like to start conversation about guestagent security issue related to backup/restore process. Trove guestagent service uses AES with 256 bit key (in CBC mode) [1] to encrypt backups which are stored at predefined Swift container. As you can see

Re: [openstack-dev] [neutron][ml2] Port binding information, transactions, and concurrency

On 02/05/2014 09:10 AM, Henry Gessau wrote: > Bob, this is fantastic, I really appreciate all the detail. A couple of > questions ... > > On Wed, Feb 05, at 2:16 am, Robert Kukura wrote: > >> A couple of interrelated issues with the ML2 plugin's port binding have >> been discussed over the past

[openstack-dev] [PTL] Designating "required use" upstream code

(This email is mostly directed to PTLs for programs that include one integrated project) The DefCore subcommittee from the OpenStack board of directors asked the Technical Committee yesterday about which code sections in each integrated project should be "designated sections" in the sense of [1] (

Re: [openstack-dev] [Openstack-docs] Conventions on naming

- Original Message - > From: "Andreas Jaeger" > To: "Mark McLoughlin" , "OpenStack Development Mailing > List (not for usage questions)" > > Cc: "Jonathan Bryce" > Sent: Wednesday, February 5, 2014 9:17:39 AM > Subject: Re: [openstack-dev] [Openstack-docs] Conventions on naming > > On

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

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-level of the project has been sufficient to declare the license chose

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On 2014/05/02 15:27, Tzu-Mainn Chen wrote: Hi, In parallel to Jarda's updated wireframes, and based on various discussions over the past weeks, here are the updated Tuskar requirements for Icehouse: https://wiki.openstack.org/wiki/TripleO/TuskarIcehouseRequirements Any feedback is appreciated

[openstack-dev] [Horizon] RFC - Suggestion for switching from Less to Sass (Bootstrap 3 & Sass support)

Dear Horizoners, in last days there were couple of interesting discussions about updating to Bootstrap 3. In this e-mail, I would love to give a small summary and propose a solution for us. As Bootstrap was heavily dependent on Less, when we got rid of node.js we started to use lesscpy. Unfo

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 > >>> time has come to get serious about imp

Re: [openstack-dev] [OpenStack-Infra] [cinder][neutron][nova][3rd party testing] Gerrit Jenkins plugin will not fulfill requirements of 3rd party testing

On Wed, 2014-02-05 at 15:50 +0400, Sergey Lukjanov wrote: > Hi Jay, > > it's really very easy to setup Zuul for it (we're using one for > Savanna CI). Yes, I set up Zuul for AT&T's gate system, thx. > There are some useful links: > > * check pipeline as an example of zuul layout configuration >

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

On Wed, Feb 5, 2014 at 4:20 PM, Doug Hellmann wrote: > Including the config file in either the developer documentation or the > packaging build makes more sense. I'm still worried that adding it to the > sdist generation means you would have to have a lot of tools installed just > to make the sdis

[openstack-dev] [Manila] Modularity of generic driver (network mediated)

Hi, The first prototype of the multi-tenant capable GlusterFS driver would piggyback on the generic driver, which implements the network plumbing model [1]. We'd have NFS-Ganesha server running on the service VM. The Ganesha server would mediate access to the GlusterFS backend (or any other Gan

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

On Wed, 2014-02-05 at 16:29 +, Greg Hill wrote: > 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. Meh, probably just habit and copy/paste behavior. > In my past exp

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

On Wed, Feb 05, 2014 at 04:29:20PM +, Greg Hill wrote: > 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-level

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

It's nice when someone removes a file from the project. They get license information transmitted automatically without needing to do extra work. > On Feb 5, 2014, at 10:46 AM, Jay Pipes wrote: > >> On Wed, 2014-02-05 at 16:29 +, Greg Hill wrote: >> I'm new, so I'm sure there's some history

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

On Wed, Feb 5, 2014 at 11:40 AM, Chmouel Boudjnah wrote: > > On Wed, Feb 5, 2014 at 4:20 PM, Doug Hellmann > wrote: > >> Including the config file in either the developer documentation or the >> packaging build makes more sense. I'm still worried that adding it to the >> sdist generation means yo

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On Wed, Feb 5, 2014 at 11:22 AM, Thierry Carrez wrote: > (This email is mostly directed to PTLs for programs that include one > integrated project) > > The DefCore subcommittee from the OpenStack board of directors asked the > Technical Committee yesterday about which code sections in each > integ

Re: [openstack-dev] olso.config error on running Devstack

On 2014-02-05 09:05, Doug Hellmann wrote: > On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > > On 2014-01-08 12:14, Doug Hellmann wrote: > > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > > On 2014-01-08 11:16, Sean Dague wrote: > On 01/08/2014 12:06 PM, Doug Hellmann wrote: > >

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

On Wed, Feb 05, 2014 at 05:40:13PM +0100, Chmouel Boudjnah wrote: > On Wed, Feb 5, 2014 at 4:20 PM, Doug Hellmann > wrote: > > > Including the config file in either the developer documentation or the > > packaging build makes more sense. I'm still worried that adding it to the > > sdist generation

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On 02/05/2014 11:22 AM, Thierry Carrez wrote: > (This email is mostly directed to PTLs for programs that include one > integrated project) > > The DefCore subcommittee from the OpenStack board of directors asked the > Technical Committee yesterday about which code sections in each > integrated pro

Re: [openstack-dev] olso.config error on running Devstack

On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: > On 2014-02-05 09:05, Doug Hellmann wrote: > > > On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > >> On 2014-01-08 12:14, Doug Hellmann wrote: >> >> >> >> On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: >> >>> On 2014-01-08 11:16, Sean Dag

[openstack-dev] [Openstack-dev] [Oslo] [Fuel] [Fuel-dev] Openstack services should support SIGHUP signal

Hi, stackers. I believe Openstack services from all projects should support SIGHUP for effective log/config files handling w/o unnecessary restarts. (See https://bugs.launchpad.net/oslo/+bug/1276694) 'Smooth reloads'(kill -HUP) are much better than 'disturbing restarts', aren't they? -- Best reg

Re: [openstack-dev] savann-ci, Re: [savanna] Alembic migrations and absence of DROP column in sqlite

Hi Sergey, Is there a bug or a blueprint for this? I did a quick search but didn't see one. Thanks, Trevor On Wed, 2014-02-05 at 16:06 +0400, Sergey Kolekonov wrote: > I'm currently working on moving on the MySQL for savanna-ci > > > On Wed, Feb 5, 2014 at 3:53 PM, Sergey Lukjanov > wrote

Re: [openstack-dev] olso.config error on running Devstack

Avoiding namespace packages is a good idea in general. At least until Python 3.whatever is baseline. > On Feb 5, 2014, at 10:58 AM, Doug Hellmann > wrote: > > > > >> On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: >>> On 2014-02-05 09:05, Doug Hellmann wrote: >>> >>> On Tue, Feb

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

On Wed, Feb 5, 2014 at 8:29 AM, Greg Hill wrote: > 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-level > of th

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On 02/05/2014 11:55 AM, Doug Hellmann wrote: > > > > On Wed, Feb 5, 2014 at 11:22 AM, Thierry Carrez > wrote: > > (This email is mostly directed to PTLs for programs that include one > integrated project) > > The DefCore subcommittee from the OpenStac

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] why do we put a license in every file?

On 02/05/2014 11:53 AM, Daniel P. Berrange wrote: > On Wed, Feb 05, 2014 at 04:29:20PM +, Greg Hill wrote: >> 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 pas

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On Wed, 2014-02-05 at 17:22 +0100, Thierry Carrez wrote: > (This email is mostly directed to PTLs for programs that include one > integrated project) > > The DefCore subcommittee from the OpenStack board of directors asked the > Technical Committee yesterday about which code sections in each > int

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

On 04/02/14 20:34, 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. I have to say that even in general, this whole idea about applying update policies to non-

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

On Wed, 2014-02-05 at 16:29 +, Greg Hill wrote: > 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-level of the

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

On Wed, Feb 05, 2014 at 11:56:35AM -0500, Doug Hellmann wrote: > On Wed, Feb 5, 2014 at 11:40 AM, Chmouel Boudjnah wrote: > > > > > On Wed, Feb 5, 2014 at 4:20 PM, Doug Hellmann > > wrote: > > > >> Including the config file in either the developer documentation or the > >> packaging build makes m

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

Hi Chris, Looking at your requirements, seems my solution (see attached email) is pretty much aligned. What I am trying to propose is 1. One root domain as owner of "virtual cloud". Logically linked to "n" leaf domains. 2. All leaf domains falls under admin boundary of "virtual cloud" owner. 3

Re: [openstack-dev] [Openstack-docs] Conventions on naming

On Feb 5, 2014, at 10:18 AM, Steve Gordon wrote: > - Original Message - >> From: "Andreas Jaeger" >> To: "Mark McLoughlin" , "OpenStack Development Mailing >> List (not for usage questions)" >> >> Cc: "Jonathan Bryce" >> Sent: Wednesday, February 5, 2014 9:17:39 AM >> Subject: Re: [op

Re: [openstack-dev] [Openstack-dev] [Oslo] [Fuel] [Fuel-dev] Openstack services should support SIGHUP signal

On 2014-02-05 10:58, Bogdan Dobrelya wrote: Hi, stackers. I believe Openstack services from all projects should support SIGHUP for effective log/config files handling w/o unnecessary restarts. (See https://bugs.launchpad.net/oslo/+bug/1276694) 'Smooth reloads'(kill -HUP) are much better than '

Re: [openstack-dev] [Horizon] RFC - Suggestion for switching from Less to Sass (Bootstrap 3 & Sass support)

On Wed 05 Feb 2014 09:32:54 AM MST, Jaromir Coufal wrote: > Dear Horizoners, > > in last days there were couple of interesting discussions about > updating to Bootstrap 3. In this e-mail, I would love to give a small > summary and propose a solution for us. > > As Bootstrap was heavily dependent on

Re: [openstack-dev] [PTL] Designating "required use" upstream code

Russell Bryant wrote: > Who gets final say if there's strong disagreement between a PTL and the > TC? Hopefully this won't matter, but it may be useful to go ahead and > clear this up front. I suspect that would be as usual. PTL has final say over his project matters. The TC can just wield the nu

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On Feb 5, 2014, at 11:12 AM, Mark McLoughlin wrote: > I don't have a big issue with the way the Foundation currently enforces > "you must use the code" - anyone who signs a trademark agreement with > the Foundation agrees to "include the entirety of" Nova's code. That's > very vague, but I assume

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On Wed, Feb 5, 2014 at 8:22 AM, Thierry Carrez wrote: > (This email is mostly directed to PTLs for programs that include one > integrated project) > > The DefCore subcommittee from the OpenStack board of directors asked the > Technical Committee yesterday about which code sections in each > integr

Re: [openstack-dev] [PTL] Designating "required use" upstream code

On 02/05/2014 12:54 PM, Jonathan Bryce wrote: > On Feb 5, 2014, at 11:12 AM, Mark McLoughlin wrote: > >> I don't have a big issue with the way the Foundation currently enforces >> "you must use the code" - anyone who signs a trademark agreement with >> the Foundation agrees to "include the entire

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

On 05/02/14 11:39, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2014-02-04 16:14:09 -0800: On 03/02/14 17:09, Clint Byrum wrote: UpdatePolicy in cfn is a single string, and causes very generic rolling Huh? http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribu

  1   2   >