Re: [openstack-dev] [all] The future of the integrated release

On Fri, Aug 8, 2014 at 2:06 AM, Thierry Carrez wrote: > > Michael Still wrote: > > [...] I think an implied side effect of > > the runway system is that nova-drivers would -2 blueprint reviews > > which were not occupying a slot. > > > > (If we start doing more -2's I think we will need to explore

Re: [openstack-dev] [all] The future of the integrated release

On Tue, Aug 5, 2014 at 9:03 AM, Thierry Carrez wrote: > We seem to be unable to address some key issues in the software we > produce, and part of it is due to strategic contributors (and core > reviewers) being overwhelmed just trying to stay afloat of what's > happening. For such projects, is it

Re: [openstack-dev] [all] The future of the integrated release

On Tue, Aug 5, 2014 at 10:02 AM, Monty Taylor wrote: > On 08/05/2014 09:03 AM, Thierry Carrez wrote: >> >> Hi everyone, >> >> With the incredible growth of OpenStack, our development community is >> facing complex challenges. How we handle those might determine the >> ultimate success or failure o

Re: [openstack-dev] [oslo] usage patterns for oslo.config

On Fri, Aug 8, 2014 at 12:41 PM, Doug Hellmann wrote: > > That’s right. The preferred approach is to put the register_opt() in > *runtime* code somewhere before the option will be used. That might be in > the constructor for a class that uses an option, for example, as described > in > http://docs

Re: [openstack-dev] [qa][ceilometer] swapping the roles of mongodb and sqlalchemy for ceilometer in Tempest

On Aug 9, 2014 4:22 AM, "Eoghan Glynn" wrote: > > > Hi Folks, > > Dina Belova has recently landed some infra patches[1,2] to create > an experimental mongodb-based Tempest job. This effectively just > overrides the ceilometer storage backend config so that mongodb > is used instead of sql-alchemy.

Re: [openstack-dev] [qa][ceilometer] swapping the roles of mongodb and sqlalchemy for ceilometer in Tempest

On Mon, Aug 11, 2014 at 3:27 PM, Joe Gordon wrote: > > > > On Mon, Aug 11, 2014 at 3:07 PM, Eoghan Glynn wrote: >> >> >> >> > Ignoring the question of is it ok to say: 'to run ceilometer in any sort >> > of >> > non-trivial deployment you must manager yet another underlying service, >> > mongodb'

Re: [openstack-dev] [all] The future of the integrated release

On Tue, Aug 12, 2014 at 10:44 AM, Dolph Mathews wrote: > > On Tue, Aug 12, 2014 at 12:30 AM, Joe Gordon wrote: >> >> Slow review: by limiting the number of blueprints up we hope to focus our >> efforts on fewer concurrent things >> slow code turn around: when a blueprint is given a slot (runway)

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 5:37 AM, Mark McLoughlin wrote: > On Fri, 2014-08-08 at 15:36 -0700, Devananda van der Veen wrote: >> On Tue, Aug 5, 2014 at 10:02 AM, Monty Taylor wrote: > >> > Yes. >> > >> > Additionally, and I think we've been getting better

[openstack-dev] [Ironic] Feature proposal freeze

Hi all, As previously announced, ironic is now entering feature proposal freeze for juno. This means that all open spec reviews will be blocked, and will need to be resubmitted when kilo opens. This will be when the first juno RC is tagged, or sooner, and will be announced on this list. What ever

Re: [openstack-dev] [all] The future of the integrated release

On Aug 14, 2014 2:04 AM, "Eoghan Glynn" wrote: > > > > >> Letting the industry field-test a project and feed their experience > > >> back into the community is a slow process, but that is the best > > >> measure of a project's success. I seem to recall this being an > > >> implicit expectation a f

[openstack-dev] [Ironic] Juno-3 milestone released

Hi all! The Juno 3 milestone has been tagged, and I am very proud of everyone who worked on it, especially over the last few weeks while I was away. https://launchpad.net/ironic/+milestone/juno-3 We had targeted 14 blueprints to this milestone, and managed to land 13 of them! This includes a l

Re: [openstack-dev] [TripleO][Ironic] Unique way to get a registered machine?

On Aug 22, 2014 12:48 AM, "Steve Kowalik" wrote: > > On 22/08/14 17:35, Chris Jones wrote: >> >> Hi >> >> When register-nodes blows up, is the error we get from Ironic sufficiently unique that we can just consume it and move on? >> You should get a clear error when attempting to add a port with a

Re: [openstack-dev] [TripleO][Ironic] Unique way to get a registered machine?

Woops, meant to respond to this in the email I just sent... On Aug 21, 2014 11:35 PM, "Steve Kowalik" wrote: > > For other drivers, we think that the pm_address for each machine will be unique. Would it be possible add some advice to that effect to Ironic's driver API? > pm_address is cr

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

On Tue, Sep 9, 2014 at 4:12 PM, Samuel Merritt wrote: > On 9/9/14, 12:03 PM, Monty Taylor wrote: [snip] >> So which is it? Because it sounds like to me it's a thing that actually >> does NOT need to diverge in technology in any way, but that I've been >> told that it needs to diverge because it's

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

On Thu, Sep 4, 2014 at 1:44 PM, Kurt Griffiths wrote: [snip] > Does a Qpid/Rabbit/Kafka provisioning service make sense? Probably. Would > such a service totally overlap in terms of use-cases with Zaqar? Community > feedback suggests otherwise. Will there be some other kind of thing that > comes o

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

On Tue, Sep 9, 2014 at 5:31 PM, Boris Pavlovic wrote: > > Devananda, >> >> >> While that is de rigueur today, it's actually at the core of the >> current problem space. Blessing a project by integrating it is not a >> scalable long-term solution. We don't have a model to integrate >1 >> project fo

Re: [openstack-dev] [zaqar] Juno Performance Testing (Round 2)

On Tue, Sep 9, 2014 at 12:19 PM, Kurt Griffiths wrote: > Hi folks, > > In this second round of performance testing, I benchmarked the new Redis > driver. I used the same setup and tests as in Round 1 to make it easier to > compare the two drivers. I did not test Redis in master-slave mode, but > t

Re: [openstack-dev] [zaqar] Juno Performance Testing (Round 2)

On Wed, Sep 10, 2014 at 6:09 PM, Kurt Griffiths wrote: > On 9/10/14, 3:58 PM, "Devananda van der Veen" > wrote: > >>I'm going to assume that, for these benchmarks, you configured all the >>services optimally. > > Sorry for any confusion; I am not tr

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Sep 15, 2014 8:20 AM, "James Slagle" wrote: > > On Mon, Sep 15, 2014 at 7:44 AM, Steven Hardy wrote: > > All, > > > > Starting this thread as a follow-up to a strongly negative reaction by the > > Ironic PTL to my patches[1] adding initial Heat->Ironic integration, and > > subsequent very deta

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Mon, Sep 15, 2014 at 9:50 AM, Clint Byrum wrote: > Excerpts from Steven Hardy's message of 2014-09-15 04:44:24 -0700: >> >> > First, Ironic is hidden under Nova as far as TripleO is concerned. So > mucking with the servers underneath Nova during deployment is a difficult > proposition. Would I

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Mon, Sep 15, 2014 at 10:51 AM, Jay Faulkner wrote: > Steven, > > It's important to note that two of the blueprints you reference: > > https://blueprints.launchpad.net/ironic/+spec/drac-raid-mgmt > https://blueprints.launchpad.net/ironic/+spec/drac-hw-discovery > > are both very unlikely to land

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Mon, Sep 15, 2014 at 9:00 AM, Steven Hardy wrote: > For example, today, I've been looking at the steps required for driving > autodiscovery: > > https://etherpad.openstack.org/p/Ironic-PoCDiscovery-Juno > > Driving this process looks a lot like application orchestration: > > 1. Take some input

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Mon, Sep 15, 2014 at 1:08 PM, Steven Hardy wrote: > On Mon, Sep 15, 2014 at 05:51:43PM +, Jay Faulkner wrote: >> Steven, >> >> It's important to note that two of the blueprints you reference: >> >> https://blueprints.launchpad.net/ironic/+spec/drac-raid-mgmt >> https://blueprints.launchpad.

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Tue, Sep 16, 2014 at 11:57 AM, Zane Bitter wrote: > On 16/09/14 13:54, Devananda van der Veen wrote: >> >> On Sep 15, 2014 8:20 AM, "James Slagle" wrote: >>> >>> > >>> >On Mon, Sep 15, 2014 at 7:44 AM, Steven Hardy wrote: >>

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Tue, Sep 16, 2014 at 11:44 AM, Zane Bitter wrote: > On 16/09/14 13:56, Devananda van der Veen wrote: >> >> On Mon, Sep 15, 2014 at 9:00 AM, Steven Hardy wrote: >>> >>> For example, today, I've been looking at the steps required for dr

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

Now that I've replied to individual emails, let me try to summarize my thoughts on why Heat feels like the wrong tool for the task that I think you're trying to accomplish. This discussion has been really helpful for me in understanding why that is, and I think, at a really high level, it is becaus

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and "ready state" orchestration

On Tue, Sep 16, 2014 at 12:42 PM, Zane Bitter wrote: > On 16/09/14 15:24, Devananda van der Veen wrote: >> >> On Tue, Sep 16, 2014 at 11:44 AM, Zane Bitter wrote: >>> >>> On 16/09/14 13:56, Devananda van der Veen wrote: >>>> >>>>

Re: [openstack-dev] [Zaqar] Zaqar and SQS Properties of Distributed Queues

On Thu, Sep 18, 2014 at 7:45 AM, Flavio Percoco wrote: > On 09/18/2014 04:09 PM, Gordon Sim wrote: >> On 09/18/2014 12:31 PM, Flavio Percoco wrote: >>> Zaqar guarantees FIFO. To be more precise, it does that relying on the >>> storage backend ability to do so as well. Depending on the storage used

Re: [openstack-dev] [Zaqar] Zaqar and SQS Properties of Distributed Queues

On Thu, Sep 18, 2014 at 7:55 AM, Flavio Percoco wrote: > On 09/18/2014 04:24 PM, Clint Byrum wrote: >> Great job highlighting what our friends over at Amazon are doing. >> >> It's clear from these snippets, and a few other pieces of documentation >> for SQS I've read, that the Amazon team approach

Re: [openstack-dev] [Zaqar] Zaqar and SQS Properties of Distributed Queues

On Thu, Sep 18, 2014 at 8:54 AM, Devananda van der Veen wrote: > On Thu, Sep 18, 2014 at 7:45 AM, Flavio Percoco wrote: >> On 09/18/2014 04:09 PM, Gordon Sim wrote: >>> On 09/18/2014 12:31 PM, Flavio Percoco wrote: >>>> Zaqar guarantees FIFO. To be more precis

Re: [openstack-dev] [Nova] [Ironic] [TripleO] scheduling flow with Ironic?

On Wed, Nov 13, 2013 at 10:11 PM, Alex Glikson wrote: > Thanks, I understand the Nova scheduler part. One of the gaps there is > related to the blueprint we have are working on [1]. I was wondering > regarding the role of Ironic, and the exact interaction between the user, > Nova and Ironic. > T

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

plications with direct access to that network to a minimum, however, so a thin agent that collects and forwards the SNMP data to the central agent would be preferable, in my opinion. Regards, Devananda > > > Thanks for response. > Ladislav > > > > On 11/18/2013 06:25 PM,

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

ud monitored. We can then build on that. > > Kind regards, > Ladislav > > > On 11/20/2013 09:22 AM, Julien Danjou wrote: > >> On Tue, Nov 19 2013, Devananda van der Veen wrote: >> >> If there is a fixed set of information (eg, temp, fan speed, etc) that >>

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

On Thu, Nov 21, 2013 at 12:08 AM, Ladislav Smola wrote: > Responses inline. > > > On 11/20/2013 07:14 PM, Devananda van der Veen wrote: > > Responses inline. > > On Wed, Nov 20, 2013 at 2:19 AM, Ladislav Smola wrote: > >> Ok, I'll try to summarize wh

Re: [openstack-dev] [Ironic][Cinder] Attaching Cinder volumes to baremetal instance

No -- attach volumes is not implemented in Ironic yet. I think it would be great if someone wants to work on it. There was some discussion at the summit about cinder support, in particular getting boot-from-volume to work with Ironic, but no one has come forward since then with code or blueprints.

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

g and add the missing aspects, we can discuss these interface > and data model clearly I think. > > > -- > *Haomeng* > *Thanks:)* > > > Cheers, Devananda > > At 2013-11-21 16:08:00,"Ladislav Smola"

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

On Nov 25, 2013 7:13 PM, "Doug Hellmann" wrote: > > > > > On Mon, Nov 25, 2013 at 3:56 PM, Devananda van der Veen < devananda@gmail.com> wrote: >> >> Hi! >> >> Very good questions. I think most of them are directed towards the

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan wrote: > On Fri, Dec 6, 2013 at 1:53 PM, David Kranz wrote: > > It's great that tempest tests for ironic have been submitted! I was > > reviewing https://review.openstack.org/#/c/48109/ and noticed that the > tests > > do not actually run. They are sk

[openstack-dev] [Ironic] cleaning up our core reviewer list

Hi all, It's about time that I look at the ironic review stats to see who should be added / removed again. There are several non-core folks doing reviews during the last month [1] -- thanks! These have been very helpful. I am also looking at the folks who are contributing code [3] to get another

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

Tue, Dec 10, 2013 at 12:43 PM, David Kranz wrote: > On 12/09/2013 01:37 PM, Devananda van der Veen wrote: > > On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan wrote: > >> On Fri, Dec 6, 2013 at 1:53 PM, David Kranz wrote: >> > It's great that tempest tests for i

[openstack-dev] [Ironic] Project status update

Hi all! I realize it's been a while since I've posted an update about the project -- it's high time I do so! And there are several things to report... We tagged an Icehouse-1 milestone, though we did not publish a tarball just yet. That should happen at the Icehouse-2 milestone. http://git.open

[openstack-dev] [Ironic] Bug list maintenance

So, I've dug into the bug list in the past few days, and want to share what I've observed. Over the Havana cycle, we all used the bug list as a way to earmark work we needed to come back to. Some of those earmarks are stale. Perhaps the status is incorrect, or we fixed it but didn't close the bug,

Re: [openstack-dev] [Ironic] firmware security

On Thu, Dec 12, 2013 at 12:50 AM, Lu, Lianhao wrote: > Hi Ironic folks, > > I remembered once seeing that ironic was calling for firmware security. > Can anyone elaborate with a little bit details about what Ironic needs for > this "firmware security"? I'm wondering if there are some existing > t

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

On Tue, Dec 17, 2013 at 10:00 PM, Gao, Fengqian wrote: > Hi, all, > > I am planning to extend bp > https://blueprints.launchpad.net/nova/+spec/utilization-aware-schedulingwith > power and temperature. In other words, power and temperature can be > collected and used for nova-scheduler just as CP

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

On Wed, Dec 18, 2013 at 7:16 PM, Gao, Fengqian wrote: > Hi, Devananda, > > I agree with you that new features should be towards Ironic. > > As you asked why use Ironic instead of lm-sensors, actually I just want to > use IPMI instead of lm-sensors. I think it is reasonable to put the IPMI > part

Re: [openstack-dev] [all project] log files and logstash

Thanks for the pointer. Since Ironic is not yet enabled by default in devstack-gate, it's OK that it is also missing, but now I know where to add it. Cheers, -Deva On Mon, Dec 30, 2013 at 11:11 AM, David Kranz wrote: > In case any one other than me didn't know this, the log files that are > in

Re: [openstack-dev] [ironic] [QA] some notes on ironic functional testing

Hi Alexander, Vladimir, First of all, thanks for working on testing Ironic! Functional testing is critical to our project, and I'm very happy you're looking into it. On Tue, Jan 14, 2014 at 6:28 AM, Alexander Gordeev wrote: > We (agordeev and vkozhukalov) had a discussion about functional testin

[openstack-dev] [Ironic] Let's move to Alembic

Hi all, Some months back, there was discussion to move Ironic to use Alembic instead of SqlAlchemy. At that time, I was much more interested in getting the framework together than I was in restructuring our database migrations, and what we had was sufficient to get us off the ground. Now that the

Re: [openstack-dev] [ironic] Disk Eraser

On Fri, Jan 17, 2014 at 12:35 PM, Alan Kavanagh wrote: > Hi Rob > > Then apart from the disk eraser and reinstalling the blade from scratch > everytime it is returned from lease, and ensure network isolation, what are > the other many concerns you are worried about for sharing the bare metal > the

Re: [openstack-dev] [ironic] Disk Eraser

On Fri, Jan 17, 2014 at 3:21 PM, Chris Friesen wrote: > On 01/17/2014 04:20 PM, Devananda van der Veen wrote: > > tl;dr, We should not be recycling bare metal nodes between untrusted >> tenants at this time. There's a broader discussion about firmware >> security goin

[openstack-dev] [Ironic] Third-party drivers and testing

Hi all, I've been thinking about how we should treat third-party drivers in Ironic for a while, and had several discussions at the Hong Kong summit and last week at LCA. Cinder, Nova, Neutron, and TripleO are all having similar discussions, too. What follows is a summary of my thoughts and a propo

Re: [openstack-dev] [ironic] Disk Eraser

On Sun, Jan 19, 2014 at 9:30 PM, Robert Collins wrote: > On 20 January 2014 18:10, Alan Kavanagh > wrote: > > +1, that is another point Rob. When I started this thread my main > interest was disk and then firmware. It is clear we really need to have a > clear discussion on this, as imho I would n

Re: [openstack-dev] [Ironic] Third-party drivers and testing

On Sun, Jan 19, 2014 at 7:47 PM, Christopher Yeoh wrote: > > On Mon, Jan 20, 2014 at 6:17 AM, Devananda van der Veen < > devananda@gmail.com> wrote: > >> 1. each driver must adhere to the existing driver interfaces. >> 2. each driver must have comprehensive uni

Re: [openstack-dev] [Ironic] Third-party drivers and testing

On Mon, Jan 20, 2014 at 8:29 AM, Jay Pipes wrote: > On Sun, Jan 19, 2014 at 2:47 PM, Devananda van der Veen < > devananda@gmail.com> wrote: > >> Hi all, >> >> I've been thinking about how we should treat third-party drivers in >> Ironic for a wh

[openstack-dev] [Ironic] Node groups and multi-node operations

So, a conversation came again up today around whether or not Ironic will, in the future, support operations on groups of nodes. Some folks have expressed a desire for Ironic to expose operations on groups of nodes; others want Ironic to host the hardware-grouping data so that eg. Heat and Tuskar ca

[openstack-dev] [Ironic] Ironic 2014.1.b2 (Icehouse-2) developer milestone available

Hi all, The Icehouse-2 milestone of Ironic is now available, and a new version (0.1.1) of our python client library has just been pushed to pypi. Here is a list of what was completed during the Icehouse-2 development cycle: https://launchpad.net/ironic/+milestone/icehouse-2 Tarballs are availabl

[openstack-dev] [Ironic] File Injection (and the lack thereof)

In going through the bug list, I spotted this one and would like to discuss it: "can't disable file injection for bare metal" https://bugs.launchpad.net/ironic/+bug/1178103 There's a #TODO in Ironic's PXE driver to *add* support for file injection, but I don't think we should do that. For the var

Re: [openstack-dev] [Ironic] File Injection (and the lack thereof)

Awesome! But, Ironic will still need a way to inject the SSL cert into the instance, eg. config-drive over virtual media, or something. -D On Jan 24, 2014 2:32 PM, "Clint Byrum" wrote: > Excerpts from Joshua Harlow's message of 2014-01-24 14:17:38 -0800: > > Cloud-init 0.7.5 (not yet released)

[openstack-dev] [TripleO] [Ironic] mid-cycle meetup?

On Fri, Jan 24, 2014 at 2:03 PM, Robert Collins wrote: > This was meant to go to -dev, not -operators. Doh. > > > -- Forwarded message -- > From: Robert Collins > Date: 24 January 2014 08:47 > Subject: [TripleO] mid-cycle meetup? > To: "openstack-operat...@lists.openstack.org" >

Re: [openstack-dev] [Ironic] Node groups and multi-node operations

On Sat, Jan 25, 2014 at 7:11 AM, Clint Byrum wrote: > > Excerpts from Robert Collins's message of 2014-01-25 02:47:42 -0800: > > On 25 January 2014 19:42, Clint Byrum wrote: > > > Excerpts from Robert Collins's message of 2014-01-24 18:48:41 -0800: > > > > >> > However, in looking at how Ironic w

Re: [openstack-dev] [Ironic][Ceilometer]bp:send-data-to-ceilometer

On Wed, Jan 29, 2014 at 7:22 AM, Gordon Chung wrote: > > Meter Names: > > fanspeed, fanspeed.min, fanspeed.max, fanspeed.status > > voltage, voltage.min, voltage.max, voltage.status > > temperature, temperature.min, temperature.max, temperature.status > > > >

Re: [openstack-dev] [TripleO] [Ironic] Roadmap towards heterogenous hardware support

As far as nova-scheduler and Ironic go, I believe this is a solved problem. Steps are: - enroll hardware with proper specs (CPU, RAM, disk, etc) - create flavors based on hardware specs - scheduler filter matches requests exactly There are, I suspect, three areas where this would fall short today:

Re: [openstack-dev] [TripleO] [Ironic] Roadmap towards heterogenous hardware support

I was responding based on "Treat similar hardware configuration as equal". When there is a very minor difference in hardware (eg, 1TB vs 1.1TB disks), enrolling them with the same spec (1TB disk) is sufficient to solve all these issues and mask the need for multiple flavors, and the hardware wouldn

Re: [openstack-dev] [Ironic] PXE driver deploy issues

I think your driver should implement a wrapper around both VendorPassthru interfaces and call each appropriately, depending on the request. This keeps each VendorPassthru driver separate, and encapsulates the logic about when to call each of them in the driver layer. As an aside, this is a code pa

Re: [openstack-dev] [TripleO] [Ironic] Roadmap towards heterogenous hardware support

On Fri, Jan 31, 2014 at 1:03 PM, Tzu-Mainn Chen wrote: > So after reading the replies on this thread, it seems like I (and others > advocating > a custom scheduler) may have overthought things a bit. The reason this > route was > suggested was because of conflicting goals for Icehouse: > > a) ho

[openstack-dev] [Ironic] Functional testing, dependencies, etc

Hi all, I've got a few updates to share on the status of functional testing of Ironic. Firstly, early last week, Ironic's tempest tests were added to our check and gate pipeline, and non-voting checks were added to devstack and tempest pipelines as well. These tests start the Ironic services in d

Re: [openstack-dev] [Ironic] PXE driver deploy issues

On Fri, Jan 31, 2014 at 12:13 PM, Devananda van der Veen < devananda@gmail.com> wrote: > I think your driver should implement a wrapper around both VendorPassthru > interfaces and call each appropriately, depending on the request. This > keeps each VendorPassthru drive

[openstack-dev] [Ironic] January review redux

The last month and a half had most of our team out for holiday leave at some point, and the review stats reflect that. I had hoped our review queue would come down once we all got back from the holidays, but that hasn't happened. In fact, our review queue has grown significantly Perhaps it's a

Re: [openstack-dev] [nova][baremetal] Partition layout of image used in nova bare-metal

On Fri, Feb 7, 2014 at 2:00 AM, Taurus Cheung wrote: > Hi, > > > > I am working on deploying images to bare-metal machines using nova > bare-metal. In current design, nova bare-metal would first write a > partition layout of root partition and swap partition, then write the image > to root partit

Re: [openstack-dev] [nova][baremetal] Support configurable inject items in nova Bare-metal

On Fri, Feb 7, 2014 at 2:01 AM, Taurus Cheung wrote: > Hi, > > > > I am working on deploying images to bare-metal machines using nova > bare-metal. In current design, some files like hostname, network config > file and meta.json are injected into the image before writing to bare-metal > machines.

[openstack-dev] [Ironic] [TripleO] Goal setting // progress towards integration

Hello ironic developers, tripleo folks, and interested third-parties! The Icehouse graduation deadline is fast approaching and I think we all need to take a good look at where Ironic is, compare that to the requirements that have been laid out by the TC [1] for all Integrated projects, and priorit

[openstack-dev] [Ironic] review days

Hi again! I promise this will be a much shorter email than my last one ... :) I'd like to propose that we find regular day/time to have a recurring code jam. Here's what it looks like in my head: - we get at least three core reviewers together - as many non-core folks as show up are welcome, too

Re: [openstack-dev] [Ironic] review days

On Wed, Feb 12, 2014 at 2:18 PM, Maksym Lobur wrote: > Also, I think 3 hours might be too much > I'm happy to start with 2 hours and see how it goes. On Wed, Feb 12, 2014 at 2:35 PM, Roman Prykhodchenko < rprikhodche...@mirantis.com> wrote: > Since there are two core-subteams located in differ

[openstack-dev] [Ironic] first review jam session redux

Just a quick follow-up to our first "review jam session". We got 5 patches landed in the server 3 in the client, and zuul is merging another 5 right now. We started an etherpad part-way through https://etherpad.openstack.org/p/IronicReviewDay Let's continue to use that to track work that spins o

Re: [openstack-dev] [Ironic] first review jam session redux

On Thu, Feb 13, 2014 at 11:06 AM, Chris K wrote: > *I think this was great. We got a lot accomplished in very little time -- > let's plan to do this again **next Thursday*, *8am* *PST* > Totally +1 from me > > *Let's also have a shorter review session at the same time on > Monday morning, before

Re: [openstack-dev] [Ironic] [TripleO] Goal setting // progress towards integration

On Thu, Feb 13, 2014 at 12:16 PM, Dan Smith wrote: > > I would also like to see CI (either third party or in the gate) for > > the nova driver before merging it. There's a chicken and egg problem > > here if its in the gate, but I'd like to see it at least proposed as a > > review. > > Yeah, I th

[openstack-dev] [Ironic] py26 test failures since Thursday

Hi all, Last Thursday, a series of patches introduced sporadic failures to our python unit tests. It only showed up on the py26 tests (most of us test with py27 locally), and it only happened ~ 40% of the time, so we didn't notice it right away. The issue persisted on Friday and into the weekend a

[openstack-dev] [Ironic] Starting to postpone work to Juno

Hi all, For the last few meetings, we've been discussing how to prioritize the work that we need to get done as we approach the close of Icehouse development. There's still some distance between where we are and where we need to be -- integration with other projects (eg. Nova), CI testing of that

Re: [openstack-dev] [Ironic] review days

I wanted to take a moment first to thank all the reviewers who have been getting up early // staying late to join in these review sessions -- I believe they've been tremendously helpful in unblocking a lot of work over the last two weeks. Thanks!! I also want to remind folks that we have another o

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On Thu, Feb 27, 2014 at 5:28 AM, Sean Dague wrote: > On 02/27/2014 08:13 AM, Doug Hellmann wrote: > > > > > > > > On Thu, Feb 27, 2014 at 12:48 AM, Michael Davies > > wrote: > > > > Hi everyone, > > > > Over in "Ironic Land" we're looking at removing XML su

Re: [openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

Thu, Feb 27, 2014 at 9:34 AM, Ben Nemec wrote: > On 2014-02-27 09:23, Daniel P. Berrange wrote: > >> On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote: >> >>> This patch is coming through the gate this morning - >>> https://review.openstack.org/#/c/71996/ >>> >>> The point being to actu

[openstack-dev] asymmetric gating and stable vs unstable tests

Hi all, I'd like to point out how asymmetric gating is challenging for incubated projects, and propose that there may be a way to make it less so. For reference, incubated projects aren't allowed to have symmetric gating with integrated projects. This is why our devstack and tempest tests are "*-

Re: [openstack-dev] [Ironic] maintaining backwards compatibility within a cycle

Let's get concrete for a moment, because it makes a difference which API we're talking about. We have to guarantee a fairly high degree of backwards compatibility within the REST API. Adding new capabilities, and exposing them in a discoverable way, is fine; a backwards-incompatible breaking chang

[openstack-dev] [Ironic] New meeting room and time!

As discussed on this list previously [0] and agreed to in the last meeting [1], our weekly IRC meeting time is changing to better accommodate the many active contributors we have who are not well served by the current meeting time. The new meeting time will alternate between 1700 UTC on Mondays an

Re: [openstack-dev] [nova] [ironic] how to remove check-tempest-dsvm-ironic-pxe_ssh on Nova check

On Tue Nov 25 2014 at 7:20:00 AM Sean Dague wrote: > On 11/25/2014 10:07 AM, Jim Rollenhagen wrote: > > On Tue, Nov 25, 2014 at 08:02:56AM -0500, Sean Dague wrote: > >> When at Summit I discovered that check-tempest-dsvm-ironic-pxe_ssh is > >> now voting on Nova check queue. The reasons given is

Re: [openstack-dev] [TripleO] [Ironic] Do we want to remove Nova-bm support?

On Thu Dec 04 2014 at 11:05:53 AM Clint Byrum wrote: > Excerpts from Steve Kowalik's message of 2014-12-03 20:47:19 -0800: > > Hi all, > > > > I'm becoming increasingly concerned about all of the code paths > > in tripleo-incubator that check $USE_IRONIC -eq 0 -- that is, use > > nova-baremet

Re: [openstack-dev] [[Openstack-dev] [Ironic] Ironic-conductor fails to start - "AttributeError '_keepalive_evt'"

Hi Lohit, In the future, please do not cross-post or copy-and-paste usage questions on the development list. Since you posted this question on the general list (*) -- which is exactly where you should post it -- I will respond there. Regards, Devananda (*) http://lists.openstack.org/pipermail/op

[openstack-dev] [Ironic] reminder: alternate meeting time

This is a friendly reminder that our weekly IRC meetings have begun alternating times every week to try to accommodate more of our contributors. Next week's meeting will be at 0500 UTC Tuesday (9pm PST Monday) in the #openstack-meeting-3 channel. Details, as always, are on the wiki [0]. Regards,

[openstack-dev] [Ironic] Fuel agent proposal

I'd like to raise this topic for a wider discussion outside of the hallway track and code reviews, where it has thus far mostly remained. In previous discussions, my understanding has been that the Fuel team sought to use Ironic to manage "pets" rather than "cattle" - and doing so required extendi

Re: [openstack-dev] [Ironic] Fuel agent proposal

Thank you for explaining in detail what Fuel's use case is. I was lacking this information, and taking the FuelAgent proposal in isolation. Allow me to respond to several points inline... On Tue Dec 09 2014 at 4:08:45 AM Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Just a short explan

Re: [openstack-dev] [Ironic] Fuel agent proposal

On Tue Dec 09 2014 at 7:49:32 AM Yuriy Zveryanskyy < yzveryans...@mirantis.com> wrote: > On 12/09/2014 05:00 PM, Jim Rollenhagen wrote: > > On Tue, Dec 09, 2014 at 04:01:07PM +0400, Vladimir Kozhukalov wrote: > > >> Many many various cases are possible. If you ask why we'd like to > support > >> a

Re: [openstack-dev] [Ironic] Fuel agent proposal

On Tue Dec 09 2014 at 10:13:52 AM Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Kevin, > > Just to make sure everyone understands what Fuel Agent is about. Fuel > Agent is agnostic to image format. There are 3 possibilities for image > format > 1) DISK IMAGE contains GPT/MBR table and a

Re: [openstack-dev] [Ironic] Fuel agent proposal

On Tue Dec 09 2014 at 9:45:51 AM Fox, Kevin M wrote: > We've been interested in Ironic as a replacement for Cobbler for some of > our systems and have been kicking the tires a bit recently. > > While initially I thought this thread was probably another "Fuel not > playing well with the community"

[openstack-dev] [Ironic] 0.3.2 client release

Hi folks, Just a quick announcement that I've tagged an incremental release of our client library to catch up with the changes so far in Kilo in preparation for the k-1 milestone next week. Here are the release notes: - Add keystone v3 CLI support - Add tty password entry to CLI - Add node-set-ma

Re: [openstack-dev] [Ironic] deadline for specs

Hi, Tan, No, ironic is not having an early feature proposal freeze for this cycle. Dec 18 is the kilo-1 milestone, and that is all. Please see the release schedule here: https://wiki.openstack.org/wiki/Kilo_Release_Schedule That being said, the earlier you can propose a spec, the better your ch

[openstack-dev] [Ironic] maintaining our stable branches

Hi folks! We now have control over our own stable branch maintenance, which is good, because the stable maintenance team is not responsible for non-integrated releases of projects (eg, both of our previous releases). Also, to note, with the Big Tent changes starting to occur, such responsibilitie

[openstack-dev] [Ironic] Cancelling next week's meeting

With the winter break coming up (or already here, for some folks) I am cancelling next week's meeting on Dec 29. I had not cancelled last night's meeting ahead of time, but very few people attended, and with so few core reviewers present there wasn't much we could get done. We did not have a forma

[openstack-dev] [Ironic] mid-cycle details

Hi folks! tldr; If you will be attending the midcycle sprint in Grenoble the week of Feb 3rd, please sign up HERE . Long version... Before the holidays, I was behind in gathering and sharing info

[openstack-dev] [Ironic] thoughts on the midcycle

I'm sending the details of the midcycle in a separate email. Before you reply that you won't be able to make it, I'd like to share some thoughts / concerns. In the last few weeks, several people who I previously thought would attend told me that they can't. By my informal count, it looks like we w

[openstack-dev] [Ironic] Bug team meeting tomorrow 1700 UTC

Following up from our IRC meeting to let folks know that we'll be having a "bug day" tomorrow (Tuesday) to clean up our bug list. Folks who want to join Dmitry and I are welcome - we'll start at the same time as today's meeting (1700 UTC // 9am PST), but in our usual channel (#openstack-ironic) rat

  1   2   3   4   >