Re: [openstack-dev] Disaster Recovery for OpenStack - call for stakeholder - discussion reminder

Hi List, I was looking at the etherpad and March 19 notes and have few Qs 1) How is the "DR middleware" (depicted in Ron's youtube video) different than the "replication agent" (noted in the March 19 etherpad notes). Are they same, if not, how/why are they different ? 2) Maybe a dumb Q.. but

Re: [openstack-dev] OpenStack/GSoC

Hi Dims! I have submitted my proposal to the Google GSoC site and I will upload it to the OpenStack GSoC wiki soon. Could you please review it for me? Please inform me if anything else is needed. Thank you, Dániel Csubák (csuby) 2014-03-18 16:19 GMT+01:00 Davanum Srinivas : > Dear Students, >

[openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

HI, all cause of the Juno, the PCI discuss keen open, for group VS to flavor/extra-information based solution. there is a use case, which group based solution can not supported well. please considerate of this, and choose the flavor/extra-information based solution. Groups problem: I: exposed

Re: [openstack-dev] [qa] API schema location

On Tue, 18 Mar 2014 19:52:27 +0100 "Koderer, Marc" wrote: > > Am I missing something or are these schemas being added now just a > > subset of what is being used for negative testing? Why can't we > > either add the extra negative test info around the new test > > validation patches and get the d

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Thu, 2014-03-20 at 01:28 +, Joshua Harlow wrote: > Proxying from yahoo's open source director (since he wasn't initially > subscribed to this list, afaik he now is) on his behalf. > > From Gil Yehuda (Yahoo’s Open Source director). > > I would urge you to avoid creating a dependency betwee

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

On Wed, 19 Mar 2014, Sullivan, Jon Paul wrote: > > From: James Slagle [mailto:[email protected]] > > Sent: 18 March 2014 19:58 > > Subject: [openstack-dev] [TripleO] Alternating meeting time for more TZ > > friendliness > > > > Our current meeting time is Tuesdays at 19:00 UTC. I think this

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination of the consequences are very fact intensive. I was the chair of the User Committee in developing the GPLv3 and I am therefor quite familiar with the legal issues. The i

Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

Just out of curiosity: what is the purpose of project "warm"? From the wiki page and the sample it looks pretty much like what Heat is doing. And "warm" is almost "HOT" so could you imagine your use cases can just be addressed by Heat using HOT templates? Regards, Thomas sahid wrote on 18/03/201

Re: [openstack-dev] Pecan Evaluation for Marconi

On 19/03/14 11:00 -0400, Doug Hellmann wrote: On Wed, Mar 19, 2014 at 7:31 AM, Thierry Carrez wrote: Kurt Griffiths wrote: > Kudos to Balaji for working so hard on this. I really appreciate his candid feedback on both frameworks. Indeed, that analysis is very much appreciated.

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On 03/19/2014 10:54 PM, Joe Gordon wrote: On Wed, Mar 19, 2014 at 9:25 AM, Miguel Angel Ajo mailto:[email protected]>> wrote: An advance on the changes that it's requiring to have a py->c++ compiled rootwrap as a mitigation POC for havana/icehouse. https://github.com/mange

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

Hi all, First of all, thanks for your suggestions! To summarize the discussions here: 1. We are not going to install Mongo (because "is's wrong" ?) 2. Idea about spawning several collectors is suspicious (btw there is a patch that run several collectors: https://review.openstack.org/#/c/79962/.)

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/20/2014 05:49 AM, Nadya Privalova wrote: > Hi all, > First of all, thanks for your suggestions! > > To summarize the discussions here: > 1. We are not going to install Mongo (because "is's wrong" ?) We are not going to install Mongo "not from base distribution", because we don't do that for

[openstack-dev] Blueprint Review request for OpenStack Neutron Port Templates Network Policy.

Hi All, Me and my fellow friends (CCed) invite the community to review OpenStack Neutron Port Templates Network Policy blueprint submitted recently. Please review the same and feel free to suggest, comment and ask questions. Link to Open Stack blueprint page https://blueprints.launchpad.net/neut

Re: [openstack-dev] [Ceilometer] [QA] Slow Ceilometer resource_list CLI command

Hi, Re-architecting the schema might fix most of the performance issues of resource_list. And also, must do some work to improve the performance of meter-list. Is the Gordon's blue print gonna cover the both aspects ? https://blueprints.launchpad.net/ceilometer/+spec/big-data-sql Samp

Re: [openstack-dev] [nova] Backwards incompatible API changes

Christopher Yeoh wrote: > The patch was merged in October (just after Icehouse opened) and so has > been used in clouds that do CD for quite a while. After some discussion > on IRC I think we'll end up having to leave this backwards incompatible > change in there - given there are most likely users

[openstack-dev] Review request: A blueprint on OpenStack Neutron Port Templates Framework

Hi All, Me and my fellow friends (CCed) invite the community to review OpenStack Neutron Port Templates Framework blueprint submitted recently. Please review the same and feel free to suggest, comment and ask questions. Link to Open Stack blueprint page https://blueprints.launchpad.net/neutron/+

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Monty Taylor wrote: > On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: >> The problem with AGPL is that the scope is very uncertain and the >> determination of the consequences are very fact intensive. I was the >> chair of the User Committee in developing the GPLv3 and I am therefor >> quite famili

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

Sean, thank for analysis. JFYI, I did some initial profiling, it's described here https://www.mail-archive.com/[email protected]/msg19030.html. On Thu, Mar 20, 2014 at 2:15 PM, Sean Dague wrote: > On 03/20/2014 05:49 AM, Nadya Privalova wrote: > > Hi all, > > First of all, thank

[openstack-dev] Review request: A blueprint on OpenStack Neutron audit logging enhancement

Hi All, I would like you to go through a blueprint I submitted recently and get early comments from you, so that it covers all the use cases and anything else which will improve the blueprint. Link to Open Stack blueprint page https://blueprints.launchpad.net/neutron/+spec/neutron-auditlogging

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On 03/20/2014 05:31 AM, Miguel Angel Ajo wrote: On 03/19/2014 10:54 PM, Joe Gordon wrote: On Wed, Mar 19, 2014 at 9:25 AM, Miguel Angel Ajo mailto:[email protected]>> wrote: An advance on the changes that it's requiring to have a py->c++ compiled rootwrap as a mitigation POC fo

[openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

Hello all, I have been working on adding tests in Tempest for Marconi, for the last few months. While there are many amazing people to work with, the process has been more difficult than I expected. Couple of pain-points and suggestions to make the process easier for myself & future contributo

Re: [openstack-dev] Review request: A blueprint on OpenStack Neutron Port Templates Framework

Hi, As said here [1], please don't send review requests directly to the ML. [1] http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html 2014-03-20 12:08 GMT+01:00 Kamat, Maruti Haridas : > Hi All, > > Me and my fellow friends (CCed) invite the community to review OpenSt

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Wed, 2014-03-19 at 12:37 -0700, Devananda van der Veen wrote: > Let me start by saying that I want there to be a constructive discussion > around all this. I've done my best to keep my tone as non-snarky as I could > while still clearly stating my concerns. I've also spent a few hours > reviewin

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

+1 for performance analysis to understand what needs to be optimised. Metering should be light-weight. For those of us running in production, we don't have an option to turn ceilometer off some of the time. That we are not able to run through the gate tests hints that there are optimisations t

Re: [openstack-dev] [nova] Backwards incompatible API changes

On Thu, 20 Mar 2014 11:51:26 +0100 Thierry Carrez wrote: > > I still think reverting before release is an option we should > consider. My point is, yes we broke it back in October for people > doing CD (and they might by now have gotten used to it), if we let > this to release we'll then break it

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

Tim, yep. If you use one db for Ceilometer and Nova then nova's performance may be affected. I've seen this issue. Will start profiling ASAP. On Thu, Mar 20, 2014 at 3:59 PM, Tim Bell wrote: > > +1 for performance analysis to understand what needs to be optimised. > Metering should be light-wei

Re: [openstack-dev] OpenStack/GSoC

On 03/18/2014 07:19 PM, Davanum Srinivas wrote: Dear Students, Student application deadline is on Friday, March 21 [1] Once you finish the application process on the Google GSoC site. Please reply back to this thread to confirm that all the materials are ready to review. thanks, dims [1] http

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 20/03/14 09:09 +, Mark McLoughlin wrote: On Wed, 2014-03-19 at 12:37 -0700, Devananda van der Veen wrote: Let me start by saying that I want there to be a constructive discussion around all this. I've done my best to keep my tone as non-snarky as I could while still clearly stating my con

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: > Monty Taylor wrote: > > On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: > >> The problem with AGPL is that the scope is very uncertain and the > >> determination of the consequences are very fact intensive. I was the > >> chair of the User

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Tue, Mar 18, 2014 at 7:38 PM, Yuriy Taraday wrote: > I'm aiming at ~100 new lines of code for daemon. Of course I'll use some > batteries included with Python stdlib but they should be safe already. > It should be rather easy to audit them. > Here's my take on this: https://review.openstack.o

Re: [openstack-dev] [Marconi] [Ceilometer] Why is marconi a queue implementation vs a provisioning API?

- Original Message - > Monty Taylor wrote: > > On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: > >> The problem with AGPL is that the scope is very uncertain and the > >> determination of the consequences are very fact intensive. I was the > >> chair of the User Committee in developing the

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 03/20/2014 08:36 AM, Mark McLoughlin wrote: > On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: >> Monty Taylor wrote: >>> On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination of the consequences are very

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/20/2014 01:27 PM, Nadya Privalova wrote: > Tim, yep. If you use one db for Ceilometer and Nova then nova's > performance may be affected. If I understood it correctly the problem is not the higher load produced directly by Ceilometer on the database. The problem is that the Ceilometer comput

Re: [openstack-dev] Blueprint Review request for OpenStack Neutron Port Templates Network Policy.

On Thu, Mar 20, 2014 at 5:21 AM, Kumar, Vinod (HP Networking) < [email protected]> wrote: > Hi All, > > > > Me and my fellow friends (CCed) invite the community to review OpenStack > Neutron Port Templates Network Policy blueprint submitted recently. > > Please review the same and feel free to

Re: [openstack-dev] Review request: A blueprint on OpenStack Neutron Port Templates Framework

Also, before undertaking large blueprints like this, I'd highly encourage folks to look at existing work in the community. The Neutron community has been working on Group Based Policy since last fall. There was a design summit session in Hong Kong around this as well, and we've been meeting weekly

Re: [openstack-dev] OpenStack/GSoC

Team, Here's what i see in the system so far. Mentors: ybudupi blint boris_42 coroner cppcabrera sriramhere arnaudleg greghaynes hughsaunders julim ddutta (Organization Administrator) dims (Organization Administrator) Projects: Cross-services Scheduler project. Artem Shepelev Artem Shepelev Prop

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

We're using a dedicated MongoDB instance for ceilometer and a distinct DB for each of the Nova cells. Tim From: Nadya Privalova [mailto:[email protected]] Sent: 20 March 2014 13:27 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Ceilometer][QA

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

Wow Yuriy, amazing and fast :-), benchmarks included ;-) The daemon solution only adds 4.5ms, good work. I'll add some comments in a while. Recently I talked with another engineer in Red Hat (working in ovirt/vdsm), and they have something like this daemon, and they are using BaseMan

[openstack-dev] Hierarchicical Multitenancy Discussion

Hi, As discussed in the last meeting, i had changed the POC for Quota Management in Hierarchical Multitenancy setup. Please check the following links Twiki Page -> https://wiki.openstack.org/wiki/POC_for_QuotaManagement#API_URLs Code (diff) -> https://github.com/vinodkumarboppanna/POC-For-Quo

Re: [openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

Hi Yongli, I'm very glad that you bring this up and relive our discussion on PCI passthrough and its application on networking. The use case you brought up is: user wants a FASTER NIC from INTEL to join a virtual networking. By FASTER, I guess that you mean that the user is allowed t

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On 03/20/2014 12:32 PM, Monty Taylor wrote: On 03/20/2014 05:31 AM, Miguel Angel Ajo wrote: On 03/19/2014 10:54 PM, Joe Gordon wrote: On Wed, Mar 19, 2014 at 9:25 AM, Miguel Angel Ajo mailto:[email protected]>> wrote: An advance on the changes that it's requiring to have a

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Hi y'all! It's good to be back, eh! On Wed, Mar 19, 2014 at 11:35 PM, Eugene Nikanorov wrote: > >>- Active/Passive Failover >> - I think this is solved with multiple pools. >> >> The multiple pools support that is coming with L7 rules is to support >> content-switching based on L7 HTTP

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 20/03/14 08:52 -0400, Sean Dague wrote: On 03/20/2014 08:36 AM, Mark McLoughlin wrote: On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: Monty Taylor wrote: On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Let me start by saying that I want there to be a constructive discussion around all this. I've done my best to keep my tone as non-snarky as I could while still clearly stating my concerns. I've also spent a few hours reviewing the current code and docs. Hopefully this contribution will be bene

Re: [openstack-dev] [nova] Backwards incompatible API changes

I concur. I suspect people/organizations who are doing CD *probably* won't mind such a change as much as the people who use the versioned releases will mind backwards-incompatibility. Correct me if I'm wrong, but doing CD requires a certain willingness to roll with the punches, so to speak, where

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

> > > I agree this is quite an issue but I also think that pretending that > we'll be able to let OpenStack grow with a minimum set of databases, > brokers and web servers is a bit unrealistic. The set of supported > technologies won't be able to fulfill the needs of all the > yet-to-be-discovered

[openstack-dev] [keystone] python-keystoneclient unit tests only if python-memcache is installed

Hi, I've noticed that if there's python-memcache installed, building the python-keystoneclient (last version: 0.6.0) will produce some unit tests errors (see below the first 2 errors, there's 7 of them in total). If I apt-get purge python-memcache, the errors don't show. I'm worried that this is

[openstack-dev] Display images/icon in Horizon Tables

?Hi, I'm creating a custom panel for horizon. I have developed a table that displays some information, and I would like to add a 'icon' to each row. Ideally, I want to be able to specify the URL of a remote image, and have it displayed using the tag. Can this be acheived with filters, or s

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Tue, Mar 11, 2014 at 12:58 AM, Carl Baldwin wrote: > > https://etherpad.openstack.org/p/neutron-agent-exec-performance > I've added info on how we can speedup work with namespaces by setting namespaces by ourselves using setns() without "ip netns exec" overhead. -- Kind regards, Yuriy.

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On 03/20/2014 05:41 AM, Yuriy Taraday wrote: On Tue, Mar 18, 2014 at 7:38 PM, Yuriy Taraday mailto:[email protected]>> wrote: I'm aiming at ~100 new lines of code for daemon. Of course I'll use some batteries included with Python stdlib but they should be safe already. It shoul

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/20/2014 06:15 AM, Sean Dague wrote: On 03/20/2014 05:49 AM, Nadya Privalova wrote: Hi all, First of all, thanks for your suggestions! To summarize the discussions here: 1. We are not going to install Mongo (because "is's wrong" ?) We are not going to install Mongo "not from base distribu

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Thanks for the input. I too was thinking "IP Access Control" could be solved with the firewall service in Neutron. To clarify what I mean check out our current API docs on this feature here.

Re: [openstack-dev] Display images/icon in Horizon Tables

This is easy to accomplish by creating a custom template for a cell. In your table, instead of providing a data field for the column, provide a method name, have that method load a custom HTML template. Here is an example of this without an image of this method: https://github.com/openstack/ho

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 03/20/2014 11:11 AM, Chuck Thier wrote: > > I agree this is quite an issue but I also think that pretending that > we'll be able to let OpenStack grow with a minimum set of databases, > brokers and web servers is a bit unrealistic. The set of supported > technologies won't be ab

Re: [openstack-dev] [Openstack-dev] [Nova] use Keystone V3 token to volume attachment

On 3/19/2014 10:02 AM, Matthew Treinish wrote: On Wed, Mar 19, 2014 at 09:35:34AM -0500, Matt Riedemann wrote: On 3/19/2014 2:48 AM, Shao Kai SK Li wrote: Hello: I am working on this patch(https://review.openstack.org/#/c/77524/) to fix bugs about volume attach failure with keystone

[openstack-dev] [Nova] Updates to Juno blueprint review process

We recently discussed the idea of using gerrit to review blueprint specifications [1]. There was a lot of support for the idea so we have proceeded with putting this together before the start of the Juno development cycle. We now have a new project set up, openstack/nova-specs. You submit change

Re: [openstack-dev] [keystone] python-keystoneclient unit tests only if python-memcache is installed

Yes, those tests are conditionally executed if https://pypi.python.org/pypi/python-memcached/ is installed and if so, memcached is assumed to be accessible on localhost. Unfortunately the test suite doesn't have a sanity check for that following assumption, so the test failures aren't particularly

Re: [openstack-dev] [Openstack-dev] [Nova] use Keystone V3 token to volume attachment

Conversation from #openstack-dev starting at 2014-03-20T15:09:49 http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2014-03-20.log On 3/20/2014 10:47 AM, Matt Riedemann wrote: On 3/19/2014 10:02 AM, Matthew Treinish wrote: On Wed, Mar 19, 2014 at 09:35:34AM -0500, Matt

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Thu, Mar 20, 2014 at 7:28 PM, Rick Jones wrote: > On 03/20/2014 05:41 AM, Yuriy Taraday wrote: > >> Benchmark included showed on my machine these numbers (average over 100 >> iterations): >> >> Running 'ip a': >>ip a : 4.565ms >>

[openstack-dev] [Neutron][IPv6] Prefix delegation - API Attributes

Hi, Anthony Veiga and I did a small bit of whiteboarding this morning to sketch out what a prefix delegation would look like in the Neutron API. https://wiki.openstack.org/wiki/Neutron/IPv6/PrefixDelegation -- Sean M. Collins ___ OpenStack-dev mailing

Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

warm is just an other client, like we can have for the cli. It does not claim to do what Heat can. It should be useful to prepare some templates to be reused in different OpenStack environment without using script shell or python. When I said standalone client, I mean there is no need to install s

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

> The incorporation of AGPLv3 code Into OpenStack Project is a >significant decision To be clear, Marconi does not incorporate any AGPL code itself; pymongo is Apache2 licensed. Concerns over AGPL were raised when Marconi was incubated, and I totally respect that some folks are not comfortable w

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Thu, Mar 20, 2014 at 5:41 PM, Miguel Angel Ajo wrote: > >Wow Yuriy, amazing and fast :-), benchmarks included ;-) > >The daemon solution only adds 4.5ms, good work. I'll add some comments > in a while. > >Recently I talked with another engineer in Red Hat (working > in ovirt/vdsm),

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/20/2014 11:35 AM, David Kranz wrote: > On 03/20/2014 06:15 AM, Sean Dague wrote: >> On 03/20/2014 05:49 AM, Nadya Privalova wrote: >>> Hi all, >>> First of all, thanks for your suggestions! >>> >>> To summarize the discussions here: >>> 1. We are not going to install Mongo (because "is's wron

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On 03/20/2014 09:07 AM, Yuriy Taraday wrote: On Thu, Mar 20, 2014 at 7:28 PM, Rick Jones mailto:[email protected]>> wrote: Interesting result. Which versions of sudo and ip and with how many interfaces on the system? Here are the numbers: % sudo -V Sudo version 1.8.6p7 Sudoers policy

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

> >>>- Active/Passive Failover >>> - I think this is solved with multiple pools. >>> >>> The multiple pools support that is coming with L7 rules is to support >>> content-switching based on L7 HTTP information (URL, headers, etc.). There >>> is no support today for an active vs. passive p

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 03/20/2014 12:29 PM, Kurt Griffiths wrote: >> The incorporation of AGPLv3 code Into OpenStack Project is a >> significant decision > > To be clear, Marconi does not incorporate any AGPL code itself; pymongo is > Apache2 licensed. > > Concerns over AGPL were raised when Marconi was incubated,

Re: [openstack-dev] Display images/icon in Horizon Tables

Thanks, That worked perfectly. I defined a method like this: def get_image_url(stack): template_name = 'openwave/stack_catalogue/_icon.html' context = {"stack" : stack } return template.loader.render_to_string(template_name, context) Stack is my class that has a field called image_i

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Thu, Mar 20, 2014 at 8:23 PM, Rick Jones wrote: > On 03/20/2014 09:07 AM, Yuriy Taraday wrote: > >> On Thu, Mar 20, 2014 at 7:28 PM, Rick Jones > > wrote: >> Interesting result. Which versions of sudo and ip and with how many >> interfaces on the system? >>

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/20/2014 12:31 PM, Sean Dague wrote: On 03/20/2014 11:35 AM, David Kranz wrote: On 03/20/2014 06:15 AM, Sean Dague wrote: On 03/20/2014 05:49 AM, Nadya Privalova wrote: Hi all, First of all, thanks for your suggestions! To summarize the discussions here: 1. We are not going to install Mo

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Mar 20, 2014, at 5:52 AM, Sean Dague wrote: > On 03/20/2014 08:36 AM, Mark McLoughlin wrote: >> On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: >>> Monty Taylor wrote: On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: > The problem with AGPL is that the scope is very uncertain

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

>To be clear, Marconi does not incorporate any AGPL code itself; pymongo is Apache2 licensed. Understood, but here's the rub. Someone else is going to want to build on this (which it the point of this open source project). Whereas 'pymongo' is Apache licensed, since the copyright holder, MongoDB

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Stephen, I don’t think the active/passive pools feature is referring to the HA of loadbalancers. This is about the ability to divide the list of members servicing load-balanced requests into 2 groups: The first one is active and the second one is passive (or a backup pool). If all the members i

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

The use case from our customers has been mostly for database (MySql) load balancing. If the master goes down then they want another master/slave on standby ready to receive traffic. In the simplest case, I think Neutron can achieve this with 2 pools with 1 node each. If pool #1 goes down then po

Re: [openstack-dev] [horizon] horizon PyPi distribution missing

On Mon, Mar 17, 2014 at 5:22 AM, Timur Sufiev wrote: > It depends on openstack_dashboard, namely on > openstack_dashboard.settings. So it is fine from Murano's point of > view to have openstack_dashboard published on PyPi. Many thanks for > considering my request :). > We are having this issue too

[openstack-dev] How does the role stuff work in real production deployment?

Hi How does the keystone role stuff work in real production deployment? Every service team considers the user who has role with the name "admin" as "admin". So basically I can't have a separate admin user for keystone, nova, swift. Isn't this a security issue? Given a project how to

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Right, it could be solved by pool's member weights and appropriate scheduling algorithm. Eugene. On Thu, Mar 20, 2014 at 9:21 PM, Jorge Miramontes < [email protected]> wrote: > The use case from our customers has been mostly for database (MySql) > load balancing. If the master go

Re: [openstack-dev] [Nova] Updates to Juno blueprint review process

IMHO, I feel like many of the things in the "Implementation" section should just be in the launchpad BP, and not in the git-tracked spec. While I think that the idea of having the BP in Gerrit is a great idea, I feel like the details of the "Implementation" section (assignee, etc) will lead to

Re: [openstack-dev] [horizon] horizon PyPi distribution missing

As a workaround you can use tarball in requirements.txt (or test-requirements.txt). Each versions of Horizon/openstack_dashboard is available at http://tarballs.openstack.org/horizon/. Each tarball is generated every time corresponding branch or tag is updated. If you would like to use horizon I-3

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Jorge, Just to clarify, is this a feature to control which client IP addresses can access the VIP? Thanks, Youcef From: Jorge Miramontes [mailto:[email protected]] Sent: Thursday, March 20, 2014 8:37 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [

[openstack-dev] [nova] instances stuck with task_state of REBOOTING

I'm running a havana install, and during some testing I've managed to get the system into a state where two instances are up and running but are reporting a task_state of REBOOTING. I can see the nova-api logs showing the soft-reboot request. I don't see a corresponding nova-compute log indic

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

On Thu, Mar 20, 2014 at 11:35:15AM +, Malini Kamalambal wrote: > Hello all, > > I have been working on adding tests in Tempest for Marconi, for the last few > months. > While there are many amazing people to work with, the process has been more > difficult than I expected. > > Couple of pai

Re: [openstack-dev] [nova] instances stuck with task_state of REBOOTING

Hi Chris, Are you in the position to determine whether or not this happens with the latest master code? Either way, it definitely looks like a bug. If you could give more specific reproduction instructions, that would be most useful. Best Regards, Solly Ross - Original Message - From:

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Aah! Yes-- you are correct. I was thinking a the load balancer level, not the pool level. (Maybe we can clarify this distinction in the requirements doc?) But I would also be surprised if there are load balancers today that don't intrinsically offer "active / backup pool membership" as a standar

Re: [openstack-dev] [nova] Backwards incompatible API changes

On 03/20/2014 11:05 AM, Solly Ross wrote: I concur. I suspect people/organizations who are doing CD *probably* won't mind such a change as much as the people who use the versioned releases will mind backwards-incompatibility. Correct me if I'm wrong, but doing CD requires a certain willingness

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Kurt, Your point is that NoSQL solution may be required for innovative project. And that is MongoDB. But what if come another amazing project that needs CouchDB, neo4j, Riak, (put your favorite NoSQL DB here)? It would be in the same position cause everyone would say hey, we already have NoSQL in

Re: [openstack-dev] [nova] Backwards incompatible API changes

Sorry if my meaning was unclear. I think we should revert as well. Best Regards, Solly Ross - Original Message - From: "David Kranz" To: [email protected] Sent: Thursday, March 20, 2014 2:20:42 PM Subject: Re: [openstack-dev] [nova] Backwards incompatible API changes On

Re: [openstack-dev] [nova] instances stuck with task_state of REBOOTING

On 03/20/2014 12:06 PM, Solly Ross wrote: Hi Chris, Are you in the position to determine whether or not this happens with the latest master code? Either way, it definitely looks like a bug. Unfortunately not right now, working towards a deadline. If you could give more specific reproduction

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

If we limited Openstack projects to just one database, is that database (e.g. MySQL) going to be the best storage deployment for that job? Or are there cases where other technologies such as Redis, MongoDB, Cassandra, CouchDB, etc make more sense? Marconi has a pluggable storage driver model w

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Excerpts from Flavio Percoco's message of 2014-03-19 03:01:19 -0700: > FWIW, I think there's a value on having an sqlalchemy driver. It's > helpful for newcomers, it integrates perfectly with the gate and I > don't want to impose other folks what they should or shouldn't use in > production. Marcon

Re: [openstack-dev] [nova] instances stuck with task_state of REBOOTING

On 03/20/2014 12:29 PM, Chris Friesen wrote: The fact that there are no success or error logs in nova-compute.log makes me wonder if we somehow got stuck in self.driver.reboot(). Also, I'm kind of wondering what would happen if nova-compute was running reboot_instance() and we rebooted the cont

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

Thanks Matt for your response !! It has clarified some of the 'cloudy areas' ;) "So having only looked at the Marconi ML thread and not the actual TC meeting minutes I might be missing the whole picture. But, from what I saw when I looked at both a marconi commit and a tempest commit is that ther

Re: [openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

On Thu, 2014-03-20 at 13:50 +, Robert Li (baoli) wrote: > Hi Yongli, > > I'm very glad that you bring this up and relive our discussion on PCI > passthrough and its application on networking. The use case you brought up > is: > >user wants a FASTER NIC from INTEL to join a virtual

[openstack-dev] [Cinder] [Nova] Blueprint review request for pagination sorting enhancements

Please review the following blueprints, both are scoped to supporting multiple sort key and sort directions on the API request when retrieving volumes and servers. https://blueprints.launchpad.net/cinder/+spec/cinder-pagination https://blueprints.launchpad.net/nova/+spec/nova-pagination Note th

Re: [openstack-dev] [qa] API schema location

On Thu, 2014-03-20 at 19:34 +1100, Christopher Yeoh wrote: > On Tue, 18 Mar 2014 19:52:27 +0100 > "Koderer, Marc" wrote: > > > > Am I missing something or are these schemas being added now just a > > > subset of what is being used for negative testing? Why can't we > > > either add the extra nega

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

I will agree that the TC language is not as strong as it should be (and really should be clarified, but I don't think that's going to happen until the release is looking solid). Honestly, though, I think Sahara is a good example here of the level of that we expect. They have actively engaged with u

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

> -Original Message- > From: Malini Kamalambal [mailto:[email protected]] > Sent: Thursday, March 20, 2014 12:13 PM > > 'project specific functional testing' in the Marconi context is > treating > Marconi as a complete system, making Marconi API calls & verifying the > resp

Re: [openstack-dev] [Nova] Updates to Juno blueprint review process

On Thu, Mar 20, 2014 at 10:49 AM, Russell Bryant wrote: > We recently discussed the idea of using gerrit to review blueprint > specifications [1]. There was a lot of support for the idea so we have > proceeded with putting this together before the start of the Juno > development cycle. > > We no

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/20/2014 01:01 PM, David Kranz wrote: > On 03/20/2014 12:31 PM, Sean Dague wrote: >> On 03/20/2014 11:35 AM, David Kranz wrote: >>> On 03/20/2014 06:15 AM, Sean Dague wrote: On 03/20/2014 05:49 AM, Nadya Privalova wrote: > Hi all, > First of all, thanks for your suggestions! >

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

On Thu, Mar 20, 2014 at 1:19 PM, Rochelle.RochelleGrober < [email protected]> wrote: > > > > -Original Message- > > From: Malini Kamalambal [mailto:[email protected]] > > Sent: Thursday, March 20, 2014 12:13 PM > > > > 'project specific functional testing' in the Mar

  1   2   >