13:03:50 <matjazp> #startmeeting training-guides
13:03:52 <openstack> Meeting started Tue Apr  4 13:03:50 2017 UTC and is due to finish in 60 minutes.  The chair is matjazp. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:03:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:03:56 <openstack> The meeting name has been set to 'training_guides'
13:04:07 <asettle> o/ ola
13:04:16 <matjazp> #link Agenda at https://etherpad.openstack.org/p/training-guides-meeting-agenda
13:04:41 <matjazp> ok, standard agenda ;)
13:04:50 <ianychoi> okay
13:04:55 <matjazp> #topic Upstream training
13:05:03 <matjazp> many new developments here
13:05:14 <matjazp> ildikov: can you summarize?
13:05:25 <ildikov> matjazp: sure
13:05:36 <matjazp> ildikov: for the meeting minutes :)
13:06:00 <ildikov> so we started to build a team of trainers/coaches
13:06:44 <ildikov> we wanted to have more interaction before the training and ensure that who's coming to help out are familiar with the purpose of the training and the content as well
13:07:39 <ildikov> we are also working on to continuously evolve the format and the content of the training and now we have more eyes on this too and more people to give us ideas
13:08:09 <ildikov> on the administrational side we renamed the program to OpenStack Upstream Institute
13:08:17 <ildikov> #link https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute
13:08:19 <matjazp> #info Upstream training -> OpenStack Upstream Institute
13:08:33 <ildikov> the above link is the team wiki page
13:08:59 <ianychoi> Oh kmARC will come - great :)
13:09:04 <ildikov> we are trying to build a liaison team having people from each project
13:09:17 <ildikov> ianychoi: +1 :)
13:09:30 <matjazp> #info new dedicated IRC channel for Upstream efforts: #openstack-upstream-institute
13:09:42 <ildikov> we also have an IRC channel
13:10:06 <ildikov> #info IRC for the training program is #openstack-upstream-institute
13:10:42 <ildikov> the channel is also open for people who are interested in on boarding new people to their projects/to the community
13:10:53 <ildikov> so don't restrict it to only training related topics
13:11:29 <asettle> Okay :) joined!
13:11:36 <trevormc> o/
13:11:37 <ildikov> #info weekly meeting of the training team: 2000 UTC, #openstack-meeting-3
13:12:06 <ildikov> matjazp: I think that's all in a nutshell
13:12:11 <ianychoi> Unfortunately it is difficult to join but I will follow meeting minutes
13:12:14 <ildikov> does anyone has any questions?
13:12:20 <matjazp> ildikov: yes, thnx, this all sound really great
13:12:24 <ildikov> ianychoi: I know, sorry about that :(
13:12:47 <ianychoi> +1 :) ildikov: fine, I have not replied the survey because at that time I was too busy.. :(
13:12:50 <ildikov> ianychoi: I think we could do a short catch up on Tuesday withthose who cannot join on MOnday
13:13:13 <ildikov> ianychoi: I know about 3 people who would be interested for sure and I think we have at least two more who might be
13:13:46 <ildikov> ianychoi: we went to the slot where the majority of people could join from those who replied
13:14:09 <matjazp> ildikov: yes, we can do a summary of the meeting here
13:14:14 <ildikov> ianychoi: unfortunately we're covering the globe, so there's no magic slot and the Boston training is too soon to alternate
13:14:19 <ianychoi> ildikov, yep this is how survey is so important :) I am really fine and I will follow meeting minutes :)
13:14:53 <ildikov> ianychoi: we can catch up on the team IRC, that will be informative to everyone who couldn't join the day before for any reason
13:15:12 <ildikov> matjazp: yep, we can have a short update here too
13:15:18 <ianychoi> ildikov, I totally understand, don't worry about it :)
13:15:30 <ildikov> matjazp: one quick question
13:16:00 <matjazp> ildikov: sure
13:16:21 <ildikov> matjazp: do I remember correctly we agreed in storing the VM image source under the training-guides repository?
13:16:27 <matjazp> yes
13:16:50 <matjazp> and publish the VM on infra's servers
13:17:01 <ianychoi> maybe.. tarballs.o.o?
13:17:03 <matjazp> tarballs.o.o ?
13:17:14 <matjazp> yes, I believe so
13:17:17 <matjazp> just the last
13:17:20 <matjazp> image
13:17:26 <ildikov> yes, we will do the publishing
13:17:30 <matjazp> not an archive
13:17:31 <ianychoi> #link http://tarballs.openstack.org/training-labs/images/
13:17:37 <matjazp> no
13:17:46 <ildikov> kmARC is updating the image now to use Ocata and we will get the image manually updated once it's ready
13:17:49 <matjazp> that is for training labs, not training guides
13:17:50 <ildikov> then work on the automation
13:17:51 <ianychoi> This is what I found and I used it during Korean local upstream training
13:18:29 <ianychoi> ildikov, would you move the location from http://tarballs.openstack.org/training-labs/images/ to training-guides - e.g.) http://tarballs.openstack.org/training-guides/images/ ?
13:18:33 <ildikov> ianychoi: kmARC's VM image is not uploaded to tarballs.o.o yet
13:18:40 <matjazp> ? I dont know actually... is this the right image?
13:18:49 <ianychoi> hmm.. really
13:19:07 <ildikov> I asked him yesterday and he said they didn't upload any version finally
13:20:07 <matjazp> ianychoi: is this a usable image? for all the upstream training purposes?
13:20:44 <ianychoi> matjazp, I remember that ildikov asked to infra team to upload such ova image
13:21:16 <matjazp> ildikov: do you know if this is the right image?
13:21:27 <ianychoi> (I am one of observers in #openstack-infra IRC channel.. haha)
13:21:45 <ildikov> matjazp: according to what kmARC said yesterday his image is not supposed to be on tarballs.o.o
13:22:01 <ildikov> we talked about uploading the image with the infra guys
13:22:22 <ildikov> they were also looking into automating the image build and upload but they ran into some issues
13:22:36 <ildikov> so we need to investigate that once we get there to have bandwidth for that
13:22:57 <matjazp> ildikov: but as you know it, this is not it?
13:23:17 <ildikov> matjazp: ianychoi: the date of that image you copied the link here is October 19 last year
13:23:25 <spotz> Ok back and here ish:)
13:23:37 <ildikov> matjazp: ianychoi: we discussed to upload the image somewhere way after that as I remember
13:23:54 <matjazp> ildikov: yes, that is what I remember
13:24:11 <matjazp> so to sum it up:
13:24:12 <ianychoi> ildikov, yep.. I think so... you would be the right
13:24:15 <ildikov> the October date is before the Barcelona Summit
13:24:22 <ildikov> so it cannot be Mark's image
13:24:31 <matjazp> 1) we need to port the KMarc's code to the training guides repo
13:24:51 <matjazp> 2) we publish manually created image under tarballs.o.o
13:25:00 <matjazp> 3) we automate the creation process
13:25:46 <ildikov> matjazp: +1
13:25:52 <matjazp> ildikov: maybe this is the image that Roger and Pranav created with their osbash scripts and is alreaddy preinstalled
13:26:01 <ildikov> matjazp: automation will most likely happen after the Boston training
13:26:14 <ildikov> matjazp: that can be
13:26:15 <matjazp> ildikov: yes, that's why I included step #2
13:26:36 <ildikov> matjazp: cool, tnx
13:27:11 <matjazp> ildikov: can Mark submit the patch? Or is he busy with other stuff?
13:27:18 <ianychoi> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-01-17.log.html#t2017-01-17T17:12:10
13:27:32 <ildikov> matjazp: you mean to move the source to our repo?
13:27:34 <ianychoi> It was tested on January with October image
13:27:55 <matjazp> ildikov: yes
13:28:10 <matjazp> now that he no longer works with openstack
13:28:26 <ianychoi> matjazp, but his name is in: https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute :)
13:28:30 <matjazp> maybe he doesn't have time to do it=
13:29:06 <ildikov> matjazp: he will come to the training and works on the image
13:29:13 <matjazp> great
13:29:17 <ildikov> matjazp: I will double check with him
13:29:38 <ildikov> matjazp: do you have any preference where the folder should go under the project tree?
13:29:51 <matjazp> just not under docs :)
13:30:03 <ildikov> ok :)
13:30:18 <ianychoi> #link http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-01-17.log.html#t2017-01-17T16:17:24
13:30:36 <ianychoi> Maybe.. we need to move http://tarballs.openstack.org/training-labs/images/ to http://tarballs.openstack.org/training-guides/images/
13:30:50 <matjazp> oh, and maybe not labs? It's to confusing
13:31:02 <matjazp> ianychoi: definitely
13:31:22 <ildikov> ianychoi: hmm, then the date must be when the image was modified or smth
13:31:46 <ianychoi> I remember it because at that time I was seeing infra channel a lot for i18n issues..
13:31:57 <ianychoi> ildikov, that's fine we can change :)
13:32:04 <ildikov> ianychoi: I think it's ok to clean this up once we have the new image ready
13:32:08 <matjazp> Image can also stay there as far as I'm concerened.. but then the automation process would be problemativ
13:32:13 <ildikov> ianychoi: I will talk to the infra guys
13:32:17 <ianychoi> ildikov, +1 :)
13:32:24 <ildikov> ianychoi: thanks for double checking
13:32:35 <ianychoi> ildikov, no problem
13:35:14 <matjazp> we can publish Mark's code under /images, and we can also use the same folder under tarballs.o.o for the created images? So when you look into the repo, you see the code for the image creation and the automation process publishes it under tarballs.o.o/training-guides/images?
13:35:32 <ianychoi> matjazp, +1 for me
13:35:33 <matjazp> or maybe even tarballs.o.o/training-guides/
13:35:45 <matjazp> so no images subfolder
13:36:02 <matjazp> as this will be the only artefact there
13:36:07 <ianychoi> It completely depends on which files would be needed to be synced
13:36:33 <ildikov> matjazp: sounds good
13:36:59 <ildikov> matjazp: I have no idea at this point what was the issue with the automation last time
13:37:17 <ildikov> matjazp: but if we decided the placement of the files that's already a good step
13:37:31 <matjazp> ildikov: problems with vagrant in the infra's VMs?
13:37:46 <ianychoi> ildikov, question: automation means.. that creating an ova file in openstack-infra using DevStack?
13:38:23 <ildikov> ianychoi: building the image and uploading it to tarballs.o.o
13:38:39 <matjazp> automation = creating the new image when code in /images repo changes
13:38:50 <ildikov> matjazp: maybe, I wasn't deeply involved in that part, I'm guessing it's in the IRC logs somewhere
13:38:52 <ianychoi> ildikov, my questioin is that where the build of the ova file occurs - in openstack-infra? or kmARC's local computer?
13:39:04 <matjazp> ianychoi: infra
13:39:08 <ildikov> ianychoi: should happen in infra
13:39:27 <matjazp> but for Boston, we'll build it by hand
13:39:43 <matjazp> automation won't be ready for this in time
13:39:49 <ianychoi> Since kmARC's current script depends on VirtualBox & Vagrant, some more things would be needed with the help from infra team I think
13:40:24 <ildikov> matjazp: +1
13:40:26 <ianychoi> I see :) Since running DevStack in openstack-infra dynamically would be some issues..
13:41:13 <matjazp> I think that mkARC now the details
13:41:24 <matjazp> now=know
13:41:38 <ianychoi> Yep I wanna ask the details on the next irc meeting or during Boston Summit
13:41:49 <ianychoi> And I wanna help :)
13:42:02 <ildikov> ianychoi: we can spend time on the automation during the Summit
13:42:14 <ianychoi> ildikov, great! :)
13:42:38 <matjazp> ok, can we switch the topic to the AOB?
13:42:50 <ianychoi> +1
13:42:51 <ildikov> yep, that's all from me
13:43:03 <matjazp> #topic Any other business
13:43:20 <matjazp> so is there anything that needs a discussion?
13:43:35 <ianychoi> #link https://bugs.launchpad.net/openstack-training-guides
13:43:42 <ianychoi> #link https://blueprints.launchpad.net/openstack-training-guides
13:43:57 <ianychoi> If we have time, how about reflecting current status into the both?
13:44:27 <matjazp> huh, we can delete all the BPs
13:44:55 <ianychoi> So... training-guides speciality team will not use BPs?
13:44:57 <matjazp> latest were from 2014
13:45:29 <matjazp> they should be with the docs bps
13:46:11 <ianychoi> Then, for example, upstream training VM image stuff needs to be described in docs-specs?
13:46:47 <ianychoi> Sometimes I am a little bit confused - how Docs team and training-guides specialty team work together
13:46:57 <ianychoi> That's the motivation from my asking
13:47:16 <asettle> ^^ what ianychoi said :p
13:47:31 <asettle> We kinda don't work together, I mean, we do... but... we don't. At least, such is my understanding.
13:47:58 <matjazp> yes, the thing evolved from a separate project
13:48:17 <matjazp> then the training labs split the project in half
13:48:39 <matjazp> and we both became a speciality teams under docs
13:49:09 <matjazp> so I send Alex my updates, and she publishes them in the Whats up doc
13:49:34 * asettle waves
13:49:54 <asettle> It gives the team exposure to what they're doing - esp as the doc goes out to dev, I18n, and doc
13:50:10 <asettle> We offer any help, and visa versa.
13:50:29 <matjazp> so we should be using docs-spec for our BPs
13:50:41 <matjazp> asettle: exactly
13:51:22 <asettle> So far, the process works ;) core reviews are all different too.
13:51:34 <matjazp> and delete this old stuff under blueprints.lp.net/openstack-trtaining-guides
13:52:03 <ianychoi> Yep I do not say that current process has problems.
13:53:04 <matjazp> if there are any suggestions, we can improve the process
13:53:13 <ianychoi> For better documentation stuff then I think the collaboration with Docs team is great
13:54:15 <ianychoi> As matjazp mentioned previously, it would be much nice if we change hydroglyph+rst into better slide format & style
13:55:09 <ianychoi> For such stuff then describing in docs-specs would be the best I think
13:55:14 <matjazp> yes, e.g. reveal.js is soooo much nicer and has a big community..
13:55:50 <ianychoi> But VM image automation is related with both training-guides and upstream training, then in the case, writing a spec into docs-specs would be nice or openstack-infra?
13:56:22 <matjazp> good question... I say docs-specs
13:56:38 <matjazp> with reviews from infra team
13:57:15 <matjazp> 3 minutes left
13:57:39 <ianychoi> Yep.. I now agree with matjazp
13:58:09 <matjazp> ok time's almost up
13:58:13 <ildikov> sounds good, we can look into this in Boston
13:58:30 <matjazp> thank you all for your time
13:58:36 <ianychoi> ildikov, +1 :)
13:58:37 <ildikov> thanks!
13:58:39 <ianychoi> Thanks you all!
13:58:41 <matjazp> see you in 2 weeks
13:58:52 <matjazp> in the mean time, let's sync over Docs ML
13:59:04 <ildikov> matjazp: +1
13:59:13 <ianychoi> matjazp, +1
13:59:18 <matjazp> bye all
13:59:22 <ianychoi> Bye :)
13:59:26 <ildikov> bye :)
13:59:32 <matjazp> #endmeeting