| *** hashar has joined #openstack-sprint | 00:41 | |
| *** hashar has quit IRC | 01:55 | |
| *** hashar has joined #openstack-sprint | 05:14 | |
| *** hashar has quit IRC | 06:03 | |
| *** rfolco has joined #openstack-sprint | 10:54 | |
| *** asselin_ has joined #openstack-sprint | 15:08 | |
| *** hashar has joined #openstack-sprint | 15:12 | |
| *** omrim has joined #openstack-sprint | 15:14 | |
| *** mmedvede has joined #openstack-sprint | 15:16 | |
| *** ja has joined #openstack-sprint | 15:32 | |
| *** hashar has quit IRC | 15:39 | |
| *** hashar has joined #openstack-sprint | 15:40 | |
| krtaylor | #startmeeting third-party-ci-documentation | 16:02 |
|---|---|---|
| openstack | Meeting started Wed Jan 21 16:02:16 2015 UTC and is due to finish in 60 minutes. The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:02 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:02 |
| openstack | The meeting name has been set to 'third_party_ci_documentation' | 16:02 |
| krtaylor | hello everyone | 16:03 |
| krtaylor | this is the start of the third-party-ci-documentation virtual sprint | 16:03 |
| *** luqas has joined #openstack-sprint | 16:03 | |
| krtaylor | the goal is to rewrite/refresh the third-party ci documentation | 16:04 |
| krtaylor | here is the link to the etherpad for the sprint: | 16:04 |
| krtaylor | #link https://etherpad.openstack.org/p/third-party-ci-documentation | 16:04 |
| krtaylor | anyone here for the sprint? | 16:05 |
| mmedvede | I am lurking. Looking through docs | 16:07 |
| krtaylor | ok, so the first thing is, if you have not already, read third-party.rst | 16:09 |
| krtaylor | #link http://ci.openstack.org/third_party.html | 16:09 |
| krtaylor | and | 16:10 |
| krtaylor | #link http://ci.openstack.org/running-your-own.html | 16:10 |
| krtaylor | as you are reading through it, make note of the areas that need refreshing | 16:10 |
| krtaylor | there are many | 16:10 |
| krtaylor | add notes to that section in the etherpad, at a minimum | 16:11 |
| krtaylor | even better, put your nick on the etherpad next to a section and re-write it | 16:11 |
| krtaylor | I put myself next to the Overview and Requirements sections, but that does not mean that I won't take help there | 16:12 |
| krtaylor | but it would be better to have all the sections covered first | 16:13 |
| krtaylor | but, first, some housekeeping | 16:13 |
| krtaylor | just to remind everyone, the sprint will run for 48 hours | 16:14 |
| krtaylor | so we will be in this channel round-the-clock for the next 2 days | 16:14 |
| krtaylor | I will try to be here as much as I can over that timeframe | 16:14 |
| krtaylor | ok, I guess I didnt need to start a meeting, the channel is logged | 16:18 |
| krtaylor | #endmeeting | 16:18 |
| openstack | Meeting ended Wed Jan 21 16:18:44 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:18 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/third_party_ci_documentation/2015/third_party_ci_documentation.2015-01-21-16.02.html | 16:18 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/third_party_ci_documentation/2015/third_party_ci_documentation.2015-01-21-16.02.txt | 16:18 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/third_party_ci_documentation/2015/third_party_ci_documentation.2015-01-21-16.02.log.html | 16:18 |
| krtaylor | ok, omrim you said you could help on the other side of the world, keep things moving ? | 16:20 |
| krtaylor | omrim, thanks, I know it is late for you | 16:20 |
| krtaylor | we don't have anyone signed up for running-your-own.html | 16:21 |
| krtaylor | that is probably most out of date | 16:21 |
| krtaylor | the requirements section is rather lacking, it would be good to have some expectation on what will be needed there | 16:22 |
| *** luqas has quit IRC | 16:26 | |
| krtaylor | remember to set your patch topics to: third-party-ci-documentation | 16:26 |
| krtaylor | does anyone have any questions? on the etherpad? on our goal? | 16:28 |
| krtaylor | https://review.openstack.org/#/c/146968/ is pretty well reviewed, just needs another core to merge | 16:34 |
| krtaylor | mmedvede, is there an area that you want to focus on? | 16:35 |
| *** jhesketh has quit IRC | 16:37 | |
| mmedvede | krtaylor: not anything in particular. I can just get the next unassigned section (Event Stream) | 16:38 |
| *** jhesketh has joined #openstack-sprint | 16:39 | |
| krtaylor | mmedvede, great | 16:40 |
| *** hashar has quit IRC | 16:40 | |
| krtaylor | I did get permission from jaypipes to use anything from his blogs as input as needed | 16:40 |
| krtaylor | but we should give him co-author credit for sure | 16:41 |
| krtaylor | the links for those blogs are at the bottom of the etherpad | 16:41 |
| krtaylor | rfolco 's blog is there as well, with another perspective | 16:41 |
| krtaylor | rfolco, I assume we can use wording from that blog as needed, with co-author credit? | 16:42 |
| krtaylor | hm, wish I could set the channel topic... | 17:03 |
| *** mestery has joined #openstack-sprint | 17:03 | |
| krtaylor | I am reviewing the infra manual process for advice on the proper way to link to other docs in various places | 17:09 |
| krtaylor | anyone know off hand? | 17:09 |
| rfolco | krtaylor, yes you can grab info from the article | 17:11 |
| rfolco | krtaylor, Posting Result To Gerrit (rfolco) | 17:11 |
| rfolco | krtaylor, I need some education on the doc process but I assigned one workt item to myself | 17:11 |
| krtaylor | rfolco, great! | 17:12 |
| krtaylor | I am looking for any style references we may need | 17:12 |
| krtaylor | but I feel like we should just get the words in a patch, and folks that know can add comments | 17:13 |
| krtaylor | in other words, not worry about formatting as much as content | 17:14 |
| pleia2 | good morning | 17:15 |
| krtaylor | but for links `Words to describe link <http link>`_. is the format | 17:15 |
| krtaylor | pleia2, hi! welcome! | 17:15 |
| pleia2 | krtaylor: have a moment for a quick PM? | 17:16 |
| krtaylor | pleia2, sure | 17:16 |
| krtaylor | pleia2, thanks for the tweet! | 17:26 |
| pleia2 | sure thing :) | 17:26 |
| pleia2 | should do another now actually | 17:26 |
| krtaylor | we need everyone to spread the word, this was so last minute | 17:27 |
| krtaylor | I'd really like to make sure these doc changes link into existing docs as much as possible | 17:28 |
| *** mestery has quit IRC | 17:28 | |
| krtaylor | we need to move forward with this thinking about how we can make it easier to maintain | 17:28 |
| *** mestery has joined #openstack-sprint | 17:28 | |
| pleia2 | I'll also mention that there is some work happening to create a puppet module for all of this, but I think these docs will be valuable in creating said puppet module, and even once we have that it won't always be perfect for everyone | 17:29 |
| pleia2 | so I'm sure these docs will actively evolve once that comes into play | 17:29 |
| pleia2 | but that's how things go :) | 17:30 |
| krtaylor | pleia2, yes, we discussed that in the third-party meeting | 17:30 |
| krtaylor | asselin_, agreed that after in-tree, we'd update docs | 17:31 |
| krtaylor | here is a link to that spec, btw: https://review.openstack.org/#/c/139745/ | 17:31 |
| pleia2 | thanks | 17:31 |
| krtaylor | it is shaping up very nicely | 17:32 |
| krtaylor | so, I was looking at the 2 documents we have for third-party testing | 17:33 |
| krtaylor | the first third_party.rst is basically what a system needs to do to interact with infra services | 17:33 |
| krtaylor | the second, running-your-own, is how to grab, modify and run | 17:34 |
| krtaylor | we have FAQ in the first, but the question there really belongs in the second | 17:35 |
| krtaylor | so, 2 FAQs? | 17:35 |
| krtaylor | or, and maybe this is too big, why do we have 2 documents anyway? makes it more manageable? or is it just because thats how it was done initially? | 17:36 |
| krtaylor | anyone know? | 17:36 |
| pleia2 | I think I'd forget which faq to reference if there were 2 | 17:40 |
| pleia2 | the first document was created by someone who was doing a presentation on running your own and didn't know until after he committed to it that it wasn't well documented :) | 17:41 |
| pleia2 | so in the course of talk prep, he documented | 17:41 |
| krtaylor | cool, good to know, I know we had to feel our way through the dark :) | 17:42 |
| krtaylor | yeah, 2 FAQs don't make sense | 17:42 |
| krtaylor | what if we pulled the docs together? | 17:42 |
| pleia2 | so running-your-own is kind of CI-focused document, since our project is "an open source infrastructure" and we want folks to be able to use it when they bring up their system in their organization that has nothing to do with openstack | 17:45 |
| pleia2 | my vision here would be that running-your-own would finally be maintained, and third-party would reference it as needed, adding in bits of information that are 3rd party specific | 17:46 |
| krtaylor | hm, good point, it would make it more broadly consumable to keep is separate | 17:47 |
| krtaylor | and we can always merge later if someone feels so inclined | 17:48 |
| pleia2 | yeah | 17:49 |
| krtaylor | need to grab some lunch, brb | 17:52 |
| *** mestery has quit IRC | 18:37 | |
| krtaylor | mmedvede, any work needed to event stream section? | 18:54 |
| mmedvede | krtaylor: not sure. Looks good superficially, was going to test the commands that are there | 19:00 |
| asselin_ | hi, sorry very very busy morning, and my ci system went down.... | 19:13 |
| asselin_ | (still down) | 19:13 |
| pleia2 | asselin_: ouch :\ | 19:15 |
| asselin_ | so I'd like to start migrating japipes blogs over. any comments and where that should go? | 19:17 |
| pleia2 | I think the main work there is merging his posts with an update to http://ci.openstack.org/running-your-own.html | 19:21 |
| pleia2 | since there is a lot of overlap, and we do want to keep running-your-own.html as a more general CI configuration document (unrelated to openstack, to anyone who wants to run the CI) | 19:22 |
| krtaylor | asselin_, no worries, I have a couple of meetings atm | 19:27 |
| krtaylor | but I agree with pleia2 | 19:27 |
| krtaylor | asselin_, I think running-your-own needs a lot of attention, and no one is looking at it (yet) | 19:28 |
| * asselin_ looking at running your own | 19:28 | |
| pleia2 | added the third-party-ci-documentation patch topic note to the etherpad, and link we can use for reviewing patches, once they start coming in https://review.openstack.org/#/q/topic:third-party-ci-documentation,n,z | 19:36 |
| asselin_ | I think http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/ should be a pre-read to Running your own | 19:40 |
| pleia2 | that makes sense, it does duplicate some of the other docs we have too so maybe not a drop in replacement, but I'm happy to help identify spots that we don't need to duplicate | 19:48 |
| asselin_ | pleia2, honestly, the information seems more part of Third Party Testing. A bit more background for those who don't know what it is or why have it | 19:55 |
| asselin_ | perhaps a "background" section? | 19:56 |
| asselin_ | or not. I'm down to the section of "Continuous Integration Testing" Everything before should be in other docs | 20:01 |
| pleia2 | asselin_: so there are things like talking about zuul's layout.conf where I think we can write a quick note about it, and then link to the CI docs for learning more, right now the blog post is out of date because /config repo no longer exists and the layout.yaml is in a completely different place, not having to maintain this on the third party side too would be nice | 20:01 |
| pleia2 | not that I think it will change soon, but layout examples also change and cause confusion | 20:03 |
| asselin_ | noted | 20:03 |
| asselin_ | I like the idea of basic snips + link for more info | 20:04 |
| pleia2 | great | 20:04 |
| *** rfolco has quit IRC | 20:06 | |
| asselin_ | pleia2, krtaylor https://review.openstack.org/149032 Take a look at the structure. I'll update the content after grabbing some lunch. | 20:20 |
| pleia2 | asselin_: want us to comment now, or hold off until you have some changes in? | 20:20 |
| ja | it sounds like he's after comments on structure (now) while he's at lunch. presumably he'll respond/iterate when done eating. | 20:27 |
| pleia2 | yeah, that's what I'll go with :) | 20:27 |
| * krtaylor reading | 20:30 | |
| krtaylor | btw, all of jaypipes blogs are linked at the bottom of the etherpad, as well as any other infromation sources that we use | 20:30 |
| krtaylor | and information sources | 20:30 |
| ja | krtaylor, meta-comments starting to spew out of my brain. here? etherpad? | 20:34 |
| krtaylor | ja, etherpad please, todo section or comments section, or however you want | 20:36 |
| krtaylor | wow comments from jaypipes 7 minutes from pushing the patchset! very nice asselin_ | 20:42 |
| krtaylor | :) | 20:42 |
| pleia2 | I'm really happy to see he's involved in the process | 20:44 |
| krtaylor | very | 20:45 |
| *** mestery has joined #openstack-sprint | 20:47 | |
| pleia2 | did anyone invite him over here? :) | 20:48 |
| krtaylor | 2x via email, and discussions about using his content, but not today :) | 20:58 |
| pleia2 | just sent him a msg in case he forgot :) | 21:01 |
| *** jaypipes has joined #openstack-sprint | 21:01 | |
| pleia2 | jaypipes: welcome to the party! | 21:02 |
| krtaylor | hi jaypipes, thanks for joining! | 21:02 |
| jaypipes | heya :) | 21:02 |
| krtaylor | thanks for the crazy fast comments on asselin_ patchset | 21:03 |
| jaypipes | no worries. will try to do reviews on anything you ping me about. | 21:04 |
| jaypipes | in between meetings and more meetings ;) | 21:04 |
| krtaylor | jaypipes, perfect, thanks | 21:04 |
| asselin_ | I'm back | 21:04 |
| krtaylor | ja, I am interested in your comment on a structural picture | 21:05 |
| krtaylor | ja, like - here are the components and how they hook together? | 21:05 |
| asselin_ | wow, got more than I expected :) | 21:05 |
| ja | yes, like rfolco's | 21:05 |
| asselin_ | I just go have lunch more often :) | 21:06 |
| krtaylor | ja, I have one I have done for presentations that is more general | 21:06 |
| ja | ...his blog entry has a good starting point, although I would be careful to add in the firewall since that really affects planning | 21:06 |
| krtaylor | rfolco's is pretty specific to our environment, if it is the one I am thinking of | 21:06 |
| krtaylor | yeah, that is what I was thinking for the run-your-own requirements section | 21:07 |
| krtaylor | there isnt much discussion on how much hardware youll need, firewall considerations, options for hosting logs, etc | 21:07 |
| ja | krtaylor, I could posit several actually. 1=the actual openstack one, as infra "ships" it. 2=a generic third party. 3+= specific third party examples (probably as hyperlinks) | 21:07 |
| krtaylor | yes, I think picture would really help some basic understanding of the layout of things and how they work together, it has really helped internally anyway | 21:09 |
| ja | ... 1 is the base a 3P is "copying". 2 is the logical model (some of the specifics removed, so it's down to roles & responsibilities). need at least one 3 somewhere so people have 2 diff examples (1 and 3) of applying 2 to a specific case. | 21:09 |
| ja | krtaylor, the pic on 2 would also be careful to point out places where the implementation would vary (i.e. where that's the expected state). there might also be specific cases noted where "most 3Ps do X, but you can do otherwise" eg run zuul on x86 vs something else. | 21:18 |
| ja | ... and it's another "good pub writing" practice, that whereever you give readers an option you give/point to the criteria they'd use to decide. | 21:18 |
| krtaylor | ja, good point | 21:19 |
| krtaylor | I'll look at the doc sdague did for gerrit and see how it is linked in the doc | 21:20 |
| krtaylor | ok fairly straightforward, I'll take that task | 21:25 |
| ja | krtaylor, I think I'm done etherpadding for today. I'll probably fuss with getting git-review and friends config'd tomw AM; already installed git and git-review, so if anything else I should be doing to prep feel free to shoot email with particulars at me. | 21:43 |
| *** ja has quit IRC | 21:48 | |
| *** jaypipes has quit IRC | 22:37 | |
| krtaylor | will be back on later, have to do some schools stuff for my son | 22:40 |
| asselin_ | https://review.openstack.org/#/c/149032/ updated | 22:58 |
| *** patrickeast has joined #openstack-sprint | 23:08 | |
| pleia2 | asselin_: reviewing | 23:25 |
| *** mestery has quit IRC | 23:27 | |
| jhesketh | Hey guys | 23:33 |
| jhesketh | how can I help :-) | 23:33 |
| *** mestery has joined #openstack-sprint | 23:34 | |
| pleia2 | o/ jhesketh | 23:34 |
| pleia2 | jhesketh: not many patches in flight, but what we have is here: https://review.openstack.org/#/q/topic:third-party-ci-documentation,n,z | 23:35 |
| jhesketh | cool, I'll review | 23:35 |
| asselin_ | what do you think. Should this be used? http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/#Jenkins_Job_Creation_and_Configuration Or is there a better place that explains JJB? | 23:35 |
| asselin_ | I found this: http://ci.openstack.org/jenkins-job-builder/definition.html | 23:35 |
| pleia2 | yeah, there's also http://ci.openstack.org/jjb.html | 23:36 |
| pleia2 | both have examples already | 23:36 |
| pleia2 | leveraging one or both would be my preference | 23:36 |
| asselin_ | I like http://ci.openstack.org/jjb.html#yaml-format | 23:38 |
| pleia2 | yeah | 23:38 |
| *** gothicmindfood has quit IRC | 23:42 | |
| pleia2 | woo, one patch down! thanks jhesketh | 23:47 |
| jhesketh | :-) | 23:47 |
| asselin_ | great! I'll rebase on that now. :) | 23:48 |
| asselin_ | well before my next patch set | 23:48 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!