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

On 04/22/2016 04:27 PM, Ed Leafe wrote: OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did it anyway.

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

- Mail original - > De: "Edward Leafe" > À: "OpenStack Development Mailing List (not for usage questions)" > > Envoyé: Samedi 23 Avril 2016 19:12:03 > Objet: Re: [openstack-dev] [nova] Distributed Database > > On Apr 23, 2016, at

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Magnum is not a COE installer. It offers multi tenancy from the ground up, is well integrated with OpenStack services, and more COE features pre-configured than you would get with an ordinary stock deployment. For example, magnum offers integration with keystone that allows developer

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

On 04/22/2016 04:40 PM, Davanum Srinivas wrote: Ed, fyi, i just got a ping about this effort: https://github.com/BeyondTheClouds/BeyondTheClouds.github.io/raw/master/DOCS/PAPERS/2015/nova-description/BTC-DISCOVERY-Overview.pdf https://github.com/BeyondTheClouds/rome

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On Apr 23, 2016, at 3:10 PM, Jay Pipes wrote: > > Looking forward to arriving in Austin so that I can buy you a beer, Amrith, > and have a high-bandwidth conversation about how you're wrong. :P Beer is a great addition to any conversation! -- Ed

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

I'm certainly more interested in the push model, if only to create parity with azure, AWS and Google. I suggest we start the BYOK discussions on Wednesday focusing on push. If there's an interest in shifting discussion to the pull model in the Thursday session then I have no objection to that,

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On Apr 23, 2016, at 3:10 PM, Jay Pipes > wrote: > BTW, note to Ed Leafe... unless your distributed data store supports > transactional semantics, you can't use a distributed data store for these > types of solutions. Instead, you will need to

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

On Apr 23, 2016, at 10:10 AM, Thierry Carrez wrote: >> I think replacing nova's persistent storage layer with a distributed >> database would have a great effect - but I do not think it would have >> anything to do with the database itself. It would come from the act that

[openstack-dev] [openstack-manuals] What the status of DocImpact

Hi Doc Team, I want to know the recent status of DocImpact tag, is it deprecated for config option changes now? If it's true, then what the workflow for config reference now, any hint or link? Previously, when a patch has impact to document, including config option changes, I usually ask

Re: [openstack-dev] [stable][infra] request for reviews on two requirements changes

On 4/23/2016 3:10 PM, Amrith Kumar wrote: The reason this change is being submitted is because people are advised to use upper-constraints.txt as the versions that have been tested but they don't always do that. As a result, blocking in requirements.txt is also recommended. Yeah, good point,

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: April-23-16 12:23 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][app-catalog][all] Build unified > abstraction for all COEs > > On 21/04/16 23:34

[openstack-dev] [Congress] Congress social at Austin 4/27

Hi Congress folks, We¹re going to have an evening get-together at Openstack Austin. Please shoot me an email at if you¹re planning to come. Hope to see you there! Information: Date: Wednesday, April 27 Time: 6:00PM Location: LAMBERTS DOWNTOWN BARBEQUE 401 West 2nd

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

I am not necessary agree with the viewpoint below, but that is the majority viewpoints when I was trying to sell Magnum to them. There are people who interested in adopting Magnum, but they ran away after they figured out what Magnum actually offers is a COE deployment service. My takeaway is

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On 4/23/16, 1:26 PM, "Jay Pipes" wrote: >On 04/22/2016 08:27 PM, Steven Dake (stdake) wrote: >> * Repository per OpenStack and Infra component, e.g. one from nova, >> one for neutron and etc. - to contain all needed container images >> for running corresponding

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

On 4/22/2016 4:58 PM, Tom Fifield wrote: Hi all, On 22/04/16 16:40, Clint Byrum wrote: But in the mean time, maybe we can just send this message to party planners: Provide us with interesting spaces to converse and bond in, and we will be happier. Spoke with the party planners and got the

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 15:25 Apr 23, Jay Pipes wrote: > On 04/23/2016 03:18 PM, Mike Perez wrote: > >On 14:54 Apr 18, Jay Pipes wrote: > >>On 04/16/2016 05:51 PM, Amrith Kumar wrote: > >>> - update_resource(id or resource, newsize) > >> > >>Resizing resources is a bad idea, IMHO. Resources are easier to deal

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 04/23/2016 03:25 PM, Jay Pipes wrote: > On 04/23/2016 03:18 PM, Mike Perez wrote: >> On 14:54 Apr 18, Jay Pipes wrote: >>> On 04/16/2016 05:51 PM, Amrith Kumar wrote: - update_resource(id or resource, newsize) >>> >>> Resizing resources is a bad idea, IMHO. Resources are easier

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On 04/22/2016 08:27 PM, Steven Dake (stdake) wrote: * Repository per OpenStack and Infra component, e.g. one from nova, one for neutron and etc. - to contain all needed container images for running corresponding services in different topologies; * It should be possible to use

Re: [openstack-dev] [stable][infra] request for reviews on two requirements changes

On Sat, 2016-04-23 at 12:53 -0500, Matt Riedemann wrote: > On 4/23/2016 8:20 AM, Amrith Kumar wrote: > > Folks, > > > > Changes [1] and [2] blacklist Routes 2.3 in Mitaka and Liberty. They've > > been cherry picked from a change that merged in master. > > > > I would like both changes merged so I

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On Sat, 2016-04-23 at 15:25 -0400, Jay Pipes wrote: > On 04/23/2016 03:18 PM, Mike Perez wrote: > > On 14:54 Apr 18, Jay Pipes wrote: > >> On 04/16/2016 05:51 PM, Amrith Kumar wrote: > >>> - update_resource(id or resource, newsize) > >> > >> Resizing resources is a bad idea, IMHO.

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 04/23/2016 03:18 PM, Mike Perez wrote: On 14:54 Apr 18, Jay Pipes wrote: On 04/16/2016 05:51 PM, Amrith Kumar wrote: - update_resource(id or resource, newsize) Resizing resources is a bad idea, IMHO. Resources are easier to deal with when they are considered of immutable size and

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 14:54 Apr 18, Jay Pipes wrote: > On 04/16/2016 05:51 PM, Amrith Kumar wrote: > > - update_resource(id or resource, newsize) > > Resizing resources is a bad idea, IMHO. Resources are easier to deal with > when they are considered of immutable size and simple (i.e. not complex or >

Re: [openstack-dev] [infra][devstack] stable/kilo devstack fails with pkg_resources.ContextualVersionConflict

On 4/22/2016 3:56 PM, Felipe Reyes wrote: On Thu, 21 Apr 2016 15:12:53 +1000 Tony Breeds wrote: On Tue, Apr 19, 2016 at 01:14:34PM +0200, Lajos Katona wrote: Hi, In our internal CI system we realized that stable/kilo devstack fails with the following stack trace:

Re: [openstack-dev] [infra][devstack] stable/kilo devstack fails with pkg_resources.ContextualVersionConflict

On 4/23/2016 1:02 PM, Matt Riedemann wrote: On 4/22/2016 3:56 PM, Felipe Reyes wrote: On Thu, 21 Apr 2016 15:12:53 +1000 Tony Breeds wrote: On Tue, Apr 19, 2016 at 01:14:34PM +0200, Lajos Katona wrote: Hi, In our internal CI system we realized that stable/kilo

Re: [openstack-dev] [stable][infra] request for reviews on two requirements changes

On 4/23/2016 8:20 AM, Amrith Kumar wrote: Folks, Changes [1] and [2] blacklist Routes 2.3 in Mitaka and Liberty. They've been cherry picked from a change that merged in master. I would like both changes merged so I can then make corresponding changes in Trove, and then make a Trove (Mitaka)

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

On 21/04/16 23:34 +, Fox, Kevin M wrote: Amrith, Very well thought out. Thanks. :) I agree a nova driver that let you treat containers the same way as vm's, bare metal, and lxc containers would be a great thing, and if it could plug into magnum managed clusters well, would be awesome. I

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

Amrith Kumar wrote: To all who have said the Core Party was a bad thing, let me echo Sean's feelings, and add that I actually liked the core parties more than any of the others, and actually found them to be a very good thing. I too got to meet people who I would normally not have had a

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

Monty Taylor wrote: On 04/22/2016 03:27 PM, Ed Leafe wrote: OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did it anyway.

[openstack-dev] [neutron] Discussing DLMs in the Unplugged Track

Hi guys, I'm interested in discussing the DLM RFE [1] during the unplugged track on Friday morning, around 11:00am. A face-to-face talk about this with all parties interested will surely prove fruitful and will set us up on the track we want to go through in respect to this feature. You can find

[openstack-dev] [stable][infra] request for reviews on two requirements changes

Folks, Changes [1] and [2] blacklist Routes 2.3 in Mitaka and Liberty. They've been cherry picked from a change that merged in master. I would like both changes merged so I can then make corresponding changes in Trove, and then make a Trove (Mitaka) bug fix release. Thanks, -amrith [1]

Re: [openstack-dev] [magnum] Seek advices for a licence issue

Jay, I will discuss the proposal [1] in the design summit. Do you plan to contribute on this efforts or someone from DCOS community interest to contribute? [1] https://blueprints.launchpad.net/magnum/+spec/mesos-dcos Best regards, Hongbin From: Jay Lau [mailto:jay.lau@gmail.com] Sent:

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Yes this patch fixes the issue. Thanks Ilya. On Fri, Apr 22, 2016 at 4:53 PM, Ilya Kutukov wrote: > Hello! > > I think your problem is related to the: > https://bugs.launchpad.net/fuel/+bug/1570846 > > Fix to stable/mitaka was commited 20/04/2016 >

[openstack-dev] [OpenStack-Ansible] Bug Triage 26 Apr & Community Meeting 28 Apr

Hi everyone, Due to many of us being at the summit, the weekly meetings for 26 and 28 Apr have been cancelled. See you in Austin! -- Jesse Pretorius IRC: odyssey4me __ OpenStack Development Mailing List (not for usage