19:00:15 #startmeeting ironic 19:00:16 Meeting started Mon Sep 2 19:00:15 2013 UTC and is due to finish in 60 minutes. The chair is NobodyCam. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:19 The meeting name has been set to 'ironic' 19:00:30 Good AtNoon 19:00:47 o/ 19:00:48 o/ 19:00:50 :) 19:00:50 whos here for the Ironic meeting this fine labor day 19:00:56 here 19:01:07 hey hey dkehn welcome 19:01:48 I try and keep the agenda upto date 19:01:54 #link https://wiki.openstack.org/wiki/Meetings/Ironic 19:02:18 #topic Testing env 19:02:25 ok thats me 19:02:30 for dib 19:02:50 I have updated the patches and are working thru 19:02:59 we have landed one. 19:03:06 still working it 19:03:27 dev stack looks like one +2 19:03:41 Yes 19:03:54 I have poked several core devs during the week 19:04:06 I have also sent an email to the mailing list today 19:04:06 it the FF rush 19:04:13 I think so 19:04:14 ok 19:05:01 just checking the action items from last week 19:05:03 :) 19:05:12 any q / c ? 19:05:13 There was one for me AFAIR 19:05:23 you answered it 19:05:24 :) 19:05:40 #topic in-progress tasks 19:05:51 pxe has one +2 19:06:11 I have some news about keystone 19:06:11 would like to give deva the chance to review it. 19:06:20 :) 19:06:28 do tell 19:06:53 The bug seems to be fixed to I was able to make the required set up and to try the things 19:07:05 woot 19:07:07 So good news everyone :) 19:07:15 nice 19:07:26 thing are falling into place 19:07:26 We don't have to change any code to support v3 domains 19:07:35 dkehn: want to glot? 19:07:55 ah 19:08:28 I have made some investigation of the code in keystone and found that roles are taken from either domains or tenants depending on the supplied token 19:09:24 wanted to note the dkehn quantum (notes starting name) pxe support patch landed 19:09:27 Investigating the code was really easier than making a dialog with keystone devs — everyone is so busy 19:10:07 yes, both in nova and neutron, the only thing outstanding is the python-neutronclient 19:10:37 :) 19:10:53 ok any q / c? 19:11:13 #topic API discussion 19:11:13 kudos :) 19:11:21 I can see bm deploy helper dying soon :) 19:11:30 :) 19:11:35 since landing the neutron code yesterday I have been getting requests for supporting bigswitch, ml2, nicitra, etc., so we will be soring this out 19:12:32 dkehn: I'll bet 19:12:50 ok on to 42690 19:12:57 #link https://review.openstack.org/#/c/42690/ 19:13:10 cool, about the API, there's a patch (42690) that allows us to use the PATCH http model to update the resources 19:13:18 lucasagomes: did I see a new upload this morning 19:13:27 yea, actually was a rebase 19:13:39 cause of the problem we had with wsme 19:14:08 ahh 19:14:16 and I see docs! 19:14:44 yup :) native english speakers feel free to review that doc please 19:15:12 lucasagomes: this allows us to actually delete a option 19:15:25 did we ever get a bug for that? 19:16:00 NobodyCam, yes, removing attributes will act different depending on the attribute 19:16:06 for example removing something from a collection 19:16:16 is different than removing something from the root document 19:16:18 e/g 19:16:42 multi-valued attributes like "properties" in the node resource 19:17:02 will be able to actually remove things from it 19:17:18 yes we did get a bug 19:17:19 ? 19:17:39 not really 19:17:44 I can file one 19:17:55 should we havea bug for not being about to remove "properties" 19:17:57 ?? 19:18:07 might be worth it? 19:18:16 * lucasagomes a bit confused 19:18:35 we have a bug in the moment where we can't set attributes to NULL for example 19:19:13 because our implementation in the moment (partial PUT) just allows us to replace attributes with another value 19:19:22 but not set the to null 19:20:40 NobodyCam, that's the problem u r talking about? 19:20:46 yes 19:20:53 was looking at bug list 19:21:04 I'll look later 19:21:13 so no, we don't have a a bug for that AFAIK 19:21:21 but we should 19:21:32 :) and linked to this review 19:21:43 :-p 19:21:50 yup, will do it 19:22:03 sweet :) /me is thought he was going nuts 19:22:27 ok any other q / c on put vs patch? 19:22:57 #topic API discussion 19:23:45 vendor pass_thry 19:23:50 vendor pass_thru even 19:23:58 is yuri here? 19:24:07 No, he's not 19:24:18 He took a day off 19:24:23 I see 19:24:43 lucasagomes: did you want to go over any conserns 19:25:10 lucasagomes: He will read the meeting logs tomorrow, so you can share your thoughts 19:25:28 *concerns 19:25:34 right, so... vendor_passthru will allow vendors extend our api to expose 19:25:41 some vendor specific features 19:26:26 #link https://review.openstack.org/#/c/43441/ 19:26:56 so right now, the API offers a way to clients invoke those methods, but we also need to expose a way 19:27:11 to clients retrieve information about the state of their request 19:28:08 lucasagomes: how would we track which request they are getting status on? 19:28:45 so I was thinking about using the name of the method called as an identifier 19:28:56 so the same way you do a PUT in a 19:29:18 you would do a GET on that method and it would return the status of the current state of that call 19:29:35 but I have to talk to yuri to see how it should work, since he's implementing it 19:29:41 ideas are very welcome :) 19:30:02 s/PUT/POST/g 19:30:25 my fear is to people using the passthru method on different hosts 19:31:02 wounder if we need some kind fed-ex like tracking number 19:32:13 we might... this resource is very unique I'vent seem it in others apis 19:32:41 and it opens a big door for exploits and stuff, we have to think carefully how we are going to implement that 19:33:17 yes 19:34:08 we can chat with yuri tomorrow 19:34:28 right, yea we def need his input on this 19:34:52 any other Q /c's? 19:34:54 but if there's anyone here that wants to give some ideas, comments, etc... please do 19:35:54 ok then we'll get with Yuri tomorrow and get his imput 19:36:02 ok moving on 19:36:05 #topic Food For Thought / Open Discussion 19:36:28 FFT: how will ironic interface with nova 19:37:53 there's any initial idea on how it should work? 19:38:57 in devas head 19:38:58 lol 19:39:06 i'm sure 19:39:13 just tossing it out 19:39:37 hehe 19:39:54 i was looking at hacking a power driver and replicing nova bm powerdriver with ronic 19:40:00 maybe nova will have a "driver" which will just talk to ironic 19:40:05 ya 19:40:42 at least for testing i was thinking some hack that would allow pice by pice replacement of nova bm 19:41:08 *piece 19:41:34 any thoughts? 19:41:45 I see yea... so as I see it 19:41:56 you could use both, nova as an interface to ironic 19:42:05 or use the ironic api directly 19:42:41 so is it easier to add a ironic driver or teach nova ironic api 19:43:04 for some specific tasks ironic api will be the only way to do it, since some actions won't fit in nova 19:43:31 NobodyCam, I'm not sure 19:43:40 I gotta think more about it, I'm just dumping some thoughts here 19:44:21 thats what this #topic is for 19:44:27 :D 19:44:43 any one else want to jump in 19:44:49 yea... so, hmmmmmmm maybe we could do a small prototype with nova 19:44:51 there are no wrong answer here 19:45:03 and try to implment a way to list the nodes in ironic using nova 19:45:11 the power driver is a clean cut 19:45:19 no no 19:45:29 kinda like a nnova baremetal-node-list 19:45:32 well 19:45:57 ya thats a queston we need to think about 19:46:03 how will that work 19:46:37 ironic could nave nodes that the current user does not have access to 19:47:29 we have no way of flitering resources by user 19:49:21 also some FFT: How will Ironic handle > then 1 conductor 19:50:46 well well while we were meeting 19:50:52 #ling https://review.openstack.org/44566 19:51:00 merged 19:51:25 my connection was gone :( 19:51:32 lol :) 19:51:46 there you go 19:51:50 yea, sorry 19:51:53 urgh... 19:51:55 heheh 19:52:04 did you get hte scroll back? 19:52:09 will read the logs later, what topic we are now? 19:52:16 not really 19:52:21 also some FFT: How will Ironic handle > then 1 conductor 19:52:45 just tossed that out 19:52:55 its open floor 19:53:04 I can investigate that 19:53:07 oh yea, the scalling out problem 19:53:16 I need a new task anyway 19:53:21 romcheg: :) 19:53:27 romcheg, that would be good 19:53:56 also we have no way of flitering resources by user 19:54:04 That's an # action isn't it? 19:54:19 yep 19:54:30 NobodyCam: Since we only allow admin requests the only filter might be based on domain 19:54:46 #action romcheg to look into How will Ironic handle > then 1 conductor 19:55:26 romcheg: yes but how will that play with nova baremetal-node-list 19:55:55 JUST FFT: 19:56:27 Can you please add that to the wiki? 19:56:35 last 5 minutes any last thoughts 19:57:06 which one? user filter? will do 19:57:20 The filtering 19:57:44 is the aganda ok for the FFT section for everyone? 19:57:53 it kinda just ended up there 19:58:06 I think it's better to move that to the start page 19:58:24 start? 19:58:39 I'm happy with the FFT being the last topic 19:58:51 https://wiki.openstack.org/wiki/Ironic 19:59:04 :) we can at least get a link 19:59:16 lucasagomes_: +1 19:59:39 also every one can edit the agenda 19:59:47 ok then 20:00:22 :) alright if there are no parting words we can make way for the TripleO team 20:00:32 Thank you everyone 20:00:37 :) 20:00:40 #endmeeting