Tuesday, 2014-06-24

*** kylers has quit IRC00:01
*** lucas-dinner has quit IRC00:02
*** kylers has joined #openstack-ironic00:07
*** Penick has quit IRC00:14
*** matsuhashi has joined #openstack-ironic00:21
*** achanda has quit IRC00:22
*** achanda has joined #openstack-ironic00:24
*** eghobo has quit IRC00:26
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add ironic-python-agent deploy driver (DO NOT MERGE)  https://review.openstack.org/10102000:37
*** bandicot has joined #openstack-ironic01:00
*** eghobo has joined #openstack-ironic01:05
*** eghobo has joined #openstack-ironic01:05
*** ellenh has quit IRC01:09
*** yu_ has quit IRC01:15
*** bandicot has quit IRC01:16
*** kylers has quit IRC01:22
*** nosnos has joined #openstack-ironic01:44
*** eguz has joined #openstack-ironic01:46
*** eghobo has quit IRC01:50
*** eguz has quit IRC01:51
*** pcrews has quit IRC02:34
*** killer_prince is now known as lazy_prince02:42
*** lazy_prince is now known as killer_prince02:42
*** yfujioka has joined #openstack-ironic02:42
*** killer_prince is now known as lazy_prince02:43
*** lazy_prince is now known as killer_prince02:45
*** nosnos has quit IRC02:54
*** nosnos has joined #openstack-ironic02:54
*** nosnos has quit IRC02:59
*** nosnos has joined #openstack-ironic03:05
*** vinbs has joined #openstack-ironic03:06
*** matsuhashi has quit IRC03:18
*** matsuhashi has joined #openstack-ironic03:19
*** matsuhashi has quit IRC03:24
*** nosnos has quit IRC03:34
*** nosnos has joined #openstack-ironic03:35
*** rloo has quit IRC03:37
*** eghobo has joined #openstack-ironic03:38
*** nosnos has quit IRC03:39
*** saripurigopi has joined #openstack-ironic03:40
*** todd_dsm has joined #openstack-ironic03:52
vinbsMorning Ironic! :)04:02
*** GheRivero has quit IRC04:04
*** davidlenwell_ has joined #openstack-ironic04:04
*** GheRivero has joined #openstack-ironic04:04
*** davidlenwell has quit IRC04:05
*** matsuhashi has joined #openstack-ironic04:10
*** nosnos has joined #openstack-ironic04:19
*** killer_prince is now known as lazy_prince04:24
*** todd_dsm has quit IRC04:37
*** lazy_prince has quit IRC04:41
*** rameshg87 has joined #openstack-ironic04:48
*** pcrews has joined #openstack-ironic04:49
*** rameshg87 has quit IRC04:55
*** rakesh_hs4 has joined #openstack-ironic04:57
Haomengvinbs: morning:)04:59
*** eghobo has quit IRC05:00
*** eghobo has joined #openstack-ironic05:01
*** bmahalakshmi has joined #openstack-ironic05:02
mrdaHi vinbs and Haomeng05:06
Haomengmrda: morning:)05:06
*** ajc_ has joined #openstack-ironic05:07
*** lazy_prince has joined #openstack-ironic05:09
*** achanda has quit IRC05:11
*** rameshg87 has joined #openstack-ironic05:12
*** achanda has joined #openstack-ironic05:19
*** k4n0 has joined #openstack-ironic05:21
*** lazy_prince is now known as killer_prince05:22
*** Nisha has joined #openstack-ironic05:28
*** amitpp has joined #openstack-ironic05:29
*** coolsvap|afk is now known as coolsvap05:35
*** rwsu has quit IRC05:41
*** Mikhail_D_ltp has joined #openstack-ironic05:54
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic: Imported Translations from Transifex  https://review.openstack.org/9606306:02
*** killer_prince is now known as lazy_prince06:15
*** harlowja is now known as harlowja_away06:20
*** kentaro_ has joined #openstack-ironic06:22
*** coolsvap is now known as coolsvap|afk06:24
*** k4n0 has quit IRC06:27
*** coolsvap|afk is now known as coolsvap06:28
*** k4n0 has joined #openstack-ironic06:39
*** Mikhail_D_ltp has quit IRC06:46
*** sysexit has joined #openstack-ironic06:51
*** ifarkas has joined #openstack-ironic06:53
*** eguz has joined #openstack-ironic06:59
*** yfujioka has quit IRC07:03
*** eghobo has quit IRC07:03
*** max_lobur has joined #openstack-ironic07:05
*** eguz has quit IRC07:05
*** openstackgerrit has quit IRC07:10
*** Nisha has quit IRC07:15
*** romcheg has joined #openstack-ironic07:16
*** max_lobur has quit IRC07:17
*** jcoufal has joined #openstack-ironic07:21
*** viktors|afk is now known as viktors07:30
*** Manishanker has joined #openstack-ironic07:38
*** achanda has quit IRC07:40
*** mrda is now known as mrda-away07:40
mrda-awayNight ironic...07:41
*** foexle has joined #openstack-ironic07:42
Haomengmrda-away: night:)07:45
comstudfor those awake...07:51
comstudhttps://review.openstack.org/#/c/89223/07:51
comstudneed one more +2 on that07:52
comstudwould be nice to land it before I have more conflicts in the tests07:52
romchegMorning all!07:52
comstud2 month old review :-/  although I did let it sit for a while.. and gate issues n all07:52
comstudoh, i guess it has 2 +2's now07:53
comstudjust need someone to approve07:53
comstudromcheg: hi and goodnight :)07:54
comstudbed time for me07:54
romchegBye comstud!07:54
* comstud & poof07:54
Haomengcomstud: :)08:06
Haomengcomstud: LGTM, +2 already:)08:07
*** Mikhail_D_ltp has joined #openstack-ironic08:09
*** petertoft has joined #openstack-ironic08:10
romchegOh, 3 +2s08:11
romchegI will approve it then08:11
*** amitpp has quit IRC08:12
*** yuriyz has joined #openstack-ironic08:18
*** dtantsur|afk is now known as dtantsur08:24
dtantsurMorning Ironic08:24
*** romcheg has quit IRC08:26
*** max_lobur has joined #openstack-ironic08:30
*** lucas-dinner has joined #openstack-ironic08:32
*** jcoufal has quit IRC08:33
*** jcoufal has joined #openstack-ironic08:34
*** athomas has joined #openstack-ironic08:34
foexleMorning dtantsur :)08:39
dtantsurfoexle, morning :)08:39
*** martyntaylor has joined #openstack-ironic08:42
*** martyntaylor has quit IRC08:46
dtantsurcore folks, please have a look at https://review.openstack.org/#/c/90126/08:48
dtantsur1x +2 already, should be relatively easy to review08:48
*** martyntaylor has joined #openstack-ironic08:50
*** romcheg has joined #openstack-ironic08:52
*** sysexit has quit IRC08:55
rameshg87good morning dtantsur,08:55
rameshg87dtantsur, need your input on this review https://review.openstack.org/#/c/100734/4/ironic/common/tftp.py08:55
rameshg87dtantsur, i feel image_cache can be moved to ironic.common with this review, what's your thought on that ?08:56
romchegg'morning dtantsur rameshg87 and everyone else!08:57
dtantsurrameshg87, morning :) 100% agree, left a comment08:57
dtantsurromcheg, morning as well :) want easy target to review/maybe approve? ;) https://review.openstack.org/#/c/90126/08:58
*** sysexit has joined #openstack-ironic08:58
* romcheg is looking08:59
romchegOh, that was the problem I raised :)08:59
rameshg87thanks dtantsur09:08
*** pelix has joined #openstack-ironic09:16
foexlehey guys, is there needed by Ironic to disable the neutron dhcp too? Like baremetal drivers ?09:32
romchegfoexle: there should be only one DHCP _in the baremetal network_ as far as I remember09:33
foexleromcheg: of course but => https://wiki.openstack.org/wiki/GeneralBareMetalProvisioningFramework#Services [..]"This means that you must disable neutron-dhcp"[..]09:35
foexleis that problem still exists ?09:36
*** Manishanker has quit IRC09:37
romchegfoexle: you can setup a separate network for that09:40
*** bmahalakshmi has quit IRC09:41
romchegа у меня не отменились :()09:41
dtantsur:)09:41
*** amitpp has joined #openstack-ironic09:41
romchegwhops, wrong window!09:41
romchegsorry09:41
dtantsurromcheg, now folks will suspect you of using especially dirty Russian words here :D09:42
yuriyzromcheg lol09:42
*** bmahalakshmi has joined #openstack-ironic09:43
yuriyzmorning all09:43
viktorsromcheg: why not ukrainian? )09:43
romchegviktors: I was about to write a message to a Russian team :)09:44
romchegdtantsur: I think the whole world now knows one dirty Russian word. It became popular in Western press about a week ago :)09:44
dtantsurLOL09:45
romcheghttp://www.theguardian.com/world/2014/jun/15/ukraine-minister-deshchytsia-abusive-putin-russia09:46
dtantsuryuriyz, morning09:46
*** openstackgerrit has joined #openstack-ironic09:47
*** dtantsur is now known as dtantsur|lunch09:50
*** romcheg has quit IRC10:02
*** sysexit has quit IRC10:04
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Do not delete pxe_deploy_{kernel, ramdisk} on tear down  https://review.openstack.org/10186410:06
*** athomas has quit IRC10:14
*** nosnos has quit IRC10:19
*** nosnos has joined #openstack-ironic10:19
*** athomas has joined #openstack-ironic10:23
*** matsuhashi has quit IRC10:23
*** matsuhashi has joined #openstack-ironic10:24
*** nosnos has quit IRC10:24
*** amitpp has quit IRC10:24
*** matsuhashi has quit IRC10:28
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Implement security groups and firewall filtering methods  https://review.openstack.org/9646610:30
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Add/Update docstrings in the Nova Ironic Driver  https://review.openstack.org/9753610:30
lucas-dinnermorning all :)10:32
*** lucas-dinner is now known as lucasagomes10:32
lucasagomestoo early for dinner :D10:32
openstackgerritRamakrishnan G proposed a change to openstack/ironic-specs: iLO Virtual Media Deploy Driver  https://review.openstack.org/9774410:40
*** sysexit has joined #openstack-ironic10:41
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Add the remaining unittests to the ClientWrapper class  https://review.openstack.org/9241610:53
*** sysexit has quit IRC10:54
*** romcheg has joined #openstack-ironic10:59
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Do not delete pxe_deploy_{kernel, ramdisk} on tear down  https://review.openstack.org/10186411:00
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Add set_on_error_hook to TaskManager  https://review.openstack.org/10095711:08
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Fix nodes left in an incosistent state if no workers  https://review.openstack.org/10095811:08
*** lucasagomes is now known as lucas-hungry11:19
*** bmahalakshmi has quit IRC11:26
*** coolsvap is now known as coolsvap|afk11:27
*** k4n0 has quit IRC11:28
*** bmahalakshmi has joined #openstack-ironic11:29
*** takadayuiko has joined #openstack-ironic11:43
*** bmahalakshmi has quit IRC11:43
*** bmahalakshmi has joined #openstack-ironic11:44
openstackgerritMike Heald proposed a change to openstack/ironic-python-agent: Converted documentation in md format to rst.  https://review.openstack.org/10219611:47
takadayuikoUsing Ironic succeed :D11:47
*** igordcard has joined #openstack-ironic11:53
*** saripurigopi has quit IRC11:58
*** rakesh_hs4 has quit IRC12:01
*** jdob has joined #openstack-ironic12:01
*** vinbs has quit IRC12:09
*** dtantsur|lunch is now known as dtantsur12:20
* Shrews waves good morning from behind his breakfast smoothie12:20
dtantsurShrews, morning :)12:20
*** bmahalakshmi has quit IRC12:21
*** lucas-hungry is now known as lucasagomes12:23
openstackgerritMike Heald proposed a change to openstack/ironic-python-agent: Converted documentation in md format to rst  https://review.openstack.org/10219612:24
rameshg87dtantsur, request you to take a look at these reviews: https://review.openstack.org/#/c/101765/ (bash completion support) and https://review.openstack.org/#/c/101297/ (vendor passthru support in cli) :-)12:25
rameshg87dtantsur, they are small but i think it will be useful12:26
dtantsurrameshg87, they're on my list, but I'm short of time for now, sorry :(12:26
rameshg87dtantsur, okay :-)12:27
dtantsurFolks, do we _ever_ change Node uuid after it was created? If not, I'm going to prevent this behavior on a DB level as part of DB exceptions clean-up12:30
dtantsurthe same question goes for Chassis. I see that for Ports we allow (implicitly) changing UUID, but that may be by chance12:32
dtantsurviktors, around? Maybe you know ^^^ ?12:38
Shrewsdtantsur: afaict, generate_uuid() is used to create the uuid, and that's only called when the node is created. so i think it's safe to say it never changes12:38
Shrewsand it doesn't make sense for it to change12:38
dtantsurShrews, I see, thank you. Maybe you know why we allow to change Port UUID?12:39
Shrewswe do?  :)  no idea12:39
viktorsdtantsur:  sorry, I'm not familiar with it12:39
dtantsurShrews, my bad, we don't :) And I'm going to explicitly forbid it in DB code12:42
dtantsurShrews, but we have a test on changing Chassis UUID Oo12:45
dtantsurromcheg, lucasagomes any ideas on all this ^^^ ?12:45
dtantsurI feel like preventing changing UUID's, as it may break a lot of things in an interesting fashion...12:45
romchegdtantsur: ++12:46
romchegBut please file a bug first12:46
dtantsurromcheg, sure :) and seem like I need a separate patch for this12:46
lucasagomesdtantsur, so it's possible right now, but idk if anybody uses it actually12:46
lucasagomesdtantsur, there's a bug opened for it? Also if you do, you also need to prevent it in the API https://github.com/openstack/ironic/blob/master/ironic/api/controllers/v1/node.py#L4812:48
lucasagomes(for nodes, chassis and ports)12:48
dtantsurlucasagomes, if I raise InvalidParamaterValue on db level, that would solve it for API level as well, right?12:48
romchegI also think that the appropriate changes to the docs should land first12:48
romchegSo no one would start using that12:49
lucasagomesdtantsur, it will, but the check for internal attributes might give a more useful error message12:49
lucasagomesromcheg, can't they land all together?!12:49
dtantsurlucasagomes, romcheg, I tested: API level explicitly forbid it, so problem is only internal12:50
lucasagomesif you update the docs first, and ppl try it and it works12:50
lucasagomesthat's incosistent as well12:50
romcheglucasagomes: agee12:50
*** ajc_ has quit IRC12:50
romchegagree even12:50
dtantsurhttps://bugs.launchpad.net/ironic/+bug/133368312:52
dtantsuryour opinion?12:52
Shrewsdtantsur: how will you enforce it at the db level?12:53
*** linggao has joined #openstack-ironic12:53
dtantsurShrews, raise error, if 'uuid' field is in 'value' dict12:53
Shrewsoh, i don't consider that "db level". that's more db api level12:54
*** rameshg87 has left #openstack-ironic12:58
*** rloo has joined #openstack-ironic12:58
*** sseago has quit IRC12:59
*** sseago_ has joined #openstack-ironic12:59
dtantsurShrews, fixed13:01
*** rloo has quit IRC13:02
Shrews++13:02
*** rloo has joined #openstack-ironic13:02
romchegdtantsur: I would make it shorter: DB-API allows changing UUID for Nodes, Chassis and Ports13:02
dtantsurromcheg, fixed, thnx13:07
*** lazy_prince has quit IRC13:13
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add ironic-python-agent deploy driver  https://review.openstack.org/10102013:18
*** sseago__ has joined #openstack-ironic13:20
*** sseago_ has quit IRC13:20
jrollmorning y'all13:20
jrollthe agent driver is ready to start accepting reviews... I think there's some tests missing but would love to get feedback anyway: https://review.openstack.org/#/c/101020/13:21
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix leaking DB details to API on error  https://review.openstack.org/7312113:25
dtantsurmorning, jroll13:25
romchegGood morning jroll!13:26
dtantsurgreat news \o/ will look13:26
romchegjroll: w00t!13:26
*** matty_dubs|gone is now known as matty_dubs13:30
*** Mikhail_D_ltp has quit IRC13:31
jrollmorning dtantsur and romcheg :)13:32
openstackgerritJim Rollenhagen proposed a change to openstack/ironic-specs: Add deploy driver for ironic-python-agent  https://review.openstack.org/9850613:43
jrolldtantsur, mrda-away: responded to and fixed your comments ^13:44
NobodyCamgood morning Ironic13:49
jrollmorning NobodyCam!13:49
openstackgerritJim Rollenhagen proposed a change to openstack/ironic-python-agent: Better errors for execute() failures  https://review.openstack.org/9966613:51
NobodyCammorning jroll13:51
jrolldtantsur: also finally fixed that nit on https://review.openstack.org/#/c/99666, pls to +2 :)13:51
romchegMorning NobodyCam!13:55
NobodyCammorning romcheg13:55
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Factor out TFTPImageCache  https://review.openstack.org/10073414:03
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Factor out deploy info from PXE driver  https://review.openstack.org/10073514:03
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add ironic-python-agent deploy driver  https://review.openstack.org/10102014:03
dtantsurNobodyCam, morning!14:03
dtantsurjroll, sure, will have a look14:03
jrollthanks :)14:03
NobodyCamgood morning dtantsur14:09
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix leaking DB details to API on error  https://review.openstack.org/7312114:11
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Prevent updating UUID of Node, Port and Chassis on DB API level  https://review.openstack.org/10224714:13
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Prevent updating UUID of Node, Port and Chassis on DB API level  https://review.openstack.org/10224714:15
*** killer_prince has joined #openstack-ironic14:33
NobodyCamhummmm corp travel site is saying the hotel is not approved14:33
NobodyCam:(14:33
jrolljust book outside of the system :)14:34
jrollwhat hotel is everyone staying at, anyway?14:34
matty_dubsI just got like 10 emails that Implement API to get driver properties cannot me merged14:34
matty_dubsThey are still coming14:34
*** jbjohnso has joined #openstack-ironic14:35
NobodyCamhttps://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint14:35
jrolloh, cool14:36
rloomatty_dubs: sorry and thx for the warning. All I did was -2 it. Ouch, more are showing up.14:36
jrollthanks :)14:36
jrollrloo: "all I did"14:36
matty_dubsrloo: Yeah, I'm not sure what's going on, but it's crazy. ;)14:36
matty_dubsrloo: That will teach you to -2 patches! ;)14:36
rloomatty_dubs: i wonder if i triggered some sort of bug.14:36
rloomatty_dubs: yeah, maybe I shouldn't -2 my own patches. I wonder if that was it. Or if it is cuz there is an X for work-in-progress.14:37
NobodyCammorning rloo :)14:37
rloomorning NobodyCam!14:37
NobodyCamand matty_dubs too14:37
matty_dubsMorning NobodyCam (et al.)14:37
romchegGuys, is Jenkins crazy right now or am I crazy right now?14:39
*** killer_prince has quit IRC14:40
rlooromcheg: It is just the one patch that Jenkins isn't happy with. I'm not sure why, but it started when I -2'd the patch.14:40
rlooromcheg: I just undid the -2. Hopefully that 'fixes' it. I'll just remember not to merge that patch ;)14:40
romchegrloo: Thanks!14:41
rlooromcheg: that's what you all get for not approving my patch in Icehouse :-(14:42
romchegrloo: I think it's better to talk to Infra guys14:42
rlooromcheg: ok.14:42
*** killer_prince has joined #openstack-ironic14:44
romchegI keep receiving emails14:44
matty_dubsMe too14:45
matty_dubsOn the bright side, I feel so popular now. ;)14:45
rlooromcheg, matty_dubs: sorry, I don't know how to stop it. I asked in infra, but not sure if anyone is there.14:45
romchegrloo: Don't blame yourself14:46
rlooromcheg, matty_dubs: let me know if you have any ideas. Can I delete a patch?14:46
romchegrloo: you can abandon it14:46
rlooromcheg: ok, I just abandon'd it. Lets see if that stops it.14:47
jrollthis is why I filter jenkins emails ;)14:47
romcheglooks like it helped14:48
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix leaking DB details to API on error  https://review.openstack.org/7312114:48
*** foexle has quit IRC14:48
matty_dubsYay!14:49
rlooromcheg, matty_dubs: yeah.14:49
matty_dubsHeh, Ctrl+D to delete the thread. mutt asks: "Purge 220 deleted messages? ([yes]/no)"14:51
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix leaking DB details to API on error  https://review.openstack.org/7312114:53
*** achanda has joined #openstack-ironic14:55
dtantsurok, folks, you succeeded in opening gates to hell :D14:58
rloodtantsur: ? which folks?14:59
dtantsurrloo, for example you :) I mean the infinite stream of Jenkins unhappyness15:00
rloodtantsur: ha ha. Sorry, only the people that had reviewed my patch are in the club -- that's what the gate opened ;)15:00
rloodtantsur: No worries. You only got 220 msgs. And who knows, maybe I've revealed a bug in infra!15:01
*** rloo has quit IRC15:03
*** rloo has joined #openstack-ironic15:04
*** mdorman has joined #openstack-ironic15:06
*** achanda has quit IRC15:06
*** rloo has quit IRC15:07
*** rloo has joined #openstack-ironic15:08
*** rloo has quit IRC15:08
*** rloo has joined #openstack-ironic15:09
*** jcoufal has quit IRC15:11
rloolucasagomes, jroll: wrt the instance_info attribute. Just reading the spec. It isn't clear to me. How do you set eg 'root_gb'? if i do a 'nova node-create  ... -i root_gb=10, it shows up in driver_info.15:21
jrollrloo: so uh, idk what the plans are to update the cli15:21
rloojroll: ok, will check with lucasagomes. I didn't read the spec before it was approved; seems like it should have been mentioned there15:22
jrollit may have been15:22
rloojroll: at some point, I think lucasagomes was thinking of writing specs against python-ironicclient so maybe it fell through this crack.15:23
jrollhmm15:24
jrollyeah, my memory is bad on this one15:24
rloojroll: no worries. your name was on the spec, so thought i'd ping you too :-)15:24
jrollno problem :)15:24
*** vinbs has joined #openstack-ironic15:25
lucasagomesrloo, it's part of the flavor15:25
rloolucasagomes: so are you saying that there's no API to set any of the instance_info?15:26
lucasagomesrloo, in case ur deploying a node w/o nova, you can set it -i instance_info/root_gb=1015:26
lucasagomesrloo, there's15:26
*** vinbs_ has joined #openstack-ironic15:26
lucasagomesrloo, but there's no change on that part, we are very flexible when it comes to update attributes in our resources15:26
lucasagomesrloo, we use json-patch15:27
rloolucasagomes: so if you do -i root_gb, it adds to driver_info? You have to specify 'instance_info/'?15:27
lucasagomes{'op': 'add', 'path': 'instance_info/root_gb', value='10} for e.g15:27
lucasagomesrloo, oh it goes to the driver info!?15:27
lucasagomesrloo, damn ok, so we might have to change the cli15:27
rloolucasagomes: if I just do -i root_gb.15:27
lucasagomesrloo, right it might be some logic in the cli then15:28
lucasagomes:(15:28
lucasagomesrloo, mind opnining a bug for it?15:28
NobodyCammorning lucasagomes15:28
lucasagomesNobodyCam, morning15:28
NobodyCam:)15:28
rloolucasagomes: no worries. i can open a bug. What do you think it should do? have to explicitly specify -i driver_info/xxx?15:28
rloolucasagomes: well, i'll just open a bug :-)15:29
lucasagomesrloo, yeah... you still can do a node-update <node> add instance_info/root_gb=1015:29
lucasagomesrloo, the -i is for node-create?15:29
rloolucasagomes: yeah, -i is for node-create15:29
lucasagomesright15:29
lucasagomesso hmmm should we pass instance_info when creating a node?15:29
*** vinbs has quit IRC15:30
lucasagomeswell perhaps we should allow you to create a node with all the values u already want15:30
rloolucasagomes: I don't see why we would restrict it so you can't?15:30
lucasagomesrloo, no15:30
lucasagomesu want already*15:30
lucasagomesjroll, you guys are using iPXE internally am I right?15:31
jrollyes sir15:31
lucasagomesjroll, lemme ask, u guys are not using neutron for dhcp right?15:31
jrollwith an external dhcp server15:31
jrollright15:31
jrollwe use isc-dhcp-server15:31
lucasagomesa-ha!15:31
*** rloo has quit IRC15:31
*** coolsvap|afk is now known as coolsvap15:31
lucasagomesjroll, right, yeah I was setting my env to do iPXE instead of gPXE15:31
jrolllucasagomes: did you see this? :) http://developer.rackspace.com/blog/how-we-run-ironic-and-you-can-too.html15:31
*** rloo has joined #openstack-ironic15:32
lucasagomesand as neutron uses dnsmasq, I will have to update neutron as part of the spec as well :(15:32
jrolllucasagomes: oh lord15:32
lucasagomesto make it add a ipxe tag for the dhcp15:32
*** max_lobur has quit IRC15:32
lucasagomes:(15:32
* lucasagomes feels sad15:32
jrollI'm so sorry15:32
jroll:P15:32
lucasagomesjroll, will check it out!15:32
NobodyCamlol I like step #415:32
lucasagomesjroll, and congrats on the onmetal! pretty cool man15:32
rloolucasagomes: don't be sad. be happy you noticed it now :-)15:32
jrolllucasagomes: I just got an email from your recruiters :P15:32
jrollha thanks, it's a journey :)15:32
*** vinbs_ has quit IRC15:33
lucasagomesjroll, hah come to the dark side15:33
lucasagomes:D15:33
jroll:P15:33
dtantsurlucasagomes, what do you think about having a generic spec covering what should be changed for discovery, no matter which ramdisk is used? If you don't have time, I can try (based on your etherpad).15:33
dtantsurjroll, interested for you as well ^^^15:34
jrollNobodyCam: heh, the bugs are usually, "uh oh, cherry-picking patches from gerrit failed loudly"15:34
jrolldtantsur: isn't that the point of Nisha's spec?15:34
NobodyCam:)15:34
* jroll still needs to review that15:34
lucasagomesdtantsur, hmm right, idk if that will be very well accepted upstream tho15:35
lucasagomesdtantsur, loads of insecurity15:35
jrollwell15:35
jrollI see it more of specifying the APIs etc15:35
dtantsurlucasagomes, I mean, generic one. With skipping details, that can't be solved now15:35
jrollprescribing that auth be done with something transferred out of band15:35
jrollthat kind of thing15:35
dtantsurjroll, Nisha's is about discovery on manual adding, I'm interested in auto-discovery. Of course there's a lot in common.15:36
jrolldtantsur: ah, yes15:36
lucasagomesdtantsur, right, well if u want to do the first stab15:37
jroll^15:37
* jroll helps lucas throw dtantsur under that bus :P15:37
dtantsurso nice of you, guys :)15:37
lucasagomesdtantsur, we can add multiple authors15:37
lucasagomesdtantsur, I can help a bit with the spec code as well15:38
lucasagomeslet's add jroll too15:38
lucasagomes:)15:38
jrollgah15:38
* jroll runs15:38
dtantsurlucasagomes, cool! My point is to create and approve some basis for all future discovery work15:38
jrollI'll help if I can15:38
lucasagomesdtantsur, right, let's start tossing those first on the etherpad15:38
dtantsurwe can try to agree on vendor endpoints/neutron/whatever15:38
lucasagomesdtantsur, +115:39
jrollsounds good to me15:43
jrollheading to the office, bbiab15:44
linggaoHi anteaya15:44
NobodyCammorning linggao15:45
linggaogood morning NobodyCam. Had your dose of coffee?15:46
NobodyCamoh ya :)15:46
*** viktors is now known as viktors|afk15:46
*** kylers has joined #openstack-ironic15:46
linggaoNobodyCam, we are setting up third party CI for Ironic to test ipminative driver.15:46
NobodyCamlinggao: w00t!!!115:47
anteayalinggao: hello15:47
NobodyCammorning anteaya :)15:47
linggaoanteaya, where do we find Ironic tempest scripts for Ironic?15:47
anteayamorning NobodyCam15:47
anteayalinggao: that is a good question for the -qa channel I do believe, if noone in ironic knows15:48
Shrewslinggao: in the tempest repo  :)15:48
anteayasince i do not know the answer to that15:48
dtantsurlucasagomes, starting dumping my thoughts on what to cover15:48
Shrewslinggao: start with this: http://docs.openstack.org/developer/tempest/15:49
Shrewslinggao: api tests and scenario tests are in different subdirectories15:49
Shrewsgit://git.openstack.org/openstack/tempest.git15:50
linggaoShrews, we'd like to test ironic with real hardware.15:50
Shrews++15:50
linggaoShrews, anteaya, those tempest are for use with third party CI, correct?15:51
linggaowith->by15:51
Shrewslinggao: i'm not 100% sure if 3rd parties use it, but i don't see why they can't. devstack-gate definitely uses it, though15:52
anteayarunning the tempest test suite is a good place to begin15:52
jrolllinggao: third-party CI can run any code you wish it to. it just looks for gerrit events, acts on them, and posts a comment15:52
lucasagomesdtantsur, will take a look15:53
jrolltempest is a good start15:53
anteayalinggao: attending the third party meetings will be helpful: https://wiki.openstack.org/wiki/Meetings/ThirdParty15:53
jrolldtantsur: where is this etherpad?15:53
anteayalinggao: also reading the meeting logs15:53
*** eghobo has joined #openstack-ironic15:53
*** eghobo has quit IRC15:53
anteayalinggao: reading this page: http://ci.openstack.org/third_party.html15:53
linggaoanteaya, yes. someone else in our team sets it up. But he cannot attend the meeting because of the time zoon15:54
dtantsurjroll, https://etherpad.openstack.org/p/IronicDownstreamDiscoveryRamdisk (only 1st part is of interest)15:54
jrollcool, thanks15:54
* jroll really goes to the office now15:54
anteayaas well as the patches to it: https://review.openstack.org/#/c/101013/ and https://review.openstack.org/#/c/101227/15:54
linggaoanteaya, I wil try to attend. You have gave me all the info about the meeting before.15:54
anteayalinggao: great, that would be a big help to both of us I think15:55
*** eghobo has joined #openstack-ironic15:55
linggaoanteaya, :)15:55
anteaya:D15:56
linggaoNobodyCam, anteaya, Shrews, jroll, thanks for the info. We have got the basic setup. Just need to learn how to test Ironic.  https://review.openstack.org/#/c/102121/15:56
linggaoThere is a "IBM xCAT CI", that's us.15:57
Shrewslinggao: currently, the tempest ironic tests don't do very much. more are being added (example: https://review.openstack.org/94439)15:57
*** hemna_ has joined #openstack-ironic15:58
NobodyCambbt brb15:58
Shrewsand https://etherpad.openstack.org/p/IronicTempestFeatures15:58
linggaoShrews, this new patch still use the vm to do the tests, right?15:59
Shrewslinggao: in devstack-gate, yes. but that is setup independently from tempest itself16:00
Shrewstempest doesn't care16:00
linggaoShrews, I see.16:01
*** eghobo has quit IRC16:01
*** eghobo has joined #openstack-ironic16:01
linggaoShrews, so devstack-gate set up the system when new patches are in and tempest test it?16:01
Shrewslinggao: yes16:02
linggaowhere can I find devstack-gate?16:03
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix leaking DB details to API on error  https://review.openstack.org/7312116:03
Shrewslinggao: devstack-gate just uses devstack (thus the name) which sets up the vm's and tempest16:04
linggaoShrews, oh, so we need to write a script to use devstack to setup the node and run temest.16:06
*** martyntaylor has quit IRC16:06
Shrewslinggao: no, you don't HAVE to use devstack. it just conveniently bundles tempest. tempest can run independently16:06
*** martyntaylor has joined #openstack-ironic16:07
linggaoShrews, thanks a lot for the info.16:08
Shrewssure, no problem16:09
*** martyntaylor has quit IRC16:11
Shrewsmatty_dubs: rloo: which review had the jenkins comment problem?16:12
*** bandicot has joined #openstack-ironic16:12
devanandamorning, all!16:12
dtantsurdevananda, morning16:12
rlooShrews: https://review.openstack.org/#/c/73005/16:12
*** vinbs has joined #openstack-ironic16:12
rloomorning devananda!16:12
rlooShrews: i just looked on -infra. Now I know why you asked. Yes, it was me.16:13
Shrewsrloo:  :)16:14
*** vinbs_ has joined #openstack-ironic16:14
*** vinbs has quit IRC16:14
*** vinbs_ is now known as vinbs16:15
jrollheya devananda16:15
* devananda reads all the scrollback16:16
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Prevent updating UUID of Node, Port and Chassis on DB API level  https://review.openstack.org/10224716:16
* dtantsur back in 1 hour16:16
*** dtantsur is now known as dtantsur|afk16:16
* devananda notices someone was asking a question based on https://wiki.openstack.org/wiki/GeneralBareMetalProvisioningFramework16:16
devanandamaybe we should make it mroe clear that that no longer appleis16:16
*** ellenh has joined #openstack-ironic16:17
rloodevananda: well, it does apply, but for the old baremetal stuff, not for ironic. Yes, it should be made clear.16:18
NobodyCamgood morning devananda16:18
devanandatakadayuiko: hi! glad to hear Ironic succeeded - would you care to share any details of what you are doing?16:18
devanandadtantsur|afk: the UUID of a resource shouldn't be allowed to change, but the reference between two resources can change, eg. changing nodes.chassis_uuid is fine because that represents movnig a node to a new chassis16:20
lucasagomesdevananda, morning16:20
*** jbjohnso has quit IRC16:22
devanandarloo: um, we should not pass instance_info when creating a node16:23
rloodevananda: ok, but we used to have the ability to pass eg 'pxe_root_gb'.16:24
rloodevananda: so we can update the node with instance_info?16:24
devanandarloo: hmm, while possible, that would have been illogical16:24
devanandarloo: root/swap/ephemeral sizes only have effect in the context of deploying an instance16:25
rloodevananda: do we need to document that you can't do that anymore (or ignore that it was possible at all)16:25
devanandarloo: definitely worth noting in the CLI's changelog16:28
*** martyntaylor has joined #openstack-ironic16:31
*** martyntaylor has left #openstack-ironic16:32
rloodevananda: how to add to CLI's changelog? When you tag the package, you generate the info from the logs, but there's no code change associated with this.16:32
*** yjiang5 is now known as yjiang5_away16:33
devanandarloo: the release notes / changelog isn't auto-generated16:36
devanandarloo: so i can add a line there. is there a bug or commit which should be referenced?16:37
rloodevananda: there are a bunch of commits wrt the instance_info stuff. Or do you want the spec/blueprint?16:37
rloodevananda: I suspect this is the one that changed it: https://review.openstack.org/#/c/94855/, since that's the only use of instance_info so far.16:39
lucasagomesdevananda, I was thinking about the case where you trigger the deploy via ironic node-set-deploy-state16:40
lucasagomesdevananda, so that would make sense to be able to input all the required infos when creating the node16:41
lucasagomesno?16:41
devanandalucasagomes: regarding https://review.openstack.org/#/c/96466/5 - does this do anything?16:41
* lucasagomes maybe is going too far16:41
devanandalucasagomes: yea... i can see the optimization when not using Nova to do deploys ... but ...16:41
*** jcoufal has joined #openstack-ironic16:41
lucasagomesdevananda, nova baremetal have those functions implemented, tho, I don't know if that actually does something16:42
lucasagomesnot in my env16:42
devanandalucasagomes: OTOH, I think that "create node" semantically should have physical characteristics, whereas root/swap/eph/image_source are logical characteristics of that specific instance16:42
devanandalucasagomes: right. i dont think they do anything, because nova baremetal requires the NoopFirewallDriver16:42
lucasagomesdevananda, right, should we just remove those functions instead of implementing it then?16:43
devanandalucasagomes: i think it's fine to add those methods for consistency16:43
lucasagomesdevananda, yeah... I think I agree with the node-create16:43
devanandalucasagomes: lemme check. i believe they're required16:43
lucasagomesdevananda, ack16:43
*** jbjohnso has joined #openstack-ironic16:43
devanandalucasagomes: yea. they all raise NotImplementedError() in the base class16:44
* Shrews changes venue. bbiab16:44
devanandalucasagomes: that's why I stubbed them with pass() initially - -but your patch is cleaner16:44
lucasagomesdevananda, ackd16:44
lucasagomesdevananda, btw, I saw that the spec for the nova driver has now a +216:44
lucasagomesdevananda, maybe we should start priorizing the patches that changes the nova driver16:45
devanandalucasagomes: definitely16:45
lucasagomesto send it to nova asap when the spec get merged16:45
devanandalucasagomes: all the cleanup for nova driver should be getting reviewed asap16:45
lucasagomes+116:45
lucasagomesdevananda, https://review.openstack.org/#/c/97536 < add/update the docstrings on the driver (pinging you because having a native speaker to look at it would be good)16:47
devanandalucasagomes: was just looking :)16:47
devanandalucasagomes: also, do you know anyone who likes to write wiki pages and/or documentation?16:47
lucasagomesdevananda, hmmmm... who actually likes it, not really16:48
lucasagomesmaybe we should try to share some of the doc tasks between cores at least16:49
lucasagomesso everybody helps a little bit16:49
devanandalucasagomes: i'm referring to more than just the inline code docs16:49
devanandathings like https://wiki.openstack.org/wiki/Baremetal which I wrote over a year ago16:50
devanandaand was reminded this morning, since foexle was asking questions based onthat, that these pages still exist16:50
devanandai should try to find time to rewrite it for ironic ... but would love help16:50
*** kylers has quit IRC16:51
*** yjiang5_away is now known as yjiang516:51
lucasagomesdevananda, I see hmm, not sure, I will ask internally16:52
lucasagomesdevananda, maybe the guy writting those: https://review.openstack.org/#/c/94604/ ?16:52
devanandalucasagomes: on 97536, there are actually doc strings in the nova base class16:52
devanandalucasagomes: have you looked at those // considered usign them?16:52
lucasagomesdevananda, yup I did, some of then are like hypervisorish16:53
lucasagomesso I adapted16:53
lucasagomesthem*16:53
*** kylers has joined #openstack-ironic16:53
devanandak, cool16:53
*** pelix has quit IRC16:54
*** harlowja_away is now known as harlowja16:55
*** athomas has quit IRC16:56
devanandalucasagomes: you've changed the function sig for node_is_available16:58
lucasagomesdevananda, ew :/ lemme check17:00
lucasagomesdevananda, ah, right I changed because that's actually the uuid of the node being passed not the name17:00
lucasagomesso nodename as the name of the parameter makes feel sense, u think it's an unrelated change?17:01
lucasagomesor that we shouldn't change it17:01
devanandai think we shouldn't change it17:02
devanandanodename is the nova term for this. we use "node_id" in Ironic.17:02
lucasagomesdevananda, right, the reason why its passing the UUID is because the get_available_nodes is returning a list of uuids17:03
lucasagomesdevananda, I will update the patch to not change it17:03
devanandalucasagomes: well. more than that -- nova tracks resources as (host, hypervisor_hostname)17:03
devanandaand awkwardly uses  "hypervisor_hostname" and "nodename" interchangeably to mean the same property in different parts of the code17:04
devanandayay confusion :)17:04
devanandawe've talked about cleaning that up for a year, but really should just remvoe the whole concept from nova17:04
lucasagomesheh yeah, well the description will say it's actually the UUID even tho it's called nodename :)17:04
lucasagomesright17:04
devananda++17:04
devanandaI've got amny other comments, will post shortly17:04
devanandamostly the rest are wording suggestions that you asked for17:05
*** bandicot has quit IRC17:06
lucasagomesdevananda, ack,will wait then before updating the patch17:06
*** dtantsur|afk is now known as dtantsur17:06
dtantsurdevananda, of course! I was talking about entity's own UUID, not fkey's17:07
devanandalucasagomes: posted17:09
devanandadtantsur: right :)17:09
lucasagomesdevananda, ta much17:09
dtantsurdevananda, seen our discussion about generic discovery spec? Your opinion?17:12
devanandalucasagomes: good to tag another CLI release today?17:12
devanandadtantsur: I skimmed it - can you summarize?17:12
dtantsurdevananda, my idea is to have a spec with all possible general ideas about discovery, which are independent of particular implementation (IPA, PXE, ILO, ...)17:13
*** petertoft has quit IRC17:13
lucasagomesdevananda, think it's fine... there's a requirements update patch there17:13
*** romcheg has quit IRC17:13
lucasagomesmaybe we should approve that first17:13
dtantsurdevananda, so that we can agree one some small common steps before we dive into particular implementations17:13
dtantsur* one = on17:13
devanandadtantsur: ++17:14
lucasagomesthere's also one that I had forgot (https://review.openstack.org/#/c/91585/) adding pagination support for list commands17:14
devanandalucasagomes: ooh ya. which I had a problem with last time I saw17:14
lucasagomesI need to update that patch, I think it's a bit important because if u had more than 100 nodes (default in Ironic) they won't be listed17:14
dtantsurdevananda, cool! lucasagomes, jroll and I will take part in prototyping it, will try to come up with something this week17:14
devanandalucasagomes: right - i agree, important to fix17:14
devanandadtantsur: awesoem, thanks17:14
lucasagomesdtantsur, ack!17:15
lucasagomesdevananda, mind waiting to tag it tomorrow?17:15
devanandalucasagomes: nope17:15
lucasagomesI have to rework that patch because of the limit python have on recursive functions17:16
NobodyCambrb17:16
lucasagomesdevananda, ack thanks, I will update it tomorrow17:16
devanandalucasagomes: also pls see my comment from may 3017:16
lucasagomeswill do17:16
devanandalucasagomes: i think it needs to introduce new --limit param17:16
lucasagomesdevananda, ah that's true haha17:17
devanandalucasagomes: and therefore also a new --offset param, which should accept the UUID of a resource and start the list from that piont17:17
lucasagomesdevananda, yeah makes sense, since it's already supported by our api17:18
devanandaer, s/--offset/--start-with/17:18
* lucasagomes had totally forgot about the existence of that patch17:18
jrolldtantsur: hooray for being volunteered :)17:18
devanandalucasagomes: right17:18
dtantsurjroll :D17:18
dtantsurjroll, you'll like it, I promise :)17:19
lucasagomesdtantsur, jroll o/17:19
jrolldtantsur: let me finish these other 5 specs and I'll get right on it :P17:19
dtantsurack17:19
*** martyntaylor1 has joined #openstack-ironic17:21
lucasagomesdevananda, 2 things on the docstring patch... "List of MAC addresses for the node which this instance is associated with" is too long for the one line docstring, I will remove "addresses" right?17:21
lucasagomesyeah actually only 117:23
devanandalucasagomes: sure17:24
*** rwsu has joined #openstack-ironic17:25
jrolldevananda: hey, if I get a decent configdrive patch up for the nova driver today, any chance we could prioritize that stuff with the other nova changes? :)17:26
jrolldevananda: (caveat, configdrive BP is -1'd, I'll be fixing that up today)17:26
devanandajroll: I'd punt that to the nova team and see if they are willing to take on the additional review overhead when landing the ironic driver17:27
devanandajroll: if they approve the nova spec for it -- then it's quite likely i'll prioritize reviewing it17:27
jrolldevananda: thanks, I'll see what I can do17:27
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Add/Update docstrings in the Nova Ironic Driver  https://review.openstack.org/9753617:28
*** sirushti has left #openstack-ironic17:28
devanandajroll: but I dont want that (or anything else) to further complicate or delay landing the ironic driver (cause, y'know, we *all* need that to land....)17:28
jrollof course :)17:28
jrollthat's why I'm asking :)17:28
devananda:)17:28
*** sirushti has joined #openstack-ironic17:28
jrollI guess it would get split into a separate patch in the nova review anyway, so17:28
lucasagomesalright folks, I'm done for the day17:28
lucasagomeshave a good night everyone!17:28
*** bandicot has joined #openstack-ironic17:28
jrollnight lucasagomes17:29
devanandalucasagomes: cheers, g'night!17:29
*** lucasagomes is now known as lucas-dinner17:29
NobodyCamgnight lucas-dinner17:29
openstackgerritJim Rollenhagen proposed a change to openstack/ironic-specs: Support external DHCP providers  https://review.openstack.org/10229617:35
jrollone down17:35
*** openstackgerrit has quit IRC17:35
*** openstackgerrit has joined #openstack-ironic17:36
*** vinbs_ has joined #openstack-ironic17:38
*** achanda has joined #openstack-ironic17:38
*** Manishanker has joined #openstack-ironic17:40
openstackgerritAdam Gandelman proposed a change to openstack/ironic-specs: External event callback API  https://review.openstack.org/9977017:40
*** vinbs has quit IRC17:41
*** vinbs_ is now known as vinbs17:41
NobodyCamrameshg8-: are you around?17:41
*** yu_ has joined #openstack-ironic17:43
NobodyCamdevananda: may be you know off the topof your head, dose iLo support key based logins?17:43
*** vinbs has quit IRC17:46
devanandaNobodyCam: i do not know17:46
NobodyCam:)17:46
*** vinbs has joined #openstack-ironic17:48
*** Penick has joined #openstack-ironic17:54
*** jcoufal has quit IRC17:56
*** yjiang5 is now known as yjiang5_away17:57
*** vinbs has quit IRC18:00
NobodyCambrb18:02
*** harlowja has quit IRC18:04
*** harlowja has joined #openstack-ironic18:07
*** harlowja has quit IRC18:07
Shrewsadam_g, devananda: can i get you to vote on https://review.openstack.org/94439 again? otherwise, sean will likely ignore it18:09
*** kylers has quit IRC18:09
adam_gShrews, sure.18:09
Shrewsgracias18:09
rlooJoshNang: I think you're updated https://review.openstack.org/#/c/98904/ was based off of patch set 4, not 5 :-(18:10
JoshNangrloo: oh shoot.18:10
JoshNangone sec18:10
openstackgerritJosh Gachnang proposed a change to openstack/ironic-specs: Drivers Determine Acceptable Power States  https://review.openstack.org/10230618:10
openstackgerritJosh Gachnang proposed a change to openstack/ironic-specs: Swift Temporary URLs Spec  https://review.openstack.org/9890418:14
JoshNangrloo: should be fixed :D18:14
JoshNangthanks!18:14
NobodyCamdf18:16
NobodyCamdoh18:16
devanandaShrews: hi! so those changes LGTM18:18
rloothx JoshNang18:18
Shrewsdevananda: hi! and, yay!18:19
devanandaShrews: but now i want to ask you sometjhing else ... you might hate me, though18:19
Shrewsoh geez18:19
devanandaShrews: the new test takes ~5 minutes, but it looks like it added ~20 minutes to the run time18:19
devanandaShrews: thoughts on that?18:19
devanandaShrews: also, is compute OK adding the new rebuild option? it should probably get a vote from someone in nova for that, I would think?18:20
Shrewsdevananda: one thing i had to add was a "wait_for_resources" method that waits until the single ironic node in devstack-gate is released18:20
Shrewsdevananda: not sure how long that takes, but should be 15 min18:20
Shrewsdevananda: i haven't asked anyone from nova, but will18:21
Shrewsdevananda: SHOULDN'T be 15 min... gah18:21
devanandaShrews: right, so if it waits 15 minutes, and the test takes 5, that matches my observation18:21
devanandaoh18:21
*** martyntaylor1 has left #openstack-ironic18:23
devanandaShrews: hm, looking back at the jenkins history there, maybe it was just that run that was slow?18:23
devanandaShrews: patch set 11 ran in 34 min and then in 50 min ...18:24
Shrewsdevananda: i see from my review the basic one takes about 3.5 min,  and the advanced in about twice that, which makes sense (2 instances created)18:24
devanandaright18:25
*** bandicot has quit IRC18:25
devanandain the future we're going to need to add more functionality to those scenarios, rather than add more scenarios, I think18:25
*** dsneddon has joined #openstack-ironic18:25
devanandaotherwise our test run will just take waaay too long18:26
*** harlowja has joined #openstack-ironic18:26
*** harlowja has quit IRC18:26
Shrewsdevananda: yeah. unless you want to get rid of the basic one, i don't see how to fix that one, though18:26
*** harlowja has joined #openstack-ironic18:26
*** harlowja has quit IRC18:26
devanandafor now, +5 min seems OK, but we need to keep total run time in mind18:27
*** harlowja has joined #openstack-ironic18:27
*** harlowja has quit IRC18:27
devanandaadam_g: any thoughts on ^ ?18:27
devanandaShrews, adam_g: also, are either of you working on moving our tempest tests to admin/ ?18:28
Shrewsdevananda: adam_g has a patch up for that18:28
devanandaawesome18:28
devanandalink?18:28
adam_ghttps://review.openstack.org/#/c/100989/18:28
*** harlowja has joined #openstack-ironic18:28
*** harlowja has quit IRC18:28
adam_gdevananda, runtime of tempest is going to absolutely explode once enable the parts of the API tests we skip via regex currently18:29
*** harlowja has joined #openstack-ironic18:29
*** harlowja has quit IRC18:29
devanandaadam_g: fantastic. why?18:29
*** ccrouch has joined #openstack-ironic18:29
adam_gdevananda, *lots* of API tests require spinning up an instance as part of the tests setUpClass or the invididual tests18:29
devanandaooh18:29
devanandaright18:29
devanandabecause with libvirt, instance starts in seconds18:29
adam_gyeah18:29
*** harlowja has joined #openstack-ironic18:29
*** harlowja has quit IRC18:29
devanandapxe provisioning a nested vm is terrible tho18:30
adam_gsome also start multiple instances18:30
devanandaadam_g: any estimate of how bad that will be?18:33
devanandaif it's going to be prohibitive, we will need to have a long talk with qa folks ...18:33
openstackgerritDevananda van der Veen proposed a change to openstack/python-ironicclient: Make a few minor updates to node shell help strings  https://review.openstack.org/10231218:33
*** harlowja has joined #openstack-ironic18:34
*** harlowja has quit IRC18:34
adam_gdevananda, i dont have a baseline yet, still working on getting tempest.api.compute.* to run.18:35
devanandaadam_g: ack18:36
adam_gdevananda, theres still a couple issues aside from feature flags there, but yeah.. i dont know how long is too long for a tempest job18:36
devanandaadam_g: I suspect this will have to go to the ML to discuss with QA folks18:36
devanandaadam_g: so that we can adequately explain why it's slower to the whole QA team at once, and then try to find a solution18:37
adam_gdevananda, sure18:37
devanandaadam_g: but having real numbers first would be good. if it's under an hour for the run, my guess is that'll be acceptable18:37
devanandaadam_g: if it's like 5 hours .... heh, no.18:37
adam_gdevananda, right18:37
devanandaso we need to see18:37
dtantsurjroll, around? I'm shamelessly stealing things from IPA spec and I'd like to know, whether you have written format for hardware inventories in Node.extra. I would like to include it in generic spec.18:38
devanandaas for the multiple instances tests, we can make a case that ironic tests need to run in larger instances18:38
adam_gdevananda, theres still some other rough spots i need to work out aside from feature flags. ie, tests spawning instances too quickly before n-cpu can reclaim ironic's resources from a previous tests instance18:38
*** harlowja has joined #openstack-ironic18:39
*** harlowja has quit IRC18:39
devanandaahh18:39
devanandaadam_g: i think shrews just addressed that with wait_for_resources18:39
devanandaadam_g: but we could also make some changes in the virt driver that might help that, maybe18:39
adam_gdevananda, yeah, the API tests need to do something similar, but they are structured such that there are admin tests and non-admin tests, and not really any mixing of the two (hypervisor-stats is an admin thing we'd be stressing from the non-admin tests)18:40
*** harlowja has joined #openstack-ironic18:40
*** harlowja has quit IRC18:40
adam_gdevananda, what virt driver changes did you have in mind? that'd be an easier route18:41
*** harlowja has joined #openstack-ironic18:42
devanandaadam_g: off hand ideas ...18:42
devananda- virt driver changes ResourceTracker when delete() is complete18:43
devananda- use nova's event API so ironic can actively inform nova of resource changes (rather than wait for pollign)18:43
devanandai think comstud had some sketches of how we might do the second of those18:43
ShrewsTrying to get generate_sample.sh to work makes me want to kill bunnies18:44
adam_gdevananda, interesting18:45
devanandaShrews: huh? works fine for me18:45
Shrewsdevananda: in tempest. needed a rebase now it's all borked up18:45
devanandaShrews: also, I think i saw a patch which will add a jenkins job to do that for us18:45
devanandaoh18:45
devanandaworks fine /in ironic/ for me :)18:46
* Shrews pokes devananda in eye with a stick18:46
devanandaow!18:46
comstudI don't think I have a sketch18:46
* devananda throws a cup'o'cold'coffee at Shrews18:46
comstudbut you can find examples of neutron calling back to nova...  in neutron18:46
adam_gcomstud, yeah18:46
devanandacomstud: ah. must be wishful thinking on my part then :)18:47
comstudyeah :)18:47
comstudmy part too, I guess18:47
comstudI'm just trying to get back to the object fixes I need to make yet18:48
comstudor s/need/want/18:48
comstudwhich should be RSN18:48
NobodyCamgrr how can one get the root device inside a chroot18:48
Shrewsand now, pbr will not install on a fresh devstack run/reclone18:48
* Shrews cries18:48
openstackgerritlinggao proposed a change to openstack/ironic: Fix exception handling in console start  https://review.openstack.org/10231818:49
devanandaShrews: oh, right. my devstack was hosed last week too.18:49
devanandaShrews: thanks for reminding me how sad I am about that18:49
Shrewsdevananda: solution?18:49
Shrewsif any18:49
devanandaShrews: shoot it?18:49
ccrouchany suggestions for how to deal with a failure trying to delete an instance from nova?18:49
ccrouchnova baremetal is complaining it can't authenticate to the node (a mock baremetal vm) via ssh18:49
ccrouchhttp://fpaste.org/112723/63498414/18:49
ccrouchdelete worked fine on two other instances from the same tripleo setup18:49
devanandaccrouch: using baremetal or ironic?18:50
Shrews*sigh*18:50
devanandaccrouch: right - baremetal. no clue, sorry. best advice i will give right now is: please use ironic instead :)18:50
devanandaccrouch: fwiw, that does look like a simple SSH authentication error connecting to the host on which that mock baremetal instance exist(ed)18:52
ccrouchright, its just that the authentication is the same across all the nodes, it just fails on this one :-(18:53
ccrouchi'm trying find a way to unwedge it, so i dont have to blow my undercloud away18:53
*** krtaylor has quit IRC18:56
*** achanda has quit IRC18:56
devanandaccrouch: fails repeatably on that node? or failed once on that instance?18:57
*** jdob has quit IRC18:57
*** jdob has joined #openstack-ironic18:58
ccrouchchecking18:59
*** jcoufal has joined #openstack-ironic18:59
*** krtaylor has joined #openstack-ironic19:01
ccrouchso i can't get *anything* to happen with more runs of nova delete <blah>19:02
ccrouchnothing changes in  /var/log/nova19:02
ccrouchand the instances stay in ERROR:deleting:NOSTATE19:02
ccrouchERROR : deleting : NOSTATE19:02
openstackgerritA change was merged to openstack/python-ironicclient: Updated from global requirements  https://review.openstack.org/9626319:02
Shrewsdevananda: so, we have our ++ from nova, now if i could just get a successful rebase, which seems to require a successful devstack re-install, which is borked. I shall drink much beer tonight, methinks19:04
Shrewswait, why am i even using devstack???19:05
* Shrews might need caffeine19:05
devanandaccrouch: sure. Asking nova to delete an instance that is already in the process of deleting is just a no-op19:06
devanandaccrouch: that didn't answer my qusetion19:06
*** ellenh has quit IRC19:07
devanandaccrouch: you might have better luck asking in #tripleo, as it sounds like your question is really a tripleo question, not related to ironic?19:07
*** max_lobur has joined #openstack-ironic19:07
ccrouchi think the issue is with nova-baremetal which is why i came here, but I understand that is not your focus19:08
*** max_lobur1 has joined #openstack-ironic19:09
*** jdob has quit IRC19:09
*** max_lobur has quit IRC19:09
*** jdob has joined #openstack-ironic19:09
*** Manishanker has quit IRC19:10
devanandaccrouch: from what I recall of nova-baremetal, you may be able to re-initiate the delete by restarting nova-compute19:13
devanandaccrouch: short of that, I think you'd need to do some careful manual editing of both the nova and nova_bm databases19:14
ccrouchappreciated, i will give that a go. thanks19:14
devanandaccrouch: but it's been over a year since I worked in taht code base ... sorry19:14
ccrouchyeah, i think at that point i will nuke-it-from-orbit19:14
ccrouchno problem, thanks for giving me some pointers19:14
devanandaShrews: why would a rebase require devstack running?19:15
Shrewsdevananda: it doesn't. i was using devstack as a shortcut to reinstall tempest. but even manually, i get errors with pbr19:15
Shrewsso, life sucks right now19:16
*** killer_prince has quit IRC19:24
NobodyCamahhh fstab must be correctly set to run mkinitrd... why?19:28
NobodyCamnice but as a side note I was able to build and deploy a openSUSE image19:31
*** harlowja has quit IRC19:31
NobodyCamwith only a couple of really nasty hacks :-p19:32
Shrewsdevananda: a 'rm -rf /usr/local/lib/python2.7' seems to be the cure19:32
devanandaShrews: sweet. /me tries that19:34
NobodyCambrb19:34
*** Mikhail_D_ltp has joined #openstack-ironic19:35
Shrewsdevananda: i've also set RECLONE=yes in localrc19:35
*** achanda has joined #openstack-ironic19:35
Shrewsor just rm /opt/stack19:36
*** harlowja has joined #openstack-ironic19:37
*** harlowja_ has joined #openstack-ironic19:39
devanandaShrews: pkg_resources.DistributionNotFound: pip==1.4.119:41
Shrewsdevananda: yeah, i had that too, but my pip was 1.5.6 and NOT installed via apt-get19:42
*** harlowja has quit IRC19:42
Shrewsit's all working for me now19:42
devanandaShrews: how are you installing pip?19:42
Shrewsdevananda: devstack installs it19:42
*** max_lobur has joined #openstack-ironic19:44
linggaofolks, can a patch have 2 dependencies?19:44
devanandalinggao: if they are linear, yes19:45
devanandalinggao: A -> B -> C19:45
*** max_lobur2 has joined #openstack-ironic19:45
*** max_lobur1 has quit IRC19:45
linggaodevananda, Can A depends both B and C, B and C has no relationship?19:45
devanandalinggao: no19:46
devanandalinggao: that is not modelled by gerrit, unfortunately19:46
linggaodevananda, thanks.19:46
*** Mikhail_D_ltp has quit IRC19:48
*** max_lobur has quit IRC19:49
*** jcoufal has quit IRC19:49
*** rameshg8- has quit IRC19:49
*** Penick has quit IRC19:58
*** Penick has joined #openstack-ironic20:03
*** zdiN0bot has joined #openstack-ironic20:05
*** dtantsur is now known as dtantsur|afk20:10
dtantsur|afkg'night20:11
NobodyCamnight dtantsur|afk20:11
*** dsneddon has quit IRC20:11
*** rameshg87 has joined #openstack-ironic20:15
*** ellenh has joined #openstack-ironic20:15
*** Mikhail_D_ltp has joined #openstack-ironic20:16
*** Mikhail_D_ltp has quit IRC20:16
*** Mikhail_D_ltp has joined #openstack-ironic20:16
*** zdiN0bot has left #openstack-ironic20:17
jrolldtantsur|afk: here now. not quite sure what you're asking?20:21
*** kylers has joined #openstack-ironic20:23
adam_ganyone know what the plan / stauts is for ironic.nova.compute.manager.ClusteredComputeManager ?20:25
ellenhdevananda: hi, last week you told me to use _LI() for info logging, does that still apply?  It seems to cause import errors and isn't in the logging spec anymore20:25
jrolladam_g: with regards to?20:26
*** eguz has joined #openstack-ironic20:26
devanandaellenh: hi! the i18n team is adding docs /right now/ on that :) see http://docs-draft.openstack.org/61/96961/7/check/gate-oslo.i18n-docs/c4074a7/doc/build/html/guidelines.html#log-translation for the pre-merge draft20:27
adam_gjroll, i guess wrt merging ironic.nova.* back into nova. is that going with it? do we maintain a host manager in ironic? is it even used currently? (we're not testing it upstream)20:27
devanandaellenh: which should be landed within an hour, i think20:27
devanandaadam_g: CCM is not merging20:27
devanandaadam_g: see the ironic driver spec in nova -- they kicked that bit out, even though RS is using it, and afaik so is tripleo20:28
*** davidlenwell_ is now known as davidlenwell20:28
adam_gdevananda, is it going away or staying in ironic? im looking to work around the resource reclaim stuff we were talking about wrt tempest, and that would be a good place20:28
*** eguz has quit IRC20:28
*** eguz has joined #openstack-ironic20:28
adam_gah!20:28
jrollstaying in ironic pls20:28
NobodyCamany one happen to recall enough bash to correctly construct : if [ "${chk_device:-2}" == "p[0-9]" ]; then20:29
devanandajroll: i'd rather it merge to nova, fwiw20:29
jrolldevananda: I mean short term20:29
devanandajroll: but it is not "going away" until there is a better solution20:29
jrolluntil that happens20:29
ellenhdevananda: great, thanks20:29
jrollright20:29
devanandaright20:29
*** eghobo has quit IRC20:30
*** Mikhail_D_ltp has quit IRC20:39
rloodevananda: do you have a few minutes to discuss the design of https://review.openstack.org/#/c/73005/?  API to get driver_info properties?20:39
devanandarloo: after this meeting, yep20:41
rloodevananda: ok20:41
*** max_lobur has joined #openstack-ironic20:41
*** max_lobur has quit IRC20:44
*** max_lobur2 has quit IRC20:44
openstackgerritA change was merged to openstack/ironic-python-agent: Better errors for execute() failures  https://review.openstack.org/9966620:47
openstackgerritlinggao proposed a change to openstack/ironic: Naming change for console terminal port  https://review.openstack.org/10234520:57
*** jdob has quit IRC20:58
*** jbjohnso has quit IRC21:05
devanandarloo: ok, mostly done with that meeting21:05
jrollthinking more about https://review.openstack.org/#/c/8674421:06
openstackgerritlinggao proposed a change to openstack/ironic: Naming change for console terminal port  https://review.openstack.org/10234521:06
rloodevananda: thx. wrt https://review.openstack.org/#/c/73005/, my first approach was to instantiate driver objects in the API. and you said not to do that.21:06
jrollwhat if that was just general node validation for driver actions, e.g. deploy(), tear_down(), write_firmware()21:06
rloothe 2nd approach was to use rpc to talk to conductor. romcheg said not to do that.21:06
rloothe suggestion now is to save the driver_info in the db.21:07
jrollfor example, the agent driver could make sure the agent was up and firmware exists, for write_firmware()21:07
rlooi was wondering why (maybe I forgot why) drivers shouldn't be loaded in the api service.21:07
jrolland then I realized we have validate(). maybe we should just pass the desired action to validate()?21:08
jroll(just thinking out loud)21:08
rlooand i was wondering whether saving the driver_info properties in a db table made sense.21:08
*** igordcard has quit IRC21:08
rloovs eg having the api get the driver_info properties once and caching.21:08
JoshNangjroll: seems sensible. i'd rather leave it in validation than a separate method, and have validation for each action rather than general validation is more useful in my mind21:09
*** kylers has quit IRC21:09
jrollJoshNang: exactly21:09
jrollJoshNang: and the upgrade path for each driver is easy - add an argument that (currently) is not used21:09
rlooand if we saved in a db, whether it made sense to save in conductor table cuz conductor info is only there when a conductor is available.21:09
JoshNangjroll: well and putting the current power state validation in there21:10
jrollah yes21:10
JoshNangwhich isn't much21:10
rlooanyway, i am wondering why i don't just get (in api service) all the drivers specified in setup.cfg (if i can figure out how to do that) and save/cache the driver_info properties and be done with it.21:11
JoshNangputting it in validate would make validation run longer than it does currently, because you're adding power_driver.get_power_state to validate. i don't think that's a huge concern though21:13
jrollwell21:13
jrollit's just moving it to a different place21:13
devanandarloo: why not load drivers in the api service -- because drivers talk to hardware ,and the API service shouldn't be allowed to do that21:13
jrollJoshNang: you could also restrict power state validation to 'deploy' or whatever21:14
rloodevananda: too bad. Guess I can't get a 'read-only' driver.21:14
JoshNangjroll: what do ya mean?21:14
devanandarloo: we could factor out the validation to another (set of) class(es)21:15
jrollJoshNang: like, power state validation already happens somewhere in the deploy() call. this just moves it to somewhere else in the deploy() call21:15
devanandabut...21:15
devanandarloo: what I was thinking is this...21:15
JoshNangjroll: gotcha. that's what my patch is doing currently21:15
devanandarloo: when a conductor service starts, it already calls register_conductor, which saves a list of available drivers in the db21:15
jrollJoshNang: yeah, this just moves it to somewhere else somewhere else21:15
JoshNangso yeah, it's really not a concern21:15
rloodevananda: yes. it saves the drivers for that conductor in the conductor table.21:16
devanandarloo: oh. gah. i'm juggling another meeting and thinking of something else. never mind21:16
devanandarloo: what about node update calling validate, and stashing that on the node record?21:17
rloodevananda: i was thinking i could put the driverinfo per driver in a different driver table. but then... how long does the driver table live? and how to coordinate/update the info? or do I always update it per driver each time a conductor is registered.21:17
rloodevananda: ha ha. this isn't urgent. maybe you shouldn't multitask ;)21:17
jrollcan we not store driver capabilities in the database? please?21:18
devanandarloo: conductor table stores the lsit of drivers that conductor supports. it lives until that conductor goes offline21:18
*** matty_dubs is now known as matty_dubs|gone21:18
devanandarloo: that could store the list of parameters that each of those drivers needs21:18
devanandarloo: but that gets awkward with optional params21:18
devanandaeg, ssh needs user + (pass OR key)21:18
rloodevananda: yup, unless we only want the names of the required params, i was returning required/optional/help string.21:19
devanandarloo: wait. are we talking abotu the API listing the params? or validate?21:19
devanandaaren't those separate?21:19
rloodevananda: and yeah, even then, with optional parms there are some oddities.21:19
rloodevananda: listing the params. i was using that list for validate too though.21:19
rloodevananda: listing the required/optional params.21:19
devanandarloo: oh. right. so just stash a dict on the conductor table. seems easy to me.21:20
jrolldevananda: that's going to get less and less desirable as we add features, I think21:20
devanandaor we create another table, which is also fine21:20
jrollmight just be me thinking that, though21:21
devanandajroll: i'm sure i'm not thinking it through all the way ... how so?21:21
rlooyeah, i thought of another table. guess i'd need to update it each time a conductor is registered, just to be sure the info / driver is updated.21:21
rlooi assume we're ok with the db hits for each request for driver_info properties?21:22
jrolldevananda: more features, more functions, more arguments, more problems. (lots of optional arguments too)21:22
*** eguz has quit IRC21:22
jrolldevananda: mostly just, I don't understand why we don't just get it from conductor once and then cache21:22
jroll(cache on the api side)21:22
rlooyeah, jroll: i'd rather cache on api side and not stick in a db at all.21:23
jrollinvalidation might be tricky, but we can figure it out21:23
rloojroll: but if i do it via a conductor, it means the api needs to know if new conductors/drivers come online.21:23
* jroll waves his hands around magically21:23
devanandawhat does an upgrade look like?21:23
jrollrloo: right, that's the hard part21:23
*** bandicot has joined #openstack-ironic21:23
devanandaeg, if someone rolls out a new version of pxe_ipmitool that hasthis change https://review.openstack.org/#/c/102345/121:23
rloojroll: which is why i thought if i can get all the drivers from setup.cfg, in the API, and get the info from that, it solve the problem :-)21:23
devanandas/terminal_port/console_port/21:23
jrolldevananda: maybe cache for $conductor_timeout21:23
devanandahow and when does that propagate to the API?21:24
jrollrloo: ehhhhhhhh, I'd rather grab directly from the conductor or something21:24
rloojroll: on the other hand, that doesn't solve the problem if a conductor is run on another box with a diff setup.cfg/version of ironic.21:24
devanandarloo: that would require restarting API services to reload driver modules, and keeping them in sync between conductors and api services21:24
jrollrloo: exactly21:24
jrolland what deva said21:24
devanandarloo: and the conductor /should/ be run on a different box21:24
devanandarloo: conductor is very privileged service. API is not.21:25
* devananda needs to release a doc describing recommended service toplogy for security-minded deployments21:25
rloojroll, devananda. yeah. ok, so api makes at most one rpc call when a request comes in. gets conductor/driver info and caches it.21:25
devanandajroll: unless ya'll want to ^ :)21:25
jrolldevananda: we have a diagram :P21:25
jrollrloo: that's my thought21:26
rloodevananda, jroll: i'm going to assume (still) that driver info is the same regardless of conductor. which could be wrong if diff conductors running diff versions of ironic.21:26
devanandarloo: that will be wrong during an upgrade window at some point in time, which we need to consider21:27
rloodevananda: yeah. i was just thinking of that :-(21:27
rloodevananda: but what does it mean when someone makes a request for driver info, and there are diff versions of conductors. that they explicitly specify the conductor?21:27
rlooand why would anyone ask for driver_info properties if there is an upgrade going on. they shouldn't be registering new nodes then. but of course someone will...21:30
*** eghobo has joined #openstack-ironic21:32
*** eghobo has quit IRC21:36
*** harlowja_ has quit IRC21:36
*** eghobo has joined #openstack-ironic21:36
*** harlowja has joined #openstack-ironic21:36
*** linggao has quit IRC21:38
* devananda kicks his ISP21:38
devanandarloo: indeed.... i haven't thought through all the possibilities there. randomly getting the list from *a* conductor is probably bad, because it's non-deterministic if there are dif versions of drivers21:40
devanandarloo: similarly, caching without explicit cache invalidation is bad21:41
rloodevananda: I wonder if we should be capturing the conductor's RPC_API version.21:41
devanandarloo: because an upgrade could leave the caches on different API instances non-deterministically in different states21:42
devanandarloo: that is coordinated already between api and conductor21:42
devanandarloo: the driver API doesnt have a version right now, tho21:42
rloodevananda: i was thinking that the driver_info property that is cached, needs to be associated with the conductor's rpc api version.21:43
rloodevananda: is there a plan to have driver versions?21:43
*** romcheg has joined #openstack-ironic21:45
rlooa particular conductor (version) handles one or more drivers (that are versioned). Ugh.21:45
NobodyCamrloo: oh what a tangled web you are weaving21:47
devanandarloo: rpc version != driver version.... right.21:47
devanandafun!21:47
devanandai could, for instance, upgrade a driver without changing the conductor -- all i would need to do is restart the conductor to pick up the new python module21:48
rlooNobodyCam: Yeah, who would have thought a simple API that doesn't *do* much, could be so complicated. all to make our users happy.21:48
rloodevananda: but if you did that, how is the user to know/specify which driver version they want to associate with a new node?21:49
devanandaright21:49
devanandaso the answer may be that the cluster needs to refuse certain operations on a driver if different versions are present21:49
devanandajust thinking out loud ...21:50
rlooand then you're going to ask for an API so users can know what driver versions are available with which conductors. ha ha.21:50
devanandaperhaps that's a terrible idea21:50
devanandabut it solves several things21:50
NobodyCamwhat happens with  the inevitable question: "oh we have three ironic api nodes.. I only upgraded two of them"21:50
devanandaNobodyCam: try asking the same question of Nova. they started trying to solve this two years ago. i think it's still in progress21:51
rlooNobodyCam: don't confuse the issue! we're only talking about diff conductor versions and driver versions! :-)21:51
*** yjiang5_away is now known as yjiang521:51
NobodyCam:-p21:51
NobodyCam:(21:52
openstackgerritAdam Gandelman proposed a change to openstack/ironic-specs: External event callback API  https://review.openstack.org/9977021:54
NobodyCamrameshg87: around?21:55
jrollJoshNang: another idea wrt long-running deploy ramdisks. 1) provide a reboot script with ironic to do rolling deploy ramdisk upgrades. 2) keep ramdisk version (glance uuid?) in the db. check if that's latest at deploy() time, if not, reboot into latest. thoughts?21:56
*** mrda-away is now known as mrda21:56
mrdaMorning Ironic!21:56
jrollheya mrda21:56
NobodyCamgood morning mrda21:56
mrdao/21:56
devanandarloo: one possibility would be to simply document "when upgrading a conductor driver, you must restart all API services after the conductor service upgrades are completed"21:59
JoshNangjroll: that's reasonable i think21:59
devanandarloo: i mean, if we were to have the API cache the results21:59
devanandamrda: hi! replied to your email. and just thought of this -- https://review.openstack.org/#/c/79194/22:00
devanandamrda: take a look and let me know if reviving that work sounds interesting to you22:00
mrdathanks devananda, I'll take a look22:00
rloodevananda: upgrading a conductor driver isn't the same as conductor service upgrades though.22:00
devanandarloo: but both require restarting the conductor service itself22:00
JoshNangjroll: personally, i'd like to avoid 2 actually happening. you'd add a post cycle + kill any precaching. but, on the other hand, if those aren't concerns for the deployer, that's much easier than rebooting all the agents and having deploy downtime22:01
devanandajroll: ya'll doing any work on conductor migrations / take over / ring rebalancing?22:01
rloodevananda: right, restarting one, not necessarily all conductor services.22:01
rloodevananda: so there could be two diff driver versions.22:01
JoshNangor having to come up with a rolling update + a scheduler update to look for only latest ramdisk22:01
jrolldevananda: I don't believe so, right now22:01
mrdadevananda: Just FYI, also looking at +bug/130817122:01
JoshNangjroll: where would the latest version be stored?22:01
NobodyCambrb22:02
devanandajroll: ack. it probably doesn't matter as much for IPA if you're booting instances from local disk22:02
jrollJoshNang: I mean, yeah. thinking now of "when ironic sees a new deploy ramdisk/kernel hit the db, reboot that node"22:02
rloodevananda: I seriously doubt I will get all the i's dotted and t's crossed for this 'simple' API request. ha ha. let me think about it.22:02
jrollJoshNang: idk, somewhere in the node table22:02
jrolldevananda: yeah, I don't think we'd see many problems if a conductor crashed during a deploy22:03
devanandajroll: just taht deploy failing, at most22:03
devanandajroll: actually, you're not caching any local state at all, are you22:03
jrolldevananda: I think the deploy would even go through in most (all?) cases22:03
jrolldevananda: nope, exactly22:04
rloodevananda, jroll: thx for your feedback. Gotta take off for dinner so will 'sleep' on this ;)22:04
devanandajroll: so it'd only fail if the conductor was, say, in the middle of a db transaction22:04
jrollrloo: enjoy :)22:04
JoshNangjroll: right, so each node has like node.driver_info['ramdisk_version'] = x. if x != y, reboot node into new ramdisk before deploy. but where do we store y?22:04
devanandajroll: and if IPA is not smart enough (yet) to retry on error22:04
*** rloo is now known as rloo_gone22:04
jrolldevananda: yeah. even then, it might just end up writing the image a second time or whatever22:04
jrolldevananda: tldr: when the agent heartbeats, it looks at provision_state and does things based on that (write an image, or reboot, today)22:05
* rloo_gone thinks maybe we need to add another question in the specs -- how/is the feature affected by upgrades.22:05
NobodyCamnight rloo_gone22:06
jrollJoshNang: right, this won't work in our environment or current code. but e.g. pxe driver uses driver_info['deploy_ramdisk'] = 'glance://some-image-uuid'22:06
jrollJoshNang: so like, if current image uuid is different than that uuid, reboot22:06
jrollJoshNang: does that make sense?22:06
jrollJoshNang: the more I think about things, the more I like ironic controlling DHCP/PXE configs. unfortunately, as you already know, dnsmasq. :|22:07
JoshNangjroll: so when you upload a new ramdisk to glance, how do you notify ironic of that?22:07
jrollJoshNang: idk, you like, update the nodes that should use it through the API22:07
devanandaJoshNang: you change the deploy ramdisk on each node's driver_info ?22:08
jrollJoshNang: this is how pxe driver works today, anyway22:08
jrollJoshNang, devananda: the way we do things with "one golden ramdisk" doesn't really work for heterogeneous hardware :/22:08
jrolland it's quite unfortunate22:08
devanandajroll: :(22:09
JoshNangjroll, devananda: gotcha. wfm.22:09
devanandajroll: as long as that's a limitation of your choices, and not of IPA, that's fine (but unfortunate)22:09
jrollsplitting out these patches to work like the pxe driver has taught me a lot22:09
devanandajroll: :)22:09
jrolldevananda: it's more of... a consequence of our timeline22:09
jrolldevananda: that's not a permanent thing by any means22:09
devanandajroll: ah, gotcha. that makes sense22:10
jrollbut the working code *today* assumes a lot of things that won't work upstream22:10
jrolldevananda: that said, 101020 should work for everyone :) some small IPA changes need to happen to work with it but I think it's mostly good to go (maybe better tests too)22:10
*** romcheg has quit IRC22:10
JoshNangjroll: a compromise on ironic controlling dhcp/pxe is an api endpoint generating the ipxe config? i should go read the ipxe spec (i think there is one already)22:10
jrollJoshNang: hmm22:11
jrollJoshNang: another hard part is that endpoint would be per-node22:11
devanandajroll: only whole disk images supported (but those aren't supported by PXE driver yet) ?22:11
jrollJoshNang: so the dhcp config pointing the node to ironic for ipxe configs would need to figure that out22:11
JoshNangjroll: true22:12
jrollJoshNang: I'm tempted to make glyph happy and write that twisted dhcp server :)22:12
devanandajroll: that will be awkward if an environment were to run both, or migrate from pxe to ipa22:12
JoshNangjroll: heh22:12
devanandajroll: think ipa will support partition images soon?22:12
jrolldevananda: yeah, so, that's more of an IPA limitation (just needs code to fix). plan to fix asap :)22:12
devanandagreat22:12
jrolldevananda: not sure if that should be in that patch or a separate one; open to either22:13
devanandajis there a reason your patch tree is based on https://review.openstack.org/#/c/95551/1222:13
devananda*is22:13
jrollyes, we're using instance_info things. maybe that patch isn't needed, but I just grabbed the easy end of that tree22:14
devanandajroll: how is the "factor out small things, keep IPA driver in one big patch" approach working for you guys?22:14
jrolldevananda: working for us, in terms of?22:15
jrolldevananda: this is like... minimum viable patch22:15
devanandajroll: so that patch actually removes backwards compat. there's another patch that makes it better compatibile with icehouse, which would be better to base on22:15
devanandajroll: in terms of being as painless a development process as possible, given that ipa is a work in progress still, from upstream perspective22:16
jrolldevananda: right, so, I based from that patch before that discussion22:16
devanandajroll: indeed. just pointing out that you'll want to NOT depend on 95551, since that won't merge in Juno. K can break compat with I, but J should not.22:16
jrolldevananda: right, I see that now, thanks22:17
jrolloh now we can base on master22:17
jrollyay22:17
* jroll makes a note to rebase eventually22:17
devananda:-)22:17
devanandajroll: so, dev process wise. carrying a long patch tree sucks, I know. Ya'll are doing great work. we talked a while back about things to make your life easier (like squashing the driver into a monolithic patch)22:18
jrollmhmmm, we did that and now we're going to abandon it :P22:19
devanandalol22:19
devanandain favor of?22:19
jrollin favor of this22:19
jrollour monolithic patch had configdrive, decom, long-running agent support, external dhcp support22:19
jrollwhich I'm now writing specs for and putting up as separate patch trees22:20
devanandaah22:20
jroll(which is the only sane thing to do)22:20
jrollbut, were you saying something before that tangent?22:21
devanandai see. two of those (decom, ext dhcp) are immediately things i know other folks want as well22:21
devanandajroll: no, i think that was the tangent i was asking about22:21
devanandathanks22:22
jrollah, ok22:22
devanandaon swift temp urls, have ya'll talked with the oslo team about that?22:22
devanandaor the swift and glance teams?22:22
jrolldevananda: I'm thinking we should prioritize devstack/tempest work before those additional features. agree?22:22
jrollI haven't. JoshNang ?22:22
JoshNangdevananda: not in awhile. not the oslo folks for sure22:23
jrollI think the original plan was, land in ironic and eventually move to oslo22:23
devanandajroll: yea. devstack/tempest coverage will definitely increase the rate folks are willing to review/approve IPA patches and features22:23
JoshNangi think the swift guys said they'd welcome it (probably in swiftclient)22:23
devanandatest driven development and all ...22:23
jrolldevananda: indeed22:23
devanandaJoshNang: right. so if the swift team will accept it in swiftclient, we should just do that22:24
devanandaJoshNang: if not -- if they dont want it and point us to oslo, then we should just land it22:24
devanandalocally and maybe move to oslo that way22:24
devanandabut "land in ironic, move to swiftclient" doesn't make sense22:24
jrollswiftclient is sort of a weird place to put it22:24
jrollbecause it doesn't actually connect to swift22:25
devanandaright22:25
jrolland it accepts a glance uuid, iirc?22:25
JoshNangmaybe oslo is the most sane place, since it needs both glance and swift support22:25
jrollI think that may be the same uuid in swift, though22:25
jrollwell22:25
* dhellmann perks up his ears22:25
jrollit could be in swiftclient, as 'given this swift object id/url, give me temp url'22:26
jrolldhellmann: swift temporary urls. want em? :)22:26
dhellmannis this something more than one project is going to use?22:26
jrollquite possible22:26
devanandadhellmann: most likely, yes22:26
dhellmannand why doesn't it belong in the swift client?22:26
dhellmanndoes it not talk to swift to make the url?22:26
jrollit does not22:26
devanandadhellmann: correct. it does not22:26
JoshNangdhellmann: nope. it uses a shared private secret22:27
dhellmannhow does it make a url?22:27
jrollit basically just signs a url with &22:27
dhellmannshared with whom?22:27
jrolls/&/^/ where ^ points at 'shared secret'22:27
devanandashared with swift22:27
JoshNangthe service making the url and saved in swift22:27
dhellmannso this is a thing our services will use, but is not a thing a cloud user will use?22:27
jrolldhellmann: here's a cli implementation: https://github.com/openstack/swift/blob/master/bin/swift-temp-url22:27
jrolldhellmann: it would be a service/admin things22:27
jroll-s22:27
JoshNangi think its something a cloud user could definitely use22:28
jrolluh22:28
JoshNanghere's a url that expires in x hours22:28
dhellmannwould they have the secret, though?22:28
JoshNangfor a file stored in swift22:28
jrollJoshNang: is that secret per-tenant?22:28
JoshNangyeah i think per tenant22:28
jrollok, so that's reasonable22:28
JoshNangbut yeah, you'd have to be an admin on that tenant to make it.22:28
jrollI'd want to verify that22:28
* jroll hits rax cloud with swift client22:28
devanandathe swifth temp urls can be given to end-users, fwiw22:28
devanandahttp://docs.openstack.org/trunk/config-reference/content/object-storage-tempurl.html22:29
devanandait's not an internal service-only thing22:29
dhellmannthey can be given to end-users, but can an end user make one?22:29
jrolldevananda: right, but would an end user generate one?22:29
devanandathe /generation/ of temp urls is a service thing22:29
devanandaright22:29
jrollif so, yes, probably belongs in switclient22:29
jrollok22:29
devanandaactually, correction22:30
devanandathe generation of a temp url requires privileges to access taht swift object22:30
devanandathe temp url then grants anyone with that url access to that object22:30
devanandait can be done by a user22:30
dhellmannit feels like this should go in swift client, but I agree it should live in a common library somewhere so if they don't want it then I guess we can put it in an oslo module22:31
dhellmanndevananda: I don't see https://github.com/openstack/swift/blob/master/bin/swift-temp-url accessing any remote resources at all22:31
devanandadhellmann: i dont see it doing any access to remote resoruces either22:31
dhellmannalthough I guess it takes the key it needs as input22:31
dhellmannand if you have that key, it implies you have access to the resources22:32
devanandaright22:32
jrollso, afaik, to get the key, a user runs 'swift stat'22:32
jrollI don't seem to be able to do that, on the rax cloud, at least22:32
devanandaso a user who has access to their own objects could create a temp url and give it to someone else to download that object22:32
devanandawithout giving away their credentials22:32
devananda*to their own key22:32
dhellmannok, I still think this fits with the swiftclient best, even though it doesn't actually talk to the service it is doing things with the swift API22:33
jrollyeah22:33
dhellmannbut if the swift team disagrees, we'll find a home for it in oslo22:33
* dhellmann doesn't want an oslo.swift though22:33
JoshNangjroll: http://www.rackspace.com/blog/rackspace-cloud-files-how-to-create-temporary-urls/22:33
devanandaheh22:33
jrolldevananda: is putting a dependency on latest swiftclient ok with you?22:34
jroll(if that code goes to swiftclient)22:34
dhellmannI have to run, but it seems like we're converging on that answer. Let me know if that proves to be wrong.22:34
devanandahm22:34
devanandadhellmann: seems like oslo is the answer to me22:34
jrollJoshNang: cool22:34
jrollheh22:35
devanandadhellmann: given that this feature's existed ins wift for 2+ years22:35
devanandaand it's not in their client yet22:35
openstackgerritJay Faulkner proposed a change to openstack/ironic-python-agent: No longer reccomend use of ipa-advertise-url  https://review.openstack.org/10237122:35
dhellmannwas it rejected, or did they just not implement it?22:35
devanandadhellmann: i'll punt that to notmyname22:36
devanandadhellmann: anyhow, thanks. catch you later22:36
JoshNangi'll go see if i can get it in swiftclient, failing that oslo22:36
dhellmannwfm22:37
jrollthanks, JoshNang22:37
jrolldhellmann: thanks for the help :)22:37
openstackgerritJay Faulkner proposed a change to openstack/ironic-python-agent: No longer reccomend use of ipa-advertise-url  https://review.openstack.org/10237122:37
dhellmannjroll: any time22:37
JoshNangid still like about half that code to land in ironic though. the stuff that pulls the url/creates the url from the direct url seems to make sense there. and a place to stash the shared key in the conf file22:37
JayFjroll: ^ h822:37
jrollJayF: yeah well, grammar22:37
JayFjroll: I know, but it's better now22:38
JayFjroll: lets test this stuff, I have only a few minutes before my next session and I want to see it work :)22:38
jrollI +2'd22:38
jrollidk what you want me to do22:38
JayFjroll: prod JoshNang22:38
jrollnou22:38
* JayF prods JoshNang to +2 +A https://review.openstack.org/102371 to test IPA builder post joerb22:38
jrolloh wait22:38
jrolls/reccomend/recommend22:38
jrollin commit title22:38
jroll:)22:39
JayFI fixed it as well22:39
jrolluh no?22:39
jrollI see reccomend22:39
JayFjroll: https://review.openstack.org/#/c/102371/1..2//COMMIT_MSG22:39
jrollit's fine, unless you happen to push another22:39
JoshNang weird22:39
jrollJayF: commit title22:39
JayFoh bollocks22:39
openstackgerritAdam Gandelman proposed a change to openstack/ironic: Update Nova's available resources at termination  https://review.openstack.org/10237322:39
jrollit's fine22:39
JoshNang:D22:39
jrolljust... ship it22:39
JayFfixed it22:40
openstackgerritJay Faulkner proposed a change to openstack/ironic-python-agent: No longer recommend use of ipa-advertise-url  https://review.openstack.org/10237122:40
jroll+A22:40
jrollI'm not waiting for someone else for that.22:40
JayFfair22:40
JoshNangJayF: heh i +A'ed like a sec before you re-committed22:40
JoshNangand now its double +A'ed22:40
devanandaworth calling out to ya'll there's an eventlet bug cropping up22:43
jrolluh oh22:43
devanandamost notably with the ssh driver and any parallelism, but, apparently, also with our use of qemu image utils in the pxe driver22:43
devanandaI dunno if it would affect IPA yet22:44
devanandasee the ML post this morning about it22:44
jrolloh, right22:44
jrollmorgabra has had pain with paramiko not closing connections to switches22:44
devanandaright22:44
devanandapossibly the same thing22:44
devanandaalso -- SSH'ing into switches? ugh :(22:44
jrollfyi, on swift temp urls: 15:42:23     +torgomatic | jroll: could be useful to have; I'm neutral on the topic (but I've given it only a second or two of thought)22:44
jrolldevananda: that's how cisco switches work :(22:45
devanandajroll: :( :(22:45
jrolldevananda: want to quit and go build reasonable switch software? :)22:45
jrollJoshNang: see the swift thing I posted about 5 lines up ^22:45
NobodyCambrb ...fft22:46
JoshNangon the topic of broken packages, we ran into some bugs with sql-alchemy 0.9.5. can't remember if that was brought up in this channel or not. apparently nova hit them already too22:46
JoshNangjroll: ha you beat me to the swift room by like 30s22:46
*** boris-42 has quit IRC22:46
*** romcheg has joined #openstack-ironic22:46
jroll15:46:12      +notmyname | jroll: you had me at "we're happy to write the code" ;-)22:47
jrolleasy enough22:47
JoshNangsweet. i'll throw up a patch shortly.22:47
devanandaMikhail_D_wk: hi! want to ping you re your tempest API work here: https://review.openstack.org/#/c/71476/22:48
jrollJoshNang: I just saw https://review.openstack.org/#/c/102306/22:49
jrollJoshNang: so, I'm in progress on a spec for "support long-running deploy ramdisks"... which includes this22:49
devanandaMikhail_D_wk: we're moving all the tempest baremetal api tests under /admin/ as requested by QA team -- patch is here: https://review.openstack.org/#/c/100989/ -- these may conflict since your patch is addign a new file22:49
JoshNangjroll: ah. i had figured that's what prompted the thoughts on power status22:49
jrollJoshNang: yeahhhhhh. trying to decide if I should trump yours or go side by side or what22:50
*** eghobo has quit IRC22:50
JayFI vote jroll's trumps JoshNang's22:50
jrollmine is also only 30% done or so22:51
*** Penick has quit IRC22:51
JayFthen shamelessly steal JoshNang's work, like a true genius22:51
jrollI'm just going to start riding bart for like, 4-6 hours a day. I've been trying to work on this spec all day - as opposed to finishing an entire spec on the train this morning22:51
JoshNang:O22:51
*** romcheg has quit IRC22:52
JoshNangjroll: frankly i like it going in validation22:52
JoshNangthere's cooler things we can do in there22:52
jrollheh, ok22:52
jrollyeah22:52
jrolllike, 'drivers figure out whatever the heck they want in validation'22:53
JoshNang+122:53
adam_gNobodyCam, did you ever figure out if it was the same bug you were hitting with other drivers? re https://review.openstack.org/#/c/91719/22:57
*** Penick has joined #openstack-ironic22:58
NobodyCamlooks22:58
NobodyCamadam_g: it was "other"22:59
*** boris-42 has joined #openstack-ironic23:02
adam_gNobodyCam, ah, ok23:03
NobodyCam:-p23:06
*** Penick has quit IRC23:11
*** ifarkas has quit IRC23:13
devanandaadam_g: what do you think of a tempest config option to disable all the admin/* tests23:13
adam_gdevananda, what for?23:14
devanandaadam_g: let's say I am running a "bare metal cloud" and you want to test that cloud for feature compatibility23:15
openstackgerritA change was merged to openstack/ironic-python-agent: No longer recommend use of ipa-advertise-url  https://review.openstack.org/10237123:15
devanandaadam_g: you won't have access to ironic's API to perform any CRUD operations23:15
devanandaadam_g: but you still want to run the scenario tests23:15
devanandaadam_g: or let's say that I want to run those internally and publish the results, but I haven't enabled the "fake" driver -- so creating a ndoe with test-generated (fake) data is going to cause my conductors to spew errors23:16
jrolloh god we're creating work for people now23:16
adam_gdevananda, you'd just exclude those tests or run the individual tests you are interested in via testr or whatever runner23:16
devanandajroll: LOL23:17
jroll:D23:17
devanandaadam_g: that's what i mean. there's no way to exclude those tests, afaict, today23:17
adam_gdevananda, oh actually23:18
devanandaadam_g: if you enable ironic's tests, you get, at minimum, all the api tests. and if you set [baremeta] driver_enabled=True, ten you also get the scenario tests23:18
devanandaor have I misunderstood23:18
*** Penick has joined #openstack-ironic23:18
adam_gdevananda, admin tests would be skipped if tempest.conf didnt have proper admin crednetials defined23:18
devanandaadam_g: oh23:18
devanandaneat23:18
devanandaadam_g: anyhow, take a look at my comment on https://review.openstack.org/#/c/74065/11 when you get a moment23:19
adam_gdevananda, speaking of the crud tests + fake driver.. having spent some time in the nova API tests, i think making those support running against real drivers would not be against precedent23:19
devanandaadam_g: um... that doesn't make any sense to me. how?23:19
adam_gdevananda, most of the current API tests depend on real drivers23:19
devanandaadam_g: a real virt driver != a real bare metal driver with a real piece of hardware23:20
adam_gdevananda, maybe not in the case of devstack-gate23:21
devanandaadam_g: you're thinking of third party CI with real hardware?23:21
adam_gdevananda, no, just the fact that the baremetal tests are the only API tests relying on a fake driver, and thats caused some concern among the tempest folk. the idea that the API tests should run against any cloud regardless of configured driver23:22
devanandaadam_g: i think that's a messaging failure on our part, which i'm happy to help clarify23:23
devanandain part, moving those tests to /admin/ should help, i think23:23
devanandaand my suggestion on 74065 should help, too23:23
adam_gdevananda, see matt's comments @ https://review.openstack.org/#/c/100989/1..1/tempest/api/baremetal/README.rst23:23
devanandaadam_g: is there a ML thread? if not, care to start one?23:23
*** mdorman has quit IRC23:23
* devananda looks23:24
devanandaahh23:24
*** eghobo has joined #openstack-ironic23:24
devanandayah. misunderstanding about what it means to "use ironic"23:24
devananda"functional verification of my OpenStack deployment with Ironic" ===>> the scenario tests which exercise the Nova API23:25
*** eghobo has quit IRC23:25
*** eghobo has joined #openstack-ironic23:25
adam_gdevananda, your comments on 74065 sort of relate to what i was proposing to matt. we update the tempest CRUD tests to support, say, testing against pxe_ipmi provided the admin makes details of the available nodes available somehow. default staying fake with no additional data requirements23:29
devanandaadam_g: what will that API test actually do?23:30
devanandaadam_g: i mean, if I supply tempest with IPMI creds for a unit of hardware, what will the tempest CRUD tests do that is any different than if it had the fake driver?23:31
adam_gdevananda, the same thing they'd do with the fake driver, except they'd actually pass without conductor spewing errors,  in case someone actually wanted to go through the trouble of running them with the non-default fake.23:33
devanandaadam_g: what is the purpose? what additional functionality would be getting tested from the API side?23:34
adam_gdevananda, nothing. :) i'm just thinking out loud as to how we can help make it all fit better within the context of tempest.23:35
devanandaadam_g: incidentally, running this against an operational cloud would mean the operator must first delete a node from that cloud ....23:35
devanandaadam_g: which probably isn't something folks are thinking about23:35
takadayuikodevananda: Hi, sorry for late reply. I went home and slept :P23:36
devanandaadam_g: or having additional hardware accessible by ironic, in that cloud, that isn't available for the cloud itself, which seems just as odd23:36
adam_gdevananda, yeah.23:36
takadayuikodevananda: I did baremetal provisioning using command "ironic node-set-provision-state" and I failed last week but I've succeed :)23:38
devanandatakadayuiko: not using "nova boot"?23:39
takadayuikodevananda: No, just using "node-set-provision-state" without "nova boot".23:40
devanandatakadayuiko: are you using neutron, or external dhcp, or ...?23:41
takadayuikodevananda: I did that reffering this blog. http://ma.ttwagner.com/bare-metal-deploys-with-devstack-and-ironic/23:41
takadayuikotakadayuiko: Yes, using neutron, dnsmasq(not external DHCP server)23:42
devanandatakadayuiko: ok, so that blog post describes using external dnsmasq (not neutron) to serve images23:43
*** Penick has quit IRC23:45
devanandatakadayuiko: when using "nova boot", nova will coordinate with neutron to set up DHCP for the instance. that blog describes some steps to do this manually. anyhow, I'm glad to hear you got node-set-provision-state working!23:45
devanandamatty_dubs|gone: ^ you may want to update your blog post there with the new option :)23:45
devanandaI should also be tagging a new release of the client this week to get that option into pip, fwiw23:46
takadayuikodevananda: Oh, I misunderstood. I thought my neutron was used... following the blog, I killed the process of originally dnsmasq and I booted dnsmasq independently. Is that reason why "No VIFs found for node xxx" error message was shown?23:46
devanandayes23:46
takadayuikodevananda: Ah, thank you. I could check Ironic works well, so I'll try to use Ironic via Nova :)23:48
devanandatakadayuiko: when nova handles the deployment, it coordinates between neutron VIF and physical port in Ironic. see https://github.com/openstack/ironic/blob/master/ironic/nova/virt/ironic/driver.py#L61323:48
*** Penick has joined #openstack-ironic23:52
takadayuikodevananda: Thank you so much :)23:53
jrolldevananda, adam_g, I'd really love for infra to have a pool of BM nodes for "real" tempest testing23:53
NobodyCamjroll: sound like a great third party test! have a spare raq?23:54
jrollunfortunately, no, not right now :(23:55
NobodyCamhehehe23:55
jrollwe do have a QE environment23:55
jrollfor both nova and ironic23:55
JayFWe tried to do third party CI for the IPA build, was going to use one of our OnMetal nodes for it and everything :)23:55
JayFbut instead we're actually integrated with -infra23:56
jrolland I still don't understand why rax doesn't submit third party CI results for nova (and now for ironic)23:56
JayF(assuming this build finally works, zuul queued it for the first time just now)23:56
JoshNangJayF: \o/23:56
jrollJayF: we should still do third-party CI for the agent_* drivers, at the very least23:56
jrollJayF: I would even argue for all the drivers23:56
jrollJayF: but I'm not the one paying for hardware :)23:57
devanandaadam_g: another problem -- as soon as tempest enrolled any real hardware, nova would be able to consume it, yanking it out of tempest's hands23:57
devanandaadam_g: and leading to random failures of the tempest tests -- and of nova23:57
*** harlowja_ has joined #openstack-ironic23:58
jrolldevananda: how... does that wokr?23:58
jrollwork23:58
devanandajroll: it doesn't23:58
jrollI mean, how does nova just take over the hardware?23:58
devanandajroll: the context is: point tempest at ironic in a running cloud. run CRUD tests against ironic's API.23:59
devanandamy point is, as soon as you create a resource in ironic, nova may see it23:59
devanandaand if a user of that cloud says "nova boot" the scheduler could pick the node you just added23:59
jrolldevananda: oh. no. why would you point it at a running cloud that others might use :|23:59
devanandaand then the tempest test is goign to be mighty confused23:59
NobodyCamI'm sure I have some old cobalt raq's (http://www.tech.proact.co.uk/i/sun_cobalt_raq_550.jpg) I could lend.23:59
jrolldevananda: just... make a cell23:59

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