Sam,
Thank you so much for all your contributions to ironic! I'll miss you. I'm
glad you aren't disappearing though :)
--ruby
On Thu, Oct 11, 2018 at 4:41 AM Sam Betts (sambetts)
wrote:
> As many of you will have seen on IRC, I've mostly been appearing AFK for
> the last couple of development
What is there to say? ++ :) and :(.
--ruby
On Thu, Aug 23, 2018 at 2:24 PM Julia Kreger
wrote:
> Greetings everyone!
>
> In our team meeting this week we stumbled across the subject of
> promoting contributors to be sub-project's core reviewers.
> Traditionally it is something we've only
Hi John,
So sorry to hear this but totally understandable! Thanks for letting us
know and for everything you've done! Enjoy life without ironic :)
--ruby
On Tue, Aug 21, 2018 at 10:39 AM John Villalovos
wrote:
> Good morning Ironic,
>
> I have come to realize that I don't have the time needed
Hi,
On Mon, Aug 13, 2018 at 2:40 PM, Julia Kreger
wrote:
> Greetings fellow ironicans!
>
> As many of you might know an openstack/ironic-staging-drivers[1]
> repository exists. What most might not know is that it was
> intentionally created outside of ironic's governance[2].
> ...
>
> This
Hi Julia,
Thanks for bringing this up.
On Mon, Aug 13, 2018, 2:41 PM Julia Kreger,
wrote:
> Greetings fellow ironicans!
>
> As many of you might know an openstack/ironic-staging-drivers[1]
> repository exists. What most might not know is that it was
> intentionally created outside of ironic's
Hi,
I don't want to hijack the initial thread, but am now feeling somewhat
guilty about not being vocal wrt Storyboard. Yes, ironic migrated to
Storyboard in the beginning of this cycle. To date, I have not been pleased
with replacing Launchpad with Storyboard. I believe that Storyboard is
++. Great suggestion!
--ruby
On Sun, May 20, 2018 at 10:45 AM, Julia Kreger
wrote:
> Greetings everyone!
>
> I would like to propose Mark Goddard to ironic-core. I am aware he
> recently joined kolla-core, but his contributions in ironic have been
> insightful and
On Fri, May 11, 2018 at 7:50 AM, Julia Kreger
wrote:
> Greetings folks,
>
> Is there any objection if we re-add Jim to the ironic-stable-maint
> team? He was a member prior to his brief departure and I think it
> would be good to have another set of hands that can
Hi Mike,
If we hold it, I'll (try to) be there :)
Thanks for spearheading this!
--ruby
On Mon, Apr 23, 2018 at 8:04 AM, Michael Turek
wrote:
> Hey everyone!
>
> We had a bug day about two weeks ago and it went pretty well! At last
> week's IRC meeting the idea of
Hi Mike,
This works for me. We can refine/discuss at the bug squashing event.
Thanks!
--ruby
On Wed, Apr 11, 2018 at 2:53 PM, Michael Turek
wrote:
> Sorry this is so late but as for the format of the event I think we should
> do something like this:
>
> 1) Go
On Mon, Feb 5, 2018 at 5:42 PM, Loo, Ruby wrote:
> 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
On Mon, Dec 18, 2017 at 11:29 PM, wrote:
> Thanks for response.
> My recommendation is:
> 1. only allow patches into openstack/ironic-tempest-plugin
> 2. Give Ironic CI owners time period (3 weeks?) to switch their setup to
> only use openstack/ironic-tempest-plugin and
On Fri, Dec 15, 2017 at 9:15 AM, Dmitry Tantsur wrote:
> Hi all!
>
> Half of the Queens cycle is behind us. I'd like to remind about a few
> deadlines and how they affect us:
>
> 1. Jan 18th is the non-client library release deadline. It affects
> ironic-lib and sushy. The
Thank you Julia, for sacrificing yourself and going to Australia; I'm glad
the koalas didn't get you :)
This summary is GREAT! I'm trying to figure out how we take all these asks
into consideration with all the existing asks and TODOs that are on our
plate. I guess the best plan of action (and a
Thanks for bringing this up Dmitry. See inline...
On Tue, Nov 14, 2017 at 5:05 PM, Alex Schultz wrote:
> On Tue, Nov 14, 2017 at 8:10 AM, Dmitry Tantsur
> wrote:
> > Hi folks!
> >
> > This was raised several times, now I want to bring it to the wider
>
On Wed, Nov 15, 2017 at 3:35 AM, Dmitry Tantsur wrote:
> Hi all,
>
> Due to a technical issue we had to have our weekly meeting in our main
> channel this time. And we liked it :) I wonder if we should switch to it.
>
> Pros:
> * easier to find
> * no channel switching
>
>
On Wed, Nov 15, 2017 at 4:41 AM, Shivanand Tendulker
wrote:
> Thank you. I too vote for 'Option 1'.
>
> Thanks and Regards
> Shiv
>
>
>
> On Wed, Nov 15, 2017 at 1:03 AM, Villalovos, John L <
> john.l.villalo...@intel.com> wrote:
>
>> Thanks for sending this out.
>>
>>
>>
On Thu, Nov 16, 2017 at 1:17 PM, Matt Riedemann wrote:
> On 11/16/2017 12:15 PM, Matt Riedemann wrote:
>
>> On 11/16/2017 9:58 AM, Jeremy Stanley wrote:
>>
>>> On 2017-11-16 15:17:58 +0900 (+0900), Takashi Natsume wrote:
>>>
In nova-specs project, there is an
Hi,
Thanks for your 3 votes. Every vote counts; you've convinced me of the
usefulness of having both tags and traits as separate features. I shall
advocate for you all :)
--ruby
On Fri, Oct 27, 2017 at 5:41 AM, Vladyslav Drok wrote:
>
>
> On Fri, Oct 27, 2017 at 12:19 AM,
Sending again, I don't think it went to openstack-operators@.
--ruby
On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote:
> 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
Thanks Julia, for taking this on. I'm actually fine if we take a cab to
wherever, it seems like the PTG is in some sort of 'dead' zone wrt great
food for large groups :-( Having said that, stapleton-caseys works for me,
especially if they take reservations.
My personal preference is for sushi
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
On Wed, Aug 2, 2017 at 10:55 AM, Matt Riedemann wrote:
> ...
>
> b) I think that if we're going to refactor the Nova devref home page to be
> a certain format, then we should really consider doing the same thing in
> the other projects, because today they are all different
On Wed, Oct 19, 2016 at 11:07 PM, Joshua Harlow
wrote:
> Matt Riedemann wrote:
>
>> There are a lot of specs up for review in ocata related to adding new
>> versioned notifications for operations that we didn't have notifications
>> on before, like CRUD operations on
On Fri, Oct 14, 2016 at 7:14 PM, Joshua Harlow
wrote:
>
>> This is exactly what we are planning to do. Work is ongoing to add
>> to_json_schema
>> support for every VersionedObject field [1]. Then we would like to add a
>> small
>> tool to nova that makes it possible to
On Wed, Oct 12, 2016 at 2:13 PM, Devananda van der Veen <
devananda@gmail.com> wrote:
>
>
> On 10/12/2016 05:01 AM, Dmitry Tantsur wrote:
> > Hi folks!
> >
> > I'd like to propose a plan on how to simultaneously extend the coverage
> of our
> > jobs and reduce their number.
> >
> > Currently,
On Tue, Oct 11, 2016 at 12:08 PM, Chris Dent wrote:
>
> Based on the turnout numbers and a bit of unscientific number
> crunching on the voting results it seems that the electorate was
> rather more engaged this time around. That's _great_.
>
> As others have said I
>From my point of view, the rush is so that we can be more efficient with
all of our time/efforts. In ironic, we have a bit of a mess. We now have
duplicated (and perhaps out-of-sync) admin-related information in our
developer docs [1] as well as in the official admin guide [2] -- the latter
On Mon, Sep 12, 2016 at 12:38 PM, Dean Troyer <dtro...@gmail.com> wrote:
> On Mon, Sep 12, 2016 at 10:51 AM, Ruby Loo <opensr...@gmail.com> wrote:
>
>> My preference is:
>>
>> * openstack baremetal driver show --raid-logical-disk-properties
>>
>
On Tue, Sep 6, 2016 at 8:11 AM, Galyna Zholtkevych <
gzholtkev...@mirantis.com> wrote:
> Dear all,
>
> Ironic community needs a help to decide on the specification
>
> of the openstack client command that provide the same functionality as
>
> 'ironic driver-raid-logical-disk-properties' .
>
>
Hi,
On Sun, Aug 21, 2016 at 9:08 PM, Dean Troyer wrote:
> We're excited to pre-announce the release of OSC 3.0.0. The release is
> expected to be approved by the release team during their working hours on
> Monday 22 Aug 2016.
>
> This is a **huge** release, and we shuffled
Hi,
We are yodelling 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 July 2016)
- Ironic: 216 bugs (+15) + 204 wishlist items (+3). 21 new (+8), 160 in
progress
Sweet. Thanks Jim (and everyone else that made this happen).
I do want to make sure there is one "source of truth" to the API
documentation. We are already generating REST API documentation at
http://docs.openstack.org/developer/ironic/webapi/v1.html. The info for
this comes from docstrings etc
Hi,
At the Austin summit, we had a session where we discussed and decided on
what the top priorities would be for ironic, in the newton development
cycle. The etherpad [1] captures that discussion, and there is a patch up
to add the newton priorities to our specs [2].
Everyone, and in particular
Hi,
Currently, ironic doesn't support ("live", "online", "rolling", or
minimal-downtime) upgrades between named versions of ironic. (Where "named
version" is the final release or stable release that is associated with a
development cycle). So for example, Liberty -> Mitaka release.
We've been
On Mon, Apr 18, 2016 at 3:10 PM, Ruby Loo <opensr...@gmail.com> wrote:
> ...
> Network isolation (Neutron/Ironic work) (jroll)
> ===
> - Still needs review
> - cross-project session tuesday on the future of bare meta
Hi,
We are overjoyed to present this week's subteam report for Ironic. As
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 11.04.2016):
- Ironic: 203 bugs (+3) + 166 wishlist items (+3). 30 new (+5), 134 in
progress
Hi,
We are nerdy to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 04.04.2016):
- Ironic: 200 bugs (+4) + 163 wishlist items. 25 new, 136 in progress (+1),
0
Yes, I think it would be good to have a summit session on that. However,
before the session, it would really be helpful if the folks with proposals
got together and/or reviewed each other's proposals, and summarized their
findings. You may find after reviewing the proposals, that eg only 2 are
Hi,
We are merry to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 28.03.2016):
- Ironic: 196 bugs (+17) + 163 wishlist items (-1). 28 new (+3), 135 in
progress
Hi,
We are lucky to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 14.03.2016):
- Ironic: 179 bugs (+12) + 164 wishlist items (-10). 25 new (+6), 124 in
progress
On 24 March 2016 at 15:08, Jim Rollenhagen wrote:
> Hey all,
>
> I'm nominating Julia Kreger (TheJulia in IRC) for ironic-core. She runs
> the Bifrost project, gives super valuable reviews, is beginning to lead
> the boot from volume efforts, and is clearly an expert in
Hi,
We are keen 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 07.03.2016):
- Ironic: 167 bugs (+10) + 174 wishlist items (-1). 19 new (+3), 121 in
progress (-2),
Hi,
We are jubilant 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 07.03.2016):
- Ironic: 167 bugs (+10) + 174 wishlist items (-1). 19 new (+3), 121 in
progress
Hi,
We are itchy 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 29.02.2016):
- Ironic: 157 bugs (-5) + 175 wishlist items (-3). 16 new, 115 in progress
(-8), 0
> Hi,
>>
>> > Ironic'ers, please remember to follow the RFE process; especially the
>> cores.
>> >
>> > I noticed that a patch [1] got merged yesterday. The patch was
>> associated
>> > with an RFE [2] that hadn't been approved yet :-( What caught my eye was
>> > that the commit message didn't
Hijacked from ' [openstack-dev] [ironic] Remember to follow RFE process'
thread:
> Should we revert the patch [1] for now? (Disclaimer. I haven't looked at
>> the
>> > patch itself. But I don't think I should have to, to know what the API
>> > change is.)
>> >
>>
>> Thanks for calling it out
Hi,
Ironic'ers, please remember to follow the RFE process; especially the cores.
I noticed that a patch [1] got merged yesterday. The patch was associated
with an RFE [2] that hadn't been approved yet :-( What caught my eye was
that the commit message didn't describe the actual API change so I
Hi,
We are happy 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 22.02.2016):
- Ironic: 162 bugs (+6) + 178 wishlist items (+3). 16 new (+2), 123 in
progress (+5),
Hi,
We are glad 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 08.02.2016):
- Ironic: 156 bugs (-1) + 175 wishlist items (+5). 14 new, 118 in progress
(+2), 0
Hi,
We are elated to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 25.01.2016):
- Ironic: 151 bugs (-1) + 171 wishlist items (+7). 14 new (-1), 111 in
progress
Gate failures dominated the news last week and as this week starts to pick
up steam, it looks like gate failures will again dominate the news. On
other fronts...
Hi,
We are delighted to present this week's subteam report for Ironic. As
usual, this is pulled directly from the Ironic
Hi,
We are cool to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 11.01.2016):
- Ironic: 148 bugs (+1) + 162 wishlist items (+4). 15 new (+1), 102 in
progress
On 11 January 2016 at 10:27, Doug Hellmann wrote:
> ...
>
>
> There are a few libraries on the list, too (automaton, ironic-lib), and
> that's confusing. It would be interesting to know how they're using
> table output.
>
> Doug
>
>
As far as ironic-lib goes, I took a
Hi,
We are buzzed to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 04.01.2016):
- Ironic: 147 bugs (-4) + 158 wishlist items (+9). 14 new (-9), 99 in
progress
Hi,
We are amazed to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 21.12.2015):
- Ironic: 151 bugs (+8) + 149 wishlist items. 23 new (+5), 92 in progress
(+1), 0
Hi,
We are eager to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- (no diff)
- Ironic: 143 bugs + 149 wishlist items. 18 new, 89 in progress, 0
critical, 14 high and 9 incomplete
-
Hi,
We are overjoyed to present this week's subteam report for Ironic. As
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
(diff with Dec 7)
- Open: 179 (+4). 16 new (+4), 58 in progress (-3), 0 critical (-1), 13
high (-3) and 9
On 23 November 2015 at 18:35, Shraddha Pandhe
wrote:
> Hi,
>
> I would like to know how everyone is using maintenance mode and what is
> expected from admins about nodes in maintenance. The reason I am bringing
> up this topic is because, most of the ironic
Hi,
We are pleased to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
(diff with Nov 30)
- Open: 175 (+1). 12 new (+1), 61 in progress (+1), 1 critical (+1), 16
high and 9
On 30 November 2015 at 11:25, Gururaj Grandhi
wrote:
> Hi,
>
>
>
> This is to announce that we have setup a Third Party CI
> environment for Proliant iLO Drivers. The results will be posted under
> "HP Proliant CI check" section in Non-voting mode. We will
On 30 November 2015 at 10:19, Derek Higgins wrote:
> Hi All,
>
> A few months tripleo switch from its devtest based CI to one that was
> based on instack. Before doing this we anticipated disruption in the ci
> jobs and removed them from non tripleo projects.
>
> We'd
Hi,
We are elated to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
(diff with Nov 23)
- Open: 174 (+3). 11 new, 60 in progress, 0 critical, 16 high and 11
incomplete
- Nova bugs
On 25 November 2015 at 18:02, Jim Rollenhagen
wrote:
> Hi all,
>
> We're approaching OpenStack's M-1 milestone, and as we have lots of good
> stuff in the master branch, and no Mitaka release yet, I'd like to make
> a release next Thursday, December 3.
>
> First, I've
On 20 November 2015 at 18:32, Ben Nemec wrote:
> On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote:
> > Hi,
> >
> >> Also keep in mind that DEBUG logging, while still should have some
> masking
> >> of data, since it is explicitly called out (or should be) as not safe
>
On 19 November 2015 at 08:39, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com> wrote:
> Hi all,
>
> +1 for specs in general, big features require a proper review and
> discussion for which LP is not a good choice.
>
> +1 for not requiring a spec for small features, LP BP is enough for just
>
Hi,
We are stoked to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
(diff with Nov 16)
- Open: 171 (+4). 11 new (+1), 60 in progress (-1), 0 critical, 16 high
(+2) and 11
On 17 November 2015 at 01:34, Naohiro Tamura
wrote:
> Ruby,
>
> Thanks for taking care of our weekly status report.
> I'd like to just let you know that the iRMC part is somehow consolidated
> with old statuses which I reported two and three weeks ago.
> If this
On 19 November 2015 at 09:25, Brad P. Crochet wrote:
> I have pushed up a draft of the spec. Let's move comments there.
>
> I tried to incorporate as much as I could from the discussion here.
> There was a lot of disjointed suggestions and was a bit difficult to
> follow. So
> > Another idea I floated last week was to do a virtual midcycle of sorts.
> > Treat it like a normal midcycle in that everyone tells their management
> > "I'm out for 3-4 days for the midcycle", but they don't travel anywhere.
> > We come up with an agenda, see if there's any planning/syncing
Hi,
I think we all agree that it isn't OK to log credentials (like passwords)
in DEBUG logs. However, what about other information that might be
sensitive? A patch was recently submitted to log (in debug) the SWIFT
temporary URL [1]. I agree that it would be useful for debugging, but since
that
On 15 November 2015 at 16:47, Sukhdev Kapur wrote:
> Folks,
>
> We are canceling this week's Ironic-neutron integration meeting. I have a
> family obligation to take care of and I have not been able to find a
> replacement person who can chair this meeting. Therefore, we
Hi,
We are stoked to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(diff with Nov 9)
- Open: 167 (-4). 10 new (-2), 61 in progress (-2), 0 critical, 14 high and
11 incomplete (+1)
- Nova
On 10 November 2015 at 11:31, Dmitry Tantsur wrote:
> On 11/10/2015 05:21 PM, Brad P. Crochet wrote:
>
>> On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur
>> wrote:
>>
>>> Hi all!
>>>
>>> I'd like to seek consensus (or at least some opinions) on patch
On 10 November 2015 at 12:08, Dmitry Tantsur wrote:
> On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote:
>
>> Hi,
>>
>> In the last Ironic meeting [1] we started a discussion about whether
>> we need to have a mid-cycle meeting for the Mitaka cycle or not. Some
>> ideas
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(diff with Oct 19)
- Open: 171 (+11). 12 new (+9), 63 in progress (+22), 0 critical, 14 high
(+3) and 10 incomplete (-1)
- Nova bugs with
>
> 2) Driver docs may not be backported to stable branches. This is a
> stable maintenance policy, not an Ironic policy. This problem is
> somewhat unique to Ironic as most major projects have deployer docs in
> the Ops guide repo, rather than in the code repo. I'm going to chat with
> some
Hi Ramesh,
On 15 October 2015 at 11:53, Ramakrishnan G
wrote:
>
>
> So what all are the problems ?
> 1) Ability to update the driver documentation not-related to Ironic easily
> without waiting.
> 2) To save some core reviewers time who might not be familiar with
Hi Wan-yen,
On 19 October 2015 at 01:46, Wan-yen Hsu wrote:
>
>
> I fully agreed with Ramesh. There is a need for driver owners to be able
> to quickly update their driver’s document. Particularly, vendor's drivers
> have strong
>
What do you mean by 'quickly'? Quicker
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(diff with Oct 12, no diff for inspector)
- Open: 150 (+7). 3 new (+1), 41 in progress (+5), 2 critical (+2), 11 high
(-1) and 11 incomplete
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
- (diff with Oct 5, no diff for inspector)
- Open: 143 (+6). 2 new (-2), 36 in progress (+2), 0 critical, 12 high
(+5) and 10 incomplete
Looking forward to more cores!!!
On 8 October 2015 at 17:47, Jim Rollenhagen wrote:
> Hi all,
>
> ...
I'd like to nominate Vladyslav Drok (vdrok) for the core team. His reviews
> have been super high quality, and the quantity is ever-increasing. He's
> also started
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
- (diff with Sep 28, no diff for inspector)
- Open: 137 (+2). 4 new (-5), 34 in progress (-2), 0 critical, 7 high
and 13 incomplete (+4)
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(diff with Sep 21)
- Open: 135 (-1). 9 new (+2), 36 in progress (-5), 0 critical, 7 high (-5)
and 9 incomplete
- Nova bugs with Ironic tag:
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
As of Mon, Sep 21 (diff with Sep 14)
- Open: 136 (-6). 7 new (-4), 41 in progress (-7), 0 critical, 12 high (+1)
and 9 incomplete
- Nova
Hi Subteam Leads,
In today's weekly meeting[1], it was requested that if you have no updates,
to please indicate that in the status report, so that we can distinguish
between no-update versus not-providing-a-status-report.
If you aren't sure whether you're a lead, we think you are if your name
On 17 September 2015 at 21:50, Jim Rollenhagen
wrote:
This may also mean in-band RAID configuration may not land; the
> interface in general did land, and drivers may do out-of-band
> configuration. We assumed that in-band RAID would be done through
> zapping. However,
On 11 September 2015 at 04:56, Dmitry Tantsur wrote:
> Hi all!
>
> Our install guide is huge, and I've just approved even more text for it.
> WDYT about splitting it into "Basic Install Guide", which will contain bare
> minimum for running ironic and deploying instances, and
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
As of Mon, Sep 14 (diff with Sep 7)
- Open: 142 (+4). 11 new (+1), 48 in progress, 0 critical, 11 high and 8
incomplete (-1)
- Nova bugs
On 3 September 2015 at 08:22, Thierry Carrez wrote:
> ...
> In particular, the current proposal says:
>
> "At the very minimum the feature [...] should be marked deprecated (and
> still be supported) in the next two coordinated end-of-cyle releases.
> For example, a
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
As of Mon, Aug 31 (diff with Aug 24)
- Open: 144 (+3). 9 new (+4), 50 in progress, 0 critical, 13 high and 10
(+1) incomplete
- Nova bugs
Hi,
As (most of) you are aware, in this cycle, ironic decided to switch to a
feature-based release model[0].
Our first semver release, 4.0.0, was tagged this week but a few more things
need to be ironed out still (hopefully there will be an announcement about
that in the near future).
What I
On 20 August 2015 at 23:19, Ruby Loo rlooya...@gmail.com wrote:
On 18 August 2015 at 17:13, Ruby Loo rlooya...@gmail.com wrote:
On 18 August 2015 at 13:08, Lucas Alvares Gomes lucasago...@gmail.com
wrote:
HI
Hi, I'd like to make sure I understand. Is it the case that ideally,
if we
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
As of Mon, Aug 24 (diff with Aug 10)
- Open: 141 (-1). 5 new (-1), 50 in progress, 0 critical, 13 high (+1) and
9 incomplete
- Nova bugs
On 18 August 2015 at 17:13, Ruby Loo rlooya...@gmail.com wrote:
On 18 August 2015 at 13:08, Lucas Alvares Gomes lucasago...@gmail.com
wrote:
HI
Hi, I'd like to make sure I understand. Is it the case that ideally,
if we
could go back in time, we'd like to change the client so
that I may not feel the need to reply :-)
--ruby
maybe chop off this and above when replying :-)
On 17 August 2015 at 20:20, Robert Collins robe...@robertcollins.net
wrote:
On 11 August 2015 at 06:13, Ruby Loo rlooya...@gmail.com wrote:
Hi, sorry for the delay. I vote no. I understand
Apologies, forgot to add [ironic] to the subject.
On 18 August 2015 at 13:27, Ruby Loo rlooya...@gmail.com wrote:
Hi,
I want to start a different thread on this topic because I don't think
this is about whether/how to do API microversions. Rather, given that we
are going to support
On 17 August 2015 at 20:20, Robert Collins robe...@robertcollins.net
wrote:
On 11 August 2015 at 06:13, Ruby Loo rlooya...@gmail.com wrote:
Hi, sorry for the delay. I vote no. I understand the rationale of
trying to
do things so that we don't break our users but that's what
On 18 August 2015 at 13:08, Lucas Alvares Gomes lucasago...@gmail.com
wrote:
HI
Hi, I'd like to make sure I understand. Is it the case that ideally, if
we
could go back in time, we'd like to change the client so it defaults to
1.1?
AFAIUI, yes
But since we can't, the next client that
On 1 August 2015 at 05:16, Lucas Alvares Gomes lucasago...@gmail.com
wrote:
Hi,
It sounds like we all agree -- the client we ship should default to a
fixed,
older version. Anyone who wants newer functionality can pass a newer
version
to their client.
Here's the current state of
1 - 100 of 155 matches
Mail list logo