Re: [openstack-dev] [Ironic] January review redux

From: Devananda van der Veen mailto:[email protected]>> So, I'd like to nominate the following two additions to the ironic-core team: Max Lobur https://review.openstack.org/#/q/reviewer:mlobur%2540mirantis.com+project:openstack/ironic,n,z Roman Prykhodchenko https://review.openstack.org/#

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

Hi, we had an interesting discussion on IRC about whether or not we should be maintaining backwards compatibility within a release cycle. In this particular case, we introduced a new decorator in this kilo cycle, and were discussing the renaming of it, and whether it needed to be backwards compatib

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

On 29 December 2014 at 17:45, Devananda van der Veen < [email protected]> wrote: > ... > That being said, I'd also like to put forth this idea: if we had a second > gathering (with the same focus on writing code) the following week (let's > say, Feb 11 - 13) in the SF Bay area -- who would a

Re: [openstack-dev] [Ironic] should we have an IRC meeting next week ?

Hi all, Just a reminder that May 5th is our next scheduled meeting day, but I probably won't make it, because I'll be just getting back from one trip and start two consecutive weeks of conference travel early the next morning. Chris Krelle (nobodycam) has offered to chair that meeting in my ab

Re: [openstack-dev] [Ironic] Nominating Dmitry Tantsur to ironic-core

+1 for Dmitry! --ruby From: Devananda van der Veen mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Monday, May 26, 2014 at 12:39 PM To: OpenStack Development Mailing List mailto:openstack

Re: [openstack-dev] [Ironic] Nominating Jim Rollenhagen to ironic-core

+1! jroll is on a roll ;) From: Devananda van der Veen mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Friday, July 11, 2014 at 6:50 PM To: OpenStack Development Mailing List mailto:opens

Re: [openstack-dev] [Ironic] Nominating David Shrewsbury to ironic-core

+1! shrews is as shrewd as can be ;) From: Devananda van der Veen mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Friday, July 11, 2014 at 6:50 PM To: OpenStack Development Mailing List m

Re: [openstack-dev] Nova list with all-tenants flag

It helps to understand the original intent. But from an API point of view (or new user point of view) it is confusing. I don't know if this is consistent with other commands. Is this the only nova command where you have to indicate via an option, whether you want to operate as admin or not? (And i

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

> > 2) Driver docs may not be backported to stable branches. This is a > stable maintenance policy, not an Ironic policy. This problem is > somewhat unique to Ironic as most major projects have deployer docs in > the Ops guide repo, rather than in the code repo. I'm going to chat with > some docs/s

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Oct 19) - Open: 171 (+11). 12 new (+9), 63 in progress (+22), 0 critical, 14 high (+3) and 10 incomplete (-1) - Nova bugs with Iro

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On 10 November 2015 at 12:08, Dmitry Tantsur wrote: > On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: > >> Hi, >> >> In the last Ironic meeting [1] we started a discussion about whether >> we need to have a mid-cycle meeting for the Mitaka cycle or not. Some >> ideas about the format of the mi

Re: [openstack-dev] [neutron][ironic] Ironic-Neutron meeting cancellation notice

On 15 November 2015 at 16:47, Sukhdev Kapur wrote: > Folks, > > We are canceling this week's Ironic-neutron integration meeting. I have a > family obligation to take care of and I have not been able to find a > replacement person who can chair this meeting. Therefore, we will cancel > this week's

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

On 10 November 2015 at 11:31, Dmitry Tantsur wrote: > On 11/10/2015 05:21 PM, Brad P. Crochet wrote: > >> On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur >> wrote: >> >>> Hi all! >>> >>> I'd like to seek consensus (or at least some opinions) on patch >>> https://review.openstack.org/#/c/206119/

[openstack-dev] [ironic] weekly subteam status report

Hi, We are stoked to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Nov 9) - Open: 167 (-4). 10 new (-2), 61 in progress (-2), 0 critical, 14 high and 11 incomplete (+1) - Nova b

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

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 temporary URL [1]. I agree that it would be useful for debugging, but since that te

Re: [openstack-dev] [ironic] weekly subteam status report

On 17 November 2015 at 01:34, Naohiro Tamura wrote: > Ruby, > > Thanks for taking care of our weekly status report. > I'd like to just let you know that the iRMC part is somehow consolidated > with old statuses which I reported two and three weeks ago. > If this report were generated by a script,

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

On 19 November 2015 at 09:25, Brad P. Crochet wrote: > I have pushed up a draft of the spec. Let's move comments there. > > I tried to incorporate as much as I could from the discussion here. > There was a lot of disjointed suggestions and was a bit difficult to > follow. So I've taken what I can

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

> > Another idea I floated last week was to do a virtual midcycle of sorts. > > Treat it like a normal midcycle in that everyone tells their management > > "I'm out for 3-4 days for the midcycle", but they don't travel anywhere. > > We come up with an agenda, see if there's any planning/syncing wor

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

On 20 November 2015 at 18:32, Ben Nemec wrote: > On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote: > > Hi, > > > >> Also keep in mind that DEBUG logging, while still should have some > masking > >> of data, since it is explicitly called out (or should be) as not safe > for > >> production, can c

Re: [openstack-dev] [ironic] specs process for ironic-inspector

On 19 November 2015 at 08:39, Pavlo Shchelokovskyy < [email protected]> wrote: > Hi all, > > +1 for specs in general, big features require a proper review and > discussion for which LP is not a good choice. > > +1 for not requiring a spec for small features, LP BP is enough for just > t

[openstack-dev] [ironic] weekly subteam status report

Hi, We are stoked to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === (diff with Nov 16) - Open: 171 (+4). 11 new (+1), 60 in progress (-1), 0 critical, 16 high (+2) and 11 incomplete

Re: [openstack-dev] [ironic] Releases and things

On 25 November 2015 at 18:02, Jim Rollenhagen wrote: > Hi all, > > We're approaching OpenStack's M-1 milestone, and as we have lots of good > stuff in the master branch, and no Mitaka release yet, I'd like to make > a release next Thursday, December 3. > > First, I've caught us up (best I can tel

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

On 30 November 2015 at 10:19, Derek Higgins wrote: > Hi All, > > A few months tripleo switch from its devtest based CI to one that was > based on instack. Before doing this we anticipated disruption in the ci > jobs and removed them from non tripleo projects. > > We'd like to investigate

[openstack-dev] [ironic] weekly subteam status report

Hi, We are elated to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === (diff with Nov 23) - Open: 174 (+3). 11 new, 60 in progress, 0 critical, 16 high and 11 incomplete - Nova bugs w

Re: [openstack-dev] [ironic] Announcing Third Party CI for Proliant iLO Drivers

On 30 November 2015 at 11:25, Gururaj Grandhi wrote: > Hi, > > > > This is to announce that we have setup a Third Party CI > environment for Proliant iLO Drivers. The results will be posted under > "HP Proliant CI check" section in Non-voting mode. We will be running > the basic dep

[openstack-dev] [ironic] weekly subteam status report

Hi, We are pleased to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === (diff with Nov 30) - Open: 175 (+1). 12 new (+1), 61 in progress (+1), 1 critical (+1), 16 high and 9 incomplete

Re: [openstack-dev] [ironic]Ironic operations on nodes in maintenance mode

On 23 November 2015 at 18:35, Shraddha Pandhe wrote: > Hi, > > I would like to know how everyone is using maintenance mode and what is > expected from admins about nodes in maintenance. The reason I am bringing > up this topic is because, most of the ironic operations, including manual > cleaning

[openstack-dev] [ironic] weekly subteam status report

Hi, We are lucky to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 14.03.2016): - Ironic: 179 bugs (+12) + 164 wishlist items (-10). 25 new (+6), 124 in progress (+3),

[openstack-dev] [ironic] weekly subteam status report

Hi, We are merry to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 28.03.2016): - Ironic: 196 bugs (+17) + 163 wishlist items (-1). 28 new (+3), 135 in progress (+11),

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Yes, I think it would be good to have a summit session on that. However, before the session, it would really be helpful if the folks with proposals got together and/or reviewed each other's proposals, and summarized their findings. You may find after reviewing the proposals, that eg only 2 are real

[openstack-dev] [ironic] weekly subteam status report

Hi, We are nerdy to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 04.04.2016): - Ironic: 200 bugs (+4) + 163 wishlist items. 25 new, 136 in progress (+1), 0 critical,

[openstack-dev] [ironic] weekly subteam status report

Hi, We are overjoyed to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 11.04.2016): - Ironic: 203 bugs (+3) + 166 wishlist items (+3). 30 new (+5), 134 in progress (-2

Re: [openstack-dev] [ironic] weekly subteam status report

On Mon, Apr 18, 2016 at 3:10 PM, Ruby Loo wrote: > ... > Network isolation (Neutron/Ironic work) (jroll) > === > - Still needs review > - cross-project session tuesday on the future of bare metal networking: > https://wiki.openstack

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

Hi, Currently, ironic doesn't support ("live", "online", "rolling", or minimal-downtime) upgrades between named versions of ironic. (Where "named version" is the final release or stable release that is associated with a development cycle). So for example, Liberty -> Mitaka release. We've been wor

[openstack-dev] [ironic] Newton priorities and primary contacts

Hi, At the Austin summit, we had a session where we discussed and decided on what the top priorities would be for ironic, in the newton development cycle. The etherpad [1] captures that discussion, and there is a patch up to add the newton priorities to our specs [2]. Everyone, and in particular

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

Sweet. Thanks Jim (and everyone else that made this happen). I do want to make sure there is one "source of truth" to the API documentation. We are already generating REST API documentation at http://docs.openstack.org/developer/ironic/webapi/v1.html. The info for this comes from docstrings etc in

[openstack-dev] [ironic] weekly subteam status report

Hi, We are overjoyed to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === (diff with Dec 7) - Open: 179 (+4). 16 new (+4), 58 in progress (-3), 0 critical (-1), 13 high (-3) and 9 incomplet

[openstack-dev] [ironic] weekly subteam status report

Hi, We are eager to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - (no diff) - Ironic: 143 bugs + 149 wishlist items. 18 new, 89 in progress, 0 critical, 14 high and 9 incomplete - Ins

[openstack-dev] [ironic] weekly subteam status report

Hi, We are amazed to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 21.12.2015): - Ironic: 151 bugs (+8) + 149 wishlist items. 23 new (+5), 92 in progress (+1), 0 crit

[openstack-dev] [ironic] weekly subteam report

Hi, We are buzzed to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 04.01.2016): - Ironic: 147 bugs (-4) + 158 wishlist items (+9). 14 new (-9), 99 in progress (+

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

On 11 January 2016 at 10:27, Doug Hellmann wrote: > ... > > > There are a few libraries on the list, too (automaton, ironic-lib), and > that's confusing. It would be interesting to know how they're using > table output. > > Doug > > As far as ironic-lib goes, I took a look. It isn't using PrettyT

[openstack-dev] [ironic] weekly status report

Hi, We are cool to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 11.01.2016): - Ironic: 148 bugs (+1) + 162 wishlist items (+4). 15 new (+1), 102 in progress (+3

[openstack-dev] [ironic] gate is broken

Hi, Since Saturday-ish, the gate has been and is still broken, so all patches for ironic and ironic-python-agent (any agent_ssh driver tests) will continue to fail until it is fixed. The fix [1] was approved on Monday, but it has yet to succeed through its gate :-( Until this has been fixed, plea

[openstack-dev] [ironic] weekly subteam status report

Gate failures dominated the news last week and as this week starts to pick up steam, it looks like gate failures will again dominate the news. On other fronts... Hi, We are delighted to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0

[openstack-dev] [ironic] weekly subteam status report

Hi, We are elated to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 25.01.2016): - Ironic: 151 bugs (-1) + 171 wishlist items (+7). 14 new (-1), 111 in progress (

[openstack-dev] [ironic] weekly subteam status report

Hi, We are flabergasted to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 01.02.2016): - Ironic: 157 bugs (+6) + 170 wishlist items (-1). 14 new, 116 in progress

Re: [openstack-dev] [Ironic] Specs process query

On 1 July 2015 at 08:25, Matt Keenan wrote: > Hi, > > In submitting my first ironic spec, I am following the process outlined at: > https://wiki.openstack.org/wiki/Ironic/Specs_Process > > As of Kilo this suggests we also follow: > > http://lists.openstack.org/pipermail/openstack-dev/2014-Augus

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Oslo (lintan) = initial (unstable-API) releases for oslo.cache, oslo.reports, oslo.service, automaton, futurist are in pypi - oslo.service and automation is alrea

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Jul 13 (diff with Jun 29) Open: 147 (-3). 6 new (+1), 52 in progress, 1 critical (+1), 10 high (-1) and 8 incomplete (-1) Nova b

Re: [openstack-dev] [Ironic] NoFreeConductorWorker going away with move to Futurist?

On 22 July 2015 at 08:40, Dmitry Tantsur wrote: > Hi all! > > Currently _spawn_worker in the conductor manager raises > NoFreeConductorWorker if pool is already full. That's not very user > friendly (potential source of retries in client) and does not map well on > common async worker patterns. >

Re: [openstack-dev] [Ironic] Specs process query

On 20 July 2015 at 08:27, Matt Keenan wrote: > On 07/06/15 23:19, Ruby Loo wrote: > >> On 1 July 2015 at 08:25, Matt Keenan > <mailto:[email protected]>> wrote: >> >> Hi, >> >> In submitting my first ironic spec, I am follow

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. (There wasn't any subteam report last week since the meeting was cancelled.) Bugs (dtantsur) Dashboard moved to a new home on openshift: - http://ironic-divi

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Aug 3 (diff with July 27) - Open: 142 (-5). 8 new (+2), 48 in progress (-5), 0 critical, 11 high and 8 incomplete - Nova bugs with

[openstack-dev] [Ironic] Was there a meeting yesterday (August 4, 2015 at 0500 UTC)

Hi, Was there an ironic meeting yesterday (August 4, 2015 at 0500 UTC)? I don't see any meeting logs from then. --ruby __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]

Re: [openstack-dev] [Ironic] Was there a meeting yesterday (August 4, 2015 at 0500 UTC)

On 5 August 2015 at 09:35, Jim Rollenhagen wrote: > On Wed, Aug 05, 2015 at 09:13:18AM -0400, Ruby Loo wrote: > > Hi, > > > > Was there an ironic meeting yesterday (August 4, 2015 at 0500 UTC)? I > don't > > see any meeting logs from then. > > There was

Re: [openstack-dev] [Ironic] weekly subteam status report

Hi, Oops, my bad. To be clear, there was no ironic meeting this week. But if there had been, this is what the subteams would have reported :) --ruby On 5 August 2015 at 09:05, Ruby Loo wrote: > Hi, > > Following is the subteam report for Ironic. As usual, this is pulled > direc

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

On 4 August 2015 at 12:20, Jim Rollenhagen wrote: > On Mon, Jul 27, 2015 at 01:35:25PM -0700, Jim Rollenhagen wrote: > > > > Now we've landed a patch[0] with a new version (1.11) that is not > > backward compatible. It causes newly added Node objects to begin life in > > the ENROLL state, rather

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Aug 10 (diff with Aug 3) - Open: 142. 6 new (-2), 50 in progress (+2), 0 critical, 12 high and 9 incomplete - Nova bugs with Ironi

[openstack-dev] [ironic] weekly meeting time

Hi, Starting last week, we are no longer alternating meeting times. Going forward, the ironic meetings will be held weekly on Mondays at 1700 UTC. (For more information on our weekly meetings, see [0]). There had been a friendly discussion about this [1] and it was mentioned in last week's meetin

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Neutron/Ironic work (jroll) === - all patches are up - some testing was done at the midcycle and patches are being updated from that - nova patches won't

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

On 1 August 2015 at 05:16, Lucas Alvares Gomes wrote: > Hi, > > > It sounds like we all agree -- the client we ship should default to a > fixed, > > older version. Anyone who wants newer functionality can pass a newer > version > > to their client. > > > > Here's the current state of things: > >

[openstack-dev] New API for node create, specifying initial provision state

reply first so that I may not feel the need to reply :-) --ruby maybe chop off this and above when replying :-) On 17 August 2015 at 20:20, Robert Collins wrote: > On 11 August 2015 at 06:13, Ruby Loo wrote: > > Hi, sorry for the delay. I vote no. I understand the rationale of tryi

[openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

Apologies, forgot to add [ironic] to the subject. On 18 August 2015 at 13:27, Ruby Loo wrote: > Hi, > > I want to start a different thread on this topic because I don't think > this is about whether/how to do API microversions. Rather, given that we > are going to support

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

On 18 August 2015 at 13:08, Lucas Alvares Gomes wrote: > HI > > > Hi, I'd like to make sure I understand. Is it the case that ideally, if > we > > could go back in time, we'd like to change the client so it defaults to > 1.1? > > AFAIUI, yes > > > But since we can't, the next client that we ship/

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

>> On 17 August 2015 at 20:20, Robert Collins >> wrote: >> >>> On 11 August 2015 at 06:13, Ruby Loo wrote: >>> > Hi, sorry for the delay. I vote no. I understand the rationale of >>> trying to >>> > do things so that we don't brea

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

On 18 August 2015 at 17:13, Ruby Loo wrote: > > > On 18 August 2015 at 13:08, Lucas Alvares Gomes > wrote: > >> HI >> >> > Hi, I'd like to make sure I understand. Is it the case that ideally, >> if we > > > could go back in time,

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Aug 24 (diff with Aug 10) - Open: 141 (-1). 5 new (-1), 50 in progress, 0 critical, 13 high (+1) and 9 incomplete - Nova bugs with

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

On 20 August 2015 at 23:19, Ruby Loo wrote: > > On 18 August 2015 at 17:13, Ruby Loo wrote: > >> >> >> On 18 August 2015 at 13:08, Lucas Alvares Gomes >> wrote: >> >>> HI >>> >>> > Hi, I'd like to make sure I unders

[openstack-dev] [ironic] final release in Liberty cycle

Hi, As (most of) you are aware, in this cycle, ironic decided to switch to a feature-based release model[0]. Our first semver release, 4.0.0, was tagged this week but a few more things need to be ironed out still (hopefully there will be an announcement about that in the near future). What I wan

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Aug 31 (diff with Aug 24) - Open: 144 (+3). 9 new (+4), 50 in progress, 0 critical, 13 high and 10 (+1) incomplete - Nova bugs wit

Re: [openstack-dev] [all] Base feature deprecation policy

On 3 September 2015 at 08:22, Thierry Carrez wrote: > ... > In particular, the current proposal says: > > "At the very minimum the feature [...] should be marked deprecated (and > still be supported) in the next two coordinated end-of-cyle releases. > For example, a feature deprecated during the

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

On 11 September 2015 at 04:56, Dmitry Tantsur wrote: > Hi all! > > Our install guide is huge, and I've just approved even more text for it. > WDYT about splitting it into "Basic Install Guide", which will contain bare > minimum for running ironic and deploying instances, and "Advanced Install > G

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Sep 14 (diff with Sep 7) - Open: 142 (+4). 11 new (+1), 48 in progress, 0 critical, 11 high and 8 incomplete (-1) - Nova bugs with

Re: [openstack-dev] [ironic] Liberty soft freeze

On 17 September 2015 at 21:50, Jim Rollenhagen wrote: This may also mean in-band RAID configuration may not land; the > interface in general did land, and drivers may do out-of-band > configuration. We assumed that in-band RAID would be done through > zapping. However, if folks can agree on how t

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Sep 21 (diff with Sep 14) - Open: 136 (-6). 7 new (-4), 41 in progress (-7), 0 critical, 12 high (+1) and 9 incomplete - Nova bugs

[openstack-dev] [ironic] subteam leads

Hi Subteam Leads, In today's weekly meeting[1], it was requested that if you have no updates, to please indicate that in the status report, so that we can distinguish between no-update versus not-providing-a-status-report. If you aren't sure whether you're a lead, we think you are if your name is

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Sep 21) - Open: 135 (-1). 9 new (+2), 36 in progress (-5), 0 critical, 7 high (-5) and 9 incomplete - Nova bugs with Ironic tag: 2

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) - (diff with Sep 28, no diff for inspector) - Open: 137 (+2). 4 new (-5), 34 in progress (-2), 0 critical, 7 high and 13 incomplete (+4)

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

Looking forward to more cores!!! On 8 October 2015 at 17:47, Jim Rollenhagen wrote: > Hi all, > > ... I'd like to nominate Vladyslav Drok (vdrok) for the core team. His reviews > have been super high quality, and the quantity is ever-increasing. He's > also started helping out with some smaller

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) - (diff with Oct 5, no diff for inspector) - Open: 143 (+6). 2 new (-2), 36 in progress (+2), 0 critical, 12 high (+5) and 10 incomplete

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

Hi Ramesh, On 15 October 2015 at 11:53, Ramakrishnan G wrote: > > > So what all are the problems ? > 1) Ability to update the driver documentation not-related to Ironic easily > without waiting. > 2) To save some core reviewers time who might not be familiar with the > hardware. > > To solve the

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

Hi Wan-yen, On 19 October 2015 at 01:46, Wan-yen Hsu wrote: > > > I fully agreed with Ramesh. There is a need for driver owners to be able > to quickly update their driver’s document. Particularly, vendor's drivers > have strong > What do you mean by 'quickly'? Quicker than it has been in th

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Oct 12, no diff for inspector) - Open: 150 (+7). 3 new (+1), 41 in progress (+5), 2 critical (+2), 11 high (-1) and 11 incomplete

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

On 22 May 2015 at 21:38, Morgan Fainberg wrote: > This seems like a good idea for a pattern in general to use gong forward. > > > --Morgan > Sent via mobile > > > On May 22, 2015, at 14:57, Michael Still wrote: > > > > Hey, > > > > it would be cool if devs posting changes for nova which depend o

[openstack-dev] [Ironic] new 'Client (CLI) impact' section in ironic spec template

Hi, I recently added a 'Client (CLI) impact' section to the ironic spec template [1], because I was finding it difficult to find that information in submitted specs. If you submitted a spec before May 6-ish, you will probably need to add in this section (even if it isn't applicable). Sorry, I mea

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

Thanks for the summary Devananda. Lots of juicy features to sink our teeth into :-) There was a session with Nova, to discuss HA of nova compute nodes (and Nova's resource model) as it pertains to Ironic. What does a potential future look like? --ruby _

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

On 28 May 2015 at 15:55, Jim Rollenhagen wrote: > ... > I also put an informational spec about this change up in the > ironic-specs repo: https://review.openstack.org/#/c/185171/. My goal was > to discuss this in the spec, but the mailing list is fine too. There are > some unanswered questions in

[openstack-dev] [Ironic] Weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (As of Mon, 1 Jun 17:00 UTC) Open: 150 (+2) 5 new (-2), 45 in progress (+3), 0 critical, 10 high (+3) and 12 (+2) incomplete Neutron/Ironic

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

On 4 June 2015 at 02:58, Xu, Hejie wrote: > ... > And another guideline for when we should bump Mircoversion > *https://review.openstack.org/#/c/187896/* > > > This is timely because just this very minute I was going to send out email to the Ironic com

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

Hi, In Kilo, we introduced microversions but it seems to be a work-in-progress. There is an effort now to add microversion into the API-WG's guidelines, to provide a consistent way of using microversions across OpenStack projects [1]. Specifically, in the context of this email, there is a proposed

Re: [openstack-dev] [Ironic] Time to decide something on the vendor tools repo

On 4 June 2015 at 09:29, Dmitry Tantsur wrote: On the summit we were discussing things like chassis discovery, and arrived > at rough conclusion that we want it to be somewhere in a separate repo. > More precisely, we wanted some place for vendor to contribute code (aka > scripts) that aren't goo

[openstack-dev] [Ironic] removal of deprecated items from Kilo

Hi, As noted in the Upgrade Notes in Kilo[1]: 1. The driver_info parameters of "pxe_deploy_kernel" and "pxe_deploy_ramdisk" were deprecated in favour of "deploy_kernel" and "deploy_ramdisk". 2. Drivers implementing their own version of the vendor_passthru() method has been deprecated in favour o

[openstack-dev] [Ironic] subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Drivers == iLO (wanyen) -- 3rd-party CI is ready but need to setup isloated network environment to roll it out Several specs are under review: -

[openstack-dev] [Ironic] weekly meetings and sub-team reports and people

Hi, I noticed (from reading the logs[1]) that there weren't many folks in this week's weekly meeting. And no cores attended. And the sub-team reports (in our etherpad[2]) were woefully lacking. I guess that means only driver developers are working like mad (just kidding). I'm hoping this was a on

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

On 15 June 2015 at 13:07, Jay Pipes wrote: > It has come to my attention in [1] that the microversion spec for Nova [2] > and Ironic [3] have used the project name -- i.e. Nova and Ironic -- > instead of the name of the API -- i.e. "OpenStack Compute" and "OpenStack > Bare Metal" -- in the HTTP h

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (as of Mon, 15 Jun 15:00 UTC, diff since 1 Jun) Open: 159 (+9) 5 new (0), 51 in progress (+6), 0 critical, 12 high (+2) and 12 incomplete

[openstack-dev] [Ironic] ironic-lib library

Hi, I haven't paid any attention to ironic-lib; I just knew that we wanted to have a library of common code so that we didn't cut/paste. I just took a look[1] and there are files there from 2 months ago. So far, everything is under ironic_lib (ie, no subdirectories to group things). Going forward,

Re: [openstack-dev] [Ironic] Adopting ironic-lib in Ironic

On 16 June 2015 at 03:12, Dmitry Tantsur wrote: > On 06/16/2015 08:58 AM, Ramakrishnan G wrote: > >> >> Hi All, >> >> Some time back we created a new repository[1] to move all the reusable >> code components of Ironic to a separate library. The branched out code >> has changed and there has been

[openstack-dev] [Ironic] weekly subteam status report

Hi, Happy June Solstice! Things are warming up in Ironic-land. Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, 22 Jun 15:30 UTC (diff since 15 Jun, no diff for Nova bugs for now): -

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, 29 Jun 16:00 UTC - Open: 150 (-1). 5 new, 52 in progress (+4), 0 critical, 11 high (+1) and 9 incomplete (-1) - Nova bugs with Iro

  1   2   >