Thursday, 2014-07-17

*** rameshg87 has joined #openstack-ironic00:29
openstackgerritJosh Gachnang proposed a change to openstack/ironic-python-agent: Add versioning to Agent decommission  https://review.openstack.org/10685900:34
*** hemna is now known as hemna_00:43
openstackgerritMichael Davies proposed a change to openstack/ironic: Review fixes from Nova scheduler reviews  https://review.openstack.org/10731600:58
mrdaNobodyCam: that took longer than expected (@property can only have one param :) but when you have a moment, 107316 is ready for review.01:00
*** foexle_ has joined #openstack-ironic01:06
openstackgerritRuby Loo proposed a change to openstack/ironic: Add drivers.base.BaseDriver.get_properties()  https://review.openstack.org/10709201:07
openstackgerritRuby Loo proposed a change to openstack/ironic: Implement API to get driver properties  https://review.openstack.org/10709601:08
*** foexle has quit IRC01:10
NobodyCamlifeless: you see the failed test on 10751101:10
NobodyCamlooks like https://github.com/openstack/nova/blob/master/nova/tests/compute/test_compute_mgr.py#L1815 needs a update too01:10
lifelessNobodyCam: this is why I want someone to pick the patch up and run with it01:11
NobodyCamlol... ack01:11
rlooNobodyCam: thx for rechecking 107092 & 107096. I "fixed" it I hope, but not sure why it caused sphinx to barf.01:13
NobodyCamrloo: ya that was very odd error01:17
*** rameshg87 has left #openstack-ironic01:41
*** nosnos has joined #openstack-ironic01:49
*** malini has quit IRC01:59
*** killer_prince is now known as lazy_prince02:18
*** geekyogi has joined #openstack-ironic02:32
*** rloo has quit IRC02:40
*** ramineni has joined #openstack-ironic02:59
*** Penick has joined #openstack-ironic03:01
*** vinbs has joined #openstack-ironic03:02
*** Penick has quit IRC03:05
*** Poornima has joined #openstack-ironic03:05
*** nosnos has quit IRC03:06
vinbsMorning Ironic!03:21
*** pcrews has quit IRC03:24
*** nosnos has joined #openstack-ironic03:33
*** rakesh_hs has joined #openstack-ironic03:37
Haomeng|2vinbs: morning:)03:52
mrdaHi Haomeng|2 and vinbs03:53
Haomeng|2mrda: morning:)03:53
mrda\o03:53
vinbsHaomeng|2 , mrda have you come across this error anytime: "Returning exception string indices must be integers to caller"03:57
vinbswhen I try to launch an instance I'm running into this error03:57
Haomeng|2vinbs: can you paste the code?03:57
openstackgerritMichael Davies proposed a change to openstack/ironic: Ironic nova driver to cache ironic client calls  https://review.openstack.org/10269503:58
vinbsHaomeng|2: you mean the logs? I'm using ironic juno code03:58
Haomeng|2vinbs: I mean what code you run out such exception03:59
Haomeng|2maybe this can help you - http://stackoverflow.com/questions/20084779/typeerror-string-indices-must-be-integers-while-parsing-json-using-python03:59
vinbsHaomeng|2 here's the traceback04:00
vinbshttp://paste.openstack.org/show/86860/04:00
Haomeng|2ok04:00
mrdavinbs: what were you doing to trigger this?04:02
mrdado you have a commandline you can share?04:02
vinbsmrda: I run into this error when I launch an instance through the Horizon04:03
Haomeng|2looks like  instance['uuid'] is not integers04:03
lifelessmrda: replied, i hope.04:04
mrdacool (I hope :)04:04
mrdalifeless: so, are you happy with removing the 30 second check and no other changes?04:06
mrdalifeless: or are you stuck on caching being implemented in the python-ironicclient?04:06
lifelessmrda: no - expired tokens do need to be handled04:06
lifelessmrda: I'm pretty stuck on that04:06
mrdais token.expiry > now: request new token04:06
lifelessinsufficient04:07
vinbsmrda, Haomeng|2 I do not have any other instance running prior to launching this instance (when I get the error)04:07
lifelessuhm, I seem to not be describing the situation well enough04:07
mrdahmmm, I disagree based on what I've read so far.04:07
lifelessmrda: here is the way tokens behave. Sometimes they go away in a graceful fashion. Other times the token store is deleted.04:08
vinbsmrda, HAomeng|2 and I can see that the instance which fails due to this error gets an id like 7c7af6ec-ed4c-4611-9d8e-247dd7f0956f04:08
Haomeng|2vinbs: can you debug it, should be type error04:08
Haomeng|2vinbs: yes, the uuid should be string, not integer04:08
vinbsHaomeng|2 so it might be a problem with the code I have?04:09
lifelessmrda: ok, so which of these axioms do you disagree with?04:09
Haomeng|2vinbs: sorry, not sure, have to debug I think04:09
lifeless*) clients cannot tell if a token is valid04:09
lifeless*) servers are allowed to revoke tokens before their expiry date04:09
lifeless*) clients and servers may have clock skew04:09
vinbsHaomeng|2 okay.. I'll look deeper into it04:10
Haomeng|2vinbs: ok, good luck:)04:10
*** rakesh_hs has quit IRC04:11
mrdalifeless: so I get this.  I don't understand though why you think that implementing this in ironicclient is better than in the ironic_client_wrapper code04:11
lifelessmrda: because its not unique to the nova ironic driver04:11
lifelessmrda: its a global challenge that all users of ironic's python API have04:11
mrdahow many programmatic users of python-ironicclient are there?04:12
lifelessat least 3 - os-cloud-config, nova's ironic driver, openstackclient (the last one is 'in principle')04:13
lifelesswe'll have monitoring stuff for ironic sometime soon I sspect as well04:14
*** lazy_prince is now known as killer_prince04:17
lifelessplus I don't see how you can cleanly solve it in wrapper code since it depends on understanding the semantics of failures04:18
mrdaI do think the current solution solves the problem04:18
mrda...as much as doing it in ironicclient04:19
lifelesswell, it doesn't solve the token revocation issue yet04:19
*** bmahalakshmi has joined #openstack-ironic04:19
mrdawithout talking to keystone, I don't think you can04:19
mrdano matter where that code might live04:20
lifelessyou catch the validation failure, ask for a new token, and submit04:20
lifelessor maybe I'm confused about something here04:21
mrdawell, i'm going to have to go back an re-read ironicclient code if you think that's possible04:22
lifelessI'm sure ironicclient will need to change04:22
lifelessbut I really don't want to have to go and restart nova-compute if keystone has to revoke a bunch of tokens04:23
lifelessso we need this to cope04:23
lifelessit should be fairly straightforward: if the error is a keystone token error, we know it happened before any POST / PUT / PATCH action occured, so we have situation specific knowledge to permit a resubmission of the request, and we need to ask for a new token then submit it04:24
lifelessnow, ironicclient may not have a way to ask for a new token yet - so we may need to add that (e.g. a callback the user of ironicclient can supply)04:24
*** pradipta_away is now known as pradipta04:25
lifelessI have to go pick up C04:27
*** pcrews has joined #openstack-ironic04:30
*** malini has joined #openstack-ironic04:31
*** geekyogi has quit IRC04:45
*** pcrews has quit IRC04:49
*** rameshg87 has joined #openstack-ironic04:50
*** malini has quit IRC04:56
*** killer_prince is now known as lazy_prince05:10
*** malini has joined #openstack-ironic05:20
*** shausy has joined #openstack-ironic05:25
lifelessmrda: back if you want to talk round this more05:32
*** rakesh_hs has joined #openstack-ironic05:41
*** chuckC has joined #openstack-ironic05:43
*** jcoufal has joined #openstack-ironic05:57
*** malini has quit IRC06:02
*** Nisha has joined #openstack-ironic06:05
*** malini has joined #openstack-ironic06:06
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic: Imported Translations from Transifex  https://review.openstack.org/10694806:11
*** malini has quit IRC06:11
*** bvivek has joined #openstack-ironic06:12
*** malini has joined #openstack-ironic06:12
openstackgerritNisha Agarwal proposed a change to openstack/ironic-specs: Discover node properties at node-create/node-update  https://review.openstack.org/10095106:17
*** k4n0 has joined #openstack-ironic06:22
openstackgerritNisha Agarwal proposed a change to openstack/ironic-specs: Discover node properties at node-create/node-update  https://review.openstack.org/10095106:25
*** pcrews has joined #openstack-ironic06:28
*** foexle_ has quit IRC06:29
*** ramineni1 has joined #openstack-ironic06:31
*** pleia2_ has joined #openstack-ironic06:33
*** lynxman_ has joined #openstack-ironic06:33
mrdalifeless: I'm just going to focus on review comments this afternoon and come back to client auth tomorrow06:33
*** viktors|afk has quit IRC06:34
*** Poornima has quit IRC06:34
*** d0ugal has quit IRC06:34
*** jrist has quit IRC06:34
*** krtaylor has quit IRC06:34
*** ramineni has quit IRC06:34
*** lynxman has quit IRC06:34
*** pleia2 has quit IRC06:34
*** mmitchell_ has quit IRC06:34
*** k4n0 has quit IRC06:34
lifelessmrda: k06:34
*** lynxman_ is now known as lynxman06:34
*** lynxman has quit IRC06:34
*** lynxman has joined #openstack-ironic06:34
*** mmitchell has joined #openstack-ironic06:34
*** Poornima has joined #openstack-ironic06:35
*** jrist has joined #openstack-ironic06:35
*** d0ugal has joined #openstack-ironic06:36
*** krtaylor has joined #openstack-ironic06:36
*** viktors has joined #openstack-ironic06:36
*** k4n0 has joined #openstack-ironic06:36
openstackgerritHaomeng,Wang proposed a change to openstack/ironic: Implements send-data-to-ceilometer  https://review.openstack.org/7253806:41
*** foexle has joined #openstack-ironic06:44
*** bvivek has quit IRC06:48
*** bvivek2 has joined #openstack-ironic06:49
*** pcrews has quit IRC06:49
*** Nisha has quit IRC06:51
*** Haomeng|2 has quit IRC06:51
*** Haomeng has joined #openstack-ironic06:52
soren   /win 29506:53
sorenDOh06:53
rameshg87lifeless: are you still around. just had a quick question for you :-)06:56
*** ifarkas has joined #openstack-ironic06:59
lifelessrameshg87: a little07:03
rameshg87thanks lifeless. won't take much of your time.07:04
rameshg87lifeless: this is regarding the virtual media deploy spec that we were discussing a few hours back07:05
rameshg87lifeless: based on the last discussion, your suggestion was to break down and propose as 3 specs07:05
rameshg87lifeless: #1 - add a generic virtual media boot mechnaism for booting the node and passing information out-of-band07:05
rameshg87lifeless: #2 - replace the "pxe" part of the current pxe+iscsi deploy solution and bring up a vmedia+iscsi deploy solution07:06
*** pradipta is now known as pradipta_away07:06
rameshg87lifeless: #3 - propose the (currently proposed) baremetal deploy solution from swift in a third spec, in a new vmedia+bm_deploy_swift deploy solution07:07
lifeless1) was ilo specific07:07
rameshg87lifeless: yes, #1 was ilo specific07:08
rameshg87lifeless: #1 which can be used by any deploy driver with ilo07:08
lifeless1) would deliver ilo w/iscsi07:08
lifelessso ilo native power management, virtual media boot, virtual media token handoff07:09
rameshg87lifeless: #1 is not a deploy driver by itself, just a mechanism to boot up the node and pass information out-of-band which can be used by any driver07:09
rameshg87lifeless: yes07:09
lifelessits a deploy module07:09
rameshg87lifeless: #2 and #3 are deploy drivers07:09
lifelessthe 2 and 3 you have above is slightly different to what I proposed07:09
lifeless1) IMO includes the 2) you have07:10
lifelessthe 2) I was saying was making it possible to mix different boot methods with deploy code07:10
lifeless(and vice versa)07:10
lifelessinternal refactoring to make it possible to use a different deploy solution07:10
lifeless3) would use that to do swift for ilo+vmedia or pxe+ipmi07:11
rameshg87lifeless: so do you suggest to have swift for pxe+ipmi as well.07:12
lifelessIt would be a natural consequence, if we decide swift support makes sense07:13
lifelessits not obvious that it does07:14
rameshg87lifeless: basically your suggestion is to modularize the deploy solution so that ultimately after everything ( deploy solution = boot method + deployment engine )07:14
lifelessgiven the already existing option of IPA which does swift07:14
rameshg87lifeless: am i correct ?07:14
rameshg87lifeless: so that we can mix match boot methods and deployment engines to create different deployment engines07:15
rameshg87lifeless: currently the only thing available is "pxe" for boot method and "iscsi" for deployment engine07:15
rameshg87lifeless: typo above "lifeless: so that we can mix match boot methods and deployment engines to create different deployment *SOLUTIONS*"07:16
*** jistr has joined #openstack-ironic07:18
lifelessyes07:18
lifelesswe have a bunch of modularity there already07:18
rameshg87lifeless: yeah.07:20
*** viktors has quit IRC07:22
*** kpavel has quit IRC07:23
rameshg87lifeless: we wanted to see if we can make something for juno07:23
rameshg87lifeless: we can add vmedia boot mechanism (booting with vmedia + passing information out-of-band) as it is mostly approved.07:24
rameshg87lifeless: i can propose to do vmedia + bm deploy in a modular way for now, as the solution is ready tested07:25
rameshg87lifeless: we would also propose vmedia + iscsi in design spec, but i doubt if it will get approved as it will involve some refactoring on the existing code07:26
rameshg87lifeless: is it okay if we propose the spec for refactoring and subsequently vmedia+iscsi, and do it in K release. does that look okay to you ?07:26
*** romcheg1 has joined #openstack-ironic07:27
*** Mikhail_D_ltp has joined #openstack-ironic07:32
lifelessI am confused07:33
openstackgerritMichael Davies proposed a change to openstack/ironic: Review fixes from Nova scheduler reviews  https://review.openstack.org/10731607:33
lifelesswhat I'm proposing is vastly less code, much easier to land for juno07:33
*** viktors has joined #openstack-ironic07:35
rameshg87lifeless: possible to code by juno timeframe, but no new specs(or proposals) in ironic will be accepted as per my knowledge for juno release07:36
rameshg87lifeless: am i correct ?07:36
lifelessthats a question for devananda07:37
lifelessbut this spec isn't approved yet anyway07:37
lifelessbreaking it into three subsidiary specs doesn't seem like a reason to not accept part of it07:37
*** harlowja is now known as harlowja_away07:41
*** geekyogi has joined #openstack-ironic07:42
rameshg87lifeless: i will discuss with devananda and get back regarding what all can be accommodated and get back.07:46
rameshg87lifeless: meanwhile i will just start working on breaking down specs07:46
rameshg87lifeless: thanks ..07:46
*** bvivek2 has quit IRC07:57
openstackgerritHaomeng,Wang proposed a change to openstack/ironic: Implements send-data-to-ceilometer  https://review.openstack.org/7253807:58
*** pleia2_ is now known as pleia208:04
*** derekh_ has joined #openstack-ironic08:08
*** kpavel has joined #openstack-ironic08:10
*** malini has quit IRC08:12
*** rwsu has quit IRC08:13
*** lucasagomes has joined #openstack-ironic08:23
*** bmahalakshmi has quit IRC08:24
*** bvivek has joined #openstack-ironic08:30
*** bmahalakshmi has joined #openstack-ironic08:30
*** ndipanov has joined #openstack-ironic08:36
*** pelix has joined #openstack-ironic08:38
*** martyntaylor has joined #openstack-ironic08:40
*** ndipanov has quit IRC08:40
lucasagomeslifeless, morning/evening... can you remove the -2 here? https://review.openstack.org/#/c/86092/ spec is already approved08:42
*** athomas has joined #openstack-ironic08:42
mrdalucasagomes: If I ask nicely will lifeless remove any -ve votes? :-)08:43
lucasagomesmrda, haha you can try :P08:43
mrda(and good morning to you lucasagomes btw)08:43
lucasagomesmrda, morning buddy, how it's going?08:43
mrdagood - you coming to midcycle?08:43
lucasagomesmrda, yeah, I am08:43
mrdaGreat! Looking forward to hanging out with you again!08:44
lucasagomessame here, are you going for pizza on sunday right?08:44
mrdaf'sure - I arrive Sat night, so I'm up for it08:44
lucasagomesI will try to make it, if nothing bad happens, no delays etc08:44
lucasagomesah great08:44
mrdaI need the Sunday to get me in the right TZ08:45
lucasagomesyeah hah I hear you08:45
dtantsur|afkMorning Ironic :)08:58
mrdahey dtantsur|afk08:59
*** dtantsur|afk is now known as dtantsur08:59
dtantsurmrda, good evening :)08:59
dtantsurlucasagomes, morning :) you know, what I am going to ask you, right? ;)09:00
lucasagomesdtantsur, heh yeah09:00
ramineni1dtantsur: hi, morning :)09:01
dtantsurramineni1, hi09:04
ramineni1dtantsur: regarding your comments on https://review.openstack.org/#/c/89500/25/etc/ironic/ironic.conf.sample09:05
ramineni1dtantsur: here we meant ilo_client_timeout , actually for timeout to be specified for IloClient in proliantutils module .09:06
ramineni1dtantsur : so, named it that way09:06
dtantsurramineni1, it does not matter for Ironic itself, how you used. I'm just worried about inconsistent naming09:07
lifelesslucasagomes: my comment has nothing to do with the spec09:08
lucasagomeslifeless, yup, I answer that a bit back09:08
lifelesslucasagomes: devananda said09:08
lucasagomeslifeless, there's an abstraction layer there that checks wheteher the driver does have the mgmt or not09:08
lifeless"    this whole patch series needs to land at once. Partial changes to some drivers will be very detrimental without the corresponding API changes, which are at the tail of this patch series, and are NOT approved yet."09:08
lucasagomesyup09:08
lucasagomesbut that's no problem, cause there's a backward comp layer there, if the mgmt interface is not implemented it uses the vendor_passthru09:09
lucasagomesso patches can be merged separately09:09
lucasagomesdeva already removed his -209:09
lifelessso what detrimental effect is devananda pointing out?09:09
lucasagomeslifeless, https://review.openstack.org/#/c/86092/20/ironic/conductor/utils.py09:09
lucasagomeslifeless, oh... so, I can put the API patch in front of the series09:12
lucasagomeslifeless, would that solve his concern you think?09:12
lifelesslucasagomes: I'm not sure09:12
lucasagomesI will ask him later09:12
lifelessI've removed my -2, I don't want to block for no reason09:12
lucasagomeslifeless, ack, I will sync with him about it. Thanks09:13
ramineni1dtantsur: yes , but its not actually prefixing ilo to the variable , but want to specify its actually the timeout to be specified for IloClient, do u still feel need to change the naming09:13
lifelessbut I'm very firmly of the opinion we shouldn't land things unless we're happy with the patch in isolation09:13
lucasagomes+109:13
lifelessbecause we can't predict what will happen (the gate might wedge, for instance)09:13
dtantsurramineni1, it's quite obvious, that for ILO driver you use ILO client :) yes, I feel like that09:13
lucasagomeslifeless, +1, I think it's fine. But I will double check09:14
ramineni1dtantsur: ok ..will change it :)09:15
*** mkerrin has quit IRC09:16
*** Nisha has joined #openstack-ironic09:17
Nishadtantsur: Hi09:18
*** mkerrin has joined #openstack-ironic09:23
*** martyntaylor has left #openstack-ironic09:29
dtantsurNisha, hi! I didn't quite get your questions, sorry. What do you mean by blocked here?09:30
lucasagomesdtantsur, reviewed, looking good09:33
lucasagomesdtantsur, few concerns, about how to know if the discovery is enabled for a specific driver (suggestion inline) and if we should make the activation/deactivation async09:34
lucasagomessince some drivers may need to talk to the BMC09:34
*** Nisha has quit IRC09:35
dtantsurlucasagomes, I guess it should be async, it even seems to me I put it to spec :)09:36
dtantsurwill see your comments, thanks09:36
lucasagomesdtantsur, right it was retuning 200 after the put09:36
lucasagomesso it should return 202 (accepted)09:36
lucasagomesto indicate it's async09:36
dtantsuraaaah09:36
openstackgerritAnusha Ramineni proposed a change to openstack/ironic: Add IloDriver and its IloPower module  https://review.openstack.org/8950009:47
openstackgerritSyed Ismail Faizan Barmawer proposed a change to openstack/ironic-specs: UEFI support for Ironic deploy drivers  https://review.openstack.org/9985009:50
*** nosnos has quit IRC09:54
*** romcheg2 has joined #openstack-ironic09:54
dtantsurlucasagomes, devananda, re https://review.openstack.org/#/c/107407/: reported https://bugs.launchpad.net/ironic/+bug/1343195 . If we can't support SQLite properly, I suggest not supporting it at all.09:56
*** romcheg1 has quit IRC09:57
rameshg87lucasagomes, dtantsur, just had a quick question about a refactoring i am thinking09:58
lucasagomesrameshg87, hey sure09:58
rameshg87lucasagomes, dtantsur, might not be that quick, but just wanted to check if it makes sense :-)09:58
lucasagomesdtantsur, yeah, well I think it's more like an openstack thing09:59
lucasagomesdtantsur, idk if it's our call to remove sqlite support like that09:59
rameshg87lucasagomes, dtantsur, currently our pxe driver is not truly "pxe", it's actually "pxe+iscsi", uses pxe for booting and uses iscsi for deployment09:59
lucasagomesrameshg87, true09:59
rameshg87lucasagomes, dtantsur, if i wanted to have a deploy driver which uses virtual media (vmedia) for booting and iscsi for deployment, i can make use of most of the code in there10:00
rameshg87lucasagomes, dtantsur, each stage of the PXEDeploy contains some things related to "pxe" and some things related to "iscsi"10:01
*** nosnos has joined #openstack-ironic10:01
*** bvivek has quit IRC10:01
lucasagomesrameshg87, yup, we also have the TFTP factor as well our driver pretty much assume that PXE == TFTP10:02
lucasagomesiPXE change that so I had to do some refactoring10:02
rameshg87lucasagomes, okay10:02
lucasagomesI bet the iscsi is something similar we should start refactoring that parts out of the pxe driver10:02
dtantsurlucasagomes, left one question is the spec.10:02
lucasagomesputting in a common directory that other drivers may use as well10:02
rameshg87lucasagomes: exactly, that is what i want :-)10:03
rameshg87lucasagomes: does it make sense if we split a deploy driver, so that deploy driver = BootManager + DeployManager10:03
lifelesshah, nova is picking an in-maintenance node.10:03
lifelesswtf10:03
dtantsurOo10:04
lifelessI will poke around that tomorrow, but that might explain some things :>10:04
rameshg87lucasagomes: each of BootManager and DeployManager has their own actions to perform for each stages of deploy - validate, deploy, tear_down, prepare, cleanup10:04
rameshg87lucasagomes: does that make sense ?10:04
openstackgerritMichael Davies proposed a change to openstack/ironic: Review fixes from Nova scheduler reviews  https://review.openstack.org/10731610:05
rameshg87lucasagomes: the actual deploy driver will just call BootManager's and DeployManager's corresponding method10:06
lucasagomesdtantsur, yeah I can only think about having it in the db :/10:06
dtantsurlucasagomes, but where?10:07
lucasagomeslifeless, ew, yeah shouldn't happen :/10:07
lucasagomesrameshg87, hmm I have to think about... you mean having another driver interface for boot manager?10:07
lucasagomesdtantsur, yeah thinking... cause drivers doesn't have it's on model in the db10:08
rameshg87lucasagomes: sort of, because from each of the actual deploy steps, there are certain steps belonging to the boot manager alone ..10:09
dtantsurlucasagomes, if we are to create a new DB model, I would rather drop it :) but enabling 2 drivers to do the discovery may lead to a disaster10:10
rameshg87lucasagomes: some high level method calls BootManager's method followed by DeployManager's method10:10
*** nosnos has quit IRC10:10
lucasagomesdtantsur, somewhere we have to indicate if it's enabled no?10:10
*** romcheg1 has joined #openstack-ironic10:10
dtantsurlucasagomes, I think so10:10
dtantsurand it should be something global10:11
lucasagomesyeah that's why I only can think about db, cause even if we talk about using config options10:11
rameshg87lucasagomes: ultimately deploy_driver.deploy() calls BootManager.deploy() and then calls DeployManager's deploy() [and returns whatever it is returning]10:11
lucasagomesthey are not global10:11
*** romcheg2 has quit IRC10:11
lucasagomesrameshg87, right, it makes sense... but is it something that we want to have in juno?10:11
dtantsuroooh10:11
lucasagomescause that will be hard man10:11
dtantsurlucasagomes, should we discuss it more with devananda and folks this evening?10:12
*** nosnos has joined #openstack-ironic10:12
lucasagomesdtantsur, I think so... maybe drivers need to have their db model as well, since they even have their own endpoint, vendor_passthru etc10:12
lucasagomesit makes sense to have the driver entity representation on the db10:12
lucasagomesas well as we have in the api10:13
dtantsurlucasagomes, wow-wow. this looks like a big task. I wonder if it's an acceptable compromise not to do this check10:13
dtantsurlucasagomes, put then set_discovery_enabled will no longer be idempotent10:13
lucasagomesdtantsur, yeah we can for the first version simply have no check like that10:13
lucasagomesI'm fine with that10:14
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: POC: sync models with migrations test  https://review.openstack.org/10762810:14
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: POC: use metadata.create_all() to fill database  https://review.openstack.org/10762910:14
lucasagomeswe document it as an experimental feature etc10:14
dtantsurlucasagomes, ok. I'll add 2 TODO's to the text, stating it should be done later and why10:14
lucasagomesack10:14
dtantsurbrb10:15
rameshg87lucasagomes: don't know was just thinking before i want to put it in a spec.  do you think it will be too late for juno ? :D10:18
*** martyntaylor1 has joined #openstack-ironic10:19
lucasagomesrameshg87, I think that if we are going to introduce a new interface for the drivers in juno10:20
lucasagomes+ having to change all the existing drivers10:20
lucasagomesit will be late10:20
lucasagomesbecause we are planning on landing not only the iLO driver10:20
lucasagomesbut also Drac and IPA10:20
lucasagomesand this are ongoing work, so it will all conflict10:20
lifelesslucasagomes: so drac and IPA are orthogonal10:21
lifelesslucasagomes: IPA needs a boot mechanism too, right?10:21
lucasagomeslifeless, they have a deploy interface as well afair10:21
lucasagomeslemme check the code10:21
lifelesslucasagomes: the more I think about this the more I'm convinced we have three dimensions that vary independently10:21
lifelesslucasagomes: a) how do we control power, b) how do we get our code onto the machine - how do we boot it, c) what code we're expecting on the machine (IPA / deploy-ironic-init)10:22
lifelesslucasagomes: e.g. iLO + iLO virtualmedia + IPA should totally be a thing10:22
lifelesslucasagomes: but equally we could in principle do iLO + PXE + IPA10:23
lucasagomesI agree, IPA and ILO virtualmedia are deploy interfaces, where iLO is a power interface10:23
lucasagomesand I agree with rameshg87 thinking as well10:23
lucasagomesbut I'm just wondering what can be make for _juno_10:23
lifelesslucasagomes: well, I'm saying that IPA is a deploy interface, but iLO virtualmedia is a boot interface.10:23
lifelesslucasagomes: different things10:23
lucasagomesif we introduce a new interface for the drivers in this moment, I don't think it will make it to juno10:23
mrdaok, enough for me.  Good night Ironic!10:24
lifelesslucasagomes: for Juno I'm proposing that we do iLO virtualmedia as subclass of the PXE deploy module10:24
*** mrda is now known as mrda-away10:24
lucasagomesright10:24
lifelesslucasagomes: (effectively, maybe a little pull-up into a common class)10:24
lifelesswhich should be trivial10:25
rameshg87lucasagomes, lifeless, yes a common class might also make sense because pxe inheriting virtualmedia doesn't make true sense here :-)10:25
rameshg87sorry virtualmedia inheriting pxe10:25
lucasagomeslifeless, rameshg87 yeah I think u guys are right the way it boots the machine != the way the machine gets deployed10:27
lucasagomesrameshg87, yup, the PXE driver is now bloated. It's all together PXE + TFTP + iSCSI10:27
lifelessPXE+TFTP is the boot component10:28
lifelessiSCSI is deploy10:28
lifelessand there's a niche thing in there about token hand-off10:28
lucasagomeslifeless, yeah well if you think about iPXE TFTP is only used for chainloading10:28
lucasagomeslifeless, the rest can all happen over other transport layer like HTTP10:28
lucasagomesthat's why we kinda have to refactor that as well, make it more flexible at least10:28
*** derekh_ has quit IRC10:31
lucasagomesrameshg87, lifeless so we agreed that boot interface != deploy interface10:31
lucasagomeslifeless, rameshg87 but what we can make for J?10:31
lucasagomescan we keep only the deploy interface for this cycle, and introduce a new boot interface in K?10:32
rameshg87lucasagomes, i think refactoring pxe might not be that difficult if we can quickly get a spec in (if it will be accepted)10:32
viktorsdtantsur: hi!10:32
lucasagomesrameshg87, right, so other projects like nova already started -2ing new specs10:33
lucasagomeswe are almost at the end of j-210:33
lucasagomesgoing to j-310:33
lucasagomeswe have ~8 specs approved10:34
lucasagomesaccording to last devananda's email10:34
lucasagomesand they all need reviews etc, that's why I think it will be a bit hard10:34
rameshg87lucasagomes: okay ..10:35
lucasagomesrameshg87, but as I said, I agree with the idea10:35
lucasagomesdef we have to improve that abstraction10:35
lucasagomesjust trying to be realistic about what can be achieved in this cycle10:35
lucasagomeslifeless, how is it in tripleO? are you guys still accepting new specs?10:37
*** lazy_prince is now known as killer_prince10:38
lifelessI don't think we can do the refactoring in juno10:38
lifelessbut we can land a minimal virtualmedia ilo deploy driver that shares 99% of its code with pxe10:38
lucasagomesyeah10:38
lucasagomes+1000010:38
*** nosnos has quit IRC10:38
rameshg87lucasagomes, lifeless, okay. so just to make use of the "common" code and not to touch anything in "pxe", we might need to inherit from "pxe" ?10:38
rameshg87lucasagomes, lifeless, ilo_vmedia_driver inherits from pxe and calls whatever it requires. eventhough logically it doesn't sound good, is it acceptable ?10:39
lifelesslets not confound spec (design) with impl10:40
lucasagomesrameshg87, I don't understand exactly all the bits and pieces needed for ilo media driver to tell that10:40
lucasagomesbut if there's a common code we may want to put in a common place10:40
lifelessthe spec thing here is to say that we want 99% code sharing and only diff being how it boots and how it hands tokens across10:40
lucasagomesthat can be accessed by both drivers10:40
*** derekh_ has joined #openstack-ironic10:40
*** killer_prince is now known as lazy_prince10:41
rameshg87lifeless: okay10:41
lifelessthe impl thing is to pull pxe apart vertically into 99% common code and 1% truely-pxe/tftp-unique10:41
lifelessand plug in the 1% virtualmedia glue beside it10:41
rameshg87lifeless: okay :-)10:41
rameshg87lifeless, lucasagomes, thanks a lot for your thoughts10:43
lucasagomesrameshg87, yvw10:43
*** dguerri is now known as _dguerri10:44
*** romcheg has quit IRC10:44
*** romcheg1 is now known as romcheg10:44
*** _dguerri is now known as dguerri10:46
*** Alexei_987 has joined #openstack-ironic10:46
viktorslucasagomes: hi! Can I discuss with you an idea about initial database migration?10:47
lucasagomesviktors, can we talk in a bit? I'm going for lunch10:49
openstackgerritMikhail Durnosvistov proposed a change to openstack/ironic: Check whether specified FS is supported  https://review.openstack.org/9810210:50
viktorslucasagomes: ok, sure.10:50
*** martyntaylor1 has quit IRC10:50
*** martyntaylor has joined #openstack-ironic10:51
dtantsurviktors, hi! sorry, was out10:57
viktorsdtantsur: no problem10:57
viktorsdtantsur: as for our yesterday's discussion about migrations on SQLite - I want to show you the proof-of-concept, how to fill database from models10:59
viktorsdtantsur: I suppose to create DB schema from models 1) - for testing, 2) - for installation on demand11:00
*** ndipanov has joined #openstack-ironic11:00
viktorsdtantsur: what do you think about it?11:00
*** ndipanov has quit IRC11:01
*** ramineni1 has quit IRC11:01
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: Use oslo.db library  https://review.openstack.org/4215911:05
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: POC: use metadata.create_all() to fill database  https://review.openstack.org/10762911:05
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: POC: sync models with migrations test  https://review.openstack.org/10762811:05
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: Use opportunistic approach for migration testing  https://review.openstack.org/10705311:05
*** dguerri is now known as _dguerri11:05
dtantsurviktors, should be good, let me see11:06
viktorsdtantsur: POC: use metadata.create_all() to fill database  https://review.openstack.org/10762911:06
dtantsuryeah, I see :)11:06
*** lucasagomes is now known as lucas-hungry11:07
*** Haomeng|2 has joined #openstack-ironic11:08
dtantsurlgtm actually11:09
*** Haomeng has quit IRC11:10
viktorsdtantsur: thanks! I want to show this approach to lucas-hungry also11:10
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Add newly_discovered column to Node object  https://review.openstack.org/10738911:11
viktorsad it still required oslo.db, which actuary -2'ed :(11:11
dtantsurviktors, how are things with it? does it make sense to give it a second try?11:12
kpavelHi. Can anybody point me to the reference of the neutron configuration for ironic? thanks11:12
viktorsdtantsur: I talked with devananda last night, he told, that he will re-review patch with oslo.db, because this oslo.db required for another changes11:14
dtantsurcool!11:14
viktorsdtantsur: :)11:18
*** martyntaylor has left #openstack-ironic11:19
*** _dguerri is now known as dguerri11:20
*** jcoufal has quit IRC11:22
openstackgerritDmitry Tantsur proposed a change to openstack/ironic-specs: Generic Hardware Discovery Bits  https://review.openstack.org/10734411:29
dtantsurlucas-hungry, romcheg, NobodyCam, hopefully addressed your comments ^^^11:29
* romcheg is looking11:29
*** rameshg87 has left #openstack-ironic11:32
romchegdtantsur, lucas-hungry: I'm not very familiar with different BMCs so it may be a stupid idea11:33
romchegBut is there a way to force IPMI credentials from inside the server?11:33
romchegSo when the discovery ramdisk is running it changes the ipmi creds11:34
dtantsurromcheg, I'm not familiar with IPMI at all, so I don't know... It would be nice to have actually.11:34
romchegI also think there should be a way not only set driver specific params but also to read them11:35
romchegAnyway, every driver at least should know the credentials to for the power management interface11:36
romchegDiscovering nodes without that information is useless IMO11:36
romchegBecause we cannot do anything with them after they were discovered11:36
romchegManually setting required params is not an option if we have a few hundreds of nodes11:37
dtantsurromcheg, well, you're right. That should be prototyped by somebody knowing the topic, though :(11:43
romchegdtantsur: I think NobodyCam can help us :)11:43
dtantsurromcheg, he suggested cipher 0  (or how it is called) :D11:44
*** lazy_prince has quit IRC11:47
openstackgerritImre Farkas proposed a change to openstack/ironic-specs: DRAC management driver  https://review.openstack.org/10703311:47
jrollvinbs: did you get things sorted? looks like you're running an older nova... see https://github.com/openstack/nova/commit/ccf423333a52af9d650b2eba7199dd3a3c78f0a312:06
jrollmorning ironic :)12:06
* jroll makes coffee and ponders a BootManager thing12:07
*** shausy has quit IRC12:07
*** jdob has joined #openstack-ironic12:14
dtantsurjroll, morning :)12:19
openstackgerritJim Rollenhagen proposed a change to openstack/ironic-specs: Add deploy driver for ironic-python-agent  https://review.openstack.org/9850612:19
jrolldtantsur: morning :) fixed that for you ^12:20
vinbsjroll: yes, I have nova from icehouse version and ironic drom juno version12:20
dtantsurjroll, cool! Will have a look after lunch12:20
vinbsjroll: I was hoping it would work12:20
jrollvinbs: it should mostly work... you'll need to pull that patch in at a minimum12:21
jrollvinbs: running nova from juno will definitely work :)12:21
vinbsjroll: will try just patching.. thanks :)12:21
jrollfor some definition of "work" :)12:22
jrollno problem12:22
kpavelCan anybody point me to the neutron configuration reference  for ironic?12:26
jrollkpavel: I'm not aware of any... but I don't use neutron12:27
jrollor I should say not in the way ironic does today :P12:28
kpaveljroll: If i'm using devstack to run ironic with virtual mocked nodes it uses neutron...thought just to make few changes to control real physical hardware, but no luck :(12:29
*** ndipanov has joined #openstack-ironic12:29
*** vinbs has quit IRC12:29
jrollkpavel: that should be right :/12:29
* jroll looks at a thing12:29
kpaveljroll: The real physical node seems to be pxe booted, even can see prompt on the screen, but it doesn't aswer to ping12:30
jrollkpavel: got console logs?12:31
kpaveljroll: maybe you have a one good reference to "howto" install/configure ironic? :)12:31
agordeevromcheg: thx for the link12:32
kpaveljroll: where do i find them? it's physical machine. actually a blde..12:32
jrollkpavel: not for the pxe driver, I don't, sorry :(12:32
jrollkpavel: might need to set up the ports in neutron like devstack does? https://github.com/openstack-dev/devstack/blob/master/lib/ironic#L33412:32
jrollkpavel: console logs would be found by attaching to the console via ipmi or something12:33
jrollkpavel: if you're seeing a prompt, though... it might not be pxe booted? I'm not sure if the deploy ramdisk shows a prompt12:34
jrollneed to step away for 10 minutes... brb12:35
*** lucas-hungry is now known as lucasagomes12:39
kpaveljroll: it's pxe booted. twice :) first from deploy ramdisk/kernel and after that from ramdisk/kernel. seems to be fine.12:40
kpaveljroll: maybe you know what is the expected network setup with the real network?12:41
jrollkpavel: the bare metal node needs to be able to reach ironic-api on port 6385, and ironic-conductor need to be able to mount a disk on the baremetal node over iscsi12:42
*** jcoufal has joined #openstack-ironic12:44
jrollkpavel: does this machine have ipmi?12:44
jrolllucasagomes: got a sec to talk about https://review.openstack.org/#/c/105590/ ?12:50
jrolllucasagomes: just wondering if I should also fix the config in devstack... or just the bug in ironicclient12:50
kpaveljroll: no, the machine is blade and i developed it's own power control interface similar to ipmi. the power control seems to work fine.12:54
*** matty_dubs|gone is now known as matty_dubs12:54
lucasagomesjroll, hey yes12:57
lucasagomesjroll, hmm well... to be honest I didn't look much into it, cleary our client should be more flexible and append the version if not specified12:57
lucasagomesand not append it if already specified12:57
lucasagomesjroll, but changing devstack should work both ways12:58
lucasagomesso changing devstack right now to workaround that problem seems grand12:58
lucasagomesIMO12:58
lucasagomesuntil we get the client to be more tolerant12:58
jrolllucasagomes: right... I'm going to put up both patches, I think12:58
jrolland land in order of: devstack -> client -> 10559012:59
lucasagomesjroll, cool12:59
lucasagomessounds good to me12:59
*** dguerri is now known as _dguerri13:00
jrollhmm13:00
* jroll wonders if path.replace('/v1', '') is too hacky :P13:01
*** k4n0 has quit IRC13:01
lucasagomesjroll, it is13:02
lucasagomesjroll, we can't just replace, use urlparse13:02
lucasagomesit will split the url, into address, args etc13:02
jrollright13:02
lucasagomescheck if v1 is thre13:02
lucasagomesthere*13:02
jrollgoing to check .endswith /v113:02
jrollor .endswith /v1/13:02
jrollor like... rstrip('/'); rstrip('/v1')13:03
jrollI think is the right thing to do13:03
lucasagomesheh imo +1 for urlparse13:03
lucasagomes:P13:03
jrollofc13:04
jrollwe're already using urlparse13:04
jrollyou get the whole path back13:04
jrolland someone might have apache in front and a weird subpath... like http://somehost:1234/ironic/v113:04
lucasagomesyeah13:04
jrollso urlparse().path is /ironic/v113:05
jrollbut could also be /ironic/v1/13:05
jrollon the bright side, now we won't need to rstrip('/') on every request :)13:05
jrolloh good, no tests for get_connection_params \o/13:05
*** Poornima has quit IRC13:06
lucasagomeslol13:06
*** _dguerri is now known as dguerri13:06
lucasagomes:(13:06
jrollthat means I don't need to update tests, right? ;)13:06
lucasagomes:P13:07
*** athomas has quit IRC13:07
lucasagomesbe a good guy and create some tests13:07
lucasagomesheh13:07
*** bmahalakshmi has quit IRC13:07
jrollyeah, I am :P13:08
*** athomas has joined #openstack-ironic13:11
*** Nisha has joined #openstack-ironic13:12
viktorslucasagomes: around?13:16
lucasagomesviktors, hey yes13:16
viktorslucasagomes: I wanted to discuss patch https://review.openstack.org/107629 ( POC: use metadata.create_all() to fill database)13:17
viktorslucasagomes: do you have a time for this?13:17
lucasagomesviktors, yeah lemme take a look at the patch13:18
viktorslucasagomes: sure13:18
lucasagomesdatabase is not my strongest, but let's do it :D13:18
lucasagomesviktors, so what is that patch doing exactly? (no commit msg :()13:19
viktorslucasagomes: yes, that my miss.  The main idea of this patch is - allow to create DB schema from models  for testing, and for initial installation on demand13:21
viktorslucasagomes: tis will be faster, that from migrations and suitable for SQLite13:21
lucasagomesright, well it sounds good, what are the cons?13:22
lucasagomeswe don't execute all the migrations script13:22
lucasagomesto get to the final schema right?13:22
lucasagomeswondering if for tests... executing each migration script is what we actually want to do, to guarantee it's working13:22
viktorslucasagomes: yes, correct. We will use create_all() to get DB shema13:22
lucasagomesor we should at least have 1 test that create the schema with create_all() and one by executing all the scripts13:23
lucasagomesand compare if they are the same?13:23
viktorslucasagomes: as for migrations script - I suppose to use another approach for it13:23
viktorsthis will test migrations scripts on DB backents -  https://review.openstack.org/10705313:24
* lucasagomes clicks13:25
viktorslucasagomes: and this will test, that we will get same shema from migrations and from metadata.create_all() - https://review.openstack.org/10762813:25
yuriyzhello victors lucasagomes I think this is great idea. SQLite should not be used for production (bad support in alembic) but anyone can create new empty DB for test13:25
lucasagomesviktors, so, as I said I'm not the strongest guy in databse. But I like the idea13:26
lucasagomesI would +1 it13:26
lucasagomesI never really understood why we run all the migration scripts to create the db13:26
lucasagomesand projects like nova may have like 200 migration scripts and we ran it all for a fresh install13:27
lucasagomesso sounds to me13:27
lucasagomessounds good to me*13:27
lucasagomesyuriyz, +113:27
lucasagomesand we will have a specific test to make sure that the migrations are working and the final result is _exactly_ same as the create_all()13:28
lucasagomesso sounds pretty good13:28
viktorslucasagomes: afaik, folks from Nova want to be sure, that thay will get same DB shema from models and from migrations13:28
lucasagomesyup, yeah we may want that as well13:28
lucasagomeswe def have to cover that case13:28
viktorslucasagomes: this patch check it - https://review.openstack.org/10762813:29
viktorslucasagomes: so it should be totally safe13:29
lucasagomesviktors, +113:29
yuriyzoslo.db patch is the blocker13:29
lucasagomesviktors, good stuff13:29
viktorslucasagomes, yuriyz: yes, but id depends of oslo.db, which -2'ed at the moment =(13:30
lucasagomesviktors, right, it's -2d because it doesn't run the migration scripts on gate right?13:31
lucasagomesor something like that13:31
lucasagomesthat approach would solve that?13:31
dtantsurjroll, re your IPA spec: can we do without `lookup` method, provided our discovery discussions? that does not seem in line with what you voted for then :)13:32
viktorslucasagomes: it blocked because of bugs 1327397 and 1328997.13:32
viktorslucasagomes: I tried to fix these bugs in patch https://review.openstack.org/#/c/107053/13:32
lucasagomesright13:33
viktorslucasagomes: but this patch also requires last common db code13:33
dtantsurjroll, you can put heartbeat_timeout into driver_info and have some reasonable default13:33
lucasagomesviktors, alright... maybe we should just ping deva about it and the plans13:33
lucasagomesbut seems that having oslo.db is the base for everything13:33
lucasagomesso we should do it13:33
lucasagomesbaby steps, get the oslo.db merged -> fix the migration in gate -> use the create_all schema()13:34
yuriyzlucasagomes +113:35
viktorslucasagomes: yes, you right. It's just difficult for me to ping Deva because of time difference13:35
lucasagomesviktors, right, I will try to proxy him to it then13:35
lucasagomesidk if he's in an event right now, so today I may not see him as well13:36
lucasagomesbut I will try to talk to him soon13:36
viktorslucasagomes: thanks!13:37
viktorslucasagomes:  should I build a chain from all these patches?13:37
lucasagomesviktors, linear dependency? I think so13:37
lucasagomesI mean yes13:37
viktorslucasagomes: ok, will do.13:37
viktorslucasagomes: thanks!13:38
lucasagomesviktors, yvw, thank you for the hard working!13:38
viktorslucasagomes: no problem :)13:39
jrolldtantsur: this is where I put my foot in my mouth :|13:46
dtantsurtoo late :D13:47
jrolldtantsur: honestly? I want to have a later iteration where I match on a serial number in Node.extra. or something.13:47
jrolldtantsur: but not sure how possible that is in our environment anyway :)13:47
dtantsurjroll, not really possible, e.g. you can't search nodes based on extra13:47
dtantsurjroll, also, you'll have to prove to devananda that you can store some inventory in extra :)13:48
jrolldtantsur: ah, yeah.13:48
jrolldtantsur: an operator can put whatever they like in extra :P13:48
jroll(we already store serial number there)13:48
jroll(as well as other things)13:48
jroll(just no code interaction)13:49
*** ramineni has joined #openstack-ironic13:49
ShrewsSo, I have an ironic review to push up that adds a new python module to requirements.txt, but it's version requirement is higher than that in global-requirements.txt. I wonder if it's safe to push that up??13:50
dtantsurjroll, well, my point is to do similar things similarly. if we decided to implement discovery this way, it's reasonable for IPA to also work this way :)13:50
jrolldtantsur: I'm conflicted here, I'd like to keep our lookup function, but my reviewer hat says no13:50
jrollright13:50
jrollI just don't want to change a bunch of code, I think :)13:50
jrolldtantsur: I'll chat with people about it in the office today13:51
dtantsurjroll, I suggest re-introducing lookup, when it will be really _required_13:51
dtantsursure, let me know how it goes :)13:51
jrollShrews: we do that in IPA, but then need to -2 all the "update global requirements" reviews :/13:51
jrollShrews: I'd ask deva, or even infra13:51
Shrewsjroll: I've pushed up a review to bump the version in global-requirements.txt, it's just not +A'd yet.13:52
jrolldtantsur: will do :)13:52
Shrewsbut asking infra is probably the right call13:52
jrollShrews: oh, maybe just WIP the ironic review until that lands. what's the review #?13:52
jrollinfra does global-requirements reviews, so you've already asked :P13:52
Shrewsjroll: https://review.openstack.org/10742313:52
Shrewsi'm just wondering if timing matters here. probably not13:53
jrolloh yeah, that should be fine, I wouldn't worry about it13:53
jrollthe worst that will happen is we'll have to wait until that lands to approve "update global requirements" patches in ironic13:54
Nishadtantsur: hi13:55
dtantsurNisha, hi again13:55
Nishadtantsur: :)13:55
*** malini2 has joined #openstack-ironic13:55
openstackgerritDavid Shrewsbury proposed a change to openstack/ironic: Implement retry on NodeLocked exceptions  https://review.openstack.org/10771013:56
Nishadtantsur: i wanted to ask if i should retain the inventory structure as it was proposed in your earlier spec or its fine to have it the way it was earlier?13:56
dtantsurNisha, by `inventory structure` you mean what will be returned from new ManagementInterface method?13:57
Nishayes13:57
openstackgerritMikhail Durnosvistov proposed a change to openstack/ironic: Check whether specified FS is supported  https://review.openstack.org/9810213:58
Nishadtantsur: yes you are right...i meant the dictionary returned by new ManagemnetInterface function14:00
*** Mikhail_D_ltp has quit IRC14:00
dtantsurNisha, you're free to use whatever you want (though I still like my structure :) and it corresponds to IPA's one)14:00
Nishadtantsur: Ok. I have no issues to use that one14:01
Nishadtantsur: i just wanted to know if its required to retain that structure14:01
*** dguerri is now known as _dguerri14:05
Nishadtantsur: lucasagomes devananda NobodyCam lifeless : request your review for https://review.openstack.org/#/c/100951/14:07
*** _dguerri is now known as dguerri14:07
*** Nisha has quit IRC14:11
openstackgerritJim Rollenhagen proposed a change to openstack/python-ironicclient: Trim trailing slash and version from endpoint  https://review.openstack.org/10771514:13
jrolllucasagomes: ^14:13
NobodyCamgood morning Ironic14:15
dtantsurNobodyCam, o/14:15
NobodyCammornign dtantsur14:16
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: Use metadata.create_all() to get database schema  https://review.openstack.org/10762914:17
openstackgerritVictor Sergeyev proposed a change to openstack/ironic: Add a test case for DB schema comparison  https://review.openstack.org/10762814:17
*** lazy_prince has joined #openstack-ironic14:19
*** lazy_prince has quit IRC14:19
*** lazy_prince has joined #openstack-ironic14:20
jrolllucasagomes: wondering if this is worth fixing in devstack, even... it's no longer a bug in devstack with that patch14:24
lucasagomesjroll, I think it does, fixing in the client requires a release of the client14:25
dtantsurbrb14:26
*** jgrimm has joined #openstack-ironic14:27
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add missing docstrings  https://review.openstack.org/10620214:30
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add methods to ipmitool driver  https://review.openstack.org/10036414:30
jrollwhee14:30
*** jdob has quit IRC14:31
*** jcoufal has quit IRC14:32
openstackgerritJim Rollenhagen proposed a change to openstack/ironic-specs: Add deploy driver for ironic-python-agent  https://review.openstack.org/9850614:37
jrolldtantsur: decided to just update, I'll ping you if there is objections :)14:37
*** jdob has joined #openstack-ironic14:38
*** rloo has joined #openstack-ironic14:40
jrollhey y'all, this spec covers things to fix a bug targeted for J2, can I have some eyes on it? :) https://review.openstack.org/#/c/102405/14:44
jrollrloo: updated https://review.openstack.org/106202 - thanks for the feedback14:45
jrollbrb14:45
rloojroll: thx, will look (at both maybe) in a few minutes.14:46
*** pcrews has joined #openstack-ironic14:46
jrollrloo: thanks, no rush :)14:46
rloojroll: ok, then I'll wait til next week :D (am only working a few hours and then off)14:47
*** malini2 has quit IRC14:49
yuriyzmorning/evening rloo one question in comment https://review.openstack.org/#/c/107092/3/ironic/drivers/base.py14:52
rloohi yuriyz (morning for me). I'm just replying to that :-)14:53
rlooyuriyz: just replied. let me know if you want to discuss. lucas and I have had quite a lot of discussion about a 'required' field.14:54
*** kpavel_ has joined #openstack-ironic14:55
NobodyCamif any would like to toss a +1 on a nova review https://review.openstack.org/#/c/10751114:56
yuriyzrloo your answer makes sence. 'required' is not suitable for all options variants.14:59
NobodyCamanyone know if any server then supermicro supports gracefully shut down over ipmi14:59
rlooyuriyz: that was Lucas' idea. I initially had 'required', and put the XofYproperties as required, then as optional, and both weren't quite right. So now nothing.15:00
*** foexle has quit IRC15:01
*** kpavel has quit IRC15:02
*** Alexei_987 has quit IRC15:02
*** derekh_ has quit IRC15:02
*** viktors has quit IRC15:02
*** ifarkas has quit IRC15:02
yuriyzNobodyCam, HP proliantutils for ILO (not ipmi) has press_pwr_btn() method15:06
*** derekh_ has joined #openstack-ironic15:07
*** Alexei_987 has joined #openstack-ironic15:07
*** ifarkas has joined #openstack-ironic15:07
*** ifarkas has quit IRC15:07
*** ifarkas has joined #openstack-ironic15:07
*** 18VAAEB97 has joined #openstack-ironic15:07
*** viktors has joined #openstack-ironic15:08
*** ramineni has quit IRC15:10
NobodyCamalso looks like ipmitool has power soft support15:10
*** kpavel_ has quit IRC15:13
*** mdorman has joined #openstack-ironic15:23
NobodyCambrb15:27
*** rakesh_hs has quit IRC15:28
*** matty_dubs is now known as matty_dubs|lunch15:29
*** viktors is now known as viktors|afk15:31
*** mdorman has quit IRC15:34
*** mdorman has joined #openstack-ironic15:34
*** jcoufal has joined #openstack-ironic15:38
*** 18VAAEB97 has quit IRC15:44
*** ifarkas has quit IRC15:47
*** krtaylor has quit IRC15:57
*** lazy_prince is now known as killer_prince15:57
*** jcoufal has quit IRC15:59
*** jistr has quit IRC16:01
*** hemna has joined #openstack-ironic16:02
*** ramineni has joined #openstack-ironic16:06
*** jcoufal has joined #openstack-ironic16:08
jrollrloo: noooo, today please :(16:08
rloojroll: take a look at my latest comment then.16:08
*** ramineni has quit IRC16:10
jrollrloo: checking in from the train atm, will look when I get to the office, thanks16:11
rloojroll: ha ha.16:11
*** malini1 has joined #openstack-ironic16:21
*** bvivek has joined #openstack-ironic16:23
*** mkerrin has quit IRC16:24
*** Mikhail_D_wk has quit IRC16:28
*** Mikhail_D_wk has joined #openstack-ironic16:28
lucasagomesaight folks I'll have to go now, came to the office today16:29
lucasagomesgotta get the train back home16:29
lucasagomeshave a good night everyone16:29
*** lucasagomes has quit IRC16:30
*** christop1eraedo is now known as christopheraedo16:34
romchegg'night Lucas!16:34
NobodyCamnight lucas16:35
*** Poornima has joined #openstack-ironic16:36
*** krtaylor has joined #openstack-ironic16:42
*** rameshg87 has joined #openstack-ironic16:43
*** derekh_ has quit IRC16:49
*** rwsu has joined #openstack-ironic16:55
dtantsurjroll, aha, cool, thanks!17:02
devanandamorning, all17:05
* devananda tries to catch up on all the scrollback17:07
dtantsurdevananda, morning :)17:09
*** Alexei_987 has quit IRC17:09
dtantsurjroll, +2 from me :)17:09
*** hemna has quit IRC17:11
NobodyCamgood morning devananda17:12
devanandadtantsur: it's probably a question for the oslo.db team -- why are certain ALTERs not supported/testable on sqlite?17:13
devanandadtantsur: we should switch to oslo.db soon. the patch is up, and in my review queue. if that doesn't support sqlite, it's a much bigger problem than just Ironic17:14
devanandadtantsur: and if it does, then great. no reason for us to not support it17:14
dtantsurdevananda, yeah... maybe someone just should implement them :) ok, let us see. viktors|afk's feature to create the whole base w/o migrations still looks promising to me17:15
devanandadtantsur: the oslo.db migration code is done, afaik. GheRivero and viktors proposed it. just needs review17:15
devanandadtantsur: i blocked it a month ago due to a bug i found in it. i need to confirm that it's fixed17:16
devanandaother than that, it LGTM17:16
dtantsurok17:16
*** Nisha has joined #openstack-ironic17:16
*** Poornima has quit IRC17:17
* devananda has read scrollback up to T-7hrs ... wow, lots of discussions last night!17:18
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Raise appropriate errors on duplicate Node, Port and Chassis creation  https://review.openstack.org/10250617:18
jrolldtantsur: sweet :)17:19
jrollthank you!17:19
*** harlowja_away is now known as harlowja17:20
dtantsurnp)17:20
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix leaking DB details to API on error  https://review.openstack.org/7312117:21
jrollmorning devananda17:23
devanandaromcheg: "a way to force IPMI credentials from inside the server" -- would be a huge breach of security IF it's possible17:23
openstackgerritChris Krelle proposed a change to openstack/ironic: Add option to allow soft power off  https://review.openstack.org/10777817:25
rloojroll: gonna take off now. I'll try to check in later today to see if you've updated that docstring review. (and you too dtantsur wrt 102506)17:26
NobodyCamhave a good night rloo17:26
jrollrloo: gah, just got in17:27
devanandaShrews: any change to requriements.txt must match global-reqs, or it fails gate17:27
jrollrloo: have a good weekend :) don't worry about me17:27
dtantsurg'night, rloo17:27
devanandajroll: i'm sad that you allow things not in global-req into IPA. very sad.17:27
Shrewsdevananda: ah. yeah, i was wondering if there was a gotcha.17:27
jrollrloo: oh, do you have a sec?17:27
rloobye. not night yet for me. yay! :-)17:27
rloojroll: 2 secs ;)17:27
jrolldevananda: no... we require a later pecan version than global-req17:28
jrollrloo: I removed them because it's encompassed by "invalid parameters"17:28
devanandajroll: so update global-req17:28
jrollrloo: maybe I'm wrong in the first one, because validate() checks that, but vendor_passthru doesn't raise the exception directly so I think it's fine17:28
* devananda is finally caught up on scrollback17:29
rloojroll: hmm. let me think about it on my ride home. i think other methods do mention those extra invalidates too.17:29
jrolldevananda: it's for a better test fixture thing, it was unclear to me that would be a valid reason for infra17:29
jrollrloo: ok, I can take another look too. thanks17:29
rloojroll: later. ciao.17:30
*** hemna has joined #openstack-ironic17:30
*** rloo has quit IRC17:30
*** chuckC has quit IRC17:30
devanandajroll: hm. I dunno. usually "project X needs min version Y" is good enough17:30
jroll10:27:09       devananda | Shrews: any change to requriements.txt must match global-reqs, or it fails gate <- also, what checks this, I'm not sure that's true17:30
devanandajroll: it's not true for IPA because ya'll aren't running the right checks17:30
devananda*if17:31
devananda*then17:31
jrollright17:31
jrollso what checks it17:31
jrollbecause we run pep817:31
jrollI would assume it would be there17:31
jrollbut I'm usually wrong17:31
romchegdevananda: Good morning17:32
romchegdevananda: I suspected that17:32
devanandajroll: oh. Ironic isn't running it either. Gah.17:34
devanandajroll: "gate-***-requirements"17:34
devanandait's a separate jenkins job17:34
jrolldevananda: heh17:34
jrollI find this failure hilarious, on an "update requirements.txt" review in IPA:17:36
jroll2014-07-12 23:04:20.971 |   Could not find a version that satisfies the requirement oslo.config>=1.4.0.0a2 (from -r /tmp/ironic-python-agent/requirements.txt (line 8)) (from versions: )17:37
devanandajroll: taht the result of a network / pip failure?17:37
jrollunclear, it's in multiple jobs17:38
jrollI'm going to recheck... once this merges: https://review.openstack.org/#/c/107780/17:38
jroll(bump global pecan17:38
jroll)17:38
devanandaok, i think something's wrong with ironic's jenkins config17:39
devanandaor i'm just braindead right now17:39
devanandaShrews: around?17:39
Shrewsdevananda: aye17:39
devanandaShrews: have a minute to look at infra config and tell me if i'm crazy?17:39
Shrewsdevananda: i can make a minute. what do you want me to look at?17:40
devanandapick any recent patch to ironic -- i'm looking at https://review.openstack.org/#/c/107214/17:40
devanandaactually, lemme move to -infra in case they know17:40
Shrewsk17:40
Shrewsthough they're all in germany so unlikely to be responsive17:41
devanandaah, right17:41
devanandastaying here then17:41
devanandaso i'm looking at a random recent patch in ironic, and wondering why i see "gate-*" jobs running for an initial check17:41
openstackgerritChris Krelle proposed a change to openstack/ironic: Add option to allow soft power off  https://review.openstack.org/10777817:41
devanandaand i just noticed that's also the case for nova17:41
devanandaso it's not just us17:41
JayFdevananda: it looks like they merged gate/check jobs where there is no difference17:42
JayFdevananda: config file looked that way to me when I added the IPA builder17:42
devanandahuh17:42
devanandaok. i'm just behind the times17:42
JayFdevananda: i.e. where 'gate' jobs that don't differ from 'check' jobs are just left as the same job and named gate-17:42
devanandaso real question then is, why http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/zuul/layout.yaml#n980 isn't running17:43
JayFinteresting, I don't know. I know that job isn't setup for IPA though17:44
devanandaeg, looking at a recent patch https://review.openstack.org/#/c/107214/17:44
devanandathere's no gate-ironic-requirements17:44
Shrewshrm, *that* is a good question17:44
jrollodd17:45
Shrewsdoesn't run for other projects, it seems. e.g., cinder17:45
*** pelix has quit IRC17:45
jrollmaybe it just isn't posting back status?17:45
openstackgerritA change was merged to openstack/ironic: ManagementInterface {set, get}_boot_device() to support 'persistent'  https://review.openstack.org/10575717:45
jrolllike, the job could be broken17:45
devanandait runs for nova17:46
NobodyCambrb quick walkies17:46
Shrewsdevananda: does it? don't see it here: https://review.openstack.org/10695217:48
Shrewsoh17:49
Shrewsi know17:49
*** malini1 has quit IRC17:49
Shrewsit only runs if there is a change to requirements.txt17:49
jrolloh heh17:49
jrollnice :)17:49
Shrewsdevananda: https://review.openstack.org/107710, for example17:49
Shrewsi borked it  :)17:49
* Shrews WIP's that change until his global-requirements.txt change merges17:51
*** vinbs has joined #openstack-ironic17:57
*** jcoufal has quit IRC17:58
*** malini1 has joined #openstack-ironic17:59
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Raise appropriate errors on duplicate Node, Port and Chassis creation  https://review.openstack.org/10250618:01
*** wanyen has joined #openstack-ironic18:01
wanyenramesh87: hi18:02
*** vinbs_ has joined #openstack-ironic18:02
rameshg87hi wanyen18:02
rameshg87hello devananda18:03
wanyen Deva and liefless are you there?18:03
wanyens/lief/lifeless18:03
*** vinbs has quit IRC18:04
*** vinbs_ is now known as vinbs18:04
wanyenDeva, we would like ot discuss liefeless review commetns regarding iLO deploy driver18:04
wanyenlifeless requests ilo deploy driver to support conductor deploy over iscsi18:06
rameshg87dtantsur: request you to have a look at https://review.openstack.org/#/c/89500/ . we have addressed your comments.18:07
*** vinbs has quit IRC18:08
jrollwanyen: I don't see that comment on the review?18:09
devanandawanyen: i'm waiting for another meeting to resume. have a few minutes18:09
ShrewsSo, I wonder if we should be requiring all new API calls to be asynchronous? There is a spec to change all current synchronous calls to async (in K), but should we change the way we design new calls?18:09
devanandawanyen: i read the discussion rameshg87 and lifeless had here in channel, and the internal emails18:09
dtantsurrameshg87, sure, but tomorrow, it 8pm and I'm nearly leaving :)18:09
devanandawanyen: I think his points are valid18:09
wanyenwe can add iLO deploy over iscsi as a seperate spec but I think it should not be a blocking factor for current spec18:09
*** chuckC has joined #openstack-ironic18:10
devanandawanyen: duplciating most of the deploy logic of IPA or PXE drivers is going to add a burden to the code taht is unnecessary18:10
devanandawanyen: my impression from the spec was that taht wasn't being proposd, but clearly I didn't read it thoroughly enough18:10
dtantsurg'night folks, going now18:10
devanandawanyen: using the virtual media channel to load (a slightly modified form of) the current ramdisk should be totally sufficient18:10
wanyenDeva> cusotmer willeither choose iPA or iLO driver so iLO need to be able to support bm  deploy over swift as well18:11
rameshg87dtantsur: goodnight, thanks, will wait for your review :-)18:11
*** dtantsur is now known as dtantsur|afk18:11
devanandawanyen: iPA can be used instead of tftp to load the deploy ramdisk and keys18:11
devanandawanyen: * iLO can be used ...18:11
jrollwanyen: what was discussed this morning is separating deploy mechanisms from boot mechanisms, and combining the two for a driver18:12
jrollwanyen: so iLO can boot a deploy ramdisk, to be used with iscsi or IPA18:13
wanyenDeva> I don't understand why because IPA does BM deploy then iLO driver cannot do it because some customers will want otuse iLO driver to provision Proliant server and they need to be able to do bm deploy over swift with iLO driver.18:13
rameshg87jroll: doesn't ipa have the same problem with issues - with low memory systems and unsure if it scales better than current iscsi-dd solution18:16
rameshg87jroll: is ipa planning to support iscsi deployment requesting the conductor to do it ?18:17
jrollwat18:17
jrollso18:17
rameshg87jroll: just a question :-)18:17
jrollthe proposal is that we should separate boot mechanisms and deploy mechanisms18:17
*** tatyana has joined #openstack-ironic18:18
jrollso boot mechanisms will include: pxe/tftp, iLO, ??18:18
rameshg87jroll: yeah, my question was just a general question18:18
jrolldeploy mechanisms will include: iscsi, ipa, ??18:18
jrollrameshg87: right, so18:18
rameshg87jroll: i thought ipa had a boot mechanism too which is superior to pxe.18:18
jroll1) maybe has issues with low memory systems. I believe it scales better than iscsi for *my use case*18:18
jroll2) hell no IPA will not support iscsi18:19
jrollwe use ipxe at rackspace18:19
rameshg87jroll: okay. :-)18:19
jrollthe upstream driver will use pxe/tftp, initially18:19
rameshg87jroll: oh okay.18:19
jrollhope that helps :)18:20
wanyenmy point is that iLO driver should be able to do both iscsi and swift.bm deploy.  I tshould not be limited to do just iscsi.18:20
jrollrameshg87, wanyen, I think using iLO to boot a deploy ramdisk that works with iscsi or IPA deploy driver is a great idea, FWIW18:20
jrollwanyen: agreed18:20
jrollwanyen: so if I understand correctly, this morning people proposed: v1 of ilo deploy driver subclasses the pxe driver. v2 relies on splitting up DeployInterface and BootInterface, where iLO is a BootInterface, and can be mixed with IPA or iscsi DeployInterface18:22
*** jcoufal has joined #openstack-ironic18:22
devanandawanyen: yes, using iLO virtual media channel to (securely) load the deploy agent (whether that is IPA or DIB/deploy-ironic or something else) is very important18:22
jrollfor example, rackspace probably has some HP servers. I want to use IPA to deploy images to those servers :)18:23
jrollbut I also want to do it as securely as possible, which this iLO driver can help me do :)18:23
devanandawanyen: as that out of band channel is the only secure means to load cryptographic data to a preboot environment to populate a TPM18:23
devanandajroll: ^ :)18:23
jroll\o/18:23
jroll<3 secure software18:23
devanandajroll: i had a great conversation with some folks from Intel and the NSA yesterday about this sort of thing18:24
wanyendeva and jroll, I am glad to hear that  ilo vm driver can be useful for IPA but it will require investigation so we can do it as incremental feature18:24
devanandaalso, i sort of feel dirty talking to NSA folks, but they're nic18:24
devanandanice18:25
devanandawanyen: lifeless and I recommended this incremental approach during the last cycle18:25
devanandabefore atlanta summit18:25
wanyenFor the time being, we would like to be availale to do iLO driver with bm  delpoy over swift and vm+ iscsi18:26
wanyens/available/able18:26
devanandawanyen: what is "over swift and vm+iscsi" ?18:27
devanandawanyen: that sounds like using the iLO to load the current ironic initramdisk and using the PXE deploy driver to copy the image over iSCSI18:27
wanyenI mean to do able to do provisioning on teh bm node using swift tempURL and be able to do provisionin gfrom conductor over iscsi18:27
wanyens/do/be18:27
devanandawanyen: you are proposing two different implementations?18:28
devanandawat?18:28
devanandawanyen: "provisioning from conductor over iscsi" ==> this is what the PXE deploy driver does today. so what are you proposing here?18:28
jrolldevananda: yeah, that's what you said... would love to hear more :)18:28
wanyenAgain, we can do this incrementally, bm/swift first or iscsi first18:28
devanandawanyen: just using iLO to load the deploy ramdisk on the node, then letting the PXE deploy driver to the rest?18:29
jroll^^18:29
jrollso much this18:29
devanandaI think that was discussed in IRC already18:29
devanandait would take some refactoring, but that's fine18:29
devanandathe actual new code would be VERY small18:29
devanandawanyen: that ^ seems totally fine. I'm pretty sure it's exactly what lifeless already suggested to you18:29
rameshg87devananda: yeah. vmedia+iscsi = add code to boot from virtual media  + refactored code from current pxe driver.18:30
devanandarameshg87: ++18:30
jrollor even subclass the pxe driver?18:30
jrollnot sure if that would be better or worst18:30
devanandajroll: i think it'll be a refactoring, fwiw18:30
jrollI selfishly would love for someone to factor out all of the pxe things :)18:30
devanandapossibly creating a base class taht pxe and ilo inherit from.18:30
jrollalthough this is probably the opposite way18:30
jrollfactoring out the iscsi things18:31
devanandajroll: IPA wants to use many of them too, right?18:31
wanyenwe have customers who don't want to use pxe18:31
jrollwe want to use pxe/tfto things yes18:31
wanyenso want to make iLO driver pxe-less18:31
devanandawanyen: we know18:31
devanandawanyen: taht's EXACTLY what we're suggesting to you18:31
jrollwanyen: share the iscsi parts and none of the pxe/tftp parts :)18:32
wanyenjroll: that's fine but don't block us to do bm node deploy + swift18:32
jrollnobody is blocking you on that18:33
jrollor, wait. maybe18:33
devanandasure we are18:33
jrollyeah18:33
wanyenlifeless is blocking that18:33
devanandathe swift tempurl code is ALREADY blocked18:33
jrolldevananda: nop18:33
devanandait is needed for IPA18:33
devanandajroll: oh? when i looked yesterday it was blocked18:33
jrolltemp url spec landed18:33
devanandajroll: right - but the impl is blocked on swiftclient18:33
devanandaso i bumped the BP to J318:34
jrolloh, right18:34
JoshNangwhich reminds me, i need to go poke people in -swift to get that approved again18:34
jroll+118:34
jrollJoshNang: +900018:34
devanandaJoshNang: ++18:34
devanandaon another topic18:35
devanandawe srsly need the nova baremetal -> ironic migration work that romcheg is working on18:35
wanyendeva> I just want to make sure once we modify our spec to reflect the suggestion, our spec can get reviewed quickly and still target for Juno18:35
devanandaand we need grenade testing of it18:35
devanandaand we need it soon18:35
devanandabecause it is looking like nova won't accept the driver without an already-tested migration path18:36
devanandathe promise of implementing one later is not sufficient18:36
jrollwanyen: your spec is high priority for juno, it will get reviewed18:36
devanandaand we do not have grenade tests yet18:36
jrolldevananda: I'm out of tables to flip :(18:36
devanandajroll: so am I18:36
devanandaI fondly remember the days when I had tiem to write code ....18:37
*** matty_dubs|lunch is now known as matty_dubs18:37
jrolldo we have a recent status update from romcheg ?18:37
jrollor any progress?18:37
jrolletc18:37
wanyenjroll: thanks!  We need reivwers to review them quickly as it's already late in teh Juno cycle18:37
jrollwanyen: indeed18:37
jrollwanyen: /me checks list to make sure I'm not lying about priorities18:38
jrollwanyen: maybe I shouldn't say "high" priority, but it's on the list18:38
lifelessmorning18:39
lifelessdevananda: ahh welcome to my life :)18:40
wanyenramesh87: do you know what we need to do to modify the spec. ? I was not in irc discussion earlier this morning18:40
devanandajroll: see the whiteboard18:40
devanandajroll: there's two patches from romcheg. i haven't had time to test. tldr, we need grenade to test them18:40
rameshg87wanyen: i think i have discussed with lifeless and lucasagomes earlier today18:40
jrollwanyen: http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2014-07-17.log18:41
rameshg87wanyen: what can be done for vmedia+iscsi is clear18:41
wanyenlifeless, we have discussed iLo deploy driver  with Deva and Jroll18:41
wanyenwe are okay to do vm+ iscsi but we don't think we should be block to do bm deploy over swift as we have customers who want to use iLO driver to deploy prolisnt servers and they need to be able to bm deploy over swift18:43
*** bvivek has quit IRC18:43
wanyens/prolsnt/proliant18:43
devanandawanyen: "they need to be able to bm deploy over swift" why?18:45
jrollwanyen: what deploy ramdisk will you use to deploy over swift?18:45
devanandawanyen: what prevents those customers from using iSCSI?18:46
wanyendeva> it's the choice of customer pending on their deploy environment.18:46
devanandawanyen: why would they choose swift over iscsi?18:47
wanyenjroll: we already developed a ramdisk to do bm deploy over swift18:47
jroll>.>18:47
rameshg87jroll: it will use a deploy ramdisk with deploy-ironic element.  changes to deploy-ironic for this were also proposed in the same spec.18:47
jrollok18:47
devanandarameshg87: is the change for deploy-ironic proposed to DIB?18:48
rameshg87devananda: if you remember we had 2 specs initially - one in ironic and one in tripleo, and both were merged together18:48
wanyendeva>  I thought at one point ironic is in favor of doing deployment on bm node because it was believed to be more scalabe.  I think it's pending on customer's environment.18:48
devanandarameshg87: yes. but there is still code change needed in both projects18:48
wanyens/is/was18:49
devanandarameshg87: is the CODE change proposed to diskimage-builder yet?18:49
jrollmy question is... what's the problem with a separate spec for the swift things? remove all references to swift from this spec, push it through, put up a different spec for swift + ilo18:49
rameshg87devananda: ah okay. no code change is not proposed to diskimage-builder yet18:49
devanandawanyen: yes. IPA is doing that18:49
devananda(and more)18:49
devanandawanyen: i think the concern is bloating the diskimage-builder/deploy-ironic code, which is in bash and harder to debug/maintain18:50
devanandawanyen: and thus duplicating functionality, increasing complexity, and making life harder for the core team18:50
devanandawanyen: when IPA is already proposing to cover that requirement18:50
jrolllet me write code for you :)18:50
devanandawhy should we have two implementations?18:50
devanandarameshg87: this may be a case where seeing that code change will help clarify things18:51
devanandarameshg87: if you already have it working internally, please propose it to DIB18:51
devanandarameshg87: so we can all see how complex it is. maybe it's trivially simple and that might change opinions18:52
wanyendeva> as I said, customer will either use iLo driver or IPA driver to  deploy a ProLaint server.  So, when customers choose iLO driver to do the deploy, they need to be able to do bm deploy with swift if that's what they desire.18:52
devanandawanyen: that does not make sense18:52
devanandawanyen: see the whole conversation we jsut had about using iLO with either iSCSI or IPA18:52
devanandaI need to get lunch now, then catch a train. bbi2hr18:53
jrollwanyen: if I'm deploying an HP server with IPA, I *want* to use iLO to put the IPA image on that server18:53
wanyendeva and jroll: yes.  I got that part.  However, a customer may just wan to use iLO driver to do deploy as well as OOB firmware update, fimrware setting.,,,etc, so they will just use iLO driver but not iLO driver and IPA driver together.18:54
jrollwanyen: I still think that would be possible... I would assume firmware update etc would be part of the ManagementInterface18:55
jrollwanyen: these are features that don't exist, you can't use them to justify duplicating functionality18:55
NobodyCambrb18:57
wanyenjroll> we have sumbitted design specs for these features with the proposed managemetn interface18:57
jrollI understand that18:57
jrollI still don't think "deploying via swift" should be in this spec18:58
*** rloo has joined #openstack-ironic18:58
jrollthis spec should be about "putting the pxe driver's deploy ramdisk onto a node via ilo virtual media"18:59
wanyenjroll: why only limit deplyin gvia swift to IPA? That's teh part I don't underastand because some users may not use IPA and will use iLO driver only.18:59
jrollthat's not what I'm saying19:00
jrollthat should be in a different spec19:00
jrollI don't foresee ilo deploy driver *AND* ilo deploy via swift landing in juno19:00
jrolland if those are the same spec... I don't see those landing in juno19:00
*** Nisha has quit IRC19:00
jrollbut that's just my opinion19:00
wanyenjroll: that was our current iLo virtual deploy spec to do deploying over swift. Now you folks are sugfgesting something different and I think it should be a differnt spec but it should not block our current spec.19:01
NobodyCambrb19:02
wanyenjroll: our current iLO virutal deploy spec of deploying over swift has approved by deva.19:02
lifelessit has a +2, its not fully approved19:03
wanyenokay. my mistake to use the appooved tearm19:03
rloojroll: wrt 106202, take a look at the docstring in ipminative.py: https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ipminative.py#L30719:03
lifelessjroll: booting IPA via virtualmedia makes sense too, right ?19:04
jrollrloo: right... it doesn't mention "invalid IPMI parameters"19:04
jrollrloo: I can be more specific, will fix later19:04
jrolllifeless: I wouldn't deploy an HP server any other way :)19:04
lifelessjroll: as in boot mechanism is orthogonal to deploy logic is [mostly] orthogonal to BMC type19:04
jrolllifeless: yes, totally agree with separating boot management from deploy management19:05
lifelessthought so but worth checking :)19:05
rloojoll: it mentions 'or required ipmi credentials are missing' -- that's from the _parse_driver_info. and the 'invalid boot device is specified' is from the validate() code.19:05
jrollrloo: right... I mentioned the specific parameters before19:06
jrollrloo: I'll update, please hold19:06
*** Nisha has joined #openstack-ironic19:06
jrolllifeless: I wouldn't block the ilo deploy spec on that separation... as that would likely be k cycle. but I agree that it should focus on putting the existing deploy ramdisk on a server. securely.19:07
lifelessjroll: right, not suggesting we block it19:09
jrollright19:09
wanyenThe iLo deploy spec is targeting for juno.19:10
jrollwanyen seems to think you're trying to block it19:10
lifelessjroll: my suggestion was to make it a sibling of pxe; pull up the 99% common code into a base class and have only the boot logic differences in the pxe or virtualmedia classes19:10
jrolllifeless: + a million19:10
lifelessjroll: which should make for 2 tiny patch sets19:10
jrollyeah19:10
lifelessjroll: and preps us for the bigger thing later19:10
jrollI read this morning :)19:10
lifelesswanyen: what I don't understand is the pushback here; I'm actively trying to help you get an ilo virtualmedia driver in19:11
*** Nisha has quit IRC19:11
lifelesswanyen: but you seem to be arguing that you want to bring a much bigger thing in that has (IMO) nearly no chance of passing code review, because it will have such code structural issues19:12
jroll(albeit without swift support)19:12
lifelesssaying 'ilo virtualmedia driver with swift image-transfer support' makes my head hurt, because they aren't related at all19:12
lifelessthere will be swift needed for the virtual media hosting itself19:12
wanyenlifeless: It wasn't clear to me whether you suggest us to do just iscsi or we can do both iscsi and bm+swift.19:13
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add missing docstrings  https://review.openstack.org/10620219:13
jrollrloo: ^19:13
lifelesswanyen: just iscsi, because the swift aspect is where the problems in the spec are19:13
lifelesswanyen: swift-for-the-main-image-transfer, I mean19:14
JoshNangtempurls were just approved in swiftclient. woo!19:14
jrollJoshNang: siiiick19:14
jrollJoshNang: now to see if they'll release a new client, or if we need to pin to a hash, or what19:15
jrollI suspect pinning to a hash would not be advised19:15
lifelessyou'll need a new client19:15
lifelesspinning to a hash would be incompatible with global requirements19:15
jrollright19:15
jrollI assumed as such19:15
lifelessand changing global requirements to a hash would result in me jumping up and down and going 'you broke tripleo' :)19:16
wanyenI understand tha tIPA is using swift for deploy on bm but I don't understand why we limit this approach to just IPA because a custoemr can use iLo driver but not IPA driver.19:16
jrollJoshNang: get them to release, change global requirements, change ironic requirements19:16
lifelesswanyen: they are two independent drivers.19:16
JoshNangjroll: that's what i'm asking them for right now19:16
JoshNangyup, that's my plan19:16
lifelesswanyen: ilo(power-mgmt) and ilo(virtual-media) - neither have implication for image transfer19:16
wanyenlifeless: exactly.  So both need be able to do deploy on bm over swift19:16
lifelesswanyen: you want to add deploy-ramdisk-swift, which is fine, but its a totally different conversation19:17
lifelessneither need to be able to do swift19:17
jrollwanyen: we're not limiting you to IPA. we're asking that you limit this to iscsi for juno, and in k we can split the interfaces properly, and if you like you could write a deploy-ramdisk-swift DeployInterface19:17
jroll(or just use IPA because E_TOOMANYREASONS)19:17
lifelesswanyen: it feels to me like you really really really want this swift deploy driver - why? Its going to overlap with IPA in lots of way, and there doesn't seem to be a good reason to do that.19:18
lifelesswanyen: we're on the path to probably deprecating all non-IPA deploy codepaths at some point19:18
lifelesswanyen: (long way down the track, but I can see it happening - once we IPA in mainline, + get multicast into IPA so that it can handle low-memory situations as efficiently as iSCSI does)19:19
lifelesswanyen: whats *functionally different* about using swift to transfer the image vs iSCSI that matters to you?19:20
wanyenokay. we will submit a different spec for vm+iscsi and target it for Juno.  We will keep curent iLO deploy spec (the one with vm+bm deploy via swift) and try to land it in Juno if time permits.19:20
jroll.........19:20
lifelesswanyen: I doubt we'll reach consensus on the current spec19:21
*** tatyana_ has joined #openstack-ironic19:21
lifelesswanyen: since now the issues we have have been identified everyone thats discussed this has gone 'oh yeah, we have to fix the structure, doh'19:21
wanyenlifeless:  we just don't want to limit to iscsi and give users more choices if they feel bm deploy is more sutibale for htem19:21
*** tatyana has quit IRC19:21
*** tatyana_ is now known as tatyana19:21
lifelesswanyen: I want to give them more choice too, but pushing back against the clearly right road to do that is strange.19:22
wanyenlifeless: I am confused what's right what's wrong.  A few months back it was right now it's wrong...etc19:24
*** tatyana has quit IRC19:24
wanyenramesh87:  you got what you need for the next steps?19:25
lifelesswanyen: you know technical design - you learn more about the problem space as you go along19:26
lifelesswanyen: its why we plan and deliver in short cycles19:26
rameshg87wanyen: yes, i did.19:26
wanyenramesh87:  okay.19:27
wanyenfolks!  Thanks for the discussion.  Once we submit the spec as suggested by this discussion, we will announce in the chat room, please review the spec as quickly as you can.19:30
openstackgerritRuby Loo proposed a change to openstack/ironic: Add drivers.base.BaseDriver.get_properties()  https://review.openstack.org/10709219:33
openstackgerritRuby Loo proposed a change to openstack/ironic: Implement API to get driver properties  https://review.openstack.org/10709619:49
NobodyCambrb19:49
*** foexle has joined #openstack-ironic19:53
*** Nisha has joined #openstack-ironic20:04
*** hemna has quit IRC20:07
JayF iLO driver only.20:14
JayFsorry bad paste20:15
NobodyCamlifeless: fyi https://review.openstack.org/#/c/107511 landed20:15
jroll?20:15
jrolllol20:15
JayFI like clicking while reading too much :)20:15
*** ndipanov has quit IRC20:15
lifelessNobodyCam: wow, most excellent and fast20:18
NobodyCam:)20:21
romchegjroll: I'm back from the dinner now20:21
romchegjroll, devananda: I'm working on Grenade and trying to catch Sean to ask him a ton of questions :)20:22
*** hemna has joined #openstack-ironic20:24
*** Nisha has quit IRC20:25
*** jdob has quit IRC20:25
Shrewswow, i've never seen jenkins -2 a review before. am i that unobservant?20:38
*** malini1 has quit IRC20:40
Shrewsah, maybe just on verify20:40
*** malini has joined #openstack-ironic20:52
NobodyCamdevananda: gots a second for pluck you brain?21:00
devanandaNobodyCam: i'm on a train. and in the Nova meeting. go for it21:01
NobodyCamlol21:01
NobodyCamshort version is I need to trigger this: https://review.openstack.org/#/c/107778 only for rebuilds21:02
devanandaNobodyCam: so, why?21:04
devanandaNobodyCam: also, that shouldn't be a config option, which makes it global to the whole cluster, it should be per-power-cycle21:04
devanandaNobodyCam: also, why? soft-power can be ignored by the OS21:04
NobodyCamyea... that just a initial wip21:05
devanandathat's a totally different function. "inform the host's operating system that we intend to power it off, and ask it to do so nicely" vs "turn it off"21:05
NobodyCamthis was for rebuilds of things like mysql (or other db type applacations)  servers where hard power offs are bad21:05
devanandalifeless: this something tripleo needs for rebuilds?21:06
NobodyCamI got it vi Ng21:07
openstackgerritRamakrishnan G proposed a change to openstack/ironic-specs: iLO Virtual Media iSCSI Deploy Driver  https://review.openstack.org/9774421:07
devanandai would think what ever is orchestrating the rebuild should quiesce sensitive services first21:07
*** matty_dubs is now known as matty_dubs|gone21:07
NobodyCams/vi/via/21:07
devanandanot rely on that quiescense *during* the nova rebuild21:07
devanandaNg: hi!21:07
Nghi :)21:07
devanandaNobodyCam: I disagree that Ironic is the right the layer for quiesce of the guest21:07
lifelessdevananda: so, turned up when looking at things21:07
lifelessdevananda: I share your concern about layering21:07
lifelessdevananda: I mentioned just an hour ago to ng that perhaps heat is the right place21:08
lifelessdevananda: that said, I think ironic does need to know about soft vs hard off21:08
lifelessdevananda: because nova knows/is learning21:08
lifelessdevananda: (there's been some list discussion recently, didn't go all that far yet)21:08
lifelessI have to take C to kindy21:08
devanandalifeless: i agree that soft/hard power off awareness fits in ironic21:09
lifelessdevananda: but I'm fairly sure there will be (or should be) a bug on nova libvirt w.r.t. soft vs hard poweroffs21:09
devanandaand they're separate commands21:09
devanandas/command/function/21:09
rameshg87devananda, lifeless, NobodyCam, jroll, just posted a new design spec for the very recently discussed ilo driver with vmedia+iscsi. https://review.openstack.org/#/c/9774421:09
rameshg87devananda, lifeless, NobodyCam, jroll, please review it when you get time. thanks.21:10
jrolldevananda: can I set provision_state while registering a node, or will it throw a fit?21:10
lifelessdevananda: tl;dr - yes its needed, whatever the right design is is fine by me21:10
*** rameshg87 has left #openstack-ironic21:14
devanandajroll: you can not set provision state21:16
jrollboooo21:17
jrollwhere's that newly_registered flag? :P21:18
devanandajroll: for the upgrade from nova-bm, the plan is to stop ir-cond, write direct to the db, then start ir-cond21:21
*** chuckC has quit IRC21:22
jrolldevananda: right, I want to add a node via the API that drops directly into decom21:22
openstackgerritA change was merged to openstack/ironic: oslo.i18n migration  https://review.openstack.org/10513221:42
devanandalifeless: what's the status of nova.virt.baremetal testing in tripleo these days?21:44
*** mrda-away is now known as mrda21:48
mrdaMorning Ironic!21:48
NobodyCammorning mrda21:48
mrdaNobodyCam: \o21:48
mrdadevananda: Just FYI, I've had a request to rework the client authentication code and move it all into the ironicclient.  So I'll do that in the next few hours, get a patch up, and abandon the original ironic patch (102695).  The good news is that this removes this dependency from landing the Nova Ironic driver - at least in direct code imports.21:53
*** romcheg has quit IRC21:58
jrollmorning mrda22:00
mrdajroll: \o22:01
devanandamrda: i'm not sure that makes sense yet22:07
* devananda looks at the review22:07
mrdadevananda:  https://review.openstack.org/#/c/10269522:08
devananda" I've seen this exact antipattern with novaclient and heatclient"22:09
devanandaheh22:09
mrdadevananda: I think there's validity on the current approach, but there's also merit in the new proposed approach.22:11
lifelessdevananda: just calling it how I see it :)22:12
mrdadevananda: I'm happy to have both reviews up and ironic cores can decide which one they want22:12
devanandalifeless: so there's two things here22:12
mrdadevananda: but I am aware that we need to move on this today22:12
devanandawhich aren't really well separated in this review22:12
lifelessdevananda: we still run jobs on check using nova baremetal22:12
lifelessdevananda: we22:12
devanandalifeless: cool, thanks for the invo on taht22:12
devanandare 102695, tthis is adding both token caching and client caching22:13
devanandaeven if python-ironicclient cached the tokens, we would need the ClientCacher metaclass22:13
devanandato cache the client object itself22:13
lifelessdevananda: so client caching pattern does seem like its tied into nova22:14
lifelessdevananda: though a metaclass seems like a really weird implementation strategy22:14
lifelessdevananda: token caching is the thing I am concerned about22:14
devanandalifeless: metaclass seemed bettter here than a module object to me, anyway22:14
*** foexle has quit IRC22:15
mrdalifeless: btw, I did invite you to comment on the review, so I got what I asked for :)22:15
devanandaand it's a testable way to have a class-based singleton with guards around accessing / changing it22:15
devanandamrda: don't abandon this patch -- we need the cleint caching22:16
mrdadevananda: so I'm not sure how we could seperate token and client caching.22:16
lifelessdevananda: mrda: you should look at nova/network/neutronv2/__init__.py which is the neutron API client caching strategy22:16
lifelessno metaclass22:16
mrdai.e. what conditions would cause a client cache refresh if not token expiry?22:16
devanandaoh22:16
lifelessin particular there's thread safety concerns22:17
devanandamrda: i think the point is, the ironic_client.get_client call is generating both a new client AND a new token22:17
lifelesswhich I haven't expressed in the current review22:17
devanandamoving the "the token is invalid, fetch a new one" logic into the client itself22:17
devanandawould mean we only create one ironic_client object, at service startup22:17
NobodyCambr22:18
NobodyCambrb22:18
mrdaright so ironcclient.get_client gets a client object, that object would check token internally and refresh as needed.22:19
mrdathe current ironic_client_wrapper code would remain, save for the refreshing part which would disappear22:19
mrdai.e. _cli would remain once set22:19
devanandamrda: has_token_expired also goes away22:19
mrda(....and associated fixings :)22:20
*** chuckC has joined #openstack-ironic22:23
lifelessdevananda: https://review.openstack.org/#/c/104060/22:24
*** Haomeng has joined #openstack-ironic22:24
*** Haomeng|2 has quit IRC22:26
*** radsy has joined #openstack-ironic22:30
devananda\o/22:33
*** malini has quit IRC22:37
*** malini has joined #openstack-ironic22:42
NobodyCambrb... quick walkies22:44
*** Haomeng has quit IRC22:50
*** Haomeng has joined #openstack-ironic22:50
*** wanyen has quit IRC22:50
*** wanyen has joined #openstack-ironic22:51
*** radsy has quit IRC22:51
*** pcrews has quit IRC22:51
*** ekarlso has quit IRC22:51
*** pradipta_away has quit IRC22:51
*** GheRivero has quit IRC22:51
*** zer0c00l has quit IRC22:51
*** boris-42 has quit IRC22:51
*** chuckC has quit IRC22:52
*** pquerna has quit IRC22:52
*** BadCub has quit IRC22:52
*** kevinbenton has quit IRC22:52
*** yuriyz has quit IRC22:52
*** gilliard has quit IRC22:52
*** coolsvap has quit IRC22:52
*** davidlenwell has quit IRC22:52
openstackgerritMichael Davies proposed a change to openstack/ironic: Review fixes from Nova scheduler reviews  https://review.openstack.org/10731622:52
*** chuckC has joined #openstack-ironic22:53
*** pquerna has joined #openstack-ironic22:53
*** BadCub has joined #openstack-ironic22:53
*** kevinbenton has joined #openstack-ironic22:53
*** yuriyz has joined #openstack-ironic22:53
*** gilliard has joined #openstack-ironic22:53
*** coolsvap has joined #openstack-ironic22:53
*** davidlenwell has joined #openstack-ironic22:53
*** radsy has joined #openstack-ironic22:53
*** pcrews has joined #openstack-ironic22:53
*** pradipta_away has joined #openstack-ironic22:53
*** boris-42 has joined #openstack-ironic22:53
*** ekarlso has joined #openstack-ironic22:53
*** GheRivero has joined #openstack-ironic22:53
*** zer0c00l has joined #openstack-ironic22:53
mrdaHey Ironic Reviewers: I'd appreciate getting some eyeballs on https://review.openstack.org/#/c/107316 - these are changes Nova reviewers are asking us to make before the Nova Ironic driver can land in their code.  (Once you approve I port the change into the Nova tree for their approval)22:53
*** mikal has quit IRC22:54
*** mikal has joined #openstack-ironic22:54
*** jrist has quit IRC22:54
*** lynxman has quit IRC22:54
*** pleia2 has quit IRC22:54
*** JayF has quit IRC22:54
*** soren has quit IRC22:54
*** stevebaker has quit IRC22:54
*** dtantsur|afk has quit IRC22:54
*** hemna_ has quit IRC22:54
*** zigo has quit IRC22:54
*** adam_g has quit IRC22:54
*** aignatov has quit IRC22:54
*** Isotopp has quit IRC22:54
*** aweeks has quit IRC22:54
*** mgagne has quit IRC22:54
*** enikanorov_ has quit IRC22:54
*** agordeev has quit IRC22:54
*** LiveOne has quit IRC22:54
*** comstud has quit IRC22:54
*** mmitchell has quit IRC22:55
*** morgabra has quit IRC22:55
*** tteggel has quit IRC22:55
*** keekz has quit IRC22:55
*** Ng has quit IRC22:55
*** chuckC has quit IRC22:55
*** jrist has joined #openstack-ironic22:55
*** lynxman has joined #openstack-ironic22:55
*** pleia2 has joined #openstack-ironic22:55
*** JayF has joined #openstack-ironic22:55
*** soren has joined #openstack-ironic22:55
*** stevebaker has joined #openstack-ironic22:55
*** dtantsur|afk has joined #openstack-ironic22:55
*** hemna_ has joined #openstack-ironic22:55
*** zigo has joined #openstack-ironic22:55
*** adam_g has joined #openstack-ironic22:55
*** aignatov has joined #openstack-ironic22:55
*** Isotopp has joined #openstack-ironic22:55
*** mgagne has joined #openstack-ironic22:55
*** aweeks has joined #openstack-ironic22:55
*** enikanorov_ has joined #openstack-ironic22:55
*** LiveOne has joined #openstack-ironic22:55
*** agordeev has joined #openstack-ironic22:55
*** comstud has joined #openstack-ironic22:55
*** mikal has left #openstack-ironic22:55
*** mikal has joined #openstack-ironic22:55
jrollmrda: why is baremetal_host_manager getting pulled in22:55
jrollactually, I'll read the comments22:56
jrollgotta run for a bit22:56
*** mmitchell has joined #openstack-ironic22:56
*** morgabra has joined #openstack-ironic22:56
*** tteggel has joined #openstack-ironic22:56
*** keekz has joined #openstack-ironic22:56
*** Ng has joined #openstack-ironic22:56
mrdajroll: thanks22:57
NobodyCammrda: py27 failed on the last version22:58
NobodyCamdoesn't look like its the patch thou22:59
mrdarecheck bug 1336161 :)23:00
mrdaLe sigh23:00
NobodyCamwait until its done23:00
mrdaNobodyCam: yup, need more patience :)23:00
NobodyCam:-p23:00
*** krtaylor has quit IRC23:02
*** chuckC has joined #openstack-ironic23:03
*** jgrimm has quit IRC23:10
*** malini has quit IRC23:13
*** zul has quit IRC23:17
openstackgerritMichael Davies proposed a change to openstack/ironic: Ironic nova driver to cache ironic client calls  https://review.openstack.org/10269523:23
*** zul has joined #openstack-ironic23:31
*** mdorman has quit IRC23:38

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