Re: [openstack-dev] [Heat] re: discussion about passing metadata into provider stacks as parameters

On Fri, 2013-06-21 at 15:49 +1000, Angus Salkeld wrote: > On 20/06/13 22:19 -0400, cbjc...@linux.vnet.ibm.com wrote: > > > >So anyway, let's get back to the topic this thread was discussing > >about - "passing meta data into provider stacks". > > > >It seems that we have all reached an agreement t

Re: [openstack-dev] [Heat][State-Management] Task/Workflow requirements for Heat

On 20/06/13 21:34, Joshua Harlow wrote: Thanks Adrian for adding that, Zane, it would be great if you could show up. I have a few questions about said heat requirements, especially about how the current mechanism accomplishes those requirements. Sorry for missing that meeting, I left the house

[openstack-dev] Basic configuration with VMs with a local private network

Hi. We are trying to get a basic scenario with two VMs with private IP addresses configured in a Compute node controlled by a Controller node. We want to achieve a basic private network with some VMs. We tried using Open vSwitch Quantum plugin to configure the network, but we have not achieved our

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

On 21-06-13 07:24, Kashyap Chamarthy wrote: On 06/20/2013 10:18 PM, Russell Bryant wrote: On 06/20/2013 10:36 AM, Giorgio Franceschi wrote: Hello, I created a blueprint for the implementation of: A tool for pinning automatically each running virtual CPU to a physical one in the most efficient

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

It seems that numad is libvirt specific - is that the case? I'm not sure if there is a daemon for other hypervisors but would it make sense to have this functionality in OpenStack so we can extend it to work for each hypervisor allowing it to control the affinity in their own way? I guess this

Re: [openstack-dev] [Nova] Adding a xenapi_max_ephemeral_disk_size_gb flag

Its just that the limit you want to set varies depending on the flavor. So flavor = 10TB, limit = 2000GB, the final disk is a bit of an odd size, maybe 1024GB would be a better split. Although you make a good point, maybe we should set the "splitting point" in extra specs in the flavor, rather tha

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

On Fri, Jun 21, 2013 at 09:10:32AM +, Bob Ball wrote: > It seems that numad is libvirt specific - is that the case? No, it is a completely independant project https://git.fedorahosted.org/git/numad.git It existed before libvirt started using it for automatic placement. Daniel -- |: http:

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

On Thu, Jun 20, 2013 at 12:48:16PM -0400, Russell Bryant wrote: > On 06/20/2013 10:36 AM, Giorgio Franceschi wrote: > > Hello, I created a blueprint for the implementation of: > > > > A tool for pinning automatically each running virtual CPU to a physical > > one in the most efficient way, balanci

Re: [openstack-dev] disabling a tenant still allow user token

Hello, [moving on the public mailing list since this bug is anyway public] On 3 Jun 2013, at 17:25, Dolph Mathews wrote: > Apologies for the delayed response on this. We have several related open bugs > and I wanted to investigate them all at once, and perhaps fix them all in one > pass. > Di

Re: [openstack-dev] XML Support for Nova v3 API

+1 for a world class JSON API, tooling and docs. I was +1 for a cheap XML API, but maybe that will make those who want XML even more unhappy? John On 20 June 2013 21:57, Kevin L. Mitchell wrote: > On Thu, 2013-06-20 at 16:02 -0400, Sean Dague wrote: >> There are lots of nice things we could do,

[openstack-dev] Removing OS_AUTH_SYSTEM

Hello, We have discussed this some time ago to remove the OS_AUTH_SYSTEM from novaclient since this was implemented for RAX and these days RAX has moved to pyrax. Since last time I have looked into this it seems that there was some updates to it : https://github.com/openstack/python-novaclient/b

Re: [openstack-dev] Removing OS_AUTH_SYSTEM

Hi, some comments inline. On Fri 21 Jun 2013 (12:53), Chmouel Boudjnah wrote: > Hello, > > We have discussed this some time ago to remove the OS_AUTH_SYSTEM from > novaclient since this was implemented for RAX and these days RAX has > moved to pyrax. > > Since last time I have looked into this it

[openstack-dev] [Infra][Nova] Running Nova DB API tests on different backends

Hi, all! In Nova we've got a DB access layer known as "DB API" and tests for it. Currently, those tests are run only for SQLite in-memory DB, which is great for speed, but doesn't allow us to spot backend-specific errors. There is a blueprint ( https://blueprints.launchpad.net/nova/+spec/db-api-t

Re: [openstack-dev] [Infra][Nova] Running Nova DB API tests on different backends

On 06/21/2013 07:40 AM, Roman Podolyaka wrote: Hi, all! In Nova we've got a DB access layer known as "DB API" and tests for it. Currently, those tests are run only for SQLite in-memory DB, which is great for speed, but doesn't allow us to spot backend-specific errors. There is a blueprint (http

Re: [openstack-dev] [Infra][Nova] Running Nova DB API tests on different backends

Hello Sean, all, Currently there are ~30 test classes in DB API tests, containing ~370 test cases. setUpClass()/tearDownClass() would be definitely an improvement, but applying of all DB schema migrations for MySQL 30 times is going to take a long time... Thanks, Roman On Fri, Jun 21, 2013 at 3

[openstack-dev] Consolidate CLI Authentication

Hi, I have some questions regarding the "Consolidate CLI Authentication" (https://etherpad.openstack.org/keystoneclient-cli-auth and https://review.openstack.org/#/c/21942/). It looks like that the code for keystone client is almost ready for merge. What are the plans for the other clients (no

[openstack-dev] Adding 'rm' to compute filter

Hi, Referring to the Jenkins failure logs on https://review.openstack.org/#/c/32549/3, Log at http://logs.openstack.org/32549/3/check/gate-nova-python27/25158/console.html The command that the test tried to execute using nova's rootwrap was: COMMAND=/home/jenkins/workspace/gate-nova-python27/.t

Re: [openstack-dev] [PTLs] Proposed simplification around blueprint tracking

Thierry Carrez wrote: > A script will automatically and regularly align "series goal" with > "target milestone", so that the series and milestone views are > consistent (if someone sets target milestone to "havana-3" then the > series goal will be set to "havana"). Now if the Launchpad API was exp

Re: [openstack-dev] about the ovs plugin & ovs setup for the tunnel network type

For the list, I'll post the same response i gave you when you pinged me off-list about this: t was a long time ago when I wrote that, and the original goal was to use a single bridge, but there some something about how OVS worked at the time that required the two bridges. I think it was related t

[openstack-dev] SecurityImpact tagging in gerrit

This is a quick note to announce that the OpenStack gerrit system supports a SecurityImpact tag. If you are familiar with the DocImpact tag, this works in a similar fashion. Please use this in the commit message for any commits that you feel would benefit from a security review. Commits with thi

Re: [openstack-dev] Configuring Quantum REST Proxy Plugin

Hi Julio, If I get your message correctly, you have a proxy which is pretty much a shim layer between the big switch plugin (QuantumRestProxyV2) and the OpenNaaS server. In this case all you need to do is to configure the [restproxy] session of etc/quantum/plugins/bigswitch/restproxy.ini with the

Re: [openstack-dev] Removing OS_AUTH_SYSTEM

On 06/21/2013 06:53 AM, Chmouel Boudjnah wrote: > Hello, > > We have discussed this some time ago to remove the OS_AUTH_SYSTEM from > novaclient since this was implemented for RAX and these days RAX has > moved to pyrax. Rackspace should be ashamed for having spent a single second of effort on

Re: [openstack-dev] [Heat][State-Management] Task/Workflow requirements for Heat

Sweet, thx Zane. Looking forward to figuring out how we can make this all work. Fun times ahead ;) Sent from my really tiny device... On Jun 21, 2013, at 1:24 AM, "Zane Bitter" wrote: > On 20/06/13 21:34, Joshua Harlow wrote: >> Thanks Adrian for adding that, >> >> Zane, it would be great i

Re: [openstack-dev] SecurityImpact tagging in gerrit

Interesting. Does it automatically make the commit in "stealth mode" so that it's not seen in public? Thanks, Yun On Fri, Jun 21, 2013 at 11:26 AM, Bryan D. Payne wrote: > This is a quick note to announce that the OpenStack gerrit system supports > a SecurityImpact tag. If you are familiar wi

Re: [openstack-dev] SecurityImpact tagging in gerrit

Yun Mao wrote: > Interesting. Does it automatically make the commit in "stealth mode" so > that it's not seen in public? Thanks, Not at all. (1) there is no stealth mode in Gerrit (2) this is meant to get security design advice on new features, not to submit exploitable vulnerabilities. For the l

Re: [openstack-dev] Cells design issue

In my view a cell should only know about the queue it's connected to, and let the 'global' message queue to do its job of dispatching the messages to the right recipient: that would solve the problem altogether. Were federated queues and topic routing

Re: [openstack-dev] SecurityImpact tagging in gerrit

On Fri, Jun 21, 2013 at 12:08:43PM -0400, Yun Mao wrote: > Interesting. Does it automatically make the commit in "stealth mode" so > that it's not seen in public? Thanks, This tag is about asking for design input / code review from people with security expertize for new work. As such the code is a

Re: [openstack-dev] Cells design issue

On Fri, 2013-06-21 at 09:16 -0700, Armando Migliaccio wrote: > In my view a cell should only know about the queue it's connected to, > and let the 'global' message queue to do its job of dispatching the > messages to the right recipient: that would solve the problem > altogether. There is no "glob

Re: [openstack-dev] Cells design issue

On Jun 21, 2013, at 9:16 AM, Armando Migliaccio wrote: > In my view a cell should only know about the queue it's connected to, and let > the 'global' message queue to do its job of dispatching the messages to the > right recipient: that would solve the problem altogether. > > Were federated q

Re: [openstack-dev] Basic configuration with VMs with a local private network

I reckon the admin guide [1] contains sufficiently up-to-date information for the grizzly release. Please let me know if you find it lacks important information. We'll be more than happy to make the necessary amendments. Your scenario appears to be fairly simple. On the compute node you will need

Re: [openstack-dev] [Heat] re: discussion about passing metadata into provider stacks as parameters

On 21/06/13 07:49, Angus Salkeld wrote: On 20/06/13 22:19 -0400, cbjc...@linux.vnet.ibm.com wrote: So anyway, let's get back to the topic this thread was discussing about - "passing meta data into provider stacks". It seems that we have all reached an agreement that deletepolicy and updatepoli

[openstack-dev] [Heat] autoscaling question

Dear All, I'd like to have some confirmation about the mechanism that is going to be used to inform Heat's clients about instance create and destroy in an auto-scaling group. I am referring to the wiki page at https://wiki.openstack.org/wiki/Heat/AutoScaling. I assume, but I may be wrong, th

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

Sorry, my point about numad being libvirt specific was that I couldn't find references to other hypervisors using numad for their placement. I recognise that it's not _tied_ to libvirt but the reality seems to be that only libvirt uses it. Xen, for example, can't use numad because dom0 might o

Re: [openstack-dev] Cells design issue

On Fri, 2013-06-21 at 09:30 -0700, Chris Behrens wrote: > > On Mon, Jun 17, 2013 at 2:14 AM, Mark McLoughlin > wrote: > > I don't know whether I like it yet or not, but here's how it might > look: > > > > [cells] > > parents = parent1 > > children = child1, child2 > > > > [cell:parent1] > >

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

On Fri, Jun 21, 2013 at 05:09:24PM +, Bob Ball wrote: > Sorry, my point about numad being libvirt specific was that I > couldn't find references to other hypervisors using numad for > their placement. I recognise that it's not _tied_ to libvirt > but the reality seems to be that only libvirt u

Re: [openstack-dev] Configuring Quantum REST Proxy Plugin

Thanks Salvatore. That's right, the configuration for server and port resides in: etc/quantum/plugins/bigswitch/restproxy.ini Let us know if you need further help. ~Sumit. On Fri, Jun 21, 2013 at 8:37 AM, Salvatore Orlando wrote: > Hi Julio, > > If I get your message correctly, you have a proxy

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

> It seems that numad is libvirt specific - is that the case? Hi, Hyper-V 2012 supports NUMA as well. It'd be great to plan an hypervisor independent solution from the start. On 21.06.2013, at 11:13, "Bob Ball" wrote: > It seems that numad is libvirt specific - is that the case? > > I'm not

[openstack-dev] Celery

Hello all, Included here is a link to a Celery wiki, explaining what the Celery project is and how it works. Currently, celery is being used in a distributed pattern for the WIP task flow project. As such, links to both the distributed project, and its' parent task flow project have been includ

Re: [openstack-dev] The future of run_tests.sh

It sounds like the censuses in this thread is: In the long run, we want to kill run_tests.sh in favor of explaining how to use the underlying tools in a TESTING file. But in the short term, we should start moving toward using a TESTING file (such as https://review.openstack.org/#/c/33456/) but ke

Re: [openstack-dev] Celery

Sweet, thanks jessica for the awesome docs and work. From: Jessica Lucci mailto:jessica.lu...@rackspace.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Friday, June 21, 2013 10:33 AM To: "openstack-dev@lists.openstack.org

Re: [openstack-dev] The future of run_tests.sh

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/21/2013 01:44 PM, Joe Gordon wrote: > It sounds like the censuses in this thread is: > > In the long run, we want to kill run_tests.sh in favor of > explaining how to use the underlying tools in a TESTING file. I agree. I'd like to add that 'lo

Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically

Russell, That's great initiative! I'm wondering if a framework/abstraction layer can be built so that different algorithms can be plugged in. I'm sure we can learn from the none-vm world: http://en.wikipedia.org/wiki/Processor_affinity Thanks, Qing > > -Original Message- > From: Russ

Re: [openstack-dev] FW: [Keystone][Folsom] Token re-use

From: Adam Young [mailto:ayo...@redhat.com] Sent: Thursday, June 20, 2013 6:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] FW: [Keystone][Folsom] Token re-use On 06/20/2013 04:50 PM, Ali, Haneef wrote: 1) I'm really not sure how that will solve the original issue

[openstack-dev] [vmware] VMwareAPI sub-team status update

Greetings Stackers! It's time for the end of the week report from your friendly neighborhood VMware API team. We are making good progress, but I'll just point out that if you want to be sure something makes the Havana-2 deadline (based on length of time for code review and so on) I would seriou

Re: [openstack-dev] Quantum's new name is….

On 06/19/2013 09:14 AM, Mark McClain wrote: > The OpenStack Networking team is happy to announce that the Quantum > project will be changing its name to Neutron. You'll soon see Neutron > in lots of places as we work to implement the name change within > OpenStack. Congratulations for the cool nam

Re: [openstack-dev] XML Support for Nova v3 API

On Thu, Jun 20, 2013 at 12:44 PM, Russell Bryant wrote: > On 06/20/2013 12:00 PM, Thierry Carrez wrote: > > Christopher Yeoh wrote: > >> Just wondering what people thought about how necessary it is to keep XML > >> support for the Nova v3 API, given that if we want to drop it doing so > >> during

Re: [openstack-dev] XML Support for Nova v3 API

On Thu, Jun 20, 2013 at 2:00 PM, Vishvananda Ishaya wrote: > > On Jun 20, 2013, at 10:22 AM, Brant Knudson wrote: > > How about a mapping of JSON concepts to XML like: > > collections: > the-value ... > the-value ... > > values: > text > > > > number > > This type of mapping would remo

Re: [openstack-dev] [Networking] Allocation of IPs

There will be a deployment option where you can configure the default IP allocator. Additionally, the allocator will be configurable at subnet creation time. mark On Jun 20, 2013, at 4:51 PM, Edgar Magana wrote: > Could it be possible to add a flag to disable the allocation for the IP? > If

[openstack-dev] [quantum] Deadlock on quantum port-create

I'm moving a thread we had with some vmware guys to this list to make it public. We had a problem with quantum deadlocking when it got several requests in quick succession. Aaron suggested we set sql_dbpool_enable = True. We did and it seemed to resolve our issue. What are the downsides of turn

Re: [openstack-dev] XML Support for Nova v3 API

On Jun 21, 2013, at 12:38 PM, Doug Hellmann wrote: > > > > On Thu, Jun 20, 2013 at 2:00 PM, Vishvananda Ishaya > wrote: > > On Jun 20, 2013, at 10:22 AM, Brant Knudson wrote: > >> How about a mapping of JSON concepts to XML like: >> >> collections: >> the-value ... >> the-value .

Re: [openstack-dev] XML Support for Nova v3 API

On Fri, Jun 21, 2013 at 3:46 PM, Vishvananda Ishaya wrote: > > On Jun 21, 2013, at 12:38 PM, Doug Hellmann > wrote: > > > > > On Thu, Jun 20, 2013 at 2:00 PM, Vishvananda Ishaya > wrote: > >> >> On Jun 20, 2013, at 10:22 AM, Brant Knudson wrote: >> >> How about a mapping of JSON concepts to XML

[openstack-dev] [Heat] Celery

Hello all, Included here is a link to a Celery wiki (distributed task queue) explaining what the Celery project is and how it works. Currently, celery is being used in a distributed pattern for the WIP task flow project. As such, links to both the distributed project, and its' parent task flow

[openstack-dev] [networking][ml2] Common files (was: Device configuration)

Hi All - Some light reading and softball questions for a Friday afternoon. Here are some common files that the cisco mech driver (and I'm assuming the other mechanism drivers) will need to start off. common/exceptions.py common/constants.py We might even want to consider moving config.py into t

Re: [openstack-dev] [Networking] Allocation of IPs

Mark, Can you point me to the BP for this feature? I want to keep an eye on it. Thanks, Edgar From: Mark McClain Reply-To: OpenStack List Date: Friday, June 21, 2013 12:41 PM To: OpenStack List Subject: Re: [openstack-dev] [Networking] Allocation of IPs There will be a deployment optio

Re: [openstack-dev] [quantum] Deadlock on quantum port-create

Hi Jay, there are indeed downsides with this setting. The code currently uses connection pooling in a way that each subtransaction end up using a distinct connection from the pool. As we have nested transactions in multiple points in Neutron's code, this leads to a situation where you can exhaust

Re: [openstack-dev] Consolidate CLI Authentication

That blueprint doesn't have anything to do with the linked code review, so I'm not sure which you're asking about relative to other projects. The goal for "Consolidate CLI Authentication" is to allow python-keystoneclient to own the UX around authentication parameters, and allow other clients (e.g

Re: [openstack-dev] disabling a tenant still allow user token

On Fri, Jun 21, 2013 at 5:25 AM, Chmouel Boudjnah wrote: > Hello, > > [moving on the public mailing list since this bug is anyway public] > > On 3 Jun 2013, at 17:25, Dolph Mathews wrote: > > Apologies for the delayed response on this. We have several related open > bugs and I wanted to investiga

[openstack-dev] [Horizon] Is it the time to separate horizon and openstack_dashboard?

Hi, I think horizon will be very attractive to Django developers if we separate it from openstack_dashboard. Is it the time to do it? I found it's pretty easy to use the horizon app in a standard Django project and it just works. Current issues: * Some places still tight to OpenStack. * It pul