[openstack-dev] [ironic] [API] Evolving our REST API

Hi all, We discussed a little at the last summit, and discussed further at the midcycle [1], about how we might go about remedying some of the frustrations and missing functionality in our API, and I volunteered to work on it during the Newton cycle. As I looked at all of the feedback we

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On 10/12/2016 05:01 AM, Dmitry Tantsur wrote: > Hi folks! > > I'd like to propose a plan on how to simultaneously extend the coverage of our > jobs and reduce their number. > > Currently, we're running one instance per job. This was reasonable when the > coreos-based IPA image was the default,

Re: [openstack-dev] [ironic] Next API meeting cancelled

Considering I'm the only one currently working on it / bringing up new topics, I think biweekly is a better match to the pace I'm working on this. However, I hope that changes after the summit / once we start implementing these changes. --d On 09/22/2016 08:38 AM, Jim Rollenhagen wrote: > We

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

I like this approach more than the current "you're in or you're out". +1 --deva On Mon, Aug 22, 2016 at 7:02 AM Vladyslav Drok wrote: > +1 from me then :) > > On Mon, Aug 22, 2016 at 4:52 PM, Jim Rollenhagen > wrote: > >> On Mon, Aug 22, 2016 at

Re: [openstack-dev] [ironic] Driver composition defaults call

On 08/11/2016 10:37 AM, Julia Kreger wrote: > Yesterday as a group (jroll, rloo, dtantsur, matt128, devananda, > vdrok, and myself) discussed defaults for driver composition. > > The options we discussed were: > > * The existing specification[0] - Global and hardware_type >

Re: [openstack-dev] [ironic] static Portgroup support.

On 08/09/2016 01:28 AM, Vasyl Saienko wrote: > Hello Ironic'ers! > > We've recorded a demo that shows how static portgroup works at the moment: > > Flat network scenario: https://youtu.be/vBlH0ie6Lm4 > Multitenant network scenario: https://youtu.be/Kk5Cc_K1tV8 Awesome! Thank you for creating &

[openstack-dev] [Ironic] v2 API - request for feedback on "problem description"

Hi all, Today's ironic-v2-api meeting was pretty empty, so I am posting a summary of our subteam's activity here. I have taken the midcycle notes about our API's current pain points / usability gaps, and written them up into the format we would use for a spec's "Problem Description", and posted

Re: [openstack-dev] [ironic] network_interface, defaults, and explicitness

On 08/01/2016 05:10 AM, Jim Rollenhagen wrote: > Hey all, > > Our nova patch for networking[0] got stuck for a bit, because Nova needs > to know which network interface is in use for the node, in order to > properly set up the port. > > The code landed for network_interface follows the following

Re: [openstack-dev] [ironic] [nova] [neutron] get_all_bw_counters in the Ironic virt driver

On 07/28/2016 05:40 PM, Brad Morgan wrote: > I'd like to solicit some advice about potentially implementing > get_all_bw_counters() in the Ironic virt driver. > > https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L438 > Example Implementation: >

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

We spent the majority of today's weekly IRC meeting [1] discussing the finer points of this question. I agreed to post a summary of those to the list (it's below the break). tldr; * we don't know if network_interface should behave like other hardware interfaces, but... * we need to come to an

Re: [openstack-dev] [kolla][ironic] My thoughts on Kolla + BiFrost integration

At a quick glance, this sequence diagram matches what I envisioned/expected. I'd like to suggest a few additional steps be called out, however I'm not sure how to edit this so I'll write them here. As part of the installation of Ironic, and assuming this is done through Bifrost, the Actor

Re: [openstack-dev] [ironic] Proposing two new cores

On 06/16/2016 08:12 AM, Jim Rollenhagen wrote: > Hi all, > > I'd like to propose Jay Faulkner (JayF) and Sam Betts (sambetts) for the > ironic-core team. > > Jay has been in the community as long as I have, has been IPA and > ironic-specs core for quite some time. His background is operations,

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

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

On 06/07/2016 09:55 AM, Joshua Harlow wrote: > Joshua Harlow wrote: >> Clint Byrum wrote: >>> Excerpts from Joshua Harlow's message of 2016-06-07 08:46:28 -0700: Clint Byrum wrote: > Excerpts from Kris G. Lindgren's message of 2016-06-06 20:44:26 +: >> Hi ironic folks, >> As

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

On 06/06/2016 01:44 PM, Kris G. Lindgren wrote: > Hi ironic folks, > As I'm trying to explore how GoDaddy can use ironic I've created the following > in an attempt to document some of my concerns, and I'm wondering if you folks > could help myself identity ongoing work to solve these (or

Re: [openstack-dev] [ironic] [oslo] Template to follow for policy support?

On 05/31/2016 04:01 PM, Jay Faulkner wrote: > Hi all, > > > During this cycle, on behalf of OSIC, I'll be working on implementing proper > oslo.policy support for Ironic. The reasons this is needed probably don't need > to be explained here, so I won't :). > > > I have two requests for the

Re: [openstack-dev] [ironic] Tooling for recovering nodes

On 05/31/2016 01:35 AM, Dmitry Tantsur wrote: > On 05/31/2016 10:25 AM, Tan, Lin wrote: >> Hi, >> >> Recently, I am working on a spec[1] in order to recover nodes which get stuck >> in deploying state, so I really expect some feedback from you guys. >> >> Ironic nodes can be stuck in >>

Re: [openstack-dev] [ironic] usage of ironic-lib

On 05/16/2016 07:14 AM, Lucas Alvares Gomes wrote: > On Mon, May 16, 2016 at 2:57 PM, Loo, Ruby wrote: >> Hi, >> >> A patch to ironic-lib made me wonder about what is our supported usage of >> ironic-lib. Or even the intent/scope of it. This patch changes a method, >>

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

On Mon, May 9, 2016 at 11:03 AM, Mooney, Sean K wrote: > Hi > > > > If we choose to use bifrost to deploy ironic standalone I think combining > kevins previous > > suggestion of modifying the bifrost install playbook with Steve Dake’s > suggestion of creating a series >

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

On Fri, May 6, 2016 at 1:16 PM, Fox, Kevin M wrote: > I was under the impression bifrost was 2 things, one, an > installer/configurator of ironic in a stand alone mode, and two, a > management tool for getting machines deployed without needing nova using > ironic. > "Bifrost

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

On Fri, May 6, 2016 at 10:56 AM, Steven Dake (stdake) wrote: > Sean, > > Thanks for taking this on :) I didn't know you had such an AR :) > > From: "Mooney, Sean K" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < >

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Hi folks, It's a shame that etherpad was down during the ODS kolla/bifrost session. My recollection is that we agreed *not* to re-invent it Bifrost in containers, but to just stick with running it in a VM (as it is today) because that is the quickest path, and allows the Kolla community to

Re: [openstack-dev] [ironic] API docs now publishing from our tree

Works for me. The api-ref stuff is much easier to maintain, review, and the resulting docs are infinitely more usable for developers. I'm already working on getting api-ref up to date; the current docs there are sorely out of date and wrong. I'd like to land these patches quickly and iterate on

Re: [openstack-dev] Summit Core Party after Austin

On Thu, Apr 21, 2016 at 9:07 AM, Michael Krotscheck wrote: > Hey everyone- > > So, HPE is seeking sponsors to continue the core party. The reasons are > varied - internal sponsors have moved to other projects, the Big Tent has > drastically increased the # of cores, and the

Re: [openstack-dev] [ironic] upgrade support between which versions of ironic?

On Wed, Apr 20, 2016 at 5:38 AM, Mathieu Mitchell wrote: > > > On 2016-04-19 11:29 PM, Tan, Lin wrote: > >> I agree this is reasonable to support all these cases in “cold upgrades” >> but in supports-rolling-upgrade (live upgrade in another word) case it is >> different

Re: [openstack-dev] [ironic] upgrade support between which versions of ironic?

Thanks for starting the thread, Ruby. We need to first establish a grenade job to test "cold upgrades" and assert the supports-upgrade tag. I believe Ironic meets all the criteria for that tag except: - having a job that tests it (so, you know, it might be broken and I might be wrong) - having

Re: [openstack-dev] [ironic] Nominating Julia Kreger for core reviewer

Very happy and welcoming +1 from me! On Thu, Mar 24, 2016 at 1:37 PM, Villalovos, John L < john.l.villalo...@intel.com> wrote: > +1 for me. Julia has been an awesome resource and person in the Ironic > community :) > > John > > -Original Message- > From: Jim Rollenhagen

Re: [openstack-dev] [ironic] [tripleo] [stable] Phasing out old Ironic ramdisk and its gate jobs

Responding to your points out of order, since that makes more sense to me right now ... Since currently DIB claims to be backwards compatible, we just need to > leave master backwards compatible with Kilo and Liberty Ironic, which > means not deleting the bash ramdisk element. If Ironic wants to

Re: [openstack-dev] [all] A proposal to separate the design summit

On Mon, Feb 22, 2016 at 11:51 AM, Walter A. Boring IV wrote: > On 02/22/2016 09:45 AM, Thierry Carrez wrote: > >> Amrith Kumar wrote: >> >>> [...] >>> As a result of this proposal, there will still be four events each year, >>> two "OpenStack Summit" events and two

Re: [openstack-dev] [all] A proposal to separate the design summit

On Mon, Feb 22, 2016 at 7:14 AM, Thierry Carrez wrote: > Hi everyone, > > TL;DR: Let's split the events, starting after Barcelona > Thank you for the excellent write-up, Thierry (and everyone else behind it)! This sounds great to me. > Long long version: > > In a global

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Wed, Jan 20, 2016 at 9:53 AM, Flavio Percoco wrote: > Greetings, > > At the Tokyo summit, we discussed OpenStack's development themes in a > cross-project session. In this session a group of folks started discussing > what > topics the overall community could focus on as a

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

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

[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

[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

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

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

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

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

[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

[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

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

[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

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

[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

  1   2   3   4   >