Monday, 2018-10-08

*** gabys has joined #openstack-ironic00:46
*** gabys has quit IRC00:51
*** hoangcx has joined #openstack-ironic00:53
openstackgerritMerged openstack/ironic-inspector-specs master: fix tox python3 overrides  https://review.openstack.org/60744900:59
*** jiapei has joined #openstack-ironic01:39
*** MattMan_1 has quit IRC01:43
*** MattMan_1 has joined #openstack-ironic01:43
*** tiendc has joined #openstack-ironic02:22
*** trungnv has joined #openstack-ironic03:06
*** jaganathan has joined #openstack-ironic03:17
*** hoangcx has quit IRC04:27
openstackgerritDhanuka proposed openstack/sushy master: WIP: Add `CompositionService` top-level resource  https://review.openstack.org/60856304:53
*** jtomasek has joined #openstack-ironic05:17
openstackgerritKaifeng Wang proposed openstack/ironic-inspector-specs master: Configurable introspection data store  https://review.openstack.org/58769806:11
*** e0ne has joined #openstack-ironic06:21
*** iurygregory has joined #openstack-ironic06:23
*** gabys has joined #openstack-ironic06:58
openstackgerritKaifeng Wang proposed openstack/ironic-inspector master: DNM/TEST grenade job  https://review.openstack.org/60859107:14
*** jtomasek has quit IRC07:16
*** jtomasek has joined #openstack-ironic07:17
*** rcernin has quit IRC07:21
*** moshele has joined #openstack-ironic07:26
*** pvc has joined #openstack-ironic07:35
pvchi anyone not busy here07:35
openstackgerritKaifeng Wang proposed openstack/ironic-inspector master: DNM/TEST grenade job  https://review.openstack.org/60859107:52
*** bandini has joined #openstack-ironic08:03
*** olivierb has joined #openstack-ironic08:06
*** dciabrin has joined #openstack-ironic08:11
*** serlex has joined #openstack-ironic08:11
*** tssurya has joined #openstack-ironic08:15
*** S4ren has joined #openstack-ironic08:25
*** lenka has joined #openstack-ironic08:47
openstackgerritMoshe Levi proposed openstack/ironic-specs master: Add Support for Smart NIC  https://review.openstack.org/58276708:48
*** hoangcx has joined #openstack-ironic08:49
*** stendulker has joined #openstack-ironic08:54
*** gabys has quit IRC08:57
*** jrist has joined #openstack-ironic08:57
*** gabys has joined #openstack-ironic08:57
*** jrist has quit IRC09:02
*** jrist has joined #openstack-ironic09:13
openstackgerritMadhuri Kumari proposed openstack/ironic master: Implement basic interfaces for GraphicalConsole Interface  https://review.openstack.org/54735609:17
*** pvc has quit IRC09:30
*** lenka has quit IRC09:36
openstackgerritMadhuri Kumari proposed openstack/ironic master: Implement basic interfaces for GraphicalConsole Interface  https://review.openstack.org/54735609:40
openstackgerritDmitry Tantsur proposed openstack/ironic-inspector master: Replace subprocess with processutils  https://review.openstack.org/60634909:45
openstackgerritMadhuri Kumari proposed openstack/ironic master: Implement basic interfaces for GraphicalConsole Interface  https://review.openstack.org/54735609:46
openstackgerritMadhuri Kumari proposed openstack/ironic master: VNC Console: Update RPC object and related change  https://review.openstack.org/59956009:47
*** dtantsur|afk is now known as dtantsur09:49
dtantsurTheJulia: \o/ at a grub job09:49
dtantsurmorning ironic09:49
iurygregorygood morning09:51
openstackgerritMadhuri Kumari proposed openstack/ironic master: Implement basic interfaces for GraphicalConsole Interface  https://review.openstack.org/54735609:55
*** iurygregory is now known as iurygregory|lunc09:59
etingofo/ everyone ironic10:00
*** jtomasek has quit IRC10:09
openstackgerritparesh sao proposed openstack/sushy master: Requests session keyword arguments for sushy connector  https://review.openstack.org/60780910:12
*** moshele has quit IRC10:26
*** lenka has joined #openstack-ironic10:26
*** jtomasek has joined #openstack-ironic10:28
*** rcernin has joined #openstack-ironic10:35
*** moshele has joined #openstack-ironic10:49
*** moshele has quit IRC10:59
*** moshele has joined #openstack-ironic11:00
*** stendulker has quit IRC11:07
*** lenka has quit IRC11:09
*** lenka has joined #openstack-ironic11:15
*** rcernin has quit IRC11:17
*** iurygregory|lunc is now known as iurygregory11:32
*** adrianc has joined #openstack-ironic11:33
*** rpittau has joined #openstack-ironic11:35
*** adrianc has quit IRC11:38
*** lenka has quit IRC11:40
*** jrist has quit IRC11:49
*** jrist has joined #openstack-ironic11:50
*** jrist has quit IRC11:54
*** lenka has joined #openstack-ironic11:57
*** jrist has joined #openstack-ironic11:57
*** dnuka has joined #openstack-ironic11:59
*** skazi has quit IRC12:02
*** e0ne has quit IRC12:04
*** rh-jelabarre has joined #openstack-ironic12:08
*** sw3 has joined #openstack-ironic12:12
*** e0ne has joined #openstack-ironic12:13
*** trown|outtypewww is now known as trown12:18
*** weshay_pto is now known as weshay12:19
hjensaso/ etingof :)12:22
etingofhjensas, o/12:22
*** bfournie has joined #openstack-ironic12:23
*** arne_wiebalck_ has joined #openstack-ironic12:25
jroll\o morning all12:26
openstackgerritIlya Etingof proposed openstack/ironic master: Fix unit test run on OS X  https://review.openstack.org/60865512:29
TheJuliaGood morning12:37
dtantsurmorning jroll, TheJulia12:38
jrollhey :)12:38
* TheJulia awaits the coffee to be brewed12:39
* dtantsur is not sure if his good morning to TheJulia and jroll actually got through12:40
jrolldtantsur: indeed, my hey was for you12:40
dtantsurthis Monday is too Monday: my wifi router disconnects all my devices (and only mine) every some minutes12:40
dtantsurokay, so I did not see your hey :)12:40
jrolloof12:40
jrollwell then morning dtantsur :)12:41
jrollI don't miss znc dropping messages on abrupt disconnects12:41
dtantsuryeaaaahh..12:41
dtantsurto better news: I might have figured what is wrong with inspector grenade: https://review.openstack.org/60862012:41
patchbotpatch 608620 - openstack-dev/grenade - nova: do not verify standard resource classes when... - 1 patch set12:41
TheJuliaI figured out why rescue jobs sometimes failed12:49
TheJuliahttps://review.openstack.org/#/c/60840412:49
patchbotpatch 608404 - ironic - Avoid race with nova on power sync and rescue - 2 patch sets12:49
jrollTheJulia: hrm, now we just have a race with our power sync loop :/12:50
* TheJulia needs a coffee iv this morning12:52
etingofgood morning to jroll & TheJulia o/12:53
jrollhey etingof12:53
etingofwhenever I see power sync, it immediately reminds me of my power sync patch... does anybody feel the same way? ;)12:54
TheJuliaetingof: seeking reviews? :)12:56
*** ijw has joined #openstack-ironic12:56
*** ijw has quit IRC12:56
*** ijw has joined #openstack-ironic12:57
etingofTheJulia, yep, this will play well with your morning coffee -- https://review.openstack.org/#/c/607949/12:58
patchbotpatch 607949 - ironic - WIP: Avoid long-pending ipmitool processes - 1 patch set12:58
*** ijw has quit IRC12:59
*** ijw_ has joined #openstack-ironic13:00
jrollTheJulia: oh, we have an exclusive lock, that patch should be okay, I'll add one comment13:00
*** lenka has quit IRC13:01
TheJuliajroll: yeah, we do, which I figured is partially why that was the less painful path13:01
jrollTheJulia: yeah, I'm +2 if you can add the TODO I mentioned :)13:02
TheJuliaI can definitely add a todo13:02
jrollthanks13:04
*** e0ne has quit IRC13:05
*** arne_wiebalck_ has quit IRC13:08
sambetts|afkTheJulia, jroll: with that patch anything watching the notifications will still see a power off event https://github.com/openstack/ironic/blob/master/ironic/conductor/utils.py#L32613:08
sambetts|afkin case we want to hide that too13:09
*** lenka has joined #openstack-ironic13:10
sambetts|afkcould add a flag on the node_power_action function to prevent it updating the db and making the notification something like "silent=True"13:11
*** mjturek has joined #openstack-ironic13:12
jrollI think we'd still want to push that to notifications13:12
jrollif they're being used for auditing or something, it might be needed13:12
sambetts|afkah thats a good point, although feels a little weird to have two different outputs from ironic telling you different things13:14
jrollagree13:14
TheJuliatonyb: is https://review.openstack.org/#/c/594591/ just blocked on our ci?13:14
patchbotpatch 594591 - ironic-python-agent - Add a UUID to the extra-hardware data on ppc64le - 5 patch sets13:14
*** tiendc has quit IRC13:15
jrollsambetts|afk: I really really don't like the premise of the patch, but it can also happen in production, and I think it's probably for the best to land now until we can do a callback to nova to notify it13:15
TheJuliaI agree, we still want to push notifications, it is just that we still have an overall operation in-flight where nova sees it and thinks "oh! I know this!"13:15
sambetts|afkjroll: I can envision something being like "my autiting system is telling me the server got powered off, but I can see a log in nova telling me its turned on"13:15
jrollsambetts|afk: totally13:16
jrollsambetts|afk: but worse is "I did a rescue on this instance and now it keeps shutting down randomly"13:16
TheJuliasambetts|afk: Sure, but it is still overall in an in-flight operation that Ironic is managing13:16
sambetts|afkyeah 100%13:16
sambetts|afkI guess even with this patch there is a brief blip where the db changes13:17
* jroll hopes to get sambetts|afk angry enough about this that he goes and does the work to callback to nova :D13:17
rpittaugit diff13:17
rpittaulol wrong window :D13:17
sambetts|afkjroll: ;) /me is already angry at heat not doing what he wants it to do after 2hrs of waiting for something to deploy13:18
*** skazi has joined #openstack-ironic13:18
jrollsounds like heat :P13:18
dtantsurlol13:21
TheJuliasambetts|afk: there is, the right thing would be to add recognition in nova... except they've recently complained about tight coupling, and it would be even more tight coupling. :(13:21
sambetts|afkTheJulia: yeah tight coupling sucks, but isn't that what driver's in nova are for (you can't tell me the xen driver isn't tightly coupled to xen)? alternatively a flag to node_power_action could prevent the inital db change which is then overridden, or even a "power_state_mask=state.POWER_ON" which can be used to set which power state to mask the server's power state with13:25
TheJuliasambetts|afk: I completely agree with you but they apparently don't see it that way. At the same time, aiui, the power sync loop is mostly outside of our influence other than the status of each instance being checked higher up in the nova-compute process13:27
jrollTheJulia: nova was very supportive of doing a callback when we changed power state13:28
TheJulia+++13:28
TheJuliaThat would effectively prevent this from ever being an issue13:28
sambetts|afkalthough we'd have to have control of the callback from each different action in ironic, so recue could decide not to send it13:29
sambetts|afkbut other actions will13:29
*** arne_wiebalck_ has joined #openstack-ironic13:29
jrolleh? we want to send it always13:30
jrollthat way the nova instance is always up to date, and doesn't think something powered it on out of band13:30
jroll(thus nova wanting to shut it back off)13:30
sambetts|afkexcept we don't for this case, because then nova will think the server has gone off like it does currently13:30
sambetts|afkright?13:31
jrollbut it will also know it's meant to turn back on, so it won't shut it back down13:31
jrollbasically,13:31
jrollif nova thinks something should be off, and sees that it's on, it shuts it down13:31
sambetts|afkright, but nova thinks it should be off, because ironic is tell it its off13:32
sambetts|afkI thought thats what TheJulia's patch is circumventing13:32
jrollright13:32
jrollbut with the callback, ironic would be telling it "hey, I'm turning this on now, update your db"13:32
jrollrather than nova sayign "oh, somehow this came on13:33
TheJuliaand then mashing the "turn it off!" button13:33
jrollbasically, we'd be hooking in here: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L106613:33
sambetts|afkso is the current nova behaviour: if a node goes off out of band it learns a node is off and saves that state, but if a node powers on out of band it powers it back off?13:34
jrollcorrect13:34
jrollit doesn't correct the former because things like "systemctl shutdown" and such13:35
sambetts|afkwow... makes sense but isn't wholely intuative :-P13:36
sambetts|afkand so with the callback nova wouldn't treat an out of band power on as an out of band power on any more? or would we still update our db without a callback to nova if the node was actually out of band powered on?13:40
sambetts|afkso it would still get powered back off13:40
sambetts|afk(although I guess that depends on your setting on the ironic power sync force option)13:40
jrollright, I think we would do it depending on that config13:41
jrollI need to write up some sort of spec13:41
TheJuliaspeaking of specs, any progress on conductor_group support for nova-compute?13:42
* TheJulia is working on the whiteboard atm13:43
jrollno, super busy october downstream13:44
jrollhopefully later this month I can get to it13:44
openstackgerritDmitry Tantsur proposed openstack/ironic stable/rocky: Fixes a race condition in the hash ring code  https://review.openstack.org/60867513:45
TheJuliajroll: k13:46
sambetts|afkjroll, TheJulia: based on what you've said I'm +2 on that patch with the same comment as jroll13:49
*** jaypipes has joined #openstack-ironic13:53
openstackgerritDmitry Tantsur proposed openstack/ironic stable/queens: Fixes a race condition in the hash ring code  https://review.openstack.org/60867813:58
*** dougsz has joined #openstack-ironic14:00
*** skazi has quit IRC14:02
*** lenka has quit IRC14:07
*** munimeha1 has joined #openstack-ironic14:07
*** baha has joined #openstack-ironic14:08
*** SteelyDan is now known as dansmith14:13
*** lenka has joined #openstack-ironic14:15
*** e0ne has joined #openstack-ironic14:17
*** dnuka has quit IRC14:19
*** olivierb has quit IRC14:21
*** beekneemech is now known as bnemec14:22
TheJuliadtantsur: at a glance, it looks like the merge conflict wasn't too bad14:24
dtantsurTheJulia: with the hash ring patch? yeah, more or less straightforward14:24
TheJuliaHey jroll, could you take a look at https://review.openstack.org/#/c/608678 when you get a minute14:24
patchbotpatch 608678 - ironic (stable/queens) - Fixes a race condition in the hash ring code - 1 patch set14:24
*** bfournie has quit IRC14:27
jrollTheJulia: yep will do14:27
openstackgerritMadhuri Kumari proposed openstack/ironic master: Implement basic interfaces for GraphicalConsole Interface  https://review.openstack.org/54735614:28
*** moshele has quit IRC14:31
openstackgerritAija Jaunteva proposed openstack/sushy master: Add support for loading resources from archive file  https://review.openstack.org/58914714:31
*** skazi has joined #openstack-ironic14:32
openstackgerritJulia Kreger proposed openstack/ironic master: Avoid race with nova on power sync and rescue  https://review.openstack.org/60840414:35
TheJuliajroll: thanks!14:37
jrollTheJulia: the email or?14:37
*** jaganathan has quit IRC14:37
TheJuliathe patch14:37
jrollah right14:37
* TheJulia has not looked at email this morning14:37
jrollyou said thanks about 5 seconds after I +1'd the tenks thing via email :P14:38
TheJuliajroll: I just noticed that :)14:39
jrollTheJulia: did you also want to review the queens version? it's good with me14:39
TheJuliaI thought I did...14:40
jrollheh, I'll just leave a +2 then14:40
TheJuliadone14:40
jrollthanks14:41
TheJuliaI've put status updates on a number of items https://etherpad.openstack.org/p/IronicWhiteBoard14:41
*** cdearborn has joined #openstack-ironic14:46
*** stendulker has joined #openstack-ironic14:47
*** etingof is now known as etingof|brb14:48
*** edleafe has joined #openstack-ironic14:51
*** arne_wiebalck_ has quit IRC14:53
*** gcb_ has joined #openstack-ironic14:53
*** etingof|brb has quit IRC14:54
*** e0ne has quit IRC14:54
* devananda starts the coffee14:56
TheJulia++14:56
*** ijw_ has quit IRC14:58
*** ijw has joined #openstack-ironic14:58
*** kaifeng has joined #openstack-ironic14:59
jrollwhat is with you people and computer before coffee :P14:59
jrollmorning deva14:59
devanandamorning, jroll15:00
TheJulia#startmeeting ironic15:00
openstackMeeting started Mon Oct  8 15:00:22 2018 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ironic)"15:00
TheJuliaGood morning eveyrone!15:00
openstackThe meeting name has been set to 'ironic'15:00
TheJuliao/15:00
rpioso\o15:00
kaifengo/15:00
jroll\o15:00
iurygregoryo/15:00
stendulkero/15:00
cdearborno/15:00
*** etingof has joined #openstack-ironic15:00
TheJuliaOur agenda this week is fairly strait forward, and can be found on the wiki.15:01
TheJulia#link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting15:01
etingofo/15:01
TheJulia#topic Announcements / Reminders15:01
*** openstack changes topic to "Announcements / Reminders (Meeting topic: ironic)"15:01
jiapeio、15:01
jiapeio/15:01
TheJulia#info We have published the priorities document for the cycle! \o/15:02
mgoddardo/15:02
jrollwoo15:02
TheJulia#link http://specs.openstack.org/openstack/ironic-specs/priorities/stein-priorities.html15:02
TheJuliaThere should be a story for everything in storyboard at this time. There is also a high level worklist page on storyboard now15:02
TheJulia#link https://storyboard.openstack.org/#!/worklist/49415:03
TheJuliaDoes anyone have anything else to announce or remind us of this week?15:04
* etingof would like to introduce the newborn ironicer - iurygregory \o/15:04
rpiosoWelcome, iurygregory :-)15:04
jrollwelcome!15:04
TheJuliaWelcome iurygregory!15:04
iurygregorythanks everyone o/15:05
mgoddardwelcome15:05
TheJuliaOne reminder, I will be effectively completely AFK all day tomorrow.15:05
stendulkerwelcome15:05
jiapeiwelcome iurygregory15:05
TheJulia#topic Review action items from previous meeting15:06
*** openstack changes topic to "Review action items from previous meeting (Meeting topic: ironic)"15:06
TheJulia#info No action items last week, so moving on!15:06
TheJulia#topic Review subteam status reports15:06
*** openstack changes topic to "Review subteam status reports (Meeting topic: ironic)"15:06
TheJulia#link https://etherpad.openstack.org/p/IronicWhiteBoard15:07
TheJuliaStarting around line 17315:07
TheJuliaI've put initial statuses on some of the items, If you own one of the items according to the priorities, please indicate a status, even if work has not started on that item yet.15:08
TheJuliadtantsur: awesome about a prototype15:09
dtantsur:)15:09
*** e0ne has joined #openstack-ironic15:11
mjtureko/15:11
TheJuliaGreetings mjturek15:12
TheJuliaRegarding python3 first, have any 3rd party CI operators had a chance to look at setting up a job or two to run python3?15:12
mjturekTheJulia not much of an update, but our CI guru doesn't see any issues with it15:13
TheJuliaOkay, it should be fairly easy, duplicate and pass USE_PYTHON3=True into the CI job :)15:14
* TheJulia wonders if we need a "Just for fun" category15:14
TheJuliaAnyway, has everyone had a chance to review and update statuses?15:15
TheJuliaAnd with that, are we ready to proceed?15:15
rpiosoTheJulia: We're looking into it.15:15
rpiosoJust a question of which to cut over.15:16
TheJuliarpioso: in your guys case, you have tons of jobs, I would just cut over the ones you feel most exercise your driver to use Python315:16
rpiosoTheJulia: +115:16
TheJuliaEveryone good to proceed?15:17
* TheJulia gets out the crickets15:18
TheJuliaOkay, I guess we're good to proceed then15:19
TheJulia#topic Deciding on priorities for the coming week15:19
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"15:19
TheJulia#link https://etherpad.openstack.org/p/IronicWhiteBoard15:19
TheJuliaStarting at line 105, I pre-populated a list based based on looking through review this morning15:20
TheJuliaIs there anything anyone feels is missing? That they feel needs to be added or removed?15:20
jrollseems reasonable15:21
TheJuliaAny objections, are we good to proceed15:22
* TheJulia brews more coffee and hands it out15:23
* etingof would love to have the long-running ipmitool processes idea criticized15:23
*** serlex has quit IRC15:23
etingofmeaning https://review.openstack.org/#/c/607949/15:23
patchbotpatch 607949 - ironic - WIP: Avoid long-pending ipmitool processes - 1 patch set15:23
mgoddardlooks good to me15:23
* jroll already gave his feedback :)15:24
TheJuliaetingof: I've not had a chance to look yet, could we take that to discussion?15:24
etingofsure15:24
etingofthank you!15:24
TheJuliaOkay, Moving on then15:24
TheJulia#topic Discussion15:24
*** openstack changes topic to "Discussion (Meeting topic: ironic)"15:24
TheJuliaFirst topic of the day is: Do we have a forward path on deploy templates?15:24
jrollI'm still waiting to see jay's proposal for the full picture15:25
jrollbut I think we have enough to start building it out?15:25
TheJuliajroll: I'm not sure he is going to given the way the discussion went :(15:25
jaypipesjroll: I wasn't planning on continuing any formal proposal considering the discussions.15:25
jrollerm15:26
jrollI thought we landed on agreement with that proposal15:26
jrollother than folks saying it would take too long, I guess15:26
TheJuliaI think we can do the internals without many issues or disagreements, the what information we act upon and how we get that in or populated seems to be lacking agreement15:26
jaypipesjroll: I essentially capitulated.15:26
jrolljaypipes: don't blame you, I guess it's my optimism hoping you were continuing writing instead of arguing :)15:27
jrollTheJulia: again, I think everybody came to agreement in that thread, with a small chunk of "we don't have time!!!!!!"15:27
jrollmaybe I read it wrong15:27
jaypipesjroll: the official line from nova is that virt drivers should feel free to use the required traits list as signals to the virt driver to configure an instance. We advise the virt driver not to put non-schedulable/non-placement-influencing things as required traits.15:28
mgoddardthe recent mail Chris Friesen suggested traits should only be used for configuration of booleans15:28
TheJuliaI feel like with the side discusison, is that the mechanism would be capabilities, and we would just ignore traits15:28
TheJuliaand capabilities would essentially now live forever15:28
jrollcapabilities?15:28
jaypipesjroll: that said, we're not keen to add any deploy_template_X stuff to os-traits standard traits library, so the deploy template traits should be prefixed with CUSTOM_.15:28
TheJuliaAnd then we would have an external overide mechanism15:28
sambetts|afkI thought the purpose of the deploy templates was to turn deploy steps into booleans?15:28
TheJuliajaypipes: We were never ever suggesting that15:29
jrolljaypipes: yep, hear everything you're saying loud and clear15:29
jaypipesTheJulia: johnthetubaguy was.15:29
TheJuliajaypipes: oh... well... Ummm.. Hmm. :(15:29
mgoddardjaypipes: he wanted to use standard traits, but not like that15:29
TheJuliajaypipes: I'll put it this way, my impression and understanding is that we would simply rely upon existing traits, but not do anything like a template definition in os-traits, since it is completely freeform with CUSTOM_15:30
mgoddardif there is a sensible standard trait, then it could be used. He wasn't suggesting putting garbage into os-traits15:30
jaypipesmgoddard: we'd still support standard traits being added to os-traits like BOOT_MODE_UEFI/BOOT_MODE_BIOS or STORAGE_RAID5 etc15:30
jrollso where I believe we're at (or did before this meeting) - we have a path for boolean config things like UEFI, we still need to determine the path for more complex configuration data, and there's a good proposal from jaypipes in that thread. I still think this is the path we should take15:30
jroll^ curious folks' take on that15:30
* jroll gets links15:31
TheJuliajroll: I concur15:31
jaypipesTheJulia: ++15:31
*** TheJulia sets mode: -o TheJulia15:31
* TheJulia doesn't know why she didn't do that sooner15:31
jrollthis is the proposal I think we should take:15:31
jroll#link http://lists.openstack.org/pipermail/openstack-dev/2018-October/135300.html15:31
jrolland I can't find the simple boolean proposal now :|15:32
jrollah, the simple part:15:33
jroll#link http://lists.openstack.org/pipermail/openstack-dev/2018-October/135446.html15:33
jaypipesjroll: so, yeah, I'd love to see that type of solution long term, but it ain't a reality any time soon given current state of thinking in nova.15:33
jaypipesjroll: I'm referring to the first link above.15:34
jrolljaypipes: yeah, social problem, not technical. can be overcome.15:34
jaypipesjroll: and yes, cfriesen's email represents the agreed, simple approach.15:34
TheJuliajroll: It was on another thread if I remember correctly15:34
jrollTheJulia: yes, I linked it :)15:35
jaypipesjroll: to which I responded with the Ironic-ness here: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135474.html15:35
* devananda looks for the jar of unicorn dust, and adds some to their coffee15:35
jrolljaypipes: indeed15:35
jrollanyway, to the original question,15:35
mgoddardso if we were to build a solution for the boolean proposal using traits, and until --config-data exists, abuse it for non-booleans, how would that sit with everyone?15:35
jrolllet's proceed... yes what mgoddard said :)15:36
jroller wait15:36
jrollno, I don't want to abuse traits like that15:36
jrolljust wait for complex things until someone cares enough to push for the right solution15:36
mgoddardso no support for non-booleans?15:36
TheJuliaI totally didn't see jaypipes's further comments below15:36
jrollmgoddard: that's my opinion, yes, we're going to dig ourselves another compatibility hole like capabilities15:37
mgoddardif we build a generic mechanism, can we stop people?15:37
TheJuliamgoddard: I'm good with that15:37
TheJuliamgoddard: maybe if we also sprinkle some of this unicorn dust devananda has been hiding15:37
TheJulias/sprinkle/sprinkle in/15:38
jrollwe can't stop people15:38
jrollbut we can yell that it isn't supported15:38
jrolland then not care about breaking it15:38
mgoddardpeople will just ignore it15:38
jrollthat's fine15:39
mgoddardwhich might be ok, but we should understand that15:39
TheJuliamgoddard: well, if things don't match up or are not viable and don't pass validate, drivers should fail and prohibit deployment15:39
jrolland they may be broken later15:39
dtantsurare we leaning towards delaying RAID for eternity more?15:39
TheJulia(we might  need to augment the list in the ironic virt driver for interfaces cared about at some point)15:39
TheJuliadtantsur: I think we can consider a boolean of raid, but not information about a raid15:39
dtantsurright, so a template still?15:39
mgoddardboolean is quite subtle here - you could argue that RAID5 is a boolean - you either have it or you don't15:39
dtantsuryeah, this ^^ is my question15:40
*** e0ne has quit IRC15:40
TheJuliadtantsur: I think it would still be a template, default configuraitons would need to be populated in the boolean scenario15:40
TheJuliaonce we have something with metadata references, then we can allow more dynamic pass-in of raid configuration15:40
* TheJulia wonders if we're all on the same page and in a relatively happy place15:41
mgoddardso RAID is a boolean?15:41
mgoddard(that's not what I understand boolean to mean...)15:41
TheJuliaso, the gap is the fact that our model requires the configuraiton for raid to be set, the template stored in ironic... I guess in theory could replace the raid template15:42
devanandavery few boot-time-configurable traits are true booleans, because many of them interact with other settings. how about secure boot mode <-> legacy BIOS setting?15:42
TheJuliaerr15:42
TheJuliaraid config15:42
*** e0ne has joined #openstack-ironic15:42
TheJuliaSo in theory, we could have RAID5, RAID10, and a deploy template could swap default configurations around :\15:43
* TheJulia doesn't want raid to derail the boolean nature of secure boot15:43
devanandaTheJulia: I'm pointing out that secure boot actually isn't a simple boolean, unfortunately15:44
devanandawhat if I request secureboot=true, and biosmode=true?15:44
TheJuliadevananda: I think settings would need to fall into the entire bios setting side of the universe where an operator could advertise a specific trait on nodes based upon bios settings they have applied, and as time goes on we could iterrate that15:44
jrollnow I'm thinking - drivers can already read the traits passed to ironic, for the simple things. the simple proposal just adds some mechanisms to nova to pass additional traits to the virt driver; our side is done. I imaging the more complex --config-data proposal would pass this data in a different way, and I think that's where deploy templates need to come in.15:45
TheJuliadevananda: validate() code would need to be sufficent enough to recognize such a condition and prohibit deployment.15:45
devanandaI don't mean to derail, but I don't think this problem is limited to RAID settings15:45
jrollso maybe the deploy templates work needs to propose the ironic side of the --config-data bits, and then we can complete the work in the nova api15:46
TheJuliadevananda: I absolutely agree with you there, but we can only announce 80-ish possible traits to be scheduled upon anyway.15:46
TheJuliadevananda: and all of those things are booleans, they exist or not15:46
devanandaI see15:47
TheJuliajroll: I think that is reasonable as well15:47
*** tssurya has quit IRC15:47
* TheJulia thinks we just need to go off and hack on code at this point15:47
mgoddardjroll: I'd be wary of implementing something without buy in from nova on a high level design15:47
jrollmgoddard: I didn't see anyone from nova opposed to this proposal for reasons other than "it'll take too long and we need to solve this asap"15:48
jrolljaypipes: ^ would you agree with that?15:48
*** e0ne has quit IRC15:49
TheJuliaWe also kind of reached a similar point in prior in-person discussions and it felt like we're were kind of at that point where an ID value was blessed, and even ironic could recieve that in the post to move to active state, and then go lookup the data if needed15:49
jaypipesjroll: reading back, one sec15:50
TheJuliaWell, it should likely be set first, that way validate can do the needful to determine if the deployment is actually possible or not15:50
* TheJulia thinks we still call validate right before deployment anyway, so she is just rambling off into the wind15:50
jrolljaypipes: more pointedly, would you agree that the only resistance to your proposal from nova folks was about the time it will take?15:51
*** lenka has quit IRC15:51
jaypipesjroll: that was the primary resistance, yes.15:53
jrollnod15:53
jaypipesjroll: and that resistance was from ironic as well :)15:53
jrollsure15:53
jrollmgoddard: so I'm not too worried about technical resistance from nova, but we can get a nova spec up sooner than later, so we don't implement it without some sort of buyoff15:54
mgoddardjroll: +1 for submitting a nova spec15:55
TheJuliajaypipes: I think a good chunk of that was also because we didn't want to go to an extreme to get started, but it feels like (with the current discussion) that a happy place has been obtained15:55
TheJuliaSo 5 more minutes for our scheduled time block, I'd like to jump to etingof's ad-hoc topic if we feel that we're at a happy place on the current topic15:56
jrollone more question: who's doing the nova spec? :)15:56
TheJuliaAdditional to that, do we want to get it done before berlin?15:57
jaypipesTheJulia: ++15:57
TheJuliaIf needed, I can take the nova spec on my todo list.15:58
TheJuliaBut I'm totally adding a just for fun review category then :)15:58
TheJulia(Its the only way I'll retain sanity)15:58
* TheJulia takes silence as consensus15:59
jrollTheJulia: take "delegate the nova spec" on your todo list instead :)15:59
TheJuliajroll: heh15:59
TheJuliaetingof: So, https://review.openstack.org/#/c/607949/  :)15:59
patchbotpatch 607949 - ironic - WIP: Avoid long-pending ipmitool processes - 1 patch set15:59
etingofso I think I've discovered that we can't trust ipmitool's timeout/retries values we pass it. if we do, ironic gets blocked for up to 250 secs on a dead node. in the patch I've proposed I am trying to play it safe with ipmitool not to get blocked for long.15:59
TheJuliaI remember we discussed this a long long long time ago (many years) and couldn't reach consensus because it required really cracking open ipmitool's code to understand what it was doing.16:00
TheJuliaI'm +1 to fixing the behavior16:00
etingofwell, I've debugged it a bit16:00
etingofit has adaptive delays here and there16:01
devanandaetingof: just curious, which implementation and version of ipmitool are you having that problem with?16:01
etingofbut that does not matter, the bad thing is that once we call ipmitool on a dead node, we are blocked out for some time16:01
etingofdevananda, 1.816:02
devanandaetingof: I mean, which implementation? there are different codebases out there, which different distros package under similar package names, which all create a binary called "ipmitool"16:02
devanandaagain, don't mean to derail, but that was one of the fixes that I found way-back-when ...16:03
devanandaone of the implementations was a lot less "locky" than others16:03
etingofdevananda, oh, I used one packaged for centos and fedora16:03
*** gcb_ has quit IRC16:03
devanandak16:03
etingofdevananda, but does it matter? do we want to depend on some specific ipmitool?16:03
etingofrather than on the one being shipped with a distro16:04
devanandaif there's a bug in an external package, should we fix it in ironic?16:04
etingofdevananda, it does not sound like a bug16:04
devanandaah16:04
TheJuliaWe kind of already do, I seem to remember we've got comments stating 1.8.15 in our docs.16:04
etingofdevananda, I take it as a way to deal with broken BMCs16:04
jrolletingof: we already depend on a given implementation: https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ipmitool.py#L2716:04
devanandawe also already implemented backoff timing in ironic, to work around issues like this in external commands. I don't know if that code is still around (/me goes and look s for it)16:05
*** moshele has joined #openstack-ironic16:05
* dtantsur suspects we should wrap up the meeting..16:06
etingofdevananda, that backoff thing does not prevent ipmitool to take as much time as it wants16:06
jrollindeed, I'm hungry16:06
TheJuliaYeah...16:06
TheJuliaAnyone have anything else or we'll call this meeting a wrap?16:06
* etingof is sorry for being boring tonight16:06
TheJuliaetingof: your not being boring :(16:06
TheJuliaOkay, calling this meeting over, Thanks everyone!16:07
TheJulia#endmeeting16:07
*** openstack changes topic to "Bare Metal Provisioning | Status: http://bit.ly/ironic-whiteboard | Docs: http://docs.openstack.org/ironic/ | Bugs: https://storyboard.openstack.org/#!/project_group/75 | Contributors are generally present between 6 AM and 12 AM UTC, If we do not answer, please feel free to pose questions to openstack-dev mailing list."16:07
openstackMeeting ended Mon Oct  8 16:07:40 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:07
*** jrist has quit IRC16:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-10-08-15.00.html16:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-10-08-15.00.txt16:07
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-10-08-15.00.log.html16:07
*** iurygregory is now known as iurygregory|away16:09
TheJuliaetingof: by chance have you generated any numbers behind what reducing the timeouts and taking over some of the logic in the conductor would save across 10, 100, 1000 nodes?16:09
* TheJulia hopes nobody has 1000 nodes down, but construction equipment does seem to like datacenter power feeds16:09
etingofTheJulia, no, but I can probably factor in the limited size of the job queue for that16:10
*** kaifeng has quit IRC16:10
etingofto see at what node set conductor would throttle at power sync16:11
TheJuliaetingof: I think numbers are the best way for us to determine a forward path :)16:11
TheJuliaThat way we can at least all relate it and kind of go from there.16:11
etingofTheJulia, some numbers for a single, isolated ipmitool invocation is in the patch16:11
TheJuliaI saw :)16:12
*** jrist has joined #openstack-ironic16:12
TheJuliaKind of where I got the idea of maybe we need a little more so we can put some of this into perspective16:12
etingofTheJulia, the other thing is that the ipmitool situation confuses operators - they set ipmitool to time out in 60 sec, but that may never happen16:13
TheJuliaYeah, it does :(16:13
TheJuliaWe've had a few operators come in and complain about that over the years16:14
etingofthe third thing is that we might have certain timers in conductor (like node power recovery timing), if power sync timeout does not keep up with the settings, those other features might not work as expected16:15
TheJuliaor take far longer than expected in an ideal universe16:17
*** jrist has quit IRC16:17
TheJuliadevananda: by chance did you see if the backoff code was still present?16:17
devanandaetingof: after reading your WIP patch, I like the approach, defaulting to much lower timeouts, but in the stated case of a BMC misbehaving and ipmitool getting kinda stuck ...16:17
devanandaTheJulia: haven't found it yet16:17
TheJuliak, I remember that whole path is kind of confusing too :(16:17
etingofthere is the code that makes sure that we won't invoke ipmitool again if we are by the configured timeout16:18
TheJuliaWell, ipmitool is going to get stuck if the bmc is offline16:18
TheJuliaat least until its internal timeout is reached16:18
devanandait looks like we now check if ipmitool supports the -N -R options, but don't handle timing ourselves in the situation where it doesn't16:18
etingofbut that only works if ipmitool is done16:18
etingofdevananda, let me show you what I mean16:19
devanandato handle dead BMC // stuck ipmitool, I think we would need a reaper daemon, or a periodic task in conductor that invokes 'kill'16:19
devanandaor something along those lines16:19
devanandaI've avoided using fedora's package of ipmitool for years because it used to get badly stuck ... sounds like you're still running into that issue16:19
TheJuliaI think several operators would greatly appreciate a periodic task to hunt/kill stalled/frozen ipmi processes16:20
*** dtantsur is now known as dtantsur|afk16:20
dtantsur|afko/16:20
TheJuliagoodnight dtantsur|afk16:21
etingofdevananda, https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ipmitool.py#L45116:21
devanandaas an aside, there are 3 separate implementations of ipmitool that I found in a minute of googling16:21
devanandafreeipmi, openipmi, and ipmitool/ipmitool16:22
devanandadifferent operators' differing experiences stem from this, to some degree16:22
devanandait may be worth adding notes about that in our docs, not just inline in the code16:22
etingofdevananda, are those ipmi protocol implementations or `ipmitool` binary implementations?16:22
devanandat16:22
devanandathe latter16:23
* etingof have seen ipmiutil16:23
etingofdevananda, http://ipmiutil.sourceforge.net/docs/ipmisw-compare.htm16:23
TheJulialooks like we explicitly reference versioning for ipmitool/ipmitool, but don't explicitly note the caveat16:24
devanandaTheJulia: that's what i remember, and looking at that project on github, it looks familiar16:24
etingofTheJulia, we can probably go the forced ipmitool extermination way16:25
*** gabys has quit IRC16:25
TheJuliawe even link to the correct utility16:25
devanandahttps://github.com/ipmitool/ipmitool   isn't on that list, etingof, but is the one we depend on16:25
TheJulianote: there is a public note someplace about ipmtool moving from sourceforge to github16:25
*** gabys has joined #openstack-ironic16:25
etingofdevananda, it is under the name https://sourceforge.net/projects/ipmitool/16:25
devanandaooh. I see now16:26
devanandayeah, nice note once I clicked through to SF16:26
* etingof goes offline for a brief while16:27
devanandahttps://git.openstack.org/cgit/openstack/ironic/tree/ironic/drivers/modules/ipmitool.py#n44516:28
*** baha has quit IRC16:28
devanandaI think the issue is this execute is a blocking call, no?16:28
TheJuliadevananda: basically, yes16:29
devanandaif ipmitool takes longer than expected to return, that thread is stuck, regardless of how narrow the timing parameters were ... so we would need a periodic task to "reap" stuck processes (assuming that stuck processes really is the concern)16:29
* TheJulia wonders if this is where we need a real dlm 16:30
* TheJulia ducks16:30
*** gabys has quit IRC16:30
devananda:P16:30
* TheJulia has already started on that code and even got a +1 from dmitry :)16:30
TheJuliadevananda: I think we actually kind of need both, try and expediently loop through (which would be bad)... although there is the alternative threading module that someone pointed us to at the PTG that might help.... ?simplify? (well, unlikely, solve is likely the right word) the threading performance issues and lack of additional cpu core use (since greenthreads)16:32
devanandaI have a knee-jerk reaction when someone says "use another python threading model, it'll solve everything"16:33
*** gabys has joined #openstack-ironic16:33
TheJuliaIt won't, that is for sure16:34
*** etingof has quit IRC16:34
TheJuliait it can definitely help solve some of the issues and operator complaints16:34
devanandaI don't see any problems with reducing the default timing and doing incremental backoff timing, like in etingof's proposal.16:34
devanandabut I also don't think it will solve the problem it claims to address16:34
TheJuliaI think the issue is larger than just initial timing for execution16:35
devanandayes16:35
*** stendulker has quit IRC16:37
TheJuliaIf we make a venn diagram of what the issues are, I think etingof's context is one circle that overlaps with your circle, which ultimately too overlaps with my circle of context16:37
devanandaI like diagrams16:37
TheJuliaEveryone likes digrams!16:38
TheJuliadiagrams16:38
*** gabys has quit IRC16:38
* TheJulia just can't type16:38
*** etingof has joined #openstack-ironic16:42
TheJuliawelcome back etingof16:43
etingof;)16:43
etingofdid I miss anything crucial?16:43
TheJuliaetingof: so I think we're at a point where we belive the contextual venn diagram to be three separate circles with some overlap16:43
etingofsounds promising!16:44
etingofwhat are those cycles?16:45
TheJuliaone is the pure blocking length of time for ipmitool, the other is ipmitool actually becoming stuck hard and never returning, the third is "why does ironic only use one cpu, make it go faster!"16:46
TheJulias/cpu/cpu core/16:47
*** gyee has joined #openstack-ironic16:48
etingofthat is: 1) tackle ipmitool timeouts to limit its blocking time 2) kill the hopelessly blocked ipmitool and 3) fork conductor process ?16:48
TheJulia3) I think is going to be a lot of small things and maybe a few efforts as time goes on, but there was that library that someone mentioned which could help things to fork for periodics...16:50
TheJuliabut otherwise yes16:50
etingofI probably missed that library being mentioned16:50
TheJuliaetingof: If I'm rememering correctly, it is mentioned on the etherpad from when we were having that discussion16:51
etingofdo you think I should propose a patch that would kill long-stuck ipmitool processes?16:51
etingofwhich would qualify as cicle #2 while cicle #1 is already proposed16:52
TheJuliaetingof: as a separate worker.... I guess that should work, we would likely need to check lock status in real time though (hey, that pluggable locking patch!)16:52
etingofdoes it need to be a separate worker given that we seem to wait on the forked ipmitool child to exit?16:53
etingofI mean we (as process parent) could kill stuck child, no?16:53
TheJuliaetingof: aiui, a child process being launched halts the thread, so that worker should never be able to become involved16:55
TheJuliahence why I was thinking a new worker16:55
TheJuliarunning inside of the same parent (I think that should work....)16:55
etingofalright, I will take a look16:55
devanandaTheJulia: did work ever get completed to move periodictasks into a separate process?16:57
etingofthe other thing that worries me is this - currently each ipmi session needs a dedicated ipmitool process. it would probably be more scalable if a single ipmitool-like process would be able to handle more than one BMC at a time16:57
TheJuliadevananda: no, I started picking that concept back up recently though which is where some of the ptg discussion that I was referencing came from16:58
openstackgerritMerged openstack/ironic master: Add functionality for individual cleaning on nodes  https://review.openstack.org/58627716:58
*** dougsz has quit IRC16:58
TheJuliadevananda: which is also why I started hacking on improving locking support16:58
devanandaetingof: ah, so there was the pyghmi project, which had the goal of becoming our defacto pure-python parallel execution of ipmi commands16:58
devanandaetingof: but it never gained traction....16:58
etingofwould it make sense to research if we could may be wrap libipmi (the lib behind ipmitool afaik) in some async or MT way?16:59
devanandaTheJulia: gotcha. that might be something I'd be interested in, and/or how that relates to splitting the conductor up a bit16:59
TheJuliaetingof: that exec of ipmitool is a HUGE computational and disk cost16:59
TheJulia(well, cache hit cost, but if cache is low, then disk is still hit16:59
TheJulia)16:59
devanandaTheJulia: any thoughts on reviving pyghmi?16:59
etingofideally, we would have libipmi being called from python as a green thread17:00
TheJuliaJared has been receptive to patches and changes, I think the issue that ultimately resulted in the intree ipminative power interface getting pulled was a lack of real use and then once tried to use it became clear it was not in a good state.17:00
etingofI think the problem with anything other than ipmitool is that other ipmi implementations are less compatibile with existing bmcs17:00
devanandaI completely agree on that exec() call being a huge cost, it would be great to remove it17:00
devanandaetingof: and the general pervasive availability of "ipmitool" as both a system call, and something every operator is familiar with, give it momentum // make anything else have trouble gaining adoption.17:01
etingofif we are to believe Tanenbaum, unix process creation is generally expensive17:02
*** trown is now known as trown|lunch17:02
devanandayes17:03
etingofdevananda, right, that's why if libipmi is as tenacious as ipmitool is, may be python bindings to libipmi would let us do async ipmi calls from conductor?17:03
devanandaalso I would like to see more containerization of the control plane in general17:03
*** baha has joined #openstack-ironic17:04
devanandaie, avoiding packaging ipmitool with ironic-conductor would be good17:05
etingofI think we are likely to stay dependent on ipmitool/libipmi because it is supposedly more compatible with bmcs than pyghmi might be...17:06
etingofI can imagine bmc vendors testing bmc firmware against ipmitool17:07
* TheJulia can confirm this happens17:07
* etingof context switches to homework, but could be preempted17:09
TheJuliaenjoy17:12
* TheJulia thinks she is finally going to take a shower17:12
mosheleTheJulia: hi17:15
TheJuliaHi moshele, sorry I've not replied to the email you sent me, I've been extremely busy so far this morning17:16
mosheleTheJulia: I update the smart nic spec https://review.openstack.org/#/c/582767/ as I understood from isaku. I just wanted explain that we are working with intel to provide a solution that would fit all use cases17:17
patchbotpatch 582767 - ironic-specs - Add Support for Smart NIC - 10 patch sets17:17
mosheleTheJulia: no worries17:18
TheJuliamoshele: Understood, I think the disconnect is on the actual use cases supported by behaviors17:19
TheJuliabehaviors of the existing components that is17:19
TheJuliawe should still sync up though, but I'll try to review the spec after I get some lunch17:19
mosheleTheJulia: ok cool, let me know when it a good time for sync  ( I guess it will be tomorrow it too late in my timezone)17:23
mosheleTheJulia: bon appetit!17:24
*** e0ne has joined #openstack-ironic17:24
*** moshele has quit IRC17:25
*** S4ren has quit IRC17:26
*** e0ne has quit IRC17:29
*** moshele has joined #openstack-ironic17:50
*** moshele has quit IRC17:51
*** e0ne has joined #openstack-ironic17:54
openstackgerritMerged openstack/ironic stable/rocky: Fixes a race condition in the hash ring code  https://review.openstack.org/60867518:03
*** trown|lunch is now known as trown18:11
*** slagle has joined #openstack-ironic18:52
*** tssurya has joined #openstack-ironic18:53
*** sambetts|afk has quit IRC19:07
*** sambetts_ has joined #openstack-ironic19:10
openstackgerritMerged openstack/ironic stable/queens: Fixes a race condition in the hash ring code  https://review.openstack.org/60867819:10
TheJuliajroll: can you pull your -2 from https://review.openstack.org/#/c/579583 ?19:33
patchbotpatch 579583 - ironic-specs - Add virtual Bare Metal Clusters spec - 10 patch sets19:33
jrollTheJulia: done19:33
TheJuliaThanks!19:33
jrollare we calling it agreed, or?19:34
TheJuliaI think leaving open for a couple days then declaring agreed19:35
jrollokay19:35
TheJuliabut with a -2, nobody is going to review it :)19:35
jrollhopefully rloo has a chance to look tomorrow19:35
jrollhopefully they'd read the comment, or the email thread19:35
jroll¯\_(ツ)_/¯19:35
*** sthussey has joined #openstack-ironic19:36
TheJuliaYeah, hopefully19:40
*** slagle has quit IRC19:40
*** dciabrin has quit IRC19:50
*** jtomasek has quit IRC20:13
*** e0ne has quit IRC20:19
*** slagle has joined #openstack-ironic20:20
*** e0ne has joined #openstack-ironic20:20
*** tssurya has quit IRC20:28
*** slagle has quit IRC20:37
*** e0ne has quit IRC20:48
*** pcaruana has quit IRC20:49
*** trown is now known as trown|outtypewww20:59
*** lenka has joined #openstack-ironic21:02
*** sai_p has joined #openstack-ironic21:04
*** baha has quit IRC21:08
*** cdearborn has quit IRC21:39
*** rh-jelabarre has quit IRC21:48
*** ijw has quit IRC22:19
openstackgerritJulia Kreger proposed openstack/ironic master: Create base pxe class  https://review.openstack.org/60878622:28
*** munimeha1 has quit IRC22:50
*** rcernin has joined #openstack-ironic22:50
*** gyee has quit IRC23:57

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!