Re: [openstack-dev] [ironic] When should a project be under Ironic's governance?

On Mon, Oct 17, 2016 at 4:27 PM, Michael Turek wrote: > Hello ironic! > > At today's IRC meeting, the questions "what should and should not be a > project be under Ironic's governance" and "what does it mean to be under > Ironic's governance" were raised. Log here: > > http://eavesdrop.openstack.o

[openstack-dev] [ironic] ironic-specs core team update

Hi friends, At the summit we discussed making the ironic-specs core team the same as the ironic core team. This proposal had unanimous support from the existing specs core team, so I've made the changes in gerrit now. https://review.openstack.org/#/admin/groups/352,members Happy +2'ing! // jim

Re: [openstack-dev] [ironic][ironic-python-agent]ask something about this commit https://review.openstack.org/#/c/369245/

On Mon, Oct 31, 2016 at 3:46 AM, wrote: > Hi ironic team： > > I send this email to ask something about > https://review.openstack.org/#/c/369245/ . > > The jenkins has -1 for this commit.After I rebase the code Oct 27，this > commit didn't pass the jenkins anymore. > > And I don't know what ca

[openstack-dev] [ironic] PTG attendance

Hey folks, Thought I sent this to the list, but apparently not, maybe just the organizers. The ironic team *does* plan to be at the PTG in February. Hope to see everyone there. :) // jim __ OpenStack Development Mailing Lis

[openstack-dev] [ironic] Core team updates

Hey friends, The ironic-core team has done some great things over the last year. We've landed a ton of code, grown some new members (and continually growing more), and generally stayed pretty well connected. However, some folks are clearly reviewing far more than others. While I realize that folk

Re: [openstack-dev] [requirements][lbaas] gunicorn to g-r

On Mon, Oct 17, 2016 at 1:33 PM, Doug Wiegley wrote: > Hi, > > On a review to add gunicorn to global requirements[1], we were asked to send > a notice to the ML. In this particular application, it’s for use inside a > service VM for Octavia. Objections/comments/other? global-requirements is mea

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

> > ++ > > Thanks for bringing this up Dmitry! Might I suggest, if we don't already > have it, that this would be a good time to track (in a spreadsheet-like > form), the jobs with the tests covered by each job (or desired but not > covered yet). I can never remember what we are testing vs not test

Re: [openstack-dev] [QA][Ironic]Removal of Ironic tests from Tempest

On Wed, Oct 12, 2016 at 1:01 PM, Jordan Pittier wrote: > Hi guys, > As you may know we are pushing projects to use Tempest plugins and we are > only keeping "core" projects tests in Tempest tree. > > There has been several attempts to remove Ironic from Tempest so I guess > it doesn't come as a s

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

On Wed, Oct 12, 2016 at 8: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 def

[openstack-dev] [ironic] Meeting logs for October 12, 2016

Hi all, Since meetbot was down yesterday, thought I'd send out the meeting logs for the ironic meeting. http://paste.openstack.org/show/585338/ // jim __ OpenStack Development Mailing List (not for usage questions) Unsubscr

[openstack-dev] [ironic] Summit schedule is set

Hi folks, We've locked in our summit schedule, that is here (including a bonus talk at the top due to how the search works): https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ironic%3A Please do let me know ASAP if there are any major conflicts. If you've proposed o

Re: [openstack-dev] [ironic][neutron] ML2 plugin for Ironic needs

On Mon, Oct 10, 2016 at 4:32 AM, Vasyl Saienko wrote: > Hello Community, > > > Ironic and Neutron projects have become integrated even closer with > multitenancy implementation in Ironic. > > There are 2 bugs that require separate ML2 driver specifically for Ironic > needs: > > > Booting ironic in

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On Tue, Oct 11, 2016 at 6:43 AM, Dmitry Tantsur wrote: > On 10/10/2016 11:34 PM, Tony Breeds wrote: >> >> On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: >> >>> I think it would also make sense to *release* on the boundary of the >>> switch; >>> so that it’s clear which phase a re

Re: [openstack-dev] [ironic][docs] What is the policy for backporting docs changes to stable branches?

On Wed, Oct 5, 2016 at 9:00 AM, Luigi Toscano wrote: > On Wednesday, 5 October 2016 15:31:50 CEST Pavlo Shchelokovskyy wrote: >> Hi all, >> >> lately I realized that docs for two of the features I was working on during >> Newton cycle are absent from Ironic's new install guide [0]. This is my >> f

Re: [openstack-dev] [tc] open question to the candidates

On Mon, Oct 3, 2016 at 11:30 AM, gordon chung wrote: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the > candidates for those

Re: [openstack-dev] TC candidacy

>> +1 to release notes or something of that like. i was asked to give an >> update on the TC internally and it seems the only information out there >> is to read through backlog of meeting logs or track the items that do >> get raised to ML. even then, it's hard to define what deliverables were >>

[openstack-dev] TC candidacy

I'd like to throw in my hat to serve the community as a TC member. My name is Jim Rollenhagen, but I'm better known in the community as jroll. I've worked in many environments, from 20-person startup to massive corporations. For the past three years, I've been working on OpenS

[openstack-dev] [ironic] Newton post-mortem

Similar to keystone/neutron/nova, I thought it would be healthy for us to do a post-mortem on the Newton cycle. Here's the etherpad: https://etherpad.openstack.org/p/ironic-newton-retrospective Let's try to keep it troll-free (I know it's hard). Also note I put a poll about having a summit sessio

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

On Thu, Sep 22, 2016 at 2:30 PM, Devananda van der Veen wrote: > 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 >

Re: [openstack-dev] [ironic] base node payload for notification

On Tue, Sep 27, 2016 at 9:57 AM, Loo, Ruby wrote: > Hi Yuriy, > > > > Thanks for bringing this up. I'm good with your list, with the exception of > driver_info and instance_info. I'm on the fence with these two. If we assume > that any secrets will be bleep'd out (configdrives won't be there), is

[openstack-dev] [ironic] Summit session planning

Hey friends, Just a reminder to add your summit session proposals to our etherpad: https://etherpad.openstack.org/p/ironic-ocata-summit Unless I hear of an earlier deadline from summit planning folks, I'd like to have these locked in by October 14 (as I'm out the week before summit). This means w

[openstack-dev] [ironic] Ocata is open

Hi friends, The newton branch was cut last week. It was an amazing cycle, with tons of awesome features. Thanks to everyone that contributed and focused to get so much done! :) Details are here: http://docs.openstack.org/releasenotes/ironic/newton.html Now, on to Ocata. The branch is open, and w

Re: [openstack-dev] [ironic] ironic-inspector-core team update

// jim On Mon, Sep 26, 2016 at 5:24 AM, Dmitry Tantsur wrote: > Hi folks! > > As you probably know, Imre has decided to leave us for other challenges, so > our small core team has become even smaller. I'm removing him on his > request. > > I suggest adding Milan Kovacik (milan or mkovacik on IRC

Re: [openstack-dev] [ironic] [qa] Testing config drive creation in our CI

On Mon, Sep 26, 2016 at 7:29 AM, Sean Dague wrote: > On 09/26/2016 07:15 AM, Dmitry Tantsur wrote: >> On 09/26/2016 01:09 PM, Sean Dague wrote: >>> This should probably be set at the job level, and not buried inside >>> devstack to be different based on hypervisor. That's going to be a lot >>> mor

Re: [openstack-dev] [ironic] Testing config drive creation in our CI

On Fri, Sep 23, 2016 at 7:37 AM, Dmitry Tantsur wrote: > Hi folks! > > We've found out that we're not testing creating of config drives in our CI. > It ended up in one combination being actually broken (pxe_* + wholedisk + > configdrive). I would like to cover this testing gap. Is there any benefi

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

We decided in the last meeting to cancel next week's meeting. So we'll meet again October 4. Side question: should we just make this meeting biweekly always? // jim __ OpenStack Development Mailing List (not for usage questi

Re: [openstack-dev] [kolla][fuel][tripleo][openstack-ansible] Reference architecture to deploy OpenStack on k8s

On Thu, Sep 22, 2016 at 7:04 AM, Flavio Percoco wrote: > Greetings, > > I've recently started looking into the container technologies around > OpenStack. > More specifically, I've been looking into the tools that allow for deploying > OpenStack on containers, which is what I'm the most interested

[openstack-dev] [ironic] PTL nomination

Hi friends, I'd like to be the ironic PTL for another cycle, if you'll have me. Newton, in my opinion, has been Ironic's best cycle yet. We got a ton of work done, and made good progress on the work we didn't finish. Some of the highlights from this cycle include: * Upgrade testing. We've strugg

Re: [openstack-dev] [ironic] Bug smash day: Wed, Sep 14

On Wed, Sep 14, 2016 at 5:52 AM, Dmitry Tantsur wrote: > On 09/12/2016 08:00 PM, Dmitry Tantsur wrote: >> >> Hi all! >> >> On Wednesday, Sep 14, 2016 we will try to clean up our bug list, triage, >> separate RFEs from real bugs, etc. Then we'll find out which bugs must >> be fixed for Newton, and,

[openstack-dev] [ironic] Marking untested drivers as unsupported

Hi folks, I submitted this patch[0] to mark any untested driver as deprecated. Please review it to be sure I didn't miss anything or mark things that are tested (I suspect SSH driver will be controversial, but from what I've seen, the community is keen to stop supporting that). To be clear, the d

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

On Tue, Sep 13, 2016 at 7:27 AM, Dmitry Tantsur wrote: > On 09/13/2016 12:52 PM, Pavlo Shchelokovskyy wrote: >> >> Hi all, >> >> On Mon, Sep 12, 2016 at 9:28 PM, Loo, Ruby > > wrote: >> >> Cross-project: >> == >> - Infra insists on switching new j

Re: [openstack-dev] [QA] [Ironic] [Tempest] Problem with paramiko on grenade

On Fri, Sep 9, 2016 at 7:32 AM, Dmitry Tantsur wrote: > On 09/08/2016 11:24 AM, Anton Arefiev wrote: >> >> Hi folks! >> >> We've ran into the problem with paramiko, similar to[1] in Inspector. >> Our grenade job fails on TestNetworkBasicOps.test_network_basic_ops with >> [2] or [3] in 90% cases. >

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On Wed, Sep 7, 2016 at 11:43 AM, Thierry Carrez wrote: > Hi everyone, > > As you probably know by now, starting with the Boston event in 2017, the > Summit will happen further away from the release day and more around the > middle of the next development cycle. You can find more info on the > rati

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

On Tue, Sep 6, 2016 at 4:24 PM, Jim Rollenhagen wrote: > On Mon, Aug 29, 2016 at 5:03 AM, Lucas Alvares Gomes > wrote: >> Hi, >> >> I overall agree with the proposed plan. I like the idea of having a >> "supported" flag (or another name as per Kurt's

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

rty driver teams >> that do not implement a reliable reporting CI test system by the N release >> feature freeze (see Deliverable milestones above) will be removed from the >> ironic source tree.", IIUC meaning that conductor will fail startup not >> being able to find th

Re: [openstack-dev] [ironic] API v.next meeting cancelled

On Tue, Sep 6, 2016 at 1:23 PM, Jim Rollenhagen wrote: > We're cancelling the next two meetings as well, for the same reason. > > We'll meet again on September 27. I'm bad at counting, apparently, the next meeting will be September 20. // jim > > On Tue

Re: [openstack-dev] [ironic] API v.next meeting cancelled

We're cancelling the next two meetings as well, for the same reason. We'll meet again on September 27. // jim On Tue, Aug 30, 2016 at 1:32 PM, Jim Rollenhagen wrote: > Sorry for the late notice, but we decided we'd rather keep working on > Newton things this week i

[openstack-dev] [ironic] API v.next meeting cancelled

Sorry for the late notice, but we decided we'd rather keep working on Newton things this week instead of having this meeting, so it's cancelled for today. // jim __ OpenStack Development Mailing List (not for usage questions)

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

On Mon, Aug 22, 2016 at 8:01 AM, Vladyslav Drok wrote: > On Fri, Aug 19, 2016 at 5:15 PM, Jim Rollenhagen > wrote: >> >> Hi Ironickers, >> >> There was a big thread here[0] about Cinder, driver removal, and standard >> deprecation policy. If you haven

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

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

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

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

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

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

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

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

[openstack-dev] [ironic] v2 API workgroup meeting begins July 12

Hey all, I had an action item from the midcycle to kickstart a workgroup for the v2 API. I've set up a meeting for that on Tuesdays at 1800 UTC in #openstack-meeting-3: https://wiki.openstack.org/wiki/Meetings/Ironic_v2_API All who are interested are welcome to join. By the way, we wouldn't min

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

On Thu, Jun 16, 2016 at 11:12:31AM -0400, 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 cor

Re: [openstack-dev] [Ironic] Grenade non-voting test results

On Fri, Jun 17, 2016 at 08:23:05PM +, Jay Faulkner wrote: > +1 lets get it voting. Feel free to add me as a reviewer to the > project-config patch to make the change if you want me to vote officially :). Agree. I did the thing :) https://review.openstack.org/#/c/331422/1 // jim > > > Tha

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

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, and he's getting good with Python. He's given great reviews for

[openstack-dev] [ironic] June 20 meeting cancelled

Hey all, The weekly ironic meeting for June 20 will be cancelled because it overlaps with our midcycle. Join the midcycle instead. :) We'll resume our normal schedule on June 27. // jim __ OpenStack Development Mailing List

[openstack-dev] [ironic] Midcycle reminder

Hi all, Just a reminder that our midcycle is next week! Details are here: https://wiki.openstack.org/wiki/VirtualSprints#Ironic_Virtual_Newton_Midcycle https://wiki.openstack.org/wiki/Sprints#Future_sprints_for_Newton Etherpad: https://etherpad.openstack.org/p/ironic-newton-midcycle Please add

[openstack-dev] [ironic] Launchpad permissions

Hi all, This morning I did a quick audit of the launchpad projects for our various projects, and found some projects that have some incorrect permissions/ownership things. Can the current maintainers of these projects please change the "driver" and "maintainer" fields on the home page to "ironic-d

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

On Fri, Jun 10, 2016 at 12:35:43PM -0700, Devananda van der Veen wrote: > 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 disc

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

l help us > land these and see it at work. The first of these is merged, which gets us most of what we needed. Thanks everyone for your hard work on this! /me rechecks some things waiting for this testing :D // jim > > Thanks in advance, > Jay Faulkner > OSIC > > On 6/9/16

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

On Thu, Jun 09, 2016 at 06:17:56PM +0100, Lucas Alvares Gomes wrote: > Hi, > > Thanks for writing it down Jim. > > > So, I've been thinking about this quite a bit. We've also talked about > > doing a v2 API (as evil as that may be) in Ironic here and there. We've > > had lots of lessons learned f

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

On Thu, Jun 09, 2016 at 06:17:56PM +0100, Lucas Alvares Gomes wrote: > Hi, > > Thanks for writing it down Jim. > > > So, I've been thinking about this quite a bit. We've also talked about > > doing a v2 API (as evil as that may be) in Ironic here and there. We've > > had lots of lessons learned f

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

> >1.)Nova<-> ironic interactions are generally seem terrible? > I don't know if I'd call it terrible, but there's friction. Things that > are unchangable on hardware are just software configs in vms (like mac > addresses, overlays, etc), and things that make no sense in VMs are > >

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

Hi friends, We're two patches away from having grenade passing in our check queue! This is a huge step forward for us, many thanks go to the numerous folks that have worked on or helped somehow with this. I'd love to push this across the line today as it's less than 10 lines of changes between th

Re: [openstack-dev] [ironic] Virtual midcycle date poll

, Jun 06, 2016 at 11:10:19AM -0400, Jim Rollenhagen wrote: > By the way, I created an etherpad for the midcycle to start bringing in > ideas. You know what to do. :) > > https://etherpad.openstack.org/p/ironic-newton-midcycle > > // jim > > On Wed, Jun 01, 2016 at 02:4

Re: [openstack-dev] Got Failure:"fixtures._fixtures.timeout.TimeoutException"

On Wed, Jun 08, 2016 at 01:29:49AM -0700, Clark Boylan wrote: > On Tue, Jun 7, 2016, at 10:40 PM, zhangshuai wrote: > > Hi all > > > > I have a question with fixtures._fixtures.timeout.TimeoutException. like > > following: > > > > > > > > > > Traceback (most recent call last): > > > > File

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

On Wed, Jun 08, 2016 at 10:39:20AM +, Sam Betts (sambetts) wrote: > > > On 07/06/2016 23:59, "Kris G. Lindgren" > mailto:klindg...@godaddy.com>> wrote: > > Replying to a digest so sorry for the copy and pastes > > > >> There's also been discussion of ways we could do ad-hoc changes in

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On Tue, Jun 07, 2016 at 03:10:24PM +0100, Daniel P. Berrange wrote: > On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote: > > On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote: > > > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: > &

Re: [openstack-dev] [ironic] Trello board

On Fri, Jun 03, 2016 at 07:50:42PM +, Tristan Cacqueray wrote: > On 06/03/2016 07:08 PM, Jim Rollenhagen wrote: > > On Fri, Jun 03, 2016 at 06:29:13PM +0200, Alexis Monville wrote: > >> Hi, > >> > >> On Fri, Jun 3, 2016 at 5:39 PM, Jim Rol

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

Thanks for getting to this before me, Deva. Saved me some typing. :) A little more color inline. On Mon, Jun 06, 2016 at 05:01:04PM -0700, Devananda van der Veen wrote: > > On 06/06/2016 01:44 PM, Kris G. Lindgren wrote: > > Hi ironic folks, > > As I'm trying to explore how GoDaddy can use ironi

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote: > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: > > > Hello all, > > > > At Rackspace we're running into an interesting problem: Consider a user > > who boots an instance in Nova with an image which only supports SSH > > public-ke

Re: [openstack-dev] [ironic] Virtual midcycle date poll

By the way, I created an etherpad for the midcycle to start bringing in ideas. You know what to do. :) https://etherpad.openstack.org/p/ironic-newton-midcycle // jim On Wed, Jun 01, 2016 at 02:45:33PM -0400, Jim Rollenhagen wrote: > On Thu, May 19, 2016 at 09:25:18AM -0400, Jim Rollenha

Re: [openstack-dev] [ironic] Trello board

On Fri, Jun 03, 2016 at 06:29:13PM +0200, Alexis Monville wrote: > Hi, > > On Fri, Jun 3, 2016 at 5:39 PM, Jim Rollenhagen > wrote: > > Hey all, > > > > Myself and some other cores have had trouble tracking our priorities > > using Launchpad and friends,

[openstack-dev] [ironic] Trello board

Hey all, Myself and some other cores have had trouble tracking our priorities using Launchpad and friends, so we put together a Trello board to help us track it. This should also help us focus on what to review or work on. https://trello.com/b/ROTxmGIc/ironic-newton-priorities Some notes on this

Re: [openstack-dev] [ironic] Virtual midcycle date poll

On Thu, May 19, 2016 at 09:25:18AM -0400, Jim Rollenhagen wrote: > Hi Ironickers, > > We decided in our last meeting that the midcycle for Newton will again > be virtual. Now, we need to choose a date. Please indicate which options > work for you (more than one may be selec

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

On Wed, May 25, 2016 at 07:27:09AM -0400, Jim Rollenhagen wrote: > On Wed, May 25, 2016 at 01:58:18PM +0900, Yuiko Takada wrote: > > Hi! > > > > Hironori, Lucas, thank you for bringing this topic up! > > > > Yes, as Lucas says, our latest spec is > >

Re: [openstack-dev] [ironic][neutron] bonding?

On Tue, May 24, 2016 at 12:18:40PM -0700, Armando M. wrote: > On 24 May 2016 at 04:51, Jim Rollenhagen wrote: > > > Hi, > > > > There's rumors floating around about Neutron having a bonding model in > > the near future. Are there any solid plans for that

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

On Wed, May 25, 2016 at 01:58:18PM +0900, Yuiko Takada wrote: > Hi! > > Hironori, Lucas, thank you for bringing this topic up! > > Yes, as Lucas says, our latest spec is > https://review.openstack.org/#/c/319505 > > I and Tien, Hironori, Akira discussed and merged our idea. > > And new Nova sp

[openstack-dev] [ironic][neutron] bonding?

Hi, There's rumors floating around about Neutron having a bonding model in the near future. Are there any solid plans for that? For context, as part of the multitenant networking work, ironic has a portgroup concept proposed, where operators can configure bonding for NICs in a baremetal machine.

[openstack-dev] [ironic] No meeting next monday, May 30

Hi team, There's a US holiday next Monday (May 30) and as such I'm cancelling the corresponding weekly ironic meeting. See you all the following week. // jim __ OpenStack Development Mailing List (not for usage questions) U

Re: [openstack-dev] [ironic] process for making decisions?

On Thu, May 19, 2016 at 02:02:32PM +, Loo, Ruby wrote: > Hi, > > I think it would be good if we came up with some general guidelines wrt the > processes by which decisions are made. By ³decisions², I mean decisions that > we, as a community, will try to abide by ? > > I have noticed in the

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

On Thu, May 19, 2016 at 01:21:35PM -0700, Devananda van der Veen wrote: > 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 t

[openstack-dev] [ironic] Virtual midcycle date poll

Hi Ironickers, We decided in our last meeting that the midcycle for Newton will again be virtual. Now, we need to choose a date. Please indicate which options work for you (more than one may be selected): http://doodle.com/poll/gpug7ynd9fn4rdfe I'll close this poll two Mondays from now, May 30.

Re: [openstack-dev] [heat] [grenade] need for a testing phase?

On Thu, May 12, 2016 at 02:50:03PM -0400, Sean Dague wrote: > I just discovered this - > https://github.com/openstack/heat/blob/fed92fdd6e5a14ea658621375e528f1c0cbde944/devstack/upgrade/resources.sh#L41 > in looking at why - https://review.openstack.org/#/c/315501/ did not > pass on gate-grenade-ds

Re: [openstack-dev] [ironic] Midcycle: virtual or physical?

weekly ironic > meeting :) > > ‹ruby > > > > On 2016-05-09, 6:24 PM, "Jim Rollenhagen" wrote: > > >Hey all, > > > >In this morning's meetings we discussed having a virtual midcycle again > >this cycle, versus a physical midcycle. >

Re: [openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

reate some resources to persist across upgrades (this ensures we don't break existing resources when upgrading) * upgrade to $new * run more tempest tests We can't just skip the resource create phase here. // jim > > On Thu, May 12, 2016 at 12:53 AM, Jim Rollenhagen > wrot

Re: [openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

On Thu, May 12, 2016 at 06:48:02AM -0400, Sean Dague wrote: > On 05/11/2016 05:53 PM, Jim Rollenhagen wrote: > > I've ran into a bit of a wedge working on ironic grenade tests. > > > > In a normal dsvm run, the ironic setup taps the control plane into the > > te

[openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

I've ran into a bit of a wedge working on ironic grenade tests. In a normal dsvm run, the ironic setup taps the control plane into the tenant network (as that's how it's currently intended to be deployed). That code is here[0]. However, in a grenade run, during the resource create phase, a new ne

<    1   2   3   4   5   >