Re: [openstack-dev] [Neutron][LBaaS] Should TLS settings for listener be set through separate API/model?

+1 for option 1. SNI list is managed by separate entity, default TLS container is part of a listener object. It will have None value when listener does not offloads TLS. Managing another entity for 1:0-1 relationship just for future use seems not right to me. Breaking TLS settings apart from lis

Re: [openstack-dev] [Neutron][LBaaS] Should TLS settings for listener be set through separate API/model?

>>SNI list is managed by separate entity What is this entity? From: Evgeny Fedoruk [mailto:evge...@radware.com] Sent: Tuesday, June 24, 2014 12:25 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Should TLS settings for listener be

[openstack-dev] [Mistral] Mistral test infrastructure proposal

(reposting due to lack of subject) Hello, everyone! I am happy to announce that Mistral team started working on test infrastructure. Due to this fact I prepared etherpad https://etherpad.openstack.org/p/MistralTests where I analysed what we have and what we need to do. I would like to get your f

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 and +1 Thank you Ana and Zhenguo! -- Kind regards, Tatiana 2014-06-21 1:17 GMT+04:00 Lyle, David : > I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core. > > Zhenguo has been a prolific reviewer for the past two releases providing > high quality reviews. And providing a s

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 +1 Deserved. On Tue, Jun 24, 2014 at 10:41 AM, Tatiana Ovtchinnikova < t.v.ovtchinnik...@gmail.com> wrote: > +1 and +1 > Thank you Ana and Zhenguo! > > -- > Kind regards, > Tatiana > > > 2014-06-21 1:17 GMT+04:00 Lyle, David : > >> I would like to nominate Zhenguo Niu and Ana Krivokapic to H

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

On Fri, Jun 20, 2014 at 09:17:41PM +, Lyle, David wrote: > I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core. > > Zhenguo has been a prolific reviewer for the past two releases providing > high quality reviews. And providing a significant number of patches over > the past

Re: [openstack-dev] [Neutron][L3] BGP Dynamic Routing Proposal

Hi, keshav...@hp.com : > > If this BaGpipe BGP does not support MPLS data plane driver, what is > advantage of this BGP from current. Just to avoid any misunderstanding: Bagpipe BGP **does** support an MPLS dataplane for IPVPN today. For E-VPN, bagpipe could support an MPLS dataplane with a ne

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

On 20/06/14 22:17, Lyle, David wrote: > I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core. > > Zhenguo has been a prolific reviewer for the past two releases providing > high quality reviews. And providing a significant number of patches over > the past three releases. > > A

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

Fuelers, Ok, today is bug squash day. No activities except bugs triage /fix/review/merge. Current count: 17 new bugs 25 incomplete bugs

Re: [openstack-dev] [Neutron][LBaaS] Should TLS settings for listener be set through separate API/model?

Vipsniassociations table: Line 147 in last patch of the document From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com] Sent: Tuesday, June 24, 2014 10:17 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Should TLS setting

[openstack-dev] [Nova] Timeline for the rest of the Juno release

Hi, this came up in the weekly release sync with ttx, and I think its worth documenting as clearly as possible. Here is our proposed timeline for the rest of the Juno release. This is important for people with spec proposals either out for review, or intending to be sent for review soon. (The num

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 to both On Tue, Jun 24, 2014 at 1:48 PM, Julie Pichon wrote: > On 20/06/14 22:17, Lyle, David wrote: > > I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core. > > > > Zhenguo has been a prolific reviewer for the past two releases providing > > high quality reviews. And pro

Re: [openstack-dev] [Nova][neutron][NFV] Mid cycle sprints

On 18 June 2014 12:00, Carlos Gonçalves wrote: > I’ve added Joao Soares (Portugal Telecom) and myself (Instituto de > Telecomunicacoes) to https://wiki.openstack.org/wiki/Sprints/ParisJuno2014 for > a Neutron and NFV meetup. > Please add yourselves as well so that we can have a better idea of who

Re: [openstack-dev] [hacking] community consensus and removing rules

On Mon, 2014-06-23 at 19:55 -0700, Joe Gordon wrote: > * Add a new directory, contrib, for local rules that multiple > projects use but are not generally considered acceptable to be > enabled by default. This way we can reduce the amount of cut > and pasted code (than

[openstack-dev] Hyper-v meeting schedule

Hi All, The Hyper-v meetings for the next two weeks will need to be canceled due to travel and vacations. We will resume in two weeks. Best, P ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/

Re: [openstack-dev] [QA] Questions about test policy for scenario test

On 06/24/2014 01:29 AM, Fei Long Wang wrote: > Greetings, > > We're leveraging the scenario test of Tempest to do the end-to-end > functional test to make sure everything work great after upgrade, > patching, etc. And We're happy to fill the gaps we found. However, I'm a > little bit confused abou

Re: [openstack-dev] [Openstack-security] Periodic Security Checks

Is this intended only for checking the OpenStack infrastructure or for checking the hosted guest VMs as well ? Why does the scheduling of the checks even have to be part of OpenStack ? Why can't the operating system that OpenStack is running on provide that ? Any reason this is limited to "

Re: [openstack-dev] [Nova] bp: nova-ecu-support

The basic framework for supporting this kind of resource scheduling is the extensible-resource-tracker: https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking https://review.openstack.org/#/c/86050/ https://review.openstack.org/#/c/71557/ Once that lands being able schedule on

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

> -Original Message- > From: John Garbutt [mailto:j...@johngarbutt.com] > Sent: 23 June 2014 10:35 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction > as part of resize ? > > On 18 June 2014 21:57

Re: [openstack-dev] [hacking] community consensus and removing rules

On 06/24/2014 12:34 AM, Angus Salkeld wrote: > On 24/06/14 12:59, Joe Gordon wrote: >> Hi All, > >> After Friday's thread on removing several hacking rules. H402 and H803 are >> lines >> up to removed in the next few days, while Ben has volunteered to work on >> H305. >> In addition to helping

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

Hi Michael, Not sure I understand the need for a gap between "Juno Spec approval freeze" (Jul 10th) and "K opens for spec proposals" (Sep 4th).I can understand that K specs won't get approved in that period, and may not get much feedback from the cores - but I don't see the harm in letting

[openstack-dev] Tripleo, Ironic, the SSH power driver, paramiko and eventlet fun.

There's a bug on this: https://bugs.launchpad.net/ironic/+bug/1321787?comments=all It seems like it's been well-known for a long time that paramiko parallelism doesn't work well with eventlet. Ironic's aggressive use of the ssh power driver seems to hit this hard. The sign that you're hitting

[openstack-dev] [Neutron][LBaaS] Layer7 Switching - L7 Rule - comapre_type values

Hi One of L7 Rule attributes is ‘compare_type’. This field is the match operator that the rule should activate against the value found in the request. Below is list of the possible values: - Regexp - StartsWith - EndsWith - Contains - EqualTo (*) - GreaterThan (*) - LessThan (*) The last 3 operat

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

On Tue, Jun 24, 2014 at 10:55:41AM +, Day, Phil wrote: > > -Original Message- > > From: John Garbutt [mailto:j...@johngarbutt.com] > > Sent: 23 June 2014 10:35 > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova] Do any hyperviors

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

Phil -- I really want people to focus their efforts on fixing bugs in that period was the main thing. The theory was if we encouraged people to work on specs for the next release, then they'd be distracted from fixing the bugs we need fixed in J. Cheers, Michael On Tue, Jun 24, 2014 at 9:08 PM, D

Re: [openstack-dev] [QA] Questions about test policy for scenario test

- Original Message - > From: "Fei Long Wang" > To: "OpenStack Development Mailing List (not for usage questions)" > > Cc: br...@catalyst.net.nz > Sent: Tuesday, June 24, 2014 8:29:03 AM > Subject: [openstack-dev] [QA] Questions about test policy for scenario test > Greetings, > We're l

[openstack-dev] [mistral] Mistral 0.0.4 released

Hi, Mistral version 0.0.4* has just been released! This is an intermediate release however it contains a series of important changes/fixes. Here’s the list of the most noticeable changes: Speeded up tests using Testr Modified launch script to start any combination of Mistral components (engine,

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

On 06/24/2014 07:35 AM, Michael Still wrote: > Phil -- I really want people to focus their efforts on fixing bugs in > that period was the main thing. The theory was if we encouraged people > to work on specs for the next release, then they'd be distracted from > fixing the bugs we need fixed in J.

Re: [openstack-dev] [Ceilometer] [Heat] Ceilometer aware people, please advise us on processing notifications..

On Tue, Jun 24 2014, Clint Byrum wrote: > Basically in Heat when a user boots an instance, we would like to act as > soon as it is active, and not have to poll the nova API to know when > that is. Angus has suggested that perhaps we can just tell ceilometer to > hit Heat with a web hook when that h

[openstack-dev] [Neutron][QA] Enabling full neutron Job

There is a long standing patch [1] for enabling the neutron full job. Little before the Icehouse release date, when we first pushed this, the neutron full job had a failure rate of less than 10%. However, since has come by, and perceived failure rates were higher, we ran again this analysis. Here

Re: [openstack-dev] [Neutron][QA] Enabling full neutron Job

Ops... I forgot to mention that in agreement with sdague we won't anyway enable this job before thursday June 26th, in order to give a few days to the trusty update to settle down. Salvatore On 24 June 2014 14:14, Salvatore Orlando wrote: > There is a long standing patch [1] for enabling the

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

On Tue, Jun 24, 2014 at 7:07 AM, Russell Bryant wrote: > On 06/24/2014 07:35 AM, Michael Still wrote: > > Phil -- I really want people to focus their efforts on fixing bugs in > > that period was the main thing. The theory was if we encouraged people > > to work on specs for the next release, the

Re: [openstack-dev] [TripleO] dib-utils Release Question

Ahh, ok. I had just assumed it was a Python library, but I admittedly didn't look too closely at it. Thanks :) On 06/23/2014 09:32 PM, Steve Kowalik wrote: On 24/06/14 06:31, Jay Dobies wrote: I finished the releases for all of our existing projects and after poking around tarballs.openstack.o

[openstack-dev] [Fuel] Blueprints process

Guys, We have a beautiful contribution guide: https://wiki.openstack.org/wiki/Fuel/How_to_contribute However, I would like to address several issues in our blueprints/bugs processes. Let's discuss and vote on my proposals. 1) First of all, the bug counter is an excellent metric for quality. So l

[openstack-dev] [Fuel] Removing old node logs

Guys, What do you think of removing node logs on master node right after removing node from cluster? The issue is when user do experiments he creates and deletes clusters and old unused directories remain and take disk space. On the other hand, it is not so hard to imaging the situation when user

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

On 06/20/2014 11:17 PM, Lyle, David wrote: I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core. Zhenguo has been a prolific reviewer for the past two releases providing high quality reviews. And providing a significant number of patches over the past three releases. Ana has

Re: [openstack-dev] [hacking] rules for removal

On 06/20/2014 02:33 PM, Joe Gordon wrote: > On Fri, Jun 20, 2014 at 11:07 AM, Sean Dague wrote: > >> After seeing a bunch of code changes to enforce new hacking rules, I'd >> like to propose dropping some of the rules we have. The overall patch >> series is here - >> >> https://review.openstack.o

Re: [openstack-dev] [hacking] rules for removal

On 06/22/2014 02:49 PM, Duncan Thomas wrote: > On 22 June 2014 14:41, Amrith Kumar wrote: >> In addition to making changes to the hacking rules, why don't we mandate also >> that perceived problems in the commit message shall not be an acceptable >> reason to -1 a change. > > -1. > > There are s

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

On 06/24/2014 08:56 AM, Anne Gentle wrote: > > > > On Tue, Jun 24, 2014 at 7:07 AM, Russell Bryant > wrote: > > On 06/24/2014 07:35 AM, Michael Still wrote: > > Phil -- I really want people to focus their efforts on fixing bugs in > > that period was the

[openstack-dev] [blazar] Blazar client V2 REST API support and Horizon integration

Blazar cores, I managed to get our client working against our V2 REST API and I implemented the first bits of our Blazar Dashboard for Horizon. In order to continue working on the last, I need this patches on master. I suggest this order: https://review.openstack.org/#/c/99389/ (V2

Re: [openstack-dev] [hacking] rules for removal

On 23 June 2014 07:04, Jay Pipes wrote: > I would also love to get rid of H404, otherwise known as the dumb rule that > says if you have a multiline docstring, that there must be a summary line, > then a blank line, then a detailed description. It makes things like this > illegal, which, IMHO, is

Re: [openstack-dev] [Neutron][LBaaS] Layer7 Switching - L7 Rule - comapre_type values

I think the API should provide an richly featured interface, and individual drivers should indicate if they support the provided configuration. For example there is a spec for a Linux LVS LBaaS driver, this driver would not support TLS termination or any layer 7 features, but would still be valuabl

Re: [openstack-dev] [TripleO] [Heat] Reminder: Mid-cycle Meetup - Attendance Confirmation

On 20/06/14 16:26 -0400, Charles Crouch wrote: Any more takers for the tripleo mid-cycle meetup in Raleigh? If so, please sign up on the etherpad below. The hotel group room rate will be finalized on Monday Jul 23rd (US time), after that time you will be on your own for finding accommodation.

Re: [openstack-dev] [Neutron][LBaaS] Layer7 Switching - L7 Rule - comapre_type values

Hi Dustin I agree with the concept you described but as far as I understand it is not currently supported in Neutron. So a driver should be fully compatible with the interface it implements. Avishay From: Dustin Lundquist [mailto:dus...@null-ptr.net] Sent: Tuesday, June 24, 2014 5:41 PM To: Open

Re: [openstack-dev] [Fuel] Removing old node logs

Hi, If user runs some experiments with creating/deleting clusters, then taking care of old logs is under user's responsibility, I suppose. Fuel configures log rotation with compression for remote logs, so old logs will be gzipped and will not take much space. In case of additional boolean paramet

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

> -Original Message- > From: Russell Bryant [mailto:rbry...@redhat.com] > Sent: 24 June 2014 13:08 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release > > On 06/24/2014 07:35 AM, Michael Still wrote: > > Phil -- I really w

Re: [openstack-dev] [Neutron] High bandwidth routers

On Jun 23, 2014, at 9:21 AM, CARVER, PAUL mailto:pc2...@att.com>> wrote: Is anyone using Neutron for high bandwidth workloads? (for sake of discussion let’s “high” = “50Gbps or greater”) With routers being implemented as network namespaces within x86 servers it seems like Neutron networks wou

Re: [openstack-dev] [hacking] rules for removal

On 06/24/2014 10:34 AM, Robert Collins wrote: On 23 June 2014 07:04, Jay Pipes wrote: I would also love to get rid of H404, otherwise known as the dumb rule that says if you have a multiline docstring, that there must be a summary line, then a blank line, then a detailed description. It makes

[openstack-dev] [Barbican] Barebones CA

Hi all, I’m sure this has been discussed somewhere and I’ve just missed it. Is there any value in creating a basic ‘CA’ and plugin to satisfy tests/integration in Barbican? I’m thinking something that probably performs OpenSSL certificate operations itself, ugly but perhaps useful for some thin

Re: [openstack-dev] [Fuel] Removing old node logs

Yeah, I thought about diagnostic snapshot too. Maybe it would be better to implement per-environment diagnostic snapshots? I.e. add diagnostic snapshot generate/download buttons/links in the environment actions tab. Such snapshot would contain info/logs about Fuel master node and nodes assigned to

Re: [openstack-dev] [Fuel] Removing old node logs

Hi guys, What about our diagnostic snapshot? I mean we're going to make snapshot of entire /var/log and obviously this old logs will be included in snapshot. Should we skip theem or such situation is ok? - Igor On Tue, Jun 24, 2014 at 5:57 PM, Aleksandr Didenko wrote: > Hi, > > If user run

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

On 06/24/2014 07:32 AM, Daniel P. Berrange wrote: On Tue, Jun 24, 2014 at 10:55:41AM +, Day, Phil wrote: -Original Message- From: John Garbutt [mailto:j...@johngarbutt.com] Sent: 23 June 2014 10:35 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [opens

Re: [openstack-dev] [Fuel] Removing old node logs

What about to gzip old logs by Astute and place them to a special directory, which will be managed under logrotate.d, and logrotate will remove untouched logs after 1 month. On Tue, Jun 24, 2014 at 6:57 PM, Aleksandr Didenko wrote: > Hi, > > If user runs some experiments with creating/deleting

Re: [openstack-dev] [hacking] rules for removal

On Tue, Jun 24, 2014 at 11:28 AM, Jay Pipes wrote: > > """ > This is a summary. > > And this is a description > """ > > will result in a failure of H404, due to the "This is a summary." not > being on the first line, like this: > > """This is a summary. > > And this is a description > """ > > It

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

One more reason why block storage management doesn't really work on file systems. I'm OK with storing the format, but that just means you fail migration/backup operations with different formats, right? On Mon, Jun 23, 2014 at 6:07 PM, Trump.Zhang wrote: > Hi, all: > > Currently, there are

Re: [openstack-dev] [TripleO] [Heat] Reminder: Mid-cycle Meetup - Attendance Confirmation

On 24/06/14 10:55 -0400, Jordan OMara wrote: On 20/06/14 16:26 -0400, Charles Crouch wrote: Any more takers for the tripleo mid-cycle meetup in Raleigh? If so, please sign up on the etherpad below. The hotel group room rate will be finalized on Monday Jul 23rd (US time), after that time you wi

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

On 24 June 2014 16:42, Avishay Traeger wrote: > One more reason why block storage management doesn't really work on file > systems. I'm OK with storing the format, but that just means you fail > migration/backup operations with different formats, right? Actually I think storing the format *fixes

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

On Tue, Jun 24, 2014 at 9:42 AM, Avishay Traeger wrote: > One more reason why block storage management doesn't really work on file > systems. I'm OK with storing the format, but that just means you fail > migration/backup operations with different formats, right? > ​+1... so nice that someb

[openstack-dev] [Nova][Scheduler]

Hi, I was wondering if there's a way to set a tag (key/value) of a Virtual Machine from within a scheduler filter ? I want to be able to tag a machine with a specific key/value after passing my custom filter Thanks, -- -- Abbass MAROUNI VirtualScale __

Re: [openstack-dev] [Neutron][LBaaS] Layer7 Switching - L7 Rule - comapre_type values

I brought this up on https://review.openstack.org/#/c/101084/. -Dustin On Tue, Jun 24, 2014 at 7:57 AM, Avishay Balderman wrote: > Hi Dustin > > I agree with the concept you described but as far as I understand it is > not currently supported in Neutron. > > So a driver should be fully compa

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

On Tue, Jun 24, 2014 at 9:56 AM, Duncan Thomas wrote: > On 24 June 2014 16:42, Avishay Traeger wrote: > > One more reason why block storage management doesn't really work on file > > systems. I'm OK with storing the format, but that just means you fail > > migration/backup operations with diffe

[openstack-dev] Stackalytics 0.6 released!

Hi Stackers, More then a year ago Mirantis announced Stackalytics as a public resource for the OpenStack community. Initially it was an internal tool for our performance tracking, but later resource became de-facto standard for measuring contribution statistics. We've started with several POCs on

Re: [openstack-dev] Periodic Security Checks

On Sat, Jun 21, 2014 at 11:33 AM, Alexandr Naumchev wrote: > Hello! > We have blueprints here: > > https://blueprints.launchpad.net/horizon/+spec/periodic-security-checks > > and here: > > https://blueprints.launchpad.net/nova/+spec/periodic-security-checks/ > > And we already have some code. Is

Re: [openstack-dev] [Fuel] Removing old node logs

Hello, @Aleks, it's a good idea to make snapshot per environment, but I think we can keep functionality to make snapshot for all nodes at once too. - Igor On Tue, Jun 24, 2014 at 6:38 PM, Aleksandr Didenko wrote: > Yeah, I thought about diagnostic snapshot too. Maybe it would be better to > i

Re: [openstack-dev] [Fuel] Removing old node logs

Yes, of course, snapshot for all nodes at once (like currently) should also be available. On Tue, Jun 24, 2014 at 7:27 PM, Igor Kalnitsky wrote: > Hello, > > @Aleks, it's a good idea to make snapshot per environment, but I think > we can keep functionality to make snapshot for all nodes at once

Re: [openstack-dev] [hacking] rules for removal

Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > On 06/22/2014 02:49 PM, Duncan Thomas wrote: > > On 22 June 2014 14:41, Amrith Kumar wrote: > >> In addition to making changes to the hacking rules, why don't we mandate > >> also > >> that perceived problems in the commit messa

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

On 06/11/2014 12:25 AM, Brian Rosmaita wrote: > That said, I prefer to have resources actually be things that the software creates. An action > isn't created. It is performed. > > I would prefer to replace the term "action(s)" with the term "task(s)", as is proposed for Nova [1]. Glance alre

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

On 06/11/2014 02:34 AM, Mark Washenberger wrote: I think the tasks stuff is something different, though. A task is a (potentially) long-running operation. So it would be possible for an action to result in the creation of a task. As the proposal stands today, the actions we've been looking at are

Re: [openstack-dev] [TripleO] dib-utils Release Question

Whoops, sorry, I didn't realize a tox.ini was required to release the project. We do actually need to push this to pypi because it's going to be a dep of diskimage-builder, so although there is currently no Python code in the project it needs to be pip installable anyway (similar to tripleo-image-

Re: [openstack-dev] [Horizon] Quick Survey: Horizon Mid-Cycle Meetup

> On 6/20/14, 6:24 AM, "Radomir Dopieralski" wrote: > > >On 20/06/14 13:56, Jaromir Coufal wrote: > >> On 2014/19/06 09:58, Matthias Runge wrote: > >>> On Wed, Jun 18, 2014 at 10:55:59AM +0200, Jaromir Coufal wrote: > My quick questions are: > * Who would be interested (and able) to get

Re: [openstack-dev] [Fuel] Removing old node logs

+1 to @Aleksandr On Tue, Jun 24, 2014 at 8:32 PM, Aleksandr Didenko wrote: > Yes, of course, snapshot for all nodes at once (like currently) should > also be available. > > > On Tue, Jun 24, 2014 at 7:27 PM, Igor Kalnitsky > wrote: > >> Hello, >> >> @Aleks, it's a good idea to make snapshot pe

[openstack-dev] [Neutron][LBaaS] Trouble with Devstack

I'm running Ubuntu 14.04, and rather suddenly I'm unable to run "./stack.sh" successfully. Brandon, who is also running Ubuntu 14.04, is seeing no issues here. However, all the same, I'm at a loss as to understand what the problem is. At the bottom of my text is the terminal output from runni

Re: [openstack-dev] [Neutron][LBaaS] Trouble with Devstack

Hi Trevor, I ran into the same issue. I worked around quickly by doing the following: - After stack.sh uninstalls pip, and fails with the "pkg_resources.DistributionNotFound: pip==1.4.1" error, install pip from easy_install - # easy_install pip - And re - stack.sh Haven't done the

Re: [openstack-dev] [Barbican] Barebones CA

Hello Robert, I would actually hope we have a self-contained certificate plugin implementation that runs 'out of the box' to enable certificate generation orders to be evaluated and demo-ed on local boxes. Is this what you were thinking though? Thanks, John

Re: [openstack-dev] [Neutron][LBaaS] Trouble with Devstack

Fawad, Thanks Fawad, that seems to have fixed my issue at this point. Amused me, since pip is supposed to replace easy_install, but I won't nitpick if it fixes it ha ha. -Trevor From: Fawad Khaliq [fa...@plumgrid.com] Sent: Tuesday, June 24, 2014 12:43 PM To: O

[openstack-dev] [Neutron][LBaaS] Which entities need status

I think we missed this discussion at the meet-up but I'd like to bring it up here. To me having a status on all entities doesn't make much sense, and justing having a status on a load balancer (which would be a provisioning status) and a status on a member (which would be an operational status) ar

Re: [openstack-dev] [barbican] Juno Mid-cycle Meetup

Hi Everyone, Just a reminder that the Barbican mid-cycle meetup is just under two weeks away. I just wanted to send out a link to the etherpad we’re using to do some pre-planning of things that need to be covered during the meetup https://etherpad.openstack.org/p/barbican-juno-meetup Also, ple

[openstack-dev] [swift] Providing a potentially more open interface to statsd statistics

I've lamented for awhile that while swift/statsd provide a wealth of information, it's in a somewhat difficult to use format. Specifically you have to connect to a socket and listen for messages. Furthermore if you're listening, nobody else can. I do realize there is a mechanism to send the d

[openstack-dev] [cinder][glance] Update volume-image-metadata proposal

Hi folks, I started working on this blueprint [1] but the work to be done is not limited to cinder python client. Volume-image-metadata is immutable in Cinder and Glance has RBAC image properties and it doesn't provide any way to find out which are those protecte

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi Brandon, I think just one status is overloading too much onto the LB object (which is perhaps something that a UI should do for a user, but not something an API should be doing.) > 1) If an entity exists without a link to a load balancer it is purely > just a database entry, so it would always

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi lbaas folks, IMO a status is really an important part of the API. In some old email threads Sam has proposed the solution for lbaas objects: we need to have several attributes that independently represent different types of statuses: - admin_state_up - operational status - provisioning state N

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

On Tue, 2014-06-24 at 18:53 +, Doug Wiegley wrote: > Hi Brandon, > > I think just one status is overloading too much onto the LB object (which > is perhaps something that a UI should do for a user, but not something an > API should be doing.) That is a good point and perhaps its another discu

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi Doug & Brandon, 1) +1 Doug -- I like the status "Building" but that's a personal preference. It's entirely up to the driver (but it should be reasonable) and we should pick the states up front (as we already do with constants) 2) We actually touched upon that with the distinction between sta

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Eugene, Thanks for the feedback. I have a feeling thats where we will end up going anyway so perhaps status on all entities for now is the proper way to build into that. I just want my objections to be heard. Thanks, Brandon On Tue, 2014-06-24 at 23:10 +0400, Eugene Nikanorov wrote: > Hi lbaas

[openstack-dev] Cinder pools implementation

Hi, As per our discussions in the last meeting I have made an etherpad which details different pool implementations and at the end comparison between the approaches. Please go through it and be ready with any questions or opinions for tomorrow's meeting. Here is the link for etherpad: https:/

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

Mid-day numbers update: startdelta from 2014-06-17mid-daydelta from startenddelta from startdelta from 2014-06-17New1751701705Incomplete25-621-421-4-10Critical/High for 5.1 140 140 33Critical/High for 5.1, Confirmed Triaged92 87-587-5 Medium/Low/Undefined for 5.1, Confirmed/Triaged238 230-8230-8

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

+1 to what Eugene just iterated: * Different types of statuses * Not every status on every object * Status should be API call Thanks, Vivek From: Eugene Nikanorov mailto:enikano...@mirantis.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:opensta

Re: [openstack-dev] [neutron][nova] nova needs a new release of neutronclient for OverQuotaClient exception

On Mon, Jun 23, 2014 at 11:08 AM, Kyle Mestery wrote: > On Mon, Jun 23, 2014 at 8:54 AM, Matt Riedemann > wrote: >> There are at least two changes [1][2] proposed to Nova that use the new >> OverQuotaClient exception in python-neutronclient, but the unit test jobs no >> longer test against trunk-

Re: [openstack-dev] [hacking] rules for removal

On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote: > Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > > On 06/22/2014 02:49 PM, Duncan Thomas wrote: > > > On 22 June 2014 14:41, Amrith Kumar wrote: > > >> In addition to making changes to the hacking rules, why don't we manda

[openstack-dev] [NFV] Specific example NFV use case - ETSI #5, virtual IMS

Hello all Following on from my contribution last week of a specific NFV use case (a Session Border Controller) here's another one, this time for an IMS core (part of ETSI NFV use case #5). As we touched on at last week's meeting, this is not making claims for what every example of a virtual IMS c

Re: [openstack-dev] [Fuel] Support for plugins in fuel client

Why not to use stevedore? On Wed, Jun 18, 2014 at 1:42 PM, Igor Kalnitsky wrote: > Hi guys, > > Actually, I'm not a fun of cliff, but I think it's a good solution to use > it in our fuel client. > > Here some pros: > > * pluggable design: we can encapsulate entire command logic in separate > pl

Re: [openstack-dev] [Nova][Scheduler]

On Jun 24, 2014 9:00 AM, "Abbass MAROUNI" wrote: > > Hi, > > I was wondering if there's a way to set a tag (key/value) of a Virtual Machine from within a scheduler filter ? The scheduler today is just for placement. And since we are in the process of trying to split it out, I don't think we want

Re: [openstack-dev] [FUEL] OpenStack patching and FUEL upgrade follow-up meeting minutes

I think, Vladimir means, that we need to improve our scheduling of the CI jobs over available CI resources. As I know, now we have a dedicated server groups for separate tests and we cannot use free resources of other server groups in case of overbalanced load. On Thu, Jun 5, 2014 at 6:52 PM, Jes

Re: [openstack-dev] [nova] Set compute_node:hypervisor_nodename as unique and not null

On Jun 18, 2014 11:40 AM, "Manickam, Kanagaraj" wrote: > > Hi, > > > > This mail is regarding the required model change in nova. Please fine more details below: > > > > As we knew, Nova db has the table “compute_nodes” for modelling the hypervisors and its using the “hypervisor_hostname” field to

Re: [openstack-dev] [hacking] community consensus and removing rules

On 06/24/2014 04:49 AM, Mark McLoughlin wrote: > On Mon, 2014-06-23 at 19:55 -0700, Joe Gordon wrote: > >> * Add a new directory, contrib, for local rules that multiple >> projects use but are not generally considered acceptable to be >> enabled by default. This way we can re

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Jun 18, 2014 3:03 PM, "Chris Friesen" wrote: > > The output of "nova list" and "nova show" reflects the current status in the database, not the actual state on the compute node. > > If the instances in question are on a compute node that is currently "down", then the information is stale and po

Re: [openstack-dev] [hacking] rules for removal

Excerpts from Mark McLoughlin's message of 2014-06-24 12:49:52 -0700: > On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote: > > Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > > > On 06/22/2014 02:49 PM, Duncan Thomas wrote: > > > > On 22 June 2014 14:41, Amrith Kumar wrote:

Re: [openstack-dev] [Barbican] Barebones CA

Yeah pretty much. That¹s something I¹d be interested to work on, if work isn¹t ongoing already. -Rob On 24/06/2014 18:57, "John Wood" wrote: >Hello Robert, > >I would actually hope we have a self-contained certificate plugin >implementation that runs 'out of the box' to enable certificate

[openstack-dev] [sahara] Upgrade of Hadoop components inside released version

Hi Team, I want to raise topic about upgrade of components in Hadoop version that is already supported by released Sahara plugin. The question is raised because of several change requests [1] and [2]. Topic was discussed in Atlanta ([3]), but we didn't come to the decision. All of us agreed that

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On 06/24/2014 04:42 PM, Joe Gordon wrote: > > On Jun 18, 2014 3:03 PM, "Chris Friesen" > wrote: >> >> The output of "nova list" and "nova show" reflects the current status > in the database, not the actual state on the compute node. >> >> If the instances in qu

  1   2   >