Wednesday, 2015-08-12

-openstackstatus- NOTICE: Zuul was restarted due to an error; events (such as approvals or new patchsets) since 23:01 UTC have been lost and affected changes will need to be rechecked00:04
*** mrodden has quit IRC00:21
*** britthouser has quit IRC01:30
*** britthouser has joined #openstack-ansible01:39
*** alejandrito has quit IRC01:55
*** britthouser has quit IRC02:52
*** fawadkhaliq has joined #openstack-ansible03:22
*** dabernie_ has joined #openstack-ansible03:23
*** dabernie has quit IRC03:26
*** sdake_ has joined #openstack-ansible03:35
*** sdake has quit IRC03:39
*** sdake_ is now known as sdake03:46
odyssey4meo/05:17
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/20757705:32
*** fawadkhaliq has quit IRC05:38
*** pellaeon has quit IRC05:38
odyssey4memattt andymccr hughsaunders as soon as you're in, please review https://review.openstack.org/207576 and https://review.openstack.org/207577, both of which are crucial to adding a docs check which will allow our docs to merge05:50
*** fawadkhaliq has joined #openstack-ansible05:59
*** javeriak has joined #openstack-ansible06:13
*** sdake_ has joined #openstack-ansible06:35
*** sdake has quit IRC06:39
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated master for new dev work - Liberty-2  https://review.openstack.org/19912606:46
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated master for new dev work - Liberty-2  https://review.openstack.org/19912606:52
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Update kilo for new dev work - 10 Aug 2015  https://review.openstack.org/21126507:07
*** fawadkhaliq has quit IRC07:12
*** fawadk has joined #openstack-ansible07:13
*** javeriak has quit IRC07:19
*** javeriak has joined #openstack-ansible07:20
*** javeriak has quit IRC07:32
*** javeriak_ has joined #openstack-ansible07:40
*** javeriak_ has quit IRC07:46
*** javeriak has joined #openstack-ansible07:46
*** javeriak_ has joined #openstack-ansible07:50
*** javeriak has quit IRC07:50
*** javeriak_ has quit IRC07:54
*** javeriak has joined #openstack-ansible07:54
matttodyssey4me: is teh former the correct review?07:56
odyssey4memattt that one's already fine - it needs the other one to merge before it can go through07:57
openstackgerritChristian Berendt proposed stackforge/os-ansible-deployment: Run bash through /usr/bin/env  https://review.openstack.org/21188507:57
odyssey4mesorry, I didn't notice that it was already two +2's07:57
odyssey4mehttps://review.openstack.org/207577 is the one you want07:58
odyssey4meand we'll have to backport that to both kilo and juno, although juno will need some adjustment07:58
odyssey4meI'll handle the backports, but I'll need support to get them merged quickly as there's a new -infra gate job which will require those to be in place in order to pass gate checks07:58
matttodyssey4me: there is an HP reference in https://review.openstack.org/#/c/207577/4/setup.py, is that correct?08:00
odyssey4memattt yep, that matches where it came from08:00
matttok done08:02
*** sdake_ has quit IRC08:04
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Update kilo for new dev work - 10 Aug 2015  https://review.openstack.org/21126508:07
odyssey4methanks mattt08:07
*** javeriak_ has joined #openstack-ansible08:33
*** javeriak has quit IRC08:35
*** javeriak has joined #openstack-ansible08:41
*** javeriak has quit IRC08:43
*** javeriak_ has quit IRC08:44
openstackgerritChristian Berendt proposed stackforge/os-ansible-deployment: Create /openstack/log/instance-info prior to using it  https://review.openstack.org/21190608:49
odyssey4memattt if you could please review https://review.openstack.org/209047 that'd be awesome so we can update master to liberty-2 in the follow on patch08:53
*** metral is now known as metral_zzz08:55
*** metral_zzz is now known as metral09:04
*** javeriak has joined #openstack-ansible09:13
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Add iptables rule to neutron agents containers  https://review.openstack.org/21191809:14
matttodyssey4me: you still there ?09:18
matttodyssey4me: in https://review.openstack.org/#/c/209047/, what specifically is 'overcoming import race conditions'?09:19
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Add iptables rule to neutron agents containers  https://review.openstack.org/21191809:27
*** javeriak_ has joined #openstack-ansible09:27
*** javeriak has quit IRC09:28
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Add iptables rule to neutron agents containers  https://review.openstack.org/21191809:35
*** javeriak_ has quit IRC09:52
*** javeriak has joined #openstack-ansible09:53
*** javeriak has quit IRC09:59
*** javeriak has joined #openstack-ansible10:02
*** javeriak has quit IRC10:06
*** fawadk has quit IRC10:41
*** javeriak has joined #openstack-ansible10:42
*** javeriak has quit IRC10:55
evrardjpgood afternoon guys11:40
evrardjpis the rackspace ELK stack for kilo already released somewhere? It's still mentionned in OSAD docs11:48
evrardjprsyslog is really a pain for debugging logs11:49
evrardjp;)11:49
*** britthouser has joined #openstack-ansible11:53
*** britthou_ has joined #openstack-ansible11:54
*** britthouser has quit IRC11:57
odyssey4meevrardjp there are only RC's at this stage - https://github.com/rcbops/rpc-openstack/tree/r11.0.0rc13 is the latest12:01
odyssey4memattt without that patch, oslo.middleware pukes occasionally when apache loads the keystone wsgi - which causes 500 errors in keystone12:03
odyssey4methat patch isolates the threads properly, resulting in no race conditions between the threads when trying to load their deps12:03
odyssey4meadmin & service are also appropriately segregated into their own application groups12:04
odyssey4meI didn't get much out of the keystone guys about the details of the race conditions, but that patch was based on advice from the keystone cores12:04
matttodyssey4me: ok cool, i'm pretty much g2g then ... but what about hugh's comment about stuff breaking if setup isn't run?12:05
mattthughsaunders: what did you mean there?12:05
odyssey4memattt fyi: https://github.com/openstack/keystone/blob/master/httpd/wsgi-keystone.conf12:05
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Add iptables rule to neutron agents containers  https://review.openstack.org/21191812:05
hughsaundersmattt: where?12:05
mattthughsaunders: https://review.openstack.org/#/c/209047/12:06
odyssey4memattt hughsaunders I think he means the entries in the defaults12:07
odyssey4mewe use the ansible_processor_vcpus but default them in case they don't exist12:07
matttodyssey4me: yeah the dynamic values, but what is the implication of doing that?12:07
odyssey4mewell, those were the values we previously had - so I've maintained the same pattern, but just put them into variables instead of the template12:08
hughsaundersmattt: keystone_wsgi_threads: "{{ ansible_processor_vcpus | default(2) // 2 }}"12:09
odyssey4meI agree with hugh that it probably doesn't make sense to have them there as those facts will always exist if someone runs ansible in a normal way, but hughsaunders mentioned that it is slightly possible that someone may run it without the gathering facts stage, in which case those defaults will take effect12:09
odyssey4meit's an edge case12:09
hughsaunderswhat odyssey4me said12:09
odyssey4meI do think that we should probably remove it at some stage, but I didn't want to change the values in this patch - I just wanted to have variables to override and adjust the config so that keystone works12:10
openstackgerritChristian Berendt proposed stackforge/os-ansible-deployment: Adds a pep8 target to tox.ini  https://review.openstack.org/20766212:17
mattti see, so preferably let ansible fail if the facts don't exist12:17
matttok, since you're not changing behaviour that seems ok to me12:17
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Add iptables rule to neutron agents containers  https://review.openstack.org/21191812:18
odyssey4methanks mattt12:19
*** woodard has joined #openstack-ansible12:20
matttnp12:21
openstackgerritChristian Berendt proposed stackforge/os-ansible-deployment: Removes trailing whitespace for bashate  https://review.openstack.org/20766312:25
openstackgerritChristian Berendt proposed stackforge/os-ansible-deployment: Removes tab indents for bashate  https://review.openstack.org/20766412:25
openstackgerritMerged stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/20757712:30
*** bapalm has joined #openstack-ansible12:31
*** shausy has joined #openstack-ansible12:32
openstackgerritChristian Berendt proposed stackforge/os-ansible-deployment: Make the tox docs environment workable  https://review.openstack.org/21200212:37
*** KLevenstein has joined #openstack-ansible12:49
*** tlian has joined #openstack-ansible12:50
*** wmlynch has joined #openstack-ansible12:53
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/21201112:58
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/21201112:58
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/21201513:02
odyssey4mehughsaunders andymccr mattt palendae sigmavirus24_awa please review these backports asap as they are required to fix the doc gating: https://review.openstack.org/212011 https://review.openstack.org/21201513:04
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Move ansible logging to gate-check script only  https://review.openstack.org/21173013:05
*** wmlynch has quit IRC13:10
*** britthou_ has quit IRC13:14
openstackgerritMerged stackforge/os-ansible-deployment: Improve Keystone Apache configuration  https://review.openstack.org/20904713:14
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Improve Keystone Apache configuration  https://review.openstack.org/21202113:18
openstackgerritMerged stackforge/os-ansible-deployment: Add ebtables to neutron agent configuration  https://review.openstack.org/21059313:21
openstackgerritMerged stackforge/os-ansible-deployment: Add ebtables to neutron agent configuration  https://review.openstack.org/21059313:21
*** vdo_ has joined #openstack-ansible13:21
matttodyssey4me: i think i've heard you say that 5x in the past week :P13:31
odyssey4memattt this time it's for real-real13:31
matttdone13:31
odyssey4melast time it was a juno patch, but -infra wanted us to use the standard docs tests instead of our home grown frankenscripts13:31
odyssey4meso now we do it right13:32
odyssey4methanks13:32
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Add iptables rule to neutron agents containers  https://review.openstack.org/21191813:33
*** jaypipes has joined #openstack-ansible13:42
*** sdake_ has joined #openstack-ansible14:00
*** spotz_zzz is now known as spotz14:00
*** javeriak has joined #openstack-ansible14:01
odyssey4meandymccr mattt you missed this one :p https://review.openstack.org/21201514:01
odyssey4mehughsaunders palendae  sigmavirus24_awa ^ (backport)14:01
dstanekodyssey4me: i just commented on the tox kilo backport - the change by itself is broken14:03
odyssey4medstanek how so?14:04
odyssey4meah dstanek so that's ok - we'll get that other patch backported14:04
dstanekk, that change should be an easy merge and backport14:05
odyssey4methe issue here is that no docs patches are able to merge because we have an infra-job that skips the commit/lint jobs for pure doc patches14:05
*** javeriak has quit IRC14:05
odyssey4me-infra did some fixups a little while ago which closed a loophole we happened to be using14:05
odyssey4methey fixed a bug, and since then our skip tells zuul to ignore our doc patches14:05
odyssey4meso I've submitted a patch in -infra to add a docs gate check, but for that to even run we need your patch in every branch14:06
odyssey4meI know that it will fail without the ceilometer fix, but that will give incentive to merge the ceilometer fix and backport it. :)14:06
dstanekodyssey4me: isn't that a chicken/egg problem since my patch won't run?14:07
odyssey4methat's why I remove the dependency14:07
odyssey4meso all we need to do is merge the ceilometer patch right after it14:07
odyssey4methat'll unblock the gate and the world will be a better place14:07
odyssey4memake sense?14:08
dstanekyeah, i'll just be happy to start seeing those reviews get out of my dashboard view14:09
odyssey4me:) me too14:09
odyssey4medstanek this is what's needed to clear that docs queue: https://review.openstack.org/21049814:12
odyssey4meI expect that we'll get the +w today in the next few hours14:12
*** sigmavirus24_awa is now known as sigmavirus2414:13
*** shausy has quit IRC14:17
*** shausy has joined #openstack-ansible14:17
*** britthouser has joined #openstack-ansible14:21
*** yaya has joined #openstack-ansible14:21
dstanekodyssey4me: nice. that looks more like what I'm used to14:21
*** Bjoern_ has joined #openstack-ansible14:21
*** javeriak has joined #openstack-ansible14:22
*** Mudpuppy has joined #openstack-ansible14:24
odyssey4medstanek :) I'd like to see if we can use more of the existing templated jobs, perhaps initially for the bashate and pep8 linting, then later for other things14:26
*** jmckind has joined #openstack-ansible14:26
*** Mudpuppy_ has joined #openstack-ansible14:27
*** Mudpuppy has quit IRC14:30
dstanekodyssey4me: yes, that's good goal to have. no more (or at least less) snowflake!14:31
*** cristicalin has joined #openstack-ansible14:31
*** Mudpuppy_ is now known as Mudpuppy14:32
cristicalinhi, anybody have issues with building the mysql-galera containers with latest master branch of osad ?14:32
cristicalinit fails for me at pip install python-MySQL14:32
odyssey4mecristicalin are you aware, first of all, that master of osad tracks openstack liberty?14:33
cristicalinyes, I am aware of that14:33
cristicalinbut this seems to be too basic to fail because of liberty14:33
odyssey4meok, cool - no, I haven't seen that - nor is our gate check... do you have a pastebin of the install log to inspect?14:34
cristicalingive me a sec, it's my first days with osad14:34
cristicalinwhere is the install log ?14:34
odyssey4mecristicalin also, are you using setup-infrastructure, or are you using run-playbooks.sh ?14:34
odyssey4mecristicalin the install log is output to the console14:35
cristicalinodyssey4me, I did it like this ./scripts/bootstrap-ansible.sh ./scripts/bootstrap-aio.sh ; cd playbooks ; openstack-ansible setup-everything.yaml14:35
odyssey4mecristicalin ah, then you're using the setup-infrastructure playbook which does an rsync from an upstream repo14:36
cristicalinhmm, ok I have to run it again with a tee to get the log14:36
odyssey4metry running the playbook 'repo-build.yml'14:36
odyssey4methen try 'cd /opt/os-ansible-deployment; ./scripts/run-playbooks.sh'14:37
cristicalinok14:37
odyssey4methe upstream repo for master is very likely broken at the moment - thanks for the reminder as I think I can rebuild it now14:37
odyssey4meah, not yet - need ot get https://review.openstack.org/199126 merged first14:38
*** javeriak_ has joined #openstack-ansible14:38
*** javeriak has quit IRC14:38
cristicalinis there any way to clean the environment to try with the kilo branch ?14:39
cristicalinor i need to deploy another vm14:39
odyssey4mecristicalin there's a script in the scripts directory called 'teardown' which will do an almost good job of tearing everything down14:40
odyssey4meit'll also destroy your /etc/openstack_deploy directory - so back that up if you care about it14:40
cristicalincurrently I'm trying to get an AIO to work so don't yet care about the openstack_deploy dir14:40
cristicalinI was hoping to try liberty and osad at the same time but ... one at a time is probably best14:41
odyssey4mecristicalin yeah - best would be to checkout 11.1.0 as a starting point14:41
cristicalinthat is kilo based ?14:42
odyssey4meuse teardown, then bootstrap-aio; bootstrap-ansible; run-playbooks14:42
odyssey4mecristicalin yep, that's the latest tag from the kilo branch14:42
odyssey4meas upstream is constantly changing in the upstream master branch, our master branch can behave differently from day to day14:43
odyssey4mebut we track the upstream branch so that we can fix things week by week and release our liberty branch only hours after upstream releases14:43
cristicalinok, I'll take that route first to understand how osad works14:43
odyssey4mecristicalin you may find http://osad.readthedocs.org/en/latest/ useful later too :)14:44
cristicalini'm looking for a tool that can be used for the lifecycle of the cloud not just for the initial deployment and osad at the moment seems as clode as it can get to that14:44
*** jmckind has quit IRC14:44
odyssey4mewe still need to do quite a bit of work on the docs, but they're helpful to understand some of the basics of how the config works14:44
cristicalinodyssey4me, already bookmarked that :) thanks14:44
odyssey4mecristicalin yep, OSAD is the basis for Rackspace Private Cloud and is deployed in many production deployments - both in RAX DC's and in customer DC's14:45
cristicalinodyssey4me, I got the log, are you still interested in it ?14:46
odyssey4mecristicalin sure14:46
cristicalinodyssey4me, http://pastebin.com/keYymJ5z14:49
odyssey4mecristicalin line 1377 shows the upstream clone14:51
odyssey4mea local repo build is preferred and advised, but let me fix the upstream repo - give me 30 mins or so14:52
*** galstrom_zzz is now known as galstrom14:52
*** alextricity has joined #openstack-ansible14:53
*** yaya has quit IRC14:54
cristicalinhmm, the teardown.sh leaves behind the loopback devices for swift14:57
cristicalinand for some reason losetup -d does not want to delete them :(14:58
cristicalinneed to reboot the test vm14:58
odyssey4mecristicalin if it's a test vm and you can destroy and rebuild, that'll be better15:00
odyssey4meotherwise yes, the teardown script could do with a little love15:00
odyssey4meas I recall they can't be deleted because they're still mounted - but we haven't had much chance to look into it15:00
odyssey4meupstream master wheel repo has been rebuilt, fyi15:01
odyssey4mepalendae sigmavirus24 andymccr mattt hughsaunders can we please get this review through the door? (update sha's and version for head of kilo) https://review.openstack.org/21126515:02
*** phalmos has joined #openstack-ansible15:05
*** meteorfox has quit IRC15:05
*** matt_____ has joined #openstack-ansible15:06
*** serverascode has quit IRC15:06
*** mattoliverau has quit IRC15:06
*** gus has quit IRC15:06
javeriak_hey guys, is it absolutely necessary to use actual target hostnames in openstack_user_config.yml, someone just mistakenly left them as infra1/infra2/infra3 etc, and the playbooks have completed fine, no actual testing has been done yet so I'm not sure if the deployment is in a healthy state15:06
*** meteorfox has joined #openstack-ansible15:07
odyssey4mejaveriak_ no, as long as the IP's are fine then it's fine - the playbooks put hosts files everywhere with those values15:08
*** gus has joined #openstack-ansible15:08
odyssey4meit would make my ocd tendancies turn me inside out, but hey - it's your environment :p15:08
sigmavirus24heh15:09
sigmavirus24poor odyssey4me15:09
*** serverascode has joined #openstack-ansible15:11
javeriak_odyssey4me, okay cool, this actually seems like a better way, instead of using the random hostnames people tend to give, it now has uniform containers prepended with infra1_ etc15:11
*** jwagner_away is now known as jwagner15:17
sigmavirus24odyssey4me: https://mail.python.org/pipermail/cryptography-dev/2015-August/000481.html Cryptography 1.0 was released today15:21
sigmavirus24We should remove the SHA pin we have for that for Keystone fernet tokens15:21
alextricityHello :). How is image sync'ing done in Kilo now? rsync?15:22
alextricityfor glance images15:22
odyssey4mesigmavirus24 every time I check, that crypto library still hasn't released a v1 - so I just let the sha update15:23
odyssey4mealextricity no change, a shared glance back-end is recommended15:23
odyssey4meso either NFS, or swift or cloudfiles15:23
alextricityinteresting. I set up a 11.0.4 build a few weeks back and it looks like some kind of syncing is going on.15:24
odyssey4meglance store hacks are bad, mmmmk15:24
alextricityBut maybe I did something and can't think of it right now15:24
odyssey4meoh sigmavirus24  I didn't see your message before that :) yes, in that case I think a follow-up patch to remove the pin to a sha is very necessary :)15:25
odyssey4mealextricity in an AIO build there's only one glance container - so no problem :p15:25
javeriak_odyssey4me: while we're on the topic of syncing glance images, if I didnt want to setup a backend storage nodes, whats the recommended way to simply sync images to save on all three infra's15:25
alextricityodyssey4me: No this is a clustered build15:25
openstackgerritErik Wilson proposed stackforge/os-ansible-deployment: Archive Keystone to Keystone Federation rst content  https://review.openstack.org/21174715:26
odyssey4mejaveriak_ there is no recommended way - the recommended way is to use a shared back-end of some sort15:26
odyssey4meyou could do something like rsync and cron it, but you'd have no guarantee that a new image would be on all controllers in time15:26
*** shausy has quit IRC15:27
odyssey4meso you'd have to also set your load balancer for glance to use one glance container as a primary, and the others only in backup mode15:27
odyssey4meand if you lose your primary glance container, you'd have to make your new primary do the syncing15:27
odyssey4meit's a mess, which is why there's no hack in osad for it15:27
javeriak_odyssey4me: why the later, if the image is present on all three, would it matter where the request landed?15:27
odyssey4methe right way to do it is to use nfs, swift, or ceph as a glance back-end15:27
odyssey4mejaveriak_ rsync would still take time to sync from one node to the others - before it's finished then other node may get the request15:28
javeriak_also i havnet had much time to look into any of these options, but I assume they each require setting up a separate storage node?15:29
odyssey4mejaveriak_ we don't facilitate the setup of anything except swift - all we do at this stage is allow you to configure which nfs/ceph back-end you wish glance to use15:29
odyssey4meyou would have to setup your nfs server or ceph cluster15:30
alextricityjaveriak_: For the NFS option, you could use the first glance container to host the NFS export15:30
odyssey4meyep, that's an option - just make sure you're doing your backups :)15:30
javeriak_okay yes I understand, customer deployments would of course use proper backends, for in-house testing, simply syncing and giving the images time to get to all containers seems the easiest atm :)15:31
odyssey4mejaveriak_ sure, do whatever you like in your own lab :)15:35
*** yaya has joined #openstack-ansible15:37
javeriak_haven't seen cloudnull around for a while?15:43
odyssey4mejaveriak_ he's on leave in europe, enjoying a disconnected holiday15:44
palendae"disconnected"15:46
palendaeHe's dropped in and done a few reviews15:47
openstackgerritgit-harry proposed stackforge/os-ansible-deployment: WIP: Generic ini conf template  https://review.openstack.org/21207915:47
javeriak_odyssey4me: lucky guy :)15:49
*** bapalm has quit IRC15:49
*** bapalm has joined #openstack-ansible15:49
*** yaya has quit IRC15:49
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/21201115:56
*** alop has joined #openstack-ansible15:57
*** matt_____ is now known as mattoliverau16:03
openstackgerritgit-harry proposed stackforge/os-ansible-deployment: WIP: Generic ini conf template  https://review.openstack.org/21207916:03
openstackgerritgit-harry proposed stackforge/os-ansible-deployment: WIP: Separate nova.conf vars from os_nova role  https://review.openstack.org/21208716:03
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Implement /usr/bin/env as the shebang in all bash scripts  https://review.openstack.org/21188516:07
*** sdake_ is now known as sdake16:13
odyssey4meSam-I-Am good question on https://review.openstack.org/211747 - the docs were meant to cover both how to set things up, but also how some of the things we do automagically are done manually16:17
odyssey4mebut I'd like to discuss how we can arrange the information in a way that's easier to consume16:17
*** sigmavirus24 is now known as sigmavirus24_awa16:18
odyssey4meI've learned that it's possible to use meetbot in this channel, so perhaps we should schedule a chat between myself, you and miguelgrinberg to discuss the content and cover any Q&A? Some time next week perhaps?16:18
Sam-I-Ami think the descriptions of things done automagically for end-users belong in devdocs16:19
Sam-I-Amthe things end-users need to do go in pre- and post- steps in the install guide16:19
palendaeJumping in here, but maybe we should clearly delineate between 'dev docs' and 'user/deployer docs'16:19
palendaeIn the hierarchy16:19
palendaeRight now it seems implicitly that everything not install guide is dev docs16:20
odyssey4mepalendae yeah, good point16:20
odyssey4meSam-I-Am the truth is that almost all that info is install guide material - the command line stuff is more operations guide material16:20
odyssey4methat could possibly go into upstream docs, actually16:21
odyssey4mebut we could also include it in dev docs to illustrate what we're automating16:21
odyssey4mepalendae I'm kinda of the opinion that that the in-repo docs should pretty much be dev docs... and we should have another repo for install docs which should target being added into the upstream install guide list16:22
palendaeThat's a reasonable stance16:23
Sam-I-Amodyssey4me: whats wrong with just the doc dir?16:23
Sam-I-Ami dont see a reason for a separate project16:23
odyssey4meit's pretty much the pattern for every other openstack project16:23
Sam-I-Amalthough, big-tentish... we could go in openstack-manuals16:23
Sam-I-Amif you look at fuel, their docs are in-tree16:23
palendaeThen again, yeah16:23
odyssey4medifferent dir for now, but not a different project - just a different repo16:23
*** erikmwilson has joined #openstack-ansible16:23
Sam-I-Amthere's the openstack devdocs too16:24
Sam-I-Amor devref, whatever you want to call it16:24
odyssey4mesure, so I'm happy with this case for now and a different directory is a good place16:24
odyssey4mebut there is going to come a time when a split makes more sense16:25
odyssey4meit'll give the operators and docs team more autonomy over their own patches without getting lost between code patches16:25
Sam-I-Amthe automated build process that dstanek is working on should help16:25
*** sigmavirus24_awa is now known as sigmavirus2416:25
odyssey4meSam-I-Am yep, I'm waiting for the final +2+w from -infra for that to become a gate check16:26
Sam-I-Amthere's probably three classes of things - install, operations, and devref16:26
odyssey4menext step will be to learn how to use the publishing process16:26
Sam-I-Amnone of which should duplicate upstream content16:26
odyssey4meSam-I-Am agreed16:26
KLevensteinso should we just go ahead and polish up the files in the federation docs patch, and worry about rearranging everything into different repos later?16:26
Sam-I-Amso... basically ops includes things specific to osad16:26
odyssey4meKLevenstein of course :)16:26
Sam-I-AmKLevenstein: polish as in make render nicely or polish as in make some sense of the blob16:27
Sam-I-Amright now there's no obvious rhyme or reason to the conent16:27
KLevensteinSam-I-Am: both, ideally16:27
Sam-I-Amcontent16:27
KLevensteinorganize the information, then make it render nicely16:27
odyssey4meSam-I-Am I think the OSAD user-base is probably more interested in devref and install docs at this point16:27
*** yaya has joined #openstack-ansible16:27
odyssey4menew operator entrants want the install guide, new developer entrants want the devref16:28
erikmwilsonWhy are putting out information on things that don't work yet?16:28
odyssey4meerikmwilson the stuff actually does work ,it's just not very pretty16:28
odyssey4meit's a little klunky to use for end-users16:28
odyssey4meso we're putting it out there in order for more operators and developers to be able to try it out and be informed16:29
erikmwilsonOk. What we need for the federation stuff is an overarching procedure that gives the order of all the sub procedures.16:29
*** phalmos has quit IRC16:29
Sam-I-Amideally the install guide is going to contain a section for configuring any features (including federation)16:29
palendaeI think also putting it down so we're not lost16:29
odyssey4meit's part of driving the conversation about federation and what needs to happen for real people to use it16:29
odyssey4meyes, there is what palendae said too - we did a ton of work, and a lot of people are interested in how to make it go... and in a month we'll probably need our own docs to remember :p16:30
KLevensteinokay, cool. so then our next steps are to get an overview of the process that fits all the pieces in the patch together, fix up the content accordingly, then make it render nicely as part of OSAD’s in-tree install guide16:32
erikmwilsonSounds good to me.16:33
KLevensteinerikmwilson: for RST formatting conventions etc., model it on what’s already there in the OSAD doc repo16:34
erikmwilsonWill do16:34
palendaethe install guide portion, ideally16:34
palendaeMost of the stuff outside the install guide doesn't match cause I just kinda wrote stuff16:34
KLevensteinrightyright16:34
palendaeWe'll need to make it all match. New stuff I write does16:34
KLevensteinpalendae: that’s what they pay us the tech writer bucks for :)16:35
palendaeyep!16:35
Sam-I-Amlol16:35
odyssey4meand away she goes: https://review.openstack.org/210498 expect to see a docs verify and merge check in zuul's list soon :)16:36
Sam-I-Amso... theres really no devref except for random readme fles?16:36
palendae\o/16:36
palendaeSam-I-Am: Everything i wrote was intended to be devref16:36
palendaeIn some areas it's kind blurred16:36
odyssey4mepalendae expect to see many gate failures until we fix the docs :)16:37
palendaeodyssey4me: Fine with me16:37
palendaeThough last I knew they were building just fine16:37
odyssey4mepalendae there's a series of patches from dstanek we need to hit and backport pronto16:37
odyssey4menext step I'd like to use -infra's bashate and pep8 lint checks instead of our own custom one16:38
*** vdo_ has quit IRC16:38
palendaeDepends on how their pep8 one works16:38
palendaeSince we have to locate our python files16:38
Sam-I-Ampalendae: what im really asking is, do we want a devref directory so we can structure this stuff16:39
Sam-I-Amrather than random files everywhere16:39
odyssey4mepalendae no matter, we'll work it out and perhaps patch the upstream job to be a little more flexible16:39
palendaeSam-I-Am: Yes, that was what I was thinking. 2 branches, devdocs and user16:39
odyssey4meSam-I-Am by 'random files' you mean the example files right?16:39
palendaeodyssey4me: I think he means the top level files in doc/16:39
palendaeAgain, they were intended to be dev docs so they were not random at all when it was made16:40
Sam-I-Amodyssey4me: anything .rst16:40
Sam-I-Amor .md i guess16:40
palendaeAre there .mds?16:40
Sam-I-Amthe example config files can be in the source16:40
Sam-I-Amor whatever16:40
*** persia has quit IRC16:42
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Adds ceilometer link in configure.rst  https://review.openstack.org/20757616:43
Sam-I-Amso, keystone seems to do this - https://github.com/openstack/keystone/tree/master/doc/source16:43
Sam-I-Amanything in there is devref16:43
Sam-I-Amobviously the install guide, config ref, and other bits (mostly for end users) live in other repos16:43
Sam-I-Amso, for now we can either make a devref dir... or move the install guide elsewhere16:44
KLevensteinany reason we can’t have devref live here: https://github.com/stackforge/os-ansible-deployment/tree/master/doc/source16:46
KLevensteinand keep the install guide as a subdir?16:46
odyssey4meKLevenstein Sam-I-Am  at this point why don't we consider both the install guide and devref docs all to be devrefs, until such time that it changes?16:48
KLevensteinthat seems reasonable to me16:48
odyssey4methe devrefs are just appendices?16:48
*** cristicalin has quit IRC16:48
KLevensteindoc re-architecting isn’t something to be done off the cuff anyway16:48
odyssey4meie deeper info on particular topics beyond the common use-cases covered by the install guide16:48
KLevensteinsounds good16:48
openstackgerritMerged stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/21201516:49
odyssey4me\o/16:49
KLevensteinsweet16:49
Sam-I-Amodyssey4me: i dunno, i think the install guide is pretty end-user friendly to be a devref16:50
odyssey4mestill waiting for the -infra patch to take effect... testing with a doc patch in review every now and again16:50
odyssey4meSam-I-Am yes it is, but this group will be adding more docs in the future that will not necessarily be friendly16:50
odyssey4methe professional docs people can then patch the docs to make them friendly16:51
KLevensteinthis is one of those cases where I’m okay with “work with what we have, redesign when we need to (but be aware that need for redesign is coming”16:51
odyssey4mewe can't hold the operators who want to add bits back from adding bits, even if their bits are in broken english16:51
odyssey4meKLevenstein agreed, we iterate with what we have - when it becomes unmanageable then we do a sprint to overhaul it16:52
*** javeriak has joined #openstack-ansible16:52
*** bapalm has quit IRC16:52
odyssey4mehahaha, the first merge fail due to a doc fail16:52
odyssey4mewe have docs checks in the gate people :)16:53
Sam-I-Amodyssey4me: which?16:53
odyssey4meSam-I-Am it's still processing - you'll have to check the zuul status board16:54
*** javeriak_ has quit IRC16:54
odyssey4mehttp://status.openstack.org/zuul/16:54
odyssey4mefilter for stackforge/os-ansible-deployment and expand by default16:54
odyssey4mehttps://review.openstack.org/207576 is the key review to unblock the master gate16:55
odyssey4meand it's just waiting for resources16:55
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Document required repository hosts config info  https://review.openstack.org/20225816:57
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Documentation of the static-route feature  https://review.openstack.org/20784916:57
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Cinder_volumes_containers are automatically tagged with is_metal  https://review.openstack.org/20986116:58
dstanekodyssey4me: i forgot that when i looked at your change job this morning that the templated docs job uses a tox environment that i didn't include17:15
dstanekodyssey4me: so i just have to add that for the job to work17:15
*** alop has quit IRC17:17
odyssey4medstanek oh dear, but for any change to merge it needs to include https://review.openstack.org/20757617:20
odyssey4meare you able to do the update quickly?17:20
openstackgerritDavid Stanek proposed stackforge/os-ansible-deployment: Adds venv environment to tox for -infra docs job  https://review.openstack.org/21211217:20
odyssey4medstanek you'll have to merge https://review.openstack.org/207576 and https://review.openstack.org/212112 otherwise the docs check will not pass17:21
dstanekodyssey4me: yes.... ^ that won't work.... updating the ceilometer review17:21
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Adds venv environment to tox for -infra docs job  https://review.openstack.org/21211317:22
odyssey4medstanek fyi, as we have no docs in-repo for juno that patch as it is will work just fine for that branch, so I've backported it17:23
openstackgerritDavid Stanek proposed stackforge/os-ansible-deployment: Adds ceilometer link in configure.rst  https://review.openstack.org/20757617:23
dstanekodyssey4me: ^ updated17:24
*** alop has joined #openstack-ansible17:24
odyssey4medstanek ta, oddly I don't see it coming into the queue - I guess it hit some of the -infra nodes which aren't yet updated17:24
*** persia has joined #openstack-ansible17:24
*** persia has quit IRC17:24
*** persia has joined #openstack-ansible17:24
*** britthou_ has joined #openstack-ansible17:27
*** britthouser has quit IRC17:30
odyssey4meit appears that zuul is having a little hernia17:32
svglet's cross our streams on him17:35
odyssey4mesvg eh?17:36
svgto kill him?17:36
odyssey4mesvg haha, no - one must be nice to zuul17:36
svgbut... busting makes me feel good!17:37
odyssey4mezuul schedules all the testing, so it's better to buy him large quantities of the water of life17:37
svgI never understood how picking the name of a bad guy for such a crucial process seemed like a good idea :)17:38
odyssey4mesvg nerd humour?17:38
svgeuhm17:39
svgAren't we talking about the Ghostbuster reference?17:39
odyssey4mesvg in my case http://status.openstack.org/zuul/ but in your case, yes17:39
svgWell, the point of the pun is that those are the same :)17:40
* odyssey4me pokes zuul with a pointed stick17:40
svgodyssey4me: are you always that serious?17:41
odyssey4mesvg very serious when I'm being held back from my scotch by a patch that I got merged :p17:42
* svg is zipping from his scotch with a view on a pool and a part of southern France17:42
* svg ducks17:43
* odyssey4me throws a pointed stick in svg's general direction17:43
*** yaya has quit IRC17:43
odyssey4mecrapola, over 4000 events in the queue :/17:44
*** Bjoern_ has left #openstack-ansible17:54
*** woodard has quit IRC17:55
*** phalmos has joined #openstack-ansible17:56
*** yaya has joined #openstack-ansible17:56
*** bapalm_ has joined #openstack-ansible18:15
*** bapalm has joined #openstack-ansible18:23
*** bapalm has quit IRC18:24
*** woodard has joined #openstack-ansible18:39
openstackgerritMarc Gariépy proposed stackforge/os-ansible-deployment: lxc.mounts udev conflict with lxc.autodev=1  https://review.openstack.org/21214218:45
openstackgerritChristopher H. Laco proposed stackforge/os-ansible-deployment: Templateize neutron_api_workers  https://review.openstack.org/21214618:52
*** Mudpuppy has quit IRC18:57
*** Mudpuppy has joined #openstack-ansible18:57
*** Mudpuppy has quit IRC18:57
*** Mudpuppy has joined #openstack-ansible18:58
*** javeriak_ has joined #openstack-ansible19:02
*** javeriak has quit IRC19:02
*** cristicalin has joined #openstack-ansible19:04
*** yaya has quit IRC19:06
*** cristicalin has quit IRC19:07
dstanekodyssey4me: yay, i looks like that one is rolling along now. i still don't know how the tox review got out of order ;-) probably not worth looking into19:15
odyssey4medstanek meh, it'll unblock soon and I'll sort the other branches out tomorrow19:16
*** jmckind_ has joined #openstack-ansible19:20
*** javeriak_ has quit IRC19:27
*** javeriak has joined #openstack-ansible19:40
*** woodard_ has joined #openstack-ansible19:48
*** woodard has quit IRC19:51
openstackgerritMerged stackforge/os-ansible-deployment: Adds ceilometer link in configure.rst  https://review.openstack.org/20757620:10
*** jmckind_ has quit IRC20:35
*** woodard_ has quit IRC20:39
*** woodard has joined #openstack-ansible20:40
*** jwagner is now known as jwagner_away20:40
*** galstrom is now known as galstrom_zzz20:43
*** jmckind has joined #openstack-ansible20:55
*** jmckind_ has joined #openstack-ansible21:11
*** jmckind has quit IRC21:12
*** tlian has quit IRC21:31
*** fawadkhaliq has joined #openstack-ansible21:43
*** jmckind_ has quit IRC21:44
*** fawadkhaliq has quit IRC21:50
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Implement /usr/bin/env as the shebang in all bash scripts  https://review.openstack.org/21188521:56
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Small readme fix  https://review.openstack.org/20770021:57
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated master for new dev work - Liberty-2  https://review.openstack.org/19912621:57
*** woodard has quit IRC22:01
*** woodard has joined #openstack-ansible22:01
openstackgerritMerged stackforge/os-ansible-deployment: Small readme fix  https://review.openstack.org/20770022:20
*** woodard has quit IRC22:24
*** KLevenstein has quit IRC22:35
*** marekd is now known as marekd_40422:36
*** spotz is now known as spotz_zzz22:39
*** devlaps has joined #openstack-ansible22:44
*** jmckind has joined #openstack-ansible22:45
*** Mudpuppy has quit IRC22:48
*** galstrom_zzz is now known as galstrom22:51
*** markvoelker has quit IRC23:14
*** phalmos has quit IRC23:37
*** galstrom is now known as galstrom_zzz23:45
*** alop has quit IRC23:53
openstackgerritMerged stackforge/os-ansible-deployment: Updated master for new dev work - Liberty-2  https://review.openstack.org/19912623:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!