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

[Loo, Ruby]

Hey Vasyl,

Thanks for all your contributions to Ironic! I hope that you'll still find a 
bit of time for us :-)

--ruby

From: Vasyl Saienko 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 23, 2018 at 9:02 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] Stepping down from Ironic core

Hey Ironic community!

Unfortunately I don't work on Ironic as much as I used to any more, so i'm
stepping down from core reviewers.

So, thanks for everything everyone, it's been great to work with you
all for all these years!!!




Sincerely,
Vasyl Saienko
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] team dinner at Dublin PTG?

[Loo, Ruby]

Hi ironic-ers,

Planning for the Dublin PTG has started. And what's the most important thing 
(and most fun event) to plan for? You got it, the team dinner! We'd like to get 
an idea of who is interested and what evening works for all or most of us.

Please indicate which evenings you are available, at this doodle: 
https://doodle.com/poll/d4ff6m9hxg887n9q

If you're shy or don't want to use doodle, send me an email.

Please respond by Friday, Feb 16 (same deadline as PTG topics-for-discussion), 
so we can find a place and reserve it.

Thanks!
--ruby

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Nominating Hironori Shiina for ironic-core

[Loo, Ruby]

+1 from me. He's been really helpful with the boot-from-volume and rescue work. 
Looking forward to Hironori joining us :)

Thanks Julia, for bringing this up!

--ruby

On 2018-02-05, 1:12 PM, "Julia Kreger"  wrote:

I would like to nominate Hironori Shiina to ironic-core. He has been
working in the ironic community for some time, and has been helping
over the past several cycles with more complex features. He has
demonstrated an understanding of Ironic's code base, mechanics, and
overall community style. His review statistics are also extremely
solid. I personally have a great deal of trust in his reviews.

I believe he would make a great addition to our team.

Thanks,

-Julia

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] FFE - Implementation for UEFI iSCSI boot for iLO drivers

[Loo, Ruby]

+1. This seems minimal risk.

--ruby

From: Debayan Ray 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, January 24, 2018 at 2:36 AM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [ironic] FFE - Implementation for UEFI iSCSI boot for 
iLO drivers

Requesting FFE for firmware based iSCSI boot from volume support in iLO
---

# Pros
--
With the patches up for review[0] we have implemented firmware based iSCSI
boot from volume for iLO hardware.

This functionality will allow users to take advantage of iLO BMC based boot
from volume, as UEFI firmware 1.40 or higher in HPE Gen9 and Gen10 ProLiant
hardware supports booting from iSCSI volume.

The change adds the feature to the iLO drivers feature set and does not have
any impact on the existing functionalities of iLO driver.

# Cons
--
None

# Risks
---
None

# Reason of delay
-
This feature required new version of proliantutils (2.5.0), which got released
last week

# Core reviewers

Julia Kreger, Shivanand Tendulker

[0] https://review.openstack.org/#/c/468288/


Thanks & Regards,
Debayan Ray (on behalf of Paresh Sao)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] FFE - classic drivers deprecation

[Loo, Ruby]

+1 :)

I'm also +1 on amending our FFE rules so that the PTL can get a FFE on one 
thing of their desire, regardless of anyone disagreeing, as long as they have 
two cores that are willing to review. As a small thank-you for being PTL! :D 
(I'm serious even though I just thought of this.)

--ruby

On 2018-01-23, 5:23 AM, "Dmitry Tantsur"  wrote:

Hi all,

I'm writing to request an FFE for the classic drivers deprecation work 
[1][2]. 
This is a part of the driver composition reform [3] - the effort started in 
Ocata to revamp bare metal drivers.

The following changes are in scope of this FFE:
1. Provide an automatic migration to hardware types as part of 
'ironic-dbsync 
online_data_migrations'
2. Update the CI to use hardware types
3. Issue a deprecation warning when loading classic drivers, and deprecate 
enabled_drivers option.

Finishing it in Queens will allow us to stick to our schedule (outlined in 
[1]) 
to remove classic drivers in Rocky. Keeping two methods of loading drivers 
is a 
maintenance burden. Even worse, two sets of mostly equivalent drivers 
confuse 
users, and the confusion well increase as we introduce features (like 
rescue) 
that are only available for nodes using the new-style drivers.

The downside of this work is that it introduces a non-trivial data 
migration 
close to the end of the cycle. Thus, it is designed [1][2] to not fail if 
the 
migration cannot fully succeed due to environmental reasons.

rloo and stendulker were so kind to agree to review this work during the 
feature 
freeze window, if it gets an exception.

Dmitry

[1] 

http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/classic-drivers-future.html
[2] https://review.openstack.org/536298
[3] 

http://specs.openstack.org/openstack/ironic-specs/specs/7.0/driver-composition-reform.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] FFE request for node rescue feature

[Loo, Ruby]

+1 (and thx Dmitry and Julia for reviewing!)

--ruby

On 2018-01-23, 5:15 AM, "Dmitry Tantsur"  wrote:

I'm +1 on this, because the feature has been proposed for a while (has 
changed 
the contributor group at least once) and is needed for feature parity with 
virtual machines in nova.

On 01/23/2018 06:56 AM, Shivanand Tendulker wrote:
> Hi
> 
> The rescue feature [1] is an high priority for ironic in Queens. The spec 
for 
> the same was merged in Newton. This feature is necessary for users that 
lose 
> regular access to their machine (e.g. lost passwords).
> 
> Landing node rescue feature late in the cycle will lead to less time 
being 
> available for testing, with a risk that the feature being released with 
defects. 
> The code changes are fairly isolated from existing code to ensure it does 
not 
> cause any regression. The Ironic side rescue code patches are all in 
review [2], 
> and are now are getting positive reviews or minor negative feedback.
> 
> dtantsur and TheJulia have kindly agreed to review the same during the 
FFE window.
> 
> [1] 
> 
https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/implement-rescue-mode.html
> [2] 
> 
https://review.openstack.org/#/q/topic:bug/1526449+(status:open+AND+project:openstack/ironic)
> 
> Thanks and Regards,
> Shiv (stendulker)
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] FFE request for node traits

[Loo, Ruby]

+1 :)

On 2018-01-23, 5:04 AM, "Dmitry Tantsur"  wrote:

+1 on keeping moving forward with it. that's important for future nova 
work, as 
well as our deploy steps work.

On 01/22/2018 10:11 PM, Mark Goddard wrote:
> The node traits feature [1] is an essential priority for ironic in 
Queens, and 
> is an important step in the continuing evolution of scheduling enabled by 
the 
> placement API. Traits will allow us to move away from capability-based 
> scheduling. Capabilities have several limitations for scheduling 
including 
> depending on filters in nova-scheduler rather than allowing placement to 
select 
> matching hosts. Several upcoming features depend on traits [2].
> 
> Landing node traits late in the cycle will lead to less time being 
available for 
> testing, with a risk that the feature is release with defects. There are 
changes 
> at most major levels in the code except the drivers, but these are for 
the most 
> part fairly isolated from existing code. The current issues with the 
grenade CI 
> job mean that upgrade code paths are not being exercised frequently, and 
could 
> lead to additional test/bug fix load on the team later in the cycle. The 
node 
> traits code patches are all in review [3], and are now generally getting 
> positive reviews or minor negative feedback.
> 
> rloo and TheJulia have kindly offered to review during the FFE window.
> 
> [1] 
> 
http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/node-traits.html
> [2] 
> 
https://review.openstack.org/#/c/504952/7/specs/approved/config-template-traits.rst
> [3] https://review.openstack.org/#/q/topic:bug/1722194+(status:open)
> 
> Thanks,
> Mark (mgoddard)
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Thanks for bringing it up John. I totally forgot about that. Not only are the 
samples in the docs, there is a link in those docs so that the sample can be 
downloaded as a file. Also, for a patch that modifies the configs, you can see 
the rendered file(s) via the generated docs. PROFIT! :)

+1.

--ruby

Now to deal with the "" in our config file... grumble, 
grumble...

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, January 22, 2018 at 3:55 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: 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://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/policy.json.sample
http://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/ironic.conf.sample
http://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/policy.json

And in a similar way:
http://git.openstack.org/cgit/openstack/ironic-inspector/tree/policy.yaml.sample
http://git.openstack.org/cgit/openstack/ironic-inspector/tree/example.conf

There is an argument that says we shouldn't force operators to build a full 
environment to generate these, but this has been somewhat superseded by us 
having good docs:

https://docs.openstack.org/ironic/latest/configuration/sample-config.html
https://docs.openstack.org/ironic/latest/configuration/sample-policy.html
https://docs.openstack.org/ironic-inspector/latest/configuration/sample-config.html
https://docs.openstack.org/ironic-inspector/latest/configuration/sample-policy.html

It could look something like this (but with the tests working...):
https://review.openstack.org/#/c/536349

What do you all think?

Thanks,
johnthetubaguy

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] FFE - Requesting FFE for Routed Networks support.

[Loo, Ruby]

/me +1 too.

--ruby

On 2018-01-17, 10:05 AM, "Dmitry Tantsur"  wrote:

Hi!

I'm essentially +1 on granting this FFE, as it's a low-risk work for a 
great 
feature. See one comment inline.

On 01/17/2018 10:54 AM, Harald Jensås wrote:
> Requesting FFE for Routed Network support in networking-baremetal.
> ---
> 
> 
> # Pros
> --
> With the patches up for review[7] we have a working ml2 agent;
> __depends on neutron fix__; and mechanism driver combination that
> enables support to bind ports on neutron routed networks.
> 
> Specifically we report the bridge_mappings data to neutron, which
> enable the _find_candidate_subnets() method in neutron ipam[1] to
> succeed in finding a candidate subnet available to the ironic node when
> ports on routed segments are bound.
> 
> This functionality will allow users to take advantage of the
> functionality added in DHCP Agent[2] which enables the DHCP agent to
> service other subnets on the network via DHCP relay. For Ironic this
> means we can support deploying nodes on a remote L3 network, e.g
> different datacenter or different rack/rack-row.
> 
> 
> 
> # Cons
> --
> Integration with placement does not currently work.
> 
> Neutron uses Nova host-aggregates in combination with Placement.
> Specifically hosts are added to a host-aggregate for segments based on
> SEGMENT_HOST_MAPPING. Ironic nodes cannot currently be added to host-
> aggregates in Nova. Because of this the following will appear in the
> neutron logs when ironic-neutron agent is started:
> RESP BODY: {"itemNotFound": {"message": "Compute host  id> could not be found.", "code": 404}}
> 
> Also the placement api cannot be used to find good candidate ironic
> nodes with a baremetal port on the correct segment. This will have to be 
worked around by the operator via capabilities and flavor properties or manual 
additions to resource providers in placement.
> 
> Depending on the direction of other projects, neutron and nova, the way
> placement will finally work is not certain.
> 
> Either the nova work [3] and [4], or a neutron change to use placement
> only or a fallback to placement in neutron would be possible. In either
> case there should be no need to change the networking-baremetal agent
> or mechanism driver.
> 
> 
> # Risks
> ---
> Unless this bug[5] is fixed we might break the current baremetal
> mechanism driver functionality. I have proposed a patch[6] to neutron
> that fix the issue. In case no fix lands for this neutron bug soon we
> should probably push these changes to Rocky.

Let's add Depends-On to the first patch in the chain to make sure your 
patches 
don't merge until the fix is merged.

> 
> 
> # Core reviewers
> 
> Julia Kreger, Sam Betts
> 
> 
> 
> 
> [1] https://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/ip
> am_backend_mixin.py#n697
> [2] https://review.openstack.org/#/c/468744/
> [3] https://review.openstack.org/#/c/421009/
> [4] https://review.openstack.org/#/c/421011/
> [5] https://bugs.launchpad.net/neutron/+bug/1743579
> [6] https://review.openstack.org/#/c/534449/
> [7] https://review.openstack.org/#/q/project:openstack/networking-barem
> etal
> 
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Please ignore this; we didn't have a weekly meeting (because we had our 
midcycle virtual meet up instead).

--ruby

From: "Yeleswarapu, Ramamani" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, November 27, 2017 at 5:29 PM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [ironic] this week's priorities and subteam reports

Hi,

We are glad to present this week's priorities and subteam report for Ironic. As 
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. Midcycle planning: https://etherpad.openstack.org/p/ironic-queens-midcycle
2. Use adapters for cinderclient: https://review.openstack.org/#/c/476171/ 
MERGED
2.1. then also for inspector client: 
https://review.openstack.org/#/c/476172/ MERGED
3. install guide update for hw types: https://review.openstack.org/#/c/517290/
3.1. before that, separate pages for deploy and boot interfaces: 
https://review.openstack.org/#/c/517632/
4. BIOS interface spec: https://review.openstack.org/#/c/496481/
5. Rescue:
5.1. driver interface https://review.openstack.org/#/c/509335/
5.2. RPC https://review.openstack.org/#/c/509336/
5.3. rescuewait timeout https://review.openstack.org/#/c/353156

Vendor priorities
-
cisco-ucs:
Patchs in works for SDK update, but not posted yet, currently rebuilding 
third party CI infra after a disaster...
idrac:

ilo:
https://review.openstack.org/207337 - Out-of-band Boot from UEFI iSCSI 
volume for HPE Proliant server
irmc:
SPEC to add a new hardware type for another FUJITSU server: PRIMEQUEST MMB:
  https://review.openstack.org/#/c/515717/ MERGED

oneview:
Add validations for OneView ML2 driver -  
https://review.openstack.org/#/c/508946/

Subproject priorities
-
bifrost:
ironic-inspector (or its client):
  - dnsmasq-based inspector PXE filter driver: 
https://review.openstack.org/#/c/466448/ TL;DR: replaces iptables with a 
dynamic configuration of dnsmasq (pretty cool thing too ;)
- folks might consider trying the test patch to experiment manually with 
this https://review.openstack.org/#/c/468712/54
networking-baremetal:
neutron baremetal agent https://review.openstack.org/#/c/456235/
sushy and the redfish driver:
(dtantsur) implement redfish sessions: 
https://review.openstack.org/#/c/471942/

Bugs (dtantsur, vdrok, TheJulia)

- Stats (diff between 13 Nov 2017 and 20 Nov 2017)
- Ironic: 219 bugs (-4) + 254 wishlist items (+7). 11 new (-2), 153 in progress 
(+2), 0 critical, 31 high and 35 incomplete (+1)
- Inspector: 16 bugs + 31 wishlist items. 0 new (-2), 16 in progress, 0 
critical, 4 high and 5 incomplete (+2)
- Nova bugs with Ironic tag: 14 (+1). 2 new (+1), 0 critical, 1 high
- HIGH bugs with patches to review:
- Clean steps are not tested in gate 
https://bugs.launchpad.net/ironic/+bug/1523640: Add manual clean step ironic 
standalone test https://review.openstack.org/#/c/429770/15
- prepare_instance() is not called for whole disk images with 'agent' deploy 
interface https://bugs.launchpad.net/ironic/+bug/1713916:
- Fix to return 'root_uuid' as part of command status 
https://review.openstack.org/#/c/500719/4
- Fix ``agent`` deploy interface to call ``boot.prepare_instance`` 
https://review.openstack.org/#/c/499050/
- If provisioning network is changed, Ironic conductor does not behave 
correctly https://bugs.launchpad.net/ironic/+bug/1679260: Ironic conductor 
works correctly on changes of networks: https://review.openstack.org/#/c/462931/
- (rloo) needs some direction

CI refactoring and missing test coverage

- not considered a priority, it's a 'do it always' thing
- Standalone CI tests (vsaienk0)
- next patch to be reviewed, needed for 3rd party CI: 
https://review.openstack.org/#/c/429770/
- localboot with partitioned image patches:
- IPA - build tinycore based partitioned image with grub 
https://review.openstack.org/#/c/504888/
- Ironic - add localboot partitioned image test: 
https://review.openstack.org/#/c/502886/
- when previous are merged TODO (vsaienko)
- Upload tinycore partitioned image to tarbals.openstack.org
- Switch ironic to use tinyipa partitioned image by default
- Missing test coverage (all)
- portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476
- adoption: https://review.openstack.org/#/c/344975/
- should probably be changed to use standalone tests
- root device hints: TODO
- node take over
- resource classes integration tests: 
https://review.openstack.org/#/c/443628/

Essential Priorities


Ironic 

[openstack-dev] [ironic] zuul v3 migration: legacy jobs in tree

[Loo, Ruby]

Hi,

As part of the zuul v3 migration, we are *almost* done with moving all of 
ironic projects' legacy jobs in-tree. Thanks to Pavlo Shchelokovskyy for 
starting the etherpad to track this [1] and thanks to everyone that chipped in 
to help!

What are the next steps/things to do? Just thinking out loud here:
- people update the etherpad [1] (we'll use that for now) with other things we 
should/want to do
- we decide on which and the order
- volunteers make-it-happen

Given the number of ironic projects that we have, I think it was really useful 
to have someone take the lead and "manage" the effort, so that we didn't miss 
any projects, that the changes were consistent, and that they were done in a 
timely fashion. (Let's not forget the fun factor!) This would be a good thing 
to do as we continue to make more changes to our CI jobs.

For now, please update the etherpad [1] with things that we should do; 
hopefully we can go over them in our next weekly meeting.

Thanks!
--ruby

[1] https://etherpad.openstack.org/p/ironic-zuulv3-intree-tracking 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] [Openstack-operators] replace node "tags" with node "traits"

[Loo, Ruby]

Hello ironic'ers,

A while ago, we approved a spec to add node tag support to ironic [1]. The 
feature itself did not land yet (although some of the code has). Now that the 
(nova) community has come up with traits, ironic wants to support node traits, 
and there is a spec proposing that [2]. At the ironic node level, this is VERY 
similar to the node tag support, so the thought is to drop (not implement) the 
node tagging feature, since the node traits feature could be used instead. 
There are a few differences between the tags and traits. "Traits" means 
something in OpenStack, and there are some restrictions about it:
- max 50 per node
- names must be one of those in os-traits library OR prefixed with 'CUSTOM_'

For folks that wanted the node tagging feature, will this new node traits 
feature work for your use case? Should we support both tags and traits? I was 
wondering about e.g. using ironic standalone.

Please feel free to comment in [2].

Thanks in advance,
--ruby

[1] 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/nodes-tagging.html
[2] https://review.openstack.org/#/c/504531/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Proposing Shivanand Tendulker for ironic-core

[Loo, Ruby]

+1, Thx Dmitry for the proposal and Shiv for doing all the work :D

--ruby

From: Dmitry Tantsur 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, October 2, 2017 at 10:17 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] Proposing Shivanand Tendulker for ironic-core

Hi all!
I would like to propose Shivanand (stendulker) to the core team.

His stats have been consistently high [1]. He has given a lot of insightful 
reviews recently, and his expertise in the iLO driver is also very valuable for 
the team.
As usual, please respond with your comments and objections.
Thanks,
Dmitry

[1] http://stackalytics.com/report/contribution/ironic-group/90
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] code patches & bugs

[Loo, Ruby]

Hi,

Just a reminder to make sure that if you are submitting a code patch to fix 
something that could be apparent to our users, that it should be considered a 
bug (or a feature). Which means that there should be a launchpad bug [1] 
associated with it, and a release note.

I know we've been fairly lax about that in the past and I know that it is yet 
more-stuff-to-do-just-to-fix-something. However, we (I) just encountered a case 
where we are backporting a patch that did not originally have a bug associated 
with it nor a release note :-(

Thanks!
--ruby

[1] https://bugs.launchpad.net/ironic
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic][docs] I see, you see, we all see red*

[Loo, Ruby]

Hi,

In case folks wonder what happened, I submitted a patch [1] to change it to 
black :)

--ruby

[1] https://review.openstack.org/#/c/505348/


From: Ruby Loo 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, August 24, 2017 at 11:19 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [ironic][docs] I see, you see, we all see red*

Hi Alex,

Sorry, I don't know much about the docs stuff; Andreas' links were useful for 
enlightening me.

Clearly, I'm biased and would prefer no difference in colour. What about that 
(darker?) blue from [0], where it sez (I'm referring to the upper-cased words 
here) 'Modern color theory uses either the ... RED-CYAN, GREEN-MAGENTA, 
BLUE-YELLOW'. Would that blue clash with the blue you are mentioning? (Well, 
maybe it is the bold + blue that I like, not just the blue.)

I don't really think a complementary colour is good, orange is marginally 
better than red. I'd like it to be highlighted but I guess I like subtle, not 
strong.

Having said all that, I'm a reader/viewer of these documents and this is *just* 
my opinion. It seems to me that there might be research into what works best? 
Anyone know?

Thanks,
--ruby

On Thu, Aug 24, 2017 at 6:19 AM, Alexandra Settle 
> wrote:
Hey Ruby!

Good point – thanks for bringing it up :)

I was brought up to think that red was one of those colours that people had 
different (and sometimes really negative) associations with. When I look at our 
latest and greatest! ironic documentation (e.g. [1]), I see red. Not only do I 
see red, but the term has a different background colour and is bordered (or 
whatever it is called). Are we using the wrong .rst syntax, should we be 
highlighting terms differently? And/or is there some way to change the 
appearance of highlighted terms? I much prefer something simple, like bold 
black text in some uniform font. On the other hand, perhaps lots of others like 
this and I'm in the minority.

Andreas is right – the red definitely correct, and this is how we have always 
done it in manuals. But that doesn’t mean we have to continue. We just need to 
come up with another strong, inoffensive colour that matches; I believe the red 
was chosen to simply contrast the blue. A compromise, and complementary 
colour[0], would be orange. How would you feel about this?

I hesitated about sending this due to the wonderful bike shedding that could 
happen, don't disappoint me, cuz I'm sure we all have opinions about colour. :)

Not going to lie, also afraid of all the bike shedding! But you bring up a good 
point – and I don’t want others to also feel negatively about our 
documentation. We should be as inclusive as we can.

Also, this email thread isn't about discussing the green and orange colours 
used for the code blocks; feel free to start your own thread about that if you 
want!

No thanks, if I can avoid it :P

Cheers,

Alex

[0] https://en.wikipedia.org/wiki/Complementary_colors

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic][docs] I see, you see, we all see red*

[Loo, Ruby]

Hi,

I was brought up to think that red was one of those colours that people had 
different (and sometimes really negative) associations with. When I look at our 
latest and greatest! ironic documentation (e.g. [1]), I see red. Not only do I 
see red, but the term has a different background colour and is bordered (or 
whatever it is called). Are we using the wrong .rst syntax, should we be 
highlighting terms differently? And/or is there some way to change the 
appearance of highlighted terms? I much prefer something simple, like bold 
black text in some uniform font. On the other hand, perhaps lots of others like 
this and I'm in the minority.

I can handle the Warnings that are in red though. (I'm not sure it is necesary, 
given that it is all in a BOX with a WARNING SYMBOL.)

I hesitated about sending this due to the wonderful bike shedding that could 
happen, don't disappoint me, cuz I'm sure we all have opinions about colour. :)

Also, this email thread isn't about discussing the green and orange colours 
used for the code blocks; feel free to start your own thread about that if you 
want!

Thanks for listening,
--ruby

*unless you're colour blind

[1] https://docs.openstack.org/ironic/latest/install/enabling-drivers.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] ironic-staging-drivers core cleanup and additions

[Loo, Ruby]

I agree whether I have a vote or not ;)

Thanks Dmitry!

--ruby

From: Dmitry Tantsur 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, August 22, 2017 at 5:24 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Cc: Lucas Alvares Gomes 
Subject: [openstack-dev] [ironic] ironic-staging-drivers core cleanup and 
additions

Hi all!

This email concerns the ironic-staging-drivers project which is outside of the
official Ironic governance. Please ignore it if you don't care about this 
project.

I've checked the core [1] and the release [2] teams for the project, and I think
they need an update based (see [3]).

I suggest removing the following people:
* Dan Prince (due to inactivity)
* Lucas Alvares Gomes (due to priorities change)
* Imre Farkas (no longer works on OpenStack)

I suggest adding Pavlo Shchelokovskyy, who actively contributes to and reviews
the project, to the core team.

I've cc'ed affected people as I was a bit too lazy to reach to them on IRC :)
Please let me know your opinion.

[1] https://review.openstack.org/#/admin/groups/1258,members
[2] https://review.openstack.org/#/admin/groups/1259,members
[3] http://stackalytics.com/?module=ironic-staging-drivers=pike

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] [release] [stable] pike release

[Loo, Ruby]

Hi,

I'd like to get more information from the release folks (wrt grenade support or 
lack of, what might be reasonable or not to do, etc.), and how other OpenStack 
projects that use the same release model as ironic, do it. I think that 
whatever we do, it ought to be the easiest for all concerned; e.g.: I don't 
want to have to keep track of which patches in master need to be backported to 
the stable branch if there is going to be more than a small handful of them. 
And for users, it ought to be (somewhat) clear to them, what these releases 
are/mean.

We saw at least one issue, grenade jobs needing stable/pike branch. Were there 
others?

--ruby

From: "Sam Betts (sambetts)" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, August 21, 2017 at 6:01 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [ironic] [release] [stable] pike release

Quick reply with my thoughts in-line.

Sam

On 21/08/2017, 10:13, "Dmitry Tantsur" 
> wrote:

(adding the release and stable team just for their information)

Thanks Julia and everyone for handling this situation while I was out. More
comments inline.

On 08/17/2017 07:13 PM, Julia Kreger wrote:
> Greetings everyone!
>
> As some of you may have noticed, we released ironic 9.0.0 today. But
> wait! There is more!
>
> We triggered this release due to a number of issues, one of which was
> that we learned that we needed the stable/pike branch for our grenade
> jobs to execute properly. This was not done previously because
> Ironic’s release model is incompatible with making release candidate
> releases.

Yep :( So, I think the lesson to learn is to create our stable/XXX branch 
at the
same time as the other projects. We kind of knew that already, but did not
anticipate such a huge breakage so quickly. I suggest we don't try it in 
Queens :)

Now, with that in place we still have two options:
1. A conservative one - make the branching the hard feature freeze, similar 
to
other projects. We may start with a soft freeze at around M3, and just move 
into
Queens when stable/queens is created. As that point, what is out - is out.
2. Alternative - continue making selected feature backports until the final
freeze roughly one week before the final release. This kind of contradicts
calling a branch "stable" though.

I don't have a strong opinion, but I'm slightly more in favor of the
conservation option #1 to avoid confusing people and complicating the 
process.

Thoughts?

Personally, I think option 2 still makes sense, and it aligns us closely with 
the process in the other projects, the difference between us and them is that 
their branch is cut using a release candidate instead of a real release. The 
act of backporting things into the stable branch and then re-releasing is the 
same though.

Another alternative I wonder if we should consider is cutting our branch 
earlier in the cycle, when we make our first intermediary release, and then 
finding out if we can sync the branches at each release time instead of 
backporting everything. E.g. git checkout stable/X, git reset –hard 
origin/master or git rebase master, git push. Doing this will allow us to 
retain the git history and same commit ids from master to stable/X until master 
stops developing stable/X and moves on to stable/X+1. I think another advantage 
of this is it also allows people to find and use our latest intermediary 
releases easier. But I don’t know how nicely this would work with all the 
tooling etc the release team has in place.

>
> Once we’ve confirmed that our grenade testing is passing, we will back
> port patches we had previously approved, but that had not landed, from
> master to stable/pike.

++ I've approved a few patches already, and will continue approving them 
today.

>
> As a result, please anticipate Ironic’s official Pike release for this
> cycle to be 9.1.0, if the stars, gates, and job timeouts align with
> us.

Right, I think we will request it on Wednesday, to allow a bit more time to 
test
our newly populated not-so-stable stable/pike :)

>
> If there are any questions, please feel free to stop by
> #openstack-ironic. We have also been keeping our general purpose
> whiteboard[1] up to date, you can see our notes regarding our current
> plan starting at line 120, and notes regarding gate failures and
> issues starting at line 37.
> Thanks!
>
> -Julia
>
> [1]: https://etherpad.openstack.org/p/IronicWhiteBoard
>
> __
> OpenStack Development Mailing List (not for usage questions)
> 

Re: [openstack-dev] [ironic]HP proliant create logical drive not according to the target_raid_config

[Loo, Ruby]

Hi, I suggest either providing more information so someone may be able to help 
you here, or go onto irc, #openstack-ironic, and ask for help there.

--ruby

From: 王俊 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, July 19, 2017 at 7:55 AM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [ironic]HP proliant create logical drive not according 
to the target_raid_config

Hi,
 May I ask a question about RAID?I set target_raid_config before I set 
the node state to ‘provide’, but when I make the node to available, the 
server’s logical drive does not like my configures.I don’t know why.who can 
give some help?

保密：本函仅供收件人使用，如阁下并非抬头标明的收件人，请您即刻删除本函，勿以任何方式使用及传播，并请您能将此误发情形通知发件人，谢谢！
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] [stable] another ironic-stable-maint update proposal

[Loo, Ruby]

Definitely, +1 to add Julia. That's unanimous from the team!

How do we get you to have ACL (or do PTLs not get ACL?)

Jim Roll..., who's that guy? :-(

--ruby

From: Dmitry Tantsur 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, June 30, 2017 at 12:10 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] [stable] another ironic-stable-maint update 
proposal

Hi all!

I'd like to propose another round of changes to the ironic-stable-maint group 
[0]:

1. Add Julia Kreger (TheJulia) to the group. Julia is one of the top reviewers
in Ironic, and she is quite active on stable branches as well [1].

2. Remove Jim Rollenhagen (sigh..) as he no longer works on OpenStack.

So for those on the team already, please reply with a +1 or -1 vote.
I'll also need somebody to apply this change, as I don't have ACL for that.

[0] https://review.openstack.org/#/admin/groups/950,members
[1]
https://review.openstack.org/#/q/(project:openstack/ironic+OR+project:openstack/ironic-python-agent+OR+project:openstack/ironic-lib)+NOT+branch:master+reviewer:%22Julia+Kreger+%253Cjuliaashleykreger%2540gmail.com%253E%22

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

I was hoping that if I ignored this, it wouldn't be true. Who am I kidding... 
sigh... sob...

Good bye Jim, last of the Js (Josh, Jay) from Rackspace, thank you for IPA, for 
sacrificing yourself and being PTL, for sacrificing yourself and talking to the 
nova folks :-), and for everything else you brought to ironic!

Needless to say, I have, and will, miss you.

Good luck Jim, I know you'll go on to do great things!

--ruby


From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, June 8, 2017 at 8:45 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [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.

The last 3.5 years have been amazing. I'm extremely grateful that I've been 
able to work in this community - I've learned so much and met so many awesome 
people. I'm going to miss the insane(ly awesome) level of collaboration, the 
summits, the PTGs, and even some of the bikeshedding. We've built amazing 
things together, and I'm sure y'all will continue to do so without me.

I'll still be lurking in #openstack-dev and #openstack-ironic for a while, if 
people need me to drop a -2 or dictate old knowledge or whatever, feel free to 
ping me. Or if you just want to chat. :)

<3 jroll

P.S. obviously my core permissions should be dropped now :P
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OSC][ironic][mogan][nova] mogan and nova co-existing

[Loo, Ruby]

Hi Zhenguo (and others),

is there a description/email thread/documentation about how mogan and nova 
co-exists in the same cloud? In particular, will it be possible for mogan and 
nova (with ironic driver) to run? Is this something that we will recommend or 
not recommend or not mention? Because I don't see how the end user will know to 
issue a mogan command to get a baremetal server, vs a nova-boot command to get 
a baremetal server. And/or does anyone envison that horizon will hide all that 
from the user somehow?

--ruby

From: Zhenguo Niu 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, May 25, 2017 at 10:41 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 
'baremetal'?



As I understand, baremetal instance in nova is a 'specical virtual machine'(raw 
performance). Users claim the instance by specifying a flavor with 'vcpus', 
'memory', "root_gb" instead of real hardware specs like (cpu model/cores, hard 
drives type/amount, nics type/amount), then he get an instance with properties 
like 'vm_state' and other 'virtual' stuff. As baremetal in nova use the same 
model and same set of API that designed for vms, so even for end users, it's 
not that easy to know which instance is a baremetal server, so maybe it's good 
to call that baremetal server a special vm instance.

So, yes the end user actually know that there is a difference between getting a 
bremetal instance via mogan or via nova :)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

[Loo, Ruby]

Hi Zhenguo,

Thanks for bringing this up. Naming is hard :-(

Maybe this is a dumb question but your phrase "We copied nova's server resource 
concept here, so users may easily to accept the 'baremetal server'" made me 
wonder. I'm not a user of Mogan so I don't know if this would work, but OSC 
already has
openstack server  
openstack flavor  
openstack keypair  

Why can't we use the existing OSC commands, and add an option eg '--bm' to 
indicate that the server is baremetal, not a VM?

Of course, having asked this, how does the user know/distinguish between 
getting a baremetal instance via mogan or via nova... (and should the end user 
actually know that there is a difference...) But I suspect I am digressing.

--ruby

From: Zhenguo Niu 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, May 25, 2017 at 5:38 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 
'baremetal'?


On Thu, May 25, 2017 at 4:27 PM, Dmitry Tantsur 
> wrote:
On 05/25/2017 10:20 AM, Zhenguo Niu wrote:
hi all,

Hi!

I'm from the Mogan team, we chose the same keyward 'baremetal' when 
implementing a OSC plugin [1]. As we think the baremetal command is 
representative of a baremetal resource, not a service, so it makes sense for 
different projects to share the top level resource name that OpenStack can 
provide.

We do not "own" the word "baremetal", so nothing prevents you from using it. 
However, in my experience:
1. This does confuse users, as they expect "openstack baremetal" to be a prefix 
belonging to Ironic.
2. Collisions may happen. We had two collisions with TripleO already, one 
resulted in us killing a TripleO command abruptly.

Alternatively, I don't mind to change this to 'bm' or something like that for 
Mogan, but some operators told me that it will confuse users more to have both 
'baremetal' and 'bm' in there CLI.
And as I understand, ironic commands are not used frequently, and it's even 
less if ironic inspector can help to automatically enroll nodes/ports.



The commands we have implemented are listed below, seems there's no collision 
with Ironic presently, and Ironic doesn't manage such resources.

* openstack baremetal server  
* openstack bareemtal flavor  
* openstack baremetal keypair  
* openstack baremetal availability zone  

Ironic does not have any notion of either of these, so it should be fine.

I'm still a bit on a -1 side because of potential users confusion. I wonder how 
can we send a message across that prefixes do not designate a specific project, 
but are rather just part of a "sentence". I'm specifically worried about 
confusing "baremetal server" of Mogan with "baremetal node" of Ironic. For many 
people these can be synonyms.

We copied nova's server resource concept here, so users may easily to accept 
the 'baremetal server'. For 'baremetal node', seems only 
operators/administrators may use such commands, so seems the synonyms is not a 
big problem as they are for different roles.


So, we'd like to ask if our CLI pattern is allowed before we release the client.

Thanks in advance!


[1] https://github.com/openstack/python-moganclient

--
Best Regards,
Zhenguo Niu


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Best Regards,
Zhenguo Niu
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi Lucas,

This is a big loss for our community (but lucky OVS/OVN projects!) It has been 
awesome to work with you over the years. I'll always treasure the friendship we 
have! I know you're still around but it won't be the same; I'll miss you :-(

So long core, and thanks for the fish, although Pixie Boots might be your 
biggest legacy ;)
--ruby

From: Lucas Alvares Gomes 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, May 9, 2017 at 10:15 AM
To: OpenStack Development Mailing List 
Subject: [openstack-dev] [Ironic] Stepping down from core

Hi all,

This is a difficult email to send. As some of you might already know,
lately I've been focusing on the OVS/OVN (and related) projects and I
don't have much time left to dedicate on reviewing patches in Ironic,
at least for now.

My biggest priority for this cycle was to create a basic Redfish
driver and now that the patches are merged and a -nv job is running in
the gate I feel like it would be a good time to step down from the
core team. If needed, I could still help out as core reviewer on some
small projects which I'm very familiar with such as Sushy and
VirtualBMC, those doesn't take much time and the review queue is
usually short.

Also, this is not a good-bye email, I'm still very interested in
Ironic and I will continue to follow the project closely as well as be
around in the #openstack-ironic IRC channel at all times (-:

So, thanks for everything everyone, it's been great to work with you
all for all these years!!!

Cheers,
Lucas

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] [stable] ironic-stable-maint update proposal

[Loo, Ruby]

+1 to all and more sighs.

I wish I didn't have to be added. Can't we make people stay? :)

--ruby

From: Julia Kreger 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, April 27, 2017 at 5:57 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [ironic] [stable] ironic-stable-maint update 
proposal

On Thu, Apr 27, 2017 at 10:21 AM, Dmitry Tantsur 
> wrote:

1. Add Ruby Loo (rloo) to the group.

+1

2. Remove Jay Faulkner (sigh..) per his request at [2].

+1 to the sigh.


3. Remove Devananda (sigh again..)
+1 *more sighs*

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Goodbye ironic o/

[Loo, Ruby]

Hi Mario,

I will miss you; good luck!

So long and thanks for all the metrics :)

--ruby

From: Mario Villaplana 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, April 28, 2017 at 12:12 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] Goodbye ironic o/

Hi ironic team,

You may have noticed a decline in my upstream contributions the past few weeks. 
Unfortunately, I'm no longer being paid to work on ironic. It's unlikely that 
I'll be contributing enough to keep up with the project in my new job, too, so 
please do feel free to remove my core access.

It's been great working with all of you. I've learned so much about open 
source, baremetal provisioning, Python, and more from all of you, and I will 
definitely miss it. I hope that we all get to work together again in the future 
someday.

I am not sure that I'll be at the Forum during the day, but please do ping me 
for a weekend or evening hangout if you're attending. I'd love to show anyone 
who's interested around the Boston area if our schedules align.

Also feel free to contact me via IRC/email/carrier pigeon with any questions 
about work in progress I had upstream.

Good luck with the project, and thanks for everything!

Best wishes,
Mario Villaplana
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Resigning as a core reviewer

[Loo, Ruby]

Hi Jay,

I'm so SAD to see you go, especially in these circumstances :-(

The first time I met you was when you three Js waltzed (err, walked) into the 
ironic mid-cycle with your IPA proposal. It is the end of an era. We've had 
some great times; I'll miss your opinions, especially wrt specs :) Thank you so 
much for your contributions!

Good luck!
--ruby

From: Jay Faulkner 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, April 26, 2017 at 3:42 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] Resigning as a core reviewer


Hi all,



As most of you know, I'm no longer being paid to work on OpenStack Ironic. 
Working with you all has been an amazing part of my career, an I've learned 
more than you'll ever know. I'll still be in #openstack-ironic, willing to 
answer any questions about something I'm an expert in. However, as I won't be 
actively participating in the project, or reviewing code anymore, I'd like to 
request my core reviewer access be removed.



Thanks for everything! I wish for nothing but the best for everyone in the 
OpenStack community who have always treated me with kindness and patience.



Sincerely,

Jay Faulkner
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] gate status for 3rd party CI

[Loo, Ruby]

Hi,

In yesterday's meetup, we discussed how we could help 3rd party CI become all 
green (ie, not fail). One of the suggestions was to have the gate status 
available. Among other things, this would help developers know whether they 
should (or shouldn't) ignore gate failures for 3rd party CI.

We've put in place a similar process for 3rd party CIs, as we have been doing 
for ironic CIs:

1. There is a section in our main etherpad [2] for mentioning failures. 3rd 
party CI maintainers, please try to keep that up to date.
2. There is a separate etherpad [3] to capture all failures, discussions of, 
and what their resolutions were. The data should prove useful, at the very 
least, so developers know what they should be looking out for, when reviewing :)

Thanks!
--ruby

[1] https://etherpad.openstack.org/p/ironic-virtual-meetup, starting at L90
[2] https://etherpad.openstack.org/p/IronicWhiteBoard, starting around L50
[3] https://etherpad.openstack.org/p/IronicThirdPartyGateDebugging
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Thank you Heidi!

> Long live Pixie Boots!

May (s)he reign forever :D

--ruby

From: Heidi Joy Tretheway 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, April 21, 2017 at 6:02 PM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [ironic] New mascot design

Hello Ironic team,
Thanks for your comments on the last round. Here is the latest Pixie Boots 
mascot (in every variation) ready for your downloading pleasure. We’ll also be 
updating these to a public repo and to openstack.org/project-mascots, but 
please be patient as our fab web team is slammed with Summit stuff.

Here’s a quick look at the mascot:
https://www.dropbox.com/s/qf8lent6ncpq0ip/OpenStack_Project_Ironic_vertical.jpg?dl=0

And here’s a dropbox with all 10 versions:
https://www.dropbox.com/sh/w14cufsymu9hxiw/AAA5eJTW42AC-C0qPkMi4i1ra?dl=0

Long live Pixie Boots!


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] cancelled Re: [ironic] Ironic review party invitation

[Loo, Ruby]

Hi,

Effective immediately and indefinitely (or err in 10 minutes :)), the Ironic 
review parties have been cancelled. It was the best kept secret but frowned 
upon when discovered. Too much partying and drinking you know. [I am just 
kidding!]

If someone wants to resume this or do something similar in the future, please 
do so!

Thank you Mario and everyone else that attended, you all made it way too 
successful :)

--ruby

From: Mario Villaplana 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, March 20, 2017 at 11:20 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [ironic] Ironic review party invitation

Hi ironic team,

I'm proposing that we move this to 20:00 UTC Thursdays (8pm UTC, 4pm
in my timezone which is US Eastern). I think this will better fit with
the daylight saving time adjustment that most attendees had last week.
Please message me here or in IRC if there are objections. I've updated
the etherpad at https://etherpad.openstack.org/p/ironic-review-party
to reflect this new time.

I am now back from vacation and will be around for this week's review
party. Thanks to whoever led last week's review party.

Mario

On Tue, Feb 28, 2017 at 2:14 PM, Mario Villaplana
> wrote:
Hi ironic team,

Last cycle, I started holding some informal "review parties" for new
members of OSIC [0] to come together with other OSIC people who had
been working on OpenStack for a while and have group discussions about
technical topics related to ironic and generally how to be more
effective upstream community members.

People found this decently helpful, with a weighted average of 3.6
when polled for feedback on the usefulness of the event on a 1-5
scale.

As a result of some of this feedback, I thought it'd be good to invite
the whole ironic community to participate in this weekly event.

It'll now be happening Thursdays at 2100 UTC in a Google Hangouts room
so that more community members can join. Here's an etherpad with the
Hangouts link and more information about the event:
https://etherpad.openstack.org/p/ironic-review-party

This is a totally informal, unofficial event. Feel free to put any
topic you'd like to discuss with a larger audience on that etherpad in
the section for the current week. I'll be looking over whatever's on
that list 24 hours in advance of the party to get adequately prepared,
but feel free to show up with other topics, too.

Thanks!

Mario

[0] https://osic.org/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

[Loo, Ruby]

Hi Solio,

Thanks for volunteering to be the liaison for the logging working group. The 
project that are listed there, are the ones that have liaisons with the working 
group. It gives everyone an idea of which projects have liaisons. So your name 
will be added there shortly, as the ironic liaison :)

There is a section in our etherpad [1] (look for 'Cross-project'), where you 
could add anything of interest (i.e. anything from the logging working group 
that impacts ironic). We look at (and discuss) these during our weekly ironic 
meetings [2].

--ruby

[1] https://etherpad.openstack.org/p/IronicWhiteBoard
[2] https://wiki.openstack.org/wiki/Meetings/Ironic

From: "Sarabia, Solio" <solio.sara...@intel.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Monday, March 20, 2017 at 12:22 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Ruby.
I’d like to volunteer for logging, in case ironic still needs a liaison with 
this group. In the CrossProjectLiaisons wiki [1], for the logging group, only a 
few projects are listed. Does this mean that the projects listed there are the 
only needing help? Or as people volunteer, her/his name are added to the list?

Btw, I’m relatively new to ironic as well, and would like to contribute in 
areas where ironic needs help.

-Solio

From: Rushil Chugh <rch...@ncsu.edu>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Saturday, March 18, 2017 at 9:17 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Ruby,

I am still new to the Ironic project and want to get more involved. I would 
like to be the oslo project liason as this would give me an opportunity to 
become more active within the Ironic community. I have worked with multiple 
OpenStack projects in prior jobs and have a few connections within the Oslo 
community. This would give me valuable experience learning more about the Oslo 
project and I believe I have the time commitment to take this on.

Thanks,
Rushil

On Wed, Mar 15, 2017 at 11:11 AM, Loo, Ruby 
<ruby@intel.com<mailto:ruby@intel.com>> wrote:
Hi,

The ironic community is looking for volunteers to be cross-project liaisons [1] 
for these projects:
- oslo
- logging working group
- i18n

The expectations are documented in [1] on a per-project basis. The amount of 
commitment varies depending on the project (and I don't know what that might 
be).

[insert here why it would be an awesome experience for you, fame, fortune, ... 
:D]

--ruby

[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Rushil Chugh
MS - Computer Networks
North Carolina State University
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

[Loo, Ruby]

Hi Rushil,

We (or I am) are happy that you are volunteering to be the oslo project 
liaison. Thanks!

There is a section in our etherpad [1] (look for 'Cross-project'), where you 
could add anything of interest (i.e. anything from oslo that impacts ironic). 
We look at (and discuss) these during our weekly ironic meetings [2].

--ruby

[1] https://etherpad.openstack.org/p/IronicWhiteBoard
[2] https://wiki.openstack.org/wiki/Meetings/Ironic

From: Rushil Chugh <rch...@ncsu.edu>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Saturday, March 18, 2017 at 10:17 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Ruby,

I am still new to the Ironic project and want to get more involved. I would 
like to be the oslo project liason as this would give me an opportunity to 
become more active within the Ironic community. I have worked with multiple 
OpenStack projects in prior jobs and have a few connections within the Oslo 
community. This would give me valuable experience learning more about the Oslo 
project and I believe I have the time commitment to take this on.

Thanks,
Rushil

On Wed, Mar 15, 2017 at 11:11 AM, Loo, Ruby 
<ruby@intel.com<mailto:ruby@intel.com>> wrote:
Hi,

The ironic community is looking for volunteers to be cross-project liaisons [1] 
for these projects:
- oslo
- logging working group
- i18n

The expectations are documented in [1] on a per-project basis. The amount of 
commitment varies depending on the project (and I don't know what that might 
be).

[insert here why it would be an awesome experience for you, fame, fortune, ... 
:D]

--ruby

[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Rushil Chugh
MS - Computer Networks
North Carolina State University
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

[Loo, Ruby]

Hi Jay,

That makes a lot of sense and thank YOU for being the i18n liaison! :D

--ruby

On 2017-03-15, 11:18 AM, "Jay Faulkner" <j...@jvf.cc> wrote:


> On Mar 15, 2017, at 8:11 AM, Loo, Ruby <ruby@intel.com> wrote:
> 
> Hi,
> 
> The ironic community is looking for volunteers to be cross-project 
liaisons [1] for these projects:
> - oslo
> - logging working group
> - i18n

The i18n and docs projects are closely related. I also don’t think they do 
a lot of translating for ironic. Unless we have a contributor who utilizes i18n 
and is more familiar, I can take this on.

-Jay
> 
> The expectations are documented in [1] on a per-project basis. The amount 
of commitment varies depending on the project (and I don't know what that might 
be).
> 
> [insert here why it would be an awesome experience for you, fame, 
fortune, ... :D]
> 
> --ruby
> 
> [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] volunteers for cross project liaisons

[Loo, Ruby]

Hi,

The ironic community is looking for volunteers to be cross-project liaisons [1] 
for these projects:
- oslo
- logging working group
- i18n

The expectations are documented in [1] on a per-project basis. The amount of 
commitment varies depending on the project (and I don't know what that might 
be).

[insert here why it would be an awesome experience for you, fame, fortune, ... 
:D]

--ruby

[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are meditative to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. "standalone" (without nova) tests: https://review.openstack.org/#/c/423556/
2. get multi-node grenade job up and running.
2.1. Backports: https://review.openstack.org/#/c/444950/ & 
https://review.openstack.org/#/c/444944/ need to land
3. review/land next BFV patch: https://review.openstack.org/#/c/355625/
4. update/review IPA API versioning spec: 
https://review.openstack.org/#/c/341086/
5. redfish driver: https://review.openstack.org/#/c/438982/
6. review e-tags spec: https://review.openstack.org/#/c/381991/


Bugs (dtantsur, mjturek)

- Stats (diff between 06 Mar 2017 and 13 Mar 2017)
- Ironic: 236 bugs (+4) + 246 wishlist items (+3). 14 new, 196 in progress 
(+5), 0 critical, 29 high (+3) and 30 incomplete (-2)
- Inspector: 16 bugs + 28 wishlist items (+2). 3 new (+1), 15 in progress (-1), 
0 critical, 1 high and 4 incomplete
- Nova bugs with Ironic tag: 13. 2 new, 0 critical, 0 high

Essential Priorities


CI refactoring and missing test coverage

- Standalone CI tests (vsaienk0)
- patch on review https://review.openstack.org/#/c/423556/
- Missing test coverage (all)
- portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476

Generic boot-from-volume (TheJulia, dtantsur)
-
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- Weekly meeting now established on Thursdays at 1600 UTC in 
#openstack-meeting-5
- http://eavesdrop.openstack.org/#Ironic_Boot_from_Volume_meeting
- Initial meeting was held last week between joanna and TheJulia. Basic 
context and information sharing/coordination.
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Patch series is in need of being updataed, and validated against the 
data model for volume connection information. //Base cinder interface was 
updated and validated against volume object usage in nova and cinder itself
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches
- These changes should be expected to land once Pike opens.
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231
- we cannot land these until we land Ironic API bits

Rolling upgrades and grenade-partial (rloo, jlvillal)
-
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- patch ready for review: https://review.openstack.org/#/c/407491/
- rest of patches will be updated this week: 
https://review.openstack.org/#/q/topic:bug/1526283
- Testing work:
- 13-Mar-2017: Multi-node + multi-tenant + grenade job is passing with 
patches
- We are almost done :) Hope to have it working before end-of-week
- Two backports need to be merged:
- https://review.openstack.org/444944 stable/ocata
- https://review.openstack.org/444950 stable/newton
- After backports are done need patch to openstack-infra/project-config 
to land:
- https://review.openstack.org/443348
- Will need to move job from experimental to non-voting

Reference architecture guide (jroll)

- have been hacking on a devstack setup to explore some of the kvm/ironic 
interactions

Driver composition (dtantsur, jroll)

* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- TODO as of 6 Mar 2017
- install guide / admin guide docs
- client changes:
- driver commands update: https://review.openstack.org/419274
- node-update update: https://review.openstack.org/#/c/431542/
- new hardware types:
- ilo: https://review.openstack.org/#/c/439404/
- contentious topics:
- what to do about driver properties API and dynamic drivers?
- rloo and dtantsur started brainstorming: 

[openstack-dev] [ironic] ironickers and mascot at Pike PTG (or "where's Waldo?")

[Loo, Ruby]

Dmitry, our fearless PTL, looks like the tallest person in the group. Is that 
what happens when you become PTL, or is it a requirement to be PTL? :)

Many thanks to  that organized and took this picture at the 
Pike PTG:

https://www.flickr.com/photos/152419717@N06/32926952872/in/album-72157680602754246/

--ruby

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Pike PTG report

[Loo, Ruby]

Thanks Dmitry for the great report! If you want your comment(s) to be available 
to the ironic community, please respond here, not in Dmitry's blog. (Or, to 
rephrase it a different way, if you have comments that you don't want me to 
know about, please respond in Dmitry's blog :))

Many thanks to Michael Turek for taking great notes during the PTG. Speaking of 
which, we did have some informal discussions Friday morning, but Michael wasn't 
there :)

--ruby

On 2017-03-08, 10:06 AM, "Dmitry Tantsur"  wrote:

Hi all!

I've finished my Pike PTG report. It is spread over four blog posts:

http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-1.html
http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-2.html
http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-3.html
http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-4.html

It was a lot of typing, please pardon mistakes. The whole text (in RST 
format) 
for archiving purposes is copy-pasted in the end of this message.

Please feel free to respond here or in the blog comments.

Cheers,
Dmitry


Ongoing work and status updates
---

Etherpad: https://etherpad.openstack.org/p/ironic-pike-ptg-ongoing-work.

We spent the first half of Wednesday discussing this. There was a lot of
incomplete work left from Ocata, and some major ongoing work that we did not
even plan to finish in Ocata.

Boot-from-volume


Got some progress, most of the Ironic patches are up. Desperately needs 
review
and testing, though. The Nova part is also lagging behind, and should be
brought to the Nova team attention.

**Actions**
 **mgoddard** and **dtantsur** volunteered to help with testing, while
 **mjturek**, **hsiina** and **crushil** volunteered to do some coding.
**Goals for Pike**
 finish the first (iSCSI using iPXE) case and the Nova part.

Networking
~~

A lot of progress here during Ocata, completed bonding and attach/detach 
API.

VLAN-aware instances should work. However, it requires an expensive ToR 
switch,
supporting VLAN/VLAN and VLAN/VXLAN rewriting, and, of course ML2 plugin
support. Also, reusing an existing segmentation ID requires more work: we 
have
no current way to put the right ID in the configdrive.

**Actions**
 **vsaienko**, **armando** and **kevinbenton** are looking into the 
Neutron
 part of the configdrive problem.

Routed networks support require Ironic to be aware of which physical 
network(s)
each node is connected to.

**Goals for Pike**
 * model physical networks on Ironic ports,
 * update VIF attach logic to no longer attach things to wrong physnets.

We discussed introducing notifications from Neutron to Ironic about events
of interest for us. We are going to use the same model as between Neutron 
and
Nova: create a Neutron plugin that filters out interesting events and posts
to a new Ironic API endpoint.

**Goals for Pike**
 have this notification system in place.

Finally, we agreed that we need to work on a reference architecture 
document,
describing the best practices of deploying Ironic, especially around
multi-tenant networking setup.

**Actions**
 **jroll** to kickstart this document, **JayF** and **mariojv** to help.

Rolling upgrades


Missed Ocata by a small margin. The code is up and needs reviewing. The CI
is waiting for the multinode job to start working (should be close as well).

**Goals for Pike**
 rolling upgrade Ocata -> Pike.

Driver composition reform
~

Most of the code landed in Ocata already. Some client changes landed in 
Pike,
some are still on review. As we released Ocata with the driver composition
changes being experimental, we are not ready to deprecate old-style drivers 
in
Pike. Documentation is also still lacking.

**Goals for Pike**
 * make new-style dynamic drivers the recommend way of writing and using
   drivers,
 * fill in missing documentation,
 * *recommend* vendors to have hardware types for their hardware, as 
well
   as 3rdparty CI support for it.
**Important decisions**
 * no new classic drivers are accepted in-tree (please check when 
accepting
   specifications),
 * no new interfaces additions for classic drivers(``volume_interface`` 
is
   the last accepted from them),
 * remove the SSH drivers by Pike final (probably around M3).

Ironic Inspector HA
~~~

Preliminary work (switch to a real state machine) done in Ocata. Splitting 
the
service into API 

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

[Loo, Ruby]

On 2017-03-06, 3:46 PM, "Mario Villaplana"  wrote:

Hi ironic,

At the PTG, an issue regarding the default version of the ironic API
used in our python-openstackclient plugin was discussed. [0] In short,
the issue is that we default to a very old API version when the user
doesn't otherwise specify it. This limits discoverability of new
features and makes the client more difficult to use for deployments
running the latest version of the code.

We came to the following consensus:

1. For a deprecation period, we should log a warning whenever the user
doesn't specify an API version, informing them of this change.

2. After the deprecation period:

a) OSC baremetal plugin will default to the latest available version

I think OSC and ironic CLI have the same behaviour -- are we only interested in 
OSC or are we interested in both, except that we also want to at some point 
soon perhaps, deprecate ironic CLI?

Also, by 'latest available version', the OSC plugin knows (or thinks it knows) 
what the latest version is [1]. Will you be using that, or 'latest'?

b) Specifying just macroversion will default to latest microversion
within that macroversion (example: --os-baremetal-api-version=1 would
default to 1.31 if 1.31 is the last microversion with 1 macroversion,
even if we have API 2.2 supported)

I have a patch up for review with the deprecation warning:
https://review.openstack.org/442153

Do you have an RFE? I'd like a spec for this too please.

Please comment on that patch with any concerns.

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
with any suggestions on the deprecation period.

Thanks,
Mario


[0] https://etherpad.openstack.org/p/ironic-pike-ptg-operations L30

Thank YOU!

--ruby

[1] 
https://github.com/openstack/python-ironicclient/blob/f242c6af3b295051019aeabb4ec7cf82eb085874/ironicclient/osc/plugin.py#L29

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are magnanimous to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. PTG summary and deciding on Pike priorities: 
https://review.openstack.org/439710
1.1. update subteam list afterwards
2. portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476
3. "standalone" (without nova) tests: https://review.openstack.org/#/c/423556/
4. get multi-node grenade job up and running
5. review e-tags spec: https://review.openstack.org/#/c/381991/
6. rebase, review and land node tags: 
https://review.openstack.org/#/q/topic:bug/1526266


Bugs (dtantsur, mjturek)

- Stats (diff between 27 Feb 2017 and 06 Mar 2017)
- Ironic: 232 bugs (+5) + 243 wishlist items (+5). 14 new (-6), 191 in progress 
(+2), 0 critical, 26 high (+2) and 32 incomplete (+3)
- Inspector: 16 bugs (+1) + 26 wishlist items (+3). 2 new (-1), 16 in progress 
(+3), 0 critical, 1 high and 4 incomplete
- Nova bugs with Ironic tag: 13 (+2). 2 new (+2), 0 critical, 0 high

CI refactoring and missing test coverage (dtantsur, lucasagomes)

* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- standalone tests proposed by vsaienk0 
https://review.openstack.org/#/c/423556/
- portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283.
- Testing work:
- 6-Mar-2017: Multi-node + multi-tenant + grenade job is passing with 
patches
- Currently one patch to devstack remaining to get merged.
- https://review.openstack.org/#/c/440303/
- Big thanks to vsaienk0 for his work! :) +1
- Multinode job random failures due to nova bug: 
https://bugs.launchpad.net/nova/+bug/1670319

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Patch series is in need of being updataed, and validated against the 
data model for volume connection information.
- Hopefully we will have our first meeting this week, please respond to 
the doodle poll http://doodle.com/poll/qwhnpqazmf7fn5ik regarding scheduling.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches
- These changes should be expected to land once Pike opens.
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231
- we cannot land these until we land Ironic API bits

Driver composition (dtantsur, jroll)

* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- TODO as of 6 Mar 2017
- install guide / admin guide docs
- client changes:
- driver commands update: https://review.openstack.org/419274
- node-update update: https://review.openstack.org/#/c/431542/
- talked at PTG about anything missing, path to getting vendor hw types, 
etc. jroll will update with what is left to do.

Rescue mode (JayF / mariojv)

* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- Working in devstack! http://imgur.com/a/dqvE2
- 3/6 status
- ironic patch chain order updated to make reviews easier
- Please review :D
- ironic
- https://review.openstack.org/#/c/350831/ - API/conductor methods
- https://review.openstack.org/#/c/353156/ - rescuewait timeout 
periodic task
- https://review.openstack.org/#/c/400437/ - agent driver patch
- client
- https://review.openstack.org/#/c/408341/ - client support patch - 
potentially needs update
- IPA
- https://review.openstack.org/#/c/423521 - IPA support for CoreOS 

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

[Loo, Ruby]

Hi Julia,

Thanks for asking!

I'm agnostic about whether the BFV meeting should use the same day/time as the 
ironic-neutron meeting was. As long as people who are/will be attending this 
meeting are fine with the date/time, I'm fine too :)

I would actually prefer that the date/times are chosen to accommodate the folks 
that intend on attending those meetings. I'm concerned about keeping/having a 
'generic' meeting time that doesn't work that well for the same folks all the 
time. If we 'set this in stone', new people may not feel like they could ask to 
change the day/time :-(

I did not take any poll so I may be bringing something up that no one cares 
about. E.g., I'm totally fine with the proposed date/time but I don't know if 
I'll be attending this or future meetings :)

--ruby

From: Julia Kreger 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, February 28, 2017 at 9:42 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

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

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 years.  Largely, in a
slow incremental approach, which is in part due to how I perceived it
to best fit into the existing priorities when the discussions started.

During PTG there was quite the interest by multiple people to become
involved and attempt to further Boot from Volume forward this cycle. I
would like to move to having a weekly meeting with the focus of
integrating this functionality into ironic, much like we did with the
tighter neutron integration.

I have two reasons for proposing a new meeting:

* Detailed technical status updates and planning/co-ordination would
need to take place. This would functionally be noise to a large number
of contributors in the ironic community.

* Many of these details would need need to be worked out prior to the
first part of the existing ironic meeting for the weekly status
update. The update being a summary of the status of each sub team.

With that having been said, I'm curious if we could re-use the
ironic-neutron meeting time slot [0] for this effort.  That meeting
was cancelled just after the first of this year [1].  In it's place I
think we should have a general purpose integration meeting, that could
be used as a standing meeting, specifically reserved at this time for
Boot from Volume work, but could be also by any integration effort
that needs time to sync-up in advance of the existing meeting.

-Julia

[0] 
http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings/ironic-neutron-integration-meeting.yaml
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-January/109536.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are fascinated to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. PTG summary and deciding on Pike priorities
2. update subteam list
3. portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476


Bugs (dtantsur, vdrok)
==
- Stats (diff between 13 Feb 2017 and 27 Feb 2017)
- Ironic: 227 bugs (+7) + 238 wishlist items (+2). 20 new (+3), 189 in progress 
(+8), 0 critical, 24 high (-1) and 29 incomplete
- Inspector: 15 bugs (+1) + 23 wishlist items (+3). 3 new (+1), 13 in progress 
(+1), 0 critical, 1 high and 4 incomplete (-1)
- Nova bugs with Ironic tag: 11. 0 new (-1), 0 critical, 0 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- tempest tests https://review.openstack.org/382476 need review

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- standalone tests proposed by vsaienk0 
https://review.openstack.org/#/c/423556/

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283.
- Testing work:
- 27-Feb-2017: Grenade + multi-tenant + multi-node is passing on the 
OSIC cluster :)
- This is of course with a few patches which still need to land.
- There is an issue with the job failing on clusters other than 
OSIC :(

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Julia in process of updating base changes
- Volunteers indicated they would be willing to assist with the 
remaining work. TheJulia will be reaching out to those volunteers during the 
week after the PTG in order to schedule a regular meeting.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches
- These changes should be expected to land once Pike opens.
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231

Driver composition (dtantsur, jroll)

* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- a job based on the IPMI hardware type is running non-voting
- will probably be rolled into some other job(s) later
- api-ref merged
- next steps (some yet to be written/finished) as of 13 Feb 2017:
- install guide / admin guide docs - TODO
- client changes:
- driver commands update: https://review.openstack.org/419274
- node-update update: https://review.openstack.org/#/c/431542/
- talked at PTG about anything missing, path to getting vendor hw types, 
etc. jroll will update with what is left to do.

Rescue mode (JayF / mariojv)

* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- Working in devstack! http://imgur.com/a/dqvE2
- 2/27 status
- need reviews on:
- https://review.openstack.org/#/c/350831/ - API/conductor methods 
(tested working)
- https://review.openstack.org/#/c/353156/ - rescuewait timeout 
periodic task
- https://review.openstack.org/#/c/400437/ - agent driver patch (tested 
working)
- https://review.openstack.org/#/c/408341/ - client support patch 
(tested working)
- https://review.openstack.org/#/c/423521 - IPA support for CoreOS 
Image + DHCP networks (tested working)
- https://review.openstack.org/#/c/419606/ - ironic docs patch - needs 
rebase and updates
- https://review.openstack.org/#/c/431622/ - IPA docs patch - needs 
updates
- Still WIP
- Nova patch: https://review.openstack.org/#/c/416487/

etags in the REST API (gzholtkevych)

Re: [openstack-dev] [ironic] End-of-Ocata core team updates

[Loo, Ruby]

Vasyl + Mario: definitely +2. Just like the rest of us, they aren't experts in 
everything, but we trust them and us to review and +2 based on our degree of 
confidence etc! Looking forward to them relieving the load :)

Devananda. Unfortunately, +2 but I'd rather do a -2. This makes me so sad. I am 
happy that Deva is on another journey but I wished it included ironic. I am so 
grateful for everything he has done for ironic, especially all the non-ironic 
parts of it :)

--ruby

From: Dmitry Tantsur 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 17, 2017 at 4:40 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] End-of-Ocata core team updates

Hi all!

I'd like to propose a few changes based on the recent contributor activity.

I have two candidates that look very good and pass the formal barrier of 3
reviews a day on average [1].

First, Vasyl Saienko (vsaienk0). I'm pretty confident in him, his stats [2] are
high, he's doing a lot of extremely useful work around networking and CI.

Second, Mario Villaplana (mariojv). His stats [3] are quite high too, he has
been doing some quality reviews for critical patches in the Ocata cycle.

Active cores and interested contributors, please respond with your +-1 to these
suggestions.

Unfortunately, there is one removal as well. Devananda, our team leader for
several cycles since the very beginning of the project, has not been active on
the project for some time [4]. I propose to (hopefully temporary) remove him
from the core team. Of course, when (look, I'm not even saying "if"!) he comes
back to active reviewing, I suggest we fast-forward him back. Thanks for
everything Deva, good luck with your current challenges!

Thanks,
Dmitry

[1] http://stackalytics.com/report/contribution/ironic-group/90
[2] http://stackalytics.com/?user_id=vsaienko=marks
[3] http://stackalytics.com/?user_id=mario-villaplana-j=marks
[4] http://stackalytics.com/?user_id=devananda=marks

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi Heidi,

I'm happy with the proposed logo.

As far as the "kiss" style face painting goes, I don't like it. But that is 
because I am not a fan of KISS or their music. Having said that, I can 
understand why people would like it and why it fits with ironic, so I am fine 
if it is used :)

Thank you for being so patient with us and going the extra kilometres!

--ruby

From: Lucas Alvares Gomes 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, February 16, 2017 at 5:44 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

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

Hi,

Hi Ironic team,

[TL;DR - we agree to Miles’ proposal for two images (one mascot, one logo) for 
different contexts. We’re looking for any final feedback on the stylized logo 
for use on the website, while the PixieBoots mascot remains yours for swag, 
etc.]

I’m doing my best to reply to all questions on this thread as Lucas requested: 
http://lists.openstack.org/pipermail/openstack-dev/2017-February/112212.html.
Please feel free to drop a note here if I’ve missed anything. I’m summarizing 
everything below:

Design issues:
—The bear looked angry in v1
Answer: We removed the angry expression and replaced it with a neutral 
expression
—The metal horns hand gesture is culturally inappropriate (rude in some 
countries) (from Ruby)
Answer: We removed this feature and replaced it, based on the team’s input, 
with the bear holding sticks (as drumsticks)
—What about a goat-like horned bear? (Joanna)
Answer: We removed horned references due to the cultural reference to 
cuckolding as the Ironic team pointed out
—The bear looks too much like a Russian meme with two hands up
Answer: We have a face-forward bear, not a side-view bear, and only one hand 
raised.
—The bear’s face decoration looked too much like the band Kiss
Answer: While this was intentional by the designer (for a more “metal” look), 
we removed this feature and replaced it with basic bear face coloring. Some 
folks (including Miles, Dmitry, Sam who added +1s) would like this back in. 
We’re happy to do it, we just need the team to agree on one direction.

I'm OK either way, but liked the "KISS" style face painting.


+1 the kiss star looks cool indeed.




—Don’t like the style (reminds Lucas of church windows)
Answer: The design style for all of the mascots is set. It was shared in July 
when we started this project, and unfortunately the feedback window regarding 
design style has passed, as 95% of projects have now received their logos.


Fair enough



—Request to abbreviate the bear so it just shows head/top of torso/hand holding 
drumsticks (from Dmitry)
Answer: We can revisit that with the designers, however it doesn’t match the 
rest of the logo set, which is either face or full body of each mascot. We’re 
happy to try this, but as we’ve already been four rounds with the team, I’m 
soliciting ANY final feedback on this version before we finalize it.

I'm OK with this. I think it'll be the closest we'll get to something everyone 
can agree on. +1 from me.


Outstanding questions:
—Can we use PixieBoots in the future?
Answer: Absolutely. You’re welcome to produce vintage swag like shirts and 
stickers with your original logo. Any team can use their old logo in this way. 
Put another way, if you’d like to call PixieBoots your mascot, but refer to the 
Ironic logo our illustrators have created as merely a logo, that’s fine. And 
you don’t have to use this logo if you don’t want to.
—Can we use (1) A stylized logo, matching the guidelines, for use in “official” 
settings and anywhere that it will be seen in other projects’ logos; and (2) 
Our existing PixieBoots mascot, for use in “official” settings (laptop 
stickers, T-shirts, chatbots, webcomic, etc.)? (suggested by Miles)
Answer: Great suggestion! Yes. Together with the answer above, that’s our 
intention—we’d like for you to be able to continue to use your beloved mascot 
in your own way, and we’d like the Ironic team to select some logo that is 
consistent with the rest of the community project logos, that we can use on 
official channels such as the website.
—What will we see at the PTG?
Answer: Out of respect for the team, we did not print stickers or signage for 
the Ironic team with any logo on it until the team reaches an agreement.
—What license will the mascot have?
Answer: It will be CC-BY-ND, which the foundation uses for most of our 
collateral. That allows you to use it (and we’ve provided ten versions to the 
PTLs of the projects with finalized mascots so they have a good amount of 
flexibility in logo use). It prevents, for example, a for-profit company from 
inserting its commercial logo into an element of the community-use mascots 
(which was a common request early in the design process). If you would like to 
make a derivative work, we can 

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are feverish to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. Clean up release notes for 7.0.0 https://review.openstack.org/#/c/431188/
1.1. also inspector https://review.openstack.org/#/c/433043/
1.2. also IPA https://review.openstack.org/#/c/433051/
2. portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476
3. review maximum specs, especially those proposed for PTG discussions


Bugs (dtantsur)
===
- Stats (diff between 06 Feb 2017 and 13 Feb 2017)
- Ironic: 220 bugs (-5) + 236 wishlist items (+5). 17 new (-8), 181 in progress 
(-3), 0 critical, 25 high and 29 incomplete (+3)
- Inspector: 14 bugs (+1) + 20 wishlist items. 2 new, 12 in progress, 0 
critical, 1 high (-1) and 5 incomplete (+1)
- Nova bugs with Ironic tag: 11. 1 new (+1), 0 critical, 0 high (-1)

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- tempest tests https://review.openstack.org/382476 need review

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- standalone tests proposed by vsaienk0 
https://review.openstack.org/#/c/423556/

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- bumped to Pike.
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283.
- Testing work:
- Grenade + multi-tenant is now working!!!  With a couple grenade 
patches that need to land.
- Next step is: grenade + multi-tenant + multi-NODE.
- As expected, it is failing :( Currently debugging the issue to 
determine what is the reason.

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- Bumped to pike
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Julia expecting to rebase these change Monday 2/14
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches
- They need OSC support added into the revisions.
- These changes should be expected to land once Pike opens.
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231

Driver composition (dtantsur, jroll)

* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- a job based on the IPMI hardware type is running non-voting
- will probably be rolled into some other job(s) later
- api-ref merged
- next steps (some yet to be written/finished) as of 13 Feb 2017:
- install guide / admin guide docs - TODO
- client changes:
- driver commands update: https://review.openstack.org/419274
- node-update update: https://review.openstack.org/#/c/431542/
- We should agree on some scope for this feature for Ocata, I guess. Maybe 
we call it semi-done when we finish ^^^
- +1, and we can talk at PTG about anything missing, path to getting 
vendor hw types, etc
- UPD: I think we can call it done for Ocata, modulo docs
- (rloo) i thought CI and hw types equivalents for classic drivers 
was still missing

Rescue mode (JayF)
==
- Work on pause until Ocata is cut (no more rebasing until then :D)
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- Bumped to pike.
- Working in devstack! http://imgur.com/a/dqvE2
- 1/30 status
- need reviews on:
- https://review.openstack.org/#/c/350831/ - API/conductor methods 
(tested working)
- https://review.openstack.org/#/c/353156/ - rescuewait timeout 
periodic task
- https://review.openstack.org/#/c/400437/ - agent driver patch (tested 
working)
- https://review.openstack.org/#/c/408341/ - client support patch 
(tested working)
- 

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are freewheeling to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. Continue reviewing driver composition things (especially devstack/CI 
changes): https://review.openstack.org/#/q/status:open+topic:bug/1524745
2. portgroups and attach/detach tempest tests and docs: 
https://review.openstack.org/382476
3. other docs, bug fixes
3.1. see bugs in list below
3.2. vdrok to find doc patches that need attention:
  3.2.1. WIP: docs for dynamic drivers - 
https://review.openstack.org/426819 - need to be written
  3.2.2. Api-ref changes for dynamic drivers - need to be written mariojv 
working on this 2/2/17•
  3.2.3. Portgroups configuration - https://review.openstack.org/429826 WIP
  3.2.4. Nice to have:
3.2.4.1. Detailed sequence-diagram for deploy 
https://review.openstack.org/414512
3.2.4.2. Help a user to enable console redirection 
https://review.openstack.org/384578


Bugs (dtantsur)
===
- Stats (diff between 30 Jan 2017 and 06 Feb 2017)
- Ironic: 225 bugs (-5) + 231 wishlist items (-2). 25 new (+3), 184 in progress 
(-3), 0 critical, 25 high (-2) and 26 incomplete (-3)
- Inspector: 13 bugs + 20 wishlist items (-2). 2 new, 12 in progress (-1), 0 
critical, 2 high and 4 incomplete
- Nova bugs with Ironic tag: 11 (+1). 0 new, 0 critical, 1 high (+1)
- Some bugs vdrok thinks would be good to look into before release:
- instance rebuild with multitenancy - 
https://bugs.launchpad.net/ironic/+bug/1657083
- Conductor's periodic tasks stops executing - 
https://bugs.launchpad.net/ironic/+bug/1637210
- Seemingly wrong deploy callback timeouts - 
https://bugs.launchpad.net/ironic/+bug/1646477
- regenerate the PXE configuration on neutron port update - 
https://bugs.launchpad.net/ironic/+bug/1614094
- proper subcontrollers handling - https://launchpad.net/bugs/1580997
- couple of smaller API issues: 
https://bugs.launchpad.net/ironic/+bug/1643995 and 
https://launchpad.net/bugs/1640546

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- tempest tests https://review.openstack.org/382476 need review
- documentation (need to be written still)

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- We now run a non-voting UEFI job in the gate (and it's green) o/

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- leaning towards moving this to Pike.
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283.
- concerns about https://review.openstack.org/#/c/420728/ (Add 
compatibility with Newton when creating a node)
- had irc discussion about status: 
http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2017-01-23.log.html#t2017-01-23T16:17:41
- Testing work:
- The final tempest "smoke" test is failing after the grenade run in 
the multi-tenant grenade job.
- 
http://logs.openstack.org/49/422149/5/experimental/gate-grenade-dsvm-ironic-multitenant-ubuntu-xenial-nv/74c9ed9/console.html
- Believe that this issue is due to the network getting changed 
after Grenade finishes and then we lose connectivity to the Ironic node.
- The grenade portion passes for the multi-tenant grenade job
- 
http://logs.openstack.org/49/422149/5/experimental/gate-grenade-dsvm-ironic-multitenant-ubuntu-xenial-nv/74c9ed9/logs/grenade.sh.summary.txt.gz
- Testing being done in: https://review.openstack.org/#/c/422149/
- This needs multi-node testing, and multi-node has a very low 
probability of working in Ocata

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Last patch set for cinder common client interface was reverted in a 
rebase.  TheJulia expects to address this Monday afternoon.
- 

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

[Loo, Ruby]

Hi,

I don't like the new one. I think Lucas captured it nicely. I prefer our 
PixieBoots.

Jim, do you remember what our choices are? Could we use PixieBoots?

--ruby

From: Lucas Alvares Gomes 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, January 31, 2017 at 5:13 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

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

I may be biased to some extent but I don't like it.

The mascot doesn't seem to have any personality. It also looks odd
because he has this straight face while he's doing the sign of horns,
it just doesn't work.

I remember when I first saw a logo related to Ironic in that
presentation that Jay and Josh made in the Atlanta summit (2014),
check it out: https://www.youtube.com/watch?v=2Oi2T2pSGDU=96s

That's a rocker bear. It has a rockstar pose, it has an expression,
the paul stanley star on his face is pretty cool, it's holding a
awesome guitar, etc etc etc... When I think that someone is paying a
professional to create the mascots that's the level of design that I
expect. Now, the proposed bear doesn't even incorporate the main
elements of PixieBoots: 1) It doesn't look like a rockstar and 2) He's
not a drummer [0] (PixeBoots is a drummer bear!).

I have no problem with minimalist logos, I actually like then a lot
but the idea is to capture the essence of something using a simple
design. This one just looks poorly thought out and simpleminded.

[0] 
https://wiki.openstack.org/wiki/Ironic#Pixie_Boots.2C_the_Ironic_drummer_bear

Cheers,
Lucas

On Tue, Jan 31, 2017 at 8:49 PM, Jim Rollenhagen 
> wrote:
Hey ironic-ers,

The foundation has passed along a new version of our mascot (attached) to
us, and would like your feedback on it.

They're hoping to have all mascot-related things ready in time for the PTG,
so please do send your thoughts quickly, if you have them. :)

// jim

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are jovial to present this week's priorities and subteam report for Ironic. 
As usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. Continue reviewing driver composition things (see notes below, some of the 
WIP patches are ready other than docs/reno): 
https://review.openstack.org/#/q/status:open+topic:bug/1524745
2. portgroups and attach/detach tempest tests and docs: 
https://review.openstack.org/382476
3. other docs, bug fixes
3.1. dtantsur to find bugs potentially requiring attention and throw them 
at people
3.2. vdrok to find doc patches that need attention


Bugs (dtantsur)
===
- Stats (diff between 23 Jan 2017 and 30 Jan 2017)
- Ironic: 230 bugs (+3) + 233 wishlist items (-4). 22 new (+3), 187 in progress 
(-3), 0 critical, 27 high (-1) and 29 incomplete (-2)
- Inspector: 13 bugs (+2) + 22 wishlist items (-2). 2 new (+2), 13 in progress 
(-3), 0 critical, 2 high (-1) and 4 incomplete
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- tempest tests https://review.openstack.org/382476 need review
- documentation (need to be written still)

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- UEFI patches are merged!
- Project-config patch adding an experimental job: 
https://review.openstack.org/#/c/424576/

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- leaning towards moving this to Pike.
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283.
- concerns about https://review.openstack.org/#/c/420728/ (Add 
compatibility with Newton when creating a node)
- had irc discussion about status: 
http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2017-01-23.log.html#t2017-01-23T16:17:41
- Testing work:
- The final tempest "smoke" test is failing after the grenade run in 
the multi-tenant grenade job.
- 
http://logs.openstack.org/49/422149/5/experimental/gate-grenade-dsvm-ironic-multitenant-ubuntu-xenial-nv/74c9ed9/console.html
- Believe that this issue is due to the network getting changed 
after Grenade finishes and then we lose connectivity to the Ironic node.
- The grenade portion passes for the multi-tenant grenade job
- 
http://logs.openstack.org/49/422149/5/experimental/gate-grenade-dsvm-ironic-multitenant-ubuntu-xenial-nv/74c9ed9/logs/grenade.sh.summary.txt.gz
- Testing being done in: https://review.openstack.org/#/c/422149/
- This needs multi-node testing, and multi-node has a very low 
probability of working in Ocata

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Last patch set for cinder common client interface was reverted in a 
rebase.  TheJulia expects to address this Monday afternoon.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches
- They need OSC support added into the revisions.
- These changes should be expected to land once Pike opens.
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231

Driver composition (dtantsur, jroll)

* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- we're now able to load hardware types on start-up! \o/
- next steps (some yet to be written/finished) as of 23 Jan 2017:
- API changes for setting hardware types and interfaces
- ready for review
- https://review.openstack.org/417970
- https://review.openstack.org/#/c/424720/
- still todo:
- update 

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are jittery to present this week's priorities and subteam report for Ironic. 
As usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. nova patch for soft power/reboot: https://review.openstack.org/#/c/407977/
2. ironicclient queue: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient
3. ironic-inspector-client queue: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironic-inspector-client
4. Continue reviewing driver composition things (see notes below, some of the 
WIP patches are ready other than docs/reno): 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1524745
5. Node tags: https://review.openstack.org/#/q/topic:bug/1526266


Bugs (dtantsur)
===
- Stats (diff between 16 Jan 2017 and 23 Jan 2017)
- Ironic: 227 bugs (-3) + 237 wishlist items (-1). 19 new, 190 in progress 
(-1), 0 critical, 28 high (-1) and 31 incomplete (+1)
- Inspector: 11 bugs (-1) + 24 wishlist items (+1). 0 new, 16 in progress (+2), 
0 critical, 3 high (+1) and 4 incomplete (-1)
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- everything is done, except for tempest tests and documentation.(need to 
be written still)

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
done

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- Two more patches to go to add support for deploying UEFI images with 
Ironic in devstack: 1) https://review.openstack.org/#/c/414604/ (DevStack) 2) 
https://review.openstack.org/#/c/374988/ BOTH MERGED
- focus (lucasagomes) is to get UEFI testing in gate. More patches needed 
for this.

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- leaning towards moving this to Pike.
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283.
- concerns about https://review.openstack.org/#/c/420728/ (Add 
compatibility with Newton when creating a node)
- had irc discussion about status: 
http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2017-01-23.log.html#t2017-01-23T16:17:41
- Testing work:
- Great progress this last week! Able to fix issue that had blocked us 
for several weeks in the multi-tenant grenade job!
- Tempest smoke is now working for the multi-tenant grenade job during 
the initial pre-grenade run.
- The grenade portion passes for the multi-tenant grenade job
- 
http://logs.openstack.org/49/422149/5/experimental/gate-grenade-dsvm-ironic-multitenant-ubuntu-xenial-nv/74c9ed9/logs/grenade.sh.summary.txt.gz
- The final tempest "smoke" test is failing after the grenade run in 
the multi-tenant grenade job.
- 
http://logs.openstack.org/49/422149/5/experimental/gate-grenade-dsvm-ironic-multitenant-ubuntu-xenial-nv/74c9ed9/console.html
- Testing being done in: https://review.openstack.org/#/c/422149/
- This needs multi-node testing, and multi-node has a very low 
probability of working in Ocata

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review
- Last patch set for cinder common client interface was reverted in a 
rebase.  TheJulia expects to address this Monday afternoon.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches
- They need OSC support added into the revisions.
- These changes should be expected to land once Pike opens.
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231

Driver composition (dtantsur, jroll)

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are jubilant to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. nova code for portgroups and attach/detach: 
https://review.openstack.org/#/c/364413/ and 
https://review.openstack.org/#/c/388756/
2. client patch for soft power/reboot: https://review.openstack.org/#/c/357627/ 
to unblock the nova patch: https://review.openstack.org/#/c/407977/
3. ironicclient queue: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient
4. ironic-inspector-client queue: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironic-inspector-client
5. Continue reviewing driver composition things: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1524745
6. Rolling upgrades work: 
https://review.openstack.org/#/q/topic:bug/1526283+status:open
7. boot from volume: next up: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691


Bugs (dtantsur)
===
- Stats (diff between 09 Jan 2017 and 16 Jan 2017)
- Ironic: 230 bugs (+7) + 238 wishlist items. 19 new (+5), 191 in progress 
(-1), 0 critical, 29 high (+1) and 30 incomplete (+4)
- Inspector: 12 bugs + 23 wishlist items. 0 new, 14 in progress (+2), 0 
critical, 2 high and 5 incomplete
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- just one patch left on the ironic side: 
https://review.openstack.org/#/q/topic:bug/1618754
- once that lands, then nova patch - https://review.openstack.org/388756
- note that the nova patch cannot land until after the attach/detach 
API nova-patch lands (https://review.openstack.org/364413)

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- ironic patches merged, ironicclient released
- Nova patch needs reviews - https://review.openstack.org/364413

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- Two more patches to go to add support for deploying UEFI images with 
Ironic in devstack: 1) https://review.openstack.org/#/c/414604/ (DevStack) 2) 
https://review.openstack.org/#/c/374988/

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283
- Testing work:
- Tempest "smoke" is now working for multi-tenant / multi-node
- Patch up to enable tempest "smoke" for the multi-node job
- https://review.openstack.org/417959
- Next step Grenade
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information has a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change has been rebased on top of the iPXE template update 
revision to support cinder/iscsi booting.
- Boot from volume/storage cinder interface is up for review.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- Original volume connection information client patches were rebased this 
past week
- They need OSC support added into the revisions.
- These changes are extremely unlikely to make client freeze for this 
cycle, which means we should target to land them at the beginning of Pike
- 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526231

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- next patch makes conductor actually load defined hardware types: 
https://review.openstack.org/#/c/412631/
- small inspector-related clean up: https://review.openstack.org/416232
 

Re: [openstack-dev] [ironic] Stepping down as PTL after this cycle

[Loo, Ruby]

Jim,

(Now that the shock has worn off). Thanks for being such a great PTL. I very 
much appreciated what you did/do as PTL! And welcome back to the land of 
coding, etc. :)

--ruby

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, January 6, 2017 at 2:02 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] Stepping down as PTL after this cycle

Hi friends,
I'll be stepping down as PTL after Ocata is done. I'll still be 100% dedicated 
to the project, but I'd like to be able to focus more on writing code and 
reinforcing the bridges between us and other projects (Nova, Neutron, etc).
I'd love to see two or more people step up and run next cycle in a real 
election. I'm happy to chat with anyone interested in becoming the Pike PTL, if 
you have questions or need a candidacy review or whatever.
It's been an amazing experience leading this project. You're all awesome, and 
I'm grateful you chose me to do so. I hope the following cycles are even 
better. :)

// jim
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are jazzy to present this week's priorities and subteam report for Ironic. 
As usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. attach/detach: review code, needs done ASAP to unblock nova stuff before 
freeze: https://review.openstack.org/#/q/topic:bug/1582188+status:open
2. nova code for portgroups and attach/detach: 
https://review.openstack.org/#/c/364413/ and 
https://review.openstack.org/#/c/388756/
3. client patch for soft power/reboot: https://review.openstack.org/#/c/357627/ 
to unblock the nova patch: https://review.openstack.org/#/c/407977/
4. ironic-lib queue: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic-lib
5. Continue reviewing driver composition things: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1524745
6. boot from volume: next up: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
7. Rolling upgrades work: 
https://review.openstack.org/#/q/topic:bug/1526283+status:open
8. Work to test UEFI: https://review.openstack.org/#/c/414227/ (Ironic), 
https://review.openstack.org/#/c/414604/ (Devstack).


Bugs (dtantsur)
===
- Stats (diff between 19 Dec 2016 and 09 Jan 2017)
- Ironic: 223 bugs (+5) + 238 wishlist items (+5). 14 new (+5), 192 in progress 
(+6), 0 critical, 28 high (-1) and 26 incomplete (-2)
- Inspector: 12 bugs (+1) + 23 wishlist items (+1). 0 new, 12 in progress, 0 
critical (-1), 2 high (+1) and 5 incomplete (+1)
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- just one patch left on the ironic side (OSC): 
https://review.openstack.org/#/q/topic:bug/1618754 merged
- Another one needed is adding mode/properties to the portgroups in client, 
will be done soon :)
- once those land, will need a client release and then nova patches
- note that the nova patch cannot land until after the attach/detach 
API nova-patch lands

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Last Ironic patch up for review: https://review.openstack.org/#/c/404240/
- Rebasing in progress (sambetts)
- IronicClient patch - https://review.openstack.org/364420
- Nova patch needs updating based on IronicClient patch and can't merge 
until we make a client release including the above patch - 
https://review.openstack.org/364413

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- We need to move the logic of setting the default image from DevStack into 
Ironic to be able to set a UEFI compatible image, patches are: 
https://review.openstack.org/#/c/414227/ (Ironic), 
https://review.openstack.org/#/c/414604/ (Devstack)

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- RFE for online-db-migration, approved: 
https://bugs.launchpad.net/ironic/+bug/1585141
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283
- Testing work:
- Tempest "smoke" is now working for multi-tenant / multi-node
- Patch up to enable tempest "smoke" for the multi-node job
- https://review.openstack.org/417959
- Next step Grenade
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information have a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- This change will need to be rebased on top of the storage interface 
work so we can begin working towards a single chain of revisions to build 
testing against. +1
- Boot from volume/storage interface work needs to be updated, TheJulia 
will be doing that this week
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: 

Re: [openstack-dev] [Ironic] python-ironicclient weird behaviour

[Loo, Ruby]

From: Maxime Belanger 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, December 22, 2016 at 9:32 AM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [Ironic] python-ironicclient weird behaviour


Hi Ironic folks,



Yesterday I come across a weird behaviour in python-ironicclient. I discussed 
briefly with the problem with Julia and befor creating a bug I would like your 
opinion on the problem and potential fix.



When doing nodes.get(resource_id=None), I get back a Node object set with 
attribute nodes={nodes: [{uuid: 'blah'}, {uuid: 'bleh'}]}. I guess that is not 
expected which is the bug I found and I know where to fix it if we agree to not 
change the behavour: If resource_id=None the client is doing a GET on /v1/nodes 
which is expected here : 
https://github.com/openstack/python-ironicclient/blob/1.8.0/ironicclient/common/base.py#L55.



The thing is, returning the first item of the list while doing a get on 
something that doesn't exists is a bit strange. I do not want to do extra 
validation on my application side to not pass None to the ironicclient. I would 
it to behave correctly: 404 or a even a 400.



What do you think/or prefer?



A. Fixing the bug and not changing actual behaviour of the API

B. Changing the API behaviour and returning a 404 error since resource None is 
not found

C. Changing the API behaviour and returning a 400 error because None is not a 
valid request. The will be identical to the command line that is doing this:
ironic node-show None
Invalid input for field/attribute node_ident. Value: 'None'. unable to convert 
to uuid_or_name (HTTP 400)

Thanks
Max

Thanks for tripping over this! :-( I think this is a bug in the API. I think it 
is just a coincidence that it happens to return the list of nodes (because the 
generated HTTP request works). That code should be checking that resource_id is 
non-empty -- that's what the CLI does. And if it isn't, raise an exception. I 
vote for B, sort of. It shouldn't return an http status error since no http 
request should be made. Looking at the existing exceptions, I'm guessing 
InvalidAttribute or ValidationError?

Your C above is a different situation, 'None' is a string that is the name of a 
node, but that string doesn't conform to the allowed name syntax.

--ruby

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic] Retiring ironic-webclient

[Loo, Ruby]

Thanks Julia.

--ruby

From: Julia Kreger 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, December 19, 2016 at 2:34 PM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [Ironic] Retiring ironic-webclient

As discussed at the last summit during the contributor meet-up, as well as 
during today’s Ironic team meeting[0], we will be retiring the 
ironic-webclient. This is due to a number of factors, the largest being that 
the primary contributor has changed positions and is no longer contributing, 
nor does he have any interest in continuing to develop or maintain the 
ironic-webclient. Beyond that, no contributions have landed in the last six 
months, nor has there ever been an official release of the ironic-webclient.  
This should not be confused with ironic-ui which is a horizon plug-in.

Since there have been no releases, nor objections thus far, I will begin the 
process of retiring ironic-webclient this week.

-Julia

[0] 
http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-12-19-17.00.log.html


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are delighted to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. attach/detach: review code: https://review.openstack.org/#/c/327046/
2. rolling upgrades spec for dbsync online-db-migration. need to approve: 
https://bugs.launchpad.net/ironic/+bug/1585141
3. boot from volume: next up: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
4. next notifications: review code for CRUD notifications: 
https://review.openstack.org/#/c/356541/


Bugs (dtantsur)
===
- Stats (diff between 12 Dec 2016 and 19 Dec 2016)
- Ironic: 218 bugs (+1) + 233 wishlist items (+2). 9 new (+2), 186 in progress 
(+3), 0 critical (-3), 29 high and 28 incomplete (-1)
- Inspector: 11 bugs + 22 wishlist items. 1 new (+1), 12 in progress, 1 
critical (+1), 1 high and 4 incomplete
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- just one patch left on the ironic side (OSC): 
https://review.openstack.org/#/q/topic:bug/1618754
- Another one needed is adding mode/properties to the portgroups in client, 
will be done soon :)
- once those land, will need a client release and then nova patches
- note that the nova patch cannot land until after the attach/detach 
API nova-patch lands

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- (lucasagomes) No updates

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- RFE for online-db-migration, need to approve: 
https://bugs.launchpad.net/ironic/+bug/1585141
- patches need reviews: https://review.openstack.org/#/q/topic:bug/1526283
- Testing work:
- Tempest "smoke" tests are now passing for multi-node/multi-tenant 
with various patches!
- Grenade patch has one +2: https://review.openstack.org/407502
- merged
- Sort of blocked by tempest becoming a plugin. Merged 19-Dec-2016.
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Ironic patch up for review: 
https://review.openstack.org/#/q/topic:bug/1582188
- IronicClient - https://review.openstack.org/364420
- Patches need updating still:
- Nova - https://review.openstack.org/364413

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information have a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- Boot from volume/storage interface work was rebased on top of the driver 
composition work this past week.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
- TheJulia intends to begin work on the iPXE iscsi boot work required this 
week.

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- the patch introducing hardware types defining and loading: 
https://review.openstack.org/336626 merged
- generic hardware types: https://review.openstack.org/400678 merged
- Maybe 4-6 more patches to go before work is completed.
- next patch is still WIP but a review or two wouldn't hurt: 
https://review.openstack.org/#/c/409812/
- jroll hopes to have some API patches started before the holidays

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- 12/19 status
- spec update needs reviews: https://review.openstack.org/#/c/407236
- patch for API/conductor methods needs an update, failing tests 
https://review.openstack.org/#/c/350831/
- agent driver implementation needs an update for additional tests and a 
rebase: https://review.openstack.org/#/c/400437

etags in the REST API (gzholtkevych)

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are dazzled to present this week's priorities and subteam report for Ironic. 
As usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. attach/detach: review code: https://review.openstack.org/#/c/327046/
2. portgroup: review code https://review.openstack.org/335964, then 
https://review.openstack.org/398417
3. driver composition: the next patch introduces hardware types: 
https://review.openstack.org/336626
4. next notifications: review code for CRUD notifications: 
https://review.openstack.org/#/c/356541/
5. boot from volume: next up: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691

Bugs (dtantsur)
===
- Stats (diff between 05 Dec 2016 and 12 Dec 2016)
- Ironic: 217 bugs (-2) + 231 wishlist items (+4). 7 new (-9), 183 in progress 
(+12), 3 critical (+3), 29 high (-1) and 29 incomplete (+1)
- Inspector: 11 bugs (-3) + 22 wishlist items. 0 new (-3), 12 in progress (+1), 
0 critical, 1 high and 4 incomplete (+1)
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high (-1)
- Critical bugs are related to ironicclient CI issues
- Thanks a lot JayF for your bug triaging effort

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- portgroups patches need reviews: 
https://review.openstack.org/#/q/topic:bug/1618754
- including the client!

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- (lucasagomes) No updates

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- spec was merged last week: https://review.openstack.org/299245
- RFE/patch for online-db-migration has some reviews. Need more details: 
https://bugs.launchpad.net/ironic/+bug/1585141
- Testing work:
- Tempest "smoke" tests are now passing for multi-node/multi-tenant 
with various patches!
- Grenade patch has one +2: https://review.openstack.org/407502
- Sort of blocked by tempest becoming a plugin.
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268
- Work on-going to get tempest "smoke" test working for the 
multi-node/multi-tenant job(vsaienko)

Security groups (jroll)
===
* trello: 
https://trello.com/c/klty7VVo/30-security-groups-for-provisioning-cleaning-network
- status as of most recent weekly meeting:
- last patch, documentation, merged last week: 
https://review.openstack.org/#/c/393962/

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Ironic patch up for review: 
https://review.openstack.org/#/q/topic:bug/1582188
- Patches need updating still:
- Nova - https://review.openstack.org/364413
- IronicClient - https://review.openstack.org/364420

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- API side changes for volume connector information have a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- Boot from volume/storage interface patches will be rebased this Monday.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- still on review: the patch introducing hardware types defining and 
loading: https://review.openstack.org/336626
- new on review: generic hardware types: https://review.openstack.org/400678
- Maybe 4-6 more patches to go before work is completed.

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- status as of most recent weekly meeting:
- patch for API/Conductor methods needs review: 
https://review.openstack.org/#/c/350831/

etags in the REST API (gzholtkevych)

* trello: https://trello.com/c/MbNA4geB/33-rest-api-etags
- status as of most recent weekly meeting:
- (gzholtkevych) spec needs 

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are dumbfounded to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. portgroup: review code  
https://review.openstack.org/#/q/status:open+branch:master+topic:bug/1618754
2. attach/detach: review code (after sambetts updates): 
https://review.openstack.org/#/c/327046/
3. boot from volume: next up: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691
4. next notifications: review code: 
https://review.openstack.org/#/q/topic:bug/1606520+status:open # NOTE(mariojv): 
This doesn't have all the notification patches. See subteam status report for 
links to all notification patches. (this is next, not all)
5. rolling upgrades spec needs reviews: https://review.openstack.org/#/c/299245/
6. driver composition: the next patch introduces hardware types: 
https://review.openstack.org/336626


Bugs (dtantsur)
===
- Stats (diff between 27 Nov 2016 and 05 Dec 2016)
- Ironic: 219 bugs (-15) + 227 wishlist items. 16 new (-28), 171 in progress 
(-6), 0 critical (-1), 30 high (+1) and 28 incomplete (+7)
- Inspector: 14 bugs (+2) + 22 wishlist items. 3 new, 11 in progress (+1), 2 
critical (+1), 1 high and 3 incomplete (+1)
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 1 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- portgroups patches need reviews: 
https://review.openstack.org/#/q/topic:bug/1618754
- including the client!

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- (lucasagomes): postgres job with standard PXE deployment fixed

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- spec was updated, needs reviews, is really close: 
https://review.openstack.org/299245
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268
- Work on-going to get tempest "smoke" test working for the 
multi-node/multi-tenant job(vsaienko)

Security groups (jroll)
===
* trello: 
https://trello.com/c/klty7VVo/30-security-groups-for-provisioning-cleaning-network
- status as of most recent weekly meeting:
- last patch, documentation. Needs to be rebased and reviewed: 
https://review.openstack.org/#/c/393962/

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Ironic patch up to date with latest version of spec, however we decided 
in Ironic/Neutron meeting to experiment with spliting it down for easier review 
(driver changes/RPC API changes/REST API changes)
- Ironic - https://review.openstack.org/327046
- Patches need updating still:
- Nova - https://review.openstack.org/364413
- IronicClient - https://review.openstack.org/364420

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- The majority of volume connection information patches have landed for the 
conductor.
- API side changes for volume connector information have a procedural -2 
until we can begin making use of the data in the conductor, but should stil be 
reviewed
- https://review.openstack.org/#/c/214586/
- Boot from volume/storage interface patches have been rebased and received 
updates, and now await reviews.
- 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- moved node_create to conductor
- the next patch introduces hardware types: 
https://review.openstack.org/336626

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- status as of most recent weekly meeting:
- patch for API/Conductor methods needs review: 
https://review.openstack.org/#/c/350831/

etags in the REST API (gzholtkevych)

* trello: https://trello.com/c/MbNA4geB/33-rest-api-etags
- status as of most recent weekly meeting:
- 

[openstack-dev] cancelled Re: [ironic] Ironic-qa meeting canceled this week (Nov 23rd)

[Loo, Ruby]

Hi,

In Monday's ironic meeting [1], we decided to cancel the QA meetings.

--ruby

[1] from 17:49:21, 
http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-11-28-17.00.log.html

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, November 21, 2016 at 3:29 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [ironic] Ironic-qa meeting canceled this week (Nov 
23rd)

On Mon, Nov 21, 2016 at 3:23 PM, Kurt Taylor 
> wrote:
Hey everyone, due to projected low turnout for this weeks ironic-qa meeting,
it will be canceled. I will update the wiki meeting page to reflect this.

FYI, I brought up a proposal last week to merge this meeting back into the
main Monday ironic meeting, and handle any work via sub team reports.
Comments?

As a note, this was discussed in this morning's ironic meeting,
nobody was against it. We're waiting for John V's opinion before
cancelling it for real, but everyone's comments are welcome of
course.

// jim

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are nonplussed to present this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. portgroup: review code  
https://review.openstack.org/#/q/status:open+branch:master+topic:bug/1618754
2. attach/detach: review code (after sambetts updates): 
https://review.openstack.org/#/c/327046/
3. boot from volume: review volume connection work: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231
4. next notifications: review code: 
https://review.openstack.org/#/q/topic:bug/1606520
5. rolling upgrades spec needs reviews: https://review.openstack.org/#/c/299245/
6. next driver composition patch: we need to move node_create to conductor, see 
the reasoning in the commit message: https://review.openstack.org/401311


Bugs (dtantsur)
===
- Stats (diff between 14 Nov 2016 and 21 Nov 2016)
- Ironic: 234 bugs (-4) + 220 wishlist items. 42 new (+1), 177 in progress 
(-6), 1 critical, 29 high (+2) and 21 incomplete (-2)
- Inspector: 12 bugs (-1) + 21 wishlist items. 2 new, 10 in progress (-1), 1 
critical, 1 high (-1) and 2 incomplete
- Nova bugs with Ironic tag: 10 (-1). 0 new, 0 critical, 1 high
- dtantsur is seriously behind the bug triaging due to his current assignments, 
help appreciated

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- yet another multitenancy spec update, configuration-related fields in 
portgroup objects - https://review.openstack.org/396610 -- merged, working on 
code
- portgroups patches need reviews: 
https://review.openstack.org/#/q/topic:bug/1618754

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- (lucasagomes): postgres job with standard PXE deployment fixed

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rollindg-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- spec was updated, needs reviews: https://review.openstack.org/299245
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268

Security groups (jroll)
===
* trello: 
https://trello.com/c/klty7VVo/30-security-groups-for-provisioning-cleaning-network
- status as of most recent weekly meeting:
- merged last week: https://review.openstack.org/#/c/361451/
- last patch, documentation. Needs to be rebased and reviewed: 
https://review.openstack.org/#/c/393962/

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Ironic patch up to date with latest version of spec, however we decided 
in Ironic/Neutron meeting to experiment with spliting it down for easier review 
(driver changes/RPC API changes/REST API changes)
- Ironic - https://review.openstack.org/327046
- Patches need updating still:
- Nova - https://review.openstack.org/364413
- IronicClient - https://review.openstack.org/364420

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- We have started receiving reviews and traction with the volume connection 
substrate.  The first 2 patches have landed for volume connector 
database/object entries.
- reviews needed for volume connection work: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- first patches are merged
- we need to move node_create to conductor, see the reasoning in the commit 
message: https://review.openstack.org/401311
- the (quite complex) patch introducing hardware types can use some reviews 
too: https://review.openstack.org/336626

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- status as of most recent weekly meeting:
- patch for API/Conductor methods needs review: 
https://review.openstack.org/#/c/350831/

etags in the REST API (gzholtkevych)

* trello: https://trello.com/c/MbNA4geB/33-rest-api-etags
- status as of most recent weekly 

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

Hi,

We are nonpareil in presenting this week's priorities and subteam report for 
Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and 
formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. portgroup: review code  
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1618754
2. attach/detach: review code (after sambetts updates): 
https://review.openstack.org/#/c/327046/
3. boot from volume: review volume connection work: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231
4. next notifications: review code: 
https://review.openstack.org/#/q/topic:bug/1606520
5. getting tests out of tempest tree (jroll working on code, will update when 
there's things to land)
6. next driver comp patch (database foo) to review: 
https://review.openstack.org/396681
7. rolling upgrades spec needs reviews: https://review.openstack.org/#/c/299245/


Bugs (dtantsur)
===
- Stats (diff between 14 Nov 2016 and 21 Nov 2016)
- Ironic: 238 bugs (+5) + 220 wishlist items. 41 new (+6), 183 in progress 
(+2), 1 critical, 27 high and 23 incomplete
- Inspector: 13 bugs (+1) + 21 wishlist items. 2 new, 11 in progress (+1), 0 
critical, 2 high (+1) and 2 incomplete
- Nova bugs with Ironic tag: 11. 0 new, 0 critical, 1 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- yet another multitenancy spec update, configuration-related fields in 
portgroup objects - https://review.openstack.org/396610
- portgroups patches need reviews: 
https://review.openstack.org/#/q/topic:bug/1618754
- portgroup spec (in nova) needs approval before nova spec freeze deadline 
Nov 17: https://review.openstack.org/#/c/387534/ -- APPROVED

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- (lucasagomes): postgres jobs now runs with IPMI and Standard PXE, the job 
is current broken and the patch fixing it is: 
https://review.openstack.org/#/c/399485/
- dropping ironic from tempest code still in progress, have had some back 
and forth with qa team on how to handle a particular flag

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rollindg-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- spec was updated, needs reviews: https://review.openstack.org/299245
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268
- Discovered issue in project-config settings that ironic devstack 
plugin enabled twice.
- Fix proposed: https://review.openstack.org/396802 in project-config

Security groups (jroll)
===
* trello: 
https://trello.com/c/klty7VVo/30-security-groups-for-provisioning-cleaning-network
- status as of most recent weekly meeting:
- Very close to being merged needs reviews: 
https://review.openstack.org/#/c/361451/

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Code patches need updates to align with most recent version of the spec. 
sambetts hopes to get the ironic patches updated today:
- Ironic - https://review.openstack.org/327046
- Nova - https://review.openstack.org/364413
- IronicClient - https://review.openstack.org/364420

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status as of most recent weekly meeting:
- reviews needed for volume connection work: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of most recent weekly meeting:
- first patches are merged, still a few to review and more to write
- jroll agreed to help with API part in parallel

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- status as of most recent weekly meeting:
- patch for API/Conductor methods needs review: 
https://review.openstack.org/#/c/350831/

etags in the REST API (gzholtkevych)

* trello: https://trello.com/c/MbNA4geB/33-rest-api-etags
- status as of most recent weekly meeting:
- (gzholtkevych) spec needs review: 

[openstack-dev] feedback Re: [ironic] ocata summit summary

[Loo, Ruby]

Hi,

Thanks for the great summary Jim!

As an aside (or in addition to this?), we (or maybe I should speak for myself 
only) am always interested in constructive feedback and suggestions on how we 
(as a community) can improve.

If you have ideas on how we can improve the design sessions at the summit (for 
future PTGs), please let us know.

We have an etherpad with retrospectives for Newton [1]. There isn't much 
activity there so we didn't have any meeting to discuss it. That doesn't mean, 
though, that we aren't interested. If you have ideas on how we can do better 
than in the Newton daze, please share!

--ruby

[1] https://etherpad.openstack.org/p/ironic-newton-retrospective

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, November 16, 2016 at 11:02 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [ironic] ocata summit summary

Hi all,

Sorry for the late-ness of this email, but wanted to send a wrap-up of the
Ocata summit from ironic's perspective. It was another super productive summit
and I'm thankful for all of the people who showed up and made it so. :)

As always, we discussed priorities for the cycle and those have been documented
here: 
http://specs.openstack.org/openstack/ironic-specs/priorities/ocata-priorities.html
Notes from that session are here:
https://etherpad.openstack.org/p/ironic-ocata-summit-priorities

We discussed a few specs that are up for evolving our API to be more useful
for both humans and computers. Not much contention here, they're all pretty
obvious things to do. Those notes are here:
https://etherpad.openstack.org/p/ironic-ocata-summit-api-evolution

We talked about improvements for our QA code and CI jobs. Lots of different
topics there. Most notable was agreement to consolidate some of our CI jobs
so we aren't burning a nodepool node per feature (essentially). Another
good discussion was around lack of features in Cirros holding us back. A
couple of options forward here are convincing Cirros to enable these, or
building our own image with these features built in. Notes from this session:
https://etherpad.openstack.org/p/ironic-ocata-summit-qa

Another session covered using callbacks and event handlers to handle async
actions in Neutron better. This improves those interactions by waiting until
they are done, rather than hoping things complete in time. It involves adding
code to Neutron or a Neutron plugin. Which we add code to was debated, but
Deva and I chatted with Armando later and agreed it should be okay to add it
to Neutron's tree, assuming it shares much of the code with the existing code
to do the same thing with Nova. Notes are here:
https://etherpad.openstack.org/p/ironic-ocata-summit-neutron-events

We joined the Nova team to discuss how a user might be able to define RAID
configuration during the server-create request. This ended with two options,
which Jay Pipes and Dmitry are going to explore. The first is adding to the
BDM v2 API, and the second is adding to a device metadata tag API. Ironic
will also need to expose a trait that says "can do RAID" to the resource
tracker. Last, we agreed that a flavor may have a default RAID config to be
passed to ironic. And of course, a spec will be needed. However, this work
probably won't happen until Pike or later. Notes:
https://etherpad.openstack.org/p/ironic-ocata-summit-deploy-time-raid

The task framework session discussed how we might build an API to expose
status and progress for asynchronous operations triggered by the API, as well
as returning data for actions like "send this command to the BMC". We made
some progress, there are concerns about the database schema and how we purge
old data from the DB. Notes here:
https://etherpad.openstack.org/p/ironic-ocata-summit-deploy-time-raid

Graphical consoles were another session. Much of the session was trying to
figure out how we secure things, and what should be in and out of tree.
Notes here: https://etherpad.openstack.org/p/ironic-ocata-summit-vnc-console

We spent a session figuring out what blockers exist for priorities, and how
to move around those, how to order things to avoid large conflicts, etc.
The notes are basically a plan to get each feature done. This session was
super valuable to me (and I hope, to everyone else), just to get in sync with
where everything is at.
https://etherpad.openstack.org/p/ironic-ocata-summit-unblock-priorities

Contributor meetup had three major discussions. First, our project logo. Most
folks were not huge fans of it and agreed to leave feedback. Second, what
projects belong in ironic governance or not. I sent an email about that
already: 
http://lists.openstack.org/pipermail/openstack-dev/2016-November/106569.html
Third, we decided that the entire core team should be core on specs, to increase
velocity there. I also 

[openstack-dev] [ironic] ending the API meetings

[Loo, Ruby]

Hi,

We are ending the ironic API meetings that we started in July [0]. There were 
few AND mighty meetings. I thank Devananda for an awesome job of addressing 
some major API pain points in his epic "Evolving our REST API" series of 
specifications [1]! Now we need to follow his lead and get those specs 
implemented :)

--ruby

[0] http://lists.openstack.org/pipermail/openstack-dev/2016-July/098988.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-October/105665.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] this week's priorities and subteam reports

[Loo, Ruby]

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.

NEW! Starting today, we will also include the week's priorities (also available 
from the whiteboard[0]). The priorities are decided at Monday's weekly meeting 
[1], after reviewing the subteam reports.

This Week's Priorities (as of the weekly ironic meeting)

- portgroup: review code 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1618754
- attach/detach: review code (after sambetts updates): 
https://review.openstack.org/#/c/327046/
- boot from volume: review volume connection work: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231
- next notifications: review code: 
https://review.openstack.org/#/q/topic:bug/1606520
- root device hints: review code (after lucasagomes updates): 
https://review.openstack.org/#/c/386714/
- getting tests out of tempest tree
- next driver comp patch (database foo) to review: 
https://review.openstack.org/396681
- rolling upgrades spec needs reviews: https://review.openstack.org/#/c/299245/

Bugs (dtantsur)
===
- Stats (diff between 07 Nov 2016 and 14 Nov 2016)
- Ironic: 233 bugs + 220 wishlist items (+2). 35 new (+2), 181 in progress 
(+1), 1 critical, 27 high (-1) and 23 incomplete
- Inspector: 12 bugs (-1) + 21 wishlist items. 2 new (-1), 10 in progress (+1), 
0 critical, 1 high and 2 incomplete (-1)
- Nova bugs with Ironic tag: 11. 0 new (-1), 0 critical, 1 high

Portgroups support (sambetts, vdrok)

* trello: https://trello.com/c/KvVjeK5j/29-portgroups-support
- status as of most recent weekly meeting:
- yet another multitenancy spec update, configuration-related fields in 
portgroup objects - https://review.openstack.org/396610
- portgroups patches need reviews: 
https://review.openstack.org/#/q/topic:bug/1618754
- portgroup spec (in nova) needs approval before nova spec freeze deadline 
Nov 17: https://review.openstack.org/#/c/387534/

CI refactoring (dtantsur, lucasagomes)
==
* trello: https://trello.com/c/c96zb3dm/32-ci-refactoring
- status as of most recent weekly meeting:
- (lucasagomes) Gate has switched jobs to run on Xenial + ipmitool (merged 
already)
- (dtantsur) Making more jobs voting: 
https://review.openstack.org/#/c/397164/
- (lucasagomes) Patch to disable iPXE in favor of testing standard PXE in 
the postgres job: https://review.openstack.org/#/c/397129/
- (lucasagomes) Patch to switch the postgres job to ipmitool: 
https://review.openstack.org/#/c/397160/
- 2016-11-08: pep8 jobs (jlvillal): 
http://lists.openstack.org/pipermail/openstack-dev/2016-November/106668.html
- ironic-python-agent passes new pep8 job: 
http://logs.openstack.org/23/395123/2/experimental/experimental-ironic-python-agent-pep8-ubuntu-xenial/b8e761c/
- ironic passes new pep8 job: 
http://logs.openstack.org/02/395102/3/experimental/experimental-ironic-pep8-ubuntu-xenial/891b1ce/
- python-ironicclient passes new pep8 job: 
http://logs.openstack.org/99/382999/4/experimental/experimental-python-ironicclient-pep8-ubuntu-xenial/5c78e08/
- ironic-inspector passes new pep8 job: 
http://logs.openstack.org/98/395598/1/experimental/experimental-ironic-inspector-pep8-ubuntu-xenial/0ea1c1a/

Rolling upgrades and grenade-partial (rloo, jlvillal)
=
* trello: 
https://trello.com/c/GAlhSzLm/2-rollindg-upgrades-and-grenade-with-multi-node
- status as of most recent weekly meeting:
- spec was updated, needs reviews: https://review.openstack.org/299245
- Work is ongoing for enabling Grenade with multi-tenant: 
https://review.openstack.org/389268
- Discovered issue in project-config settings that ironic devstack 
plugin enabled twice.
- Fix proposed: https://review.openstack.org/396802 in project-config

Security groups (jroll)
===
* trello: 
https://trello.com/c/klty7VVo/30-security-groups-for-provisioning-cleaning-network
- status as of most recent weekly meeting:
- Very close to being merged needs reviews: 
https://review.openstack.org/#/c/361451/

Interface attach/detach API (sambetts)
==
* trello: https://trello.com/c/nryU4w58/39-interface-attach-detach-api
- status as of most recent weekly meeting:
- Spec merged and Nova BP approved
- Code patches need updates to align with most recent version of the spec
- Ironic - https://review.openstack.org/327046
- Nova - https://review.openstack.org/364413
- IronicClient - https://review.openstack.org/364420

Generic boot-from-volume (TheJulia)
===
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- 

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

We are nonchalant 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 between 31 Oct 2016 and 07 Nov 2016)
- Ironic: 233 bugs + 218 wishlist items (+7). 33 new, 180 in progress (+5), 1 
critical, 28 high (-1) and 23 incomplete (+4)
- Inspector: 13 bugs + 21 wishlist items. 3 new (-1), 9 in progress, 0 
critical, 1 high and 3 incomplete
- Nova bugs with Ironic tag: 11. 1 new, 0 critical, 1 high

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- status: portgroups patches need reviews: 
https://review.openstack.org/#/q/topic:bug/1618754
- portgroup spec (in nova) needs approval before nova spec freeze deadline Nov 
17: https://review.openstack.org/#/c/387534/
- Attach/Detach spec needs approval https://review.openstack.org/#/c/317636/ to 
be accepted by Nova folks (nova BP is ready to be approved, waiting on ironic 
spec being approved; see 14:39 at 
http://eavesdrop.openstack.org/meetings/nova/2016/nova.2016-11-03-14.00.log.html)

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- lucas is working on switching the CI to pxe_ipmitool completely
- multi-node CI job: devstack-gate patches landed last week. Still a few 
non-Ironic patches to get landed.
- Proposed improvements to the devstack plugin BM network simulation (should 
make multitenancy testing and grenade testing less crappy): 
https://review.openstack.org/#/c/392959/ (sambetts)

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- status: Specification has landed.
- reviews needed for volume connection work: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- status: driver composition spec was amended to cover the defaults
- the first patches are posted, still a lot of ahead: 
https://review.openstack.org/#/q/status:open+topic:bug/1524745

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- Provision state change notifications need reviews: 
https://review.openstack.org/#/c/348437/

Rolling upgrades and grenade-partial (xek)
==
* trello: https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-partial
- spec needs to be updated

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- Pretty much completed, only docs missing: 
https://review.openstack.org/#/c/386714/

Drivers:

DRAC (mgould/lucas/dtantsur)

- dtantsur is fixing a few bugs in python-dracclient, then firing a release
- per summit discussion, python-dracclient may leave ironic governance

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weakly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 17 Oct 2016 and 31 Oct 2016)
  - Ironic: 233 bugs (+9) + 211 wishlist items (+2). 33 new (+10), 175 in 
progress (+4), 1 critical, 29 high (-1) and 19 incomplete (-1)
  - Inspector: 13 bugs (+3) + 21 wishlist items (+2). 4 new (+3), 9 in 
progress, 0 critical, 1 high and 3 incomplete (+2)
  - Nova bugs with Ironic tag: 11. 1 new, 0 critical, 1 high
- dtantsur will try to return to speed with bug triaging after the summit :(
- the critical bug is the neutron pool issue (has workaround in place right 
now):
  - https://bugs.launchpad.net/ironic-python-agent/+bug/1629133
  - the workaround was removed, and I've heard we got broken again, confirming 
right now

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- no updates, but we've recapped our plans on the summit

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Specification has been updated:
- https://review.openstack.org/#/c/294995/

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- dtantsur has overtaken the driver composition spec amendment, new revision 
posted:
- https://review.openstack.org/357262

Bifrost (TheJulia)
==
- Bifrost's CI is presently broken due to an issue with upper-constraints not 
being used, however that has exposed another issue that we are presently 
investigating.

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] next meeting is a spooky one

[Loo, Ruby]

Hi,

Since the Barcelona summit is next week, the Monday (Oct 24) ironic meeting is 
cancelled.

We'll have a spooky meeting the week after (Oct 31). Feel free to come in 
costumes :)

--ruby
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hello ironic'ers,

For the design sessions to be as productive as possible, please prepare 
beforehand so that the sessions are spent discussing and coming up with 
solutions/consensus, instead of describing and getting folks up-to-speed on the 
issues.

Feel free to add your comments directly in the etherpads (or as reviews in any 
proposed patches). This will be especially useful for people that cannot attend 
the sessions.

Thanks!

--ruby

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, October 11, 2016 at 8:53 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [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 one of the sessions, please do start filling in the
etherpad with proposals and references.

Thanks!

// jim

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Core team updates

[Loo, Ruby]

Chris and Haomeng, thanks for your past reviews and I look forward to your 
return to the core team.

For the folks that are clearly reviewing far more than others, what do you 
think about asking them not to review so much? I'd vote for that :)

--ruby

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, October 17, 2016 at 6:09 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [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 folks may have commitments outside of ironic, I'd like to ask
everyone to be mindful of their review quantity (and always quality, of
course). :)

Reviews for the ironic umbrella in the last 90 days:
http://stackalytics.com/report/contribution/ironic-group/90

A good rule of thumb to try to meet is 3 reviews/day, which our top 8
reviewers are meeting (admittedly I am not).

There's also a couple people that haven't been active in the project
for quite a while that I'm dropping today:

Chris Krelle (NobodyCam)
Haomeng Wang (haomeng)

Of course, we welcome both of you back quickly if your activity picks
back up. :)

// jim

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 10 Oct 2016 and 17 Oct 2016)
- Ironic: 224 (+8) bugs + 209 wishlist items (-3). 23 new (+8), 171 in progress 
(-2), 1 critical, 30 high and 20 incomplete (+1)
- Inspector: 10 bugs (-1) + 19 wishlist items. 1 new, 9 in progress (-1), 0 
critical, 1 high and 1 incomplete
- Nova bugs with Ironic tag: 11 (+1). 1 new (+1), 0 critical, 1 high
- the critical bug is the neutron pool issue (has workaround in place right 
now):
- https://bugs.launchpad.net/ironic-python-agent/+bug/1629133
- seems like they've merged a fix, we should try removing the work around:
- https://review.openstack.org/#/c/381965/

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- ironic-lib was successfully moved to xenial, and finally has some good 
coverage
- I've proposed a plan on our CI jobs refactoring: 
http://lists.openstack.org/pipermail/openstack-dev/2016-October/105558.html

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Specification in need of reviews: https://review.openstack.org/#/c/294995/

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- dtantsur has reviewed the spec update. lgtm, but needs clarification a bit.

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- Power state change notifications currently merging: 
https://review.openstack.org/#/c/321865/
- Spec for CRUD notifications, provision state change notifications, and 
maintenance notifications landed: https://review.openstack.org/#/c/347242/
- Code still needing review
- https://review.openstack.org/#/c/348437/
- https://review.openstack.org/#/c/356541/ (currently workflow -1)

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- nova patch merged last Friday: https://review.openstack.org/#/c/328157/
- DONE \o/

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- The code is merged in all involved projects: Ironic, IPA and ironic-lib
- Missing documentation: https://review.openstack.org/#/c/386714/

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- no updates, hacking on :) ++ lol

Bifrost (TheJulia)
==
- Keystone support and support for enabling inspector to enroll discovered 
hardware currently in review.

.

Until the week after the summit,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 03 Oct 2016 and 10 Oct 2016)
- Ironic: 216 bugs (+11) + 212 wishlist items. 15 new (+9), 173 in progress 
(+4), 2 critical (+2), 30 high (-2) and 19 incomplete (+1)
- Inspector: 11 bugs (-3) + 19 wishlist items. 1 new, 10 in progress (-3), 0 
critical, 1 high (-3) and 1 incomplete
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 1 high
- critical bugs:
- https://bugs.launchpad.net/ironic-python-agent/+bug/1629133 external 
connectivity broken by neutron, temporary worked around in IPA
- https://bugs.launchpad.net/ironic/+bug/1631875 move to Xenial is blocked by 
misbehaving iSCSI deploy, temporary worked around by reverting move to Xenial, 
still needs urgent fixing

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- now we run all combinations of drivers and image types in ironic-lib gate
- our move to Xenial is BLOCKED by 
https://bugs.launchpad.net/ironic/+bug/1631875 and we need someone looking into 
it (Lucas volunteered, but we could use more eyes on it as well)

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- No updates, still need reviews

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- no updates, still needs review in nova

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- no updates, some spec review is happening
- resulting maybe in an API WG suggestion: 
https://review.openstack.org/#/c/383862/

Bifrost (TheJulia)
==
- Reviews to allow a bifrost deployment to leverage keystone have been posted.

.

Until next week,
--ruby



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 26 Sep 2016 and 03 Oct 2016)
- Ironic: 205 bugs (+10) + 212 wishlist items (-4). 6 new (+6), 169 in progress 
(+10), 0 critical, 32 high (+1) and 18 incomplete (+1)
- Inspector: 14 bugs (+3) + 19 wishlist items. 1 new, 13 in progress (+3), 0 
critical, 4 high (+3) and 1 incomplete
- Nova bugs with Ironic tag: 10 (+4). 0 new, 0 critical, 1 high (+1)

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- no updates from dtantsur
- (lucasagomes) UEFI tests works but currently "blocked" by cirros not 
supporting UEFI in the latest release, see: 
https://bugs.launchpad.net/ironic/+bug/1625616

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- TheJulia will be rebasing/updating revisions this week.

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- Power state notifications patch is close: 
https://review.openstack.org/#/c/321865/
- CRUD notification spec needs reviewer attention: 
https://review.openstack.org/#/c/347242/

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- Nova patch: needs review https://review.openstack.org/#/c/328157/
- ironic bug: needs review https://review.openstack.org/#/c/363647/

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- Waiting on a ironic-lib release
  (jroll) release team won't do release until next week (after final Newton 
releases this week)

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- a patch is up to move all inspector tempest jobs to Xenial
- LLDP bits for the python-ironic-inspector-client: 
https://review.openstack.org/#/c/374381/ (spec)

Bifrost (TheJulia)
==
- Currently working towards support of keystone based authentication.

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] install guide has moved

[Loo, Ruby]

Hi Andreas,

Because you asked so nicely, tada: 
http://docs.openstack.org/project-install-guide/baremetal/newton/

Also, thanks for clarifying about ../draft/.. !

--ruby

From: Andreas Jaeger 
Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard, 
Graham Norton , HRB 21284 (AG Nuernberg)
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, September 27, 2016 at 11:04 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [ironic] install guide has moved

On 2016-09-27 17:02, Andreas Jaeger wrote:
On 2016-09-27 16:54, Ruby Loo wrote:
Hi,



Thanks to the huge efforts put in by Mathieu Mitchell (mat128) and Jay
Faulkner (JayF), we've moved ironic's install guide from the developer
documentation to the official openstack site [1]. Isn't it a beauty? :D



Please update your bookmarks to point to the new location, and help us
improve the install guide by providing feedback and submitting patches.



--ruby



[1] http://docs.openstack.org/project-install-guide/baremetal/draft/
Be aware that this is the draft location - the version from master, so
this will soon be the Ocata version.
Once newton is released, docs.openstack.org will point to the Newton
version which is published from stable/newton branch already to:
http://docs.openstack.org/project-install-guide/baremetal/newton/

Oh, the draft version is really a beauty. Can you backport that to
newton, please?

Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] install guide has moved

[Loo, Ruby]

Hi,

Thanks to the huge efforts put in by Mathieu Mitchell (mat128) and Jay Faulkner 
(JayF), we've moved ironic's install guide from the developer documentation to 
the official openstack site [1]. Isn't it a beauty? :D

Please update your bookmarks to point to the new location, and help us improve 
the install guide by providing feedback and submitting patches.

--ruby

[1] http://docs.openstack.org/project-install-guide/baremetal/draft/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Summit session planning

[Loo, Ruby]

Also, as part of this reminder. If you add a proposal to the etherpad, please 
put your name/NIC next to it so we know who added it/is going to lead it. 
Bruno, I added your name to #12 & 13 :)

Thanks,
--ruby

From: Jim Rollenhagen 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, September 27, 2016 at 9:47 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [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 we should try to get them all up this week, start talking about
what we do and don't want in next Monday's meeting, iterate, and make final
decisions in the following meeting (October 10).

Please get things in and start thinking about what we want to accept
by Monday. Thanks!

// jim

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

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 there 
other information there that might be useful? I'm not totally sure what 
notifications will be used for; it is somewhat hard to assume.

I suppose we could look at it this way, since you and Mario are fine without 
those two. If no one speaks up wanting them, then we'll do as you propose, and 
not expose those two fields.

--ruby


From: Yuriy Zveryanskyy 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, September 27, 2016 at 7:00 AM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [ironic] base node payload for notification

Hi,
there is a discussion starting in comment on 
https://review.openstack.org/#/c/321865/
I agree with Ruby Loo proposal about a base node payload.
Currently we have these node's fields exposed via API (in alphabetical order):

"chassis_uuid", "clean_step", "console_enabled", "created_at",  "driver",
"driver_info", "driver_internal_info", "extra", "inspection_finished_at",
"inspection_started_at", "instance_info", "instance_uuid", "last_error",
"maintenance", "maintenance_reason", "name", "network_interface",
"power_state", "properties", "provision_state", "provision_updated_at",
"raid_config", "reservation", "resource_class", "target_power_state",
"target_provision_state", "target_raid_config", "updated_at", "uuid"
In my opinion these field should be excluded from base node payload:

"chassis_uuid": it not represents node state, not changed too often, additional
DB SELECT will be needed for base payload
"driver_info": it not represents node state, contains only driver settings and
secrets like IPMI passwords
"driver_internal_info": it's driver internal info
"instance_info": configdrive blob can be saved inside
"raid_config": it's hardware related
"reservation": it's not independent changed fields, only lock flag
"target_raid_config": it's hardware related
And resulting base payload fields list (for version 1.0):

"clean_step", "console_enabled", "created_at",  "driver", "extra",
"inspection_finished_at", "inspection_started_at", "instance_uuid",
"last_error", "maintenance", "maintenance_reason", "name",
"network_interface", "power_state", "properties", "provision_state",
"provision_updated_at", "resource_class", "target_power_state",
"target_provision_state", "updated_at", "uuid"

Any other suggestions are welcome.
Yuriy Zveryanskyy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 16 Sep 2016 and 26 Sep 2016)
- Ironic: 195 bugs (+9) + 216 wishlist items (+1). 0 new (-1), 159 in progress 
(+14), 0 critical, 31 high (-1) and 17 incomplete (+2)
- Inspector: 11 bugs + 19 wishlist items (+1). 1 new, 10 in progress (-2), 0 
critical, 1 high (-1) and 1 incomplete
- Nova bugs with Ironic tag: 6 (-2). 0 new, 0 critical, 0 high

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- switching jobs to xenial is still in progress
- one non-voting inspector job was switched
- vasyl to switch other non-voting jobs

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- Small spec updates landed
- Patches still pending review:
- https://review.openstack.org/#/c/347242/ yuriyz has a spec up for 
CRUD notifications, needs reviewers
- https://review.openstack.org/#/c/321865/ power state notifications 
ready for review; oustanding issues seem to be related to deciding on what to 
include in payload

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console- Nova patch: needs 
review (Ocata is open)  https://review.openstack.org/#/c/328
157/
- ironic bug: needs review https://review.openstack.org/#/c/363647/

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- Ocata is now open, waiting on a ironic-lib release to unblock https://review.o
penstack.org/#/c/366742/

Install guide migration (JayF and mat128)
=
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- Waiting for https://review.openstack.org/#/c/376603/ "Skip slow ironic tests o
n install-guide changes"
- otherwise, the patches are ready to land :)

Inspector (dtansur)
===
- we've made the final release, thanks all
- we've got a tempest equivalent of all our bash-based jobs
- I've just switched the non-voting discovery job to Xenial to see if it 
works
- if it does, it will be the last to replace the bash job
- early ocata changes that need attention/are good to review:
- the states patch (HA)
- Listing introspection statuses endpoint spec

Bifrost (TheJulia)
===
- Documentation on how to pronounce Bifrost merged :)

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 12 Sep 2016 and 16 Sep 2016)
  - Ironic: 186 bugs (-69) + 215 wishlist items (+2). 1 new (-40), 145 in 
progress (-36), 0 critical, 32 high (-3) and 15 incomplete (-1)
  - Inspector: 11 bugs + 18 wishlist items (-2). 1 new, 12 in progress, 0 
critical, 2 high and 1 incomplete
  - Nova bugs with Ironic tag: 8 (-1). 0 new, 0 critical, 0 high
- the bug smash was a fantastic success, let's have it from time to time
- dtantsur on PTO Sep 19-20, so the stats are from Friday

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- we've reduced the number of unused jobs we generate in project-config
- one missing job was spotted and added: pxe_ssh + whole disk image (and it 
seems to pass!)
- TODO: make it voting after some time
- vsaienk0 is working on experimental job using Xenial
- Patches proposed to get ironic-multinode job workiing.

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- power state notifications: https://review.openstack.org/#/c/321865/ needs 
more work and reviews

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- It's been postponed to Ocata, but the base patches for ironic-lib is already 
merged
- A -2 patch waiting for Ocata to open is already proposed: 
https://review.openstack.org/#/c/366742/

Install guide migration (JayF and mat128)
=
- https://review.openstack.org/#/q/topic:bug/1612278

Inspector (dtansur)
===
- we've worked around a problem with grenade, so we're landing the last patches 
for Newton
- we've moved all our jobs except for discovery one to grenade (incl. nv jobs 
on ironic and IPA)
- we plan on moving the discovery job too before stable/newton

Drivers:

DRAC (mgould/lucas)
---
- ifarkas has left RH, our new contact for the driver is mgould

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 29 Aug 2016 and 12 Sep 2016)
- Ironic: 255 bugs (+21) + 213 wishlist items (-1). 41 new (+8), 181 in 
progress (+11), 0 critical, 35 high (+1) and 16 incomplete (-1)
- Inspector: 11 bugs (+1) + 20 wishlist items. 1 new, 12 in progress (+3), 0 
critical, 2 high (+1) and 1 incomplete (-1)
- Nova bugs with Ironic tag: 9 (-1). 0 new, 0 critical, 0 high

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- Infra has asked us to fix the list of jobs we're generating. dtantsur is 
handling it
- Infra also wants us to move to Xenial from Newton on

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- will get back to it in Ocata (which is soon!)

OpenStackClient plugin for ironic (dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- "done". The OSC commands are 98 (+-1.999%) complete and in 
python-ironicclient 1.7.0
- update to spec to reflect reality: https://review.openstack.org/#/c/363921/
- bugs/rfes have been opened for remaining commands (that rloo is aware of)
- will remove this subteam item after today's meeting

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- we should try to merge them this week IMO

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- the only remaining bit is the preventative unit test that would prevent 
future API changes from landing without a policy check

Active node creation (TheJulia)
===
* trello: https://trello.com/c/BwA91osf/22-active-node-creation
- New revision of the tempest tests should be expected later today.

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- Nova patch: in review(unfortunately, removing -2 by Matt was mistake??)
- Ironic patches: merged

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- It's been postponed to Ocata, but the base patches for ironic-lib is already 
merged
- A -2 patch waiting for Ocata to open is already proposed: 
https://review.openstack.org/#/c/366742/

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- our grenade job has been down due to a failure in network_basic_ops test
- we had to hack on our test runner to disable this test until we find a 
sane way to fix it
- otherwise we're ready for the release

Install guide migration (JayF and mat128)
=
- Plan and progress: 
https://etherpad.openstack.org/p/ironic-install-guide-migration-plan
- Initial docs published: 
http://docs.openstack.org/project-install-guide/baremetal/draft/ yay!
- 2 reviews in-flight for importing existing content
- https://review.openstack.org/#/q/topic:bug/1612278

Cross-project:
==
- Infra insists on switching new jobs to Xenial

Drivers:

OneView (gabriel-bezerra/thiagop/xavierr)
-
- Inband inspection
- RFE: https://bugs.launchpad.net/ironic/+bug/1621530
- Code: https://review.openstack.org/367065
- CI server is down -- we're working on fixing it (2016-09-09)

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] should we provide 'ironic node-list --chassis' and 'ironic port-list --node' commands?

[Loo, Ruby]

Hi,

Vlad was the only one that was luke-warm in favour of 'ironic node-list 
--chassis'. Since I haven't received any positive, enthusiastic comment about 
wanting it, I don't think it is worth spending any more time pursuing it.

'openstack baremetal node list --chassis' does exist though (in 1.7.0 [1]).

--ruby

[1] http://docs.openstack.org/releasenotes/python-ironicclient/newton.html


On 2016-08-30, 11:57 AM, "Vladyslav Drok" 
<vd...@mirantis.com<mailto:vd...@mirantis.com>> wrote:

The ironic node-list --chassis seems to be easier to understand for me. I've 
commented on one of the patches that maybe we should deprecate the 
chassis-node-list if we add this, but then, the deprecation is slow, we have 
some functional tests already... Having two commands kind of reflects the 
duplication in our API, where we can do /chassis//nodes and 
/nodes?chassis_uuid=, so maybe having both of them is fine.

Vlad

On Mon, Aug 29, 2016 at 7:22 PM, Loo, Ruby 
<ruby@intel.com<mailto:ruby@intel.com>> wrote:
Hi,

While working on the openstackclient plugin commands for ironic, I was thinking 
about the equivalents for 'ironic chassis-node-list' (nodes that are part of 
specified chassis) and 'ironic-node-port-list' (ports that are part of 
specified node). It didn't make sense to me to have an 'openstack baremetal 
chassis node list', since a 'chassis' and a 'node' are two different objects in 
osc lingo and we already have 'openstack baremetal chassis xx' and 'openstack 
baremetal node yy' commands. Furthermore, our REST API supports 'GET 
/v1/nodes?chassis=c1' and 'GET /v1/ports?node=n1'.

So I proposed 'openstack baremetal node list --chassis' and 'openstack 
baremetal port list --node' [1]. To implement this, I need to enhance our 
corresponding python APIs. The question I have is whether we want to only 
enhance the python API, or also provide 'ironic node-list --chassis' and 
'ironic port-list --node' commands. The latter is being proposed [2] and coded 
at [3]. Doing this would mean two different ironic CLIs to do the same thing, 
but also provide a more obvious 1:1 correspondence between ironic & osc 
commands, and between ironic CLI and python API.

Thoughts?

It'd be great if we could decide in the next day or so, in order to get the 
osc-related commands into the client this week for the Newton release.

--ruby

[1] 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/ironicclient-osc-plugin.html#openstack-baremetal-node
[2] https://launchpad.net/bugs/1616242
[3] https://review.openstack.org/#/c/359520/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic][OpenStackClient] two openstack commands for the same operation?

[Loo, Ruby]

Hi,

Thanks for everyone's comments. Dean's were very useful, I'm going to file 
those away for future commands.

In this case, I think we'll go with 'passthru' since I do want to make life 
easier for the operators :)

--ruby

On 2016-08-29, 12:00 PM, "Jay Faulkner" <j...@jvf.cc<mailto:j...@jvf.cc>> wrote:


On Aug 29, 2016, at 8:19 AM, Dean Troyer 
<dtro...@gmail.com<mailto:dtro...@gmail.com>> wrote:

On Mon, Aug 29, 2016 at 9:41 AM, Loo, Ruby 
<ruby@intel.com<mailto:ruby@intel.com>> wrote:
I did this because 'passthrough' is more English than 'passthru' and I thought 
that was the 'way to go' in osc. But some folks wanted it to be 'passthru' 
because in ironic, we've been calling them 'passthru' since day 2.

Our default rule is to use proper spellings and not abbreviations[0].  The 
exceptions we have made are due to either a) significant existing practice in 
the industry (outside OpenStack, mostly in the network area so far); and b) 
when the user experience is clearly improved.

To be clear; thru is a valid english word, in just about every dictionary I've 
checked. In fact, some evidence shows it predates "through" as a word. I agree 
with other folks who have posted on the mailing list that keeping "passthru" is 
going to be more clear to operators of ironic than changing it to "passthrough" 
in this single context.

Thanks,
Jay Faulkner
OSIC


You might notice that calling out prior OpenStack usage is absent from that 
list.  One of the tenets of OSC from the start is to look first at user 
experience and identifying a _single_ set of terminology.  An existing practice 
can fall under (b) when it is compelling overall, and is an easier case to make 
when there is no competing OSC usage, or other OSC usage matches.

Unfortunately, I wasn't able to make everyone happy because someone else thinks 
that we shouldn't be providing two different openstack commands that provide 
the same functionality. (They're fine with either one, just not both.)

I agree with not aliasing commands out of the box.  We'll do that for 
deprecations, and are looking at a generalize alias method for other reasons, 
but on initial implementation I would prefer to not do this.

What do the rest of the folks think? Some guidance from the OpenStackClient 
folks would be greatly appreciated.

I would suggest you pick the one that lines up with usage outside OpenStack, in 
the sorts of ways that our users would be familiar with[1].  In this case, a 
grep of help output of even 'passthr' will find the match.

Hopefully this all makes enough sense that we can add it as a guideline to the 
OSC docs.  Feedback welcome.

Thanks
dt

[0] Where 'proper' is usually North American English, for whatever definition 
of that we have. This is totally due to me not thinking far enough ahead 4 
years ago...

[1] Cases like "all other clouds use this term" or "it is the common way to 
refer to this resource in the networking field" have been used in the past.

--
Dean Troyer
dtro...@gmail.com<mailto:dtro...@gmail.com>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly subteam report

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 22 Aug 2016 and 29 Aug 2016)
- Ironic: 234 bugs (+11) + 214 wishlist items (+3). 33 new (+7), 170 in 
progress (+6), 0 critical (-1), 34 high and 17 incomplete (+1)
- Inspector: 10 bugs (+1) + 20 wishlist items. 1 new (+1), 9 in progress, 0 
critical, 1 high and 2 incomplete
- Nova bugs with Ironic tag: 10. 0 new, 0 critical, 0 high

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- Patch to allow constraints to be used for ramdisk: 
https://review.openstack.org/358855

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Spec needs reviews: https://review.openstack.org/#/c/294995/
- Volume connector information revisions to be rebased this week 
(https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526231)

OpenStackClient plugin for ironic (dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- patches for review: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526479
- 'passthru' vs 'passthrough' for eg 'openstack baremetal node passthru list'. 
Going to only use 'passthru' : 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/102449.html
- providing 'openstack baremetal node list --chassis' & 'openstack baremetal 
port list --node'. Should we provide 'ironic node list --chassis' and 'ironic 
port list --node' ? : 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/102461.html
- some discrepancies/bugs wrt existing osc commands, will push up some patches 
(hopefully in next 2 days) [rloo]

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- 8/29/2016 update
- Notification base classes and docs patch merged
- Power state notification patch needs reviews

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- patch to apply policy to /heartbeat - https://review.openstack.org/353696 
(more related to agent API promotion)
- https://review.openstack.org/#/c/350177/ (Add test to ensure policy is always 
authorized)
- otherwise done!

Active node creation (TheJulia)
===
* trello: https://trello.com/c/BwA91osf/22-active-node-creation
- New revision of the tempest tests should be expected later today.

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- documentation: merged https://review.openstack.org/#/c/293872/
- nova patch: needs review https://review.openstack.org/#/c/328157/  (-2ed 
again). Will have to wait til Ocata.

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- Two patches for ironic-lib ready to review (they address the white space 
problem from last week): https://review.openstack.org/#/c/348953/1 and 
https://review.openstack.org/#/c/358000/

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- no updates, releases are coming soon
- states patch needs deciding whether to land before Feature freeze 
https://review.openstack.org/#/c/348943/ (milan)

Bifrost (TheJulia)
==
- Will be cutting a release this week.

.

Until next week (or the week after, if next week's meeting doesn't happen),
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard
~


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] should we provide 'ironic node-list --chassis' and 'ironic port-list --node' commands?

[Loo, Ruby]

Hi,

While working on the openstackclient plugin commands for ironic, I was thinking 
about the equivalents for 'ironic chassis-node-list' (nodes that are part of 
specified chassis) and 'ironic-node-port-list' (ports that are part of 
specified node). It didn't make sense to me to have an 'openstack baremetal 
chassis node list', since a 'chassis' and a 'node' are two different objects in 
osc lingo and we already have 'openstack baremetal chassis xx' and 'openstack 
baremetal node yy' commands. Furthermore, our REST API supports 'GET 
/v1/nodes?chassis=c1' and 'GET /v1/ports?node=n1'.

So I proposed 'openstack baremetal node list --chassis' and 'openstack 
baremetal port list --node' [1]. To implement this, I need to enhance our 
corresponding python APIs. The question I have is whether we want to only 
enhance the python API, or also provide 'ironic node-list --chassis' and 
'ironic port-list --node' commands. The latter is being proposed [2] and coded 
at [3]. Doing this would mean two different ironic CLIs to do the same thing, 
but also provide a more obvious 1:1 correspondence between ironic & osc 
commands, and between ironic CLI and python API.

Thoughts?

It'd be great if we could decide in the next day or so, in order to get the 
osc-related commands into the client this week for the Newton release.

--ruby

[1] 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/ironicclient-osc-plugin.html#openstack-baremetal-node
[2] https://launchpad.net/bugs/1616242
[3] https://review.openstack.org/#/c/359520/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic][OpenStackClient] two openstack commands for the same operation?

[Loo, Ruby]

Hi,

In ironic, we have these ironic CLI commands:
- ironic node-vendor-passthru (calls the specified passthru method)
- ironic node-get-vendor-passthru-methods (lists the available passthru methods)

For their corresponding openstackclient plugin commands, we (I, I guess) have 
proposed [1]:
- openstack baremetal node passthrough call
- openstack baremetal node passthrough list

I did this because 'passthrough' is more English than 'passthru' and I thought 
that was the 'way to go' in osc. But some folks wanted it to be 'passthru' 
because in ironic, we've been calling them 'passthru' since day 2. To make 
everyone happy, I also proposed (as aliases):

- openstack baremetal node passthru call
- openstack baremetal node passthru list

Unfortunately, I wasn't able to make everyone happy because someone else thinks 
that we shouldn't be providing two different openstack commands that provide 
the same functionality. (They're fine with either one, just not both.)

What do the rest of the folks think? Some guidance from the OpenStackClient 
folks would be greatly appreciated.

--ruby


[1] 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/ironicclient-osc-plugin.html




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] ideas for Ocata summit sessions

[Loo, Ruby]

Hi,

Start getting those ironic juices flowing! We've got an etherpad [1] ready to 
capture your ideas for the Ocata summit sessions. As discussed in today's 
meeting [2], in next Monday's ironic meeting [3] we will decide on the number 
of fishbowl and workroom sessions, and the ideas submitted by then will help 
inform our decision.

Thanks,
--ruby

[1] https://etherpad.openstack.org/p/ironic-ocata-summit
[2] 
http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-08-22-17.00.log.html#17:20:20
[3] 
https://wiki.openstack.org/wiki/Meetings/Ironic#Weekly_Ironic_Project_Team_Meeting


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between 15 Aug 2016 and 22 Aug 2016)
- Ironic: 223 bugs (-9) + 211 wishlist items (+12). 26 new (-10), 164 in 
progress (+4), 1 critical (+1), 34 high (+1) and 16 incomplete (-3)
- Inspector: 9 bugs + 20 wishlist items. 0 new, 9 in progress, 0 critical, 1 
high (-1) and 2 incomplete
- Nova bugs with Ironic tag: 11. 0 new, 0 critical, 0 high
- a critical bug:
  - IPA for stable/liberty unit tests fail with AssertionError: InspectionError 
not raised by extension_manager
  - https://bugs.launchpad.net/ironic-python-agent/+bug/1611528
  - Patch proposed to use constraints: https://review.openstack.org/#/c/353124/
  - mat128 has volunteered to fix the Dockerfile issue. Proposing patch to 
master and then getting it backported to stable releases.

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- portgroups patches still in review
- patch for security groups for provisioning network coming this week

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- No updates from dtantsur

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Boot from Volume specification has received minor updates in the last week, 
reviews required: https://review.openstack.org/#/c/294995/
- Substrate volume connection information changes still in review.

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- a spec update is proposed (thanks TheJulia): 
https://review.openstack.org/357262

OpenStackClient plugin for ironic (dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- 'openstack baremetal create' merged
- a few commands are still on review
- chassis https://review.openstack.org/345815
- a few commands need fixing and/or rebasing:
- port list https://review.openstack.org/346722
- port delete https://review.openstack.org/346075
- driver https://review.openstack.org/350050
- outstanding patches: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526479
- there are some more node-related commands that have not been coded yet (rloo 
did a diff last week)
- e.g. validate

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- August 22, 2016
- Base patch updated
- https://review.openstack.org/#/c/298461
- Previously had 2 +2s, but 1 was removed. Needs re-review after update 
this morning.

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- "mask secrets in API responses" generated some debate, still not merged
- https://review.openstack.org/#/c/326768/

Active node creation (TheJulia)
===
* trello: https://trello.com/c/BwA91osf/22-active-node-creation
- Proposed tempest changes have received feedback.  New revision should be 
expected Monday.

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- documentation: needs review (got +2)  https://review.openstack.org/#/c/293872/
- nova patch: needs review https://review.openstack.org/#/c/328157/

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- 2 patches for review in ironic-lib (https://review.openstack.org/#/c/348953/ 
https://review.openstack.org/#/c/358000/). But currently stuck in a problem 
where oslo_utils.specs_matcher.match() does not handle spaces, which is needed 
for backward compat in Ironic

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- The grenade job is voting on ironic-inspector now \o/
- Now we only need upgrade documentation to claim assert:supports-upgrade 
tag
- volunteers needed for ^^^
- Still working on migrating our bash-based gate to tempest
- tempest job for the client: https://review.openstack.org/358663

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

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

[Loo, Ruby]

Hi,

I admit, I didn't read the entire thread [0], but did read the summary [1]. I 
like this, except that I'm not sure about #3. What's the rationale of adding a 
new config option 'enable_unsupported_drivers' that defaults to False. Versus 
not having it, and "just" logging a warning if they are loading an unsupported 
(in-tree) driver?

If I understand this...

If we have 'enable_unsupported_drivers': since it defaults to False, the 
conductor will fail on startup, if an unsupported driver is in the 
enabled_drivers config. (The conductor will emit a warning in the logs, or 
maybe it won't?) The operator (if they haven't changed it), will now change it 
to True if they want to use any unsupported drivers. The conductor will start 
up and emit a warning in the logs.

If we don't have an enable_unsupported_drivers config, will the conductor start 
up and emit a warning in the logs?

I was also wondering, where is the value for the 'supported' flag for each 
driver going to be kept? Hard-coded in the driver code?

--ruby


On 2016-08-19, 10:15 AM, "Jim Rollenhagen" 
> wrote:

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, but I think we
should go roughly the same route, for the sake of the users.

1) A ``supported`` flag for each driver that is True if and only if the driver
   is tested in infra or third-party CI (and meets our third party CI
   requirements).
2) If the supported flag is False for a driver, deprecation is implied (and
   a warning is emitted at load time). A driver may be removed per standard
   deprecation policies, with turning the supported flag False to start the
   clock.
3) Add a ``enable_unsupported_drivers`` config option that allows enabling
   drivers marked supported=False. If a driver is in enabled_drivers, has
   supported=False, and enable_unsupported_drivers=False, ironic-conductor
   will fail to start. Setting enable_unsupported_drivers=True will allow
   ironic-conductor to start with warnings emitted.

It is important to note that (3) does still technically break the standard
deprecation policy (old config may not work with new version of ironic).
However, this is a much softer landing than the original plan. FWIW, I do
expect (but not hope!) this part will be somewhat contentious.

I'd like to hear thoughts and get consensus on this from the rest of the
ironic community, so please do reply whether you agree or disagree.

I'm happy to do the work required (update spec, code patches, doc updates)
when we do come to agreement.

// jim

[0] http://lists.openstack.org/pipermail/openstack-dev/2016-August/101428.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-August/101898.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi,

Here is this week's subteam report for Ironic. As usual, this is pulled 
directly from the Ironic whiteboard[0] and formatted.

Bugs (dtantsur)
===
- Stats (diff between  1 Aug 2016 and 15 Aug 2016)
- Ironic: 232 bugs (+16) + 199 wishlist items (-5). 36 new (+15), 160 in 
progress, 0 critical, 33 high (+2) and 19 incomplete
- Inspector: 9 bugs (-2) + 20 wishlist items. 0 new, 9 in progress (-2), 0 
critical, 2 high and 2 incomplete
- Nova bugs with Ironic tag: 11. 0 new, 0 critical, 0 high
- I suspect this time we might need an earlier feature freeze to win some time 
to sort all these bugs :/

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- multitenant networking is done \o/
- portgroups still todo

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- We should consider using bindep for installing binary dependencies instead of 
letting devstack-gate install a bunch of thing automagically. Details: 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101590.html
- ++ +1
- though I believe Andreas is planning to post the patch, maybe? 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101599.html good 
for us then :)

Multiple compute hosts (jroll, devananda)
=
* trello: https://trello.com/c/OXYBHStp/7-multiple-compute-hosts
- done! \o/

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- No change since last week
- Volume connection information revisions still in review. 
https://review.openstack.org/#/q/topic:bug/1526231+status:open+project:openstack/ironic
- Boot from Volume spec still in review. 
https://review.openstack.org/#/c/294995/
- Code for Boot from Volume still under active development. 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1559691

Agent top-level API promotion (dtantsur)

* trello: 
https://trello.com/c/37YuKIB8/28-promote-agent-vendor-passthru-to-core-api
- MERGED

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- We seem to have a consensus now on the defaults, see 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101477.html
- TheJuila will submit an update to the spec
- dtantsur will continue hacking soon :)

OpenStackClient plugin for ironic (thrash, dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- Still under review: chassis https://review.openstack.org/345815
- Port commands needs addressing review comments

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- still have to respond to comments on first patch in series 
https://review.openstack.org/#/c/298461/

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- mostly done! a couple follow-up / docs patches left

Software metrics (JayF, alineb)
===
* trello: https://trello.com/c/XtPGyHcP/18-software-metrics
- basically done, there's still a few patches adding metrics but I expect those 
to keep coming in

Active node creation (TheJulia)
===
* trello: https://trello.com/c/BwA91osf/22-active-node-creation
- Tempesting test still pending review: 
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526315

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- follow-up patches:
- https://review.openstack.org/#/c/335378/: merged
- https://review.openstack.org/#/c/293872/: needs review
- nova patch:
- https://review.openstack.org/#/c/328157/: needs review(-2 has been 
removed by Nova PTL)

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- nothing last week, got stuck on other priorities

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- draft patches up
- spec still needs reviewing

Inspector (dtansur)
===
- ironic-inspector 4.1.0 released with local_link_connection discovery
- 
http://docs.openstack.org/releasenotes/ironic-inspector/current-series.html#id1

Bifrost (TheJulia)
==
- Some test timeouts are occuring, largely due to the 

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

[Loo, Ruby]

Hi Julia,

Thanks for discussing with Sam and sending out this email. I like the 5 steps 
described below!

--ruby

On 2016-08-11, 1:37 PM, "Julia Kreger" 
> wrote:

Yesterday as a group (jroll, rloo, dtantsur, matt128, devananda,
vdrok, and myself) discussed defaults for driver composition.

The options we discussed were:

* The existing specification[0] - Global and hardware_type
default_FOO_interface configuration, global enabled_FOO_interfaces in
configs, supported_FOO_interface in the hardware_type.

* Sambetts proposal[1] - To base any defaults on the intersection of
enabled_FOO_interfaces and the supported_FOO_interface lists taking
the first common option.

During the discussion the group came to the conclusion that if we were
to enable the ability to set defaults solely by list ordering, as put
forth in sambetts proposal, the question would then shift to who knows
best. The operator, or the vendor via the hardware_type. This further
evolved into substantial amounts of potential configuration which we
seemed to agree was confusing and unrealistic. We eventually circled
back to the original intent of the global configuration
default_FOO_interface which was to make an operator’s life easier by
allowing the definition of what would by in large be an explicitly
chosen environmental or operating default.

Circling back to the intent allowed us to focus the discussion further
and decide the following:

1. If the client creating the node does not set an explicit
FOO_interface, we must save whatever is determined as the default, in
node.FOO_interface.

2. To determine a default if one is not explicitly set via a
default_FOO_interface, the intersection between the hardware_type
definition supported_FOO_interfaces and the enabled_FOO_interfaces
global configuration would be used to determine the default.

Having determined the two preceding items, we reached a consensus that
the resulting default that is determined, must be present in
enabled_FOO_interfaces list. The result of this is that there should
be no implicit enablement of drivers, and the operator should be
selecting the interfaces possible for their environment in the
enabled_FOO_interfaces global configuration setting.

In following up with sambetts this morning and discussing the concerns
that drove his proposal initially, Sam and I determined that any
implicit enablement of drivers was not ideal, that an operator
explicit default override for its intended purpose seemed okay, and
that the determination of any default should come from the the
intersection of what is supported versus what is enabled, as the
larger group reached a consensus on.  That this would ultimately
result in default_FOO_interface dropping from the hardware_type and
only being present as global configuration option for an operator to
use if they so choose to do so.  This seems in-line with what the
group reached while on the call yesterday.

Conceptually, this leaves us with something that looks like the
following when nodes are created without a valid FOO_interface in the
initial API post.

1. The hardware_type's supported_FOO_interfaces is in order of
preference by the vendor, for example: supported_FOO_interface = [BAR,
CAR, DAR] this represents: if BAR enabled then use BAR else if CAR
enabled then use CAR else if DAR enabled then use DAR.

2. possible_FOO_interfaces to use for a hardware_type are calculated
by intersecting enabled_FOO_interfaces and the hardware_type's
supported_FOO_interfaces, order as in supported_FOO_interface is
maintained.

3. If configuration option default_FOO_interface is set AND
default_FOO_interface is in possible_FOO_interfaces THEN
node.FOO_interface is set to default_FOO_interface

4. If configuration option default_FOO_interface is set AND
default_FOO_interface is NOT in possible_FOO_interfaces THEN node
create fails

5. If configuration option default_FOO_interface is NOT set THEN
node.FOO_interface is set to the first interface in
possible_FOO_interface

Thank you Sam for typing out the above logic.  I think this means we
seem to have some consensus on the direction to move forward, at least
I hope. :)

-Julia

[0] 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/driver-composition-reform.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-July/099257.html

On Mon, Aug 8, 2016 at 8:51 AM, Julia Kreger
> wrote:
Thank you for sending the corrected link Mathieu!  I thought I fixed it
before I sent the email, but... *shrug*

Anyway!  Looking at the doodle, the mutually available time is 4 PM UTC on
this Wednesday (8/10/16).  If there are no objections, I guess we will hear
those seeking to discuss defaults on conferencing[0] bridge number  at
that time.

-Julia

[0] https://wiki.openstack.org/wiki/Infrastructure/Conferencing

Re: [openstack-dev] [ironic] How should ironic and related project names be written?

[Loo, Ruby]

Honestly, I don't think it matters what we use in our specifications, since 
specifications are not public documents. Personally, in specifications, I am 
fine with any of the proposed because they are all understandable! IF we have 
to decide on something or if we want some preferred ways, then I'd suggest 
going with what is more 'official'. By that, I mean we could do what is 
suggested for documentation on docs.openstack.org, as described at [1]: "Use 
lowercase when you refer to project names".

Which leads us to the question you ask, what is a "project name". I think we 
could use the names described in the projects.yaml file [2]. So 'ironic', 
'ironic-inspector', 'ironic-lib', 'ironic-python-agent'.

What do you think?

--ruby

[1] 
http://docs.openstack.org/contributor-guide/writing-style/openstack-components.html
[2] 
https://github.com/openstack/governance/blob/7176a32e158d685d4552d9935982e4981bb79bf7/reference/projects.yaml#L1978


On 2016-08-01, 6:35 AM, "Sam Betts (sambetts)" 
> wrote:

Its official OpenStack policy that project names be written in lower case, for 
example Ironic must always be written as ironic, however I was recently writing 
a spec for IPA, and was unsure how to approach writing IPAs name in full.
Discussing this with Dmitry on IRC, we decided it would be best brought to a 
wider audience on the ML because this affects any project that includes 
ironic’s name in their name.

Ironic Python Agent
ironic Python Agent
ironic python agent
ironic-python-agent

I prefer a capitalised Ironic Python Agent name, because it lines up with the 
way we write the acronym, IPA, and makes it obvious its a name, however I’m 
unsure if this aligns with the OpenStack policy. If we need to lower case the 
whole of IPA’s name, then I prefer we refer to it using including the dashes, 
so that it is obviously a project name.

A couple of other projects that also use ironic in the name:

Ironic Inspector
ironic Inspector
ironic inspector
Ironic-inspector

Ironic Lib
ironic Lib
ironic lib
ironic-lib

I would like to hear some opinions on whether we should always refer to the 
projects as they are written if you go to git.openstack.org (with dashes) or 
which of the above styles we’re allowed, and prefer?

Sam


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi,

We are zealous 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 update - dtantsur is out sick today

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- main code landed, non-voting job in the gate. Please pay attention to it!
- work still to do: portgroups, security groups, inspector integration

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- python-ironicclient now has a voting functional test job
- ironic now has an experimental job for multi-node testing. This is a step in 
our work to get to a multi-node grenade job

Multiple compute hosts (jroll, devananda)
=
* trello: https://trello.com/c/OXYBHStp/7-multiple-compute-hosts
- nova code has one +2
- https://review.openstack.org/#/c/348443/

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Specification needs reviews: https://review.openstack.org/#/c/294995/
- Volume connector revisions are available for review, and start at 
https://review.openstack.org/#/c/200983/

Agent top-level API promotion (dtantsur)

* trello: 
https://trello.com/c/37YuKIB8/28-promote-agent-vendor-passthru-to-core-api
- agent vendor passthru API deprecation is done, last patch is waiting for gate 
fixes, should land today

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- (unknown - dtantsur is out today)

OpenStackClient plugin for ironic (thrash, dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- patches ready for review: 
https://review.openstack.org/#/q/status:open+project:openstack/python-ironicclient+branch:master+topic:bug/1526479

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- Responded to comments and rebased, code needs re-reviews
- https://review.openstack.org/#/c/298461
- https://review.openstack.org/#/c/321865/
- CRUD and provision state notification spec needs reviews 
https://review.openstack.org/#/c/347242/

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- most code landed, need to finish follow-ups and docs

Software metrics (JayF, alineb)
===
* trello: https://trello.com/c/XtPGyHcP/18-software-metrics
- Metrics coverage:
- Full API coverage
- About 50% metrics coverage in various drivers (Should be up to 75% by EOW)
- IPA metrics code needs reviews -> https://review.openstack.org/#/c/119981/

Active node creation (TheJulia)
===
* trello: https://trello.com/c/BwA91osf/22-active-node-creation
- No update, reviews for tempest test addition are still pending.  
https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bug/1526315

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- console_utils: merged
- IPMITool driver interface: merged
- follow-on patches:
- https://review.openstack.org/#/c/335378/: need review (all primary 
contacts +1d)
- https://review.openstack.org/#/c/349400/: merged
- install guide: needs review (all primary contacts +1d)  
https://review.openstack.org/#/c/293872/
- nova patch: needs review (-2 was removed)  
https://review.openstack.org/#/c/328157/

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- Ironic-lib patch extending the parse_root_device_hints() method to work with 
operators (need more tests): https://review.openstack.org/#/c/348953/

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- Spec needs reviews  https://review.openstack.org/#/c/171878/ (1x+2, no 
negative feedback)
- Draft code already partially up, should be 75%+ up by EOW

Inspector (dtansur)
===
- HA effort: introspection state in database; patch up for review: 
https://review.openstack.org/#/c/348943/

Drivers:

OneView (gabriel-bezerra/thiagop)
-
- Dynamic allocation for Oneview drivers code was merged
- Docs included (thanks JayF and NobodyCam)

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

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

[Loo, Ruby]

Hi,

We are xenodochial 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 July 2016)
- dtantsur on PTO, no stats from me this week

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- may still be able to get the nova patch merged this cycle for multitenance 
without portgroups: https://review.openstack.org/#/c/297895/
- "may" because we're past feature freeze

Node claims API (jroll, lintan)
===
* trello: https://trello.com/c/3ai8OQcA/25-node-claims-api
- this may be superceded by the Placement Engine: 
http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/generic-resource-pools.html

Multiple compute hosts (jroll, devananda)
=
* trello: https://trello.com/c/OXYBHStp/7-multiple-compute-hosts
- some progress at nova midcycle: 
http://lists.openstack.org/pipermail/openstack-dev/2016-July/099922.html

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Specification updated and is in need of reviews - 
https://review.openstack.org/#/c/294995/
- Cinerama has been kind enough to begin rebasing and correcting the volume 
connection information patch series which is required for boot from volume.
- Patch series starts at https://review.openstack.org/#/c/200983/

OpenStackClient plugin for ironic (thrash, dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- patches for port and chassis commands ready for review: 
https://review.openstack.org/#/q/topic:bug/1526479

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- responded to patch comments, ready for re-review 
https://review.openstack.org/#/c/298461/ 
https://review.openstack.org/#/c/321865/

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- code, unit tests, and docs are done. Split into several patches, starting 
with:
- https://review.openstack.org/#/c/325599/
- next up: integration with Bifrost

Active node creation (TheJulia)
===
* trello: https://trello.com/c/BwA91osf/22-active-node-creation
- Tempest test posted https://review.openstack.org/#/c/344975/
- Required some additional substrate and bug fixes in the tempest api 
client and utilities: https://review.openstack.org/#/c/344974/

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- console_utils: merged
- IPMITool driver interface: needs review (got a few +2s) 
https://review.openstack.org/#/c/293873/

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- https://review.openstack.org/#/c/346068/ helps refactoring some of the 
current root device hints code

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- Surprise, surprise: https://review.openstack.org/#/c/171878/ needs reviews

Inspector (dtansur)
===
- grenade for inspector unblocked, thx for escalating ; smoke test for 
inspector in merge conflict now (milan)

Bifrost (TheJulia)
==
- Interest has been expressed in adding ISC-dhcpd and keystone support in to 
bifrost.  TheJulia will be following up with those who have expressed interest 
this week.
- ISC-DHCP initial work started: https://review.openstack.org/#/c/343947 
(WIP: thou reviews are welcomed!)

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi,

We are wriggly 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 July 2016)
- Ironic: 201 bugs (+4) + 201 wishlist items (+4). 13 new (+3), 145 in progress 
(+3), 0 critical, 29 high and 21 incomplete (-4)
- Inspector: 9 bugs + 21 wishlist items. 0 new, 8 in progress (+1), 0 critical, 
2 high and 2 incomplete
- Nova bugs with Ironic tag: 9 (-2). 0 new, 0 critical, 0 high

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- much code merged!
- still to merge: PortGroup support, Inspector support for LLDP, two Nova 
changes, documentation

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- network multitenancy test passing, will be moved from experimental to 
non-voting check queue this week

Agent top-level API promotion (dtantsur)

* trello: 
https://trello.com/c/37YuKIB8/28-promote-agent-vendor-passthru-to-core-api
- I'm tired of rebasing this series :/ ping me when you're ready to review and 
I'll rebase it again

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- blocked by
- agent API promotion
- ongoing discussions about interfaces defaults

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- Status 7/18/2016: Still needs reviews. Rebased again.
- https://review.openstack.org/#/c/298461/
- https://review.openstack.org/#/c/321865/

Keystone policy support (JayF, devananda)
=* trello: 
https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- Spec merged, code needs to be updated still.

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- console_utils: merged
- IPMITool driver interface: needs review

Inspector (dtansur)
===
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- The grenade job is still blocked by this one-liner in grenade itself: 
https://review.openstack.org/337372 (too bad 8x +1 != 4x +2 ;)

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Thanks Devananda and Dmitry and Sam!

From my point of view, I wanted to make sure that:

1. we agreed on  whether the 'network_interface' was, or was not, an interface 
that was similar to the existing power, deploy, ... interfaces so that it fit 
into the driver composition work
2. we agreed on having or not having the default_network_interface 
configuration option, and whether/how it fit into the driver composition work.

I think, because I haven't heard anyone disagree (yet), that the 
network_interface fits into the driver composition work and that we want the 
configuration option. It looks like we are trying to figure out *how* it fits 
into the driver composition work and hardware_types. To that end, I thought I'd 
put up a patch [1] that I hope captures everyone's suggestions. Maybe we can 
move to that patch to comment.

As far as the multi-tenant networking patches [2] go, as long as we're good 
with the above, I think we're good to continue. The details wrt how the 
network_interface and default configuration option is integrated with 
hardware_types can be worked out.

If you think otherwise, please let me know :)

--ruby

[1] https://review.openstack.org/#/c/341084/

[2] https://review.openstack.org/#/c/285852/


On 2016-07-12, 8:02 AM, "Dmitry Tantsur" 
> wrote:

Thanks for writing this up, minor comments inline.

On 07/11/2016 10:57 PM, Devananda van der Veen wrote:
We spent the majority of today's weekly IRC meeting [1] discussing the finer
points of this question. I agreed to post a summary of those to the list (it's
below the break).

tldr;

* we don't know if network_interface should behave like other hardware
interfaces, but...
* we need to come to an agreement on it this week, so we can proceed with the
network integration work.





There was a proposal from sambetts towards the end of the meeting, which I've
edited for clarity (please correct if I misunderstood any of your points). This
seems to capture/address most of the points above and proposes a way forward,
while keeping within the intent of our driver composition reform spec. It was
the only clear suggestion during the meeting.

- in-tree hardware_types declare supported_network_interfaces to be empty [4]
and declare no default_network_interface

We need supported_network_interfaces, otherwise you won't be able to
check compatibility. I think we should introduce a constant to use like
that:

  class MyHwType:
supported_network_interfaces = ironic.network.ALL_INTERFACES

- we add a CONF option for default_network_interface, with a sane default value
- this CONF option is validated on conductor load to be supported by all loaded
hardware_types, and the conductor refuses to start if this CONF option is set to
a value not supported by one or more enabled_hardware_types

How do we distinguish between interfaces which have a default and which
don't? For example, I can see a use case for having defaults for deploy
and inspect (the latter would be used by tripleo for sure).

- if a(n out of tree) hardware_type declares a default_network_interface, this
will take precedence over the CONF option
- a node created without specifying a network interface will check the
hardware_type's supported_network_interfaces, and when that is empty, fall back

s/supported/default/ here?

to the CONF.default_network_interface, just as other interfaces fall back to the
hardware_type's relevant default
- operators can override a specific node's network_interface, which follows the
usual rules for setting an interface on a Node (ie, the interface must be in
hardware_type.supported_network_interfaces AND in 
CONF.enabled_network_interfaces)


If anyone else has other clear suggestions that address all the issues here,
please reply with them.

I'm going to make myself available tomorrow at 1700 UTC, in both IRC and by
voice [3] (conference line # TBD) to discuss this with anyone. If we need to
discuss it again on Wednesday, we can.


Thanks much,
--devananda



[1] starting at 17:20

http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-07-11-17.00.log.html

[2]
http://specs.openstack.org/openstack/ironic-specs/specs/approved/driver-composition-reform.html

[3] https://wiki.openstack.org/wiki/Infrastructure/Conferencing

[4] I think we may need to have in-tree drivers declare
supported_network_interfaces to be [noop, flat, neutron], but that is not what
Sam suggested during the meeting



On 06/28/2016 08:32 AM, Dmitry Tantsur wrote:
Hi folks!

I was reviewing https://review.openstack.org/317391 and realized I don't quite
understand why we want to have node.network_interface. What's the real life use
case for it?

Do we expect some nodes to use Neutron, some - not?

Do we expect some nodes to benefit from network separation, some - not? There
may be a use case here, but then we have to expose this field to Nova for
scheduling, so that users can request a "secure" node or a "less secure" one. If

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

[Loo, Ruby]

Hi,

We are veracious 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 27 June 2016)
- Ironic: 197 bugs (-10) + 197 wishlist items (+6). 10 new (-2), 142 in 
progress (+2), 0 critical, 29 high (-3) and 25 incomplete (-1)
- Inspector: 9 bugs (+2) + 21 wishlist items (+1). 0 new, 7 in progress (+2), 0 
critical, 2 high (+1) and 2 incomplete (+1)
- Nova bugs with Ironic tag: 11 (-3). 1 new (+1), 0 critical, 0 high

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- Currently blocked on contention regarding network_interface, and a possible 
default value which conflicts with the driver composition model.
- The nova FF has passed and https://review.openstack.org/#/c/297895/ is 
dependent upon the ironic code landing.

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- the last inspector gate job (source job running on IPA) is switched to tinyipa

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Spec still in review.

Agent top-level API promotion (dtantsur)

* trello: 
https://trello.com/c/37YuKIB8/28-promote-agent-vendor-passthru-to-core-api
- code patches are up and under review: 
https://review.openstack.org/#/q/topic:bug/1570841

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- started working on code patches

OpenStackClient plugin for ironic (thrash, dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- stalled, needs someone to check the spec against the actual code
- rloo volunteers to do this fun job

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- code patches are up and need reviews. just rebased after merge conflict from 
friday, so jenkins is reverifying
- https://review.openstack.org/#/c/298461/ had a +2 and a +1 before, 
responded to -1 comments after that
- https://review.openstack.org/#/c/321865/

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- Spec needs reviews
- Code is in progress, needs some more work

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- Ironic:
- spec: approved
- code: needs review
- Nova:
- spec: not required
- code: needs review
Nova Feature Freeze was last week and this didn't get a FFE (feature freeze 
exception) so will not land in Newton

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- stalled on getting nova's ops matcher into oslo.utils for use by ironic

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- spec needs reviews still

Inspector (dtansur)
===
- Our grenade job passed for the first time and now runs non-voting in the 
check pipeline
- It does not run any inspection tests though, working on it: 
https://review.openstack.org/336532
- blocked by grenade patch: https://review.openstack.org/337372
- newton-2 releases were done

Cross-project:
==
- QA (dtantsur)
- the gate is moving from Python 3.4 to Python 3.5. There will be a new 
non-voting job very soon. It's up to us when we decide to switch our master to 
Python 3.5. Stable branches stay on 3.4. Details: 
http://lists.openstack.org/pipermail/openstack-dev/2016-July/098665.html

Drivers:

iLO (wanyen)
 - The CI is enabled for all three ilo drivers. Due to some space issue on the 
base hardware where we have jenkins setup, we have temporarily shut down the CI.
- The patches https://review.openstack.org/264590 and 
https://review.openstack.org/266803 are there in review from long time and 
needed for ilo drivers CI. Since these are not getting reviews, they move to 
merge conflict state any time.

.

Until next week,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] next week's meeting is cancelled

[Loo, Ruby]

Hi,

Quite a few people will be away next Monday (July 4), due to a US holiday (and 
other reasons), so we decided to cancel the ironic meeting. The next meeting 
[1] will be on Monday, July 11.

--ruby

[1] https://wiki.openstack.org/wiki/Meetings/Ironic#Next_Meeting
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Loo, Ruby]

Hi,

We are upbeat 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 13 June 2016)
- Ironic: 207 bugs (-6) + 191 wishlist items (+9). 12 new (-3), 140 in progress 
(-7), 0 critical, 32 high (-2) and 26 incomplete (+5)
- Inspector: 7 bugs (-1) + 20 wishlist items (+1). 0 new, 5 in progress (-2), 0 
critical, 1 high (-1) and 1 incomplete (+1)
- Nova bugs with Ironic tag: 14. 0 new, 0 critical, 0 high

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
* trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- Switch to ipmitool gate is stalling, as the jobs are not showing the desired 
reliability
- We also need to start running ipmitool gates on IPA

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
* trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Information storage specification approved.
- Boot from volume specification to be updated early this week.

Agent top-level API promotion (dtantsur)

* trello: 
https://trello.com/c/37YuKIB8/28-promote-agent-vendor-passthru-to-core-api
- some patches are up, some of them are ready for review: 
https://review.openstack.org/#/q/topic:bug/1570841

Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- The spec is merged \o/


Driver composition (dtantsur)
=
* trello: https://trello.com/c/fTya14y6/14-driver-composition
- The spec is merged \o/

OpenStackClient plugin for ironic (thrash, dtantsur, rloo)
==
* trello: https://trello.com/c/ckqtq3kG/16-openstackclient-plugin-for-ironic
- Merged node provision state operations and support for maintenance mode

Notifications (mariojv)
===
* trello: https://trello.com/c/MD8HNcwJ/17-notifications
- https://review.openstack.org/#/c/298461/ hasn't been getting many reviews, 
needs a rebase. Expect to be rebased by end of day (CDT) today.

Keystone policy support (JayF, devananda)
=
* trello: https://trello.com/c/P5q3Es2z/15-keystone-policy-support
- Spec needs reviews: https://review.openstack.org/#/c/327437/
- Code is up, pending spec approval: 
https://review.openstack.org/#/q/status:open+branch:master+topic:add-ironic-policy

Software metrics (JayF, alineb)
===
* trello: https://trello.com/c/XtPGyHcP/18-software-metrics
- Blocked on reviews: ironic-lib code up with no negative feedback since 
6/8(thanks dmitry): https://review.openstack.org/#/c/301526/
- all other patches irrelevant until this one lands + is released

Serial console (yossy, hshiina, yuikotakadamori)

* trello: https://trello.com/c/nm3I8djr/20-serial-console
- spec: not approved yet, but have gotten +2 by Ruby 
https://review.openstack.org/#/c/319505/ (landed this morning) thanks!
- Thank you for your reviewing in Midcycle!
- Before driver composition, we will implement 2 drivers in the short 
term.
- A path to socat binary will not be necessary.
- code:
- nova: needs review https://review.openstack.org/#/c/328157/
- Nova non-priority feature freeze is June 30.
- ironic:
- console_utils: needs review https://review.openstack.org/#/c/328168/
- IPMITool driver: needs review https://review.openstack.org/#/c/293873/
- CI: We cannot implement CI tests because virtualbmc doesn't have console.
- Can be added https://bugs.launchpad.net/virtualbmc/+bug/1596624

Rolling upgrades and grenade-partial (lintan)
=
* trello: https://trello.com/c/GAlhSzLm/2-rolling-upgrades-and-grenade-partial
- jlvillial, sambetts, TheJulia and mat128
- Trying to get multinode to work with simple tempest run
- Progress here 
https://etherpad.openstack.org/p/ironic-newton-grenade-whiteboard
- Patch is proposed to run a multinode job as experimental in the gate: 
https://review.openstack.org/332490

Enhanced root device hints (lucasagomes)

* trello: https://trello.com/c/f9DTEvDB/21-enhanced-root-device-hints
- patch proposed to move operators processing under ironic-lib: 
https://review.openstack.org/#/c/334431/

Rescue mode (JayF)
==
* trello: https://trello.com/c/PwH1pexJ/23-rescue-mode
- https://review.openstack.org/#/c/171878/ has some negative feedback, needs 
more reviews. Expect to respond to feedback today/tomorrow.

Inspector (dtansur)
===
- Grenade work is ongoing; current patch stack:
- https://review.openstack.org/#/c/327667/
- 

[openstack-dev] [ironic] mid cycle feedback

[Loo, Ruby]

Hi,

Now that we've all had a chance to recover from the mid-cycle last week and 
while it is still fresh in your minds (or am I too late?), I was wondering 
whether you had any feedback about the mid-cycle. What worked for you, what 
didn't. I am especially interested in knowing what can be improved for future 
mid cycles, or what you got out of the mid-cycle that might help us improve our 
processes or whatever.

For those that were unable to attend but wanted to, what could be done to help 
you attend next time? Or to help you get up-to-speed on what happened (although 
I have to say, Mathieu's summary [1] was excellent.)

One thing that didn't work out well was the conferencing number not working 
sometimes, so folks that couldn't call in via SIP were unable to call in.

Now that I think of it, maybe during the next mid-cycle, we could add ideas to 
the etherpad as to what could be done to improve things in the future.

--ruby

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-June/098060.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Ironic Newton midcycle sprint summary

[Loo, Ruby]

Thanks Mathieu, that is a great summary! It is much easier than trying to 
figure that out from the etherpad [1] notes.

--ruby

[1] https://etherpad.openstack.org/p/ironic-newton-midcycle



On 2016-06-23, 3:08 PM, "Mathieu Mitchell" 
> wrote:

Dear group,

Please enjoy this midcycle sprint summary. You might have to put your
Markdown glasses on for proper formatting :)


The midcycle sprint lasted three days. It was virtually held over
Infra's conference system and IRC. The event was split in two different
time slots. The first slot, from 15:00 to 20:00 UTC, was by far the most
popular. A lot of topics were covered by the participants. The second
slot, from 00:00 to 04:00 UTC, was much less popular, having a whooping
peak participant count of four.


June 20 2016 15:00 to 20:00 UTC
---

Most of the group was present for this session. Missing were Devananda
van der Veen (devananda) and Jay Faulkner (JayF). We decided to create
an agenda for the upcoming sessions and reserve topics of interest to
our missing members for the days where they would be present. Also,
Ukraine was observing a national holiday, so some of our Ukrainian
members were absent, too.

The session started with an overview of our Newton priorities. This was
done using the new Ironic Newton Priorities Trello board [1].

[1] https://trello.com/b/ROTxmGIc/ironic-newton-priorities


### Ironic-Neutron integration

The first topic to be covered was the Ironic-Neutron integration. At the
time of discussing that topic, most patches needed rebasing. However,
the group still agreed on the following game plan:

   * Merge the devstack parts ASAP
   * Split portgroups support to the end of the patch chain so they can
merge later. (done: Vladyslav Drok (vdrok) quickly posted a new revision
for [1] and created [2]).
   * Merge everything but portgroups in server-side Ironic
   * Merge client patches in
   * Merge "Ironic: change flat network provider to 'flat'" in nova [3]
   * Finish portgroups
   * Merge "Replace vif_portgroup_id with vif_port_id" [4] (merged
already, thanks Dmitry)

[1] https://review.openstack.org/#/c/206244/
[2] https://review.openstack.org/#/c/332177/
[3] https://review.openstack.org/#/c/297895/
[4] https://review.openstack.org/#/c/325197/


### Security groups for Bare metal deployments

Sukhdev Singh (Sukhdev) reports that full security group support will be
available for bare metal deployments by leveraging the Neutron integration.

> There is minor work that is needed in the Ironic driver. Most of the
ML2 drivers already know how to deal with Security Groups. Hence, this
becomes a slam dunk - huge reward with little work.


### Future networking work

Up for review is the spec for VLAN-aware baremetal instances [1] by Sam
Betts (sambetts). It has received comments and a few reviews, but more
eyes would help get this through :)

Attach and detach are becoming first class citizens [2] and will be
defined in network drivers, allowing for different vendors to implement
their own logic. This will also support post-boot network attach/detach.
Also, keep an eye open for network-aware scheduling in Nova.

[1] https://review.openstack.org/#/c/277853/
[2] https://review.openstack.org/#/c/317636/


### Driver composition

Big topic that has been in progress for officially more than a year
(first patch set is dated June 4th, 2015!). We are finally reaching
consensus. Most people are okay with the spec, the only pain point was
using the `driver` vs `hardware_type` field. Since hardware_type was
introduced before dynamic driver had default interfaces, most of the
group agreed to dropping it and simply keeping the `driver` field.

Dmitry Tantsur (dtantsur) quickly posted a few new patch sets and the
spec [1] is currently awaiting workflow.

[1] https://review.openstack.org/#/c/188370/


### Serial console spec

Up for review is the Nova-compatible serial console support [1]. The
group had a few questions but none of the authors were present in the room.

One interesting question was whether this should depend on the driver
composition spec. The answer was that, given the limited scope of the
serial console in current deployments, simply one or two new drivers
could be added to the matrix, instead of duplicating all current
drivers, preventing this from requiring the driver composition.

Everyone interested posted questions directly in the review for the
authors to answer. Another point of interest was the full path to the
socat binary, and the code behaving differently based finding "socat" in
said string.

[1] https://review.openstack.org/#/c/319505/


June 21 2016 00:00 to 04:00 UTC
---

A small number of participants assisted the session.

An informal discussion took place and the following topics were discussed:

* Merge conflicts and their cause
* Feature enabling
* v2 API
* Multi-node devstack deployments

The session ended 

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

[Loo, Ruby]

Jim,

Thanks for the proposal.

+2 +A. Err, +2 :)

--ruby

On 2016-06-16, 11:12 AM, "Jim Rollenhagen" 
> wrote:


Both Sam and Jay are to the point where I consider their +1 or -1 as
highly as any other core, so I think it's past time to allow them to +2
as well.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] simple patches requiring only one +2/+A

[Loo, Ruby]

Hi,

There was a short discussion on IRC a few minutes ago [1] about when it would 
be acceptable for a patch to be approved with one +2 (as opposed to two +2s). 
The few of us that commented (I think all are cores in one or several ironic 
projects) agreed that it would be good to do that, but "use your common sense" 
didn't seem to provide enough guidance :)

I've updated our wiki [2] (see bullet 4, bullet 2) to reflect what I think we 
agreed on. It didn't seem necessary to vote on it. Please let me/us know if you 
disagree or have other comments.

(I know, we should move this information from the wiki to our documentation, 
but that's a separate issue.)

Thanks,
--ruby


[1] 
http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2016-06-14.log.html#t2016-06-14T16:51:40
[2] https://wiki.openstack.org/wiki/Ironic/CoreTeam#Other_notes

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] weekly sub team status report

[Loo, Ruby]

Hi,

We are thrilled 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 6 June 2016)
- Ironic: 213 bugs (+9) + 182 wishlist items (+4). 15 new (+7), 147 in progress 
(+9), 0 critical, 34 high (-1) and 21 incomplete (-1)
- Inspector: 8 bugs + 19 wishlist items (-1). 0 new, 7 in progress, 0 critical, 
2 high (+1) and 0 incomplete
- Nova bugs with Ironic tag: 14 (-2). 0 new, 0 critical, 0 high

Upgrade (aka Grenade) testing (jlvillal/mgould):

- trello: https://trello.com/c/y127DhpD/3-ci-grenade-testing
- Grenade full job is now running in the check queue as non-voting! :)
- TODO: Setup the Grenade partial job (jlvillal)

Network isolation (Neutron/Ironic work) (jroll, TheJulia, devananda)

- trello: 
https://trello.com/c/HWVHhxOj/1-multi-tenant-networking-network-isolation
- needs a rebase, but after that let's focus on reviewing this stuff
- please make sure it passes grenade :D

Gate improvements (jlvillal, lucasagomes, dtantsur)
===
- removed old ramdisk support (not a direct improvement, but still)

Node search API (jroll, lintan, rloo)
=
- trello: https://trello.com/c/j35vJrSz/24-node-search-api

Node claims API (jroll, lintan)
===
- trello: https://trello.com/c/3ai8OQcA/25-node-claims-api

Multiple compute hosts (jroll, devananda)
=
- trello: https://trello.com/c/OXYBHStp/7-multiple-compute-hosts
- need to sync up with jaypipes and get a new spec up

Generic boot-from-volume (TheJulia, dtantsur, lucasagomes)
==
- trello: https://trello.com/c/UttNjDB7/13-generic-boot-from-volume
- Specification and dependent specification updated last week, reviews required.
- https://review.openstack.org/#/c/200496/
- https://review.openstack.org/#/c/294995/

Driver composition (dtantsur)
=
- trello: https://trello.com/c/fTya14y6/14-driver-composition
- No updates (please review the spec)

Inspector (dtantsur)

- (milan) implementing grenade fork of Ironic in a slow pace; have got some 
progress on env setup (https://github.com/dparalen/devstack-gate-test )

.

Until the week after next,
--ruby

[0] https://etherpad.openstack.org/p/IronicWhiteBoard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev