We're cancelling this week's meeting and next week's meeting due to the
OpenStack Summit and US holidays the following week where some of our core
reviewers will also be on vacation.
If there are any questions, please feel to ask in #openstack-ironic.
See you all in IRC.
On Tue, Nov 6, 2018 at 9:19 AM Joshua Cornutt wrote:
> Another approach would be to make the projects "FIPS aware" where we
> choose the hashing algorithm based on the system's FIPS-enforcing
> state. An example of doing so is what I'm proposing for Django
> (another FIPS-related patch that
On Mon, Nov 5, 2018 at 12:50 PM Dmitry Tantsur wrote:
> On Mon, Nov 5, 2018, 20:07 Julia Kreger wrote:
>> *removes all of the hats*
>> *removes years of dust from unrelated event planning hat, and puts it on
>> for a moment*
>> In my e
I don't know how the cost structure works for Bluejeans, but I've found it
works very well for calls with many people on video. I typically have calls
with 14+ people nearly everyone has their video enabled without a problem.
The limiting factor is really if one participant has limited or somewhat
On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann wrote:
> Sean McGinnis writes:
> > I'm interested in some feedback from the community, particularly those
> > OpenStack deployments, as to whether FIPS compliance  is something
> > are looking for.
> I know we've
*removes all of the hats*
*removes years of dust from unrelated event planning hat, and puts it on
for a moment*
In my experience, events of any nature where convention venue space is
involved, are essentially set in stone before being publicly advertised as
contracts are put in place for hotel
On Wed, Oct 31, 2018 at 7:38 AM Dmitry Tantsur wrote:
> > Ditto, grenade jobs do not cover our tests at all. Also this is the
> very job we
> > run on other projects (nova, neutron, maybe more), so it will be a
> bit painful
> > to remove it.
> > We run the
On Wed, Oct 31, 2018 at 5:44 AM Dmitry Tantsur wrote:
> On 10/31/18 1:36 AM, Julia Kreger wrote:
> > ironic-tempest-dsvm-ipa-wholedisk-agent_ipmitool-tinyipa-multinode -
> This job is
> > essentially the same as our grenade mutlinode
With the discussion of CI jobs and the fact that I have been finding myself
checking job status several times a day so early in the cycle, I think it
is time for ironic to revisit many of our CI jobs.
The bottom line is ironic is very resource intensive to test. A lot of that
is because of the
> PS - You're going to have a long week :|
> Julia Kreger
> October 16, 2018 at 4:44 PM
> Greetings Jimmy,
> Looks like it is still showing up on the schedule that way. I just
> reloaded the website page and it still has b
Looks like it is still showing up on the schedule that way. I just reloaded
the website page and it still has both sessions scheduled for 4:20 PM
local. Sadly, I don't have cloning technology. Perhaps someone can help me
with that for next year? :)
On Tue, Oct 16, 2018
On Mon, Oct 8, 2018 at 8:27 AM Doug Hellmann wrote:
> TC members,
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups .
> Last term we went through a period
+1 to bringing back formal meetings. A few replies below regarding
On Fri, Oct 5, 2018 at 5:38 AM Doug Hellmann wrote:
> Thierry Carrez writes:
> > Ghanshyam Mann wrote:
> >> On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley <
> fu...@yuggoth.org> wrote
> >> > On
On Wed, Oct 3, 2018 at 9:17 AM Mark Goddard wrote:
> On Wed, 3 Oct 2018 at 17:10, James LaBarre wrote:
>> On 10/2/18 10:37 AM, Mark Goddard wrote:
>> On Tue, 2 Oct 2018 at 14:03, Jay Pipes wrote:
>>> On 10/02/2018 08:58 AM, Mark Goddard wrote:
>>> > Tenks is a project for
On Mon, Oct 1, 2018 at 3:37 PM Jay Pipes wrote:
> On 10/01/2018 06:04 PM, Julia Kreger wrote:
> > On Mon, Oct 1, 2018 at 2:41 PM Eric Fried wrote:
> > > So say the user requests a node that supports UEFI because their
> > image
On Mon, Oct 1, 2018 at 2:41 PM Eric Fried wrote:
> > So say the user requests a node that supports UEFI because their image
> > needs UEFI. Which workflow would you want here?
> > 1) The operator (or ironic?) has already configured the node to boot in
> > UEFI mode. Only pre-configured
Greetings, Comments in-line.
On Sat, Sep 29, 2018 at 11:27 PM Moshe Levi wrote:
> Hi Julia,
> I don't mind to update the ironic spec . Unfortunately, I wasn't in the
> PTG but I had a sync meeting with Isuku.
> As I see it there is 2 use-cases:
Very well said, I completely agree with you. We should not hold
ourselves back based upon perceptions of original intended purpose.
Things do change. We have to accept that. We must normalize this fact
in our actions moving forward.
That being said, I'm not entirely sure I'm personally
On Fri, Sep 28, 2018 at 5:00 AM Jeremy Stanley wrote:
> If memory serves, the biggest challenge around that solution was
> determining who approves such proposals since they still need
> per-project specs for the project-specific details anyway. Perhaps
> someone who has recently worked on a
I suspect the avenue of at least three different specs is likely going
to be the best path forward and likely what will be required for each
project to fully understand how/what/why. From my point of view, I'm
quite interested in this from a Nova point of view because that is the
Now that the PTG is over, I would like to go ahead and get the
specification that was proposed to ironic-specs updated to represent
the discussions that took place at the PTG.
A few highlights from my recollection:
* Ironic being the source of truth for the hardware
In my mind, there is value to having a mailing list for things like
important meetings, but it seems more reasonable to just address such
items as needed. At the same time, I agree with ttx, the separate list
is no longer useful. +1
On Fri, Sep 21, 2018 at 5:24 AM Thierry Carrez wrote:
underway over the past few months.
On Tue, Sep 4, 2018 at 2:07 PM John Dickinson wrote:
> On 4 Sep 2018, at 12:16, Julia Kreger wrote:
> > Greetings Stackers!
> > I hereby announce my candidacy for a position on the OpenStack
> > Technical
OpenStack Development Mailing List (not for usage questions
I fully support merging the lists proposed, as well as the interop-wg
list that Chris Hodge proposed. I look forward to the day when cross
posting is no longer a necessary evil.
On Thu, Aug 30, 2018 at 10:04 AM Jeremy Stanley wrote:
> The openstack, openstack-dev, openstack-sigs and
On Mon, Aug 27, 2018 at 9:53 AM Julia Kreger
> Greetings everyone!
> We in Ironic land would like to go into the PTG with some additional
> thoughts, requirements, and ideas as it relates to distributed and
Welcome to the community!
Your interests seem to span quite a bit of the OpenStack community, so
I think it might be a good idea for you possibly look at the
individual teams that interest you the most, and reach out to those
teams and engage in discussion from there.
What may be a
On Mon, Aug 27, 2018 at 9:09 AM Dmitry Tantsur wrote:
> I would like propose the metalsmith library  for inclusion into the bare
> metal project governance.
I am +1 to this. I think this is a logical inclusion to Ironic's
governance, and overall benefits the ecosystem by allowing greater
We in Ironic land would like to go into the PTG with some additional
thoughts, requirements, and ideas as it relates to distributed and
geographically distributed deployments.
As you may or may not know, we did take a first step towards
supporting some of the architectures
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 addressed as needed or
desired by consensus with-in those sub-projects, but we were past due
time to take a look
This is sad news to read, but completely understandable!
Thank you for all of your excellent work on Ironic, and should time
and focus ever make sense later down the road for you to rejoin
ironic-core, know you'll be welcomed back.
On Tue, Aug 21, 2018 at 8:38 AM, John
Greetings fellow ironicans!
As many of you might know an openstack/ironic-staging-drivers
repository exists. What most might not know is that it was
intentionally created outside of ironic's governance.
At the time it was created ironic was moving towards removing drivers
that did not meet
In the past month we released ironic 11.0 and now this week we expect
to release ironic 11.1.
With 11.1, ironic has:
* The ``deploy_steps`` framework in order to give better control over
what consists of a deployment.
* BIOS settings management interfaces for the ``ilo`` and ``irmc``
A few weeks ago I created an etherpad to begin discussion of ideas
and thoughts for items to discuss during the PTG. I've raised this
during our meetings, but not yet raised it to the mailing list.
If you are interested, please feel free to add discussion items,
Given that the ironic-lib version in question is already in
upper-constraints, I think it may be fine. Realistically we do want
people to be running the latest version of ironic-lib when deploying
anyway. That being said, I'm +1 for this, however we need a second
ironic-core to be willing to
to become the the
defacto API driven hardware provisioning toolkit. This will naturally
mean some more work and we will need to continue with our momentum and focus
on enablement and performance enhancements to improve the user experience.
Thank you for your consideration.
Julia Kreger (TheJulia
In my rush to get the email sent, I somehow put the wrong time on the email.
The correct date and time is Tuesday, July 17th, at 12:00 UTC.
On Tue, Jul 10, 2018 at 12:28 PM, Julia Kreger
> Fellow ironicans!
> Lend me your ears! With the cycl
Lend me your ears! With the cycle quickly coming to a close, we
wanted to take a couple hours for high bandwidth discussions covering
the end of cycle for Ironic, as well as any items that need to be
established in advance of the PTG.
We're going to use bluejeans since it
The state of the ironic universe
This month we're trying a new format to keep those interested updated
on what is going on in ironic. The intent is for our weekly updates to
now take the form of a monthly newsletter to cover highlights of what
is going on in the ironic community. If you have
Back to the topic of nitpicking!
I virtually sat down with Doug today and we hammered out the positive
aspects that we feel like are the things that we as a community want
to see as part of reviews coming out of this effort. The principles
change in governance has been updated as a result.
patch that will try to bring them back to their
> initial state, I promise :)
> On 05/29/2018 03:55 PM, Julia Kreger wrote:
>> During the Forum, the topic of review culture came up in session after
>> session. During these discussions,
On Tue, May 29, 2018 at 7:42 PM, Zane Bitter wrote:
> Since I am replying to this thread, Julia also mentioned the situation where
> two core reviewers are asking for opposite changes to a patch. It is never
> ever ever the contributor's responsibility to resolve a dispute between two
On Tue, May 29, 2018 at 3:16 PM, Jay S Bryant wrote:
> On 5/29/2018 2:06 PM, Artom Lifshitz wrote:
>> Yeah, I feel like we're all essentially in agreement that nits (of the
>> English mistake of typo type) do need to get fixed, but sometimes
>> (often?) putting the burden of fixing them on
During the Forum, the topic of review culture came up in session after
session. During these discussions, the subject of our use of nitpicks
were often raised as a point of contention and frustration, especially
by community members that have left the community and that were
On Tue, May 22, 2018 at 5:41 PM, Brian Haley wrote:
> On 05/22/2018 04:57 PM, Jay Pipes wrote:
> I read this the other way - the goal is to get all the forked code from
> StarlingX into upstream repos. That seems backwards from how this should
> have been done (i.e.
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
valuable. The kind of value that comes from operative use.
I also make this nomination knowing that our community landscape
The ironic meeting next week is cancelled as we will have some
attendees in Vancouver for the summit and forum. The next meeting will
be May 28th.
I have updated the wiki page accordingly.
On Fri, May 11, 2018 at 8:20 AM, Dmitry Tantsur wrote:
>> If there are no objections, I'll re-add him next week.
> I don't remember if we actually can add people to these teams or it has to
> be done by the main stable team.
I'm fairly sure I'm the person
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 approve the
changes as three doesn't seem like quite enough when everyone is busy.
On Mon, May 7, 2018 at 4:34 PM, Doug Hellmann wrote:
> As a consumer of team updates from outside of the team, I do find
> them valuable.
Ditto, if I have time to read them.
> I think having a regular email update like that is a good communication
> pattern we've
On Wed, May 9, 2018 at 5:10 PM, Casey Bodley wrote:
> On 05/09/2018 11:40 AM, Casey Bodley wrote:
>> On 05/09/2018 11:22 AM, Matthew Thode wrote:
>>> python-swiftclient prior to 3.2.0 seemed to incidentally support radosgw
>>> tempurls. That is, there was no
About two hours ago, we started seeing Ironic CI jobs failing pep8
with new errors. For some of our repositories, it just seems to be
a couple of lines that need to be fixed. On ironic itself, supporting
this might have us dead in the water for a while to fix the code in
accordance with what
For some time, Rama Yeleswarapu (rama_y) has been graciously sending
out a weekly update for Ironic to the mailing list. We found out late
last week that this contributor would be unable to continue to do so.
While discussing this and searching for a volunteer, we came up with
On Mon, Apr 23, 2018 at 12:04 PM, Michael Turek
> What does everyone think about having Bug Day the first Thursday of every
All for it!
OpenStack Development Mailing List (not
> This looks like some behavior that has been pulled out as part of pbr 4
> (version 3 is being used in the stable branch). Perhaps we want to
> update the pbr constraint there to use the newer version?
And it looks like doing that for stable/queens, at least from an
ironic-inspector point of
One of the topics that came up at during the Ironic sessions at the
Rocky PTG was firmware management.
During this discussion, we quickly reached the consensus that we
lacked the ability to discuss and reach a forward direction without:
* An understanding of capabilities and available vendor
In an effort to have our meeting be a little friendlier to
contributors in Japan and India, we agreed today  to move our
meeting time up two hours to 1500 UTC.
The appropriate change  has been submitted to the irc-meetings repository.
Please let me know if you have any
I'm all for the idea, although that may be because I've been been one
of the people in the past attempting to assist people who have found
specs, and who are are confused or frustrated. I believe it is because
some people latch on to the highly technical design documents when
they can't find
On Wed, Mar 14, 2018 at 4:52 AM, Dmitry Tantsur wrote:
> Just to clarify: only for public endpoints, right? I don't think e.g.
> ironic-python-agent can talk to self-signed certificates yet.
For what it is worth, it is possible for IPA to speak to a self signed
The Ironic PTG Summary - The blur(b) from the East
In an effort to provide visibility and awareness of all the things
related to Ironic, I've typed up a summary below. I've tried to keep
this fairly generalized with enough context and convey action items or
the instances of consensus where
On Tue, Mar 6, 2018 at 2:08 PM, Ivan Kolodyazhny wrote:
> Horizon needs to fix integration tests
> Ironic UI team wants to have their integration tests based on Horizon tests
Not exactly. There are multiple goals, with the central end goal of
preventing breaking changes in
Given the weather impact upon travel out of Dublin the end of this last
week (and this week at this point...), we’re going to cancel today’s
The rough list of priorities for this week:
* Rocky Priorities - Expect a patch to be proposed in the next 24 hours.
On Mon, Mar 5, 2018 at 1:48 AM Dmitry Tantsur wrote:
> On 03/04/2018 09:46 PM, Zhipeng Huang wrote:
> > Thx Julia,
> > Another option is instead of changing meeting time, you could establish a
> > tick-tock meeting, for example odd weeks for US-Euro friendly times and
On Mon, Mar 5, 2018 at 1:47 AM Dmitry Tantsur wrote:
> > Please don't feel the need to select times that would be burdensome to
> > yourself. This is only to gather information as to the time of day
> > that would be ideal for everyone. All times are set as UTC on the
As our community composition has shifted to be more global, the
question has arisen if we should consider shifting the meeting to be
more friendly to some of our contributors in the APAC time zones.
Alternatively this may involve changing our processes to better plan
> No valid host was found. Reason: No conductor service registered which
> supports driver agent_ipmitool. (HTTP 400)
> I can't see anything helpful in the logs. What driver should I be using for
> bifrost? agent_ipmitool seems to be enabled in ironic.conf.
Weird, I'm wondering what the error
As time goes on it is natural for corporate interests to ebb and flow.
Sometimes this comes as a new side project which complements
OpenStack. Sometimes it is a negative hit where several contributors
are abruptly in search of new jobs. Sadly, I think there is some
normalcy to that. What we do
This is saddening news, but thank you for letting us know. It has been a
pleasure working with you!
I’ve gone ahead and removed you from ironic-core.
Until next time!
On Fri, Feb 23, 2018 at 2:02 AM Vasyl Saienko wrote:
> Hey Ironic community!
Thanks to derekh, we have a reservation for our evening gathering at the
We will be gathering at Fegan’s Pub on Tuesday the 27th at 7 PM.
146 Drumcondra Rd Lower
Drumcondra, Dublin 9
If anyone is interested in joining us that has not previously let
Greetings fellow Ironic humanoids!
We have had a planning etherpad  up for a couple weeks collecting ideas.
If you plan on attending the Ironic sessions at the PTG, please post
any additional ideas as well as feedback for the other ideas. We also
need an idea of interest for the purposes of
Since all of our ironic cores have replied and nobody has stated any
objections, I guess it is time to welcome Hironori to the team! I will
make the changes in gerrit after coffee.
On Fri, Feb 9, 2018 at 7:13 AM, Sam Betts (sambetts) wrote:
to grow as a community. While we have
had set backs like all projects, we still have massive potential.
Thank you for your consideration,
Julia Kreger (TheJulia)
OpenStack Development Mailing List (not for usage questions
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
Circling back to this,
Since Dmitry and myself agreed to continue reviewing this work, I
believe we have implicitly agreed to grant this FFE and continue to
land this work. Should anyone disagree, please reply indicating as
such. I will also bring this up during our weekly meeting that is in
> And actually I almost think the holiday time is the best time since the
> fewest number of people are going to care. But maybe I'm wrong. I do wonder
> if nobody is around to watch a 3rd Party CI for two weeks, how likely is it
> to still be working when they get back?
> I'm not vehemently
I believe It would need to involve multiple machines at the same time.
I guess there are two different approaches that I think _could_ be
taken to facilitate this:
1) Provide a facility to use a specific volume as the "golden volume"
to boot up for IPA, and then initiate
On Tue, Nov 21, 2017 at 10:59 AM, Waines, Greg
> i am now thinking that perhaps i am thinking of a USE CASE that is NOT the
> typical IRONIC USE CASE.
> I think the ‘typical’ IRONIC USE CASE is that there are a pool of physical
> that are
On Tue, Nov 14, 2017 at 9:16 AM, Pavlo Shchelokovskyy
> As a core in n-g-s myself I'm happy with either 1) or 2), but not really
> fond of 3) as it kind of stretches the networking-baremetal scope too much
Personally, I'm happy with 1 or 2. I
Greetings ironic folk!
Like many other teams, we had very few ironic contributors make it to
Sydney. As such, I wanted to go ahead and write up a summary that
covers takeaways, questions, and obvious action items for the
community that were raised by operators and users present during the
On Sun, Nov 12, 2017 at 4:03 AM, Thomas Goirand wrote:
> Instead of thinking "this will be more work", why don't you think of the
> LTS as an opportunity to only release OpenStack Chef for the LTS? That'd
> be a lot less work indeed, and IMO that's a very good opportunity for
Sorry! A little late to the discussion with how busy I was last week.
Replies/thoughts in-line with trimmed text.
>> When I tried it I got this
>> [ 370.704896] dracut-initqueue: Warning: iscistart: Could not
>> get list of targets from firmware.
>> perhaps we could alter iscistart to
I guess I'm slightly not clear. In fact, I may be slightly even more
confused since we've discussed this directly. Thinking out loud, there are
two different scenarios of booting from iSCSI.
1) Human created/assigned/associated LUN off of a SAN which we want a node
My perception is that if we need to encourage the spreading of task, roles,
responsibility amongst many. In other words, encourage building trust.
Building trust should hopefully foster a personal sense of investment
and responsibility, hopefully resulting in further diversity
On Thu, Oct 12, 2017 at 12:42 PM, Clay Gerrard wrote:
> To candidates:
> Would you please self select a change (or changes) from
> https://github.com/openstack/governance/ in the past ~12 mo or so where they
> thought the outcome or the discussion/process was
On Thu, Oct 12, 2017 at 11:38 AM, Ed Leafe wrote:
> In the past year or so, has there been anything that made you think “I wish
> the TC would do something about that!” ? If so, what was it, and what would
> you have wanted the TC to do about it?
There have been some great
I would like to submit my candidacy for the Technical Committee.
I have been involved with the OpenStack community since the Juno cycle and
interested in OpenStack while I worked as an engineer supporting data center
hosting operations. My experience having bridged these
> I would like to propose Shivanand (stendulker) to the core team.
OpenStack Development Mailing List (not for usage questions)
>> The short explanation which clicked for me (granted it's probably an
>> oversimplification, but still) was this: Ironic provides an admin
>> API for managing bare metal resources, while Mogan gives you a user
>> API (suitable for public cloud use cases) to your Ironic backend. I
Greetings fellow stackers!
I would like to propose adding Anup Navare to ironic-ui-core. Anup has
been involved with ironic-ui this past cycle as well as various other
areas across ironic which gives me further confidence in making this
I have already informally polled the existing
I did some searching around yesterday near the venue for places to
eat. The area is very spread out, but
http://coloradopubco.com/stapleton-caseys/ is with-in walking
distance. I spoke with some of the staff, and they said they were good
with large groups, and that Mondays is somewhat hit or miss
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
This work is presently underway, although is largely an effort in
Ironic as we must orchestrate volume attachments and detachments
with-in the lifecycle of the machine. We presently have weekly status
meetings which happens to occur in approximately 3 hours, and we
Greetings my ironic cohorts!
It seems everyone is busy this week and we have nothing really to
discuss during today's ironic-ui meeting. As such, today's meeting is
Talk to everyone next week or on #openstack-ironic.
In our new reality, in order to maximize velocity, I propose that we
loosen the review requirements for ironic-ui to allow faster
iteration. To this end, I suggest we move ironic-ui to using a single
core reviewer for code approval, along the same lines as Horizon.
Our new reality is a
Following up for our fearless PTL, the Ironic meetings next week are
cancelled due to the Summit and the schedule of various participants.
This comprises the Team meeting that would be on May 8th, the UI
meeting on May 9th, and the Boot from Volume meeting on May 11th.
As always, you can
For me, sad is an understatement. It would be a lie if I denied tears
at the moment. My brain keeps going back to the sudden tackle hug
milliseconds after NobodyCam and BadCub introduced me to the Ironic
team at the Paris summit. Seeing and having had a chance to work with
a friend that I've had
On Thu, Apr 27, 2017 at 10:21 AM, Dmitry Tantsur wrote:
> 1. Add Ruby Loo (rloo) to the group.
> 2. Remove Jay Faulkner (sigh..) per his request at .
+1 to the sigh.
> 3. Remove Devananda (sigh again..)
+1 *more sighs*
I love it! +1
On Fri, Mar 10, 2017 at 11:28 AM, Heidi Joy Tretheway <
> Hi Ironic team,
> Here’s an update on your project logo. Our illustrator tried to be as true
> as possible to your original, while ensuring it matched the line weight,
On Wed, Mar 1, 2017 at 3:10 PM, Jim Rollenhagen wrote:
> On Wed, Mar 1, 2017 at 9:07 AM, Dmitry Tantsur wrote:
>> Speaking of which, I propose the networking subteam to start (continue?)
>> having their own meeting as well. There is a lot of
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
1 - 100 of 118 matches
Mail list logo