Re: [openstack-dev] Unexpected error in OpenStack Nova

Hi Hossein, openstack-dev is a development mailing list, focused around the future of OpenStack and the development thereof. I would recommend that you address your question (with appropriate debug log output) to the openstack-operators mailing list. Best regards, Jesse On 3 September 2014 21:

Re: [openstack-dev] [Nova] [feature freeze exception] Move to oslo.db

I'm good with this one too, so that makes three if Joe is ok with this. @Josh -- can you please take a look at the TH failures? Thanks, Michael On Wed, Sep 3, 2014 at 8:10 PM, Matt Riedemann wrote: > > > On 9/3/2014 5:08 PM, Andrey Kurilin wrote: >> >> Hi All! >> >> I'd like to ask for a featur

Re: [openstack-dev] [Heat][Docker] How to Dockerize your applications with OpenStack Heat in simple steps

Hi Thiago, IMO - no - docker is not a "replacement for VMs". Docker can be used to isolate (and with it make them also transportable) applications from the underlying OS and other apps running on that same host. Imagine you have a EC2 / RackSpace instance - they charge X per VM instance whether o

Re: [openstack-dev] [TripleO] Review metrics - what do we want to measure?

I've moved it back up the review chain for you :-) Rackspace Australia On 9/3/14 6:34 PM, Robert Collins wrote: We would benefit a great deal from having this sooner. On 3 September 2014 20:11, Joshua Hesketh wrote: On 9/3/14 10:43 AM, Jeremy Stanley wrote: On 2014-09-03 11:51:13 +1200 (+12

Re: [openstack-dev] [neutron] New meeting rotation starting next week

How is the master list compiled into a calendar? Is it possible to use that same system to filter by project? On Wed, Sep 3, 2014 at 4:45 PM, Sukhdev Kapur wrote: > +1 > > It will be very useful to have neutron specific meetings on iCal - > considering that they will be moving around... > > -Su

[openstack-dev] [Octavia] Question about where to render haproxy configurations

Hello! At today's Octavia meeting, one of the questions briefly discussed was where, in the Octavia architecture, haproxy configuration files should be rendered. This discussion went long and we decided to take it to the mailing list for more thorough discussion and to gather alternate ideas. Any

Re: [openstack-dev] [nova] Bug: resize on same node with allow_resize_to_same_host=True

Hi Jay, I have summited a patch https://review.openstack.org/#/c/117116/ with same fix. But there are different opinions provided this patch. Could you validate and provide your inputs on this patch. Thanks. Regards Kanagaraj M -Original Message- From: Jay Pipes [mailto:jaypi...@gmail

Re: [openstack-dev] [Heat][Docker] How to Dockerize your applications with OpenStack Heat in simple steps

Hi Marouen, Just curious to know more on the deployment of dockers with OpenStack like: i) Does any body deployed dockers with OpenStack? ii) What are the common/most widely deployed applications using Dockers containers? Appreciate your inputs. Regards, Balaji.P On Wed, Aug 27, 2014 at 8:00

Re: [openstack-dev] [nova] Resize:allow_resize_to_same_host=True fails

Updated the subject From: Manickam, Kanagaraj Sent: Wednesday, September 03, 2014 5:30 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [openstack][nova] Resize: allow_resize_to_same_host=True fails This mail is regarding the flag "allow_resize_to_same

Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

Hi all, May I suggest putting your feedback into this review, which is on the same subject? https://review.openstack.org/#/c/118623/ Thanks, doug On 9/3/14, 8:57 PM, "trinath.soman...@freescale.com" wrote: >This is a Good option to go with. > >To trigger a specific CI, CI can have their own

[openstack-dev] [neutron][policy] Group-based Policy next steps

Hi, There's been a lot of lively discussion on GBP a few weeks back and we wanted to drive forward the discussion on this a bit more. As you might imagine, we're excited to move this forward so more people can try it out. Here are the options: * Neutron feature branch: This presumably allows the

[openstack-dev] [nova] Call for review w.r.t. scheduler being passed requested networks

Hi Stackers, I was wondering if I could get a few folks to look at https://review.openstack.org/#/c/118010/ -- basically with the switch to conductor having a bigger role in the deployment process (and lessening the scheduler's role), the scheduler lost the ability to look at the networks being re

Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

This is a Good option to go with. To trigger a specific CI, CI can have their own string or in a community specified format. Like retrigger-freescale .. Also, in the ML or in IRC rooms, I have seen many people asking on how to recheck with an X CI. And many people are not aware of what strin

[openstack-dev] [Neutron][LBass] Item for the meeting tomorrow

Since progress on LBaaS V2 has come to a halt due to the incubator limbo, but mainly because development focus has been put on Octavia for most of the team, I'd like to suggest discussing whether it is worth pursuing a solution to the issue (at least what I see as an issue) of drivers being respons

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On Wed, 2014-09-03 at 23:10 +0200, Salvatore Orlando wrote: > > > On 3 September 2014 22:10, Joe Gordon wrote: > > > > On Tue, Aug 26, 2014 at 4:47 PM, Salvatore Orlando > wrote: > TL; DR > A few folks are proposing to s

Re: [openstack-dev] [all] Alpha release of Congress

Congrats! Will appear in J or K? And will there's an interface in horizon? Thanks! On Thu, Sep 4, 2014 at 5:41 AM, Tim Hinrichs wrote: > Hi all, > > The alpha release of Congress is now available! We'd love any and all > feedback. > > Components and Features > - Support for policy monitoring >

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On Wed, 2014-09-03 at 15:41 -0500, Kyle Mestery wrote: > On Wed, Sep 3, 2014 at 3:22 PM, Sean Dague wrote: > > On 08/26/2014 07:47 PM, Salvatore Orlando wrote: > >> TL; DR > >> A few folks are proposing to stop running tests for neutron advanced > >> services [ie: (lb|vpn|fw)aas] in the integrated

Re: [openstack-dev] [neutron] New meeting rotation starting next week

+1. This would be better! Maybe we can send a google calendar invitation. On Thu, Sep 4, 2014 at 7:45 AM, Sukhdev Kapur wrote: > +1 > > It will be very useful to have neutron specific meetings on iCal - > considering that they will be moving around... > > -Sukhdev > > > > On Mon, Sep 1, 2014 at

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

On Wed, Sep 3, 2014 at 7:07 PM, Joe Gordon wrote: > On Wed, Sep 3, 2014 at 2:50 AM, Nikola Đipanov > wrote: > >> The reason many features including my own may not make the FF is not >> because there was not enough buy in from the core team (let's be >> completely honest - I have 3+ other core me

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

On 9/3/2014 10:57 AM, Solly Ross wrote: I will follow up with a more detailed email about what I believe we are missing, once the FF settles and I have applied some soothing creme to my burnout wounds, but currently my sentiment is: Contributing features to Nova nowadays SUCKS!!1 (even as a co

Re: [openstack-dev] [Nova] [feature freeze exception] Move to oslo.db

On 9/3/2014 5:08 PM, Andrey Kurilin wrote: Hi All! I'd like to ask for a feature freeze exception for porting nova to use oslo.db. This change not only removes 3k LOC, but fixes 4 bugs(see commit message for more details) and provides relevant, stable common db code. Main maintainers of oslo

Re: [openstack-dev] [Ironic] (Non-)consistency of the Ironic hash ring implementation

On 4 September 2014 08:13, Robert Collins wrote: > On 3 September 2014 23:50, Nejc Saje wrote: > > Forgive my slowness :). > >> Disclaimer: in Ironic terms, node = conductor, key = host > > Sadly not inside the hash_ring code :/. host == conductor, key == data. > >> The test I linked fails with I

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On 2014-09-03 13:27:55 +0400 (+0400), Yuriy Taraday wrote: [...] > May be we should drop 3.3 already? It's in progress. Search review.openstack.org for open changes in all projects with the topic "py34". Shortly I'll also have some infra config changes up to switch python33 jobs out for python34,

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

Joe, Nova is big and complex enough that I don't think any one person is able to > identify what we need to work on to make things better. Oh this is really bad.., if there is no person that understand what is happening in project and where it should move... IMHO Project can't evolve without str

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

On Wed, Sep 3, 2014 at 8:57 AM, Solly Ross wrote: > > I will follow up with a more detailed email about what I believe we are > > missing, once the FF settles and I have applied some soothing creme to > > my burnout wounds, but currently my sentiment is: > > > > Contributing features to Nova nowa

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

On Wed, Sep 3, 2014 at 2:50 AM, Nikola Đipanov wrote: > On 09/02/2014 09:23 PM, Michael Still wrote: > > On Tue, Sep 2, 2014 at 1:40 PM, Nikola Đipanov > wrote: > >> On 09/02/2014 08:16 PM, Michael Still wrote: > >>> Hi. > >>> > >>> We're soon to hit feature freeze, as discussed in Thierry's rec

Re: [openstack-dev] [neutron] New meeting rotation starting next week

+1 It will be very useful to have neutron specific meetings on iCal - considering that they will be moving around... -Sukhdev On Mon, Sep 1, 2014 at 6:58 PM, Kevin Benton wrote: > Unfortunately the master ICAL has so many meetings that it's not useful to > have displaying as part of a normal

Re: [openstack-dev] [Ironic] (Non-)consistency of the Ironic hash ring implementation

On 4 September 2014 00:13, Eoghan Glynn wrote: > > >> On 09/02/2014 11:33 PM, Robert Collins wrote: >> > The implementation in ceilometer is very different to the Ironic one - >> > are you saying the test you linked fails with Ironic, or that it fails >> > with the ceilometer code today? >> >> Dis

Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

Incidentally, I replied to Kurt's email this morning on this subject - below is what I wrote. There are several threads with such information. While it is great to express opinions on the MLs, converting them into decisions/conclusions should be done in a formal fashion. I suggested that this be ad

Re: [openstack-dev] [neutron][IPv6] Neighbor Discovery for HA

Sounds impressive! :-D On 1 September 2014 23:52, Xu Han Peng wrote: > Anthony, > > Thanks for your reply. > > If HA method like VRRP are used for IPv6 router, according to the VRRP RFC > with IPv6 included, the servers should be auto-configured with the active > router's LLA as the default

[openstack-dev] [Nova] [feature freeze exception] Move to oslo.db

Hi All! I'd like to ask for a feature freeze exception for porting nova to use oslo.db. This change not only removes 3k LOC, but fixes 4 bugs(see commit message for more details) and provides relevant, stable common db code. Main maintainers of oslo.db(Roman Podoliaka and Victor Sergeyev) are OK

Re: [openstack-dev] [neutron][IPv6] Neighbor Discovery for HA

It should be noted that "send_arp_for_ha" is a configuration option that preceded the more recent in-progress work to add VRRP controlled HA to Neutron's router. The option was added, I believe, to cause the router to send (default) 3 GARPs to the external gateway if the router was removed from on

[openstack-dev] [sahara] integration tests in python-saharaclient

Hi team, Today I've realized that we have some tests called 'integration' in python-saharaclient. Also I've found out that Jenkins doesn't use them and they can't be run starting from April because of typo in tox.ini. Does anyone know what these tests are? Does anyone mind if I delete them since

[openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?

On Wed Sep 3 19:23:52 UTC 2014, Doug Hellmann wrote: >On Sep 3, 2014, at 2:03 PM, Ken Giusti wrote: >> Hello, >> >> I'm proposing a freeze exception for the oslo.messaging AMQP 1.0 >> driver: >> >> https://review.openstack.org/#/c/75815/ >> Thanks, >> >> Ken > >Ken, > >I think we’re generally i

[openstack-dev] [all] Alpha release of Congress

Hi all, The alpha release of Congress is now available! We'd love any and all feedback. Components and Features - Support for policy monitoring - Policy engine implementation - Message-passing architecture - Drivers for Nova and Neutron - Devstack integration - Documentation - REST API README (

Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

On 09/03/2014 02:03 PM, Akihiro Motoki wrote: > Hi Neutron team, > > There are many third party CI in Neutron and we sometimes/usually > want to retrigger third party CI to confirm results. > A comment syntax varies across third party CI, so I think it is useful > to gather "recheck command" in on

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

> -Original Message- > From: Clark Boylan [mailto:cboy...@sapwetik.org] > Sent: 03 September 2014 21:57 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt > > > > On Wed, Sep 3, 2014, at 01:06 PM, Kuvaja, Erno wrote: >

Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

+1 It would also be really helpful if the recheck command is shown in the output of the results from each CI so the developer doesn't even have to visit this page. On Wed, Sep 3, 2014 at 11:03 AM, Akihiro Motoki wrote: > Hi Neutron team, > > There are many third party CI in Neutron and we some

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On 3 September 2014 22:10, Joe Gordon wrote: > > > > On Tue, Aug 26, 2014 at 4:47 PM, Salvatore Orlando > wrote: > >> TL; DR >> A few folks are proposing to stop running tests for neutron advanced >> services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only on >> the neutron gate.

Re: [openstack-dev] [Glance][Nova][All] requests 2.4.0 breaks glanceclient

On 9/3/14, 2:20 PM, "Sean Dague" wrote: >On 09/03/2014 03:12 PM, Gregory Haynes wrote: >> Excerpts from Kuvaja, Erno's message of 2014-09-03 12:30:08 +: >>> Hi All, >>> >>> While investigating glanceclient gating issues we narrowed it down to >>>requests 2.4.0 which was released 2014-08-29. U

Re: [openstack-dev] [nova] libvirt version_cap, a postmortem

On Sat, Aug 30, 2014 at 9:08 AM, Mark McLoughlin wrote: > > Hey > > The libvirt version_cap debacle continues to come up in conversation and > one perception of the whole thing appears to be: > > A controversial patch was "ninjaed" by three Red Hat nova-cores and > then the same individuals p

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 3, 2014, at 01:06 PM, Kuvaja, Erno wrote: > > -Original Message- > > From: Clark Boylan [mailto:cboy...@sapwetik.org] > > Sent: 03 September 2014 20:10 > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [all] [glance] do NOT ever sort > > requirements.

Re: [openstack-dev] [third-party] [infra] New mailing lists for third party announcements and account requests

On Fri, Aug 29, 2014 at 12:47 PM, Elizabeth K. Joseph wrote: > Third-party-request > > This list is the new place to request the creation or modification of > your third party account. Note that old requests sent to the > openstack-infra mailing list don't need to be resubmitted, they are > alread

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On Wed, Sep 3, 2014 at 3:22 PM, Sean Dague wrote: > On 08/26/2014 07:47 PM, Salvatore Orlando wrote: >> TL; DR >> A few folks are proposing to stop running tests for neutron advanced >> services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only >> on the neutron gate. >> >> Reason: pr

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On 08/26/2014 07:47 PM, Salvatore Orlando wrote: > TL; DR > A few folks are proposing to stop running tests for neutron advanced > services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only > on the neutron gate. > > Reason: projects like nova are 100% orthogonal to neutron advanced >

Re: [openstack-dev] [Ironic] (Non-)consistency of the Ironic hash ring implementation

On 3 September 2014 23:50, Nejc Saje wrote: Forgive my slowness :). > Disclaimer: in Ironic terms, node = conductor, key = host Sadly not inside the hash_ring code :/. host == conductor, key == data. > The test I linked fails with Ironic hash ring code (specifically the part > that tests consi

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On Tue, Aug 26, 2014 at 4:47 PM, Salvatore Orlando wrote: > TL; DR > A few folks are proposing to stop running tests for neutron advanced > services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only on > the neutron gate. > > Reason: projects like nova are 100% orthogonal to neutron

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

> -Original Message- > From: Clark Boylan [mailto:cboy...@sapwetik.org] > Sent: 03 September 2014 20:10 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt > > > > On Wed, Sep 3, 2014, at 11:51 AM, Kuvaja, Erno wrote: >

Re: [openstack-dev] Unexpected error in OpenStack Nova

Any Idea? On Wed, Sep 3, 2014 at 6:41 PM, Hossein Zabolzadeh wrote: > Hi, > After successful installation of both keystone and nova, I tried to > execute the 'nova list' command by the folllowing env variables(My > Deployment Model is single machine deployment): > export OS_USERNAME=admin > exp

Re: [openstack-dev] [UX] [Horizon] [Heat] Merlin project (formerly known as cross-project UI library for Heat/Mistral/Murano/Solum) plans for PoC and more

Zane, Thank you. I have added ASL 2.0. Drago On 8/28/14, 9:10 PM, "Zane Bitter" wrote: >On 28/08/14 13:31, Drago Rosson wrote: >> You are in luck, because I have just now open-sourced Barricade! Check >>it >> out [4]. >> >> [4]https://github.com/rackerlabs/barricade > >Please add a license (pr

Re: [openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?

On Sep 3, 2014, at 2:03 PM, Ken Giusti wrote: > Hello, > > I'm proposing a freeze exception for the oslo.messaging AMQP 1.0 > driver: > > https://review.openstack.org/#/c/75815/ > > Blueprint: > > > https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation > >

Re: [openstack-dev] [Glance][Nova][All] requests 2.4.0 breaks glanceclient

On 09/03/2014 03:12 PM, Gregory Haynes wrote: > Excerpts from Kuvaja, Erno's message of 2014-09-03 12:30:08 +: >> Hi All, >> >> While investigating glanceclient gating issues we narrowed it down to >> requests 2.4.0 which was released 2014-08-29. Urllib3 seems to be raising >> new ProtocolErr

Re: [openstack-dev] [Glance][Nova][All] requests 2.4.0 breaks glanceclient

Excerpts from Kuvaja, Erno's message of 2014-09-03 12:30:08 +: > Hi All, > > While investigating glanceclient gating issues we narrowed it down to > requests 2.4.0 which was released 2014-08-29. Urllib3 seems to be raising new > ProtocolError which does not get catched and breaks at least gl

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 3, 2014, at 11:51 AM, Kuvaja, Erno wrote: > > -Original Message- > > From: Sean Dague [mailto:s...@dague.net] > > Sent: 03 September 2014 13:37 > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [all] [glance] do NOT ever sort req

Re: [openstack-dev] [glance][feature freeze exception] Proposal for using Launcher/ProcessLauncher for launching services

Hi Erno, I agree that we must document what all config parameters will be reloaded after SIGHUP signal is processed, that's the reason why we have added DocImpact tag to patch https://review.openstack.org/#/c/117988/. We will test what parameters are reloaded and report them to the Doc team.

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: 03 September 2014 13:37 > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt > > I'm not sure why people keep showing up with "s

[openstack-dev] [rally][iperf] Benchmarking network performance

Hi Looking into the following blueprint which requires that network performance tests be done as part of a scenario I plan to implement this using iperf and basically a scenario which includes a client/server VM pair The client than sends out TCP traffic using iperf to server and the VM through

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

Here is a docker image that will bring up subway. https://registry.hub.docker.com/u/nibalizer/subway/ On Wed, Sep 3, 2014 at 10:04 AM, Clark Boylan wrote: > On Wed, Sep 3, 2014, at 07:26 AM, Ryan Brown wrote: > > On 09/03/2014 09:35 AM, Sylvain Bauza wrote: > > > Re: ZNC as a service, I think

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

Anyone know what happened to (or is happening) to: https://github.com/pypa/pip/issues/988 'Pip needs a real dependency resolver' Maybe it's time we as a community helped pip get that feature in? -Josh On Sep 3, 2014, at 5:37 AM, Sean Dague wrote: > I'm not sure why people keep showing up wit

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

+1 I had several pacthes in "start lxc from block device" series. The blueprint was waiting since Icehouse. In Juno it was approved, however, besides Daniel Berrange no one was looking at these patches. Now it's being pushed to Kilo, regadless of the fact that everything is +2ed. Normally, I do

[openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

Hi Neutron team, There are many third party CI in Neutron and we sometimes/usually want to retrigger third party CI to confirm results. A comment syntax varies across third party CI, so I think it is useful to gather "recheck command" in one place. I struggled to know how to rerun a specific CI.

Re: [openstack-dev] Rally scenario Issue

Hello Timur, I have one question, so I am testing rally boot and delete scenario, it seems to work fine when tenant is 1 and user is 1. Although if I change tenant to 2 and users 2, I see below error. Any idea why this can happen ? = 2014-09-03 10:51:18.138 17441 CRITICAL rally [-] Service

[openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?

Hello, I'm proposing a freeze exception for the oslo.messaging AMQP 1.0 driver: https://review.openstack.org/#/c/75815/ Blueprint: https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation I presented this work at the Juno summit [1]. The associated spec has bee

Re: [openstack-dev] [OpenStack-Infra] VMWare NSX CI - recheck info

Hi Kurt, We (Arista) were one of the early adapters of the CI systems. We built our system based upon the Neutron requirements as of late last year/early this year. Our CI has been up and operational since January of this year. This is before (or in parallel to Jay Pipes effort of Zuul based CIs).

Re: [openstack-dev] [Keystone] Domain-specific Drivers

On 08/26/2014 06:12 AM, Henry Nash wrote: Hi It was fully merged for Juno-2 - so if you are having problems, feel free to share the settings in you main config and keystone.heat.config files Henry On 26 Aug 2014, at 10:26, Bruno Luis Dos Santos Bompastor mailto:bruno.bompas...@cern.ch>> wro

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 3, 2014 at 11:23 AM, Doug Hellmann wrote: > > On Sep 3, 2014, at 12:20 PM, Dolph Mathews > wrote: > > > On Wed, Sep 3, 2014 at 8:25 AM, Sean Dague wrote: > >> On 09/03/2014 09:03 AM, Daniel P. Berrange wrote: >> > On Wed, Sep 03, 2014 at 08:37:17AM -0400, Sean Dague wrote: >> >> I'm

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

On Wed, Sep 3, 2014, at 07:26 AM, Ryan Brown wrote: > On 09/03/2014 09:35 AM, Sylvain Bauza wrote: > > Re: ZNC as a service, I think it's OK provided the implementation is > > open-sourced with openstack-infra repo group, as for Gerrit, Zuul and > > others. > > The only problem I can see is how to

Re: [openstack-dev] [Infra][Neutron] How to verify link to logs for disabled third-party CI

Thanks Joshua. I will give it a try. Gary On Wed, Sep 3, 2014 at 1:21 AM, Joshua Hesketh wrote: > On 9/3/14 12:11 PM, Gary Duan wrote: > > Hi, > > Our CI system is disabled due to a running bug and wrong log link. I > have manually verified the system with sandbox and two Neutron testing > p

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

On Wed, Sep 03, 2014 at 02:23:41PM +0200, Thierry Carrez wrote: > Stefano Maffulli wrote: > > On 08/29/2014 11:17 AM, John Garbutt wrote: > >> After moving to use ZNC, I find IRC works much better for me now, but > >> I am still learning really. > > > > There! this sentence has two very important

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Sep 3, 2014, at 12:20 PM, Dolph Mathews wrote: > > On Wed, Sep 3, 2014 at 8:25 AM, Sean Dague wrote: > On 09/03/2014 09:03 AM, Daniel P. Berrange wrote: > > On Wed, Sep 03, 2014 at 08:37:17AM -0400, Sean Dague wrote: > >> I'm not sure why people keep showing up with "sort requirements" patc

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On Sep 3, 2014, at 11:57 AM, Clark Boylan wrote: > On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote: >> >> On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote: >> >>> On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote: Hello. Currently for alpha releases of oslo libraries w

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 3, 2014 at 8:25 AM, Sean Dague wrote: > On 09/03/2014 09:03 AM, Daniel P. Berrange wrote: > > On Wed, Sep 03, 2014 at 08:37:17AM -0400, Sean Dague wrote: > >> I'm not sure why people keep showing up with "sort requirements" patches > >> like - https://review.openstack.org/#/c/76817/6,

Re: [openstack-dev] Kilo Cycle Goals Exercise

On Sep 3, 2014, at 11:37 AM, Joe Gordon wrote: > As you all know, there has recently been several very active discussions > around how to improve assorted aspects of our development process. One idea > that was brought up is to come up with a list of cycle goals/project > priorities for Kilo [0]

Re: [openstack-dev] Rally scenario Issue

Please pass on your VMTasks.py. Further, floating ips are available. Thanks for the help! On Wed, Sep 3, 2014 at 8:07 PM, Ajay Kalambur (akalambu) wrote: > The reason this is failing is you are specifying a fixed network and at > the same time asking for a new network to be created using cont

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

> I will follow up with a more detailed email about what I believe we are > missing, once the FF settles and I have applied some soothing creme to > my burnout wounds, but currently my sentiment is: > > Contributing features to Nova nowadays SUCKS!!1 (even as a core > reviewer) We _have_ to change

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote: > > On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote: > > > On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote: > >> Hello. > >> > >> Currently for alpha releases of oslo libraries we generate either > >> universal > >> or Python 2.x-only

Re: [openstack-dev] [Fuel] Goals for 5.1.1 & 6.0

Feature blockers: Versioning for REST API , UI, serialization Ongoing activities: Nailgun plugin

Re: [openstack-dev] Treating notifications as a contract

On Sep 3, 2014, at 9:50 AM, Sandy Walsh wrote: > Is there anything slated for the Paris summit around this? > > I just spent nearly a week parsing Nova notifications and the pain of no > schema has overtaken me. > > We're chatting with IBM about CADF and getting down to specifics on their >

[openstack-dev] Kilo Cycle Goals Exercise

As you all know, there has recently been several very active discussions around how to improve assorted aspects of our development process. One idea that was brought up is to come up with a list of cycle goals/project priorities for Kilo [0]. To that end, I would like to propose an exercise as dis

Re: [openstack-dev] [Fuel] Pre-5.1 and master builds ISO are available for download

Dmitry, I totally agree that we should support nightly builds in upgrades. I've created a blueprint for this: https://blueprints.launchpad.net/fuel/+spec/upgrade-nightly On Tue, Sep 2, 2014 at 3:24 AM, Dmitry Borodaenko wrote: > We should not confuse beta and rc builds, normally betas predate

Re: [openstack-dev] Treating notifications as a contract

> > For example: It appears that CADF was designed for this sort of thing and> > > > was considered at some point in the past. It would be useful to know> > > > more of that story if there are any pointers.> >> > My initial reaction is > > that CADF has the stank of enterprisey all over> > it ra

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

On Wed, Sep 3, 2014 at 10:19 AM, Mark McClain wrote: > > On Sep 3, 2014, at 11:04 AM, Brian Haley wrote: > >> On 09/03/2014 08:17 AM, Kyle Mestery wrote: >>> Given how deep the merge queue is (146 currently), we've effectively >>> reached feature freeze in Neutron now (likely other projects as we

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On Sep 3, 2014, at 5:27 AM, Yuriy Taraday wrote: > On Tue, Sep 2, 2014 at 11:17 PM, Clark Boylan wrote: > On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote: > > Hello. > > > > Currently for alpha releases of oslo libraries we generate either > > universal > > or Python 2.x-only wheels. This

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote: > On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote: >> Hello. >> >> Currently for alpha releases of oslo libraries we generate either >> universal >> or Python 2.x-only wheels. This presents a problem: we can't adopt alpha >> releases in proj

Re: [openstack-dev] Treating notifications as a contract

On 9/3/2014 11:32 AM, Chris Dent wrote: > On Wed, 3 Sep 2014, Sandy Walsh wrote: > >> We're chatting with IBM about CADF and getting down to specifics on >> their applicability to notifications. Once I get StackTach.v3 into >> production I'm keen to get started on revisiting the notification >> for

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

On Sep 3, 2014, at 11:04 AM, Brian Haley wrote: > On 09/03/2014 08:17 AM, Kyle Mestery wrote: >> Given how deep the merge queue is (146 currently), we've effectively >> reached feature freeze in Neutron now (likely other projects as well). >> So this morning I'm going to go through and remove BP

Re: [openstack-dev] Rally scenario Issue

The reason this is failing is you are specifying a fixed network and at the same time asking for a new network to be created using context. What happens is the VM gets attached to your fixed network instead of the created Rally network So you need to modify vm_tasks.py for this case and basically

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

On 09/03/2014 08:17 AM, Kyle Mestery wrote: > Given how deep the merge queue is (146 currently), we've effectively > reached feature freeze in Neutron now (likely other projects as well). > So this morning I'm going to go through and remove BPs from Juno which > did not make the merge window. I'll

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

On 09/03/2014 07:31 AM, Gary Kotton wrote: On 9/3/14, 12:50 PM, "Nikola Đipanov" wrote: On 09/02/2014 09:23 PM, Michael Still wrote: On Tue, Sep 2, 2014 at 1:40 PM, Nikola Đipanov wrote: On 09/02/2014 08:16 PM, Michael Still wrote: Hi. We're soon to hit feature freeze, as discussed in Th

Re: [openstack-dev] [solum] Consistency of development environment

Alex, Thanks for your question, and for your interest in Solum. Our current dev environment setup relies on devstack to produce a working OpenStack environment for Solum to run within. We have noticed lately that our devstack setup does not always work. Because we are checking out devstack code

Re: [openstack-dev] Treating notifications as a contract

On Wed, 3 Sep 2014, Sandy Walsh wrote: Is there anything slated for the Paris summit around this? There are plans to make plans, but that's about all I know. I just spent nearly a week parsing Nova notifications and the pain of no schema has overtaken me. /me passes the ibuprofen We're c

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

On 09/03/2014 09:35 AM, Sylvain Bauza wrote: > Re: ZNC as a service, I think it's OK provided the implementation is > open-sourced with openstack-infra repo group, as for Gerrit, Zuul and > others. > The only problem I can see is how to provide IRC credentials to this, as > I don't want to share my

Re: [openstack-dev] [Cinder][Nova]Quest about Cinder Brick proposal

That¹s good. Thanks for your suggestion. On 3/9/14 9:44 pm, "Duncan Thomas" wrote: >openstack-cinder ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [QA] Meeting Thursday September 4th at 22:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, September 4th 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 t

Re: [openstack-dev] [Ironic] (Non-)consistency of the Ironic hash ring implementation

On Wed, Sep 3, 2014 at 12:50 PM, Nejc Saje wrote: > > > On 09/02/2014 11:33 PM, Robert Collins wrote: >> >> The implementation in ceilometer is very different to the Ironic one - >> are you saying the test you linked fails with Ironic, or that it fails >> with the ceilometer code today? > > > Disc

Re: [openstack-dev] [glance][feature freeze exception] Proposal for using Launcher/ProcessLauncher for launching services

In principle I like the idea and concept, a lot. In practice I don't think glance code is ready in a state that we could say SIGHUP reloads our configs. Even more my concern is that based on the behavior seen some config options gets picked up and some does not. As long as we do not have defini

Re: [openstack-dev] Treating notifications as a contract

Is there anything slated for the Paris summit around this? I just spent nearly a week parsing Nova notifications and the pain of no schema has overtaken me. We're chatting with IBM about CADF and getting down to specifics on their applicability to notifications. Once I get StackTach.v3 into pr

Re: [openstack-dev] [Cinder][Nova]Quest about Cinder Brick proposal

Emma I encourage you to join the cinder RIC channel, #openstack-cinder, on the freenode irc network (irc.freenode.net) to ask questions, you'll get much more interactive feedback there. Regards -- Duncan ___ OpenStack-dev mailing list OpenStack-dev@l

Re: [openstack-dev] [glance][feature freeze exception] Proposal for using Launcher/ProcessLauncher for launching services

Hi All, Please give your support me for applying the freeze exception for using oslo-incubator service framework in glance, based on the following blueprint: https://blueprints.launchpad.net/glance/+spec/use-common-service-framework I have ensured that after making these changes everything is

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

Le 03/09/2014 14:38, Kuvaja, Erno a écrit : Another well working option that can be easily used: 1) get a Linux system with internet connection (local box, VM in a cloud, whatever floats your boat) 2) install irssi and screen 3) run irssi in a screen Now you can login (local console, ssh, teln

  1   2   >