17:00:04 #startmeeting training-guides 17:00:04 Meeting started Mon Oct 6 17:00:04 2014 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:07 The meeting name has been set to 'training_guides' 17:00:17 hello hello 17:00:31 hello 17:00:40 hey 17:01:29 hello 17:02:07 #topic docs 17:02:38 hi all 17:02:43 hello matjazp 17:02:49 hi matjazp 17:02:51 Hello 17:02:52 evening matjazp 17:03:10 ...and MeganR :) 17:03:11 More fixes coming up this month. I am fixing the XML syntax to bring it up to the level of other documentation projects 17:03:58 I think that is it for docs this time 17:04:02 cool 17:04:08 anyone else? 17:04:33 any questions/suggestions/new contributors? 17:05:01 im eager to discuss user group training 17:05:24 unless a new contributor has a question 17:05:42 #topic user group training 17:05:47 should we keep user group training for the extras section? 17:05:52 rather than discuss in docs? 17:06:15 i just changed the topic 17:06:17 ahh :) 17:06:25 what is user group training? 17:06:27 unless you need more time 17:06:37 no I am good 17:06:45 cool 17:06:50 #link http://lists.openstack.org/pipermail/openstack-docs/2014-October/005274.html 17:07:33 now that i am mostly moved over in my new digs 17:07:53 i have some time and new people to work with 17:08:40 the general idea is that we run the associates training 17:08:44 yep, good news 17:08:49 in between the summits to start 17:09:00 also more feedback from the trainers for keeping the content quality better 17:09:06 we attract trainers to help out 17:09:15 dbite, yeah def 17:09:44 it will help us fine tune the great body of work that we have to work with 17:09:56 work out bugs faster 17:10:05 get new contributors 17:10:42 i have 3-4 people willing to help run a 2 hour training session in the SF bay area 17:11:02 i have a proposed schedule in the email linked above 17:11:07 That is great - then are you looking to expand to other meet-ups throughout the country? 17:11:14 if possible we need 1-2 regular contributors for docs sub-team too 17:11:29 meganr yes very much so 17:11:45 sarob, this looks great 17:12:06 meganr ;) 17:12:33 sarob: looks promising 17:12:45 sooo, i see some stuff that needs to be prioritized IF we as a team want to support this 17:12:58 think of it as our coming out party 17:13:54 sounds good sarob :) 17:14:12 btw guys, we could also discuss this at the summit? 17:14:27 first up, can I get a sense of what the team thinks of this as one of our priorities for the next cycle? 17:14:32 matjazp: def 17:15:33 let me put this a different way 17:15:53 i would let to set our kilo priorities as 17:16:20 1: current with juno release 17:16:47 2: audio visual tools and videos 17:17:09 3: running the associate training guide in the user groups 17:17:37 4: coordinating the training guides with the upstream training 17:17:45 off the top of my head 17:18:01 im not asking for a vote or anything 17:18:16 * rluethi notices a distinct lack of scripts 17:18:17 just throughing it out there for discussion 17:18:35 I think first we need to come up with a model for releases 17:18:48 I think #4 is already starting to branch.. we update/cleanup their content.. do they use training-guides repo or their own? 17:18:59 for instance which release should we work while in the current release cycle 17:19:16 should we be one release behind ? or follow the current release while developing the content 17:19:23 rluethi: scripts are implicit :) 17:19:42 matjazp: I don't like being implicit :). 17:20:05 I think video is farther down the road in priorities, get your docs and script house in order 17:20:10 matjazp, rluethi: infra is required for our success 17:20:32 rluethi: hehehe... yes, true :) 17:20:45 dbite: I would advise one release behind for your audience (unless your target audience changes to devs) 17:20:54 annegentle: the numbers are meant as priority 17:21:06 sarob: saying 2 for video should be more like 5 17:21:07 annegentle: yes I was asking for everyones views on this 17:21:11 annegentle s/are/are not/ 17:21:14 thanks for the suggestion :) 17:21:18 sarob: ah :) 17:21:28 sarob: that not makes a big difference 17:21:42 annegentle: at least with the scripts we need to track the openstack-manuals trunk or they will become useless for doc authors. 17:21:47 annegentle always does ;) 17:22:01 sarob: I am working on the infra part, infact here is the first patch to automate upstream-training builds https://review.openstack.org/#/c/126246/ 17:22:03 rluethi very true 17:22:47 dbite nice 17:23:30 annegentle: the scripts should be good tools for install guides team 17:23:32 what do you think? 17:23:33 rluethi: okay... but even devstack has a stable/ branch each release 17:23:47 okay lets get back to the topic 17:23:48 annegentle: understood. 17:24:06 and we had an argument about openstack multinode not running on VirtualBox, the scripts will install openstack on multinode env. using virtualbox 17:24:10 i messed it up by listing stuff 17:24:11 and it works fine 17:24:14 dbite: honestly it's early to say 17:24:29 dbite: rluethi: can't wait to see what people do with the scripts 17:25:02 annegentle agreed scripts are pretty awesome 17:25:20 sarob: you have quite good contributor numbers this release, with many training-focused people in the top ten for docs 17:25:20 soo the user group training topic 17:25:45 annegentle, the team is amazing agreed ;) 17:26:39 so team. we will continue to discuss our priorities for the summit 17:27:14 sarob: do we have a meeting in paris scheduled? 17:27:19 are we generally in favor of my user group training plan here #link http://lists.openstack.org/pipermail/openstack-docs/2014-October/005274.html ? 17:28:24 yes, I in favour 17:28:30 *I am 17:28:43 yes 17:29:00 rluethi: session not settled yet 17:29:03 actually, "a laptop with enough mem or disk" should not be hard to come by. 17:29:03 agree yes 17:29:22 RAM requirements: 4 GB for the cluster 17:29:23 me too 17:29:29 sarob: can we make a session on Thursday? 17:29:42 sarob: for docs, we have cross project and a pod 17:29:47 sarob: our requirements are 4GB/ i5 machine 17:29:52 it should/may work on i3 17:29:58 sarob: I have some logistic problems and will have to go back on Friday morning 17:30:30 annegentle: okay, i need to work out a session slot with you this week if poss 17:30:48 sarob: ok, my time is quite flexible throughout the week 17:30:57 so I guess we give preference to matjazp 17:31:36 dbite, matjazp okay , fri is out, so summit session prefered tue to thur 17:31:43 sarob: right, looks like you need the pod Thursday then 17:31:47 so Mo-Th is prefered 17:32:07 matjazp mon is slammed for me already :( 17:32:29 annegentle thursday looks good 17:33:09 sarob: we can use doodle? everyone enters appropriate slots.. 17:33:48 action sarob create a training guides kilo summit doodle for design session slot options 17:34:26 #action sarob create a training guides kilo summit doodle for design session slot options 17:35:25 #action sarob start the etherpad on training guides kilo release cycle priorities and design session topics 17:35:55 lets talk scripts shall we? 17:35:59 sarob: we have the Documentation etherpad here https://etherpad.openstack.org/p/docstopicsparissummit 17:36:23 annegentle: cool, I will just add another section then 17:36:42 #undo 17:36:43 Removing item from minutes: 17:37:07 #action sarob update Documentation etherpad here https://etherpad.openstack.org/p/docstopicsparissummit with priorities and topics 17:37:29 #topic infra 17:39:19 as stated earlier, custom builds/tests are on the way 17:39:35 I have started with building upstream training content 17:39:35 https://review.openstack.org/#/c/126246 17:39:42 scripts are usable now. I have some patches pending, but there are no major bugs as of now. 17:39:43 please clone this patch and run $tox 17:40:07 and you can have the HTML and PDF under upstream-training/target/ folder 17:40:31 for now the patch will have to wait till we clear our a few dependencies with infra project 17:41:06 that would be awesome if reed can reference the repo during the pre summit training 17:41:25 yes 17:41:31 he can definatly do that 17:41:38 sarob, in what sense 'reference'? 17:41:54 reed: use the repo directly for presenting 17:42:03 dbite, that's the intention, yes 17:42:05 generating the ppts in the repo using the tools 17:42:09 dbite reed yup 17:42:15 reed: I think you will love the patch in that case :) 17:42:34 the pdf files do not have the background theme, I will be working on it a bit later if that is ok with you 17:42:51 we will have zip/tgz files with the labs directory content, hopefully in the not too distant future (also depending on how urgent people feel it is) 17:43:06 I have one question regarding the upstream-training content which directly impacts infra 17:43:20 how do we expose the html and pdf files on docs.openstack.org/training-guides ?? 17:43:27 and suggestions/solutions? 17:43:36 rluethi: what about DL of prepared images? we talked about that few moths back... 17:43:48 *months 17:44:13 dbite, indeed, cool stuff. I am issuing a call for help with the html theme 17:44:21 matjazp: I think it is better not to prepackage Images 17:44:26 reed: sure :) 17:44:43 dbite: why? 17:44:43 we do not have the resources (h/w limitations) 17:44:52 and its more easier to build the scripts 17:45:03 if we continue on the creating slides from script theme 17:45:06 we need jenkins jobs, someone has to verify the images etc. etc. 17:45:29 then perhaps we could start making it user configurable 17:45:46 and saving the user configured for others to reuse 17:46:03 matjazp: we can still do it. the problem is exporting/importing the cluster, in particular network configuration. do you have a solution for that? 17:46:25 rluethi: hmm... Vagrant? 17:46:54 rluethi: oh.. you mean automatic export of netw? 17:46:58 matjazp: I am seriously considering dropping Vagrant altogether. It has too many limitations. 17:47:09 matjazp: plus nobody seemed to be using it. 17:49:38 rluethi: netw conf is more or less static, right? we could manually create proper netw config with Vagrant (or batch), and DL already prepared images 17:50:39 matjazp: I am a bit skeptical, because I am trying to reduce complexity, but I'd be happy to discuss this with you. 17:50:49 rluethi: ok 17:50:55 matjazp: let us discuss this over the summit, what do you think? 17:51:17 sure... I'm all for it 17:51:25 matjazp: you will loose snapshots and other issues which we face 17:51:33 dbite: yes, I know 17:51:36 with bundled images 17:51:48 if we make the scripts 100% (near) reliable 17:51:58 dbite will do when i get into the office 17:52:01 matjazp: for instance, rebooting during provisioning is sort of lacking in Vagrant 17:52:11 sarob: you need to run the scripts, they are awesome 17:52:26 dbite :) 17:52:33 sarob: :) 17:53:43 rluethi: hmmm.. there seems to be some workarounds 17:54:19 rluethi: but yes... maybe the added complexity is not worth it 17:55:14 time check peoples 17:55:41 * rluethi checks watch 17:55:46 #topic any other business to discuss 17:55:59 * dbite dbite wonders if its swiss watch! 17:56:22 i have started placing items into #link https://etherpad.openstack.org/p/docstopicsparissummit 17:58:31 i guess i got everyone onto the etherpad :) 17:58:43 :D 17:59:06 i will call this latest version of the training guides team meeting at a close 17:59:15 Have a good week! 17:59:19 thanks for all your hard work 17:59:31 cheers! 17:59:38 bye 17:59:48 Bye 18:00:03 #endmeeting