Re: [openstack-dev] [Ironic] Changing our weekly meeting format

Lucas, Thanks for bringing this up (both in Paris and here). I'm strongly in favor of these changes as well. We discussed this during the meeting today [1], to which I offer the following summary: - move the status reporting to the etherpad [2] -- take one (1) minute at the start of the meeting

Re: [openstack-dev] [Ironic] A mascot for Ironic

This whole thread is made of awesome. Adding a drum kit that's built out of servers is just piling on more awesome. Cheers for the great mascot drawings, Lucas! Deva On Mon Nov 17 2014 at 8:20:09 AM Jim Rollenhagen j...@jimrollenhagen.com wrote: On Sun, Nov 16, 2014 at 01:14:13PM +, Lucas

[openstack-dev] [Ironic] Proposing new meeting times

Hi all, As discussed in Paris and at today's IRC meeting [1] we are going to be alternating the time of the weekly IRC meetings to accommodate our contributors in EMEA better. No time will be perfect for everyone, but as it stands, we rarely (if ever) see our Indian, Chinese, and Japanese

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

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 s...@dague.net 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

[openstack-dev] Program Description for OpenStack Bare Metal Provisioning

Following suit with other new programs, here is a proposed description for bare metal provisioning: Official Title: OpenStack Bare Metal Provisioning PTL: Devananda van der Veen devananda@gmail.com Mission Statement: To produce an OpenStack service and associated python libraries capable

Re: [openstack-dev] [Nova] Proposal to add Nikola Đipanov to nova-core

On Wed, Jul 31, 2013 at 12:10 PM, Russell Bryant rbry...@redhat.com wrote: Greetings, I propose that we add Nikola Đipanov to the nova-core team [1]. Nikola has been actively contributing to nova for a while now, both in code and reviews. He provides high quality reviews. so I think he

Re: [openstack-dev] [Ironic] Nomination to add Chris Krelle to ironic core

On Wed, Jul 31, 2013 at 5:29 PM, Anita Kuno ak...@lavabit.com wrote: I agree too. On 13-07-31 12:20 PM, Ghe Rivero wrote: +1 On Wed, Jul 31, 2013 at 6:10 PM, Devananda van der Veen devananda@gmail.com wrote: Hi, I'd like to propose to add Chris (NobodyCam) to ironic

Re: [openstack-dev] Is WSME really suitable? (Was: [nova] Autogenerating the Nova v3 API specification)

On Tue, Aug 6, 2013 at 2:17 PM, Mac Innes, Kiall ki...@hp.com wrote: On 06/08/13 21:56, Jonathan LaCour wrote: James Slagle james.sla...@gmail.com wrote: WSME + pecan is being used in Tuskar: https://github.com/tuskar/tuskar (OpenStack management API) We encountered the same issue

Re: [openstack-dev] [nova] Revert Baremetal v3 API extension?

+1 On Thu, Sep 5, 2013 at 3:47 AM, Alex Xu x...@linux.vnet.ibm.com wrote: +1 On 2013年09月05日 17:51, John Garbutt wrote: +1 I meant to raise that myself when I saw some changes there the other day. On 4 September 2013 15:52, Thierry Carrez thie...@openstack.org wrote: Russell Bryant

[openstack-dev] [Ironic] PTL nomination

Hi! I would like to nominate myself for the OpenStack Bare Metal Provisioning (Ironic) PTL position. I have been working with OpenStack for over 18 months, and was a scalability and performance consultant at Percona for four years prior. Since '99, I have worked as a developer, team lead,

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 cl...@fewbar.com 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

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 (*)

[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 extending

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

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 all those

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 all

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

On Tue Dec 09 2014 at 9:45:51 AM Fox, Kevin M kevin@pnnl.gov 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

[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

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

[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

[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

[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 https://www.eventbrite.com/e/openstack-ironic-kilo-midcycle-sprint-in-grenoble-tickets-15082886319 . Long version... Before the holidays, I was behind in gathering and sharing

[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

[openstack-dev] [Ironic] mid cycle etherpad

Hi folks! I've tossed up an etherpad for folks at (or not at) the mid cycle sprints to share ideas and such. This might seem last-minute (and it is). I don't have a specific agenda -- aside from what's on launchpad, what's on gerrit, and what's on your mind. Really, I'd like us to make progress

[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)

[openstack-dev] [Ironic][FFE] secure boot support in iLO drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, This feature [0] enables secure boot mode for hardware which supports UEFI. Ironic added support for UEFI in Juno. This is an incremental improvement, allowing those users to benefit more from their hardware's security features. After this

Re: [openstack-dev] [Ironic][FFE] secure boot support in iLO drivers

woops! thanks... -Devananda On Thu, Mar 19, 2015 at 10:04 AM, Ramakrishnan G rameshg87.openst...@gmail.com wrote: Corrected [1] is below (link for pxe_ilo patch review): [1] https://review.openstack.org/#/c/154808/ On Thu, Mar 19, 2015 at 10:24 PM, Devananda van der Veen devananda

[openstack-dev] [Ironic] proposing rameshg87 to ironic-core

Hi all, I'd like to propose adding Ramakrishnan (rameshg87) to ironic-core. He's been consistently providing good code reviews, and been in the top five active reviewers for the last 90 days and top 10 for the last 180 days. Two cores have recently approached me to let me know that they, too,

[openstack-dev] [Ironic] documenting our core review team policies

As the title says, I've gone ahead and written up our core review team policies, and posted it here: https://wiki.openstack.org/wiki/Ironic/CoreTeam Why now, you may ask? In the interests of full disclosure, we (the current ironic-core team) had a private discussion recently about adding a new

Re: [openstack-dev] [Ironic] Adding vendor drivers in Ironic

I know I'm arriving late to this thread, but I want to chime in with a resounding yes! to this approach. We've held to a fairly strict policy around maintaining compatibility within the driver API since early on, and we'll continue to do that as we add new interfaces (see the new

Re: [openstack-dev] [Ironic] Adding vendor drivers in Ironic

On Sun, Mar 1, 2015 at 8:45 AM, Clint Byrum cl...@fewbar.com wrote: Excerpts from Gary Kotton's message of 2015-03-01 02:32:37 -0800: Hi, I am just relaying pain-points that we encountered in neutron. As I have said below it makes the development process a lot quicker for people working on

[openstack-dev] [Ironic] Thinking about our python client UX

Hi folks, Recently, I've been thinking more of how users of our python client will interact with the service, and in particular, how they might expect different instances of Ironic to behave. We added several extensions to the API this cycle, and along with that, also landed microversion support

Re: [openstack-dev] [Ironic] proposing rameshg87 to ironic-core

a week?), I'd like to officially welcome him to the core team. -Devananda On Tue, Mar 10, 2015 at 10:03 AM David Shrewsbury shrewsbury.d...@gmail.com wrote: +1 On Mar 9, 2015, at 6:03 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all, I'd like to propose adding

Re: [openstack-dev] Avoiding regression in project governance

On Tue, Mar 10, 2015 at 12:12 PM Lauren Sell lau...@openstack.org wrote: Dissolving the integrated release without having a solid plan and replacement is difficult to communicate to people who depend on OpenStack. We’re struggling on that front. That said, I’m still optimistic about project

Re: [openstack-dev] Avoiding regression in project governance

On Tue, Mar 10, 2015 at 12:00 PM Jeremy Stanley fu...@yuggoth.org wrote: On 2015-03-10 14:42:18 -0400 (-0400), Russell Bryant wrote: [...] As to specific tags, I refer back to this: http://governance.openstack.org/reference/incubation- integration-requirements.html We worked pretty

Re: [openstack-dev] [Ironic] Stepping down from Ironic Core

Robert, Thank you for all your input and insight over the last two years. Our architectural discussions have been invaluable to me and helped shape Ironic into what it is today. All the best, Devananda On Tue Feb 24 2015 at 4:26:54 PM Robert Collins robe...@robertcollins.net wrote: Like with

Re: [openstack-dev] https://review.openstack.org/#/c/141012/ Pass the capabilities to ironic node instance_info

Nisha, If it was an unrelated bug, you would need to recheck the patch. [0] However, it looks this failure is a direct result of your patch. See the nova-compute log here:

Re: [openstack-dev] [Ironic] ironic-specs open for Liberty!

Jay, Thanks for staying on top of updating opening Liberty specs, and for all your help with specs during Kilo! -Deva On Fri, Apr 10, 2015 at 10:40 AM Jay Faulkner j...@jvf.cc wrote: Hi, Just a note to let you know Liberty specs are open for Ironic. Template Changes There are

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

FWIW, we enumerated the use-cases and expected behavior for all combinations of server [pre versions, older version, newer version] and client [pre versions, older version, newer version, user-specified version], in this informational spec:

Re: [openstack-dev] [Ironic] how about those alternating meeting times?

in IRC during the meetings by day: Monday: 3793 Tuesday: 2475 Unique attendees per day: Monday: total: 54 - cores: 9 Tuesday: total: 32 - cores: 5 On Mon, May 11, 2015 at 10:21 AM Devananda van der Veen devananda@gmail.com wrote: At the Paris summit, we discussed and eventually

[openstack-dev] [Ironic] how about those alternating meeting times?

At the Paris summit, we discussed and eventually agreed to try out alternating meeting times. So, for the last ~6mo, each week our IRC meeting has alternated between Monday evening and Tuesday morning UTC (10am PT and 10pm PT Mondays). I'd like us to review how well this has - or has not -

Re: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?

In ironic, we have use asciiflow several times quite successfully in the spec process. We also maintain in-tree docs with .PNG graphics, and versioning those has been a bit of a pain. They were originally taken out of slide decks, and served their purpose, but really ought to be in a different

Re: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?

Woops. I missed most of this thread in my last reply. I'm all for using open standard formats and versioning them. However. Not being a graphical artist myself, I have found the learning curve on some of those tools daunting, eg. inkscape, which means I'm far less likely to update a graphic in a

Re: [openstack-dev] [tripleo] [ironic] Where to keep discover images

, nice idea for an improvement! Dmitry 2015-04-14 22:27 GMT+02:00 Devananda van der Veen devananda@gmail.com: I'm wondering Rather than have a static config, could the DiscoverdInspect interface handle setting up the TFTP config, pulling those images from Glance, etc, when a node

Re: [openstack-dev] [tripleo] [ironic] Where to keep discover images

I'm wondering Rather than have a static config, could the DiscoverdInspect interface handle setting up the TFTP config, pulling those images from Glance, etc, when a node is moved into the inspect state (assuming such integration was desired by the cloud operator)? -Deva On Fri, Apr 10, 2015

Re: [openstack-dev] [Ironic] [RFC/FFE] Finishing state machine work for Kilo

Hi! The situation you describe is the same that concerned me with regards to stable/juno compatibility. As soon as the client library started passing a version header by default, it exposed Kilo changes to all users. Anyone testing from trunk would have experienced that when 99ab landed. I

Re: [openstack-dev] [all] Kilo stable branches for other libraries

Thierry, You left out python-ironicclient, which isn't a surprise as it isn't actually listed in Nova's requirements.txt file. I don't have a link handy to cite the previous discussions, but Nova felt that it was not appropriate to list a driver's dependency in their project's requirements file.

Re: [openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

On Wed, Apr 8, 2015 at 7:38 AM Chris Friesen chris.frie...@windriver.com wrote: On 04/07/2015 11:35 PM, Michael Davies wrote: I agree with Jim R's suggestion - it's really up to the consumer as to what they want to do. Having said that... I think that any consumer wants to use the

Re: [openstack-dev] [Ironic] When to bump the microversion?

On Jun 4, 2015 11:11 AM, Chris Friesen chris.frie...@windriver.com wrote: On 06/04/2015 10:14 AM, Devananda van der Veen wrote: On Jun 4, 2015 8:57 AM, Monty Taylor mord...@inaugust.com So, seriously - let's grow up and start telling people that they do not get to pick and choose user

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On Jun 5, 2015 4:36 AM, Sean Dague s...@dague.net wrote: On 06/05/2015 01:28 AM, Adrian Otto wrote: On Jun 4, 2015, at 11:03 AM, Devananda van der Veen devananda@gmail.com mailto:devananda@gmail.com wrote: On Jun 4, 2015 12:00 AM, Xu, Hejie hejie...@intel.com mailto:hejie

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On Jun 4, 2015 12:00 AM, Xu, Hejie hejie...@intel.com wrote: Hi, guys, I’m working on adding Microversion into the API-WG’s guideline which make sure we have consistent Microversion behavior in the API for user. The Nova and Ironic already have Microversion implementation, and as I know

Re: [openstack-dev] [Ironic] When to bump the microversion?

On Jun 4, 2015 8:57 AM, Monty Taylor mord...@inaugust.com wrote: On 06/04/2015 11:27 AM, Dmitry Tantsur wrote: On 06/04/2015 05:03 PM, Sean Dague wrote: On 06/04/2015 10:50 AM, Dmitry Tantsur wrote: On 06/04/2015 04:40 PM, Ruby Loo wrote: Hi, In Kilo, we introduced microversions but

Re: [openstack-dev] [Ironic] ENROLL state and changing node driver

On Jun 4, 2015 5:53 AM, Dmitry Tantsur dtant...@redhat.com wrote: Hi! While working on the enroll spec [1], I got a thinking: within the new state machine, when should we allow to change a node driver? My initial idea was to only allow driver change in ENROLL. Which sounds good to me, but

Re: [openstack-dev] [Ironic] Proposal to add a new repository

I'm On Mon, Jun 22, 2015 at 8:19 AM John Trowbridge tr...@redhat.com wrote: On 06/22/2015 10:40 AM, Dmitry Tantsur wrote: On 06/22/2015 04:19 PM, Devananda van der Veen wrote: Hi John, Thanks for the excellent summary! I found it very helpful to get caught up. I'd like to make sure I

Re: [openstack-dev] [Ironic] Proposal to add a new repository

Oh - one more thing. If ahc-tools depends on data gathered by enovance/hardware, then I'm not sure it makes sense to import one to openstack/ without the other. -Deva On Mon, Jun 22, 2015 at 5:08 PM Devananda van der Veen devananda@gmail.com wrote: I'm On Mon, Jun 22, 2015 at 8:19 AM

Re: [openstack-dev] [Ironic][Horizon][Tuskar-ui] Making a dashboard for Ironic

Hi Jim, Your characterization of this is incomplete. These are not two equal projects proposing the same thing in different ways, and while I very much want to encourage collaboration, I value our community and feel that this was not done in the spirit of that community. To be clear:

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

Almost all of our discussions so far on this topic have left something out, which Monty pointed out to me last week. I'm following up now because E_TRAVEL... tldr; What we're versioning here are API's, not packages. It's not a question of numbering and dependency ordering, but of communicating

Re: [openstack-dev] [Ironic] Mid-Cycle Sprint

Event signup page is now live -- please RSVP! *https://www.eventbrite.com/e/openstack-ironic-sprint-august-2015-tickets-17533862254 https://www.eventbrite.com/e/openstack-ironic-sprint-august-2015-tickets-17533862254* -Devananda On Thu, Jun 25, 2015 at 8:46 AM Stafford, John Richard

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

Sean's point and Dmitri's are similar. There are APIs for projects which do not have official team or program names. And some teams may produce more than one forward-facing service. Naming the API based in the team name doesn't make sense. My previous point is that restricting the API name to

Re: [openstack-dev] [Ironic] Proposal to add a new repository

Hi John, Thanks for the excellent summary! I found it very helpful to get caught up. I'd like to make sure I understand the direction ahc is going. A couple questions... I see that ahc is storing its information in swift. That's clever, but if Ironic provided a blob store for each node, would

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

On Wed, Jun 17, 2015 at 7:31 AM Jay Pipes jaypi...@gmail.com wrote: On 06/17/2015 06:30 AM, Lucas Alvares Gomes wrote: overlap there rather than competition), how crazy does it sound if we say that for OpenStack Nova is the compute API and Ironic the Bare Metal API and so on? Would that

Re: [openstack-dev] [nova] How to microversion API code which is not in API layer

Yes. A new query parameter is a change in the contract, regardless of where the code change lies. -Deva On Jun 12, 2015 6:20 PM, Chen CH Ji jiche...@cn.ibm.com wrote: Hi We have [1] in the db layer and it's directly used by API layer , the filters is directly from client's input

[openstack-dev] [Ironic] Updates from the Summit

Hello! It's that time - hopefully everyone has recovered from the summit by now and is getting back in the swing of things. I'd like to take a little of everyone's time to summarize the main points we covered while in Vancouver (and record them here for folks who didn't make it, were in other

Re: [openstack-dev] [Nova] Using depends-on for patches which require an approved spec

I think this will help because it separates the judgement of is this code good enough to land from the project and release coordination of should this code land now. I've been floating the idea of separating +2 and +A powers for the same purpose: free up many of the technical reviewers from

[openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

Hi all, tl;dr; At the summit, the Ironic team discussed the challenges we've had with the current release model and came up with some ideas to address them. I had a brief follow-up conversation with Doug and Thierry, but I'd like this to be discussed more openly and for us (the Ironic dev

[openstack-dev] [Ironic] no IRC meeting tonight

Some folks are still traveling (or recovering) from the summit, and today is a holiday in the US, so I'm cancelling tonight's meeting. There are many action items recorded in the etherpads - we'll have a lot to talk about next week! -Devananda

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Thanks for all your contributions, Ghe! You've done a lot to help keep this project synced with the common libs -- of course, you're welcome back any time. Best Deva On Mon, May 25, 2015, 09:49 Ghe Rivero g...@debian.org wrote: My focus on the Ironic project has been decreasing in the last

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow harlo...@outlook.com wrote: Clint Byrum wrote: Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700: On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileorgegui...@redhat.com

Re: [openstack-dev] [Ironic] Let's talk about API versions

, 2015 at 02:37:52PM -0700, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-07-31 04:14:54 -0700: On 07/30/2015 04:58 PM, Devananda van der Veen wrote: snip Thoughts? * I'm assuming it is possible to make micro version changes to the 1.x API

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

Hi folks, Just a quick reminder - we're switching back to a consistent meeting time, at 18:00 UTC Mondays. That means the next meeting is in two hours. I should have sent this on Friday, but exhaustion and juggling the midcycle, and well, I forgot :-/ Thanks, Deva

Re: [openstack-dev] [ironic] baremetal server boot failing at iSCSI/tgtd

Hi Vikas, It looks like the iscsi deploy process wasn't able to attach to the node. This could be a network issue. Also, what kernel and ramdisk are you using for the deploy step? Did you download one, or build it with disk-image-builder? cirros is only suitable for the instance image, not the

Re: [openstack-dev] [Ironic] Lenovo driver submission requests

Yes, yes, and yes to what has been said already. (Thanks Dmitry, Lucas, and Jim) -Devananda On Jul 30, 2015 7:05 AM, Jim Rollenhagen j...@jimrollenhagen.com wrote: On Thu, Jul 30, 2015 at 09:27:42AM +0200, Dmitry Tantsur wrote: On 07/30/2015 08:59 AM, Kai KH Huang wrote: Dear Devananda

Re: [openstack-dev] [Ironic] Let's talk about API versions

On Thu, Jul 30, 2015 at 10:21 AM Clint Byrum cl...@fewbar.com wrote: Excerpts from Jim Rollenhagen's message of 2015-07-27 13:35:25 -0700: Hi friends. Ironic implemented API micro versions in Kilo. We originally did this to allow for breaking changes in the API while allowing users to

Re: [openstack-dev] [Ironic] Let's talk about API versions

I'm going to reply to several emails in this thread - but separately, because they're from separate people and with separate POV, and I think it will be even harder to discern what I'm saying if I merge the contexts before replying... so bear with me ... On Mon, Jul 27, 2015 at 1:36 PM Jim

Re: [openstack-dev] [Ironic] Let's talk about API versions

On Tue, Jul 28, 2015 at 1:57 PM Jim Rollenhagen j...@jimrollenhagen.com wrote: On Tue, Jul 28, 2015 at 08:23:34PM +, Devananda van der Veen wrote: On Mon, Jul 27, 2015 at 4:58 PM Sean Dague s...@dague.net wrote: On 07/27/2015 07:10 PM, Jim Rollenhagen wrote: On Mon, Jul 27, 2015

Re: [openstack-dev] [Ironic] Let's talk about API versions

On Mon, Jul 27, 2015 at 4:58 PM Sean Dague s...@dague.net wrote: On 07/27/2015 07:10 PM, Jim Rollenhagen wrote: On Mon, Jul 27, 2015 at 03:28:49PM -0700, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-07-27 13:41:20 -0700: So the CLI should actually break less often, and

Re: [openstack-dev] [Ironic] Let's talk about API versions

On Mon, Jul 27, 2015 at 1:41 PM Sean Dague s...@dague.net wrote: Consider the CLI an auto negotiating microversion application of the python API client. And, realistically, should solve some of the issues of people running nova foo and getting cryptic errors from the server when they are

Re: [openstack-dev] [Ironic] Let's talk about API versions

On Tue, Jul 28, 2015 at 1:01 AM Dmitry Tantsur dtant...@redhat.com wrote: On 07/27/2015 10:41 PM, Sean Dague wrote: On 07/27/2015 04:35 PM, Jim Rollenhagen wrote: Hi friends. Ironic implemented API micro versions in Kilo. We originally did this to allow for breaking changes in the API

Re: [openstack-dev] [Ironic] how about those alternating meeting times?

This is a much-overdue follow up to this poll, which got 17 responses. TL;DR: The poll indicated that most responders did not personally find the 0500 meeting helpful. Reviewing the meeting logs for the last six months shows significantly lower core attendance in those meetings. Informal

[openstack-dev] [Ironic] Reminder - midcycle Sprint in Seattle Aug 12 - 14

Hi all! Just dropping a reminder out here -- our midcycle is one month away! We're starting to jot down informal notes and plans on an etherpad here: https://etherpad.openstack.org/p/ironic-liberty-midcycle Please continue to use that to coordinate all the things. If you plan to attend, please

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

On Sat, Jul 18, 2015 at 5:42 AM Sam Stoelinga sammiest...@gmail.com wrote: +1 on Kevin Benton's comments. Ironic should have integration with switches where the switches are SDN compatible. The individual bare metal node should not care which vlan, vxlan or other translation is programmed at

Re: [openstack-dev] [Ironic] ENROLL node state is introduced - next steps [ACTION RECOMMENDED]

So, as you know, I think that a breaking change like this is really bad for our users, no matter how loudly we declare it or when we do it. Version negotiation in the REST API doesn't give us license to do this. I also think most users should not need to know the version number at all, should be

[openstack-dev] [Ironic] No meeting tonight?

Hi all, My apologies, but I won't be able to attend the IRC meeting tonight. The agenda is very light (basically non-existent) so I suggest that we just cancel it and meet next Monday. Also, I haven't seen any response to my email (*) from one week ago about the lack of attendance to this (late

Re: [openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

se to call it . > Please see inline for my thoughts. > > On Tue, Oct 6, 2015 at 5:54 AM, Devananda van der Veen < > devananda@gmail.com> wrote: > >> tldr; the boot / deploy interface split we did broke an out of tree >> driver. I've proposed a patch. We s

Re: [openstack-dev] [ironic] Nominating two new core reviewers

++ on both counts! On Thu, Oct 8, 2015 at 2:47 PM, Jim Rollenhagen wrote: > Hi all, > > I've been thinking a lot about Ironic's core reviewer team and how we might > make it better. > > I'd like to grow the team more through trust and mentoring. We should be > able to

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

Thanks for the list, Sam. I've left some comments inline... On Tue, Nov 10, 2015 at 4:19 AM, Sam Betts (sambetts) wrote: > So you would end up with a set of commands that look like this: > > Openstack baremetal [node/driver/chassis] list > will this command support

Re: [openstack-dev] [Ironic] Suggestion to split install guide

I agree that it's far too long right now and should be split up. I would suggest splitting the section on standalone usage into its own guide, since many of the advanced topics can apply to using Ironic with and without other services. So perhaps more like this: - Basic Install Guide with

Re: [openstack-dev] [devstack][keystone][ironic] Use only Keystone v3 API in DevStack

We (the Ironic team) have talked a couple times about keystone /v3 support and about improving the granularity of policy support within Ironic. No one stepped up to work on these specifically, and they weren't prioritized during Liberty ... but I think everyone agreed that we should get on with

Re: [openstack-dev] [devstack][keystone][ironic] Use only Keystone v3 API in DevStack

m/openstack/ironic/blob/5671e7c2df455f97ef996c47c9c4f461a82e1c38/etc/ironic/policy.json > > >> >> >> Guang >> >> >> -Original Message- >> From: Devananda van der Veen [mailto:devananda@gmail.com] >> Sent: Friday, September 11, 2015

[openstack-dev] [ironic] PTL candidacy

Hi all, ( repost from https :// review.openstack.org /223753 ) It's that time again, where encumbent PTLs are supposed to write about what features

[openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

tldr; the boot / deploy interface split we did broke an out of tree driver. I've proposed a patch. We should get a fix into stable/liberty too. Longer version... I was rebasing my AMTTool driver [0] on top of master because the in-tree one still does not work for me, only to discover that my

Re: [openstack-dev] [nova] [ironic] Hardware composition

On Tue, Dec 1, 2015 at 12:07 PM, Andrew Laski wrote: > On 12/01/15 at 03:44pm, Vladyslav Drok wrote: > >> Hi list! >> >> There is an idea of making use of hardware composition (e.g. >> >>

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On Tue, Dec 1, 2015 at 3:22 AM, Steven Hardy <sha...@redhat.com> wrote: > On Mon, Nov 30, 2015 at 03:35:13PM -0800, Devananda van der Veen wrote: > >On Mon, Nov 30, 2015 at 3:07 PM, Zane Bitter <zbit...@redhat.com> > wrote: > > > > On 30/11/15 12:51,

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On Fri, Dec 4, 2015 at 7:30 AM, Thierry Carrez wrote: > Julien Danjou wrote: > > On Fri, Dec 04 2015, Dmitry Tantsur wrote: > > > >> Specifically, I'm talking about ironic-inspector, which is a auxiliary > service > >> under the bare metal program. My first assumption is

[openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

All, I'm going to attempt to summarize a discussion that's been going on for over a year now, and still remains unresolved. TLDR; The main touch-point between Nova and Ironic continues to be a pain point, and despite many discussions between the teams over the last year resulting in a

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On Mon, Nov 30, 2015 at 3:07 PM, Zane Bitter wrote: > On 30/11/15 12:51, Ruby Loo wrote: > >> >> >> On 30 November 2015 at 10:19, Derek Higgins > > wrote: >> >> Hi All, >> >> A few months tripleo switch from its

Re: [openstack-dev] [ironic][security] what is OK to put in DEBUG logs?

On Wed, Nov 18, 2015 at 9:48 AM, Ruby Loo wrote: > Hi, > > I think we all agree that it isn't OK to log credentials (like passwords) > in DEBUG logs. However, what about other information that might be > sensitive? A patch was recently submitted to log (in debug) the SWIFT >

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

On 06/10/2016 05:48 AM, Sean Dague wrote: > On 06/10/2016 08:41 AM, Jeremy Stanley wrote: >> On 2016-06-10 11:49:12 +0100 (+0100), Miles Gould wrote: >>> On 09/06/16 23:21, Jay Faulkner wrote: There was some discussion about whether or not the Ironic grenade job should be in the check

<    1   2   3   4   >