Tuesday, 2014-07-15

devanandahm? was on a call00:03
jrolldon't look up00:03
devanandaNobodyCam: so a scheduler hint to Nova based on chassis_id -- that's fine.00:04
devanandaheh, too late00:04
* devananda starts sharpening a knife00:04
NobodyCamjroll: Shrews: easy +a on for ironicclient.. https://review.openstack.org/#/c/91585 <- only 600 lines...00:04
jrolllol00:04
NobodyCamoh00:04
NobodyCamlol00:04
NobodyCamjroll: it has two +2 now00:05
NobodyCam(thats the easy part) lol00:05
jrolldefinitely not in a good place to read 600 loc right now00:05
NobodyCam:)00:06
NobodyCamit is o-beer-o-clock here in seattle00:06
jrollindeed00:07
lifelessis the cache layer in ironic on by default?00:07
lifelessI'm seeing qemu-img converts when deploying the same image a few minutes apart00:08
lifelessmaking me wonder if there is a bug somewhere00:08
*** Penick has quit IRC00:08
jrolllifeless: might be some bad defaults for cache size/ttl00:08
lifelesshahahaha00:10
lifeless# Maximum size (in MiB) of cache for master images, including00:10
lifeless# those in use (integer value)00:10
lifeless#image_cache_size=102400:10
lifelesslet me just fix that00:10
jroll:)00:10
lifelessreally we should make it like 30% of the partition its on or something00:11
lifelessbut for now, uh, 20GB sound ok?00:11
jrollI don't care, I don't use that cache :)00:11
jrollsounds reasonable00:12
devanandasure00:13
openstackgerritlifeless proposed a change to openstack/ironic: Set a more generous default image cache size  https://review.openstack.org/10690500:14
NobodyCamlifeless: thank you for the . too in that ^^^ :)00:16
openstackgerritlifeless proposed a change to openstack/ironic: Push the image cache ttl way up  https://review.openstack.org/10690600:21
lifelessand the 106905 one is kinda urgent - its actually default to smaller than a single tripleo image00:23
*** hemna is now known as hemna__00:23
lifelessso we were rebuilding images multiple times in a single cluster deploy00:23
lifelesswhich is a pretty bad performance impact00:23
jrollyou can set the option in the meantime, no?00:24
JayFlifeless: why 10080 minutes as the TTL?00:24
JayFlifeless: just seems arbitrary? Not really a magic number I'd be used to seeing somewhere like there :)00:25
lifelessjroll: yes but we try to run defaults :)00:25
JayF168 hours :)00:25
lifelessJayF: 60*24*700:25
lifeless1008000:25
JayFoh. 7 weeks.00:25
JayFer00:25
JayFyeah00:25
JayFOK, I agree00:25
jrolllifeless: sure thing00:25
jroll:)00:25
lifeless60 minutes -> 1 hr; 24 hrs -> 1 day; 7 days -> 1 week00:25
mrdaSounds like a comment is needed :)00:25
JayFmrda: or I need to math harder :)00:26
JayFlifeless: you have +1 from me on both of those, seem like reasonable default changes :)00:26
mrdaif it's not immediately obvious...00:26
* JayF <3 good defaults00:26
lifelessif I had more time I'd doa  patch to make 0 as ttl mean 'disabled'00:26
jrollI'm +1 on adding a comment00:26
lifelesslet me do that00:26
mrda\o/00:26
openstackgerritlifeless proposed a change to openstack/ironic: Push the image cache ttl way up  https://review.openstack.org/10690600:27
NobodyCamlifeless: 106905 has pep8 failure :(00:29
rlooNobodyCam: wrt 91585 & sort order. up to user to do the wrong, err right thing. if they're using marker, presumably they'd use the same sort order throughout :-)00:29
jrolllol00:29
jrollso much for quick patches00:29
*** rloo has quit IRC00:35
devanandaright - i've gotta finish a few things... see ya'll tmw!00:46
openstackgerritlifeless proposed a change to openstack/ironic: Set a more generous default image cache size  https://review.openstack.org/10690500:54
openstackgerritlifeless proposed a change to openstack/ironic: Push the image cache ttl way up  https://review.openstack.org/10690600:55
*** nosnos has quit IRC01:13
*** eguz has joined #openstack-ironic01:38
*** eghobo has quit IRC01:42
*** eguz has quit IRC02:15
*** pcrews has quit IRC02:16
*** dwalleck has joined #openstack-ironic02:17
openstackgerritJosh Gachnang proposed a change to openstack/ironic-python-agent: Add versioning to Agent decommission  https://review.openstack.org/10685902:22
*** dwalleck has quit IRC02:26
*** openstackgerrit has quit IRC02:42
*** mdorman has quit IRC02:42
*** morgabra has quit IRC02:42
*** morgabra has joined #openstack-ironic02:43
*** openstackgerrit has joined #openstack-ironic02:44
*** mdorman has joined #openstack-ironic02:46
*** bvivek has joined #openstack-ironic02:46
*** ramineni has joined #openstack-ironic02:51
*** Haomeng has joined #openstack-ironic02:53
*** harlowja is now known as harlowja_away02:54
*** harlowja_away is now known as harlowja02:58
*** vinbs has joined #openstack-ironic02:59
*** bvivek has quit IRC03:00
*** eghobo has joined #openstack-ironic03:11
*** mdorman has quit IRC03:12
*** Shrews has quit IRC03:12
*** anteaya has quit IRC03:12
*** zul has quit IRC03:12
*** Haomeng has quit IRC03:12
*** openstackgerrit has quit IRC03:12
*** yuriyz has quit IRC03:12
*** kevinbenton has quit IRC03:12
*** gilliard has quit IRC03:12
*** coolsvap has quit IRC03:12
*** davidlenwell has quit IRC03:12
*** radsy has quit IRC03:12
*** krtaylor has quit IRC03:12
*** chuckC has quit IRC03:12
*** mikal has quit IRC03:12
*** ekarlso has quit IRC03:12
*** mkerrin has quit IRC03:12
*** NobodyCam has quit IRC03:12
*** GheRivero has quit IRC03:12
*** zer0c00l has quit IRC03:12
*** boris-42 has quit IRC03:12
*** dtantsur|afk has quit IRC03:12
*** romcheg has quit IRC03:12
*** hemna__ has quit IRC03:12
*** zigo has quit IRC03:12
*** adam_g has quit IRC03:12
*** aignatov has quit IRC03:12
*** Isotopp has quit IRC03:12
*** aweeks has quit IRC03:12
*** mgagne has quit IRC03:12
*** BadCub_ has quit IRC03:12
*** enikanorov_ has quit IRC03:12
*** lynxman has quit IRC03:12
*** agordeev has quit IRC03:12
*** LiveOne has quit IRC03:12
*** comstud has quit IRC03:12
*** Mikhail_D_wk1 has quit IRC03:12
*** stevebaker has quit IRC03:12
*** dguerri has quit IRC03:12
*** soren has quit IRC03:12
*** morgabra has quit IRC03:12
*** lazy_prince has quit IRC03:12
*** ifarkas has quit IRC03:12
*** tteggel has quit IRC03:12
*** keekz has quit IRC03:12
*** Ng has quit IRC03:12
*** ramineni has quit IRC03:17
*** ramineni has joined #openstack-ironic03:17
*** jrist has quit IRC03:18
*** jrist has joined #openstack-ironic03:20
*** Haomeng has joined #openstack-ironic03:20
*** openstackgerrit has joined #openstack-ironic03:20
*** morgabra has joined #openstack-ironic03:20
*** radsy has joined #openstack-ironic03:20
*** lazy_prince has joined #openstack-ironic03:20
*** Shrews has joined #openstack-ironic03:20
*** krtaylor has joined #openstack-ironic03:20
*** yuriyz has joined #openstack-ironic03:20
*** dtantsur|afk has joined #openstack-ironic03:20
*** romcheg has joined #openstack-ironic03:20
*** ifarkas has joined #openstack-ironic03:20
*** chuckC has joined #openstack-ironic03:20
*** boris-42 has joined #openstack-ironic03:20
*** hemna__ has joined #openstack-ironic03:20
*** kevinbenton has joined #openstack-ironic03:20
*** ekarlso has joined #openstack-ironic03:20
*** gilliard has joined #openstack-ironic03:20
*** zigo has joined #openstack-ironic03:20
*** coolsvap has joined #openstack-ironic03:20
*** davidlenwell has joined #openstack-ironic03:20
*** mikal has joined #openstack-ironic03:20
*** zer0c00l has joined #openstack-ironic03:20
*** GheRivero has joined #openstack-ironic03:20
*** NobodyCam has joined #openstack-ironic03:20
*** mkerrin has joined #openstack-ironic03:20
*** comstud has joined #openstack-ironic03:20
*** agordeev has joined #openstack-ironic03:20
*** lynxman has joined #openstack-ironic03:20
*** LiveOne has joined #openstack-ironic03:20
*** enikanorov_ has joined #openstack-ironic03:20
*** BadCub_ has joined #openstack-ironic03:20
*** aweeks has joined #openstack-ironic03:20
*** mgagne has joined #openstack-ironic03:20
*** Isotopp has joined #openstack-ironic03:20
*** aignatov has joined #openstack-ironic03:20
*** adam_g has joined #openstack-ironic03:20
*** soren has joined #openstack-ironic03:20
*** dguerri has joined #openstack-ironic03:20
*** stevebaker has joined #openstack-ironic03:20
*** Mikhail_D_wk1 has joined #openstack-ironic03:20
*** Ng has joined #openstack-ironic03:20
*** keekz has joined #openstack-ironic03:20
*** tteggel has joined #openstack-ironic03:20
*** anteaya has joined #openstack-ironic03:20
*** zul has joined #openstack-ironic03:20
*** mdorman has joined #openstack-ironic03:22
*** ramineni has quit IRC03:23
*** ramineni has joined #openstack-ironic03:23
*** mdorman has quit IRC03:24
openstackgerritMichael Davies proposed a change to openstack/ironic: Ironic nova driver to cache ironic client calls  https://review.openstack.org/10269503:56
*** bmahalakshmi has joined #openstack-ironic03:59
*** nosnos has joined #openstack-ironic04:01
*** sabah has joined #openstack-ironic04:17
*** subah has joined #openstack-ironic04:18
*** sabah has quit IRC04:21
*** subah has quit IRC04:25
*** k4n0 has joined #openstack-ironic04:27
*** Nisha has joined #openstack-ironic04:44
*** vinbs has quit IRC04:55
*** vinbs has joined #openstack-ironic04:55
*** eghobo has quit IRC05:02
*** bvivek has joined #openstack-ironic05:06
*** eghobo has joined #openstack-ironic05:12
openstackgerritMichael Davies proposed a change to openstack/ironic: Ironic nova driver to cache ironic client calls  https://review.openstack.org/10269505:12
*** radsy has quit IRC05:28
*** shausy has joined #openstack-ironic05:30
*** Haomeng has quit IRC05:35
*** eghobo has quit IRC05:35
*** eghobo has joined #openstack-ironic05:35
*** lazy_prince is now known as killer_prince05:38
*** killer_prince is now known as lazy_prince05:39
*** rameshg87_afk is now known as rameshg8705:42
*** eguz has joined #openstack-ironic05:43
*** eghobo has quit IRC05:45
openstackgerritZhongyue Luo proposed a change to openstack/ironic: Moves node resource tests to a separate testcase  https://review.openstack.org/10693305:45
*** harlowja is now known as harlowja_away05:49
*** Haomeng has joined #openstack-ironic05:55
*** chuckC has quit IRC05:59
*** jcoufal has joined #openstack-ironic06:03
*** eguz has quit IRC06:05
*** eghobo has joined #openstack-ironic06:05
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic: Imported Translations from Transifex  https://review.openstack.org/10694806:10
*** pradipta has joined #openstack-ironic06:20
*** lazy_prince has quit IRC06:31
*** nosnos has quit IRC06:32
*** bmahalakshmi has quit IRC06:32
*** bmahalakshmi has joined #openstack-ironic06:38
*** eguz has joined #openstack-ironic06:40
*** eghobo has quit IRC06:44
*** geekyogi has joined #openstack-ironic06:48
*** geekyogi has quit IRC06:48
*** geekyogi has joined #openstack-ironic06:49
*** eguz has quit IRC06:51
*** Mikhail_D_ltp has joined #openstack-ironic07:04
*** killer_prince has joined #openstack-ironic07:05
*** killer_prince is now known as lazy_prince07:05
*** rameshg87 has quit IRC07:12
*** rameshg87 has joined #openstack-ironic07:13
*** viktors has joined #openstack-ironic07:22
*** jistr has joined #openstack-ironic07:30
*** foexle has joined #openstack-ironic07:30
*** pradipta is now known as pradipta_away07:30
openstackgerritGhe Rivero proposed a change to openstack/ironic: oslo.i18n migration  https://review.openstack.org/10513207:32
*** bvivek has quit IRC07:47
openstackgerritZhongyue Luo proposed a change to openstack/ironic: Moves node resource tests to a separate testcase  https://review.openstack.org/10693307:47
*** derekh_ has joined #openstack-ironic08:01
openstackgerritGhe Rivero proposed a change to openstack/ironic: oslo.i18n migration  https://review.openstack.org/10513208:13
*** ndipanov_gone is now known as ndipanov08:18
*** athomas has joined #openstack-ironic08:19
*** romcheg1 has joined #openstack-ironic08:20
*** bvivek has joined #openstack-ironic08:21
*** lazy_prince has quit IRC08:21
dtantsur|afkLate morning, Ironic08:24
*** dtantsur|afk is now known as dtantsur08:24
*** lucasagomes has joined #openstack-ironic08:29
*** killer_prince has joined #openstack-ironic08:29
*** killer_prince is now known as lazy_prince08:30
yuriyzmorning Ironic dtantsur08:31
dtantsuryuriyz, morning :)08:31
*** geekyogi has quit IRC08:32
dtantsurFolks, do you think we require a spec for this https://review.openstack.org/#/c/106905 and https://review.openstack.org/#/c/106906/ ?08:32
dtantsurlifeless, ^^^08:32
lifelessdtantsur: if you want one, but really?08:33
lifelessdtantsur: the initial numbers were AFAICT completely arbitrary, so are these, but they are based on using the code and finding it lacking08:34
dtantsurlifeless, I just don't know, whether these values are ok for everyone (initial are really arbitrary - I'm the author :)08:34
lifelessdtantsur: they probably aren't, which is why they are configurable, but do you know anyone that can buy a hard disk with < 20G of space nowadays? :)08:35
dtantsurheh08:35
mrdaNight Ironic!08:35
dtantsurnight, mrda!08:35
*** mrda is now known as mrda-away08:35
lifelessdtantsur: so, if we want more ops input, we should probably ask on the operators list about folks feelings08:35
lifelessdtantsur: however AFAICT there are three production deploys of Ironic, - Helion (in various places), TripleO-test-cluster, and OnMetal which doesn't use the cache at all.08:36
dtantsurlifeless, well, 20G and 1 week make sense to me08:37
lifelessdtantsur: so I'm not at all sure we'll get any useful responses, and I can speak for both Helion and TripleO to say that 20G is (probably) big enough - I'd be happy to make it bigger but worried about folk with smaller test VMs08:37
dtantsurlucasagomes, yuriyz are you ok with it ^^^? I am mostly convinced08:37
yuriyzI think 8-10GB OK08:38
dtantsurhmmm... lifeless, it looks like we don't have an easy agreement... What about making a spec?08:39
yuriyzand agree with lifeless for 1 week ttl08:40
*** igordcard has joined #openstack-ironic08:40
dtantsurbrb, let me know what you agree on08:40
lifelessyuriyz:08:42
lifelessroot@undercloud-undercloud-my4eb7s2dhzt:~# ls /mnt/state/var/lib/ironic/master_images/ -lh08:42
lifelesstotal 5.8G08:42
lifeless-rw-r--r-- 1 ironic ironic 3.4G Jul 14 23:58 2000e9f4-7df8-420e-a295-157fcbae687508:42
lifeless-rw-r--r-- 1 ironic ironic 6.2G Jul 15 00:56 31274650-f121-4ba2-9aa3-88576ad7b69008:42
lifelessyuriyz: now I look, I'm thinking 20G might be too small still08:42
lifelessyuriyz: 8-10GB is totally useless08:42
yuriyzhm I see that you are right08:43
lifelesssee the 5.8G total vs image sizes08:43
lifelesssparse files08:43
lifelessbut the cache sums the stats, so it gets apparent size08:44
lifelesslike I alluded to in the patch, if I had time I'd make it possible to disable the ttl08:44
lifelessimage ids are write-once there's no use case for expiring content on age08:45
yuriyzlifeless, agree we should use production-ready defaults08:47
* lucasagomes reads08:48
lucasagomeswell... yeah we have this consensus of having production-ready defaults in openstack so 20GB doesn't seems exorbitant08:50
lucasagomeson the tests VMs we can document/change devstack to tune down those values08:51
lifelesslucasagomes: I'm actually thinking 40GB might be better, and tune down the values in devtests's seed. but yeah, 1G was too small :>08:55
lucasagomeslifeless, I don't think I have parameter to object it... You guys are running it in production and figuring out what would be a sane default for it, thanks08:59
lucasagomesand yeah, thinking now 1GB may be way too small, at the begging it sounded like reasonable starting point heh09:00
*** romcheg1 has quit IRC09:05
*** pelix has joined #openstack-ironic09:11
*** martyntaylor has joined #openstack-ironic09:24
*** geekyogi has joined #openstack-ironic09:27
*** romcheg1 has joined #openstack-ironic09:30
*** igordcard has quit IRC09:32
*** Alexei_987 has joined #openstack-ironic09:39
*** Nisha has quit IRC09:43
*** bmahalakshmi has quit IRC09:55
*** geekyogi has quit IRC09:55
*** shausy has quit IRC09:55
*** k4n0 has quit IRC09:55
*** Shrews has quit IRC09:55
*** anteaya has quit IRC09:55
*** zul has quit IRC09:55
*** Haomeng has quit IRC09:55
*** lucasagomes has quit IRC09:56
*** openstackgerrit has quit IRC09:56
*** yuriyz has quit IRC09:56
*** kevinbenton has quit IRC09:56
*** gilliard has quit IRC09:56
*** coolsvap has quit IRC09:56
*** davidlenwell has quit IRC09:56
*** vinbs has quit IRC09:56
*** jrist has quit IRC09:56
*** krtaylor has quit IRC09:56
*** viktors has quit IRC09:56
*** mikal has quit IRC09:56
*** ekarlso has quit IRC09:56
*** pradipta_away has quit IRC09:56
*** mkerrin has quit IRC09:56
*** NobodyCam has quit IRC09:56
*** GheRivero has quit IRC09:56
*** zer0c00l has quit IRC09:56
*** boris-42 has quit IRC09:56
*** romcheg1 has quit IRC09:56
*** bvivek has quit IRC09:56
*** athomas has quit IRC09:56
*** Mikhail_D_ltp has quit IRC09:56
*** dtantsur has quit IRC09:56
*** romcheg has quit IRC09:56
*** hemna__ has quit IRC09:56
*** zigo has quit IRC09:56
*** adam_g has quit IRC09:56
*** aignatov has quit IRC09:56
*** Isotopp has quit IRC09:56
*** aweeks has quit IRC09:56
*** mgagne has quit IRC09:56
*** BadCub_ has quit IRC09:56
*** enikanorov_ has quit IRC09:56
*** lynxman has quit IRC09:56
*** agordeev has quit IRC09:56
*** LiveOne has quit IRC09:56
*** comstud has quit IRC09:56
*** Mikhail_D_wk1 has quit IRC09:56
*** stevebaker has quit IRC09:56
*** dguerri has quit IRC09:56
*** soren has quit IRC09:56
*** martyntaylor has quit IRC09:56
*** lazy_prince has quit IRC09:56
*** jistr has quit IRC09:56
*** jcoufal has quit IRC09:56
*** morgabra has quit IRC09:56
*** ifarkas has quit IRC09:56
*** tteggel has quit IRC09:56
*** keekz has quit IRC09:56
*** Ng has quit IRC09:56
*** pelix has quit IRC09:56
*** pleia2 has quit IRC09:56
*** mmitchell_ has quit IRC09:56
*** Alexei_987 has quit IRC09:56
*** foexle has quit IRC09:56
*** ramineni has quit IRC09:56
*** rwsu has quit IRC09:56
*** mrda-away has quit IRC09:56
*** rch has quit IRC09:56
*** antonym has quit IRC09:56
*** wendar has quit IRC09:56
*** jroll has quit IRC09:56
*** toabctl has quit IRC09:56
*** d0ugal has quit IRC09:56
*** dhellmann has quit IRC09:56
*** JoshNang has quit IRC09:56
*** derekh_ has quit IRC09:56
*** rameshg87 has quit IRC09:56
*** datajerk has quit IRC09:56
*** annegentle has quit IRC09:56
*** notq has quit IRC09:56
*** sbadia has quit IRC09:56
*** sirushti has quit IRC09:56
*** SpamapS has quit IRC09:56
*** steveh has quit IRC09:56
*** proffalken has quit IRC09:56
*** devananda has quit IRC09:56
*** kylestev has quit IRC09:56
*** russell_h has quit IRC09:56
*** matty_dubs|gone has quit IRC09:56
*** pquerna has quit IRC09:56
*** Madasi has quit IRC09:56
*** harlowja_away has quit IRC09:56
*** JoshNang has joined #openstack-ironic10:03
*** dhellmann has joined #openstack-ironic10:03
*** toabctl has joined #openstack-ironic10:03
*** jroll has joined #openstack-ironic10:03
*** wendar has joined #openstack-ironic10:03
*** antonym has joined #openstack-ironic10:03
*** d0ugal has joined #openstack-ironic10:03
*** rch has joined #openstack-ironic10:03
*** mrda-away has joined #openstack-ironic10:03
*** rwsu has joined #openstack-ironic10:03
*** foexle has joined #openstack-ironic10:03
*** mmitchell_ has joined #openstack-ironic10:03
*** pleia2 has joined #openstack-ironic10:03
*** pelix has joined #openstack-ironic10:03
*** athomas has joined #openstack-ironic10:03
*** ramineni has joined #openstack-ironic10:03
*** Alexei_987 has joined #openstack-ironic10:03
*** romcheg1 has joined #openstack-ironic10:03
*** geekyogi has joined #openstack-ironic10:03
*** lazy_prince has joined #openstack-ironic10:03
*** lucasagomes has joined #openstack-ironic10:03
*** bvivek has joined #openstack-ironic10:03
*** jistr has joined #openstack-ironic10:03
*** viktors has joined #openstack-ironic10:03
*** Mikhail_D_ltp has joined #openstack-ironic10:03
*** bmahalakshmi has joined #openstack-ironic10:03
*** pradipta_away has joined #openstack-ironic10:03
*** jcoufal has joined #openstack-ironic10:03
*** Haomeng has joined #openstack-ironic10:03
*** shausy has joined #openstack-ironic10:03
*** vinbs has joined #openstack-ironic10:03
*** k4n0 has joined #openstack-ironic10:03
*** zul has joined #openstack-ironic10:03
*** anteaya has joined #openstack-ironic10:03
*** tteggel has joined #openstack-ironic10:03
*** keekz has joined #openstack-ironic10:03
*** Ng has joined #openstack-ironic10:03
*** Mikhail_D_wk1 has joined #openstack-ironic10:03
*** stevebaker has joined #openstack-ironic10:03
*** dguerri has joined #openstack-ironic10:03
*** soren has joined #openstack-ironic10:03
*** adam_g has joined #openstack-ironic10:03
*** aignatov has joined #openstack-ironic10:03
*** Isotopp has joined #openstack-ironic10:03
*** mgagne has joined #openstack-ironic10:03
*** aweeks has joined #openstack-ironic10:03
*** BadCub_ has joined #openstack-ironic10:03
*** enikanorov_ has joined #openstack-ironic10:03
*** LiveOne has joined #openstack-ironic10:03
*** lynxman has joined #openstack-ironic10:03
*** agordeev has joined #openstack-ironic10:03
*** comstud has joined #openstack-ironic10:03
*** mkerrin has joined #openstack-ironic10:03
*** NobodyCam has joined #openstack-ironic10:03
*** GheRivero has joined #openstack-ironic10:03
*** zer0c00l has joined #openstack-ironic10:03
*** mikal has joined #openstack-ironic10:03
*** davidlenwell has joined #openstack-ironic10:03
*** coolsvap has joined #openstack-ironic10:03
*** zigo has joined #openstack-ironic10:03
*** gilliard has joined #openstack-ironic10:03
*** ekarlso has joined #openstack-ironic10:03
*** kevinbenton has joined #openstack-ironic10:03
*** hemna__ has joined #openstack-ironic10:03
*** boris-42 has joined #openstack-ironic10:03
*** ifarkas has joined #openstack-ironic10:03
*** romcheg has joined #openstack-ironic10:03
*** dtantsur has joined #openstack-ironic10:03
*** yuriyz has joined #openstack-ironic10:03
*** krtaylor has joined #openstack-ironic10:03
*** Shrews has joined #openstack-ironic10:03
*** morgabra has joined #openstack-ironic10:03
*** openstackgerrit has joined #openstack-ironic10:03
*** jrist has joined #openstack-ironic10:03
*** sbadia has joined #openstack-ironic10:03
*** sirushti has joined #openstack-ironic10:03
*** SpamapS has joined #openstack-ironic10:03
*** steveh has joined #openstack-ironic10:03
*** proffalken has joined #openstack-ironic10:03
*** devananda has joined #openstack-ironic10:03
*** kylestev has joined #openstack-ironic10:03
*** russell_h has joined #openstack-ironic10:03
*** matty_dubs|gone has joined #openstack-ironic10:03
*** pquerna has joined #openstack-ironic10:03
*** Madasi has joined #openstack-ironic10:03
*** harlowja_away has joined #openstack-ironic10:04
openstackgerritLucas Alvares Gomes proposed a change to openstack/python-ironicclient: Add pagination support to {node, port, chassis}-list  https://review.openstack.org/9158510:04
dtantsurlifeless, so we agreed on 20G and 1 week, right? Please update your commit messages (or even their summaries) to mention the new value10:07
*** derekh_ has joined #openstack-ironic10:08
*** rameshg87 has joined #openstack-ironic10:08
*** datajerk has joined #openstack-ironic10:08
*** annegentle has joined #openstack-ironic10:08
*** notq has joined #openstack-ironic10:08
lifelessdtantsur: I'll see where its at tomorrow, need to sleep on it10:09
dtantsurlifeless, g'night!10:09
*** lazy_prince has quit IRC10:20
*** lazy_prince has joined #openstack-ironic10:21
rameshg87dtantsur: request you to take a look at ilo power code which you had a look earlier: https://review.openstack.org/#/c/89500/10:27
dtantsurrameshg87, what's the state of the spec?10:28
rameshg87dtantsur: spec has been submitted https://review.openstack.org/#/c/97455/10:29
dtantsurrameshg87, ok, I'll try to find some time this evening (sorry, too much things to do)10:29
rameshg87dtantsur: sure, thanks :-)10:30
*** romcheg1 has quit IRC10:35
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Raise appropriate errors on duplicate Node, Port and Chassis creation  https://review.openstack.org/10250610:36
*** lazy_prince has quit IRC10:36
*** Haomeng has quit IRC10:38
*** killer_prince has joined #openstack-ironic10:41
*** killer_prince is now known as lazy_prince10:41
*** Haomeng has joined #openstack-ironic10:46
openstackgerritA change was merged to openstack/ironic: Prevent updating UUID of Node, Port and Chassis on DB API level  https://review.openstack.org/10224710:56
*** chuckC has joined #openstack-ironic10:56
*** zul has quit IRC11:00
*** martyntaylor has joined #openstack-ironic11:02
*** zul has joined #openstack-ironic11:05
*** ramineni has quit IRC11:05
*** bvivek has quit IRC11:11
*** bmahalakshmi has quit IRC11:11
*** k4n0 has quit IRC11:15
*** openstackgerrit has quit IRC11:21
*** martyntaylor has left #openstack-ironic11:28
*** lucasagomes is now known as lucas-hungry11:31
*** bvivek has joined #openstack-ironic11:32
*** Haomeng has quit IRC11:44
*** Haomeng has joined #openstack-ironic11:49
*** martyntaylor1 has joined #openstack-ironic11:53
*** jdob has joined #openstack-ironic12:02
*** romcheg1 has joined #openstack-ironic12:03
*** openstackgerrit has joined #openstack-ironic12:17
*** vinbs_ has joined #openstack-ironic12:17
*** vinbs__ has joined #openstack-ironic12:20
*** vinbs has quit IRC12:21
*** vinbs__ is now known as vinbs12:21
dtantsursomeone remembers, in Node.properties is `storage` in GiB or MiB?12:22
romcheg1Morning Ironic!12:22
dtantsurromcheg1, morning!12:23
*** romcheg1 is now known as romcheg_ltp12:23
romcheg_ltpMorning dtantsur!12:23
*** vinbs_ has quit IRC12:23
*** vinbs has quit IRC12:26
rameshg87dtantsur: did you mean local_gb in properties of node ?12:35
dtantsurrameshg87, I was confused by wrong example in db.utils. disregard my question, please :)12:36
rameshg87dtantsur: okay :-)12:36
*** ryanpetrello has quit IRC12:36
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Add shared functions for hardware discovery  https://review.openstack.org/10701012:36
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Fix wrong test fixture for Node.properties  https://review.openstack.org/10703112:36
dtantsurrameshg87, that's what I mean: https://review.openstack.org/#/c/107031/12:37
rameshg87dtantsur: okay, got it :-)12:37
*** rloo has joined #openstack-ironic12:38
openstackgerritImre Farkas proposed a change to openstack/ironic-specs: Enable PXE deploy driver for DRAC  https://review.openstack.org/10703312:39
*** ryanpetrello has joined #openstack-ironic12:41
*** martyntaylor1 has left #openstack-ironic12:42
*** lucas-hungry is now known as lucasagomes12:44
*** matty_dubs|gone is now known as matty_dubs12:52
rloohello ironickers ;)12:53
rlooHi ifarkas.12:53
rlooifarkas -- wrt 107033. that's a new spec?12:53
rlooifarkas -- fyi, in yesterday's meeting there was a discussion about not accepting new specs for juno anymore.12:54
*** rakesh_hs has joined #openstack-ironic12:56
lucasagomesrloo, morning12:57
ifarkasrloo, hi, yep, that's a new spec12:57
rloohi lucasagomes12:57
romcheg_ltpMorning romcheg12:57
romcheg_ltphmm12:57
rlooromcheg: did you just say morning to yourself?12:58
romcheg_ltpTab-completion sucked :)12:58
rlooha ha12:58
dtantsurmorning, rloo!12:58
ifarkasrloo, I thought the new spec proposal freeze is Jul 24 as devananda wrote in the email with subject "Juno priorities and spec review timeline"12:58
romcheg_ltpMorning rloo!12:58
*** jcoufal has quit IRC12:58
rlooifarkas: will bring up with devananda then, if he put it in an email.12:59
*** jcoufal has joined #openstack-ironic12:59
ifarkasrloo, ok. fyi: http://lists.openstack.org/pipermail/openstack-dev/2014-June/039031.html13:00
rlooifarkas: thx! devananda ^^^ your email says new spec proposal freeze Jul 2413:01
*** lynxman has quit IRC13:02
*** jistr has quit IRC13:03
*** jistr has joined #openstack-ironic13:05
*** jbjohnso has joined #openstack-ironic13:08
*** ramineni has joined #openstack-ironic13:11
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add methods to ipmitool driver  https://review.openstack.org/10036413:14
*** stendulker has joined #openstack-ironic13:15
* dtantsur is going to steal some code from jroll's agent patch :)13:16
stendulkerdtantsur : Hi13:17
dtantsurstendulker, hi!13:17
stendulkerdtantsur: I have addressed your comments related to firmware settings spec https://review.openstack.org/#/c/101122/ Can you please validate the same13:18
jrollmorning y'all13:18
jrolldtantsur: what code? :)13:18
jrolland which patch? :P13:19
dtantsurjroll, morning! finding node by list of interfaces13:19
jrolllucasagomes: around?13:19
lucasagomesjroll, yo yes13:19
jrolldtantsur: feel free to factor that out :P13:19
jrolllucasagomes: hey, so I moved the config option back... and looking at this: https://review.openstack.org/#/c/100734/16/ironic/drivers/modules/pxe.py13:19
stendulkerlucasgomes: Hi13:20
dtantsurjroll, thanks! while spec is not approved yet, I started on separating required common functions: https://review.openstack.org/#/c/107010/13:20
jrolllucasagomes: if we decide to move that back to a class, then that patch just basically does "mv ironic/drivers/modules/image_cache.py ironic/common/image_cache.py"13:20
jrolllucasagomes: which I don't have a problem with... just thinking of abandoning at this point though :)13:20
stendulkerlucasgomes: Can you please review the firmware settings spec https://review.openstack.org/#/c/101122/13:20
lucasagomesjroll, yeah that's a true point... I thought about the class because it looks more consistent with what we already have13:21
jrolldtantsur: cool13:21
lucasagomesjroll, if we have a function that only creates and return an instance of a class, it looks better to have the class directly13:21
lucasagomesIMHO13:22
jrolllucasagomes: right... I agree13:22
jrolllucasagomes: I think I was refactoring a bit too hard here :P13:22
lucasagomesheh yeah, but that file def needs some refactors13:22
lucasagomesthe names are super confusing13:23
jrollyeah :/13:23
jrollI think you're more confused about them because you're in ipxe world13:23
jrolleverybody else thinks pxe == tftp13:23
lucasagomesyeah exactly13:24
jrolland doesn't realize the transport layer is different than the boot mechanism :)13:24
lucasagomes+113:24
jrollok, so, I think I'm going to just ditch this patch for now13:24
lucasagomesack, I will rebase the iPXE work on top of ur other patch13:25
jrollok, sorry about that :/13:25
jrollshould be pretty close at this point though13:25
jrollI'm still going to keep 10073513:25
lucasagomesjroll, nah nothing to be sorry about it's all good :D13:26
jrollyeah, just I know rebasing can really suck :P13:26
lucasagomeshah yeah13:26
*** jgrimm has joined #openstack-ironic13:27
lucasagomesjroll, btw, you don't want to be core of the ironic-specs?13:28
jrolllol13:29
lucasagomes:P13:29
lucasagomessay yes say yes13:29
lucasagomeshah13:29
jrollI'll just wait for russell_h to get back and proxy my +2's through him :P13:29
jrollI'm not opposed to being core there, but I prefer code over specs13:30
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Factor out deploy info from PXE driver  https://review.openstack.org/10073513:31
*** openstackgerrit has quit IRC13:31
lucasagomesjroll, heh, fair :)13:33
*** 17SAAF480 has joined #openstack-ironic13:33
lucasagomesmaybe Shrews will want :P13:33
jrollheh13:33
jrollI'm happy to +2 some specs if someone gives me that power13:33
jrollI just don't want to read them13:34
jrollnot sure how desirable that is13:34
lucasagomeslol not very13:34
jroll:P13:34
jrollso... agent driver is going to be blocked on this: https://review.openstack.org/#/c/102632/13:36
jrollfun.13:36
17SAAF480Victor Sergeyev proposed a change to openstack/ironic: Use oslo.db library  https://review.openstack.org/4215913:36
17SAAF480Victor Sergeyev proposed a change to openstack/ironic: Use opportunistic approach from migration testing  https://review.openstack.org/10705313:36
*** ramineni1 has joined #openstack-ironic13:37
lucasagomesjroll, will review it in a bit13:38
17SAAF480Jim Rollenhagen proposed a change to openstack/ironic: Add missing docstrings  https://review.openstack.org/10620213:38
stendulkerdtantsur: Hi13:38
*** 17SAAF480 has quit IRC13:38
jrolllucasagomes: no worries... going to wait on swift people anyway13:38
viktorsdevananda: hi! Could you please, when you'll have a time, take a look at patch https://review.openstack.org/107053 (Use opportunistic approach from migration testing) - this is attempt to fix bugs 1327397 and 1328997. Thanks!13:39
*** openstackgerrit has joined #openstack-ironic13:40
*** rameshg87 has left #openstack-ironic13:40
*** ramineni has quit IRC13:41
*** pcrews has joined #openstack-ironic13:42
lucasagomesIf ur willing to review something, here's something we need and is blocking us from releasing a new version of the python-ironicclient: https://review.openstack.org/#/c/91585/13:42
openstackgerritGhe Rivero proposed a change to openstack/ironic: oslo.i18n migration  https://review.openstack.org/10513213:42
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Add missing docstrings  https://review.openstack.org/10620213:43
jrolllucasagomes: sure... let me finish up iterating on some patches13:44
lucasagomesnp13:44
dtantsurstendulker, hi, I saw your request, but we have already a huge prioritized queue of reviews, and I don't know when I'll have time to get back to it, sorry.13:45
*** ramineni1 has quit IRC13:46
stendulkerdtantsur: I understand. Just wanted to inform you status from my side. Do review it, when you get time.13:46
stendulkerdtantsur: Thank you.13:47
dtantsurnp13:47
dtantsurFolks, mind reviewing 3 lines patch for tests? https://review.openstack.org/#/c/107031/13:48
*** kevinbenton has quit IRC13:52
*** kevinbenton has joined #openstack-ironic13:53
*** ramineni has joined #openstack-ironic13:53
jrolldtantsur: +2'd... curious why that doesn't break tests. :)13:55
*** ramineni1 has joined #openstack-ironic13:55
jrolldtantsur: as in, do we even need a properties dict in that fixture?13:55
NobodyCamgood morning Ironic13:56
*** lynxman has joined #openstack-ironic13:56
rloodtantsur: approved.13:56
NobodyCamI will be starting a little late this mornig13:56
*** ramineni has quit IRC13:58
dtantsurjroll, I need it, that's why I encountered this problem :)13:59
dtantsurjroll, rloo, thanks!14:00
*** romcheg_ltp has left #openstack-ironic14:00
jrollNobodyCam: not allowed.14:00
rloodtantsur: yw. (although I always feel a bit bad fast-tracking someone's patch over others.)14:01
dtantsuroh, I understand :)14:03
*** bvivek has quit IRC14:06
jrolllucasagomes: hey, about https://review.openstack.org/#/c/91585/7/ironicclient/v1/chassis.py14:07
NobodyCamjroll: :) have to take bubbie to the vets, this morning :(14:07
jrolllucasagomes: I don't see what you're doing with filters etc there... because _path(path) just should return '/v1/chassis'.... oh I see14:08
jrolllucasagomes: I don't like it :|14:08
jrollNobodyCam: :(14:08
* lucasagomes is in a call 1 min will answer it14:09
jrolllucasagomes: no worries, I see what it's doing, I just don't like it14:09
lucasagomeslol ok14:10
jrollwhy can't we just use requests? :(((14:13
*** Mikhail_D_ltp has quit IRC14:16
lucasagomes:(14:17
lucasagomesjroll, u mean the mechanism to actually build the URL?14:17
jrolllucasagomes: yeah14:18
lucasagomesyeah that's very simplistic right now14:18
jrolllike, in a sane http client, you pass params as a dict14:18
jrollbut our client doesn't have that14:18
lucasagomesyeah that's true14:18
jroll/shrug14:19
lucasagomes:(14:19
* jroll rewrites everything14:19
lucasagomeslol14:21
lucasagomesmany parts of our driver, this base class for e.g14:21
lucasagomesis a copy&paste from other openstack clients14:21
lucasagomes:(14:21
jrollyeah...14:22
*** lynxman has quit IRC14:23
ShrewsNobodyCam: any reason why you didn't approve 101765?14:24
*** lynxman has joined #openstack-ironic14:25
*** annegentle is now known as anneonthebus14:26
*** geekyogi has quit IRC14:31
GheRiverolucasagomes: you have time to talk about https://review.openstack.org/#/c/10368514:34
lucasagomesGheRivero, hey yea14:35
GheRiverodo you have any other concerns besides revising all the InvalidParameterValue (and confirm they are indeed MissingParameterValue)14:36
jrollI have a different approach here... what if validate() also accepted the method name ('deploy', 'tear_down', etc), and could change its validation based on that?14:40
* lucasagomes looks at the patch again14:40
jrollno matter the exception raised, I don't think an error should pop up on tear_down just because some metadata is missing (that isn't used for tear_down)14:41
lucasagomesGheRivero, but afair that's my only concern there14:41
lucasagomesand also making the validate_driver_interfaces() handle that new expcetion14:41
GheRiverook. Will address that today.14:43
jrolllucasagomes: approved https://review.openstack.org/#/c/91585/ :)14:43
jrollGheRivero, lucasagomes, wdyt about validate() taking the method name14:43
jrollI think it's silly to do the same validation for deploy and tear_down14:43
jrollin our case, it's turned into moving validation into those functions14:44
GheRiverojroll: I think it should be the parent method the one dealing with the error, but it just and opinion14:44
lucasagomes\o/14:45
jrollGheRivero: I guess I disagree that missing e.g. image_source is an error at all, for tear_down14:45
lucasagomesjroll, yeah, it sounded like a good idea to have a validate method for the whole interface14:45
GheRiverovalidation should do just what it said. It shouldn't care what is the purpose os the validation. Today is easy just with a couple of methods... but if it grows, checking every option inside validate could be insane14:45
lucasagomesbut I agree that we may need something more specific for each method instead14:46
lucasagomesbut again, that validate is for the whole interface14:46
jrollGheRivero: also, imagine validate() adds some check for a parameter that tear_down needs. raises MissingParameterError if not there. now your tear_down method doesn't catch it.14:46
NobodyCamShrews: Ahh Just wanted lucasagomes to have a quick look see14:46
jrolls/doesn't catch it/keeps going/14:47
lucasagomesNobodyCam, morning14:47
NobodyCammorning lucasagomes14:47
jrollGheRivero: my bigger question is, how do you validate something, if you don't know what that something is?14:47
Shrewsinteresting that the docstring for validate() in base.py says it's for validating *deploy*. nothing about tear_down.14:50
GheRiveroi got it now.14:50
jrollShrews: dat's what I'm sayin'14:50
Shrewsjroll: yeah. the interface predates me, but i'm just wondering if it morphed over time14:51
GheRiverodifferent methods need to validate different params :/14:51
jroll"oh shit... ironic needs to tear down nodes, too, huh?" -- deva, 18 months ago14:51
jroll:P14:51
Shrewslol14:52
GheRiverolol14:52
lucasagomesheh14:52
lucasagomesyeah i think that docstring is wrong14:52
lucasagomeslol14:52
jrollthe docstring is totally right... none of that validation is needed for tear_down14:52
jrollbbiab14:53
lucasagomesright, so on the do_node_tear_down method from the manager we may not want to run validate() on the deploy interface14:55
lucasagomeswell urgh...14:56
dtantsurNobodyCam, morning!14:59
openstackgerritChris Krelle proposed a change to openstack/ironic: Set a more generous default image cache size  https://review.openstack.org/10690515:00
NobodyCammorning dtantsur15:00
*** romcheg1 has joined #openstack-ironic15:00
NobodyCamdtantsur: hahaha I just fixed the pep8 issue on that.. :-p15:03
dtantsur:)15:03
lucasagomesdtantsur, what we are doing with the inventory_timestamp?15:03
lucasagomesbrb quickly15:04
dtantsurlucasagomes, NobodyCam suggested it will be helpful for UI to actually know, when this HW information was last updated and even search/sort by it (e.g. to quickly find newly added nodes)15:04
*** mdorman has joined #openstack-ironic15:05
*** ramineni has joined #openstack-ironic15:06
*** cdent has joined #openstack-ironic15:07
cdentlucasagomes: ping?15:08
*** ramineni1 has quit IRC15:09
lucasagomesdtantsur, we have the updated_at field on nodes as well15:10
lucasagomescdent, pong15:10
cdenthowdy, I just have a quick question about that stub ipmitool host you told me about15:10
dtantsurlucasagomes, yeah, but it can be changed for a lot of reasons. Anyway, this field is more by request of reviewers, than invented by me :)15:10
cdentit's pretty slow, is that expected?15:10
cdentsingle digit minutes to gather sensor data15:11
lucasagomescdent, ouch... hmm it shouldn't be that slow15:11
lucasagomeslemme check it15:11
lucasagomesactually matty_dubs may now better15:11
lucasagomesknow*15:12
lucasagomesdtantsur, yeah, so uff... it looks that it complicates more :/ it sounds redundant as well15:13
jrollperhaps have the timestamp in the dict that's stored15:13
jrollnext to the hardware15:14
jrollI don't see any reason to sort by it... if you want to find newly added nodes, use the flag that's been added15:14
dtantsurlucasagomes, jroll: here it was introduced by request of jdob: https://review.openstack.org/#/c/102565/9/specs/juno/generic-hardware-discovery.rst15:15
dtantsur(link leads to his comment)15:15
dtantsurjroll, no dict is stored :)15:15
dtantsuronly Node.properties are updated15:15
jrolldtantsur: ohhh, right15:16
jrollblah15:16
jdobdtantsur: which comment, the one about the explicit parameter for newly_discovered?15:17
lucasagomescdent, I'm trying another node here15:17
openstackgerritChris Krelle proposed a change to openstack/ironic: Set a more generous default image cache size  https://review.openstack.org/10690515:17
dtantsurjdob, no, the 4th, about timestamp15:17
jdobah, gotcha15:17
lucasagomescdent, it seems very slow as well :(15:17
cdentfoo15:18
cdentIt's not the end of the world, it's just making my manual test cycle rather painful :)15:18
lucasagomesyeah15:18
lucasagomescdent, real1m58.163s15:19
lucasagomes:/15:19
NobodyCamdtantsur: added to the commit message for that patch ^^15:20
*** jistr has quit IRC15:20
dtantsurNobodyCam, thanks!15:20
*** jistr has joined #openstack-ironic15:21
*** openstackgerrit has quit IRC15:21
NobodyCambrb15:22
dtantsurjdob, do you really need this timestamp for UI?15:23
*** ramineni has quit IRC15:23
* cdent is still waiting from time results15:24
cdents/from/for15:24
lucasagomescdent, seems it's the location that is affecting us... matty_dubs just tried it from wexford and it took 16 seconds to run15:24
jdobdtantsur: that's a better question for jcoufal and tzumainn; from what I remember, that suggestion was largely based on what I saw elsewhere in the spec. I think they do want to show the hardware config has changed, but the specifics on how to do that are open to debate15:24
lucasagomeswestford*15:24
cdentfeh15:24
cdentreal 5m6.172s15:25
cdent(that's for sdr -v, which is what the code is calling)15:25
lucasagomesholy cow!15:25
lucasagomesyeah15:25
lucasagomeshere it took 2 min15:25
jdobmy comment was more about the internal consistency of the spec. the problem description says it can detect changes to the hardware, but I didn't see how it would actually track that15:25
lucasagomescdent, maybe if we get a machine in Brno it will be quicker15:25
* cdent nods15:25
cdentI thought perhaps I could fake something with some hardware I have around the house, but nothing has the right knobs15:26
*** rameshg87 has joined #openstack-ironic15:28
jrolljdob: I think at that point we're going back into CMDB territory again :/15:28
dtantsurjroll, got two shared functions for discovery, you may be interested: https://review.openstack.org/#/c/107010/15:29
matty_dubsSo I was thinking about the CMDB stuff last night. I wonder if it makes sense to start to envision, even if only theoretical, a separate CMDB project and see if that solves needs15:29
NobodyCam:( its such a fine line between what we need and becomming a cmdb15:30
jdobto be fair, i'm not overly familiar at all with ironic, so if things I'm suggesting aren't in line with its vision, I'm not going to argue strongly for them15:30
matty_dubsI know with the NetApp stuff, I kept coming back to "Well, Ironic is clearly the best fit of the existing projects"15:30
dtantsurlucasagomes, NobodyCam, jroll: finally, should I delete this timestamp field?15:30
jrollmatty_dubs: this has some cmdb related things https://wiki.openstack.org/wiki/Fuel15:31
* lucasagomes thinking... 15:31
jrolldtantsur: probably15:31
jrolldtantsur: I don't see a valid use case, others may15:31
lucasagomesdtantsur, if you do delete it... why we have a new method for updating the inventory?15:31
jdobmy only request then is to also delete the line from the spec, or to clarify how "Responding to basic hardware changes, e.g. new hard drive, added RAM etc" is met15:31
lucasagomeswhy not just PATCH [{'path': '/properties'...}, {}] /nodes/<uuid>15:32
jdobeither how it's met, or what it entails, because I read that as saying ironic will report or otherwise make available knowledge that changes have been made15:32
dtantsurlucasagomes, to share the code (see https://review.openstack.org/#/c/107010/ ). Maybe it was a bot overkill to put it to the spec, as it's more of implementation detail, but I wanted to show it to some people doing the same15:32
dtantsurlucasagomes, ehhhhhr... provided you know UUID for just-booted node - yes15:33
jdobthe timestamp was just a suggestion as a (presumably, which doesn't appear to be the case) simple way of saying "Something last changed on X"15:33
lucasagomesdtantsur, you're going to find the UUID by looking the NIC addr no?15:33
* lucasagomes still reading15:33
* gilliard out - see you in the morning15:34
jrolllucasagomes: the discovery ramdisk would need to know it to send a patch request15:34
jrolljdob: it "responds" to hardware changes by storing that data :P15:34
dtantsurlucasagomes, yeah, but it will be inside conductor, too late to do PATCH :)15:34
NobodyCamnight gilliard15:34
dtantsurgilliard, g'night15:34
matty_dubscdent: I could also just set you up with shell access on a box in Westford, local to that IPMI instance15:34
jdobjroll: fair enough  :)15:35
matty_dubsSince transatlantic IPMI is apparently unbearable ;)15:35
jdobmaybe i was just reading into it15:35
jrollyou guys aren't exposing IPMI to the internet... are you?15:35
* jroll hacks into red hat15:36
matty_dubsjroll: Haha, no, over corporate WAN15:36
dtantsurok, I'm deleting the timestamp. I suggest reintroducing it later on demand.15:36
jrollgood, only RH employees can pwn it :)15:36
jdobso dtantsur, check with jcoufal to see what he was thinking in terms of being able to report changes to the user, otherwise I don't have a strong argument for any sort of reporting15:36
jdoband am cool with jroll's approach of interpretting that as that ironic will keep its inventory updated15:36
matty_dubsjroll: Heh, I have (at home, not the office) some Dell boxes with a vulnerable BMC, where you can get remote console without having to log in15:36
matty_dubsAnd Dell has never patched it, since it was an old/oddball setup15:37
jrollha15:37
cdentmatty_dubs: Thanks, but I think I'll cope with what I've got: environment tweaked and all that to get everything talking to one another in a devstack15:37
jcoufaldtantsur: can we catch up tomorrow?15:37
jrollI just assume all BMCs are vulnerable :)15:37
NobodyCamjroll: they are :)15:37
dtantsurjcoufal, whenever. I suggest making it as an addition to the spec, because we can't discuss the details forever :)15:37
lucasagomesjroll, dtantsur... idk I may be thinking differently... how a machine already registered in Ironic will endup booting the discovery ramdisk?15:37
lucasagomesthe idea is not a pxe fallback config file that machines _not registered_ will fallback to and boot the deploy ramdisk?15:38
*** rameshg87 has quit IRC15:38
dtantsurlucasagomes, Nisha is prototyping doing it on request of a user, for example15:38
lucasagomesif the machine is already registered, the request will come from a known mac addr15:38
jrolllucasagomes: I think that's unclear, but we're leaving it open-ended15:38
*** jcoufal has quit IRC15:38
lucasagomesand this address will ahve a specific pxe config for it, so no autodiscovery ramdisk15:38
lucasagomesright15:39
lucasagomesidk sounds like over engineering15:39
jrolllol15:39
jrolldtantsur's specs just talks about how the discovery ramdisk will talk to ironic, and how ironic will handle it15:40
lucasagomesright, but my point is ... we already have those methods in the api15:40
dtantsurright, I have exactly nothing about how ramdisk will be there. but I'm consolidating several specs that are floating in the air and how they are going to work with Ironic15:41
dtantsurlucasagomes, where?15:41
lucasagomesproperties can be updated by using PATCH, and creation of the node using POST15:41
lucasagomesyou can GET the mac to see the node uuid15:41
jrollmmm, I see15:41
lucasagomesGET <macs> ... not registerd... register node POST, update the prorperties PUT15:41
lucasagomesboom15:41
lucasagomesno changes to the api, no redundant methods to create or update nodes15:42
jrollhmm, that's a good point15:42
dtantsurlucasagomes, 1. too many logic to put into ramdisk; 2. what if we change the way we discover node UUID; 3. how the ramdisk will now e.g. default driver?15:42
lucasagomesor I may be missing something here15:42
dtantsurnow = know15:42
dtantsurlucasagomes, also you suggest at least twice more calls to the network (actually 1 + number of macs)15:42
lucasagomesdtantsur, right default driver could be something passed via the kernel cmd line to the ramdisk?15:43
lucasagomesand a config option in Ironic?15:43
dtantsurlucasagomes, and who is overengineering? ;)15:43
lucasagomesheh15:43
*** rameshg87 has joined #openstack-ironic15:43
lucasagomesI'm tlaking about 1 config option being added15:43
lucasagomeswhich is also present on that spec15:43
lucasagomes2) I agree we may need something better later15:44
lucasagomesand for 2) we have something15:44
*** shausy has quit IRC15:44
dtantsurlucasagomes, how are you going to pass options to ramdisk, provided that DHCP configurations is static?15:44
lucasagomesonce we have the arbitrary key and value pairs indexable by ironic15:44
lucasagomeswe could save the idk some ID of the node15:44
lucasagomesso instead of GET macs you would GET that ID see if there's a node which contains it15:44
lucasagomesor multiple IDs15:44
lucasagomes"arbitrary tag support"15:45
dtantsuryou're talking about some future feature that does not even have it's spec :-/15:45
lucasagomesyeah15:45
lucasagomesbut for now we can use MAC addrs15:45
dtantsuryes. and I don't see any reason your suggestion is better15:45
lucasagomesdtantsur, options are passed using the kernel cmd line15:45
dtantsurlucasagomes, how? should user update two places instead of one?15:46
lucasagomesdtantsur, it will be in the pxe configuration file15:46
lucasagomesdtantsur, the kernel options are there15:46
*** viktors is now known as viktors|afk15:46
dtantsurok, that may be possible. I still see no reason why15:46
lucasagomesdtantsur, yeah u right about the network calls15:46
lucasagomesit's definately more calls15:46
jrolldiscovery should be a rare case, I wouldn't worry about api calls15:47
dtantsurmoving logic from Ironic to the ramdisk is not making anything simple15:47
lucasagomesbut almost no changes to ironic, less code to maintain, less redundancy15:47
dtantsurexactly the same amount of code15:47
dtantsurbut moved to ramdisk15:47
lucasagomesno man15:47
lucasagomesramdisk will do like at least 3 api calls15:47
lucasagomesget 1 mac, post and a put15:47
lucasagomescould be more depending on the number of macs15:47
dtantsuri.e. the same that I'm doing right now. Where is simplification?15:48
lucasagomesbut definetely not the same ammount of code15:48
jroll+ POST /ports for each mac15:48
lucasagomesjroll, yeah15:48
jrollif the node is new15:48
dtantsur+ some folks will want to update ports, yeah15:48
jrollwe maintain official ramdisks, yes?15:48
lucasagomeswell the PUT is also not necessary you can create the nodes with the properties on it already15:48
jrollright15:48
lucasagomesu right about the POST to /ports15:49
dtantsuryou're replacing code in Ironic making DB calls with code in _a lot of_ ramdisks doing the same by network call15:49
lucasagomeswe gotta register those after the node15:49
jrollbut you'll also want to do a GET for each mac in the new node case15:49
*** matty_dubs is now known as matty_dubs|lunch15:49
lucasagomesmaybe we should do a hangout about it15:49
jrolldtantsur: why "a lot of ramdisks"15:49
lucasagomes?15:49
dtantsurjroll, IPA, iLO, probably simple ramdisk - this is minimum what we have15:49
dtantsuryeah, iLO folks have there own ideas on OOB discovery on so on, which I was trying to embrace as well15:50
jrollhrm15:50
dtantsurask Nisha or see his spec15:50
jrollright, oob would need to be different15:51
lucasagomesdtantsur, yeah mostly are replacing the calls in ironic for network calls from the ramdisk15:51
dtantsurand I didn't receive answer to question, how we have simplification by replacing Python functions call with network calls from ramdisk15:51
jrollbut your spec doesn't help for oob discovery15:51
dtantsurjroll, it does provide some required bits15:51
BadCub_morning all15:52
jrolldtantsur: kind of... but it all relies on /.../discovery being hit15:52
dtantsurat least it helped us agree on some common approaches, e.g. format of inventory to pass in15:52
jrollright15:52
jrollbut OOB discovery won't pass anything in15:52
jrollironic needs to pull the data15:52
dtantsurjroll, yeah, and he's introducing new mgmt function with _some_ result format. We agreed on standardized format for it15:53
jrollsure15:53
jrollI'm not totally sold on putting the logic in the ramdisk... but I also don't know why I didn't think of it :)15:53
lucasagomesI see the benefits on both approachs15:54
dtantsurjroll, unrelated. but we're starting discussion about storing inventory again in comments to IPA spec....15:54
jrolldtantsur: yay.15:55
dtantsurwell, folks, that's how I see it. You're free to -2 it, if you don't like. And I have my Czech lesson very soon, so have to go for now...15:57
* lucasagomes feels a bit bad15:58
lucasagomesI don't wanna be a blocker really15:58
lucasagomesI just think it could be simpler than it is being proposed15:59
*** jcoufal has joined #openstack-ironic15:59
lucasagomessimpler I mean, ironic offering basic functions: register and update {nodes, ports}15:59
jrollit is simpler on the ironic side15:59
lucasagomesramdisk having the logic to interrogate the hardware and talk to the ironic api using that basic functions15:59
jrolland we could even code the ramdisk-side logic into the client16:00
jrolldef create_or_update_node(...):16:00
lucasagomesand then we can start tunning the ironic api to help with it. e.g arbitrary tags to not have to GET macs, being able to register all the nodes ports within the same request to register the node itself16:00
dtantsurI would rather see the simplest possible ramdisk, because it's so harder to debug...16:00
lucasagomesbut baby steps16:00
lucasagomesthat's true16:01
jrolldtantsur: a ramdisk that has an init system isn't as hard to debug ;)16:01
lucasagomesbut I don't think that X GET request and Y POST requests will make it _way_ more complicated than it will be16:01
lucasagomeswe are talking about few conditionals16:02
lucasagomesand it may even be better, because if we detect that the mac is already registered16:02
*** cdent_ has joined #openstack-ironic16:02
lucasagomeswe don't even need to interrogate the node16:02
lucasagomesnor send the inventory over the network16:02
jrolltouché16:02
jrollwell16:03
jrollwe still will want to update the node16:03
lucasagomesyeah... and for that it's fine, cause we cna do partial updates on our api16:03
*** amitpp has joined #openstack-ironic16:03
lucasagomesso ok mac is registered u have the node id16:03
lucasagomesupdate only what needs to be updated16:03
lucasagomesshutdown16:03
*** eghobo has joined #openstack-ironic16:04
jrollright, partial updates, but we'll still need to interrogate the node16:04
*** romcheg1 has quit IRC16:04
*** cdent has quit IRC16:04
*** cdent_ is now known as cdent16:04
lucasagomesyeah true16:04
lucasagomesbut there's nothing to do about it really heh16:04
jrollright16:04
jrollI'm going to shower / head to the office... I'll think about this some more16:05
lucasagomesyeah I will think about it as well. I may be missing something16:05
*** hemna has joined #openstack-ironic16:05
dtantsurI already imagine how to debug getting NodeLocked in the middle of discovery on 5 of 100 new machines... gonna be fun16:06
dtantsurwith a new endpoint you can at least ensure it will fail only for serious reasons16:07
lucasagomesdtantsur, GET doesn't need locks... POST either16:07
lucasagomesneither*16:07
dtantsurlucasagomes, you mean patching node does not lock it?16:07
lucasagomesdtantsur, ah... yeah PATCH does lock the node :/16:07
lucasagomesbut that only will aftect updates to the node16:08
lucasagomesfor creation you can POST with all properties16:08
jrolland for PATCH:16:08
dtantsurlucasagomes, yes, so updating existing node will need retrying16:08
lucasagomesdtantsur, yup, we also have a spec about having our API to retry it16:08
jrollif the node is locked... you're probably about to get deployed16:09
lucasagomesso that would alleviate that16:09
jrollwhich means your ramdisk is about to go away16:09
jrollor16:09
lucasagomesthe NodeLock is a bigger problem than discovery it affects other stuff16:09
lucasagomesand need to be worked16:09
jrollbetter yet, put the node into maintenance when doing discovery16:09
lucasagomesjroll, +116:09
jrollthat way it won't get locked for other things16:09
lucasagomesyeah maintenance will make the sync stop16:09
jrollwon't get deployed etc16:09
lucasagomeson that node, so no lock16:09
jrollok bbl for real16:10
dtantsurok, I'm close to thinking that your approach is possible. Still don't see any advantage.16:10
lucasagomesjroll, ack cheers16:10
*** lazy_prince is now known as killer_prince16:10
lucasagomesmostly is keeping the ironic code base simpler16:11
lucasagomesI know we are shifting some to the ramdisk16:11
dtantsurby increasing some other code base :)16:11
lucasagomesfew lines of code afaiui16:12
lucasagomesno new api endpoints16:12
dtantsurbut much more API calls16:12
lucasagomes== no new tempest tests16:12
lucasagomeswhich can be worked later16:12
lucasagomesas I said, this is the first version16:12
dtantsurI would not call "no tempest tests" an advantage16:12
lucasagomesI would16:12
ShrewsI WOULD!   *giggle*16:13
lucasagomesbecause there's no new endpoints16:13
lucasagomesso no new tests needed16:13
lucasagomesless code to maintain16:13
dtantsurso you suggest to make feature non-testable, right?16:13
lucasagomesfaster tests on gate16:13
Shrewsbut only b/c i've been in them so much lately16:13
lucasagomesdtantsur, no16:13
lucasagomesI mean, what is needed to have that feature is already being tested16:13
lucasagomesand already available to use16:13
lucasagomeswhich is creation of {nodes, ports} and updates of nodes16:13
dtantsurlucasagomes, yes, but not their integration as a discovery feature16:13
dtantsurI mean, we have everythings covered by unit tests, but we have also tempest for reasons16:14
lucasagomesthat's the thing and why I think that keeping it simple is important16:14
lucasagomesbecause ironic only will have basic functions16:14
lucasagomesthere's no difference between registering a node with the client16:15
lucasagomesor having the ramdisk doing it16:15
lucasagomesall we want is to have the node registered16:15
dtantsurok, I'm also really going for the lesson. We anyway can't agree on it and have to ask devananda.16:15
*** dtantsur is now known as dtantsur|afk16:16
lucasagomesdtantsur|afk, ack, alright it's just an idea16:16
lucasagomeswe can talk more about it16:16
*** jistr has quit IRC16:16
*** athomas has quit IRC16:24
*** eghobo has quit IRC16:26
*** eghobo has joined #openstack-ironic16:26
*** foexle has quit IRC16:26
*** Alexei_987 has quit IRC16:30
*** ndipanov is now known as ndipanov_gone16:30
*** athomas has joined #openstack-ironic16:38
*** Nisha has joined #openstack-ironic16:40
*** killer_prince is now known as lazy_prince16:41
*** derekh_ has quit IRC16:42
*** stendulker has quit IRC16:43
cdentlucasagomes: in case you're curious: it's "mostly working" https://tank.peermore.com/tanks/cdent-rhat/2014071516:46
lucasagomescdent, w00t! will take a look16:47
devanandamorning, all16:56
NobodyCamgood morning devananda16:56
devanandaI'm attending the OSSG meetup today & tomorrow, will be semi offline16:56
lucasagomesmorning devananda16:57
devanandalucasagomes: good evening!16:57
devanandarloo: err, if my email said Jul 24, then I goofed in the meeting yesterday16:58
devanandarloo: yesterday was the 14th.... heh16:58
rloodevananda: ok, so no -2s until the 24th then!16:59
devanandalucasagomes: i see you and dtantsur|afk wanted my opinion on something... reading scrollback16:59
lucasagomesdevananda, me dtantsur|afk and jroll had some discussion about the autodiscovery, if you get a free time there take a look at it, food for though really, because we don't seem to agree much16:59
lucasagomesyeah16:59
lucasagomesit's about the autodiscovery17:00
rlooifarkas: ^^^ the deadline is the 24th ;)17:00
*** romcheg1 has joined #openstack-ironic17:02
*** pelix has quit IRC17:07
*** harlowja_away is now known as harlowja17:08
devanandalucasagomes: ok, i think i've mostly digested the conversation17:08
*** igordcard has joined #openstack-ironic17:09
devanandalucasagomes: it sounds like there are a few very differnt approaches being proposed: OOB discovery (eg, iLO) where conductor interrogates the hw and adds/updates it in DB17:09
devananda- in-band method by a ramdisk that does not need to change the ironic API (any more than we already plan to)17:10
devananda- in-band method taht would make significant API changes17:10
lucasagomesyes17:10
lucasagomesthe first one, the iLO thing is another spec17:11
*** matty_dubs|lunch is now known as matty_dubs17:11
devanandaso (1) and (3) both propose API changes, but different ones17:11
devananda(2) proposes no API changes17:11
lucasagomesbut I dtantsur|afk was working with Nisha to make sure their work won't overlap17:11
devanandawell17:11
devanandathat's a problem17:11
devanandaI don't want us to end up with two different APIs for discovery17:12
devanandathat's silly17:12
lucasagomes+17:12
lucasagomes+117:12
*** tzumainn has joined #openstack-ironic17:12
devanandaI think Nisha's proposal conflates two things17:12
devananda- discovery17:12
devananda- re-inventory17:12
lucasagomesmy arguments is mostly because we already have functions to create and update resources, I don't think we need to create other functions that will do the same thing17:13
lucasagomesbut in a different endpoint17:13
devanandaif we table any discussion of "how do we re-inventory known hardware" then things are much clearer17:13
lucasagomesURI*17:13
devanandaand I think both IB and OOB discovery can be _initiated_ using a single API17:14
devanandaunder /v1/drivers/<driver_name>17:14
lucasagomesright17:14
devanandapass the driver enough information to tell it where to go look17:14
lucasagomesand by initiated you mean, tell ironic to for e.g prepare the pxe env for the autodiscovery ramdisk?17:14
devanandafor an IB / DHCP based discovery, like IPA, that would be just a boolean17:14
devananda"enable discovery ramdisk for DHCP BOOT requests from unknown MAC" or "disable ..."17:15
lucasagomes+117:15
devanandafor an OOB / IPMI based discovery, like iLO, that might be an IP range on the IPMI LAN17:15
Nishadevananda:yes17:15
devananda"go poke 10.0.0.0/24 using username=foo,password=bar and see if there are new nodes"17:15
devanandathis is a single new API endpoint taht covers both IB and OOB discovery17:16
devanandaupdates to known hardware can then be done in two stages without any further changes17:16
devananda- delete node $UUID17:16
devananda- discover node based on <known property>17:16
*** rameshg871 has joined #openstack-ironic17:17
devanandaor if the operator already knows what has changed, he can simply issue PATCH request to change it17:17
devanandaor she17:17
devananda:)17:17
lucasagomesright this tihng about update known hardware to me, seems like a diff feature than auto discovery17:18
devanandayes17:18
devanandait clouds the discussion, has a different API, and I'm not even sure who wants it17:19
devanandanone of the operators at the last summit brought that up17:19
lucasagomesyeah17:19
devanandain fact, some even said "delete and re-discover is fine"17:19
devananda** assuming taht discovery works :)17:19
lucasagomesso I agree with you in adding a api point to enable/disable the discovery17:19
*** rameshg87 has quit IRC17:19
lucasagomesI first thought about a config otpion but an api to make it dynamic may be better17:19
lucasagomeslike PUT /drivers/<,,,>/discovery to enable and DELETE /drivers/<,,,>/discovery to disable17:20
devanandastarting/stopping discovery should be possible without restarting cluster17:20
lucasagomesyeah17:20
devanandaand should be possible per-driver17:20
devanandalike ^17:20
lucasagomessounds good17:20
devanandait would be great to have a standard parameter set for that endpoint17:21
devanandalike IP range, user, pass17:21
*** igordcard has quit IRC17:21
devanandabut i'm not sure we can17:21
Nishadevananda: This will not require new CLI?17:21
devanandait might need to be another driver-specific dict, like the driver_info fields17:21
devanandawhich drivers need to expose17:21
*** Penick has joined #openstack-ironic17:22
*** kylestev_ has joined #openstack-ironic17:22
lucasagomesdevananda, right, or simply being passed as the body request17:22
devanandaNisha: I'm suggesting adding a new API endpoint, so yes, it will need a change to the CLI to communicate with that17:22
lucasagomesand each driver will know how to handle it17:22
lucasagomeskinda like the vendor passthru17:22
devanandalucasagomes: sure - but again, the driver needs to expose /what/ it expects in that body17:22
lucasagomesyeah17:22
lucasagomesright... ok this needs to be sorted17:23
devanandawhereas vendor passthru does not expose what it expects, I think this needs to, since I'd like it to be a standard part of the API17:23
devanandait won't be "core" since not all drivers can support discovery, but it should be "common"17:23
devanandaactually. maybe they can17:24
*** Penick has quit IRC17:24
devanandaanyway. that's a tangent17:24
lucasagomesyeah, we can iron that out later17:24
*** Penick has joined #openstack-ironic17:26
*** cdent has quit IRC17:28
lucasagomesdevananda, alright thanks for the input... I will think on it17:28
lucasagomessee if I can put on an etherpad or something17:28
Nishadevananda: lucasagomes so from CLI perspective you plan to introduce a new CLI or use existing CLI's for autodiscovery?17:29
*** rameshg871 has quit IRC17:29
devanandaNisha: I dont understand your question. why would we create a nwe command line interface?17:29
lucasagomesNisha, well if we add that endpoint to enable/disbale the autodiscovery in the API we will add it to the CLI as well17:30
devanandaNisha: also, CLI changes are a secondary effect of API changes, which need to be very deliberate17:30
lucasagomesdef not creating a new CLI for it17:30
devanandalucasagomes: thanks. It'd be great if we can sort this out by / at the midcycle, otherwise I doubt we'll be able to land it in Juno17:31
devanandalucasagomes: given how much disagreement there seems to be right now17:31
Nishadevananda: ohk...actually i meant that how OOB will invoke autodiscovery since it will require IP range etc as input....17:32
devanandaNisha: right. I already discussed that17:32
lucasagomesdevananda, yup, we really want to have this feature in J so we probably are going to work hard on it to solve the misunderstands and all17:32
devananda17:14:00 < devananda> and I think both IB and OOB discovery can be _initiated_ using a single API17:32
devananda17:14:07 < devananda> under /v1/drivers/<driver_name>17:32
devananda17:15:30 < devananda> for an OOB / IPMI based discovery, like iLO, that might be an IP range on the IPMI LAN17:33
Nishaok17:33
devanandalucasagomes: quick poke re: python-ironicclient reviews.17:34
devanandalucasagomes: anything I shouldn't approve? :)17:34
*** igordcard has joined #openstack-ironic17:34
lucasagomesdevananda, oh, the pagination was approved but jenkins is failing17:34
devanandaugh17:34
lucasagomesdevananda, other than that, there's also the mrda patch adding the cache17:34
devanandaI'd love to get a new release tagged with that17:34
devanandaand that17:34
devananda:)17:34
lucasagomesdevananda, yeah it's a werid error when fetching the packages from pip17:34
lucasagomesI will recheck that17:34
Nishadevananda: Ok i will work with lucasagomes , dtantsur|afk and see how it goes17:35
devanandaNisha: thanks!17:35
lucasagomesthe error: http://logs.openstack.org/85/91585/7/check/gate-python-ironicclient-python26/2939d4e/console.html17:35
lucasagomeskg_resources.DistributionNotFound: virtualenv>=1.9.117:35
*** dtantsur|afk is now known as dtantsur17:35
dtantsurdevananda, lucasagomes: is there some conclusion on what we started with, i.e. autodiscovery?17:36
*** geekyogi has joined #openstack-ironic17:36
devanandadtantsur: read scrollback :)17:36
devanandadtantsur: not a conclusion, but I have some suggestions17:37
devanandadtantsur: which I think make both the discussion and the implementation simpler and achievable in Juno17:37
devanandaif everyone agrees17:37
lucasagomeswill approve mrda patches on the client17:38
dtantsurit's probably evening, but I can't find it :( it's ok, we moved OOB out of the discussion, but it's not clear for me, whether we want logic on ramdisk leevel or on ironic level17:38
*** rloo has quit IRC17:38
devanandarloo: https://blueprints.launchpad.net/ironic/+spec/get-required-driver-info approved and targeted17:39
lucasagomesdtantsur, afaiui, Ironic needs an endpoint to enable/disable the autodiscovery17:40
lucasagomesfor e.g for PXE someone will do a POST /drivers/pxe/autodiscovery17:40
lucasagomesand enable it17:40
dtantsurlucasagomes, why not use a configuration option?17:41
dtantsurTrue or False :)17:41
*** tzumainn has left #openstack-ironic17:41
lucasagomesso the PXE driver will prepare the PXE enviroment and generate the default config files where requests from mac _not registered_ in ironic will boot from17:41
lucasagomesdtantsur, cause we want it to be dynamic and per driver17:41
lucasagomesdtantsur, if it's a config you will have to stop start the service17:41
dtantsurlucasagomes, ah, ok, I though you're discussing my spec17:42
dtantsurbecause this part is completely irrelevant to it17:42
lucasagomes(our services doesn't understand KILL -HUP to re-read conf unfortunately)17:42
lucasagomesour == openstack17:42
lucasagomesdtantsur, yes, that's irrelevant for that spec17:42
lucasagomesbut that's also a common group, _all_ drivers will need a way to disable/enable dynamically the autodiscovery17:42
lucasagomesso that endpoint should be in the spec, not the driver implementation17:43
lucasagomesafaiui17:43
*** bvivek has joined #openstack-ironic17:43
dtantsurlucasagomes, my spec does not touch initiating the autodiscovery at all. It discusses part after ramdisk discovered something17:43
dtantsurso it's very good, but needs one more spec written by someone (maybe me)17:43
lucasagomesright...17:44
lucasagomesafter the ramdisk is discovered? after it's boot?17:44
dtantsurlucasagomes, that's what my spec and today's arguments is about :) I though you were discussing it...17:45
devanandaifarkas: hi! drac power driver BP approved. do you think code will be be ready by J2 (next thursday) ?17:45
dtantsurI mean, for the simpliest case we don't need to have any initialization, just a DHCP/PXE server with appropriate configuration17:45
lucasagomesdtantsur, right... so one thing about the _after_17:45
lucasagomesdtantsur, discovery vs updating known hardware are diff things17:46
dtantsurthat's why I'm thinking you're discussing step #217:46
dtantsurwhile we don't have step #117:46
lucasagomesdtantsur, we need initialization17:46
devanandaso let's set "update known hardware" completely aside. For now, it can be approximated with "delete then rediscover"17:46
*** rameshg87 has joined #openstack-ironic17:47
dtantsurlucasagomes, we will, but we can live without it at first, because static configuration is a good baby step17:47
dtantsurdevananda, will we account for the case, when ramdisk is by mistake booted on a known node?17:47
dtantsuror will we create a new node inconditionally?17:48
lucasagomesdtantsur, static configuration is not a good idea IOM17:48
lucasagomesIMO*17:48
devanandaalso, static external DHCP-based discovery is a trivial oversimplification. a proposal handling /only/ that case will impact the ability of OOB systems' discovery17:48
lucasagomescause there's no way to disable it17:48
lucasagomesalso u will have to create the pxe configs by hand?17:48
lucasagomesbut let's put it aside17:48
dtantsurso, you folks don't like baby steps and what to prototype all the abilities at once?17:48
devanandano17:48
dtantsurthat we have to think about authentication as well17:48
*** kylestev_ has left #openstack-ironic17:48
devanandaI'm proposing an incremental approach17:49
devanandawhcih doesn't block further work17:49
dtantsurme too17:49
lucasagomesalright... ok even if it's static17:49
lucasagomesthe way we register the nodes after the ramdisk is being booted17:49
rameshg87devananda, dtantsur, lucasagomes, request your review on ilo power code: https://review.openstack.org/#/c/89500/ , thanks ...17:49
lucasagomesIMO we should still use POST17:50
lucasagomeson the normal /nodes17:50
lucasagomesinstead of having a new endpoint for it17:50
devanandadtantsur: of course we need to handle the case where a known node is re-discovered. but we already do -- MAC address is unique17:50
*** rameshg87 has left #openstack-ironic17:50
devanandadtantsur: though POST /v1/nodes/ to create a new node doesn't (and shouldn't) have any uniqueness checks17:50
devanandadtantsur: this simply means that IB-based (ramdisk-based) discovery needs to do some checking (like GET /v1/ports?MAC=) before creating new node17:51
dtantsurdevananda, yes, you have to make ramdisk to do all the checks with ports before17:51
devanandawhich I think is what lucasagomes was already suggesting17:51
Nishadevananda: could u explain what u mean by "uniqueness checks"? ^^^^17:51
dtantsurI hate moving logic to the ramdisk, but as you wish17:51
dtantsurI'm abandoning my spec, right?17:51
devanandadtantsur: so I didn't say the ramdisk itself has to do that work :)17:51
*** rloo has joined #openstack-ironic17:51
devanandadtantsur: jsut taht that check needs to be done before the creation17:52
devanandabut...17:52
devanandaer, so...17:52
devanandadtantsur: what about this17:52
devanandaramdisk POSTs all the data to API service17:52
lucasagomesdevananda, yes! ramdisk does the logic to discovery if the node id based on the ports17:52
devanandaAPI service contains all the logic of17:52
devananda- interpret and validate POSTed data (sanity checking, auth, etc)17:52
devananda- look up all MAC addresses contained in the body17:53
devananda- if no duplicates, create new node, create port(s) associated to node17:53
dtantsurdevananda, that is _exactly_ what I am proposing, I guess. lucasagomes is against creating an API service for it.17:53
devananda- respond success17:53
devanandalucasagomes: so taht doesn't require any conductor work -- it's just API and DB interactions17:53
lucasagomesbut using the same endpoint right? to create the node with its ports within the same request17:54
devanandadtantsur: i haven't read your current spec version .... sorry17:54
lucasagomes<lucasagomes> and then we can start tunning the ironic api to help with it. e.g arbitrary tags to not have to GET macs, being able to register all the nodes ports within the same request to register the node itself17:54
lucasagomesI suggested something like that as an improvement17:54
dtantsurlucasagomes, our current endpoint does not accept MAC's...17:54
lucasagomesyeah... as an improvement17:54
lucasagomeslater17:54
lucasagomesfor now using the MACs seems resonable17:54
lucasagomesI mean using GET on ports to find the node id17:55
lucasagomesbefore creation17:55
devanandaso, right now, all this can be done using the CLI, by the ramdisk17:55
devanandaadding a nwe API endpoint which encapsulates all the logic of "create a node with these ports, if one does not exist"17:55
devanandawould be generally a useful improvement17:55
devanandaand has nothing intrisically to do with autodiscovery17:55
devanandaoperators would in general benefit from that17:56
devanandaas it makes enrollment of known inventory faster, too17:56
devanandaeg, writing a script to import a bunch of server data in a .csv file would be easier if you could just POST once per server, rather than once per server + once for every MAC17:56
dtantsurdevananda, maybe you'll have a quick look at my spec? I already do not know what we're actually arguing, it looks like we're proposing the same...17:57
jrollI haven't read scrollback yet, but is there any operator with a sizable deployment that won't be scripting their bootstrap?17:57
devanandaI get why lucasagomes doesn't want to tie that API change to autodiscevery -- I think they're separate things17:57
devanandajroll: nope17:57
jrolland is 1+n*macs slow enough to actually matter, and need to create a new endpoint for?17:57
jroll(that many POST requests)17:57
devanandajroll: i don't think that the perf here matters, honestly, but OTOH it's a shortcut17:58
jrolllike, if I'm enrolling 1000 nodes... I don't care if it takes 10 minutes or 3017:58
dtantsurmy point is not only speed, but in context of ramdisk, complexity of ramdisks costs a lot more than complexity of Ironic itself17:58
devanandaPOST (server and all relevant data) || POST (server) + N * POST (NICS in server)17:58
dtantsurin terms of debugging and testing17:58
JayFdtantsur: O17:58
JayFdtantsur: I'm not sure I completely agree with that17:58
JayFdtantsur: logic run in a ramdisk is distributed across all your nodes17:58
JayFdtantsur: so instead of having a small cluster of conductors doing things, I have idle hardware doing things, which scales more naturally17:59
jrolldevananda: right... I think it's negligible if the operator does any sort of capacity planning, at all17:59
*** tatyana has joined #openstack-ironic17:59
JayFdevananda: if you're going to make a shortcut, make a multiple-create endpoint17:59
dtantsurJayF, not it does not, because for database access you still go to the conductor17:59
jrollthere will never be a hair on fire situation where I need to add nodes 3 times as fast17:59
JayFdevananda: that would be one call to register multiple nodes17:59
devanandadtantsur: not for creation you don't17:59
dtantsurdevananda, checking NICs?17:59
devanandadtantsur: only for update, which is one reason I suggested we table any discussion of using discovery for update17:59
devanandadtantsur: correct -- taht's just a DB lookup18:00
devanandadtantsur: the API can do that jsut fine18:00
devanandaonly updating of existing resoruces requires lock coordination, ergo only updates require the conductor18:00
lucasagomeshey folks I will have to step back a little18:00
dtantsursorry, I meant API service, not conductor18:00
devananda(delete being a type of update, too)18:01
lucasagomesstep out*18:01
devanandalucasagomes: cheers, ttyl18:01
*** romcheg1 has quit IRC18:01
NobodyCamnight lucasagomes18:01
devanandaJayF: the problem with multi-node-create is what to do if one fails18:01
dtantsurI mean, doing logic in ramdisk won't scale better, because the bottleneck is mostly database and database accesses will be the same (but over REST API)18:01
lucasagomesthanks I will read the scrollback later18:02
*** lucasagomes is now known as lucas-afk18:02
devanandaso no one is going to be enrolling nodes so quickly that scalability will seriously matter18:02
NobodyCamanyone up for a quick review of: https://review.openstack.org/#/c/10690518:02
JayFdevananda: I'm with jroll in saying I don't think we need a new endpoint. But if you really wanted to make it more convienient, multi-create would be more useful imo :)18:02
devanandaseriously - compared to the scaling issues we already know we have with deploying a fleet,18:02
devanandaregistering a fleet takes miniscule amount of time18:03
jrollheh18:03
*** romcheg1 has joined #openstack-ironic18:03
JayFYes, exactly18:03
devanandadtantsur's point is that putting the logic into a ramdisk is harder to debug than putting it in the API service18:03
dtantsurthis is my major point ^^^18:04
devanandalucas' point is that we dont need to make any API changes to accomplish the same functionality18:04
jrollok, so18:04
jrollif the log is in python-ironicclient...18:04
jrollis that harder to debug?18:04
jrolls/log/logic18:04
jroll(answer is likely yes, but less so than logic in ramdisk)18:04
dtantsurthat does not solve problem with ramdisk exiting in the middle of the process on 5 of 20 machines... that's why I want to leave minimum logic on ramdisk side18:05
devanandathat's python code with unit tests. compared to a bash script, I'd say it's probably easier to debug and maintain18:05
jrollgah, ramdisk is all bash, isn't it18:05
* jroll sadface18:05
devanandadtantsur: huh? what does "5 of 20 machiens" have to do with this?18:06
jrolldtantsur: but, does that happen today? why would that happen by adding this?18:06
dtantsurdebugging PXE faults is already a not-too-pleasant experience18:06
devanandadtantsur: enrollment is per-machine. if the ramdisk crashes halfway through enrollment, THATs gonna be harder to debug regardless.18:06
devananda*regardless of what the ramdisk is doing18:06
dtantsurok, 5/20 is irrelevant, debugging even one may be a problem18:06
devanandadtantsur: also, "leave minimum logic on ramdisk side" is counter to all the work IPA is donig18:07
devanandadoing18:07
NobodyCambrb18:07
devanandato make the ramdisk more programatic, testable, and, well, generate logging that we can consume externally18:07
*** overlayer has joined #openstack-ironic18:07
jrollwell, to be fair, we have an init system, logging, and ssh server in IPA :)18:07
dtantsurdevananda, minimum != none.18:07
dtantsurmy view on IPA is that it encapsulates all hard moments with dealing with remote hardware18:08
dtantsur(like partitioning, firmware updates etc)18:08
devanandadtantsur: IPA already has several call-and-response interactions with their driver18:08
devanandaadding this logic for discovery to it is not a significant change AIUI18:09
*** jbjohnso_ has joined #openstack-ironic18:09
devanandajroll: please tell me if I"m wrong :)18:09
jrollright, this logic would be nothing for ipa18:09
dtantsurthan where's the line between what we put to Ironic and what we put to IPA?18:10
devanandadtantsur: OTOH, adding this to the current PXE ramdisk, whcih is bash and lacks a multi-user environment, would certanly be possible, but not easy to debug, i agree18:10
jrollalthough, this logic is more than we have now18:10
dtantsuryeah, it ruins hopes to have a simple bash-based discovery before IPA is done...18:10
jrollironic side currently does the mac -> node mapping18:10
jrollOTOH, that doesn't do node creation or anything18:11
*** jbjohnso has quit IRC18:11
dtantsurI actually borrowed a lot of mapping code from jroll's implementation :) so IPA already has some of this logic in Ironic18:11
jrollright18:11
devanandadtantsur: no. it accepts the limitations of the current ramdisk -- it's harder to debug failures18:11
jrolldtantsur: but that's only because it makes it easier to change that logic18:12
jrollto map by something other than macs18:12
*** geekyogi has quit IRC18:12
*** overlayer has quit IRC18:12
*** igordcard has quit IRC18:12
jrollbut that is *driver-specific* for us, not a generic thing18:12
devanandadtantsur: the more we discuss this, the more I agree with lucas' point -- we shouldn't make API changes just to work around "PXE ramdisk is hard to debug"18:12
jroll(unclear if that matters)18:12
*** igordcard has joined #openstack-ironic18:13
jrollI think that logic should be up to the driver... whether that is on the ramdisk side or ironic, as well18:13
dtantsurI hoped we can have at least some generic peaces...18:15
*** bvivek has quit IRC18:15
jrollI'm not opposed to that... but I think the generic piece should just look to the driver. maybe some default implementation... but then again that default implementation can be done the way lucas mentioned18:16
jrollidk18:16
dtantsurok, I leave it up to IPA to define the discovery and abandon my spec, right?18:16
jrollnot sure about that, either18:17
* jroll thinks18:17
dtantsurbecause while the complexity is ok for IPA, I won't dare to implement it for PXE18:18
dtantsurI don't than, will it be possible for J18:18
NobodyCamgah anyone know the correct rights for /etc/sudoers.d directory?18:20
dtantsur0755?18:20
jrollsounds like that should only be readable by root18:21
dtantsurwell, maybe actually 0700...18:21
jroll070018:21
jrollyeah18:21
NobodyCam:)18:21
NobodyCamowned by root18:21
-openstackstatus- NOTICE: python2.6 jobs are failing due to bug 1342262 "virtualenv>=1.9.1 not found" A fix is out but there are still nodes built on the old stale images18:22
*** ChanServ changes topic to "python2.6 jobs are failing due to bug 1342262 "virtualenv>=1.9.1 not found" A fix is out but there are still nodes built on the old stale images"18:22
Shrewsooh, fun18:23
NobodyCamwoo hoo can we depercate 2.6?18:23
NobodyCamoh wait I'm actually working on suse which IS 2.618:24
jrollhahaha18:24
* Shrews deprecates NobodyCam18:25
NobodyCamShrews: jroll: up for a easy review? https://review.openstack.org/#/c/106905/18:26
Shrewssure18:26
ShrewsNobodyCam: so, why change the default? why can't tripleo just set the value in .conf?18:28
jrollShrews: kind of a shitty default, though, don't you think?18:28
NobodyCamya18:28
jrolls/tripleo/every deployer/18:28
NobodyCamjust too small18:28
Shrewswell, yeah, i guess18:28
NobodyCam:-p18:28
jrollI'd say it's pretty unusable at 1G18:28
Shrewsso how did we land on the *new* default?18:28
jrollalso arbitrary :)18:28
NobodyCamif was 10G and TripleO was looking for 20 I might push back18:29
NobodyCambut 1 k really kinda small18:29
NobodyCams/k/g/18:29
jroll1k is super small :P18:29
Shrewsheh18:29
*** rakesh_hs has quit IRC18:30
dtantsurWell, folks, have to go anyway. You can express opinions on the spec by using -2/+2 :)18:30
*** dtantsur is now known as dtantsur|afk18:30
NobodyCamhave a good night dtantsur|afk18:30
jrollsee ya, dtantsur|afk18:30
*** jbjohnso__ has joined #openstack-ironic18:35
* NobodyCam has to go pick the bubbie.. be back in a bit.18:37
*** Penick has quit IRC18:37
*** jbjohnso_ has quit IRC18:39
*** Penick has joined #openstack-ironic18:40
*** jbjohnso__ has quit IRC18:42
*** lazy_prince is now known as killer_prince18:49
* devananda lunches18:58
*** derekh_ has joined #openstack-ironic18:59
*** anneonthebus has quit IRC18:59
*** jdob_ has joined #openstack-ironic19:00
*** Penick has quit IRC19:01
*** jdob_ has quit IRC19:01
*** jistr has joined #openstack-ironic19:06
*** Nisha has quit IRC19:07
Shrewswhere art thou, openstackgerrit bot?19:20
*** Mikhail_D_ltp has joined #openstack-ironic19:20
*** tatyana_ has joined #openstack-ironic19:22
*** tatyana has quit IRC19:23
*** tatyana_ is now known as tatyana19:23
* NobodyCam is back19:27
*** Penick has joined #openstack-ironic19:28
NobodyCamTy Shrews for 1069519:28
*** Penick has quit IRC19:28
NobodyCamlifeless: just fyi 106905 landed!19:29
*** Penick has joined #openstack-ironic19:32
* devananda is back19:38
NobodyCamwb devananda19:38
devanandalet's see if i can squash up a new nova driver patch19:39
devanandaalso, anyone want to review https://review.openstack.org/#/c/102695/8 ?19:39
NobodyCamoh there has been a todo for that for a while now19:39
*** lucas-afk has quit IRC19:40
*** Mikhail_D_ltp has quit IRC19:41
NobodyCamdevananda: did you see http://logs.openstack.org/95/102695/8/check-tripleo/check-tripleo-ironic-undercloud-precise/d451bb0/logs/seed_logs/nova-compute.txt.gz#_2014-07-15_05_53_59_92719:42
devanandalooking19:42
devanandaooh19:42
NobodyCamthat kinda looks real.19:42
devanandait does19:42
devanandainteresting that it passed tempest tho19:42
NobodyCamat least I haven't seen it on the rechecks of late19:43
devanandayea, that could well be related to this change19:43
devanandaor to another change that I saw proposed recently19:43
NobodyCamI can no bug recheck it19:43
devanandano...19:43
NobodyCamsee what we get19:43
NobodyCamok19:43
NobodyCam:-p19:44
devanandaas a general rule, please avoid "recheck no bug" unless there's a really good reason19:44
devanandathat goes for ALL prjoects. it just hurts openstack when we do that19:44
NobodyCamack .. I do try and not no bug things19:44
*** openstackgerrit has joined #openstack-ironic19:44
*** tatyana has quit IRC19:45
NobodyCambrb19:49
*** jcoufal has quit IRC19:52
openstackgerritJarrod Johnson proposed a change to stackforge/pyghmi: Reduce severity of generic discrete assert to 'Ok'  https://review.openstack.org/10716419:59
*** jbjohnso has joined #openstack-ironic20:00
Shrewssome errors are just very strange though... and no logs20:03
Shrewse.g., https://review.openstack.org/10558320:05
*** annegentle has joined #openstack-ironic20:06
Shrewsi wouldn't even know where to begin to file a bug about that failure so that we can recheck on it20:06
adam_gShrews, hmm20:09
openstackgerritA change was merged to openstack/ironic: Make ComputeCapabilitiesFilter work with Ironic  https://review.openstack.org/10580220:15
adam_gShrews, https://review.openstack.org/#/c/107165/ this may help20:16
Shrewsadam_g: is that a backported change?20:18
adam_gShrews, yeah just proposed it. we removed that at some point recentlyish, its possible something in infra changed that prevents the old behavior from working as it did?20:18
Shrewsah, i see the cherry pick comment now20:19
openstackgerritJosh Gachnang proposed a change to openstack/ironic-python-agent: Add versioning to Agent decommission  https://review.openstack.org/10685920:20
adam_gShrews, also FYI, poking tempest with all recent patches + in flight stuff and all but one compute API test passes from what we currently run (ie http://logs.openstack.org/27/103227/2/check/check-tempest-dsvm-ironic/0f5e4b1/logs/testr_results.html.gz)20:21
Shrewsadam_g: what did you do for cinder?20:21
adam_gShrews, oh, just set cinder = False. actually there were a couple of flags that needed toggle in addition to patches20:22
adam_gthe one thats still failing (test_server_actions) should be fixable with a new flag added for console output support20:23
Shrewsspeaking of which.... devananda, did you see mtreinish's email response re: cinder+ironic?20:23
Shrewsadam_g: all good news... but there were a bunch of server tests failing according to your etherpad20:24
Shrewswhat was the fix for those?20:25
Shrewstempest/api/compute/servers/20:25
devanandaShrews: yes, havn't had time to respond. you want to?20:25
Shrewsdevananda: sounds like you and he need to reach a consensus. he wants cinder disabled, you don't.   :(20:26
adam_gShrews, let me update20:27
devanandaShrews: I'd love to disable it AND other things. talk with -infra. AFAIK clarkb expressly rejects that sort of non-co-gating20:27
devanandaI was sort of parrotting infra's view, but I also agree with clark on it20:27
devanandaeven though selfishly i'd love our gate to be faster20:27
Shrewsdevananda: i'll ask him to weigh in on it then20:28
adam_gShrews, oh i forgot to mention, im running with IRONIC_VM_COUNT=3, so scale is not an issue anymore, at least serially20:29
Shrewsadam_g: ah. k20:31
jbjohnsohmm, I don't see my last review on pyghmi doing anything jenkins wise20:35
Shrewsdevananda: clark will respond tomorrow (in germany atm). he has since changed his viewpoint20:36
devanandaShrews: neat!20:36
Shrewsindeed20:36
jbjohnsoon a somewhat related note, I'm starting to get more in the territory where commentary on some hardware management and authentication for confluent if anyone is interested20:36
Shrewsadam_g: i'll unabandon my 'disable cinder' review and fix it up per clark's suggestion20:37
adam_gShrews, whats his suggestion? i cant keep track anymore :)20:38
Shrewsadam_g: use features.yaml to disable it20:38
adam_gShrews, ah, ok. what repo does that live in? i haven't looked at it yet20:38
Shrewsadam_g: devstack-gate20:38
adam_gShrews, cool20:38
openstackgerritA change was merged to stackforge/pyghmi: Reduce severity of generic discrete assert to 'Ok'  https://review.openstack.org/10716420:43
jbjohnsojust had to kick jenkins a bit20:45
*** jistr has quit IRC20:55
Shrewsadam_g: got a sec?20:56
adam_gShrews, ya20:57
Shrewsadam_g: https://review.openstack.org/#/c/105278/2/tempest/api/compute/admin/test_hypervisor.py20:57
Shrewsadam_g: Ken'ichi's comment20:58
Shrewsadam_g: do you know how to check the hypervisor type?20:58
adam_gShrews, lemme see20:58
Shrews_list_hypervisors() only returns the ID and hypervisor host UUID, afaict20:59
adam_gShrews, you should be able to call a 'show hypervisor' on each id and check hypervsior_type21:00
jbjohnsoI hear rumor of people saying ipminative is not working right?21:00
adam_gShrews, not sure if thats what the test is doing21:00
*** Penick has quit IRC21:01
Shrewsadam_g: ah, yes. thx!21:01
adam_gnp21:01
*** Penick has joined #openstack-ironic21:02
*** jdob has quit IRC21:04
openstackgerritRuby Loo proposed a change to openstack/python-ironicclient: Add driver-properties command  https://review.openstack.org/7633821:06
*** Mikhail_D_wk1 has quit IRC21:07
*** stevebaker has quit IRC21:07
*** dguerri has quit IRC21:07
*** soren has quit IRC21:07
*** stevebaker has joined #openstack-ironic21:07
*** soren has joined #openstack-ironic21:07
*** dguerri has joined #openstack-ironic21:07
*** Mikhail_D_wk has joined #openstack-ironic21:08
*** amitpp has quit IRC21:13
*** igordcard has quit IRC21:16
*** jbjohnso has quit IRC21:20
NobodyCamseeking other reviewer comments on https://review.openstack.org/#/c/10368521:24
jrollNobodyCam: I still think validate() should take a method name, e.g. 'tear_down'. eventually we're going to want to validate something for tear_down21:25
*** romcheg1 has quit IRC21:28
*** jgrimm has quit IRC21:31
NobodyCamjroll: that sounds like it wold need a spec21:43
*** mrda-away is now known as mrda21:46
mrdaMorning Ironic!21:46
jrollNobodyCam: I know...21:47
jrollNobodyCam: not my patch yo :)21:47
NobodyCamgood morning mrda21:53
mrdaNobodyCam: \o21:54
Shrewshi mrda21:54
mrda\o21:54
devanandamornin, mrda!22:01
mrdahey deva22:01
NobodyCamlol guess I should read the status message22:04
NobodyCam:-p22:04
openstackgerritA change was merged to openstack/ironic: Fix wrong test fixture for Node.properties  https://review.openstack.org/10703122:04
*** Penick has quit IRC22:05
*** igordcard has joined #openstack-ironic22:09
*** Penick has joined #openstack-ironic22:15
*** mdorman has quit IRC22:16
*** Penick has quit IRC22:16
Shrewsmrda: your metaclass change makes my head hurt22:20
Shrews:)22:20
Shrewsactually, metaclasses in general make my head hurt22:20
NobodyCamShrews: so would a doc string on a meta class be meta meta data?22:27
ShrewsNobodyCam: DIAF22:27
Shrews:)22:28
NobodyCamlol22:28
Shrewsok. dinner time. see you all tomorrow22:29
mrdaShrews: Sorry about that22:34
mrdaShrews: devananda made me do the __metaclass__ thing.  We only got there with lots of experimentation.22:35
jroll"made me"...22:35
jrollI knew everybody was scared of him22:35
openstackgerritDevananda van der Veen proposed a change to openstack/ironic: Use auth_token from keystonemiddleware  https://review.openstack.org/10719722:36
mrdajroll: well, when the ptl suggests an implementation, it makes sense to follow that direction ;)22:37
openstackgerritDevananda van der Veen proposed a change to openstack/ironic: Use auth_token from keystonemiddleware  https://review.openstack.org/10719722:40
NobodyCamjroll: looking at 100364... perfect candidate for lucas's new ManagementInterface22:41
jrollgahhhhhhhhhhhh22:42
NobodyCamlol22:42
devanandayanno i like it when ya'll prove me wrong ;)22:42
jrolloh that did land22:42
* NobodyCam thinks it will land b4 the ManagementInterface spec22:42
NobodyCamjroll: nope22:43
NobodyCamnoot yet22:43
jrollhuh?22:43
jrollNobodyCam: https://github.com/openstack/ironic/blob/master/ironic/drivers/base.py#L35722:43
devanandamrda: Shrews: sorry. i'm not that fond of __metaclass__ either -- but it was the the way that I could think of to guard a class-object.22:43
devanandai'm sure there are other ways to achieve the same result22:43
NobodyCamjroll: https://review.openstack.org/#/c/10021822:44
devanandaand I do think it reads well22:44
NobodyCamhummm22:44
jrollNobodyCam: I know that spec hasn't landed, but the implementation has, so22:44
jrollI think the implementation was proposed before ironic-specs existed22:44
NobodyCamdevananda: looks like we should land https://review.openstack.org/#/c/10021822:45
mrdadevananda and Shrews: There's six.add_metaclass that I'll use instead22:45
devanandamrda: ++22:45
devanandaoh. /me pokes the spec22:46
jrollNobodyCam: if I put it in the ManagementInterface... I'll also need a spec to add it to the interface22:46
* jroll cries22:46
NobodyCamyou have a bug22:46
NobodyCam:-p22:46
* NobodyCam ducks22:46
*** igordcard has quit IRC22:47
jrolllol22:47
jrollright22:47
jrollnow I'm going to need a spec22:47
JayFWrite a spec == "this isn't landing for a long time"22:47
JayF:(22:47
NobodyCamJayF: we have been much more active on the specs of late22:47
*** derekh_ has quit IRC22:51
*** igordcard has joined #openstack-ironic23:00
devanandaso23:07
devanandathis came up in the project meeting today23:07
devanandaspecs are pretty heavy handed23:07
devanandaIMO they've been super helpful in the design process23:07
devanandabut not a great tool to indicate what our plans are, with any sort of advanced notice23:08
devanandaespecially for smallish changes, the spec and code are often written together (or code-before-spec even)23:08
JayFThey also, I don't think, get reviewed often enough. That's basically a problem with everything though, it's just now there's 2x as many reviews for a given feature23:08
devanandaJayF: so, hopefully, if a spec is thoroughly reviewed and then approved BEFORE the code,23:08
devanandathen the folks who reviewed the spec will have a much easier time revieing the code23:09
devanandaand it should be approved faster23:09
jrollJayF: that may also just be an ironic problem (not to say it's not a problem)23:09
JayFDo we have statistics showing a lower average review time for code that had a spec written vs not?23:09
JayFI've heard that presented before and I'm not 100% convinced it's true, honestly23:09
devanandawe haev statistics showing lower average # of revisions since we adopted specs23:09
devanandabut correlation != causation23:09
* devananda points to his recent email with review stats23:10
JayFI've specifically made a point to review specs with my 'ironic review time' because I think I add more value there than on the code itself at times23:10
JayFand there's just a lot of specs that feel a little stuck in the mud23:10
JayFfor lack of a more exact term23:10
JayFI think it's hard to say 'no' on a spec, in a way?23:11
openstackgerritA change was merged to openstack/ironic-specs: New driver ManagementInterface  https://review.openstack.org/10021823:12
NobodyCamjroll: ^^^ :-p23:14
NobodyCamwoo hoo23:14
jrollLOL23:14
jrollNobodyCam: can we just... land 10036423:14
jrollI know the review number by heart23:14
NobodyCamlol23:14
jrollthat's how annoying that review has been23:14
NobodyCam:(23:14
devanandaJayF: why is saying "no" hard?23:15
devanandaalso, i need to step afk. yay meetings23:15
openstackgerritDevananda van der Veen proposed a change to openstack/ironic: Use auth_token from keystonemiddleware  https://review.openstack.org/10719723:15
devanandaand that ^ isn't working yet. but we will need to fix it soonish, as keystone_client.middleware is deprecated23:16
devanandabbiab23:16
JayFdevananda: maybe it's just something for me-personally, or maybe generally about the scope of Ironic being unclear, but there's definately specs I've seen that I've wondered if they belonged in Ironic, but wasn't sure/confident enough to -1 it23:16
*** harlowja is now known as harlowja_away23:16
devanandaJayF: please don't hesitate to raise such questions23:17
devanandaon the spec, in the weekly meeting, anywhere23:17
devanandai rely on all of you to voice your opinions/concerns/etc23:18
devanandaotherwise I dont know them :)23:18
Shrewsi'm concerned that i don't have cake for my after dinner dessert23:18
devanandaShrews: that's horrible!!!!23:18
JayFNo cake? Let Shrews eat bread.23:18
Shrewsdevananda: plz fix that. kthxbye23:18
openstackgerritMichael Davies proposed a change to openstack/ironic: Ironic nova driver to cache ironic client calls  https://review.openstack.org/10269523:18
devanandaShrews: I will mail you a cake. as soon as I finish eating this one.23:18
Shrewsewwwww23:19
devanandaanother one23:19
devanandai hope you like vegan gluten-free cakes23:19
Shrewsagain, ewwwww23:19
devananda:)23:19
mrdaIt's my son's 13th birthday today - I will be eating cake23:19
devanandafine, more cake for me23:19
*** Penick has joined #openstack-ironic23:20
Shrewsmrda: how does that help me and my cake deficiency?23:20
* Shrews creates a spec for more cake23:20
NobodyCamShrews: http://sam557.deviantart.com/art/you-ve-got-virtual-cake-17476899523:21
Shrewswoot!23:21
mrdaIt doesn't, but it helps me with mine :)23:21
* JayF tries to remember to compel his wife to make gluten-free goodies for devananda at the mid-cycle23:24
* NobodyCam steps afk for a few23:25
*** rloo has quit IRC23:26
NobodyCamdevananda: did you see I had two ironic meetup tickets? one for ironic and one for nova too23:26
ShrewsNobodyCam: we need meetup tickets for the nova one?23:27
mrdaShrews: I don't think so23:27
NobodyCamno I got that b4 we had ironic tickets23:27
Shrewsoh wait. nm. i'm thinking tripleo23:28
NobodyCamthats next weeke23:28
NobodyCam:)23:28
Shrewsyeah, that's the only one i can attend23:28
mrdaSo NobodyCam, I think you should let mikal know this.  Then he can give your nova seat to a nova devel - they're at capacity in their room23:28
NobodyCamoh and my flight out is also the last day of "lavander" festival (http://www.lavenderfestival.com)23:29
mrda...because I'm assuming you'll be hanging with the rest of us ironics instead :)23:29
NobodyCammikal: please note I have both a ironic and nova meetup ticket (or think I do) I do not actually need the nova one! please give to a nova dev!!!23:30
NobodyCammrda: that work?23:30
mikalNobodyCam: thanks!23:31
mikalNobodyCam: I shall auction it to the lowest bidder23:31
JayFI think we'd also let a nova dev or two in the ironic room23:31
JayFthen lock them in until the driver gets merged23:31
JayFthat frees up a spot or two in the nova room :P23:31
mikalUmmm, not to be mean, but you'd have to _propose_ the driver first23:31
mikalJust sayin'23:31
JayFnot me, personally23:32
JayFI'm further up the chain23:32
JayFwe have a driver for /ironic/ which is waiting to be merged which depends on the ironic driver for /nova/ which is yet to be merged23:33
JayFso basically we're running pre-pre-pre-alpha software. or something like that.23:33
JayF:P23:33
lifelessJayF: why is your ironic driver blocked on the nova ironic driver?23:34
lifelessI thought we had/were removing all the ironic-driver data leaks from the nova driver.23:34
JayFlifeless: I'm in like 99% joking mode here :)23:35
mrdaNobodyCam: sure23:35
NobodyCammikal: would you like me to cancel the ticket? it's under my hp email.23:35
JayFlifeless: although honestly, I think our nova-driver for onmetal is patched compared to upstream, but idk what the diff is at this point23:35
JayF(jroll or comstud would, though)23:36
jrolloh god wat23:36
jrollwait23:36
jrollwe're not blocked on nova driver23:36
jrolllifeless: ^23:36
jrollwell, kind of. "onmetal production" has changes to the nova driver. for configdrive, etc.23:37
jrollbut the agent driver patch is not blocked on that... the only change for the agent driver patch is to add `or 'agent' in node.driver` here: https://github.com/openstack/ironic/blob/master/ironic/nova/virt/ironic/patcher.py#L3923:38
*** igordcard has quit IRC23:38
jrollmikal: the driver is proposed?23:39
mikalNobodyCam: hold off on that... I think I need to queue it so someone on the wait list gets it when its released23:39
NobodyCammikal: ack... pm the # over to ya use / abuse as you see fit23:39
mikalNobodyCam: could you reply to my eventbrite email and let me know that you can release it though so I remember?23:39
jrollmikal: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:ironic,n,z23:40
mikaljroll: it needs to be split into phases, as discussed at the summit with deva23:41
mikaldevananda is working on it I am sure, its just not done yet23:41
jrollmikal: right, it was split a week or two ago, idk what happened since23:41
jrollright23:41
mikalOh, I get you23:42
mikalSo there's three in the chain?23:42
* mrda is glad we're all on the sam page again ;)23:42
mikalIs that chain complete?23:42
jrollno idea, ask deva :P23:42
jrollrather, ask nova-core23:42
mikalWell, I was goign to work on this other blueprint23:42
mikalIts called "have a nap"23:42
jrollbecause I don't think deva would mind landing that way23:43
jroll+9000 for "have a nap"23:43
mrdamikal: you only just got out of bed.  Back to work! :)23:43
* mrda knows his timezones23:43
jrollheh23:44
mikalmrda: yeah, its the two work calls in the middle of the night at the 5:45am meeting which are killing me23:44
jrolland I thought being 2 hours off of san antonio was bad...23:44
* mrda withdraws his mikal cheekyness23:44
*** hemna has quit IRC23:44
openstackgerritJosh Gachnang proposed a change to openstack/ironic-python-agent: Add versioning to Agent decommission  https://review.openstack.org/10685923:46
* devananda returns from meetinglandia23:58
*** Penick has quit IRC23:58
devanandamikal: i proposed the nova driver in three phases like weeks ago23:59
mikalLIES23:59
mikalAlso, perhaps23:59

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