17:01:47 #startmeeting training-guides 17:01:48 Meeting started Mon Sep 21 17:01:47 2015 UTC and is due to finish in 60 minutes. The chair is matjazp. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:51 The meeting name has been set to 'training_guides' 17:02:05 hey mgrohar bgmccollum 17:02:09 roll call 17:02:16 hey 17:02:22 howdy 17:02:47 #link agenda https://wiki.openstack.org/wiki/Meetings/training-guides 17:03:03 #topic Action items review 17:03:14 ok, lets see last week's action items 17:03:38 you all know that you can see meeting minutes at http://eavesdrop.openstack.org/meetings/training_guides/2015/training_guides.2015-09-14-17.01.html 17:04:02 sorry, I'm late..here. 17:04:09 have it pulled up :) 17:04:10 hey cloudtrainme 17:05:04 #info no repllies on ML about "screenshot pastebin", so let's wait a bit for this 17:05:28 nothing else I see 17:05:33 ok moving on 17:05:50 #topic Upstream training progress 17:05:52 matjazp: do you have a set of requirements we can work against for the imgbin? 17:06:15 bgmccollum: did you see my mail on ML? 17:06:26 which list? 17:07:11 #link http://lists.openstack.org/pipermail/openstack-docs/2015-September/007448.html 17:07:22 We're using Docs ML 17:07:45 #ilink http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs 17:07:59 thanks 17:08:33 ok back to upstream training 17:08:55 bgmccollum squashed 2 bugs last week. congrats! :) 17:09:21 thanks! 17:09:50 we also have a new landing page 17:09:59 it is already published at 17:10:26 #link http://docs.openstack.org/draft/upstream-training 17:11:02 #info upstream material has a new landing page, published as draft at http://docs.openstack.org/draft/upstream-training 17:11:37 #info old slide-only landing page is still there at http://docs.openstack.org/draft/upstream-training/slide-index.html 17:12:15 New LP looks great. I like it. 17:12:24 the question is do we fill all the stuff we have on the Wiki into this? 17:12:56 #link #link https://wiki.openstack.org/wiki/OpenStack_Upstream_Training 17:13:30 What are the other Docs teams doing? Are they still using Wiki? 17:13:46 not for docs 17:13:58 just for some bookkeeping stuff 17:14:26 I like the idea of moving out wiki content to the LP, but I can be swayed if someone feels differently. 17:14:35 maybe it would be better if we also discuss this on the ML 17:15:03 sounds good 17:15:13 and ping Tim and Loic for an opinion 17:15:26 wikis tend to get "forgotten" and outdated...having it in code seems like more eyeballs would catch changes 17:15:57 #action matjazp asks about moving stuff from Upstream's wiki to the repo on Doc ML 17:16:59 bgmccollum: yes, my thoughts exactly, but wiki is ideal for last minute changes... let7s see what the other trainers think of this 17:17:13 agree with bgmccollum 17:18:04 ok, so I'll start the debate on ML, and you guys can chip in with replies to increase mail thread's visibility ;) 17:18:45 if you're not subscribing our ML, you should.. see link above 17:19:38 I'm marking training guide's msgs with "[training guides]" in the Subject 17:20:27 anyway, upstream is progressing nicely 17:21:04 currently there are only 5 bugs not assigned 17:21:19 #link https://bugs.launchpad.net/openstack-training-guides/?field.searchtext=upstream&orderby=-importance&search=Search&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branche 17:21:19 s=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on 17:21:24 huh 17:21:34 too long 17:22:25 #link https://bugs.launchpad.net/openstack-training-guides/?field.searchtext=upstream&search=Search&assignee_option=none 17:22:30 this should do it 17:23:00 but you can also see the whole list at https://bugs.launchpad.net/openstack-training-guides/ 17:23:05 it's not so long 17:24:34 picked up the horizon screenshot 17:24:36 we still need to scan for bugs on the last few chapters 17:24:48 bgmccollum: great 17:25:10 also i have some content about eavesdrop, so i might pick that up as well time permitting 17:26:07 I made a quick scan up to devstack chapterscanned 17:26:55 I'll try to look it up and enter more bugs 17:27:18 anything else for upstream? 17:28:04 ok, moving on 17:28:14 #topic training slides 17:28:48 upstream training is a priority, as it is due in a month 17:29:04 cloudtrainme: any progress on nova? 17:29:21 matjazp: I'm running into some issues with tox 17:29:34 trying to build the slides but the training-slides target is failing 17:29:55 what's the error message? 17:30:00 bgmccollum: are looking at it this morning. 17:30:06 cloudtrainme: try tox -r to recreate the venvs 17:30:13 then tox -e 17:30:32 cloudtrainme: tox -e training-slides 17:30:51 and for upstream tox -e upstream-slides 17:32:02 This is the error: ERROR: InvocationError: '/Users/bgmccollum/Documents/training-guides/.tox/upstream-slides/bin/sphinx-build -b html doc/upstream-training doc/upstream-training/build/slides doc/upstream-training/index.rst' 17:32:08 "hard reset" is to just delete .tox dir ;) 17:33:45 this is if you build for upstream training 17:33:50 ImportError: No module named openstackdocstheme 17:33:59 asselin, printenv returned nothing 17:34:37 this looks like it has no sphinx-build installed 17:34:46 maybe it didn't create venv right 17:35:25 cloudtrainme and I will continue to debug offline 17:35:41 I sometimes just delete .tox and start over 17:35:49 i reset hard and same 17:37:10 same error? 17:38:02 I think my issue is a venv error because when I run the sphinx commands or doc8 commands directly, they work. 17:38:50 My error: ERROR: InvocationError: '/Library/Frameworks/Python.framework/Versions/2.7/bin/doc8 doc/training-guides' 17:40:07 I just tried a fresh clone of the repo and got the errorabout pip beeing too old 17:41:11 oh, and I'm using the latest brew'd python 2.x 17:41:46 and in the summary ERROR: upstream-slides: could not install deps 17:41:51 something like that? 17:43:48 im rebuilding to see 17:44:08 does it install all the dependencies ok? 17:45:03 I've seen complaints about docutils module not loaded 17:46:42 this is what i get running from a `git reset --hard` environment -- http://paste.openstack.org/show/473042/ 17:46:53 it should load openstackdocs theme automatically 17:47:45 `openstackdocstheme` is not getting installed from what i can tell 17:48:43 this is a fresh clone of the repo on my comp http://paste.openstack.org/show/473055/ 17:49:42 on os x, with Python 2.7.9 and pip 7.1.2 17:50:03 this is what it should look like 17:50:40 I just cloned a repo and run tox -e upstream-slides 17:51:17 I'm on Python 2.7.6rc1 and pip 7.1.2 17:51:28 going to upgrade Python and see what I get. 17:51:43 im on python 2.7.10 pip 7.1.2 17:51:53 it shouldn't matter 17:52:03 my upstream-slides venv doesn't have `openstackdocstheme` installed 17:52:46 that was recently added for the new landing page, yes? 17:52:58 if you look at the conf.py, it should load it automatically 17:53:14 html_theme_path = [openstackdocstheme.get_html_theme_path()] 17:53:42 oh.. do you have an old repo content? 17:53:55 just pull the latest stuff 17:53:58 is that something that needs to be install system wide, out-of-band of the venv requirements? 17:54:13 im in master, up to date 17:54:22 no, it is mentioned in the test-requirements.txt 17:54:47 so it get's loaded when you start tox 17:55:01 pip freeze for the tox env doesn't show it installed though 17:55:29 but if you have old tox env, maybe it is better to just recursively delete .tox folder 17:55:37 bgmccollum: that's it 17:55:44 recreate env 17:55:59 so that it loads all required stuff 17:56:27 i git reset --hard, git pull latest, basically nuked everything and its still not getting installed 17:56:44 but .tox remains 17:56:59 it is in git ignore 17:57:24 did you delete .tox folder? 17:57:47 i did...but let me try one more time 17:58:08 just clone again and start on the fresh copy 17:58:13 huh.. 17:58:22 time's almost up 17:58:46 matjazp: sorry to derail the meeting...I know we're out of time. 17:59:00 cloudtrainme: no problems, we were done anyway 17:59:10 ok, see you guys next week 17:59:23 okay, we will reach out if we can't get this to work 17:59:25 ping me if you still have issues with the environment 17:59:26 thanks matjazp, we'll work though this 17:59:36 thanks. bye. 17:59:39 bye 17:59:43 #endmeeting