Monday, 2018-07-30

*** linkmark has quit IRC00:12
*** livelace has quit IRC00:19
*** livelace has joined #openstack-ironic00:19
*** phuongnh has joined #openstack-ironic01:13
*** liuzz has joined #openstack-ironic01:14
*** tiendc has joined #openstack-ironic01:31
*** r-daneel has joined #openstack-ironic01:33
*** prasen has joined #openstack-ironic01:52
*** trungnv has joined #openstack-ironic02:24
*** bfournie has joined #openstack-ironic02:25
*** prasen has quit IRC02:26
openstackgerritNguyen Van Trung proposed openstack/ironic master: Update docs for troubleshooting with maintainance mode  https://review.openstack.org/58512602:50
*** gkadam has joined #openstack-ironic03:30
*** yolanda_ has joined #openstack-ironic03:38
*** links has joined #openstack-ironic03:39
*** yolanda has quit IRC03:41
openstackgerritlei zhang proposed openstack/ironic master: Mark the ZeroMQ driver deprecated  https://review.openstack.org/58193603:59
*** sambetts_ has quit IRC04:07
*** sambetts_ has joined #openstack-ironic04:09
*** links has quit IRC04:15
*** hoonetorg has quit IRC04:28
*** jaganathan has joined #openstack-ironic04:30
*** links has joined #openstack-ironic04:33
*** rbartal has joined #openstack-ironic04:39
*** hoonetorg has joined #openstack-ironic04:45
*** ddurst has quit IRC04:53
*** ddurst has joined #openstack-ironic04:58
*** phuongnh has quit IRC05:03
*** tiendc has quit IRC05:03
*** trungnv has quit IRC05:03
*** phuongnh has joined #openstack-ironic05:04
*** tiendc has joined #openstack-ironic05:04
*** trungnv has joined #openstack-ironic05:04
*** rbartal has quit IRC05:06
*** e0ne has joined #openstack-ironic05:28
openstackgerritAnkit Kumar proposed openstack/ironic-tempest-plugin master: Test cases for iLO drivers in standalone ironic  https://review.openstack.org/53565205:33
*** e0ne has quit IRC06:00
*** ltomasbo has joined #openstack-ironic06:07
*** mjura has joined #openstack-ironic06:09
*** mjura has quit IRC06:09
*** mjura has joined #openstack-ironic06:13
*** jtomasek has joined #openstack-ironic06:18
*** melwitt has quit IRC06:31
*** sdake has quit IRC06:31
*** melwitt has joined #openstack-ironic06:32
*** melwitt is now known as Guest971406:32
*** sdake has joined #openstack-ironic06:32
*** sdake has quit IRC06:32
*** sdake has joined #openstack-ironic06:32
*** threestrands has joined #openstack-ironic06:38
*** threestrands has quit IRC06:38
*** threestrands has joined #openstack-ironic06:38
*** sambetts_ has quit IRC06:41
*** sambetts_ has joined #openstack-ironic06:45
*** pcaruana has joined #openstack-ironic06:56
*** tesseract has joined #openstack-ironic07:04
*** skazi has joined #openstack-ironic07:07
*** rbartal has joined #openstack-ironic07:08
*** rcernin has quit IRC07:09
*** pcaruana has quit IRC07:14
*** pcaruana has joined #openstack-ironic07:18
openstackgerritHarald Jensås proposed openstack/networking-baremetal master: Remove testrepository and .testr.conf  https://review.openstack.org/58167907:19
*** yolanda_ is now known as yolanda07:21
*** arnewiebalck__ has joined #openstack-ironic07:22
*** ajya has joined #openstack-ironic07:26
*** rbartal has quit IRC07:29
*** threestrands has quit IRC07:32
*** jtomasek_ has joined #openstack-ironic07:34
*** jtomasek has quit IRC07:34
*** AlexeyAbashkin has joined #openstack-ironic07:39
*** rpittau has joined #openstack-ironic07:43
*** mgoddard has joined #openstack-ironic07:47
*** dougsz has joined #openstack-ironic07:47
*** rbartal has joined #openstack-ironic07:48
*** e0ne has joined #openstack-ironic07:50
*** hjensas has joined #openstack-ironic08:04
*** hjensas has quit IRC08:04
*** hjensas has joined #openstack-ironic08:04
*** derekh has joined #openstack-ironic08:08
openstackgerritAija Jaunteva proposed openstack/sushy-tools master: Cleanup libvirt driver for BIOS emulator  https://review.openstack.org/58696708:09
*** tssurya has joined #openstack-ironic08:21
*** w-miller has joined #openstack-ironic08:22
*** mbeierl has quit IRC08:25
*** ajya has quit IRC08:26
*** ajya has joined #openstack-ironic08:26
*** etingof has quit IRC08:28
*** mgoddard has quit IRC08:29
*** etingof has joined #openstack-ironic08:30
*** d0ugal has joined #openstack-ironic08:31
*** d0ugal has quit IRC08:31
*** d0ugal has joined #openstack-ironic08:31
*** rbartal has quit IRC08:32
*** serlex has joined #openstack-ironic08:45
*** rbartal has joined #openstack-ironic08:45
yolandahi, is ironic gate broken? i get errors like  Error when trying to get requirement for VCS system Command "git config --get-regexp remote\..*\.url" failed with error code 1 in /opt/stack/keystone, falling back to uneditable format08:45
*** skazi has quit IRC08:53
*** rbartal has quit IRC08:53
etingofyolanda, is it reported in some patch?09:01
yolandaetingof, http://logs.openstack.org/91/585991/9/check/ironic-dsvm-standalone/78a1c01/09:04
*** rbartal has joined #openstack-ironic09:05
openstackgerritKaifeng Wang proposed openstack/ironic master: Prevents deletion of ports for active nodes  https://review.openstack.org/47027309:05
*** arnewiebalck__ has quit IRC09:08
etingofyolanda, hmm, does it fail anything in the end?09:10
etingofyolanda, btw, I see other weird errors in the log -- http://logs.openstack.org/91/585991/9/check/ironic-dsvm-standalone/78a1c01/job-output.txt.gz#_2018-07-30_08_05_47_32572309:11
yolandamm, you are right09:11
yolandathat other may be a red herring09:12
etingofyolanda, this seems to be the last nail in the coffin -- http://logs.openstack.org/91/585991/9/check/ironic-dsvm-standalone/78a1c01/job-output.txt.gz#_2018-07-30_08_07_15_18981509:14
yolandaah, again those api version problems09:14
* etingof looks into that suspicious KeyError thing09:15
yolandai tested in my local devstack and works, but i needed to depen on the python-ironicclient patch09:15
yolandai added a depends-on here as well, but doesn't seem to work09:15
etingofyolanda, which patch?09:17
yolandahttps://review.openstack.org/#/c/586508/09:17
patchbotpatch 586508 - python-ironicclient - Add management of automated_clean field09:17
yolandathe one that fails is https://review.openstack.org/#/c/585991/09:18
patchbotpatch 585991 - ironic - Add automated_clean field to the node object and API09:18
yolandai tried to depend on the first one, because locally, on my devstack, bumping the client version seems to help09:18
yolandabut that's strange, i don't recall having to bump version on the client to add bios field09:19
*** sambetts_ is now known as sambetts09:19
*** skazi has joined #openstack-ironic09:20
*** skazi has quit IRC09:21
*** rpioso is now known as rpioso|afk09:22
etingofyolanda, this is not the right version, is it? -- http://logs.openstack.org/91/585991/9/check/ironic-dsvm-standalone/78a1c01/job-output.txt.gz#_2018-07-30_07_59_46_27604109:24
yolandaetingof, i guess the patch is still running at zuul. But the logs looks similar anyway09:24
yolandathat's from the prev recheck09:24
* etingof expects the job to pull dependent patch, not the master branch... -- http://logs.openstack.org/91/585991/9/check/ironic-dsvm-standalone/78a1c01/job-output.txt.gz#_2018-07-30_07_51_28_59496909:25
yolandaetingof, by the time of that log, the depends-on was already there09:26
yolandathen, seems that the ci is not acting properly on the depends-on...09:26
etingofI am vaguely recalling the cross-repo dependency does not work in some cases, possibly for libraries... and this seems not to work as well09:26
yolandaanyway Julia put a comment, telling that my patch should not depend on the client api version... but i cannot make it work without bumping it09:27
yolandai tested on devstack and couldn't make it work until i bumped client to 1.4709:27
yolandai may miss something on the ironic rest api, but i double checked with the bios patch and i don't see differences09:28
etingofwell, this api versioning thing needs to be figured out I think ;)09:29
yolandayes09:29
yolandahas there been some change recently, since we landed the bios rest api?09:30
yolandain terms of api versioning?09:30
etingofyolanda, this is what I do not know yet ;)09:30
etingofyolanda, btw, that job does not seem to fail on CI generally -- http://ci-watch.tintri.com/project?project=ironic&time=24+hours09:30
yolandait's my patch yep...09:31
*** dtantsur|afk is now known as dtantsur09:35
dtantsurmorning ironic09:35
etingofdtantsur, good cool Monday morning o/09:36
dtantsuretingof: oh, already cool at your place? it's keeping boiling here :)09:36
dtantsuror was it sarcasm?09:36
etingofdtantsur, most certainly, sarcasm ;)09:37
etingofaren't we on ironic channel?09:37
dtantsuretingof: ah, that's bad :) going to be +35 tomorrow >_<09:37
etingofthat's tough to tolerate09:38
dtantsurright, yeah. I cannot promise to be able to work...09:38
etingofit's 32 down here09:39
dtantsuryeah, the same today09:39
etingofand local water reserve is contaminated09:39
dtantsurOUCH. how come?09:40
etingofcyanobacteria strikes again09:40
dtantsurno way :(09:41
etingofyeah, that happens at times esp when it's too hot for long09:41
dtantsurright, yeah. we mostly use bottled or boiled tap water anyway though.09:41
etingofwell, you can't swim because the water gets toxic09:42
etingofeven vapors are toxic (theoretically)09:43
etingoftap water should just end once the bacteria colonies clog the filtration system09:44
etingofso we are safe from that prospect \o/09:45
dtantsurthe human civilization is quite fragile, isn't it?09:45
etingofyes, and it's our job to add more risks to it (by coding)09:46
dtantsur\o/09:46
*** AlexeyAbashkin has quit IRC09:53
openstackgerritMerged openstack/bifrost master: Add openstacksdk to required-projects  https://review.openstack.org/58656209:58
openstackgerritDao Cong Tien proposed openstack/ironic master: Node gets stuck in ING state when conductor goes down  https://review.openstack.org/58699310:08
etingofyolanda, so I read the conversation wrt automated clean patch... may understanding is that TheJulia proposes to split up this patch onto three: new node field, client API version bump, API support of the new field10:15
etingofwith client API bump patch dependent on your API patch10:16
etingofbut may be I misinterpreted the discussion ;)10:16
yolandaetingof, then somehow testa fail again. I remember zshi having to submit a temporary patch when adding the object, otherwise rest api was failing10:25
openstackgerritchandra shekar proposed openstack/ironic-specs master: Added new spec for L3 based Ironic deployment  https://review.openstack.org/54393610:25
*** zzzeek has quit IRC10:49
openstackgerritchandra shekar proposed openstack/ironic-specs master: Added new spec for L3 based Ironic deployment  https://review.openstack.org/54393610:51
*** zzzeek has joined #openstack-ironic10:53
*** phuongnh has quit IRC10:54
*** rh-jelabarre has joined #openstack-ironic10:56
openstackgerritIlya Etingof proposed openstack/sushy-tools master: Clean up unit tests  https://review.openstack.org/58602910:59
openstackgerritDerek Higgins proposed openstack/virtualbmc master: Specifiy encoding for xml string  https://review.openstack.org/58700011:00
openstackgerritAija Jaunteva proposed openstack/sushy master: Add Redfish Message Registry resource  https://review.openstack.org/58625911:04
openstackgerritDerek Higgins proposed openstack/ironic master: Switch ironic-tempest-dsvm-ipa-partition-pxe_ipmitool-tinyipa-python3  https://review.openstack.org/58355511:04
*** AlexeyAbashkin has joined #openstack-ironic11:06
openstackgerritIlya Etingof proposed openstack/sushy-tools master: Fix nova unit tests  https://review.openstack.org/58649611:21
*** mbeierl has joined #openstack-ironic11:59
*** tiendc has quit IRC12:06
TheJuliaGood morning everyone12:08
openstackgerritMerged openstack/networking-generic-switch master: Adds ngs_switchport_mode config option to Dell PowerConnect driver  https://review.openstack.org/58163112:08
openstackgerritIlya Etingof proposed openstack/sushy-tools master: Unify BIOS unit tests with others  https://review.openstack.org/58703512:09
*** MattMan has quit IRC12:09
*** MattMan has joined #openstack-ironic12:10
etingofgood morning TheJulia o/12:11
dtantsurmorning TheJulia12:15
*** gkadam has quit IRC12:19
openstackgerritDmitry Tantsur proposed openstack/ironic-inspector master: [WIP] Remove deprecate authentication options  https://review.openstack.org/58704112:26
* TheJulia types and types and types12:28
dtantsura great day to type! (kidding)12:33
*** jcoufal has joined #openstack-ironic12:34
TheJuliaheh12:35
*** mjturek has joined #openstack-ironic12:42
etingofthat's what mother nature intended us (coders) for - to type ascii text12:42
*** jaypipes has quit IRC12:43
*** jaypipes has joined #openstack-ironic12:43
jrollmorning y'all12:44
* jroll declares scrollback bankruptcy12:44
*** links has quit IRC12:44
dtantsurmorning jroll12:47
*** mjturek has quit IRC12:51
TheJuliaGood morning jroll12:53
*** rloo has joined #openstack-ironic12:54
*** links has joined #openstack-ironic12:56
*** markguz_ has joined #openstack-ironic13:05
*** bfournie has quit IRC13:09
*** jroll has quit IRC13:10
*** markguz_ has quit IRC13:10
*** jroll has joined #openstack-ironic13:10
*** bfournie has joined #openstack-ironic13:11
*** bnemec has joined #openstack-ironic13:20
*** arnewiebalck__ has joined #openstack-ironic13:21
*** arnewiebalck__ has quit IRC13:22
*** alexpilotti has joined #openstack-ironic13:27
*** r-daneel has quit IRC13:28
*** rpioso|afk is now known as rpioso13:29
rpiosoGood morning, ironicers13:29
*** arnewiebalck__ has joined #openstack-ironic13:31
*** Goneri has joined #openstack-ironic13:38
*** markguz is now known as markguz_13:40
*** AlexeyAbashkin has quit IRC13:40
*** AlexeyAbashkin has joined #openstack-ironic13:41
*** mjturek has joined #openstack-ironic13:42
mjturekgm ironic!13:42
etingofo/ mjturek rpioso13:44
*** lbragstad has joined #openstack-ironic13:46
rpiosoetingof, mjturek: \o13:47
TheJuliaderekh: I think we're in good shape to begin landing the CI changes, because largely I think we're going to be landing documentation. https://review.openstack.org/#/c/583185/13:50
patchbotpatch 583185 - ironic - Switch ironic-tempest-dsvm-pxe_ipmitool-postgres13:50
TheJuliagood morning rpioso mjturek13:51
rpiosoTheJulia: :)13:52
derekhTheJulia: cool, I'll remove the WIP, also I took a deeper look at the python3 problem this morning, turns out it was a problem with vbmc and python3 https://review.openstack.org/#/c/587000/13:53
patchbotpatch 587000 - virtualbmc - Specifiy encoding for xml string13:53
* derekh will fix pep8 now13:53
TheJuliaderekh: oh awesome!13:55
TheJulia\o/13:55
openstackgerritDerek Higgins proposed openstack/virtualbmc master: Specifiy encoding for xml string  https://review.openstack.org/58700013:56
openstackgerritAija Jaunteva proposed openstack/sushy master: Add Message Registry File resource  https://review.openstack.org/58706813:58
*** baha has joined #openstack-ironic14:01
*** hongbin has joined #openstack-ironic14:14
*** rbartal has quit IRC14:20
rlooHappy Monday morning ironickers, TheJulia, derekh, rpioso, mjturek!14:23
rpiosorloo: Hey!14:23
dtantsurmorning rloo14:23
rloohi dtantsur!14:24
TheJuliaGood morning rloo!14:24
* TheJulia updates https://etherpad.openstack.org/p/IronicWhiteBoard14:26
*** links has quit IRC14:27
*** markguz has joined #openstack-ironic14:29
dtantsurTheJulia: I'm going to cool down before the meeting. If I'm not back in time, please record my -0 to FFEs touching API/RPC and +1 to the others.14:35
TheJuliadtantsur: ack14:35
*** ChanServ 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"14:36
*** dtantsur is now known as dtantsur|brb14:38
*** markguz has quit IRC14:40
*** hshiina has joined #openstack-ironic14:45
*** cdearborn has joined #openstack-ironic14:46
*** jiapei has joined #openstack-ironic14:49
*** stendulker has joined #openstack-ironic14:50
jiapeiGood morning Ironicers14:51
TheJuliagood morning jiapei14:56
TheJuliaWow, it is almost meeting time14:56
TheJuliaThis day is flying by14:56
*** kaifeng has joined #openstack-ironic14:57
openstackgerritJulia Kreger proposed openstack/ironic master: Change PXE logic to always link macs with UEFI  https://review.openstack.org/57895914:57
openstackgerritWill Miller proposed openstack/ironic-inspector master: Allow nested action value formatting  https://review.openstack.org/58577915:00
TheJulia#startmeeting ironic15:00
openstackMeeting started Mon Jul 30 15:00:08 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
TheJuliao/15:00
openstackThe meeting name has been set to 'ironic'15:00
mjtureko/15:00
kaifengo/15:00
bdoddo/15:00
rpioso\o15:00
etingofo/15:00
hshiinao/15:00
rlooo/15:00
stendulkero/15:00
jroll\o15:00
TheJuliaOur agenda this week is on the wiki. We have a few discussion topics this week, but hopefully it should go quickly.15:01
TheJulia#link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting15:01
TheJulia#topic Announcements/Reminders15:01
*** openstack changes topic to "Announcements/Reminders (Meeting topic: ironic)"15:01
TheJuliaThis week is R-4, which means we're closing in on release quite quickly.15:02
rajiniro/15:02
TheJulia#info python-ironicclient and python-ironic-inspector-client were released last week.15:02
TheJulia#info Reminder: Please add topics and update if you will be present on the Stein PTG planning etherpad.15:03
TheJulia#link https://etherpad.openstack.org/p/ironic-stein-ptg15:03
TheJulia#info Next week is R-3, or Rocky RC1 release. We should expect to release ironic 11.1 next week as a result.15:04
TheJuliaAlso worth noting, PTL nominations are underway and close tomorrow evening near midnight UTC.15:05
TheJuliaDoes anyone have anything to announce or remind us of?15:05
TheJuliaI guess not, we can move on then.15:06
*** MrBerns has joined #openstack-ironic15:07
TheJuliaLooks like we had no action items last week, so we can skip that15:07
*** MrBerns has quit IRC15:08
TheJulia#topic Review subteam status reports15:08
*** openstack changes topic to "Review subteam status reports (Meeting topic: ironic)"15:08
TheJulia#link https://etherpad.openstack.org/p/IronicWhiteBoard15:08
TheJuliaStarting at line 16315:08
rloowrt the Bugs, can we delete the stuff about moving to storyboard, and whether anythign needs to be addressed?15:09
rlooL169 & 17115:09
TheJuliaI don't see why not15:10
rloodone :)15:10
TheJuliaLooks like there is some discussion in the neutron event spec15:11
etingofmay be line 37 needs to be deleted as well15:11
TheJuliaBut, that really doesn't need to be focused on at the moment since we're not going to be able to move it forward until Stein15:11
rlooI updated the BIOS status (L186)15:12
TheJuliarloo: awesome15:12
*** MrBerns has joined #openstack-ironic15:13
rpiosoThe idrac vendor priority is up-to-date.15:13
TheJuliaI saw the notes, looks like a new CI job was added for that, \o/15:13
TheJuliaetingof: Okay, consider it done15:14
rloowrt classic driver removal: is the only thing left, api-ref examples?15:14
rlooL243ish15:14
rpiosoTheJulia: That's correct, thanks to rajinir15:14
TheJuliarloo: I believe so... we'll have to confirm with dtantsur|brb15:15
rloothx derekh for doing the zuul v3 playbook refactoring!15:15
TheJulia++15:15
TheJuliaI think we're good to move on to review priorities for the week. Which I did some cleanup of earlier but didn't remove all of the merged items.15:15
derekhrloo: no problem, still more to do, will start the next batch ASAP15:16
*** pcaruana has quit IRC15:16
jrollwhoa, ramdisk deploy driver landed, nice work15:16
TheJuliaEveryone good to move on?15:16
rlooderekh: :)15:16
TheJuliajroll: yeah, forgot to dance over the weekend :)15:17
rlooawesomeness!15:17
TheJuliaAnyway, lets move on to priorites if there are no objections15:17
*** arnewiebalck__ has quit IRC15:17
rloooh, nice, the nova bug fixes landed too15:17
TheJulia#topic Deciding on priorities for the coming week15:18
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"15:18
rloonothing to do I think :)15:18
TheJulia#link https://etherpad.openstack.org/p/IronicWhiteBoard15:18
TheJuliaLine 18415:18
TheJuliaer,r line 10315:18
rloo? line 100?15:18
TheJuliaYeah, 100 is the header15:20
TheJuliaAnyway, I just deleted things that merged from the list15:20
TheJuliaLots of stuff merged last week \o/15:20
TheJuliaThis week looks to largely be documentation and bug fix related since we're essentially feature frozen. I have a few FFE discussion topics up next though :)15:21
TheJuliaEveryone good with the list or is anyone aware of anything else that we should add for this next week?15:21
jrollyeah, list looks good to me15:21
jrollI'll add conductor group docs when they're up15:21
TheJuliajroll: thanks15:21
*** tssurya has quit IRC15:22
rloo++ good15:22
TheJuliaOkay, discussion time!15:22
w-millerhi all, i posted a story this morning for a feature i was looking at working on, regarding adding introspection rules for ironic ports (https://storyboard.openstack.org/#!/story/2003149). i’m not really au fait with the RFE workflow so apologies if this is the wrong time to bring it up, but if anyone had any feedback on the story it would be much appreciated :)15:22
TheJuliaw-miller: great timing!15:23
TheJulia#topic Discussion15:23
*** openstack changes topic to "Discussion (Meeting topic: ironic)"15:23
*** r-daneel has joined #openstack-ironic15:23
TheJuliaI have three items that we might wish to grant a FFE to on the agenda, The item w-miller brought up happens to be one of them15:23
TheJuliaThe change looks very minor, which is why I included it as a possibility15:24
TheJuliaerrr15:24
TheJuliawait a second15:24
w-millerah yeah, i think that’s the change i made last week - but the story is a new one for a different feature15:24
TheJuliaI was speaking regarding https://storyboard.openstack.org/#!/story/167076815:24
rloothat only affects ironic-inspector?15:24
jrollyeah I don't see it on the list :)15:24
* TheJulia got confused15:25
jrollI think w-miller is only asking for an RFE review15:25
TheJuliasorry :(15:25
TheJuliaYeah, he is sekeing an RFE review for 200314915:25
TheJuliaSeeking15:25
*** gyee has joined #openstack-ironic15:25
w-millerYeah :)15:25
jrollok, let's loop back to that15:26
TheJuliaI'm wondering if we should allow https://storyboard.openstack.org/#!/story/1670768 to be granted a FFE https://review.openstack.org/#/c/58577915:26
patchbotpatch 585779 - ironic-inspector - Allow nested action value formatting15:26
openstackgerritMerged openstack/networking-generic-switch master: add alias for hpe_comware  https://review.openstack.org/58668115:26
TheJuliawow15:26
TheJuliaokay, wrong link15:26
* TheJulia needs more coffee... or something15:26
TheJuliahttps://review.openstack.org/#/c/585779/15:26
patchbotpatch 585779 - ironic-inspector - Allow nested action value formatting15:26
TheJuliaI have no objections, dtantsur|brb indicated he was +1 to it based on his prior statement15:27
TheJuliaAny objections to granting a FFE?15:27
jrollI'm not sure about how I feel about FFEs where the patch was initially proposed... a day before (?) feature freeze?15:28
rloothere are two things: rfe needs to be approved, and code needs to be approved15:28
rloothe code change itself doesn't look difficult15:29
rloohow useful is this?15:29
rlooHaving asked those questions, I'm good with FFE if we have two cores that are willing to shepherd it along15:29
jrollthis one seems minimal, so I'm not totally against it, but proposed a day before is the epitome of rushing things :) so I'm -0 I guess15:29
jrollbasically what rloo said15:30
TheJuliaIt seems like it could be very useful for more complex rules. I'm good with shepherding it15:30
rlooyes, it is rushing things. note that the rfe was started in march.15:30
TheJuliaanyone else?15:30
openstackgerritMerged openstack/networking-generic-switch stable/queens: Set neutron branch name in tox_install.sh  https://review.openstack.org/58661115:30
w-millerwithout the change, a couple of extra ‘boilerplate’ rules are required for the same behaviour - that’s the main point i think15:31
TheJuliamarch 201715:31
rlooeven better (or worse)15:31
TheJuliaAnyway, dtantsur|brb indicated he was +1, so I say we just kind of let things progress there and see what happens.15:31
rlooi think for ffe, we need two cores to step up15:32
TheJuliaWell, dtantsur|brb is also away, so by that we're basically blocked on that15:32
rlooyou mean, dtantsur|brb coudl be one of the cores?15:32
TheJuliarloo: yes15:32
rloowho is the other core?15:32
TheJuliarloo: I volunteered earlier15:33
rloooh, i missed that.15:33
TheJuliaOh, okay15:33
rlooOK, so how about FFE oked if we get a second (hopefully dtantsur|brb) core.15:33
*** tssurya has joined #openstack-ironic15:33
rlooare we at least good with approving rfe? i guess the two cores can approve that too.15:33
TheJuliarloo: works for me.15:33
rlooGood. next... ? :)15:34
TheJuliaNext: The automated_clean feature setting on nodes that yolanda has been working on.15:34
TheJuliaThis involves changes all the way to the API. dtantsur|brb is -0 based upon the fact that it does involve an API change, we can merge it and just not merge client code since that has already been released15:35
jrollyeah, I have the same issues with rushing on this one, it was also first proposed july 2515:35
rloois there a link?15:35
TheJuliaI'm kind of -0 as well, I feel that we are rushing15:35
jrolland also has api changes which are irreversible15:35
jrollrloo: https://review.openstack.org/#/c/585795/15:35
patchbotpatch 585795 - ironic - Add automated_clean field15:35
TheJuliarloo: Three patches linked on the agenda.15:35
TheJuliahttps://review.openstack.org/58650815:36
patchbotpatch 586508 - python-ironicclient - Add management of automated_clean field15:36
rloothx. but also good to put it in the minutes, since the agenda will change.15:36
jrollI'm -2 tbh, I don't want to rush an API change15:36
TheJuliathat one can't land15:36
jroll#link https://review.openstack.org/#/c/585795/15:36
patchbotpatch 585795 - ironic - Add automated_clean field15:36
jrollthere15:36
jroll:)15:36
TheJuliaand https://review.openstack.org/#/c/585991/15:37
patchbotpatch 585991 - ironic - Add automated_clean field to the node object and API15:37
TheJuliaI really feel that we need to wait until Stein15:37
*** dtantsur|brb is now known as dtantsur15:37
jrollthe RFE also has no info whatsoever15:37
* dtantsur is back15:37
rlooIt has a client change, it might be useful w/o it, but I don't think it is worth rushing to get this in. is there a serious need for this now?15:38
TheJuliajroll: yeah, tripleo context is needed there since there is the resistance to have cleaning by default, but ceph requires it.15:38
dtantsurI'll look into the introspection rules RFE if needed15:38
* TheJulia adds that context real quick15:39
jrollTheJulia: well, I mean implementation things15:39
rloodtantsur: and review the code for that?15:39
jrollwhat's the API? etc15:39
dtantsurrloo: yes15:39
jrollhow is it used?15:39
rloodtantsur: thx, so FFE granted for that one!15:39
dtantsuras to the API addition, I think it's very useful, but I'm quiet against API changes after FF15:39
jrollthis RFE has zero info that is useful to decide whether it's a good feature to accept15:39
dtantsur* quite15:39
rlooif you're running tripleO for real, it seems dangerous to NOT clean.15:41
TheJuliaI think it is necessary, if the context of deployments with automated_clean being disbaled is taken into account.15:41
rloois this just for testing purpoess?15:41
dtantsurrloo: no, tripleo undercloud has cleaning off by default :(15:41
TheJuliaBut I think we can just wait until Stein since it involves a client change as well.15:41
dtantsurand fwiw it will be mostly useless for tripleo without client changes, either ironicclient or tripleoclient15:42
rloolet's wait then. but it would be good to update to provide more info as to why it is useful15:42
jrollyeah, we need more than a single sentence for an api change :)15:42
rloo(I mean, the rfe has to be approved first, and jroll has asked...)15:42
dtantsurI think a real use case is something like diskless nodes15:42
dtantsurand the new ramdisk deploy15:42
jrollI would especially like to discuss somewhere how safe the None/true/false thing is15:43
dtantsurwhere you simply don't need cleaning for this particular node (but may need for regular ones)15:43
TheJuliadtantsur: that is a good point, might not want it if your just spinning ramdisks around... or you may explicitly need it on some nodes15:43
rloowe used to say that a spec was needed if there was an API change.15:43
rlooI'm fine relaxing that, as long as the story has more info15:43
TheJuliarloo: I think it evolved last week, but yeah15:43
rloook, i think we've discussed this enough now :)15:43
TheJuliaAgreed!15:44
TheJuliaNext!15:44
TheJuliakaifeng proposed a patch to add the ability to save introspection results to the database, https://review.openstack.org/#/c/583930/ which seems very useful as presently the only option is swift.15:45
patchbotpatch 583930 - ironic-inspector - Supports database as an introspection data storage15:45
TheJuliaWe've kind of talked about this some in the past, and I'm +1 to the idea15:46
rloough. rfe hasn't been approved yet.15:46
rlooall of a sudden, the inspector has the spotlight...15:46
sambettsI believe we did that at some point in the past, and we remove that because it blew out the DB15:46
dtantsurit looks straightforward and benefits the standalone case *a lot*15:46
dtantsursambetts: no, it was storing huge JSONs in node.extra :)15:47
dtantsurIIRC15:47
sambettsI thought we had stored the inspection results in inspectors DB too, pre-dmidecode15:47
sambettsthen we added that and it made it HHUUUGE15:47
dtantsurI don't think so? but maybe my memory lets me down15:47
dtantsuranyway, as long as it's a separate table, it should not be a big hit15:48
TheJuliaIf we did, we should check and hold off15:48
rloowhere's the spec? details on how to decide whether to store in inspector db or in swift?15:48
jrollthat's a pretty large change, it seems to me15:48
jrolland basic pieces like this make me skeptical that it's anywhere near ready https://review.openstack.org/#/c/514552/21/ironic_inspector/conf/processing.py15:48
patchbotpatch 514552 - ironic-inspector - Supports database as introspection data storage: p...15:48
TheJuliarloo: essentially the storage feature is completely useless without swift, and there are deployments that just don't want swift...15:49
*** tssurya has quit IRC15:49
jrolloh lord it's making all the storage stuff fully pluggable15:49
* TheJulia takes that as a -1 from jroll15:49
sambettsI thought we had saving to disk in there somewhere (we might have removed that too)15:49
rlooTheJulia: right, but saying 'store it in inspector's database', doesn't give much detail. is it a new table? what field? what is the size of the field?15:49
*** tesseract has quit IRC15:49
dtantsurto be fair, I think it was me asking about pluggability15:49
jrolland again this RFE is one sentence.15:49
rlooi don't think the rfe is ready to be approved.15:49
rlooso no FFE for this. unless two cores feel strongly for it.15:50
jrollI don't usually review inspector things (sorry), but if I did I would be -1 on an FFE here15:50
sambettswe should definatly ask the question about the size of the data too, the json returned by IPA is massive with the dmi data hence we use swift, its fine in a small deployment, but any good sized ironic deployment with inspector :/15:50
TheJuliaI think that is fair15:50
TheJuliaOkay, moving on!15:50
TheJuliaand 10 minutes reamining15:51
TheJuliaerr, 915:51
rloow-miller had that question earlier on15:51
TheJulia#topic RFE Review15:51
*** openstack changes topic to "RFE Review (Meeting topic: ironic)"15:51
TheJuliaw-miller has brought forth https://storyboard.openstack.org/#!/story/200314915:51
w-millerapologies for the mistiming15:51
TheJuliato allow conditionals in inspection rules on ports15:52
TheJuliaw-miller: no worries :)15:52
sambettsnow that is a nice RFE15:52
dtantsurhonestly, we should rewrite introspection rules in some less awkward DSL15:53
TheJuliaI like it15:53
TheJuliathe RFE that is15:54
sambettsit would be cool if it just worked with the jq like json accessing logic, so we could write conditions for any data in the returned inspection data15:54
w-millerthe RFE would also be to allow for port actions as well as conditionals - setting/extending an attribute, for example, is also applicable to a port15:54
dtantsurI'm -0 on any big additions to what we have now. I'll be +2 and helping with any effort to make it more universal.15:54
TheJulia+1 re rewriting, but that is out of scope discussion wise at the moment15:54
dtantsurwell, for me it's in scope15:54
TheJuliaI don't think we can take it on, and we would have to support the old syntax and migrate15:55
TheJulias/and/and or/15:55
dtantsuras someone who is responsible for this horror :)15:55
w-millermgoddard had rewriting of conditional logic to use Jinja2 as a possible feature for me to look at in future but i think that’s a bridge to be crossed if/when it comes to it15:55
dtantsurwell, the old syntax is quite rigid, it's not hard to convert from it (yet)15:55
TheJuliadtantsur: you know inspecctor the best, which do you feel brings more value to a user?15:56
dtantsurI'm afraid the approach we take only fixed some cases. i.e. what to do when you want to update port AND node?15:57
TheJuliaTwo minute warning15:58
TheJuliadtantsur: So do you think changing to a less awkward syntax would be better than the RFE for users in the short term?15:58
w-millerdtantsur: you mean for the same conditional/within the same rule?15:59
dtantsurw-miller: yes; TheJulia: yes.15:59
dtantsurw-miller: I'm ready to discuss after the meeting15:59
w-millerokay great, thanks15:59
TheJuliaSounds good15:59
TheJuliaWell, if there is nothing else for anyone to bring up, we can call the meeting done.16:00
rpiosoI would very much appreciate reviews of https://review.openstack.org/#/c/57967316:00
patchbotpatch 579673 - python-dracclient - Filter out non-ASCII characters on invalid UTF816:00
rpiosoOops, wrong change.16:00
rpiosohttps://review.openstack.org/#/c/545184/16:00
patchbotpatch 545184 - ironic - Fix iDRAC hardware type does not work with UEFI16:00
dtantsurrpioso: will look16:01
rpiosodtantsur: ty16:01
TheJuliaThanks everyone!16:01
TheJulia#endmeeting16:01
*** 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"16:01
openstackMeeting ended Mon Jul 30 16:01:35 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-07-30-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-07-30-15.00.txt16:01
jrollthanks \o16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-07-30-15.00.log.html16:01
* jroll finds lunch16:01
dtantsurw-miller: what prevent us just fixing set-attribute right now as a quick workaround?16:01
dtantsurthe "resource" solution feels wrong since not all actions can operator on a port16:02
dtantsure.g. set-capabilities makes no sense for ports16:02
w-millerdtantsur: what do you mean by “fix”? unless you mean creating something like set-port-attribute as a separate action?16:03
dtantsurw-miller: not necessary, but I see a problem with port-scope conditions in this case..16:03
* dtantsur thinks more16:03
w-milleri suppose you would have to disallow node-scope actions in a rule with port-scope conditions16:04
w-millerif you chose to go that way16:05
*** hshiina has quit IRC16:05
sambettswhich I don't think we want to do16:05
*** kaifeng has quit IRC16:05
dtantsurw-miller: do you have a draft patch for your proposal? because I suspect it may be quite a big change in reality16:06
dtantsurI'd like to see the proposed change to the rules action interface. currently we accept node_info.16:06
dtantsurI guess I'd prefer this to have a spec, but at least makes ^^^ detailed in the RFE16:07
w-millerdtantsur: i’ve been working on it but don’t yet have a draft patch ready. you’re right that even so far it’s a bigger change than i’d anticipated16:07
*** mbeierl has quit IRC16:07
dtantsuryep16:07
dtantsurw-miller: anyway, please update the RFE with the changes to the Action interface you anticipate16:08
dtantsur(well, and Condition too - if any)16:08
sambettsI think this is why we need to have a more flexible rules DSL (for want of a better example kinda of "ansible"y) so we could do things like with_items: {{ introspection_data.ports }}; when: {{ item.switch_info }} == sw1; set-port-attribute: port: {{item.uuid}} value: pn1;16:08
w-millerdtantsur: i can do that16:09
dtantsursambetts: yeah, I also have ansible on my mind. or mistral which is quite similar.16:09
dtantsurthanks w-miller16:09
w-millersambetts: i actually originally drafted the concept in pseudo-ansible when thinking through the idea, so i agree haha16:10
sambetts\o/16:10
sambettsso we build the ansible engine into inspector right?16:10
dtantsursimple! problem solved?16:10
sambettstbh it could be interesting to have inspector generate an inventory file with the inspection data injects as a var, then we just output the inspector rules data into a temp dir and call ansible-playbook -i <generated inventory file> /tmp/inspector-rule-<hash>16:13
sambettsand the actions like set-atribute could be ansible lib extentions16:13
*** Guest9714 is now known as melwitt16:15
sambetts(can you tell I'm neck deep in ansible transitioning our CI to zuul v3...)16:16
*** mjura has quit IRC16:18
w-millerthat’s an interesting idea sambetts - what would the inventory file look like? presumably the introspection actions would only need to be run from one host with openstack API access?16:22
dtantsursambetts: heh :)16:23
sambettsI was thinking something like http://paste.openstack.org/show/726856/16:23
*** jesusaur has quit IRC16:24
dtantsurlet's just rewrite ironic-inspector in ansible :) we can leave the discovery part in place, everything else is just calling ansible16:24
w-millersambetts: right, makes sense.16:25
*** stendulker has quit IRC16:25
*** ajya has quit IRC16:26
sambettsthen the rule you proposed in the RFE might look something like: http://paste.openstack.org/show/726858/16:30
*** AlexeyAbashkin has quit IRC16:30
*** e0ne has quit IRC16:31
sambettsand the playbook we generate might look something like: http://paste.openstack.org/show/726859/16:32
*** priteau has joined #openstack-ironic16:33
sambettswhere /tmp/inspector-rule-<uuid> is the file output by inspector using the inspector rule data in the DB16:34
*** prasen has joined #openstack-ironic16:35
w-millersambetts: that looks good - similar to what i was imagining. is this something we’d actually like an RFE for?16:39
w-miller…or a spec16:39
dtantsur30C in my room \o/ kmp16:39
sambettsdtantsur: what do you think? its an interesting idea is it something we want to play with? it would significantly simplfy the rules logic carried by inspector I think, we might need to inject some rules for ansible play to lock some of the ansible side of it down too16:41
openstackgerritMerged openstack/networking-baremetal master: Update neutron-lib requirement for rocky  https://review.openstack.org/58551016:42
dtantsursambetts: it's curious, I'd like to see a PoC for it16:42
sambettsI agree16:42
dtantsurotherwise the only answer to "what do you think" in this weather is "I do not" :)16:42
sambettsdtantsur: haha I agree with that too16:43
w-milleri can have a chat with mark on wednesday about it - i’d be up for working on a PoC16:44
sambettsw-miller: I would say at least an RFE to keep track of this conversation and the fact the idea exists16:44
* w-miller feeling grateful for an air-conditioned office16:44
sambettsand a PoC would be awesome16:44
*** priteau has quit IRC16:44
w-millerno probs, i’ll get it noted down16:45
*** w-miller has left #openstack-ironic16:59
*** derekh has quit IRC17:01
*** priteau has joined #openstack-ironic17:02
*** sambetts is now known as sambetts|afk17:08
sambetts|afknight all17:08
TheJuliaSo pondering for soon(): how would people feel if we had some sort of more formalized mentoring ?17:08
TheJuliasambetts|afk: goodnight17:08
*** serlex has quit IRC17:10
*** MrBerns has quit IRC17:11
*** dougsz has quit IRC17:11
rpiososambetts|afk: Good evening17:19
openstackgerritJulia Kreger proposed openstack/ironic master: Prepare for Rocky release  https://review.openstack.org/58634217:32
mjturekTheJulia: should I apply for FFE on https://storyboard.openstack.org/#!/story/1749057 ?17:38
TheJuliamjturek: yeah, I guess17:39
mjturekwill do17:40
*** e0ne has joined #openstack-ironic17:43
*** jaganathan has quit IRC17:50
*** jiapei has quit IRC18:09
dtantsurTheJulia: overall positive, depending on what exactly you mean18:13
rpiosodtantsur, TheJulia: I'm wondering why there's an aversion to asserts in the production code? Like https://mail.python.org/pipermail/python-list/2013-November/660568.html , I feel they're reasonable to use as a form of defensive programming and for Design by Contract.18:14
dtantsurrpioso: because they work differently for optimized and non-optimized builds18:14
dtantsurspecifically, byte-compiling with -O will remove them without traces18:14
rpiosodtantsur: Well understood. In the situations I'm referring to, the asserts are being used by internal functions to belt and suspender verify input arguments that were already scrubbed by their callers.18:17
rpiosoIt's defensive and Design by Contract.18:17
dtantsurrpioso: right, but you don't want these removed in actual production.18:18
rpiosoIt wouldn't matter, since they've already been checked.18:18
rpiosoThe outer checks cannot be compiled away.18:19
dtantsurrpioso: yeah, but you start returning None instead of raising18:19
rpiosoThey're useful during development and unit test, and as a form of documentation.18:19
dtantsurI think it's much more useful to raise an exception in all cases18:20
rpiosoI've changed it to not do that.18:20
rpiosoFrom that article:18:20
rpiosohttps://www.irccloud.com/pastebin/wvzZPFmz/18:21
rpiosoAgain, this is a secondary, internal check.18:21
rpiosoOr checks :-)18:22
TheJuliaSo is there then no reason to raise an exception?18:22
rpiosoNot in those internal functions.18:22
rpiosoThey're raised by the callers.18:22
TheJuliaThen why have a secondary check if we're not going to raise an exception?18:23
rpiosoBecause changes and bugs happen :)18:23
rpiosoThey should be caught during unit test against actual h/w.18:23
TheJuliaTrue, but should we not still raise an exception if something is very wrong is found?18:23
TheJuliaThe caller can still raise then if the input or self validation is wrong, the original caller could then just have the try/except block to catch the same exception18:24
rpiosoWe do, e.g., https://review.openstack.org/#/c/545184/8/ironic/drivers/modules/drac/management.py@23118:26
patchbotpatch 545184 - ironic - Fix iDRAC hardware type does not work with UEFI18:26
rpiosoThat's the caller.18:26
rpiosoThe article proceeds,18:27
rpiosohttps://www.irccloud.com/pastebin/vvpp1hm1/18:27
TheJuliaPython's model is not defensive though, it is to ask for forgiveness18:28
rpiosoThe article is from python.org :)18:28
TheJulia"oh, sorry, that didn't work, lets try this!"18:28
dtantsurwell, asserts are NOT defensive programming18:29
TheJuliaor "Oh, something is really wrong, lets raise the exception because something is really wrong and we should all stop eveyrthing"18:29
dtantsurnor is anything that is stripped from production builds18:29
TheJuliaYeah, then we never actually do anything error handling wise18:30
* dtantsur waves18:31
*** dtantsur is now known as dtantsur|afk18:31
rpiosoThis is an internal function. The caller already checks the input.18:31
rpiosodtantsur|afk: Good nite18:31
dtantsur|afko/18:31
openstackgerritMerged openstack/ironic master: Switch ironic-tempest-dsvm-pxe_ipmitool-postgres  https://review.openstack.org/58318518:32
TheJuliarpioso: so then there is no actual reason to have the assert then?18:32
rpiosoTheJulia: There is. The article captures this well.18:33
rpiosohttps://www.irccloud.com/pastebin/bcvmmzT1/18:34
rpiosoAnd18:34
rpiosohttps://www.irccloud.com/pastebin/y6eU9CDx/18:34
*** prasen has quit IRC18:37
openstackgerritAleksandra Bezborodova proposed openstack/sushy master: Add a virtual media resource  https://review.openstack.org/57081018:41
openstackgerritMerged openstack/ironic master: Switch ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa  https://review.openstack.org/58333718:46
TheJuliaI guess what I'm confused by is that your insisting that it should be present because it should never be hit... because it is checked before it is called. I feel like we should legitimately be raising the exception the orignal caller's parent is expecting to indicate a failure has occurred... that is if we're that sure it sure it should present. What I'd prefer to avoid is us getting in a practice in relying upon18:48
TheJuliaassertion in the code because of the pitfalls.18:48
openstackgerritMerged openstack/ironic master: Switch ironic-tempest-dsvm-ipa-wholedisk-bios-pxe_snmp-tinyipa  https://review.openstack.org/58354618:55
openstackgerritMerged openstack/ironic master: Switch ironic-tempest-dsvm-ipa-partition-uefi-pxe_ipmitool-tinyipa  https://review.openstack.org/58355118:55
rpiosoTheJulia: "What I'd prefer to avoid is us getting in a practice in relying upon assertion in the code because of the pitfalls." +118:56
rpiosoTheJulia: The use cases in question don't rely upon them.18:57
rpiosoTheJulia: Belts and suspenders :-)18:57
TheJuliaheh18:57
TheJuliathat is a really good analogy18:57
rpiosoTheJulia: During development and unit testing against real h/w, when they're not compiled away, asserts can quickly find gotchas due to unforeseen changes that need to be accounted for.18:58
rpiosos/Belts/Belt/18:59
TheJuliawell there is a slight problem to that18:59
rpiosoOnly one belt is needed ;-)18:59
TheJuliaIn that many deployments run the interpretted code instead of pure compiled18:59
TheJuliaOf course, we also had to turn off the object compile caching for a CI job at one point if memory serves19:00
TheJuliaof course, that also really doesn't matter much19:00
TheJuliaWell, it is official, I've started a post-Rocky patch list19:03
rpiosoTheJulia: Also, I prefer that such internal functions not raise an exception that should have already been raised by the caller. What exception should be raised? What should its message be? Now the caller has to catch and wrap it in the desired exception. After all, the caller knows the context.19:05
*** baha_ has joined #openstack-ironic19:07
TheJuliaWell, the immediate caller doesn't have to catch it. The caller's caller can just read the same exception, it would just depend on what makes sense in each case.19:07
*** baha has quit IRC19:09
*** baha_ is now known as baha19:10
openstackgerritJulia Kreger proposed openstack/ironic master: Ramdisk deploy driver doc  https://review.openstack.org/58548619:40
openstackgerritJulia Kreger proposed openstack/ironic master: Follow-up patch to ramdisk interface  https://review.openstack.org/58632719:48
openstackgerritJulia Kreger proposed openstack/ironic master: Rework ironic landing page new docs standard  https://review.openstack.org/58662719:59
openstackgerritJulia Kreger proposed openstack/ironic master: Add admin-only provisioner reference arch  https://review.openstack.org/58661820:16
*** EranBD has joined #openstack-ironic20:21
*** rpioso is now known as rpioso|afk20:38
*** cdearborn has quit IRC20:40
openstackgerritJulia Kreger proposed openstack/ironic master: ipxe boot interface - begin the process  https://review.openstack.org/58340720:49
*** hamzy_ is now known as hamzy20:59
openstackgerritMerged openstack/networking-generic-switch master: Follow up for Juniper Junos OS device support  https://review.openstack.org/58649021:01
*** r-daneel has quit IRC21:03
eanderssonWhen running Ironic with Mitaka, is only flat networks supported? Or is it more like in a experimental state in Mitaka?21:11
*** r-daneel has joined #openstack-ironic21:11
eanderssonAlso, in general how mature was Ironic in Mitaka?21:11
TheJuliaeandersson: you realize mitaka is unsupported by the community correct?21:12
eanderssonYea - that does unfortunately not change the fact that we are not yet ready to upgrade.21:12
TheJulia:(21:12
TheJuliaOkay21:12
TheJuliaI'm fairly sure we didn't add network_interface until newton21:13
TheJuliabut I'm looking21:13
eanderssonThanks - we are deploying Ironic both as Mitaka and Queens, but we ideally want to roll out Ironic in PROD before the upgrade.21:13
*** priteau has quit IRC21:14
*** baha has quit IRC21:14
TheJuliayup, it is not in ocata, so only flat networks.21:14
TheJuliaerr21:14
TheJuliamitaka21:15
TheJuliaonly flat networks in mitaka21:15
jrollpretty sure it was newton, yeah21:15
eanderssonThanks - I thought so21:15
TheJuliamitaka was fairly stable if memory serves21:16
TheJuliaBut we've added a lot of functionality and refactored quite a bit since then. Queens would be better... You won't just be able to run a mixed environment with a queens ironic and a mitaka deployment otherwise since I believe we had to land binding profile stuffs into neutron and you need a ml2 plugin to manage the switches that supports the baremetal vnic_type21:18
TheJuliajroll: I was thinking newton because I was fairly sure I was reviewing network_interface patches when I first visited the future mother-in-law's driveway with my motorhome21:20
jrollheh, weird how memories work21:21
jrollI was thinking newton because it was like, "finally"21:21
*** ak has joined #openstack-ironic21:21
jrollrelease notes confirm newton, 6.121:22
TheJuliajroll: thanks!21:24
jroll:)21:24
jrollhave a good night y'all21:24
TheJuliaAnyway, speaking of future mother in law's... I need to go make myself presentable to take the other half and her mom out to dinner21:24
TheJuliagoodnight jroll21:24
*** ceryx has joined #openstack-ironic21:25
TheJuliaeandersson: let us know if you have any more questions or if we can be of any more assistance. For now, I'm stepping away. Have a wonderful evening21:25
eanderssonSounds good, appreciate that21:25
*** dsneddon has quit IRC21:29
*** dsneddon has joined #openstack-ironic21:31
*** Goneri has quit IRC21:36
*** bnemec has quit IRC21:46
*** rcernin has joined #openstack-ironic22:02
*** jesusaur has joined #openstack-ironic22:03
*** priteau has joined #openstack-ironic22:14
*** pmannidi has joined #openstack-ironic22:17
*** threestrands has joined #openstack-ironic22:18
*** threestrands has quit IRC22:18
*** threestrands has joined #openstack-ironic22:18
*** e0ne has quit IRC22:39
*** jcoufal has quit IRC22:40
*** linkmark has joined #openstack-ironic22:40
*** hongbin has quit IRC22:52
*** EranBD has quit IRC23:00
*** markguz has joined #openstack-ironic23:08
*** alineb has quit IRC23:14
*** markguz has quit IRC23:15
*** markguz has joined #openstack-ironic23:16
*** r-daneel has quit IRC23:16
*** markguz has quit IRC23:20
*** alineb has joined #openstack-ironic23:39
*** etingof has quit IRC23:58

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