17:10:15 #startmeeting training_guides 17:10:17 Meeting started Mon Jul 6 17:10:15 2015 UTC and is due to finish in 60 minutes. The chair is matjazp. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:10:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:10:20 The meeting name has been set to 'training_guides' 17:10:29 roll call 17:10:34 hi 17:11:09 * rluethi hears crickets chirping 17:11:31 I was a bit surprised, I thought you guys postponed the meeting time 17:11:45 pranav just said he can't make it 17:11:53 matjazp: I was surprised, too :-) 17:12:18 I knew there was talk of changing the slot, but I don't think anything has been agreed on. 17:12:27 you know if sayali will be comming? 17:12:34 no idea. 17:12:47 isn't she travelling? 17:12:53 or was that last week? 17:13:06 * rluethi shrugs 17:13:12 anyhow, lets just look at the agenda.. 17:13:22 oh, a standard one :) 17:13:23 yeah, let's :-) 17:13:29 #topic reviews 17:14:05 pranav submitted a patch for tox that publishes training guides in the drafts 17:14:47 I didn't see that. Lemme check. 17:14:58 he still needs to polish it a bit, he has a typo and maybe he should also insert a associate guide folder 17:15:39 now you can just click in the gate and you can see the training guides slides 17:16:34 which gate? 17:17:07 ...publish.-checkbuild 17:17:23 #link http://docs-draft.openstack.org/35/197535/3/check/gate-training-guides-tox-doc-publish-checkbuild/3fd20d8//publish-docs/ 17:17:25 sweet. 17:17:52 it will be easier to review content 17:18:09 not obvious for newcomers, but very cool for those who know the trick. 17:18:45 well it's the standard way of publishing drafts for the whole docs project 17:19:42 I always thought something like this should exist, but I didn't know that it did. 17:20:26 what do you think, do we need to add "associate-guide" or "associate" folder? 17:20:43 we will need it later, so maybe we can add it now 17:20:50 yes, I was about to add a comment agreeing with you. 17:21:20 later= when we add content for developer guide and operator guide 17:22:55 is there anything new about labs? 17:23:27 not really, we were busy celebrating the latest bug fix :-). 17:23:35 there was some planning for the future. 17:23:51 pranav and sayali worked on the python port. 17:24:18 I wanted to port my KVM backend to master, but it takes more time than I currently have. 17:24:45 I know taht we discussed this already a few times, but I stil think that maybe vagrant could be a good option... it has MANY providers already (KVM, vBox, OpenStack, etc.) 17:25:33 so you have KVM bash port and there's also a python/KVM labs port? 17:26:50 I hacked together a KVM backend for osbash, but it's only a PoC (i.e. breaks the virtualbox code) and needs work. 17:27:14 python is also at PoC stage. 17:27:41 the problem with vagrant is that it's a pretty substantial dependency. 17:27:53 something we've been trying to avoid. 17:28:04 so it would be an alternative, not a replacement. 17:28:11 rluethi: yes, it is, but it also solves some major pain point we have 17:28:18 that would mean we maintain yet another backend. 17:28:20 eg. different providers 17:30:03 I'm experimenting a bit with KVM backend and multinode devstack with vagrant 17:30:08 maybe. I am skeptical. I like vagrant, don't get me wrong, but right now osbash is much easier to use than setting up vagrant. 17:31:11 rluethi: for developer's guide labs, we will probably need devstack too, not just install form packages 17:31:41 ic 17:32:13 well, devstack already does that, doesn't it? 17:32:18 anyway, I just remembered about all that stuff we already discussed when I needed to reboot machine during provisioning 17:33:06 rluethi: yes, but it is much easier to install multinode devstack with vagrant 17:33:38 I'll take your word for it. 17:33:51 and for some things, you need multinode, allin-one is not enough (eg. showing scheduling, networking, etc 17:34:04 I wonder if we could leverage the devstack code instead of vagrant. 17:34:24 we do have a multinode setup, what we don't have is the install from git repos. 17:35:48 osbash that calls devstack directly? maybe 17:36:05 it would preserve osbash workflow 17:36:33 yes. 17:36:39 but back to reviews... thats it, right? 17:36:46 yes. 17:36:50 we're done. 17:37:17 #topic any other business 17:38:05 I'm just curious, would you prefer the meeting an hour or two later? 17:38:21 not really. 17:38:26 for me it's alright. 17:39:24 and others? Is the only problem Monday, or is it also the time slot? 17:39:25 i will let others decide and try to be there for the meeting if I can. 17:39:35 I dunno. 17:40:04 I was curious about that, too, and I expected to read more on the mailing list, but there was nothing. zilch. nada. 17:41:23 hmm... you have anything else? 17:41:49 nope. I'm good. 17:41:56 wrap up. 17:41:59 ok, so let's wrap this 17:42:04 #endmeeting