Hi,
A patch to ironic-lib made me wonder about what is our supported usage of
ironic-lib. Or even the intent/scope of it. This patch changes a method,
‘bootable’ parameter is removed and ‘boot_flag’ parameter is added [1].
If this library/method is used by some out-of-tree thing (or even some i
eing renamed then you can also have it
subclass the new command.
As always, the deprecation message should indicate which command / option to
use.
[1]
https://github.com/openstack/python-openstackclient/blob/b4c3adbd308e65679489c4c64680cbe0324f4bc7/openstackclient/volume/v1/volume.py#L53
Hi,
We are quick 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 9 May 2016):
- Ironic: 190 bugs (0) + 177 wishlist items (+4). 0 new (-17), 134 in progress
(+1),
Hi,
I think it would be good if we came up with some general guidelines wrt the
processes by which decisions are made. By ³decisions², I mean decisions that
we, as a community, will try to abide by ?
I have noticed in the past, that discussions in the mailing list (ML) sometimes
peter out with
Ooo, thanks for that data point Pavlo!
Thanks Lucas, Sam, Shivanand and Pavlo for commenting. From the replies, it
seems like the original intent of ironic-lib was to solely be used by ironic
and ironic-python-agent projects. But that doesn’t seem to have been
communicated properly (because I w
Hi,
We are rambunctious 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 16 May 2016)
- Ironic: 192 bugs (+2) + 178 wishlist items (+1). 0 new, 138 in progress (+4)
t; On 05/16/2016 07:14 AM, Lucas Alvares Gomes wrote:
>> > On Mon, May 16, 2016 at 2:57 PM, Loo, Ruby wrote:
>> >> Hi,
>> >>
>> >> A patch to ironic-lib made me wonder about what is our supported usage of
>> >> ironic-lib. Or even the in
Hi Jim,
Thanks for responding.
>If we do think we need a formal process for making decisions as you
>define above, I think it should be something like:
>
>* bring it up on the mailing list
>* someone /must/ propose a solution along the way, in gerrit, perhaps
> the person that started the thread
Hi,
>But the issue here is just capacity. Whether or not we keep an instance
>in a deleting state, or when we release quota, doesn't change the
>Tempest failures from what I can tell. The suggestions below address
>that.
>
>
>>
>> > > >
>> > > > I think we should go with #1, but instead of erasin
Hi,
We¹re looking for a documentation liaison [1]. If you love (Œlike¹ is also
acceptable) documentation, care that ironic has great documentation, and would
love to volunteer, please let us know.
The position would require you to:
- attend the weekly doc team meetings [2] (or biweekly, depend
Hi,
I recently reviewed a patch [1] that is trying to address an issue with ironic
(master) talking to a ramdisk that has a mitaka IPA lurking around.
It made me think that IPA may no longer be a teenager (yay, boo). IPA now has a
stable branch. I think it is time it grows up and acts responsib
Hi,
Thank you Vlad and Jay for volunteering! Neither of you love documentation, but
Jay is “very willing”, so Jay wins :D
--ruby
On 2016-05-31, 1:23 PM, "Loo, Ruby" wrote:
>Hi,
>
>We¹re looking for a documentation liaison [1]. If you love (Œlike¹ is also
>acceptabl
Hi,
We are stoked to present this week's subteam report for Ironic. As usual, this
is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 23 May 2016)
- Ironic: 204 bugs (+12) + 178 wishlist items. 8 new (+8), 138 in progress, 0
critic
g List (not for usage questions)"
Date: Thursday, 2 June 2016 22:03
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [ironic] versioning of IPA, it is time or is it?
2 июня 2016 г. 10:19 PM пользователь "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
(+
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 "us
Jim,
Thanks for the proposal.
+2 +A. Err, +2 :)
--ruby
On 2016-06-16, 11:12 AM, "Jim Rollenhagen"
mailto:j...@jimrollenhagen.com>> 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.
___
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"
mailto:mmitch...@internap.com>> wrote:
Dear group,
Please enj
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 improv
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
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
__
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
Hi,
We are pleased to present this week's subteam report for Ironic. As usual, this
is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 18 Apr 2016):
- Ironic: 190 bugs (-13) + 173 wishlist items (+7). 17 new (-13), 133 in
prog
The poll closes Sunday night/Monday morning. Ie, whenever Jim gets around to
looking at the numbers Monday (May 16) morning, before our weekly ironic
meeting :)
‹ruby
On 2016-05-09, 6:24 PM, "Jim Rollenhagen" wrote:
>Hey all,
>
>In this morning's meetings we discussed having a virtual midcy
Hi ironic’ers,
I thought we had decided that we would follow the standard deprecation process
[1], but I see that ironic isn’t tagged with that [2]. Although we have
documented guidelines wrt deprecations [3]. But I am not sure we’ve been good
about sending out email about deprecations. Does an
Hi OpenStackClient folks,
Ironic is following the standard deprecation process [1]. We added an OSC
plugin and realized that we didn’t get the commands quite right. This patch [2]
adds the right commands and deprecates the wrong ones. My question is what the
deprecation process might be. Since
the duplicate
email.
‹ruby
On 2016-05-11, 11:46 AM, "Jim Rollenhagen" wrote:
>On Wed, May 11, 2016 at 02:35:12PM +0000, Loo, Ruby wrote:
>> Hi ironic¹ers,
>>
>> I thought we had decided that we would follow the standard deprecation
>> process [1], but I s
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
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 t
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
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
do
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
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-72157680602
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"
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
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" wrote:
> On Mar 15, 2017, at 8:11 AM, Loo, Ruby wrote:
>
> Hi,
>
> The ironic community is looking for volun
ime commitment to take this on.
Thanks,
Rushil
On Wed, Mar 15, 2017 at 11:11 AM, Loo, Ruby
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 docu
uable 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
mailto:ruby@intel.com>> wrote:
Hi,
The ironic community is looking for volunteers to be cross-project liaisons [
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 simil
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] Ne
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
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 :) Th
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)"
+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 questio
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 P
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
al
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
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 yo
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
T
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
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
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
S
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
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 De
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 fairl
+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: [opens
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 th
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
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.openstac
/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
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.
+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 ironi
+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.
+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
+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
i
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 h
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
(+
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/Ironi
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)
=
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'
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"
mailto:juliaashleykre...@gmail.com>> wrote:
Yesterday as a group (jroll, rloo, dtantsur, matt128, devananda,
vdrok, and myself) discussed defa
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,
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
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
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
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]:
- ope
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 'opensta
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 (
aulkner" mailto:j...@jvf.cc>> wrote:
On Aug 29, 2016, at 8:19 AM, Dean Troyer
mailto:dtro...@gmail.com>> wrote:
On Mon, Aug 29, 2016 at 9:41 AM, Loo, Ruby
mailto:ruby@intel.com>> wrote:
I did this because 'passthrough' is more English than 'passthru'
_uuid=, so maybe having both of them is fine.
Vlad
On Mon, Aug 29, 2016 at 7:22 PM, Loo, Ruby
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
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 (
+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
worki
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
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 Lis
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: r
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: Monda
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:
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: r
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
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 duri
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 acros
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: rev
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, Janu
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
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 s
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 reviewin
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, 2
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 r
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 relea
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 y
1 - 100 of 119 matches
Mail list logo
