Re: [openstack-dev] [Ironic] Preparing for functional testing in Ironic. Will likely break any in-flight patches.

On Mon, Sep 28, 2015 at 09:00:07PM +, Villalovos, John L wrote: > Just to give a heads up to people. I have proposed the following patch: > https://review.openstack.org/228612 > > This moves the tests in ironic/tests/ to ironic/tests/unit/ > > Likely this patch will break most in-flight patch

[openstack-dev] [ironic] Mitaka summit session proposal deadline

Hi folks, We need to have our summit sessions decided by October 15. So, I'd like to propose a couple of dates. Oct 9: session proposal deadline. Oct 12: we go through session proposals in the Ironic meeting and try to get a rough order of session priority. Sometime between Oct 12 and 15, we'll

[openstack-dev] [ironic] Some reminders on the specs process

Hi all, Just a couple quick reminders about our specs process, given our new release model: * New specs should be proposed to the specs/approved/ directory, not a mitaka directory. * Specs approved in a previous development cycle do not need to be re-approved for Mitaka. The team reserves th

[openstack-dev] [release][ironic] Announcing ironic-python-agent 1.0.0

Hi all, We're ecstatic to announce the release of ironic-python-agent 1.0.0. This is the first ever release of this project, and is the basis for a stable/liberty branch. We will continue to do intermediary releases and stable branches for IPA, following Ironic's release model. IPA is the heart o

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

On Wed, Oct 07, 2015 at 12:41:55PM -0700, Devananda van der Veen wrote: > Ramesh, > > I thought about your points over night, and then looked at our in-tree > driver code from stable/kilo and asked myself, "what if this driver was out > of tree?" They'd all have broken -- for very similar reasons

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

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 promote someone to core based on a good knowledge of *some* of the code base, and trust them not to +2 things they d

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

On Thu, Oct 08, 2015 at 02:47:01PM -0700, 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 t

Re: [openstack-dev] [Neutron][Ironic] Testing Ironic multi-tenancy feature

On Mon, Oct 12, 2015 at 07:45:55AM +, Pavlo Shchelokovskyy wrote: > Hi all, > > we would like to start preliminary testing of Ironic multi-tenant network > setup which is supported by Neutron in Liberty according to [1]. According > to Neutron design integration with network equipment is done

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

On Wed, Oct 14, 2015 at 08:44:08AM +, Tan, Lin wrote: > Hi guys, > > I am looking at https://bugs.launchpad.net/ironic/+bug/1502903 which > is related to rolling upgrade and here is Jim's patch > https://review.openstack.org/#/c/234450 I really have a concern or > question about how to do Iron

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

On Wed, Oct 14, 2015 at 04:09:07PM -0700, Dan Smith wrote: > > Conductors will always need to talk to the database. APIs may not need > > to talk to the database. I think we can just roll conductor > > upgrades through, and then update ironic-api after that. This should > > just work, as long as we

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

Cross posting to the ops list for visibility. To follow up on this, we decided not to fix this after all. Besides Ramesh's (very valid) points below, we realized that fixing this for out of tree drivers that depended on Kilo behavior would break out of tree drivers that implemented their own boot

[openstack-dev] [ironic] Ironic design summit schedule

Hey all, I sorted out the design summit schedule today, attempting to reduce conflicts and such as much as possible. The schedule is here: http://mitakadesignsummit.sched.org/type/Ironic I created a general summit etherpad for us, that is here: https://etherpad.openstack.org/p/summit-mitaka-iron

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

One more try on the ops list as it turns out I wasn't subscribed... :( // jim > On Oct 14, 2015, at 17:39, Jim Rollenhagen wrote: > > Cross posting to the ops list for visibility. > > To follow up on this, we decided not to fix this after all. Besides > Ramesh's (

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

On Thu, Oct 15, 2015 at 09:23:18PM +0530, Ramakrishnan G wrote: > Hi All, > > This mail is related to driver-specific documentation in Ironic. > > First a bit of context. I work on iLO drivers in Ironic. Our team would > like to document both Ironic driver related stuff (which is related to > Ir

Re: [openstack-dev] [ironic] [horizon] ironic panels

On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: > > Hi all, > > I am currently in the process of writing an Ironic panel in Horizon > upstream. It was originally intended for this panel to be written in > Angular JS, however, as I understand, no horizon angular work will > merge for

Re: [openstack-dev] [ironic] Ironic design summit schedule

On Mon, Oct 19, 2015 at 02:33:57PM -0700, Wan-yen Hsu wrote: > Hi Jim, > > Is it possible to switch Group management session to Thursday? I > have a techtalk at 2:30pm on Wednesday and it makes it very tight for me > and Shiv to attend the group management at 2:50 pm. Since Shiv and myself

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

On Thu, May 28, 2015 at 12:54:58PM -0400, Monty Taylor wrote: > On 05/28/2015 12:41 PM, Devananda van der Veen wrote: > > 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

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

On Tue, Jun 09, 2015 at 04:33:41PM -0400, Ruby Loo wrote: > 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 > dev

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

On Thu, May 28, 2015 at 12:55:50PM -0700, Jim Rollenhagen wrote: > [snip] > > 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. T

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

On Mon, Jun 15, 2015 at 01:07:39PM -0400, 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" --

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

On Tue, Jun 16, 2015 at 08:56:37AM +0200, Dmitry Tantsur wrote: > On 06/04/2015 08:58 AM, Xu, Hejie 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 h

Re: [openstack-dev] [ironic] Baremetal Deploy Ramdisk functional testing

On Mon, Feb 15, 2016 at 01:48:11PM +0200, Maksym Lobur wrote: > Re-sending with Ironic stamp… Folks, please see below: Hi, I meant to reply to this earlier, but didn't get to it, sorry for that. > > > > > Hi All, > > > > In bareon [1] we have test framework to test deploy ramdsik with bareon

Re: [openstack-dev] [ironic] More midcycle details

We are live! Please do join :) // jim On Thu, Feb 11, 2016 at 05:20:27AM -0800, Jim Rollenhagen wrote: > Hi all, > > Our midcycle is next week! Here's everything you need to know. > > First and foremost, please RSVP on the etherpad, and add any topics > (with your na

[openstack-dev] [ironic] Midcycle summary part 1/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 1/6 was February 16, 1500-2000 UTC. * We talked a

[openstack-dev] [ironic] Midcycle summary part 2/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 2/6 was February 17, -0400 UTC. * We briefly

[openstack-dev] [ironic] midcycle voice channel is 7778

Hi, We've moved the midcycle to channel 7778 on the infra conferencing system - something is wrong with (no audio coming through). /me lets infra know as well // jim __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [ironic] midcycle voice channel is 7779

So, someone has injected their hold music into 7778. We've now moved to 7779, sorry for the trouble :( // jim On Wed, Feb 17, 2016 at 07:01:22AM -0800, Jim Rollenhagen wrote: > Hi, > > We've moved the midcycle to channel 7778 on the infra conferencing > system - something

[openstack-dev] [ironic] Midcycle summary part 3/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 2/6 was February 17, 1500-2000 UTC. * Discussed b

[openstack-dev] [ironic] Midcycle summary part 4/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 4/6 was February 18, -0400 UTC. * Did a nova

Re: [openstack-dev] [ironic] Midcycle summary part 3/6

On Wed, Feb 17, 2016 at 12:14:29PM -0800, Jim Rollenhagen wrote: > Hi all, > > As our midcycle is virtual and split into 6 "sessions" for the sake of > timezones, we'll be sending a brief summary of each session so that > folks can catch up before the next one. All o

[openstack-dev] [ironic] Midcycle summary part 5/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 5/6 was February 18, 1500-2000 UTC. * Discussed l

[openstack-dev] [ironic] Midcycle summary part 6/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 6/6 was February 19, -0400 UTC. This will be

Re: [openstack-dev] [ironic] [stable] iPXE / UEFI support for stable liberty

> On Feb 22, 2016, at 15:15, Chris K wrote: > > Hi Ironicers, > > I wanted to draw attention to iPXE / UEFI support in our stable liberty > branch. Which doesn't exist, right? Or does it work depending on some other factors? > There are environments that require support for UEFI, while iron

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

On Tue, Feb 23, 2016 at 05:32:44PM -0500, James Slagle wrote: > On Tue, Feb 23, 2016 at 5:18 PM, Devananda van der Veen > wrote: > > 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 n

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

On Wed, Mar 09, 2016 at 12:26:18PM -0500, Doug Hellmann wrote: > openstack/ironic-lib 1.1.0 > openstack/python-ironic-inspector-client 1.5.0 > openstack/python-ironicclient 1.2.0 +1, thanks Doug :) // jim __ OpenStack Develo

[openstack-dev] [ironic] ironic 5.0.0, the rest of mitaka, and beyond

Hi all, (grab some coffee, this is a bit long) Today we released ironic 5.0.0. Congrats to the team, and thank you for your hard work so far this cycle! You've all done an amazing job getting things done. The release notes[0] show how many awesome things we've shipped this cycle. Even Doug compli

[openstack-dev] [ironic] PTL candidacy

Hi all, I've had the pleasure of serving the ironic community as PTL for the Mitaka cycle, and I'd like to do it again for the Newton cycle, if you'll have me. We've done some amazing things over the past 6 months and I think we can do even more over the next 6 months. Things I'd like to do: * B

Re: [openstack-dev] [all] Maintaining httplib2 python library

On Mon, Mar 14, 2016 at 09:24:00AM -0500, Ian Cordasco wrote: >   > > -Original Message- > From: Davanum Srinivas > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: March 14, 2016 at 09:18:50 > To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [ironic] Summit session planning

Hey all, I mentioned it in Friday's novel, and again in the meeting this morning, but just to be sure everyone sees it: we're starting to plan summit sessions for Austin. Please put your ideas on this etherpad with your name and a link to more info on it. Thanks! https://etherpad.openstack.org/p/

Re: [openstack-dev] [ironic] ironic 5.0.0, the rest of mitaka, and beyond

On Fri, Mar 11, 2016 at 04:51:31PM -0800, Jim Rollenhagen wrote: [snip] > And code that we should land for the 5.1.0 release: > > * Anything fixing critical/high bugs > > * Partition image support for agent drivers > * https://review.openstack.org/#/c/1

Re: [openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

On Fri, Mar 18, 2016 at 08:16:00AM -0700, John Dickinson wrote: > 3) A dashboard generated from gerrit and git data. > http://not.mn/swift/swift_community_dashboard.html The "Community Starred > Patches" is a list of the top 20 commonly starred patches by the Swift > community. Basically, for

Re: [openstack-dev] [release] Release countdown for week R-2, Mar 21-25

Ironic and IPA should have releases coming next week. // jim > On Mar 17, 2016, at 12:23, Doug Hellmann wrote: > > We're almost to the finish line with Mitaka! > > Focus > - > > Project teams following the cycle-with-milestone model should be > testing their release candidates and fixin

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

On Wed, Mar 16, 2016 at 10:29:48PM -0400, Adam Young wrote: > On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote: > >Hi > > > >I have one proposal[1] related to negative tests in Tempest, and > >hoping opinions before doing that. > > > >Now Tempest contains negative tests and sometimes patches are bein

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

On Fri, Mar 18, 2016 at 05:26:13PM +0300, Evgeniy L wrote: > On Thu, Mar 17, 2016 at 3:16 PM, Dmitry Tantsur wrote: > > > On 03/16/2016 01:39 PM, Evgeniy L wrote: > > > >> Hi Dmitry, > >> > >> I can try to provide you description on what current Nailgun agent is, > >> and what are potential requi

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

dule yet > another discussion on closer integration with Ironic. > > BTW, about a year ago (in Grenoble) we agreed that it is not even > necessary to merge such custom things into Ironic tree. Happily, Ironic is > smart enough to consume drivers using stevedore. About ironic-inspect

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote: > Hi > > I have one proposal[1] related to negative tests in Tempest, and > hoping opinions before doing that. > > Now Tempest contains negative tests and sometimes patches are being > posted for adding more negative tests, but I'd

Re: [openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

On Sat, Mar 19, 2016 at 04:51:14PM +, Jeremy Stanley wrote: > On 2016-03-19 02:28:48 + (+), Amrith Kumar wrote: > > Maybe we could collaborate and build something that'd work for > > multiple projects? Happy to help with this. It is clearly a > > problem that some projects seem to be fa

[openstack-dev] [ironic] Keeping up with RFEs

Hey all, I just burned through every RFE we have filed. I've approved the ones that are trivial or have a spec approved already (by changing the tag to rfe-approved), asked for a spec on many others, and left the ones with an unmerged spec alone. Going forward, I plan to take a look at incoming R

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I > think it's great that you took this to the mailing list, especially seeing > the conversation that h

[openstack-dev] [ironic] Newton is open!

Hi Ironickers, We've successfully released ironic and all of its subprojects, and cut the stable/mitaka branch for those. Newton is now open for development! As a reminder, please propose sessions for the Austin summit here: https://etherpad.openstack.org/p/ironic-newton-summit And I've started

Re: [openstack-dev] [ironic] Newton is open!

On Thu, Mar 24, 2016 at 12:03:34PM -0700, Jim Rollenhagen wrote: > Hi Ironickers, > > We've successfully released ironic and all of its subprojects, and cut > the stable/mitaka branch for those. > > Newton is now open for development! > > As a reminder, please pr

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

Hey all, I'm nominating Julia Kreger (TheJulia in IRC) for ironic-core. She runs the Bifrost project, gives super valuable reviews, is beginning to lead the boot from volume efforts, and is clearly an expert in this space. All in favor say +1 :) // jim __

Re: [openstack-dev] [containers][horizon][magnum-ui] - Stable version for Liberty?

On Thu, Mar 24, 2016 at 05:17:09PM +, Adrian Otto wrote: > Marcos, > > Great question. The current intent is to backport security fixes and critical > bugs, and to focus on master for new feature development. Although we would > love to expand scope to backport functionality, I’m not sure it

Re: [openstack-dev] Bots and Their Effects: Gerrit, IRC, other

On Thu, Mar 24, 2016 at 09:56:16AM +0100, Thierry Carrez wrote: > Anita Kuno wrote: > >[...] > >So some items that have been raised thus far: > >- permissions: having a bot on gerrit with +2 +A is something we would > >like to avoid > >- "unsanctioned" bots (bots not in infra config files) in chann

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Wed, Mar 23, 2016 at 06:02:47PM -0400, Doug Hellmann wrote: > Excerpts from Jim Rollenhagen's message of 2016-03-23 14:46:16 -0700: > > On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > Hi Mike, and sorry I mis

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

On Fri, Mar 25, 2016 at 12:03:34PM -0400, Julia Kreger wrote: > On Thu, Mar 24, 2016 at 3:08 PM, Jim Rollenhagen > wrote: > > > I'm nominating Julia Kreger (TheJulia in IRC) for ironic-core. > > > I would like to thank the academy for... oh wait... wrong speech.

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote: > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000: > > On 24/03/16 08:01, Doug Hellmann wrote: > > > Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000: > > >> Hi Mike, and sorry I missed you on IRC to

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Fri, Mar 25, 2016 at 11:32:58AM -0700, Mike Perez wrote: > > On Mar 25, 2016, at 06:10, Doug Hellmann wrote: > > > > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000: > >> > >> All docs need to be drafted somewhere. I don't care where that is, but > >> make the suggestion o

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Fri, Mar 25, 2016 at 03:20:30PM -0400, Doug Hellmann wrote: > Excerpts from Jim Rollenhagen's message of 2016-03-25 10:45:30 -0700: > > On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote: > > > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000: > > > > On 24/03/16 08:

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

Ramakrishnan has clearly been reviewing tons of code lately, and more importantly the quality of the reviews and the knowledge of the code base, the problem space, and the edge cases has shown through as nothing short of awesome. Enthusiastic +2 from me! // jim On Mon, 2015-03-09 at 22:03 +,

Re: [openstack-dev] [Glance] Nitpicking in code reviews

On Thu, Mar 12, 2015 at 09:07:30AM -0500, Flavio Percoco wrote: > On 11/03/15 15:06 -1000, John Bresnahan wrote: > >FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough > >thing to get right and speaks to the quality standard to which the product > >is held even in commit mess

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

I’m not sure that recommending one or the other is best. We should lay out the options (as you just did) and let folks decide what works best for them. For things like discoverd, where you have many users, perhaps you should allow the user to pass a version (for example, option 2 depends on the us

Re: [openstack-dev] [ironic] Boot from Volume meeting?

On Wed, Mar 1, 2017 at 9:07 AM, Dmitry Tantsur wrote: > Thanks for writing this! > > On 02/28/2017 03:42 PM, Julia Kreger wrote: > >> Greetings fellow ironic humanoids! >> >> As many have known, I've been largely attempting to drive Boot from >> Volume functionality in ironic over the past two ye

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On Tue, Mar 7, 2017 at 6:36 AM, Dmitry Tantsur wrote: > On 03/07/2017 12:32 PM, Miles Gould wrote: > >> On 06/03/17 20:46, Mario Villaplana wrote: >> >>> We also still have yet to decide what a suitable deprecation period is >>> for this change, as far as I'm aware. Please respond to this email >

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On Wed, Mar 8, 2017 at 9:05 AM, Mario Villaplana wrote: > We want to deprecate ironic CLI soon, but I would prefer if that were > discussed on a separate thread if possible, aside from concerns about > versioning in ironic CLI. Feature parity should exist in Pike, then we > can issue a warning in

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Mon, Mar 13, 2017 at 12:58 PM, Chris Friesen wrote: > On 03/10/2017 01:37 PM, John Griffith wrote: > > Now that micro-versions are *the API versioning scheme to rule them all* >> one >> question I've not been able to find an answer for is what we're going to >> promise >> here for support and

Re: [openstack-dev] [ironic] New mascot design

On Fri, Mar 10, 2017 at 11:28 AM, Heidi Joy Tretheway < heidi...@openstack.org> wrote: > Hi Ironic team, > Here’s an update on your project logo. Our illustrator tried to be as true > as possible to your original, while ensuring it matched the line weight, > color palette and style of the rest. Th

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

On Wed, Mar 15, 2017 at 8:15 AM, John Garbutt wrote: > On 15 March 2017 at 09:50, Thierry Carrez wrote: > > Colette Alexander wrote: > >> Currently the Stewardship Working Group meetings every other Thursday at > >> 1400 UTC. > >> > >> We've had a couple of pings from folks who are interested in

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

On Thu, Mar 16, 2017 at 5:17 AM, Thierry Carrez wrote: > Jim Rollenhagen wrote: > > On Wed, Mar 15, 2017 at 8:15 AM, John Garbutt > <mailto:j...@johngarbutt.com>> wrote: > >> In the absence of tooling, could we replace the meeting with weekly > >>

Re: [openstack-dev] [ironic] Translations removal

On Wed, Mar 22, 2017 at 11:44 AM, Sean McGinnis wrote: > On Wed, Mar 22, 2017 at 08:42:42AM -0500, Kevin L. Mitchell wrote: > > On Tue, 2017-03-21 at 22:10 +, Taryma, Joanna wrote: > > > However, pep8 does not accept passing variable to translation > > > functions, so this results in ‘H701 E

Re: [openstack-dev] Project Navigator Updates - Feedback Request

On Thu, Mar 30, 2017 at 12:04 PM, Jimmy McArthur wrote: > This (http://paste.openstack.org/show/604775/) is absolutely perfect. I > feel like the format could work for microversions as well. Anyone from > Neutron or another microversion project that could weigh in? > This mostly seems fine to me

Re: [openstack-dev] [ironic] Translations removal

On Thu, Mar 30, 2017 at 2:36 PM, Doug Hellmann wrote: > Excerpts from Sean McGinnis's message of 2017-03-22 10:44:05 -0500: > > On Wed, Mar 22, 2017 at 08:42:42AM -0500, Kevin L. Mitchell wrote: > > > On Tue, 2017-03-21 at 22:10 +, Taryma, Joanna wrote: > > > > However, pep8 does not accept p

Re: [openstack-dev] [ironic] Translations removal

On Thu, Mar 30, 2017 at 3:24 PM, Doug Hellmann wrote: > Excerpts from Jim Rollenhagen's message of 2017-03-30 15:08:13 -0400: > > On Thu, Mar 30, 2017 at 2:36 PM, Doug Hellmann > > wrote: > > > > > Excerpts from Sean McGinnis's message of 2017-03-22 10:44:05 -0500: > > > > On Wed, Mar 22, 2017 a

[openstack-dev] [ironic][nova] Goodbye^W See you later

Hey friends, I've been mostly missing for the past six weeks while looking for a new job, so maybe you've forgotten me already, maybe not. I'm happy to tell you I've found one that I think is a great opportunity for me. But, I'm sad to tell you that it's totally outside of the OpenStack community.

Re: [openstack-dev] [ironic] Remove in-tree policy and config?

Huge +1, I didn't realize this was in docs now. We can finally stop doing it manually \o/ // jim On Mon, Jan 22, 2018 at 7:45 AM, John Garbutt wrote: > Hi, > > While I was looking at the traits work, I noticed we still have policy and > config in tree for ironic and ironic inspector: > > http:

Re: [openstack-dev] [ALL][requirements] A freeze is coming and you should be prepared

On Fri, Jan 26, 2018 at 9:46 AM, Matt Riedemann wrote: > > Well, the requirements jobs seem to be busted as well: > > http://logs.openstack.org/93/538093/1/check/legacy-requireme > nts-integration-dsvm/157d877/job-output.txt.gz#_2018-01-26_11_17_31_182762 The fix is in the gate, FWIW: https://re

[openstack-dev] [ironic] v2 API meeting cancelled for July 19

Hey all, Just a reminder the v2 API meeting will be cancelled for July 19, as both Deva and I will be at the Nova midcycle. We'll resume on July 26. // jim __ OpenStack Development Mailing List (not for usage questions) Unsu

Re: [openstack-dev] [ironic] [oslo] Stevedore 1.16 breaks IPA gate

On Sun, Jul 17, 2016 at 04:32:01PM +0200, Doug Hellmann wrote: > Excerpts from Joshua Harlow's message of 2016-07-15 18:00:37 -0700: > > I assume this is connected into: > > > > https://review.openstack.org/#/c/334014/ > > > > Which was proposed a few weeks ago, I'd be nice to identify the causin

[openstack-dev] [ironic][nova] Nova midcycle, Ironic perspective

Hi all, The nova midcycle went very well from an ironic perspective. Jay Pipes and Andrew Laski had a new (better!) proposal for how we schedule ironic resources, which I'd like to detail for folks. We explicitly split this off from the topic of running multiple nova-compute daemons for Ironic, be

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Tue, Jul 26, 2016 at 08:36:01PM +, Steven Dake (stdake) wrote: > Dims, > > The project-config addition was debated by Andreas before this partnership > in this press release was announced and the full intent of the project was > understood. The argument I see used in the review is that si

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Tue, Jul 26, 2016 at 09:42:10PM +, Steven Dake (stdake) wrote: > > > On 7/26/16, 2:13 PM, "Jim Rollenhagen" wrote: > > >On Tue, Jul 26, 2016 at 08:36:01PM +, Steven Dake (stdake) wrote: > >> Dims, > >> > >> The pro

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Thu, Jul 28, 2016 at 02:29:18PM -0400, Zane Bitter wrote: > On 28/07/16 12:54, Jay Pipes wrote: > >The TC has given guidance on this already: > > > >http://governance.openstack.org/resolutions/20160119-stackforge-retirement.html > > > > > >"In order to simplify software development lifecycle tra

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

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 order for what is actually used for the node: 1) node.network

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

On Mon, Aug 01, 2016 at 08:10:18AM -0400, 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

[openstack-dev] [nova][ironic] A couple feature freeze exception requests

Yes, I know this is stupid late for these. I'd like to request two exceptions to the non-priority feature freeze, for a couple of features in the Ironic driver. These were not requested at the normal time as I thought they were nowhere near ready. Multitenant networking == I

Re: [openstack-dev] [nova] Belated nova newton midcycle recap (part 2)

lked about supporting dynamic resource classes for Ironic use cases > which is a stretch goal for Nova in Newton. Jay has a spec for that here: > > https://review.openstack.org/#/c/312696/ > > There is a lot more detail in the etherpad and honestly Jay Pipes or Jim > Rollenhagen

[openstack-dev] [ironic] Priorities for the rest of the cycle

Hey all, There's some deadlines coming up: * non-client library freeze in 3 weeks * client library freeze in 4 weeks * final releases in 8 weeks http://releases.openstack.org/newton/schedule.html As usual, we don't do a hard feature freeze at the normal feature freeze date (4 weeks from now), h

Re: [openstack-dev] [tripleo] [ironic] Exception registering nodes when Ironic API with apache

On Sun, Jul 31, 2016 at 07:01:16PM -0400, Emilien Macchi wrote: > Hi, > > On Friday we landed a patch in TripleO to deploy Ironic API in WSGI with > Apache. > Since then, our baremetal CI jobs were failing randomly, and a lot of > time, with an exception. > I decided to revert the patch to bring

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On Thu, Aug 04, 2016 at 09:24:15AM -0400, Doug Hellmann wrote: > Excerpts from Kiall Mac Innes's message of 2016-08-04 01:27:23 +0100: > > On 18/07/16 20:14, Jeremy Stanley wrote: > > > Note that this will only be true if the change's parent commit in > > > Gerrit was the branch tip at the time it

Re: [openstack-dev] [nova] os-capabilities library created

On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please see th

Re: [openstack-dev] [nova] os-capabilities library created

>> On Aug 4, 2016, at 10:48, Jay Pipes wrote: >> >>> On 08/04/2016 10:31 AM, Jim Rollenhagen wrote: >>> On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: >>> Hi Novas and anyone interested in how to represent capabilities in a >>> consist

Re: [openstack-dev] [Nova] Some thoughts on API microversions

On Thu, Aug 04, 2016 at 04:31:00PM -0400, Jay Pipes wrote: > On 08/04/2016 01:17 PM, Chris Friesen wrote: > >On 08/04/2016 09:28 AM, Edward Leafe wrote: > > > >>The idea that by specifying a distinct microversion would somehow > >>guarantee > >>an immutable behavior, though, is simply not the case.

Re: [openstack-dev] [Nova] Some thoughts on API microversions

On Wed, Aug 03, 2016 at 08:54:07PM -0400, Andrew Laski wrote: > I've brought some of these thoughts up a few times in conversations > where the Nova team is trying to decide if a particular change warrants > a microversion. I'm sure I've annoyed some people by this point because > it wasn't germane

[openstack-dev] [ironic] About third-party CI

Hi Ironicers, This email serves as a reminder (and a bit of a call to action) about our third party CI policy: http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/third-party-ci.html 1) When I went to find a link to the policy, I realized that it isn't in our developer docs

Re: [openstack-dev] [ironic] About third-party CI

On Wed, Aug 10, 2016 at 9:21 AM, Jim Rollenhagen wrote: > Hi Ironicers, > > This email serves as a reminder (and a bit of a call to action) about our > third party CI policy: > http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/third-party-ci.html > > 1

Re: [openstack-dev] [ironic] About third-party CI

On Wed, Aug 10, 2016 at 1:05 PM, Clint Byrum wrote: > Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400: >> 2) A number of drivers do not have third-party CI up, let alone reporting >>on patches. Unless someone moves quickly, I strongly suspect the following >>drivers wi

Re: [openstack-dev] [all] versioning the api-ref?

On Thu, Aug 11, 2016 at 6:13 PM, John Dickinson wrote: > > > On 11 Aug 2016, at 15:02, Brian Rosmaita wrote: > >> I have a question about the api-ref. Right now, for example, the new >> images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are >> being generated as we speak for change

Re: [openstack-dev] [nova] os-capabilities library created

On Thu, Aug 11, 2016 at 9:03 PM, Jay Pipes wrote: > On 08/11/2016 05:46 PM, Clay Gerrard wrote: >> >> On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe > > wrote: >> >> >> Overall this looks good, although it seems a bit odd to have >> ALL_CAPS_STRINGS to represent all:caps:

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

Hi Ironickers, There was a big thread here[0] about Cinder, driver removal, and standard deprecation policy. If you haven't read through it yet, please do before continuing here. :) The outcome of that thread is summarized well here.[1] I know that I previously had a different opinion on this, b

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

On Fri, Aug 19, 2016 at 10:54 AM, Mathieu Mitchell wrote: > > > On 2016-08-19 10:42 AM, Doug Hellmann wrote: >>> >>> 3) Add a ``enable_unsupported_drivers`` config option that allows >>> enabling >>> >drivers marked supported=False. If a driver is in enabled_drivers, >>> > has >> >> Do you mea

<    1   2   3   4   5   >