Re: [openstack-dev] [Heat] HOT Software configuration proposal

Clint Byrum wrote on 23.10.2013 00:28:17: > From: Clint Byrum > To: openstack-dev , > Date: 23.10.2013 00:30 > Subject: Re: [openstack-dev] [Heat] HOT Software configuration proposal > > Excerpts from Georgy Okrokvertskhov's message of 2013-10-22 13:32:40 -0700: > > Hi Thomas, > > > > I agree wit

Re: [openstack-dev] [scheduler] APIs for Smart Resource Placement - Updated Instance Group Model and API extension model - WIP Draft

I didn't see any command referring InstanceGroupMemberConnection. What is it exactly? Could you give an example? And how can we create an InstanceGroup? 1) Create an empty group 2) Add policy, metadata 3) Add group instances ... ? or in the InstanceGroup POST message there is already a descr

[openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

Hi Neutron folks! We're going to have an IRC meeting where we will discuss development plans for LBaaS in Icehouse. Currently I'm proposing to meet on Thursday, 24 at 8:00 PDT on freenode #neutron-lbaas channel. Agenda for the meeting: 1. New features for lbaas in Icehouse Pretty much everything

Re: [openstack-dev] Testing before sending for review

Hi, 1. It's not necessary to abandon your patch if it has failed jenkins tests. 2. Before submitting the new patch for review it's better to run unit tests (tox -epy27) and pep8 check (tox -epep8) Integration testing is being done by check-tempest-devstack-vm-neutron* suites and some of them fail

Re: [openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

HI, the following time is ok for me: UTC+8: 6:00-23:00 UTC: 22:00-15:00 If it is scheduled during these time slot, I will join. Thanks Yong Sheng Gong On Wed, Oct 23, 2013 at 4:50 PM, Eugene Nikanorov wrote: > Hi Neutron folks! > > We're going to have an IRC meeting where we will discuss devel

Re: [openstack-dev] Testing before sending for review

To clarify point #2: always check the logs to see the cause of the failure. If it's due to a bug in the submitted code, fix and resubmit. If it's caused by something else, check if it's an open bug, and if not open a new bug report - in either case, do "recheck bug #". If it's really not caus

Re: [openstack-dev] Testing before sending for review

Hi > 2. Before submitting the new patch for review it's better to run unit tests > (tox -epy27) and pep8 check (tox -epep8) Instead of pep8 I think you should run flake8 we moved to that some months ago[1]. Usually I find always useful to test my changes in devstack. Regards -- Andrea Rosa [1]

Re: [openstack-dev] Testing before sending for review

Hey, On 23.10.2013 11:29, Rosa, Andrea (HP Cloud Services) wrote: Usually I find always useful to test my changes in devstack. How do you do that? I think the devstack does not always contain up to date codebase does it, so what would be the point in testing changes on the old code? Thanks

Re: [openstack-dev] Testing before sending for review

Hi >On 23.10.2013 11:29, Rosa, Andrea (HP Cloud Services) wrote: >> Usually I find always useful to test my changes in devstack. > >How do you do that? I think the devstack does not always contain up to date >codebase does it, so what would be the point in testing changes on the old >code? With de

Re: [openstack-dev] Distributed Virtual Router Discussion

Hi, I'm interested as well, please include me in the discussion. Thanks Christian -Original Message- From: Artem Dmytrenko [mailto:nexton...@yahoo.com] Sent: Monday, October 21, 2013 11:51 AM To: yong sheng gong (gong...@unitedstack.com); cloudbe...@gmail.com; OpenStack Development Maili

Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux

Hi Qing, Freescale SoCs like P4080 and T4240 etc are supported for OpenStack as well. We have been using them from OpenStack Diablo release onwards. We demonstrated at ONS 2013, Interop 2013 and China Road Show. Regards, Balaji.P On 23 October 2013 08:57, Qing He wrote: > Matt, > > **

Re: [openstack-dev] [savanna] What's the recipe to build Oozie-4.0.0.tar.gz?

Hi, Matthew! Note, apache does not make oozie builds, and we have to build it manually. To build oozie.tar.gz you should follow the steps below: 1. Download oozie distribution from apache mirror (e.g. http://apache-mirror.rbc.ru/pub/apache/oozie/4.0.0) 2. Build includes maven project, so you sho

Re: [openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

Hi, I assume you are proposing 8:00AM and not 8:00PM PDT. I will not be able to attend on this time. Better time for me is between 10:00AM PDT - 12:00AM PDT Thanks, -Sam. From: Eugene Nikanorov [mailto:enikano...@mirantis.com] Sent: Wednesday, October 23, 2013 11:51 AM To:

Re: [openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

Hi Sam, Yes, I meant 8:00AM PDT, 10:00-12:00 AM PDT works for me as well. Looks like this time is not convenient for Yongsheng, unfortunately, but I think we should stick to the time that is convenient for the majority of interested folks. Thanks, Eugene. On Wed, Oct 23, 2013 at 3:01 PM, Samue

Re: [openstack-dev] Distributed Virtual Router Discussion

Hi Swaminathan, I'm interested as well. On our side we are working on this BP https://blueprints.launchpad.net/neutron/+spec/l3-high-availability Suggestions are welcome. Regards, Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.or

[openstack-dev] FOSDEM 2014 devroom CFP

There will be a two-day "Virtualisation and IaaS" devroom at FOSDEM 2014 (Brussels, February 1-2). See below for the CFP. Note: For this edition we'll avoid high-level, generic project presentations and give priority to deep dives and developer-oriented content, so please take that into account be

[openstack-dev] [neutron] [ml2] Canceling today's ML2 meeting

Hi folks: We don't really have an agenda today, so we're going to cancel the ML2 meeting today. Depending on what ML2 items get selected for the Summit, we'll likely meet next week to plan the discussions around those. One other note: Please keep an eye open for any bug fixes we should backport t

[openstack-dev] VPNaaS questions...

Hi guys, Some questions on VPNaaS… Can we get the review reopened of the service type framework changes for VPN on the server side? I was thinking of trying to rebase that patch, based on the latest from master, but before doing so, I ran TOX on the latest master commit. TOX fails with a bunch

[openstack-dev] [NOVA][NEUTRON] Whats the correct firewall driver and interface driver to use neutron sec groups in havana

Hi guys, Seem that i cant find the right combination to get neutron security groups working with nova and OVS - I see the logs on the ovs agent like sec group updated or rule updated - I can configure the rules on neutron without an issue BUT Seems like nova is not doing anything with the the r

[openstack-dev] [keystone] updating password user_crud vs credentials

Hello, If i understand correctly (and I may be wrong) we are moving away from user_crud to use /credentials for updating password including ec2. The credentials facility was implemented in this blueprint : https://blueprints.launchpad.net/keystone/+spec/extract-credentials-id and documented here

Re: [openstack-dev] VPNaaS questions...

Hi Paul, On Wed, Oct 23, 2013 at 9:56 PM, Paul Michali wrote: > > Hi guys, > > Some questions on VPNaaS… > > Can we get the review reopened of the service type framework changes for VPN > on the server side? > I was thinking of trying to rebase that patch, based on the latest from > master, bu

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Excerpts from Thomas Spatzier's message of 2013-10-23 00:08:23 -0700: > Clint Byrum wrote on 23.10.2013 00:28:17: > > From: Clint Byrum > > To: openstack-dev , > > Date: 23.10.2013 00:30 > > Subject: Re: [openstack-dev] [Heat] HOT Software configuration proposal > > > > Excerpts from Georgy Okrok

[openstack-dev] [Trove] About single entry point in trove-guestagent

Hi Denis, Michael, Vipul and all, I noticed a discussion in irc about adding a single entry point (sort of 'SuperManager') to the guestagent. Let me add my 5cent. I agree with that we would ultimately avoid code duplication. But from my experience, only very small part of GA Manager can be consid

Re: [openstack-dev] Gerrit tools

On Sun, Oct 20, 2013 at 05:01:23AM +, Joshua Harlow wrote: > I created some gerrit tools that I think others might find useful. > > https://github.com/harlowja/gerrit_view > > The neat one there is a curses based real time gerrit review receiver > that uses a similar mechanism as the gerrit i

Re: [openstack-dev] extend Network topology view in horizon

Hi Toshi If you have some documentation on the demo, please share it. Thanks & Regards Raja Srinivasan E: raja.sriniva...@riverbed.com P: +1(408) 598-1175 -Original Message- From: Toshiyuki Hayashi [mailto:haya...@ntti3.com] Sent: Tuesday, October 22, 2013 10:47 PM To: OpenStack Develo

Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux

Thanks, Balaji. Did you keep it upto date with openstack releases or do you still stay with that Diablo? Qing From: Balaji Patnala [mailto:patnala...@gmail.com] Sent: Wednesday, October 23, 2013 3:17 AM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [nova] Openstack on power

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague wrote: > Dave Kranz has been building a system so that we can ensure that during a > Tempest run services don't spew ERRORs in the logs. Eventually, we're going > to gate on this, because there is nothing that Tempest does to the system > that should ca

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

On 10/23/2013 10:40 AM, John Griffith wrote: On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague mailto:s...@dague.net>> wrote: Dave Kranz has been building a system so that we can ensure that during a Tempest run services don't spew ERRORs in the logs. Eventually, we're going to gate on

[openstack-dev] [Neutron] tempest failure: No more IP addresses available on network

Hi, I just noticed several number of neutron check (tempest-devstack-vm-neutron-isolated) fails with the same error: "No more IP addresses available on network". This errors suddenly starts to occur from yesterday. I checked there is any commit merge around the time when this failure started, but

Re: [openstack-dev] VPNaaS questions...

See PCM: in-line. PCM (Paul Michali) MAIL p...@cisco.com IRC pcm_ (irc.freenode.net) TW @pmichali On Oct 23, 2013, at 9:41 AM, Akihiro Motoki wrote: > Hi Paul, > > > On Wed, Oct 23, 2013 at 9:56 PM, Paul Michali wrote: >> >> Hi guys, >> >> Some questions on VPNaaS… >> >> Can we get

[openstack-dev] data flow for network creation

Hello, I am new to OpenStack. I appreciate if somebody point out the data flow for network creation in OpenStack Neutron. Regards Arash Eghtesadi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailm

Re: [openstack-dev] [Trove] Replication and Clustering API

Galera cluster, in this model would be considered a service type or datastore type not a replication type. All clusters would be treated this way. The method of replication is really not important to the api IMO but rather the contract should reflect what host has copies of data (in whole or in p

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

On Wed, Oct 23, 2013 at 8:47 AM, Sean Dague wrote: > On 10/23/2013 10:40 AM, John Griffith wrote: > >> >> >> >> On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague > > wrote: >> >> Dave Kranz has been building a system so that we can ensure that >> during a Tempest run serv

Re: [openstack-dev] Gerrit tools

"Daniel P. Berrange" writes: > Actually, from my POV, the neat one there is the qgerrit script - I had > no idea you could query this info so easily. FYI the query syntax for SSH and the web is the same, so you can also make a bookmark for a query like that. The search syntax is here: https:

Re: [openstack-dev] [Trove] Replication and Clustering API

Would it be beneficial in this case to extend the meta-data model of the replication contract to allow for additional key/value pairs in the meta-data to account for DB specific and/or replication and clustering specific meta-data? -Daniel From: Daniel Salinas Reply-To: OpenStack Development M

Re: [openstack-dev] Testing before sending for review

On 2013-10-23 04:29, Rosa, Andrea (HP Cloud Services) wrote: Hi 2. Before submitting the new patch for review it's better to run unit tests (tox -epy27) and pep8 check (tox -epep8) Instead of pep8 I think you should run flake8 we moved to that some months ago[1]. Usually I find always useful

Re: [openstack-dev] Gerrit tools

Wow, awesomeness! I'll put out a 0.2 on pypi when u are ready with that, very cool. Sent from my really tiny device... > On Oct 23, 2013, at 7:12 AM, "Daniel P. Berrange" wrote: > >> On Sun, Oct 20, 2013 at 05:01:23AM +, Joshua Harlow wrote: >> I created some gerrit tools that I think othe

Re: [openstack-dev] [keystone] updating password user_crud vs credentials

On 10/23/2013 09:14 AM, Chmouel Boudjnah wrote: Hello, If i understand correctly (and I may be wrong) we are moving away from user_crud to use /credentials for updating password including ec2. The credentials facility was implemented in this blueprint : https://blueprints.launchpad.net/keyst

Re: [openstack-dev] Gerrit tools

On Wed, Oct 23, 2013 at 03:05:32PM +, James E. Blair wrote: > "Daniel P. Berrange" writes: > > > Actually, from my POV, the neat one there is the qgerrit script - I had > > no idea you could query this info so easily. > > FYI the query syntax for SSH and the web is the same, so you can also

[openstack-dev] [Nova] Blueprint review process

Greetings, At the last Nova meeting we started talking about some updates to the Nova blueprint process for the Icehouse cycle. I had hoped we could talk about and finalize this in a Nova design summit session on "Nova Project Structure and Process" [1], but I think we need to push forward on fin

Re: [openstack-dev] [keystone] updating password user_crud vs credentials

On Wed, Oct 23, 2013 at 8:14 AM, Chmouel Boudjnah wrote: > Hello, > > If i understand correctly (and I may be wrong) we are moving away from > user_crud to use /credentials for updating password including ec2. The > credentials facility was implemented in this blueprint : > > https://blueprints.la

Re: [openstack-dev] [Trove] Replication and Clustering API

Do you have any specific examples on that? I'm not opposed to adding more to the replication contract but I want to be sure that it is important to the end user of the api. I can see some edge cases for saying "replication_type": "async-master-slave" or something like that. This becomes more imp

Re: [openstack-dev] [keystone] updating password user_crud vs credentials

On 10/23/2013 11:35 AM, Dolph Mathews wrote: On Wed, Oct 23, 2013 at 8:14 AM, Chmouel Boudjnah mailto:chmo...@enovance.com>> wrote: Hello, If i understand correctly (and I may be wrong) we are moving away from user_crud to use /credentials for updating password including ec2.

Re: [openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

So is it at 8 AM PDT, or 10 AM PDT? Thanks, ~Sumit. On Wed, Oct 23, 2013 at 4:18 AM, Eugene Nikanorov wrote: > Hi Sam, > > Yes, I meant 8:00AM PDT, 10:00-12:00 AM PDT works for me as well. > Looks like this time is not convenient for Yongsheng, unfortunately, but I > think we should stick to th

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

Besides the strategy of selecting the default behavior. Let me share with you my ideas of configuration management in Trove and how the datastore concept can help with that. Initially there was only one database and all configuration was in one config file. With adding of new databases, heat prov

Re: [openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

So currently it moves to 10AM PDT Thanks, Eugene. On Wed, Oct 23, 2013 at 9:07 PM, Sumit Naiksatam wrote: > So is it at 8 AM PDT, or 10 AM PDT? > > Thanks, > ~Sumit. > > > On Wed, Oct 23, 2013 at 4:18 AM, Eugene Nikanorov > wrote: > >> Hi Sam, >> >> Yes, I meant 8:00AM PDT, 10:00-12:00 AM PDT

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Dear Steve and All, If I may add up on this already busy thread to share our experience with using Heat in large and complex software deployments. I work on a project which precisely provides additional value at the articulation point between resource orchestration automation and configurati

[openstack-dev] Glance Client - new blue print

Hi *, I have uploaded a new blue print regarding Glance Client. The basic idea is to make the schema validation check configurable (do validate the schemas or not) or let the user decide whether to skip the validation or not. The blue print can be viewed here: https://blueprints.launchpad.net/

Re: [openstack-dev] [nova] EC2 Compatibility metadata on config drive, fixed IP info

On Tue, Oct 22, 2013 at 7:35 PM, wrote: > Date: Wed, 23 Oct 2013 10:21:00 +1100 > From: Michael Still > To: OpenStack Development Mailing List > > Subject: Re: [openstack-dev] [nova] EC2 Compatibility metadata on > config drive, fixed IP info > Message-ID: > no0zzljhagph

[openstack-dev] RFC - Icehouse logging harmonization

One of the efforts that we're working on from the QA team is tooling that ensures we aren't stack tracing into our test logs during normal tempest runs. Random stack traces are scary to cloud admins consuming OpenStack logs, and exceptions in the logs should really be exceptional events (and in

[openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

Hi folks! In the images api, we depend on iso8601 to parse some dates and times. Recently, since version 0.1.4, python-iso8601 added support for a few more formats, and we finally got some other issues nailed down by 0.1.8. Maybe the fact that these formats weren't supported before was a bug. I do

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Excerpts from Patrick Petit's message of 2013-10-23 10:58:22 -0700: > Dear Steve and All, > > If I may add up on this already busy thread to share our experience with > using Heat in large and complex software deployments. > Thanks for sharing Patrick, I have a few replies in-line. > I work on

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

On Oct 23, 2013, at 10:54 AM, Ilya Sviridov wrote: > Besides the strategy of selecting the default behavior. > > Let me share with you my ideas of configuration management in Trove and how > the datastore concept can help with that. > > Initially there was only one database and all configurati

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Hi Patric, Thank you for such great post! This is very close to the vision I've tried to propose earlier on software orchestration thread and I'm glad other people concern about the same issues. However the problem the problem with PaaS-like approached it that they currently on a little bit higher

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

Hi, Why not use python-dateutil? Regards chuck On Wed, Oct 23, 2013 at 11:34 AM, Mark Washenberger < mark.washenber...@markwash.net> wrote: > Hi folks! > > In the images api, we depend on iso8601 to parse some dates and times. > Recently, since version 0.1.4, python-iso8601 added support for a

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

+1 to option #1 -- dims On Wed, Oct 23, 2013 at 2:34 PM, Mark Washenberger < mark.washenber...@markwash.net> wrote: > Hi folks! > > In the images api, we depend on iso8601 to parse some dates and times. > Recently, since version 0.1.4, python-iso8601 added support for a few more > formats, and

[openstack-dev] Announcing Project Solum

OpenStack, OpenStack has emerged as the preferred choice for open cloud software worldwide. We use it to power our cloud, and we love it. We’re proud to be a part of growing its capabilities to address more needs every day. When we ask customers, partners, and community members about what probl

Re: [openstack-dev] RFC - Icehouse logging harmonization

On Wed, Oct 23, 2013 at 11:20 AM, Sean Dague wrote: > One of the efforts that we're working on from the QA team is tooling that > ensures we aren't stack tracing into our test logs during normal tempest > runs. Random stack traces are scary to cloud admins consuming OpenStack > logs, and exception

Re: [openstack-dev] [Neutron] FWaaS IceHouse summit prep and IRC meeting

Log from today's meeting: http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-10-23-18.02.log.html Action items for some of the folks included. Please join us for the meeting next week. Thanks, ~Sumit. On Tue, Oct 22, 2013 at 2:00 PM, Sumit Naiksatam wrote: > R

Re: [openstack-dev] RFC - Icehouse logging harmonization

On Wed, Oct 23, 2013 at 1:20 PM, Sean Dague wrote: > One of the efforts that we're working on from the QA team is tooling that > ensures we aren't stack tracing into our test logs during normal tempest > runs. Random stack traces are scary to cloud admins consuming OpenStack > logs, and exception

Re: [openstack-dev] Announcing Project Solum

On 10/23/2013 03:03 PM, Adrian Otto wrote: > OpenStack, > > OpenStack has emerged as the preferred choice for open cloud software > worldwide. We use it to power our cloud, and we love it. We’re proud to > be a part of growing its capabilities to address more needs every > day. When we ask custome

Re: [openstack-dev] RFC - Icehouse logging harmonization

On 24 October 2013 08:14, Dolph Mathews wrote: > > On Wed, Oct 23, 2013 at 1:20 PM, Sean Dague wrote: > > Deprecation warnings! > > Based on the approach we're taking in the patch below, we'll be able to > notate how imminently a feature is facing deprecation. Right now, they're > just landing i

Re: [openstack-dev] RFC - Icehouse logging harmonization

On Wed, Oct 23, 2013 at 1:03 PM, Clark Boylan wrote: > On Wed, Oct 23, 2013 at 11:20 AM, Sean Dague wrote: > > One of the efforts that we're working on from the QA team is tooling that > > ensures we aren't stack tracing into our test logs during normal tempest > > runs. Random stack traces are s

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

On 24 October 2013 07:34, Mark Washenberger wrote: > Hi folks! > > 1) Adopt 0.1.8 as the minimum version in openstack-requirements. > 2) Do nothing (i.e. let Glance behavior depend on iso8601 in this way, and > just fix the tests so they don't care about these extra formats) > 3) Make Glance work

Re: [openstack-dev] RFC - Icehouse logging harmonization

On 24 October 2013 08:28, John Griffith wrote: > So I touched on this a bit in my earlier post but want to reiterate here and > maybe clarify a bit. I agree that cleaning up and standardizing the logs is > a good thing, and particularly removing unhandled exception messages would > be good. What

Re: [openstack-dev] Gerrit tools

Thanks, did some cleanup and pushed a newer version. https://pypi.python.org/pypi/gerrit-view/0.1.1 -Josh On 10/23/13 8:16 AM, "Joshua Harlow" wrote: >Wow, awesomeness! > >I'll put out a 0.2 on pypi when u are ready with that, very cool. > >Sent from my really tiny device... > >> On Oct 23, 20

[openstack-dev] [oslo] team meeting this friday

The Oslo team will be meeting Friday at 1400 UTC in the #openstack-meeting channel on IRC. The main item on the agenda is finishing the plans for fixing the delayed translation feature of gettextutils. See https://wiki.openstack.org/wiki/Meetings/Oslo for more details. Thanks, Doug __

Re: [openstack-dev] RFC - Icehouse logging harmonization

On Wed, Oct 23, 2013 at 3:26 PM, Robert Collins wrote: > On 24 October 2013 08:14, Dolph Mathews wrote: > > > > On Wed, Oct 23, 2013 at 1:20 PM, Sean Dague wrote: > > > > > Deprecation warnings! > > > > Based on the approach we're taking in the patch below, we'll be able to > > notate how immine

Re: [openstack-dev] RFC - Icehouse logging harmonization

On 10/23/2013 03:35 PM, Robert Collins wrote: On 24 October 2013 08:28, John Griffith wrote: So I touched on this a bit in my earlier post but want to reiterate here and maybe clarify a bit. I agree that cleaning up and standardizing the logs is a good thing, and particularly removing unhandle

Re: [openstack-dev] [Neutron] Distributed Virtual Router Discussion

Hello, Swami, I am interested in this topic. Please include me in the discussion. Thanks, Yapeng From: Vasudevan, Swaminathan (PNB Roseville) [mailto:swaminathan.vasude...@hp.com] Sent: Tuesday, October 22, 2013 2:50 PM To: cloudbengo; Artem Dmytrenko; yong sheng gong (gong...@unitedstack.com);

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

On Wed, Oct 23, 2013 at 2:30 PM, Robert Collins wrote: > On 24 October 2013 07:34, Mark Washenberger > wrote: > > Hi folks! > > > > 1) Adopt 0.1.8 as the minimum version in openstack-requirements. > > 2) Do nothing (i.e. let Glance behavior depend on iso8601 in this way, > and > > just fix the te

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Hi, Looking through the thread I mentioned couple definitions of software orchestration. I would like to summarize definitions before we go to deep technical discussion about actual implementation. There are two major areas and approaches covered by software orchestration: *Software component

Re: [openstack-dev] VPNaaS questions...

Hi Paul I rebased the patch, and working on unit testing too https://review.openstack.org/#/c/41827/ 2013/10/23 Paul Michali : > See PCM: in-line. > > > PCM (Paul Michali) > > MAIL p...@cisco.com > IRC pcm_ (irc.freenode.net) > TW @pmichali > > On Oct 23, 2013, at 9:41 AM, Akihiro Motoki w

Re: [openstack-dev] Announcing Project Solum

On 10/23/2013 12:03 PM, Adrian Otto wrote: > Along with eBay, RedHat, Ubuntu/Canonical, dotCloud/Docker, Cloudsoft, > and Cumulogic, we at Rackspace are happy to announce we have started > project Solum as an OpenStack Related open source project. Solum is a > community-driven initiative currently

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

John Griffith wrote: On Wed, Oct 23, 2013 at 8:47 AM, Sean Dague mailto:s...@dague.net>> wrote: On 10/23/2013 10:40 AM, John Griffith wrote: On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague mailto:s...@dague.net> >> wrote: Dave Kranz has been buil

Re: [openstack-dev] [Neutron] tempest failure: No more IP addresses available on network

> Hi, > > I just noticed several number of neutron check > (tempest-devstack-vm-neutron-isolated) fails with the same error: > "No more IP addresses available on network". > This errors suddenly starts to occur from yesterday. > > I checked there is any commit merge around the time when this fail

Re: [openstack-dev] Announcing Project Solum

On 10/23/2013 03:03 PM, Adrian Otto wrote: > OpenStack, > > OpenStack has emerged as the preferred choice for open cloud software > worldwide. We use it to power our cloud, and we love it. We’re proud to > be a part of growing its capabilities to address more needs every > day. When we ask custo

[openstack-dev] [Solum] Integration with Murano proposal

Hi, I am really excited to see Solum announcement. This is a fantastic idea to create developer friendly environment for application creation on OpenStack. I believe that this developer friendly environment will attract a lot of developers who want to write software for OpenStack platform. I thin

Re: [openstack-dev] [Neutron] tempest failure: No more IP addresses available on network

Hi folks This patch was the culprit, so we have reverted it. https://review.openstack.org/#/c/53459/1 (Note, this is revert of revert ) However even if it is reverted, the error happens http://logstash.openstack.org/index.html#eyJzZWFyY2giOiJcIklwQWRkcmVzc0dlbmVyYXRpb25GYWlsdXJlQ2xpZW50OiBObyBtb3

Re: [openstack-dev] Disable async network allocation

Hi Phil 2013/10/21 Day, Phil : > Hi Folks, > > > > I’m trying to track down a couple of obsecure issues in network port > creation where it would be really useful if I could disable the async > network allocation so that everything happens in the context of a single > eventlet rather than two (and

Re: [openstack-dev] Neutron - an issue regarding what API to follow

Hi GROSZ, Akihiro Yes, the wiki is only for discussion. Please see the official API docs. I updated the wiki page as OUTDATED. https://wiki.openstack.org/wiki/Neutron/VPNaaS#OUTDATED Thank you for your pointing out. Best Nachi 2013/10/21 Akihiro Motoki : > Hi, > > The API document is the offic

Re: [openstack-dev] Disable async network allocation

On Wed, Oct 23, 2013 at 4:37 PM, Nachi Ueno wrote: > Hi Phil > > 2013/10/21 Day, Phil : > > Hi Folks, > > > > > > > > I’m trying to track down a couple of obsecure issues in network port > > creation where it would be really useful if I could disable the async > > network allocation so that every

Re: [openstack-dev] Disable async network allocation

On Oct 23, 2013, at 5:56 PM, Aaron Rosen wrote: > I believe he's referring to: > https://github.com/openstack/nova/blob/master/nova/network/model.py#L335 > https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1211 I found some more background on the feature (not configurable)

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

On 10/23/2013 05:08 PM, Rochelle.Grober wrote: John Griffith wrote: On Wed, Oct 23, 2013 at 8:47 AM, Sean Dague > wrote: On 10/23/2013 10:40 AM, John Griffith wrote: On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague mailto:s...@dague.net>

Re: [openstack-dev] [Neutron] tempest failure: No more IP addresses available on network

On 10/23/2013 07:22 PM, Nachi Ueno wrote: > Hi folks > > This patch was the culprit, so we have reverted it. > https://review.openstack.org/#/c/53459/1 (Note, this is revert of revert ) > > However even if it is reverted, the error happens > http://logstash.openstack.org/index.html#eyJzZWFyY2giOi

[openstack-dev] [savanna] team meeting Oct 24 1800 UTC

Hi folks, We'll be having the Savanna team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_October.2C_24 http://www.timeanddate.com/worldclock/fixedtime.html?msg=Savanna+Meeting&iso=20131024T18 Sincerely yours, Serg

Re: [openstack-dev] [Neutron][LBaaS] LBaaS plans for Icehouse

Hi, We have submitted the following LBaaS related BPs: https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-extra-features I can't attend the m