Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

On 09/30/2014 02:03 PM, Soren Hansen wrote: 2014-09-12 1:05 GMT+02:00 Jay Pipes : If Nova was to take Soren's advice and implement its data-access layer on top of Cassandra or Riak, we would just end up re-inventing SQL Joins in Python-land. I may very well be wrong(!), but this statement make

[openstack-dev] [all] minimum python support version for juno

Hi, I would like to know the minimum python support version for juno. I checked the following memo. My understanding is python 2.6 support will be supported in juno and also dropped before kilo so it will be dropped in one of stable releases in juno. Is this correct understanding? https://ethe

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hi Joe, On 01/10/14 09:10, joehuang wrote: > OpenStack cascading: to integrate multi-site / multi-vendor OpenStack > instances into one cloud with OpenStack API exposed. > Cells: a single OpenStack instance scale up methodology Just to let you know - there are actually some users out there that

Re: [openstack-dev] [Openstack] Glance on swift problem

Hello, W dniu 2014-09-30 20:28, Timur Nurlygayanov napisał(a): Hi Slawek, we faced the same error and this is issue with Swift. We can see 100% disk usage on the Swift node during the file upload and looks like Swift can't send info about status of the file loading in time. On our environments

[openstack-dev] [Nova] [Cinder] [Sahara] Juno RC1 available

Hello everyone, Nova, Cinder, and Sahara just published their first release candidate for the upcoming 2014.2 ("Juno") release. The RC1 tarballs are available for download at: https://launchpad.net/nova/juno/juno-rc1 https://launchpad.net/cinder/juno/juno-rc1 https://launchpad.net/sahara/juno/jun

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hi Joe and Cellers, I've tried to understand relationship between Cell and Cascading. If Cell has been designed as below, would it be the same as Cascading? 1) Besides Nova, Neutron/Ceilometer.. is also hierarchically structured for scalability. 2) Child-parent interaction is based on REST OS-AP

Re: [openstack-dev] 2 Minute tokens

On Tue, Sep 30, 2014 at 10:44:51AM -0400, Adam Young wrote: > What is keeping us from dropping the (scoped) token duration to 5 minutes? > > > If we could keep their lifetime as short as network skew lets us, we would > be able to: > > Get rid of revocation checking. > Get rid of persisted token

Re: [openstack-dev] [Solum] Core Reviewer Change

+1 2014-10-01 8:50 GMT+02:00 Noorul Islam K M : > Adrian Otto writes: > > > Solum Core Reviewer Team, > > > > I propose the following change to our core reviewer group: > > > > -lifeless (Robert Collins) [inactive] > > +murali-allada (Murali Allada) > > +james-li (James Li) > > > > Please let me

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hello, Tom, Thanks for your mail to mention that some users out there that use cells "to integrate multi-site / multi-vendor OpenStack instances into one cloud with OpenStack API exposed.",. Why do I think Cells using scale up methodology? 1, Use case 1: All cells using shared Cinder, Neutron,

[openstack-dev] Weekly Octavia meeting (2014-10-01)

Hi Folks! Since I had to miss last week's meeting due to a last minute emergency, and since it seems there was significant confusion over some of the items I had added to last week's agenda, this week's agenda will actually be essentially the same thing as last week's. Here's what we've got on tap

Re: [openstack-dev] [neutron] Requirements freeze exception for testscenarios, oslotest, psycopg2, MySQL-python

Ihar Hrachyshka wrote: > Also, depfreeze seems to apply to openstack/requirements repository > only [1], and projects are open to consume new dependencies from there. > > [1]: https://wiki.openstack.org/wiki/DepFreeze Yes, you're right. Nothing prevents this patch from merging at this point. --

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hello, Loy, Thank you very much. You have already grasped the core design idea for OpenStack cascading: >>By my understanding, core idea of Cascading is that each resource >>building block(like child cell) is a clearly separated autonomous >>system, with the already defined REST OS-API as the NB

Re: [openstack-dev] [all] minimum python support version for juno

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/10/14 09:08, Osanai, Hisashi wrote: > > Hi, > > I would like to know the minimum python support version for juno. I > checked the following memo. My understanding is python 2.6 support > will be supported in juno and also dropped before kilo

[openstack-dev] [NFV] VLAN trunking to VM - justification/use cases

Hello all I took the action on last week's call to explain why the VLAN trunking to VM bp is a relevant use case for NFV - here's my take. The big picture is that this is about how service providers can use virtualisation to provide differentiated network services to their customers (and specif

Re: [openstack-dev] [neutron] [IPv6] New API format for extra_dhcp_opts

ip_version sounds great. Currently the opt-names are written into the configuration file of dnsmasq directly. So I would say yes, they are coming from dnsmasq definitions. It will make more sense when ip_version is missing or null, the option apply to both since we could have only ipv6 or ip

[openstack-dev] Taskflow for Juno RC1 effectively require Kombu 3.x

Hi, When building the latest release (eg: Juno RC1) of Taskflow 0.4, needed by Cinder, I've notice failures due to the impossibility to do: from kombu import message More in details, the failure is: == FAIL: unittest.loader.Mod

Re: [openstack-dev] VPNaaS site to site connection down.

See in-line @PCM PCM (Paul Michali) MAIL …..…. p...@cisco.com IRC ……..… pcm_ (irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Sep 30, 2014, at 11:31 PM, masoom alam wrote: > Hi Paul, > > Apologies for lat

Re: [openstack-dev] Taskflow for Juno RC1 effectively require Kombu 3.x

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/10/14 12:55, Thomas Goirand wrote: > Hi, > > When building the latest release (eg: Juno RC1) of Taskflow 0.4, > needed by Cinder, I've notice failures due to the impossibility to > do: > > from kombu import message > > More in details, the f

[openstack-dev] [Tripleo] Release report

1. os-apply-config: release: 0.1.22 --> 0.1.23 -->https://pypi.python.org/pypi/os-apply-config/0.1.23 --> http://tarballs.openstack.org/os-apply-config/os-apply-config-0.1.23.tar.gz 2. os-refresh-config: release: 0.1.7 --> 0.1.8 -->https://pypi.python.org/pypi/os-refresh

Re: [openstack-dev] VPNaaS site to site connection down.

In line. Thanks for the response. > > > @PCM So is the public IP for the router (172.24.4.226) an internet on the Internet? In the example, IIRC, the quantum router has an IP on the public network, and the GW IP is also on the same network (172.24.4.225). I think the latter, is assigned to the ex

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hello, Alex, Thank you very much for your mail about remote cluster hypervisor. One of the inspiration for OpenStack cascading is from the remote clustered hypervisor like vCenter. The difference between the remote clustered hypervisor and OpenStack cascading is that not only Nova involved in

Re: [openstack-dev] Taskflow for Juno RC1 effectively require Kombu 3.x

There just needs to be a fallback import. In v2.5.0 the Message class (which is the only item used from kombu.message) was in kombu.transport.base. Thomas, can you confirm that something like try: from kombu import message except ImportError: from kombu.transport import base as message Al

Re: [openstack-dev] [all] concrete proposal on changing the library testing model with devstack-gate

An initial WIP patch to show the direction I think this could materialize - https://review.openstack.org/125346 Early feedback appreciated so I can do this conversion across the board. My assumption is that all non integrated release projects should be converted to this model. On 09/26/2014 02:27

Re: [openstack-dev] 2 Minute tokens

On 10/01/2014 04:14 AM, Steven Hardy wrote: On Tue, Sep 30, 2014 at 10:44:51AM -0400, Adam Young wrote: What is keeping us from dropping the (scoped) token duration to 5 minutes? If we could keep their lifetime as short as network skew lets us, we would be able to: Get rid of revocation check

Re: [openstack-dev] [all] minimum python support version for juno

On 10/1/2014 4:24 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/10/14 09:08, Osanai, Hisashi wrote: Hi, I would like to know the minimum python support version for juno. I checked the following memo. My understanding is python 2.6 support will be supported

Re: [openstack-dev] [openstack-qa] Post job failures

Hi Josh, Just a heads up that you shouldn't use this list for any discussion. We've moved all of the discussion off this list into openstack-dev. The only reason we haven't removed the openstack-qa list is so we have a separate address for the periodic job results. (which honestly hasn't been the

Re: [openstack-dev] VPNaaS site to site connection down.

See inline at #PCM PCM (Paul Michali) MAIL …..…. p...@cisco.com IRC ……..… pcm_ (irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Oct 1, 2014, at 8:35 AM, masoom alam wrote: > In line. Thanks for the response

[openstack-dev] [QA] Meeting Thursday October 2nd at 22:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, October 2nd at 22:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to

Re: [openstack-dev] [kolla] Kolla Blueprints

On 09/30/2014 09:55 AM, Chmouel Boudjnah wrote: On Tue, Sep 30, 2014 at 6:41 PM, Steven Dake > wrote: I've done a first round of prioritization. I think key things we need people to step up for are nova and rabbitmq containers. For the developers, please

Re: [openstack-dev] [nova] Create an instance with a custom uuid

Thank you for the answers. I understood the concerns about having the UUID completely user defined and I also understand Nova has no interest in supporting a customized algorithm to generate UUID. Anyway I may have found a solution that will cover my use case and respect the standard for UUID

[openstack-dev] [Horizon] [All?] "Status" vs "State"

Hi, # The first half is related to Horizon and the latter half is about the wording in Nova and Neutron API. During Horizon translation for Juno, I noticed the words "State" and "Status" in multiple contexts. Sometimes they are in very similar contexts and sometimes they have different contexts.

Re: [openstack-dev] [nova] Create an instance with a custom uuid

(response inline) - Original Message - > From: "Pasquale Porreca" > To: openstack-dev@lists.openstack.org > Sent: Wednesday, October 1, 2014 11:08:50 AM > Subject: Re: [openstack-dev] [nova] Create an instance with a custom uuid > > Thank you for the answers. > > I understood the concer

Re: [openstack-dev] Taskflow for Juno RC1 effectively require Kombu 3.x

I'm fine with this if it works (seems pretty simple). Let me know. I can get out an adjusted release if needed... On Wed, Oct 1, 2014 at 6:10 AM, Ian Cordasco wrote: There just needs to be a fallback import. In v2.5.0 the Message class (which is the only item used from kombu.message) was in k

[openstack-dev] [All] [I18N] compiling translation message catalogs

Hi, To display localized strings, we need to compile translated message catalogs (PO files) into compiled one (MO files). I would like to discuss and get a consensus who and when generate compiled message catalogs. Inputs from packagers are really appreciated. [The current status] * Horizon conta

Re: [openstack-dev] [nova] Create an instance with a custom uuid

On Wed, Oct 1, 2014 at 8:29 AM, Solly Ross wrote: > (response inline) > > - Original Message - > > From: "Pasquale Porreca" > > To: openstack-dev@lists.openstack.org > > Sent: Wednesday, October 1, 2014 11:08:50 AM > > Subject: Re: [openstack-dev] [nova] Create an instance with a custom

Re: [openstack-dev] Taskflow for Juno RC1 effectively require Kombu 3.x

I tried this out, seems to work locally. So you should be fine doing this locally if u want or when a taskflow 0.4.1 comes out (which it can/should soon anyway) this will be there. Review up @ https://review.openstack.org/#/c/125400/ Bug @ https://bugs.launchpad.net/taskflow/+bug/1376330 Tha

[openstack-dev] [Murano] Juno RC1 is Available

We successfully released RC1 release of Murano! The RC1 tarballs are available for download at: https://launchpad.net/murano/juno/juno-rc1 Unless critical issues are found, this RC1 will be formally released as the 2014.2 final version of Murano. Please, try to do extensive testing of this versio

Re: [openstack-dev] Taskflow for Juno RC1 effectively require Kombu 3.x

On 2014-10-01 16:04:37 -0007 (-0007), Joshua Harlow wrote: > Thanks for finding this one (it'd be nice for some gate job to run > in 'strict' requirements mode which tests the lower bounds of the > requirements repo somehow, since with things like kombu>=2.5.0 > this will always pull in the newest

[openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

As stable branches got discussed recently, I'm kind of curious who is actually stepping up to make icehouse able to pass tests in any real way. Because right now I've been trying to fix devstack icehouse so that icehouse requirements can be unblocked (and to land code that will reduce grenade failu

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hi Chaoyi, Thanks for sharing these information. Sometime back I have stared a project called “Alliance” which trying to address the same concerns (see the link below). Alliance service is designed to provide "Inter-Cloud Resource Federation" which will enable resource sharing across cloud in

Re: [openstack-dev] [openstack-qa] Post job failures

On 2014-10-01 10:39:40 -0400 (-0400), Matthew Treinish wrote: [...] > So I actually think as a first pass this would be the best way to > handle it. You can leave comments on a closed gerrit changes, [...] Not so easy as it sounds. Jobs in post are running on an arbitrary Git commit (more often th

Re: [openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

On Wednesday, October 1, 2014, Sean Dague wrote: > As stable branches got discussed recently, I'm kind of curious who is > actually stepping up to make icehouse able to pass tests in any real > way. Because right now I've been trying to fix devstack icehouse so that > icehouse requirements can be

Re: [openstack-dev] [kolla] Kolla Blueprints

Excerpts from Steven Dake's message of 2014-10-01 08:04:38 -0700: > On 09/30/2014 09:55 AM, Chmouel Boudjnah wrote: > > > > On Tue, Sep 30, 2014 at 6:41 PM, Steven Dake > > wrote: > > > > > > I've done a first round of prioritization. I think key things we > > nee

Re: [openstack-dev] [Solum] Core Reviewer Change

+1 - Original Message - From: "Adrian Otto" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Tuesday, September 30, 2014 10:03:16 AM Subject: [openstack-dev] [Solum] Core Reviewer Change Solum Core Reviewer Team, I propose the following change to our core revie

Re: [openstack-dev] django-pyscss failing with Django 1.7

Hi Thomas, I have a few suggestions inline that I hope will be helpful! > From: Matt Riedemann > To: Douglas Fish/Rochester/IBM@IBMUS, Justin Pomeroy/Rochester/IBM@IBMUS > Date: 09/30/2014 10:26 PM > Subject: Fwd: Re: [openstack-dev] django-pyscss failing with Django 1.7 > > FYI in case one of y

[openstack-dev] oslo.db 1.0.2 released

The Oslo team has released version 1.0.2 of oslo.db. This patch release on the Juno series includes a fix for bug 1374497 (“change in oslo.db ‘ping’ handling is causing issues in projects that are not using transactions”). https://bugs.launchpad.net/oslo.db/+bug/1374497 Doug _

Re: [openstack-dev] [Solum] Core Reviewer Change

Thanks everyone for your feedback on this. The adjustments have been made. Regards, Adrian On Sep 30, 2014, at 10:03 AM, Adrian Otto wrote: > Solum Core Reviewer Team, > > I propose the following change to our core reviewer group: > > -lifeless (Robert Collins) [inactive] > +murali-allada (M

[openstack-dev] Help with EC2 Driver functionality using boto ...

Hi, We are currently working on writing a driver for Amazon's EC2 using the boto libraries, and are hung up on creating a snapshot of an instance. The instance remains in 'Queued' status on Openstack instead of becoming 'Active'. The actual EC2 snapshot that gets created is in 'available' status.

Re: [openstack-dev] [Horizon] [All?] "Status" vs "State"

Hi Akihiro! IMO, this is precisely where having an API standards working group can help to make the user experience of our public APIs less frustrating. Such a working group should have the ability to vet terms like "state" vs "status" and ensure consistency across the public APIs. More thou

Re: [openstack-dev] [Fuel] Documentation process

Sorry I'm so late to the party. Yes, Andreas is right, we simply cannot take on any more DocImpact in openstack-manuals, but it would be great to change the infrastructure to log against a more exact match for the bug tracker for the project with the impacted docs. Looks like you're doing so with h

Re: [openstack-dev] [Solum] Core Reviewer Change

Murali, James, congratulations on core reviewer status ! -Original Message- From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: Wednesday, October 01, 2014 1:11 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Solum] Core Reviewer Ch

[openstack-dev] [nova] formally distinguish server "desired state" from "actual state"?

Currently in nova we have the "vm_state", which according to the code comments is supposed to represent "a VM's current stable (not transition) state", or "what the customer expect the VM to be". However, we then added in an ERROR state. How does this possibly make sense given the above def

[openstack-dev] [Sahara][Doc] Overview and Architecture images in docs

Hi all, There was a discussion previously stating that the Sahara overview image http://docs.openstack.org/developer/sahara/overview.html and the architecture image http://docs.openstack.org/developer/sahara/architecture.html pretty much convey the same message. So will it be nice to strip off the

Re: [openstack-dev] [nova] formally distinguish server "desired state" from "actual state"?

On 10/01/2014 03:07 PM, Chris Friesen wrote: Currently in nova we have the "vm_state", which according to the code comments is supposed to represent "a VM's current stable (not transition) state", or "what the customer expect the VM to be". However, we then added in an ERROR state. How does thi

Re: [openstack-dev] [Openstack] Glance on swift problem

Hello, Thanks for Your help but it not helps. I checked that for sure on each swift node there is a lot of free space. What can confirm that is fact that when I try to create image with size about 1.7GB and I have swift_store_large_object_size set to 1GB than there is error (always after send

[openstack-dev] [nova] Help with EC2 Driver functionality using boto ...

> > Hi, > > We are trying to leverage EC2 from Openstack, and are currently working on > writing an EC2 driver using the boto libraries, and are hung up on snapshot > of an instance functionality. The instance remains in 'Queued' status on > Openstack instead of becoming 'Active'. The actual EC2 s

Re: [openstack-dev] [Solum] Core Reviewer Change

Happy Corethday to the both of you! On 10/1/14, 1:10 PM, "Adrian Otto" wrote: >Thanks everyone for your feedback on this. The adjustments have been made. > >Regards, > >Adrian > >On Sep 30, 2014, at 10:03 AM, Adrian Otto >wrote: > >> Solum Core Reviewer Team, >> >> I propose the following chan

[openstack-dev] [all] [announce] OpenStack Bootstrapping Hour Episode 1: Diving into OpenStack Docs - Friday Oct 3 - 19:00 UTC (15:00 Americas/New_York)

Anne Gentle will be our guest this week as we dive into OpenStack Docs. That dirty word everyone loves but hardly anyone does, documentation! For this bootstrapping hour Anne will talk about the wild world of developer docs, both for contributors and application developers. We can do a review and

[openstack-dev] [nova][neutron] "Sideways" grenade job to test Nova Network to Neutron migration

Hello, One of the requirements placed on Ironic was that they must have a path from Nova Baremetal to Ironic and that path should be tested. This resulted in a "sideways" grenade job which instead of going from one release of OpenStack to another, swaps out components within a release. In this cas

Re: [openstack-dev] [nova] formally distinguish server "desired state" from "actual state"?

On 10/01/2014 01:23 PM, Jay Pipes wrote: On 10/01/2014 03:07 PM, Chris Friesen wrote: Currently in nova we have the "vm_state", which according to the code comments is supposed to represent "a VM's current stable (not transition) state", or "what the customer expect the VM to be". However, we t

Re: [openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

On 10/1/14, 11:53 AM, "Morgan Fainberg" wrote: > > >On Wednesday, October 1, 2014, Sean Dague wrote: > >As stable branches got discussed recently, I'm kind of curious who is >actually stepping up to make icehouse able to pass tests in any real >way. Because right now I've been trying to fix devs

Re: [openstack-dev] [kolla] Kolla Blueprints

Has anyone figured out a way of having a floating ip like feature with docker so that you can have rabbitmq, mysql, or ceph mon's at fixed ip's and be able to migrate them around from physical host to physical host and still have them at fixed locations that you can easily put in static config f

[openstack-dev] [TripleO] tripleo-puppet-elements is alive!

{Puppet-OpenStack,TripleO} developpers, For your information https://github.com/openstack/tripleo-puppet-elements is now alive. Puppet Group has been assigned core on this project since most of contribution will be Puppet code. Good news! Dan Prince is both TripleO & Puppet core member, so he will

Re: [openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

On 10/01/2014 04:46 PM, Ian Cordasco wrote: > On 10/1/14, 11:53 AM, "Morgan Fainberg" wrote: > >> >> >> On Wednesday, October 1, 2014, Sean Dague wrote: >> >> As stable branches got discussed recently, I'm kind of curious who is >> actually stepping up to make icehouse able to pass tests in any

Re: [openstack-dev] [nova] formally distinguish server "desired state" from "actual state"?

On Wed, Oct 01, 2014, Chris Friesen wrote: > Currently in nova we have the "vm_state", which according to the > code comments is supposed to represent "a VM's current stable (not > transition) state", or "what the customer expect the VM to be". > > However, we then added in an ERROR state. How d

Re: [openstack-dev] [tc][cross-project-work] What about adding cross-project-spec repo?

On Mon, Sep 29, 2014 at 11:58 AM, Doug Hellmann wrote: > > On Sep 29, 2014, at 5:51 AM, Thierry Carrez wrote: > > > Boris Pavlovic wrote: > >> it goes without saying that working on cross-project stuff in OpenStack > >> is quite hard task. > >> > >> Because it's always hard to align something be

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Hi, Tiwari, Great to know you are also trying to address similar issues. For sure we are happy to work out a common solution for these issues. I just go through the wiki page, the question for me is "will the Alliance provide/retain current north bound OpenStack API ?". It's very important

Re: [openstack-dev] [nova] formally distinguish server "desired state" from "actual state"?

On 10/01/2014 04:31 PM, Chris Friesen wrote: On 10/01/2014 01:23 PM, Jay Pipes wrote: On 10/01/2014 03:07 PM, Chris Friesen wrote: Currently in nova we have the "vm_state", which according to the code comments is supposed to represent "a VM's current stable (not transition) state", or "what the

Re: [openstack-dev] [all] minimum python support version for juno

Thank you for the quick responses. > On 10/1/2014 4:24 AM, Ihar Hrachyshka wrote: > > All stable Juno releases will support Python 2.6. All Kilo releases > > are expected to drop Python 2.6 support. On Wednesday, October 01, 2014 11:28 PM, Matt Riedemann wrote: > Right, and backports could be in

Re: [openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

I agree with Sean here. The original idea was that these stable branches would be maintained by the distros, and that is clearly not happening if you look at the code review latency there. We need to sort that out before we even consider supporting a release for more than the one year we currently

Re: [openstack-dev] [nova][neutron] "Sideways" grenade job to test Nova Network to Neutron migration

Thanks for doing this. My recollection is that we still need some features landed in Neutron before this work can complete, but its possible I am confused. A public status update on that from the Neutron team would be good. Michael On Thu, Oct 2, 2014 at 6:18 AM, Clark Boylan wrote: > Hello, >

Re: [openstack-dev] Help with EC2 Driver functionality using boto ...

It is hard to tell if this is a bug or a misconfiguration from your desctiption. The failure likely generated some kind of error message in nova or glance. If you can track down an error message and a tracback it would be worth submitting as a bug report to the appropriate project. Vish On Oct

Re: [openstack-dev] [kolla] Kolla Blueprints

On Oct 1, 2014, at 2:05 PM, Fox, Kevin M wrote: > Has anyone figured out a way of having a floating ip like feature with docker > so that you can have rabbitmq, mysql, or ceph mon's at fixed ip's and be able > to migrate them around from physical host to physical host and still have > them at

[openstack-dev] [TripleO] a need to assert user ownership in preserved state

Recently we've been testing image based updates using TripleO, and we've run into an interesting conundrum. Currently, our image build scripts create a user per service for the image. We don't, at this time, assert a UID, so it could get any UID in the /etc/passwd database of the image. However,

Re: [openstack-dev] [kolla] Kolla Blueprints

On Wed, 1 Oct 2014 09:05:23 PM Fox, Kevin M wrote: > Has anyone figured out a way of having a floating ip like feature with > docker so that you can have rabbitmq, mysql, or ceph mon's at fixed ip's > and be able to migrate them around from physical host to physical host and > still have them at fi

Re: [openstack-dev] [TripleO] a need to assert user ownership in preserved state

Excerpts from Clint Byrum's message of 2014-10-02 01:50:33 +: > Recently we've been testing image based updates using TripleO, and we've > run into an interesting conundrum. > > Currently, our image build scripts create a user per service for the > image. We don't, at this time, assert a UID,

[openstack-dev] [Cinder][TripleO] Last days to elect your PTL!

Hello Cinder and TripleO contributors, Just a quick reminder that elections are closing soon, if you haven't already you should use your right to vote and pick your favourite candidate! Thanks for your time! Tristan signature.asc Description: OpenPGP digital signature _

Re: [openstack-dev] [TripleO] a need to assert user ownership in preserved state

Clint Byrum wrote on 10/01/2014 09:50:33 PM: > Recently we've been testing image based updates using TripleO, and we've > run into an interesting conundrum. > > Currently, our image build scripts create a user per service for the > image. We don't, at this time, assert a UID, so it could get any

Re: [openstack-dev] [TripleO] a need to assert user ownership in preserved state

On 02/10/14 12:26, Mike Spreitzer wrote: > I do not understand the problem statement. Unfortunately, I am not > familiar with image based updates using TripleO. What is updating what? > If the UIDs are not asserted, what UIDs shift by one? Is this because > some files keep owner UID while the so

Re: [openstack-dev] [neutron] [IPv6] [ironic] New API format for extra_dhcp_opts

As a 'heads up', adding ironic to the thread since they are a 'key' consumer of this api. On Oct 1, 2014, at 3:15 AM, Xu Han Peng mailto:pengxu...@gmail.com>> wrote: ip_version sounds great. Currently the opt-names are written into the configuration file of dnsmasq directly. So I would say y

Re: [openstack-dev] [TripleO] a need to assert user ownership in preserved state

All three of the options presented here seem to assume that UIDs will always be allocated at image-build time. I think that's because most of these UIDs will be used to write files into the chroot at image-create time - if I could think of some way around that, I think we could avoid this proble

Re: [openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

The stable-maint team has been more active in the last couple months of keeping on top of stable branch specific gate breakage (usually identified by periodic job failures). We managed to flush a bunch of reviews through the gate over the last couple weeks [1] Yea, many required rechecks, but the

Re: [openstack-dev] [All] [I18N] compiling translation message catalogs

On Wed, Oct 1, 2014 at 6:04 PM, Akihiro Motoki wrote: > Hi, Hi Akihiro! > To display localized strings, we need to compile translated message > catalogs (PO files) into compiled one (MO files). > I would like to discuss and get a consensus who and when generate > compiled message catalogs. > Inp

Re: [openstack-dev] [TripleO] a need to assert user ownership in preserved state

Excerpts from James Polley's message of 2014-10-02 05:37:25 +: > All three of the options presented here seem to assume that UIDs will always > be allocated at image-build time. I think that's because most of these UIDs > will be used to write files into the chroot at image-create time - if I