10:34:52 #startmeeting training-labs 10:34:53 Meeting started Wed May 11 10:34:52 2016 UTC and is due to finish in 60 minutes. The chair is rluethi. Information about MeetBot at http://wiki.debian.org/MeetBot. 10:34:53 rluethi, dguitarbite ? 10:34:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 10:34:57 The meeting name has been set to 'training_labs' 10:35:04 hi julenl 10:35:05 hi rluethi 10:35:53 #topic pxe poc 10:36:03 so, how's the pxe poc going? 10:36:04 I just made the blueprint 10:36:13 cool 10:36:21 link? 10:36:28 it's been on standby for a while... I have to get back to it 10:36:49 https://blueprints.launchpad.net/openstack-manuals/+spec/pxe-server-osbash 10:37:29 is it good? 10:39:00 I don't know, but I will read it 10:41:23 May be a bit terse. 10:41:51 But I don't claim to be an expert, most features we did without a blueprint. 10:42:25 Blueprints are very helpful in teams that are bigger than ours. 10:43:10 We usually had several discussions with all team members :). 10:43:36 Any progress on the implementation side? Major roadblocks? 10:43:41 yes... but Pranav suggested me to do it 10:44:10 not from my side.. I have been quite busy since Austin 10:44:10 It's good to do things by the book at least sometimes. 10:44:28 Yeah, me too. 10:45:19 I looked into providing an additional network interface config: PXE. 10:45:33 Patch is not done yet, but it should not pose major problems. 10:46:01 If I don't remember wrong, I think that the only things I am missing for the pxe, are to fix something on the kickstart file and figure out how to do the bridged interface in the right way 10:46:36 yes, I think so too 10:47:01 It is just something we need to be able to automate the whole process. 10:47:22 certainly 10:47:23 And we need that to enable automated testing of the PXE environment. 10:47:50 sure 10:47:58 are you going to work on PXE in the forseeable future? 10:48:43 I was trying to use it to try to start a VM on another computer, using my home network. But it's tricky with the dhcp (my router does not allow to shut down the dhcp server) 10:49:23 I like the idea... 10:49:38 and it doesn't seem to involve much maintenance 10:49:54 once the server is ready, the rest is built from the existing code 10:50:18 for testing it would be ideal if we could run the whole thing on one computer. 10:50:37 sure 10:50:44 also for the CI tools 10:50:44 of course, we would still have to test with several computers occasionally. 10:50:49 exactly. 10:51:56 so, about the blueprint... should I add/remove something? 10:53:07 I cannot claim that I know if or how it should be changed. 10:53:22 Maybe Pranav knows. 10:53:36 If in doubt, write the code. 10:54:07 well.. it does have a little bit of context and it explains a more or less in which direction I am trying to go 10:54:14 Yes. 10:54:40 And we can always have all hands meetings to discuss everything. 10:54:42 but yeah... the blueprints don't provide any working functionality :P 10:55:14 But a PoC is very useful to find out if a feature makes sense, what it can be used for and how it should be implemented. 10:55:22 You know, something to play with. 10:55:28 It helps with thinking :). 10:55:56 hey! and that blueprint of yours for the public cloud... it totally rocks! :D 10:56:34 yeah. the only blueprint I ever wrote, and one of the few features that I talked about without ever implementing it. 10:56:57 draw your own conclusions. 10:58:09 anyhow, any other points you would like to discuss? 10:58:20 hmm... 10:58:26 I don't think so 10:58:41 I'll try to get further with the PXE thing this week 10:58:54 sound good. 10:59:00 ... otherwise, I think I'm good 10:59:12 if you have any questions, let me know :) 10:59:21 sure! Thank you :) 10:59:36 have a good rest of the week! 10:59:47 #endmeeting