Re: [openstack-dev] neutron metadata-agent HA

ha and dvr don't play nicely today though, and for our use case, if given the choice, dvr looks more appealing then l3-ha. Thanks for the advice. We may just go with the pacemaker option with dvr taking most of the load off of the network node until l3+ha & dvr all play nice. Thanks, Kevin

[openstack-dev] [openstack][magnum] Quota for Magnum Resources

Hi All, Currently, it is possible to create unlimited number of resource like bay/pod/service/. In Magnum, there should be a limitation for user or project to create Magnum resource, and the limitation should be configurable[1]. I proposed following design :- 1. Introduce new table

Re: [openstack-dev] [Neutron][LBaaS] Regarding v2 LoadBalancer's status(es)

Hi Bryan, On Mon, 2015-12-14 at 15:19 -0600, Bryan Jones wrote: > Hi All, > > I had a few issues/questions regarding the statuses > (provisioning_status and operating_status) of a v2 LoadBalancer. To > preface these, I am working on the LBaaS v2 support in Heat. > > The first question regards

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

A question but what filtering/scheduling would be done in which place; any thoughts on the breakup between nova and ironic? If say ironic knows about all baremetal resources and nova doesn't know about them, then what kind of decisions can nova make during scheduling time? I guess the same

[openstack-dev] 答复: [keystone] Is "domain" a mapping to real-world cloud tenant?

Hi Dolph, Here it is, http://profsandhu.com/confrnc/misconf/nss14-preprint-bo.pdf You may have a look at it and see if it’s reasonable. Darren 发件人: Dolph Mathews [mailto:dolph.math...@gmail.com] 发送时间: 2015年12月15日 6:10 收件人: OpenStack Development Mailing List (not

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

On Mon, Dec 14, 2015 at 04:15:42PM -0800, James Penick wrote: > I'm very much against it. > > In my environment we're going to be depending heavily on the nova > scheduler for affinity/anti-affinity of physical datacenter constructs, > TOR, Power, etc. Like other operators we need to also have a

Re: [openstack-dev] [docs][stable][ironic] Stable branch docs

On Mon, Dec 14, 2015 at 06:42:13AM -0800, Jim Rollenhagen wrote: > Hi all, > > In the big tent, project teams are expected to maintain their own > install guides within their projects' source tree. There's a > conversation going on over in the docs list[1] about changing this, but > in the

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

I'm very much against it. In my environment we're going to be depending heavily on the nova scheduler for affinity/anti-affinity of physical datacenter constructs, TOR, Power, etc. Like other operators we need to also have a concept of host aggregates and availability zones for our baremetal as

[openstack-dev] [kolla] recent MIA from Kolla PTL

Hey folks, Normally I wouldn't talk about health problems on a public mailing list, but its not super private - just teeth problems. I wanted to explain why I have been MIA for 4 weeks. I had a tooth infection, which turned into a root canal, which turned into a failed root canal, which

Re: [openstack-dev] [docs][stable][ironic] Stable branch docs

On Tue, Dec 15, 2015 at 11:05:16AM +1100, Tony Breeds wrote: > On Mon, Dec 14, 2015 at 06:42:13AM -0800, Jim Rollenhagen wrote: > > Hi all, > > > > In the big tent, project teams are expected to maintain their own > > install guides within their projects' source tree. There's a > > conversation

Re: [openstack-dev] [docs][stable][ironic] Stable branch docs

On Mon, Dec 14, 2015 at 05:33:14PM -0800, Jim Rollenhagen wrote: > Perfect! Thanks for pointing that out. :) > > As a note, I don't actually see the new note on the page you linked, > though I do see it in the git repo. Strange. Yeah strange. I'll look into that. Yours Tony.

[openstack-dev] Cross-Project Meeting SKIPPED, Tue Dec 15th, 21:00 UTC

Hi all!  We will be skipping the cross-project meeting since there are no agenda items to discuss, but someone can add one [1] to call a meeting next time.  We also have a new meeting channel which is #openstack-meeting-cp where the cross-project meeting will now take place at it's usual time

Re: [openstack-dev] [Cinder] Is there anyone truly working on this issue https://bugs.launchpad.net/cinder/+bug/1520102?

On 11/12, mtanino wrote: > Hi Thang, Vincent, > > I guess the root cause is that finish_volume_migration() still > handles a volume as a dictionary instead of volume object and > the method returns dict volume. > > And then, 'rpcapi.delete_volume()' in migrate_volume_completion() > tries to

Re: [openstack-dev] [Fuel] Nominate Bulat Gaifulin for fuel-web & fuel-mirror cores

Hi, +1 from me to Bulat. On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky wrote: > Hi Fuelers, > > I'd like to nominate Bulat Gaifulin [1] for > > * fuel-web-core [2] > * fuel-mirror-core [3] > > Bulat's doing a really good review with detailed feedback and he's a >

[openstack-dev] [ceilometer] status of distil?

While I was trying to submit patches for projects that had old keystoneclient references (distil was one of the projects), I noticed that there hasn't been much action on this project [0]. It's been a year since a commit [1], no releases [2], and I can't submit a patch since the .gitreview file

Re: [openstack-dev] OpenStack-Announce List

... and back to this thread after a few weeks :) The conclusions I saw were: * Audience for openstack-announce should be "users/non-dev" * Service project releases announcements are good * Client library release announcements good * Security announcements are good * Internal library

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Marian Horban said on Thu, Dec 10, 2015 at 03:33:26PM +0200: > Are there some progress with reloading configuration? > Could we restore oslo-config review https://review.openstack.org/#/c/213062/ > ? Hi Marian, I'm also working on this, you might find https://review.openstack.org/#/c/251471/

Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines

Sean McGinnis wrote: > On Thu, Dec 10, 2015 at 06:20:44PM +, Flavio Percoco wrote: >> >> With the new home for the release schedule, and it being a good place >> for projects to add their own deadlines as well, I believe it would be >> good for people that use calendars to have these .ics

Re: [openstack-dev] [Fuel] Nominate Bulat Gaifulin for fuel-web & fuel-mirror cores

+1. Aleksey Kasatkin On Mon, Dec 14, 2015 at 12:49 PM, Vladimir Sharshov wrote: > Hi, > > +1 from me to Bulat. > > On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky > wrote: > >> Hi Fuelers, >> >> I'd like to nominate Bulat Gaifulin [1] for >>

[openstack-dev] [mistral] Mistral team meeting reminder

Hi, This is a reminder that we’ll have a team meeting today at #openstack- meeting at 16.00 UTC. Agenda: - Review action items - Current status (progress, issues, roadblocks, further plans) - M-2 status and planning - Open discussion -- Best Regards, Nikolay

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

On 2015-12-14 13:12, Igor Kalnitsky wrote: > My opinion here is that I don't like that we're going to build and > maintain one more custom package (just take a look at this patch [4] > if you don't believe me), but I'd like to hear more opinion here. > > Thanks, > Igor > > [1]

Re: [openstack-dev] [Fuel] Separate master node provisioning and deployment

Vladimir, Thanks for raising this question. I totally support idea of separating provisioning and deployment steps. I believe it'll simplify a lot of things. However I have some comments regarding this topic, see them inline. :) > For a package it is absolutely normal to throw a user dialog.

Re: [openstack-dev] [Fuel] Configuration management for Fuel 7.0

Dmitry, Q1. Yes. > where do you plan to actually perform settings manipulation? It was one of the critical blockers. Most of the settings are baked inside fuel-library. Your feature [1] partially fixes this BTW. Which is good. Partially, because only limited number of tasks has defined

Re: [openstack-dev] [Fuel] Nominate Bulat Gaifulin for fuel-web & fuel-mirror cores

+1 On Mon, Dec 14, 2015 at 3:05 PM, Aleksey Kasatkin wrote: > +1. > > > Aleksey Kasatkin > > > On Mon, Dec 14, 2015 at 12:49 PM, Vladimir Sharshov < > vshars...@mirantis.com> wrote: > >> Hi, >> >> +1 from me to Bulat. >> >> On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky

Re: [openstack-dev] [Fuel] Experimental Task Based Deployment Landed into Master

+1 It's really good job folks. On Sat, Dec 12, 2015 at 2:25 AM, Vladimir Kuklin wrote: > Fuelers > > I am thrilled to announce that task based deployment engine [0] has been > just merged into Fuel master. We checked it against existing BVT test cases > for regressions as

Re: [openstack-dev] [Fuel] Multiple repos UX

Hi, Vladimir, Please be informed that we'll have to also make an appropriate changes on the fuel-agent side. But yes, it's possible to do it before SCF. 2015-12-11 20:05 GMT+03:00 Vladimir Kozhukalov : > If there are no any objections, let's do fix fuel-menu ASAP. As

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

Tox 2.3.1 was released on pypi a few minutes ago, and it fixes this issue. Jordan On Mon, Dec 14, 2015 at 12:55 AM, Robert Collins wrote: > On 13 December 2015 at 03:20, Yuriy Taraday wrote: > > Tempest jobs in all our projects seem to become

Re: [openstack-dev] OpenStack-Announce List

On 14/12/15 19:33, Thierry Carrez wrote: Tom Fifield wrote: ... and back to this thread after a few weeks :) The conclusions I saw were: * Audience for openstack-announce should be "users/non-dev" * Service project releases announcements are good * Client library release announcements good *

[openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hi Fuelers, As you might know, recently we moved to CentOS 7 and as a result we got a small regression with PostgreSQL: * Fuel 7 runs on CentOS 6.6 and uses manually built PostgreSQL 9.3. * Fuel 8 runs on CentOS 7 and uses PostgreSQL 9.2 from CentOS upstream repos. There are different opinions

Re: [openstack-dev] [nova][serial-console-proxy]

Hi Markus, Thanks a lot for a detailed document. I had a problem with installing websocket but using the git repo u shared, I could install successfully and got a console. Regards, Prathyusha On Mon, Dec 14, 2015 at 11:34 PM, Markus Zoeller wrote: > Prathyusha Guduri

Re: [openstack-dev] [Group Based Policy] [Policy] [GBP]

Hi, Thanks for your question, but we haven’t explored this option. We will be happy to discuss this and provide any help/pointers you may need. Please feel free to join our weekly IRC meeting and/or drop into the #openstack-gbp channel to discuss further. ~Sumit. On Sun, Dec 13, 2015 at 9:10 AM,

Re: [openstack-dev] [Fuel] Separate master node provisioning and deployment

> One of potential disadvantages is that it is harder to track package > dependencies, but I think > a deployment script should be a root of the package dependency tree. That's something I'd try to avoid. Let's be close to distro upstream practice. I never saw something like "fuel-deploy" that

Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API

On 12/11/2015 08:25 PM, Alexander Tivelkov wrote: Hi folks! As it was decided during the Mitaka design summit, we are separating the experimental Artifact Repository API from the main Glance API. This API will have a versioning sequence independent from the main Glance API and will be run as a

Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API

On Mon, Dec 14, 2015 at 9:28 AM, Ian Cordasco wrote: > > > On 12/14/15, 02:18, "Kuvaja, Erno" wrote: > > >> -Original Message- > >> From: McLellan, Steven > >> Sent: Friday, December 11, 2015 6:37 PM > >> To: OpenStack Development Mailing List

Re: [openstack-dev] [midonet] Split up python-midonetclient

On Tue, Dec 15, 2015 at 12:02 AM, Ryu Ishimoto wrote: > On Mon, Dec 14, 2015 at 6:34 PM, Sandro Mathys wrote: >> On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote: >>> >> Honestly, I don't think this discussion is leading anywhere. >>

Re: [openstack-dev] [nova] Volume attachment APIs CRUD inconsistencies

Thanks. So it looks like os_volume-attachments has now been linked into the 2.1 doc. The lack of documentation for the PUT / update attachment doc was also noted on the etherpad. So my only remaining questions revolve around the dual and differing API implementations of the read volume

Re: [openstack-dev] [ceilometer] status of distil?

On 12/14/2015 10:01 AM, Steve Martinelli wrote: While I was trying to submit patches for projects that had old keystoneclient references (distil was one of the projects), I noticed that there hasn't been much action on this project [0]. It's been a year since a commit [1], no releases [2], and I

Re: [openstack-dev] [nova][serial-console-proxy]

Hi Tony, Your reply gave me a hint that nova-consoleauth service must be running. I did not start that service before so no token authentication was done. Now after starting the service, $nova get-serial-console vm-check-6

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

On 12/14/2015 08:20 AM, Cheng, Yingxin wrote: > Hi All, > > > > When I was looking at bugs related to race conditions of scheduler > [1-3], it feels like nova scheduler lacks sanity checks of schedule > decisions according to different situations. We cannot even make sure > that some fixes

Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API

On 12/11/2015 08:51 PM, Alexander Tivelkov wrote: Hi Steve, Thanks for the note on port. Any objections on glare using 9494 then? Anyone? Yes, I object to 9494. There should be no need to use any custom port for Glare's API service. Just use 80/443, which are HTTP(S)'s standard ports. It

Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API

On 12/14/15, 02:18, "Kuvaja, Erno" wrote: >> -Original Message- >> From: McLellan, Steven >> Sent: Friday, December 11, 2015 6:37 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service

[openstack-dev] [cinder] Custom fields for versioned objects

Hi everyone, I have a change submitted that lays the groundwork for using custom enums and fields that are used by versioned objects [1]. These custom fields allow for verification on a set of valid values, which prevents the field from being mistakenly set to something invalid. These custom

Re: [openstack-dev] [midonet] Split up python-midonetclient

On Mon, Dec 14, 2015 at 6:34 PM, Sandro Mathys wrote: > On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote: >> > Honestly, I don't think this discussion is leading anywhere. > Therefore, I'd like to request a decision by the MidoNet PTL as per > [1]. I

Re: [openstack-dev] [MidoNet] Fwd: [MidoNet-Dev] Sync virtual topology data from neutron DB to Zookeeper?

Hi Nick, We have already designed the data sync feature[1], but this development was suspended temporarily in favor of completing the v5.0 development of MidoNet. We will be resuming development work on this project soon (with high priority). It sounds to me like you need a completed, mature

Re: [openstack-dev] [ansible] One or more undefined variables: 'dict object' has no attribute 'bridge'

The port binding issues are usually related to a neutron physical interface mapping issue however based on your previous config I don't think that was the problem. If you're deploying Liberty/Master(Mitaka) there was was a fix that went in that resolved an issue within neutron and the use of

Re: [openstack-dev] [openstack-ansible] Mid Cycle Sprint

FYI it looks like Ansible Fest London is Feb 18th. On Thu, Dec 10, 2015 at 1:29 PM, Amy Marrich wrote: > I'd be game to join in if it's in San Antonio. While I'd love to go to > London I don't think I'd make. > > Like Major I'd like to see some doc work. > > Amy

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

> -Original Message- > From: Nikola Đipanov [mailto:ndipa...@redhat.com] > Sent: Monday, December 14, 2015 11:11 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race > conditions)? > > On

Re: [openstack-dev] [Neutron][LBaaS] Regarding v2 LoadBalancer's status(es)

Looks like that is only for v1 though. On Tue, 2015-12-15 at 05:38 +, Phillip Toohill wrote: > >Yeah this needs to be better documented. I would say all of those > >statuses in the docs pertain to provisioning_status, except for > >INACTIVE, which I'm actually not sure where that is being

Re: [openstack-dev] [Neutron][LBaaS] Regarding v2 LoadBalancer's status(es)

>Yeah this needs to be better documented. I would say all of those >statuses in the docs pertain to provisioning_status, except for >INACTIVE, which I'm actually not sure where that is being used. ... There is this patch to utilize the INACTIVE status: https://review.openstack.org/#/c/255875/

Re: [openstack-dev] [Neutron] Call for review focus

On Mon, Dec 14, 2015 at 12:41 PM, Rossella Sblendido wrote: > On 11/25/2015 11:05 PM, Assaf Muller wrote: >> We could then consider running the script automatically on a daily >> basis and publishing the >> resulting URL in a nice bookmarkable place. > > An update on this.

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Can we have nested project quotas in from the beginning ? Nested projects are in Keystone V3 from Kilo onwards and retrofitting this is hard work. For details, see the Nova functions at https://review.openstack.org/#/c/242626/. Cinder now also has similar functions. Tim From: Vilobh

[openstack-dev] [vitrage] Next vitrage meeting

Hi, Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress from last week * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

[openstack-dev] [QA][Tempest] Asking for reviews from Tempest cores.

Hi Tempest folks, https://review.openstack.org/#/c/195443/ I am asking you to take a review on this patch, which is the integration test for volume retype with migration in cinder. It has been taken quite a while and quite some cycles to get mature. It is a very important test for volume

[openstack-dev] FW: [vitrage] Gerrit Upgrade 12/16

Hi, Reminder: Gerrit upgrade is scheduled for tomorrow at 17:00 UTC. Ifat. -Original Message- From: Spencer Krum [mailto:n...@spencerkrum.com] Sent: Monday, December 14, 2015 9:53 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Gerrit Upgrade 12/16 This is a

Re: [openstack-dev] [ceilometer] status of distil?

wasn't aware this project existed. i've contacted flwang. just for reference, for those that extend Telemetry projects, it's good to promote it here: https://wiki.openstack.org/wiki/Telemetry#Externally_Managed On 14/12/2015 4:09 AM, Andreas Jaeger wrote: On 12/14/2015 10:01 AM, Steve

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On 2015-12-14 12:18:07 +0100 (+0100), Jordan Pittier wrote: > Tox 2.3.1 was released on pypi a few minutes ago, and it fixes > this issue. Thanks for testing it--I've gone ahead and unblocked our image update automation. If anyone notices new abnormalities from tox, please let the Infra team

[openstack-dev] [Fuel] Dropping Python 2.6

Fuelers, Since Mitaka OpenStack Infra has no resources to test python 2.6 support so the corresponding jobs are not running anymore. Since Fuel master node is on CentOS 7 now, let’s drop Python 2.6 support in Fuel. - romcheg signature.asc Description: Message signed with OpenPGP using

Re: [openstack-dev] [nova] Microversions support for extensions without Controller

Hi, Alexandre, Yes, I think we need pass the version into `server_update` extension point. My irc nick is alex_xu, let me know if you have any trouble with this. Thanks Alex 2015-12-13 2:34 GMT+08:00 Alexandre Levine : > Hi all, > > os-user-data extension implements

Re: [openstack-dev] [MidoNet] Fwd: [MidoNet-Dev] Sync virtual topology data from neutron DB to Zookeeper?

Hi Li, Sorry for the late reply. Unrelated point: please note that we've moved the mailing lists to Openstack infra (openstack-dev@lists.openstack.org - I'm ccing the list here). At the moment we don't support syncing the full Neutron DB, there has been work done for this that would allow this

Re: [openstack-dev] [Fuel] Dropping Python 2.6

Sorry for duplicating discussions. os-dev subsription was broken for me for a while so I missed a lot :( > 14 груд. 2015 р. о 15:23 Evgeniy L написав(ла): > > Hi Roman, > > We've discussed it [1], so +1 > > [1] >

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On 2015-12-14 12:55:45 +1300 (+1300), Robert Collins wrote: [...] > my suggestion would be that we either make tox pip installed > during jobs (across the board), so that we can in fact control it > with upper-constraints, That's a lot of added complication to deal with possible regressions in

Re: [openstack-dev] [Fuel] Dropping Python 2.6

+1 On Mon, Dec 14, 2015 at 3:05 PM, Roman Prykhodchenko wrote: > Fuelers, > > Since Mitaka OpenStack Infra has no resources to test python 2.6 support > so the corresponding jobs are not running anymore. Since Fuel master node > is on CentOS 7 now, let’s drop Python 2.6 support

Re: [openstack-dev] [Fuel] Dropping Python 2.6

Hi Roman, We've discussed it [1], so +1 [1] https://openstack.nimeyo.com/67521/openstack-dev-fuel-dropping-python2-6-compatibility On Mon, Dec 14, 2015 at 5:05 PM, Roman Prykhodchenko wrote: > Fuelers, > > Since Mitaka OpenStack Infra has no resources to test python 2.6

Re: [openstack-dev] [Fuel][QA] New version of fuel-devops (2.9.15)

+openstack-dev On 12/14/2015 02:40 PM, Dennis Dmitriev wrote: > Hi All, > > We have updated the version of 'fuel-devops' framework to the 2.9.15. > > This is mainly bugfix update. > > Version 2.9.15 will be updated on our product CI during next several days. > > Changes since 2.9.13: > > -

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-12-15 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - Subteam meeting during the vacation period - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [Fuel] Separate master node provisioning and deployment

> Meantime we can provide fuel-menu which will become a configuration > gate for different subprojects. Perhaps we could consider to use > pluggable approach, so each component will export plugin for fuel-menu > with own settings. fuel-menu could be a configuration gate for fuel deployment script

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hi, > Downgrading for no reason could bring us to big trouble and bad user experience +1 to this. Let's keep PostgreSQL 9.3. Regards, Alex On Mon, Dec 14, 2015 at 2:04 PM, Artem Silenkov wrote: > Hello! > > Vote for update. > > 1. We have already shipped 9.3 in

[openstack-dev] [puppet] weekly meeting #63

Hello! Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151215 See you there! -- Emilien Macchi signature.asc Description: OpenPGP digital signature

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hello! Vote for update. 1. We have already shipped 9.3 in fuel-7.0. Downgrading such complicated package without any reason is not good thing at all. User experience could suffer a lot. 2. The next reason is tests. We have tested only 9.3, 9.2 was not tested at all. I'm sure we could bring

[openstack-dev] [docs][stable][ironic] Stable branch docs

Hi all, In the big tent, project teams are expected to maintain their own install guides within their projects' source tree. There's a conversation going on over in the docs list[1] about changing this, but in the meantime... Ironic (and presumably other projects) publish versioned

Re: [openstack-dev] [docs][stable][ironic] Stable branch docs

On 12/14/2015 03:42 PM, Jim Rollenhagen wrote: Hi all, In the big tent, project teams are expected to maintain their own install guides within their projects' source tree. There's a conversation going on over in the docs list[1] about changing this, but in the meantime... Ironic (and

Re: [openstack-dev] [midonet] Split up python-midonetclient

On Tue, Dec 15, 2015 at 1:00 AM, Sandro Mathys wrote: > On Tue, Dec 15, 2015 at 12:02 AM, Ryu Ishimoto wrote: > > So if I understand you correctly, you suggest: > 1) the (midonet/internal) low level API stays where it is and will > still be called

Re: [openstack-dev] OpenStack-Announce List

On Mon, Dec 14, 2015 at 6:28 AM, Tom Fifield wrote: > On 14/12/15 19:33, Thierry Carrez wrote: > >> Tom Fifield wrote: > > * Do SDK releases fit on -announce? >>> >> >> I guess they could -- how many of those are we expecting ? >> >> > So far it looks close to zero emails :)

[openstack-dev] [puppet] [Backport Request] GPFS Cinder module to Kilo branch

Hello, Please could you backport the following commit: 2d983e20b0015ed685a874bb6117261dc1af5661 to the puppet-cinder Kilo branch? Thank you -- Christopher Brown __ OpenStack Development Mailing List (not for usage

[openstack-dev] [Neutron] Gate failure with grenade

Hi folks, Something snuck in past the gate last night [1]. Please stop rechecking and pushing in the merge queue until the matter is resolved. I will follow up with details, if someone knows more, please find me on IRC. Thanks, Armando [1]

Re: [openstack-dev] [nova][cinder] what are the key errors with volume detach

On 10/12/15 14:42, Sean Dague wrote: > On 12/02/2015 12:37 PM, Rosa, Andrea (HP Cloud Services) wrote: >> Hi >> >> thanks Sean for bringing this point, I have been working on the change and >> on the (abandoned) spec. >> I'll try here to summarize all the discussions we had and what we decided.

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

On 13 December 2015 at 23:01, Kevin Benton wrote: > Yes, as I'm starting to understand the use case, I think it would actually > make more sense to add an AZ-network mapping table. Then whatever > implementation can populate them based on the criteria it is using > (reference

Re: [openstack-dev] neutron metadata-agent HA

What about the case where your not running ha routers? Should you still run more then one? Thanks, Kevin From: Assaf Muller [amul...@redhat.com] Sent: Saturday, December 12, 2015 12:44 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [ansible] One or more undefined variables: 'dict object' has no attribute 'bridge'

I am using the liberty branch. Unfortunately this did not help, I get the same error. I also don't understand where the neutron service should run. This is the output on my compute node: root@os-compute-1:~# ps aux | grep neutron root 18782 0.0 0.0 11748 2232 pts/0S+ 17:56 0:00

Re: [openstack-dev] [nova][cinder] what are the key errors with volume detach

On 10/12/15 15:29, Matt Riedemann wrote: >> In a simplified view of a detach volume we can say that the nova code >> does: >> 1 detach the volume from the instance >> 2 Inform cinder about the detach and call the terminate_connection on >> the cinder API. >> 3 delete the dbm recod in the nova

[openstack-dev] [mistral] Mistral team meeting minutes 12/14/2015

Hi, Thank you guys to join us today! Meeting minutes - http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-14-16.01.html Meeting full log - http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-14-16.01.log.html Best Regards, Nikolay

Re: [openstack-dev] [midonet] Split up python-midonetclient

+1 I think it is good compromise. Thanks Ryu! I understand the CLI will belong to the external part. I much prefer to have it in a separate project rather than into the plugin. Even if the code is tiny. If you will want to just do midonet calls for debugging or check the MidoNet virtual

Re: [openstack-dev] [Cinder] Is there anyone truly working on this issue https://bugs.launchpad.net/cinder/+bug/1520102?

Thank you for the explanation, Gorka! Mitsuhiro On 12/14/2015 05:00 AM, Gorka Eguileor wrote: On 11/12, mtanino wrote: Hi Thang, Vincent, I guess the root cause is that finish_volume_migration() still handles a volume as a dictionary instead of volume object and the method returns dict

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hi, If we can stick with upstream PostgresSQL that would be really nice. Otherwise security updates and regular package update will be a burden of package maintainers. Ideally we should have as less forked packages as possible. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

It's important to note that given the change in the upgrade method, there will be no actual downgrade of the package, since Fuel 8.0 Admin Node will be installed on a clean system. So, from the upgrade standpoint I see no obstacles to have 9.2 in Fuel 8.0. I also greet any chance to reduce the

Re: [openstack-dev] Gerrit Upgrade 12/16

This is a gentle reminder that the downtime will be this Wednesday starting at 17:00 UTC. Thank you for your patience, Spencer -- Spencer Krum n...@spencerkrum.com On Tue, Dec 1, 2015, at 10:19 PM, Stefano Maffulli wrote: > On 12/01/2015 06:38 PM, Spencer Krum wrote: > > There is a thread

Re: [openstack-dev] [ceilometer] status of distil?

Hi Steve, Thanks for the heads up. I just worked this out with AJaejer. The .gitreview file has been updated and we will disable the CI job temporarily. Please let me know if there is any question. Cheers. On 14/12/15 22:01, Steve Martinelli wrote: > > While I was trying to submit patches for

Re: [openstack-dev] [midonet] Split up python-midonetclient

On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote: > > > On 10 December 2015 at 04:35, Sandro Mathys wrote: >> >> On Thu, Dec 10, 2015 at 12:48 AM, Galo Navarro wrote: >> > Hi, >> > >> >> I think the goal of this split is well

[openstack-dev] [Fuel] Nominate Bulat Gaifulin for fuel-web & fuel-mirror cores

Hi Fuelers, I'd like to nominate Bulat Gaifulin [1] for * fuel-web-core [2] * fuel-mirror-core [3] Bulat's doing a really good review with detailed feedback and he's a regular participant in IRC. He's co-author of packetary and fuel-mirror projects, and he made valuable contribution to fuel-web

Re: [openstack-dev] OpenStack-Announce List

Tom Fifield wrote: > ... and back to this thread after a few weeks :) > > The conclusions I saw were: > * Audience for openstack-announce should be "users/non-dev" > * Service project releases announcements are good > * Client library release announcements good > * Security announcements are good

Re: [openstack-dev] [nova][serial-console-proxy]

Prathyusha Guduri wrote on 12/11/2015 06:37:02 AM: > From: Prathyusha Guduri > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 12/11/2015 06:39 AM > Subject:

Re: [openstack-dev] [TripleO] Stable/Liberty Backports & Reviews

Nice job on this. Looking forward to reaping the benefits of the stable branch stuff for our upgrades testing too. Dan On Fri, 2015-12-11 at 12:35 +, Steven Hardy wrote: > Hi all, > > So, after the painful process of getting CI working for > stable/liberty, > everything is now working

Re: [openstack-dev] [Neutron] Gate failure with grenade

On 14 December 2015 at 10:18, Paul Michali wrote: > Thanks Sean! > > On Mon, Dec 14, 2015 at 12:58 PM Armando M. wrote: > >> On 14 December 2015 at 09:51, Sean Dague wrote: >> >>> On 12/14/2015 12:32 PM, Armando M. wrote: >>> > Hi folks, >>>

Re: [openstack-dev] [tripleo] Pin some puppet dependencies on git clone

On Fri, 2015-12-11 at 21:50 +0100, Jaume Devesa wrote: > Hi all, > > Today TripleO CI jobs failed because a new commit introduced on > puppetlabs-mysql[1]. > Mr. Jiri Stransky solved it as a temporally fix by pinning the puppet > module clone to a previous > commit in the tripleo-common

Re: [openstack-dev] [Neutron] Call for review focus

On 11/25/2015 11:05 PM, Assaf Muller wrote: We could then consider running the script automatically on a daily basis and publishing the resulting URL in a nice bookmarkable place. An update on this. The easiest bookmarkable place that I found it's my blog [1]. I have a script that updates

Re: [openstack-dev] [Neutron] Gate failure with grenade

On 14 December 2015 at 09:51, Sean Dague wrote: > On 12/14/2015 12:32 PM, Armando M. wrote: > > Hi folks, > > > > Something snuck in past the gate last night [1]. Please stop rechecking > > and pushing in the merge queue until the matter is resolved. > > > > I will follow up with

Re: [openstack-dev] [Neutron] Gate failure with grenade

On 12/14/2015 12:32 PM, Armando M. wrote: > Hi folks, > > Something snuck in past the gate last night [1]. Please stop rechecking > and pushing in the merge queue until the matter is resolved. > > I will follow up with details, if someone knows more, please find me on IRC. > > Thanks, > Armando

[openstack-dev] [kuryr] Release Notes for Kuryr

Howdy Kuryr developers! Like other OpenStack projects, I've added the functionality to use release notes with Kuryr. Once [1] merges, we can add release notes in the "releasenotes/notes" directory. I encourage everyone who has added a feature item to Kuryr to please add a release note for that

Re: [openstack-dev] [midonet] Split up python-midonetclient

On Mon, Dec 14, 2015 at 6:07 PM, Jaume Devesa wrote: > +1 > > I think it is good compromise. Thanks Ryu! > > I understand the CLI will belong to the external part. I much prefer to > have > it in a separate project rather than into the plugin. Even if the code is > tiny. >

  1   2   >