[openstack-dev] [Ironic][Nova] Functional testing of Nova Ironic driver

2014-03-23 Thread Rohan Kanade
Hi, I have successfully setup latest devstack. I am aware that the Nova Ironic driver is temporarily in "ironic.nova.virt.ironic.." I am not sure how to use this driver in Nova and then create flavors or Nodes in Nova that will then call Ironic. I am a bit confused about the workflow for creat

Re: [openstack-dev] [Openstack] [TROVE] Manual Installation Again

2014-03-23 Thread Mark Kirkwood
I've outlined two methods here, both assume you are using devstack, so would need some editorializing for an actual deployment (userids, paths etc): 1/ diskimage builder + triplo This essentially copies how trove-integration does it. 2/ Do it yourself install of required software in base imag

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

2014-03-23 Thread Christopher Yeoh
On Fri, 21 Mar 2014 12:00:00 +0100 Thierry Carrez wrote: > > > > But we certainly don't want to end up in the situation of trying to > > work out how to rollback two backwards incompatible API changes. > > My vote still goes to reverting, for all the reasons Chris just > exposed. I could live w

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

2014-03-23 Thread Christopher Yeoh
On Fri, 21 Mar 2014 13:34:08 -0400 David Kranz wrote: > On 03/21/2014 05:04 AM, Christopher Yeoh wrote: > Nope. IMO we should just accept that an incompatible change was made > that should not have been, revert it, and move on. I hope that saying > our code base is going to support CD does not

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

2014-03-23 Thread Christopher Yeoh
On Fri, 21 Mar 2014 07:57:34 -0600 Chris Friesen wrote: > This is sort of off on a tangent, but one of the things that resulted > in this being a problem was the fact that if someone creates a > private flavor and then tries to add access second flavor access call > will fail because the the tenan

[openstack-dev] auto-delete in amqp "reply_*" queues in OpenStack

2014-03-23 Thread Chris Friesen
Hi, If I run "rabbitmqadmin list queues" on my controller node I see 28 queues with names of the form "reply_". From what I've been reading, these queues are supposed to be used for the replies to rpc "calls", they're not "durable', and they all have auto_delete set to "True". Given the ab

Re: [openstack-dev] [TripleO] test environment requirements

2014-03-23 Thread Robert Collins
On 24 March 2014 14:06, Clint Byrum wrote: > Excerpts from Robert Collins's message of 2014-03-13 02:51:30 -0700: >> So we already have pretty high requirements - its basically a 16G >> workstation as minimum. >> >> Specifically to test the full story: >> - a seed VM >> - an undercloud VM (bm de

Re: [openstack-dev] [openstack][SUSE][Ceilometer] ceilometer service init script can be improved

2014-03-23 Thread ZhiQiang Fan
I confirm that after upgrade to ceilometer havana 2013.2.3 on sles 11 sp3, these problems have been fixed, which means: - restart long name ceilometer services no longer kill their brothers (similar name process), and will not duplicate themself - reboot host will no longer cause ceilometer-api qu

Re: [openstack-dev] [nova][PCI] problem about PCI SRIOV

2014-03-23 Thread yongli he
? 2014?03?21? 18:31, Gouzongmei ??: Hi, I have a problem when reading the wiki below, which is based on the latest SRIOV design. https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support#API_interface My problem is about the "/PCI SRIOV with tagged flavor"/ part. In "pci_infor

Re: [openstack-dev] [TripleO] test environment requirements

2014-03-23 Thread Clint Byrum
Excerpts from Robert Collins's message of 2014-03-13 02:51:30 -0700: > So we already have pretty high requirements - its basically a 16G > workstation as minimum. > > Specifically to test the full story: > - a seed VM > - an undercloud VM (bm deploy infra) > - 1 overcloud control VM > - 2 over

Re: [openstack-dev] [TripleO] test environment requirements

2014-03-23 Thread Clint Byrum
Excerpts from Dan Prince's message of 2014-03-21 09:25:42 -0700: > > - Original Message - > > From: "Robert Collins" > > To: "OpenStack Development Mailing List" > > Sent: Thursday, March 13, 2014 5:51:30 AM > > Subject: [openstack-dev] [TripleO] test environment requirements > > > > So

Re: [openstack-dev] [TripleO] test environment requirements

2014-03-23 Thread Clint Byrum
Excerpts from Ben Nemec's message of 2014-03-21 09:38:00 -0700: > On 2014-03-21 10:57, Derek Higgins wrote: > > On 14/03/14 20:16, Ben Nemec wrote: > >> On 2014-03-13 11:12, James Slagle wrote: > >>> On Thu, Mar 13, 2014 at 2:51 AM, Robert Collins > >>> wrote: > So we already have pretty high

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-23 Thread Timur Nurlygayanov
Hi Serg, This idea sounds good, I suggest to use name 'murano.engine.murano_pl' (not just common name like 'language' or 'dsl', but name, which will be based on 'MuranoPL') Do we plan to support the ability to define different languages for Murano Engine? Thank you! On Sun, Mar 23, 2014 at 1:

Re: [openstack-dev] [Ironic] A ramdisk agent

2014-03-23 Thread Devananda van der Veen
I took a look just now at the etherpad and left some initial comments. Most importantly, I need to clearly restate that ironic is not a fully fledged CMDB. Though it may intersect with a subset of CMDB functionality, this is merely to have enough data to provision hardware on demand. Also, ironic

Re: [openstack-dev] [Ironic] Functional testing, Tempest

2014-03-23 Thread Daryl Walleck
Hi Adam, I think the steps you've completed so far are the foundation for testers like myself to be able to really dive in and start kicking the tires of Ironic. Having an easily repeatable way to generate test environments makes a huge impact in where I spend my time (environments vs actual te

[openstack-dev] Separating our Murano PL core in own package

2014-03-23 Thread Serg Melikyan
There is a idea to separate core of Murano PL implementation from engine specific code, like it was done in PoC. When this two things are separated in different packages, we will be able to track and maintain our language core as clean as possible from engine specific code. This will give to us an