19:04:18 <mtaylor> #startmeeting
19:04:19 <openstack> Meeting started Tue Jul 24 19:04:18 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:04:29 <mtaylor> bwahahaha. I haz taken over!
19:04:36 <Daisy> :)
19:04:37 <Daisy> Hello !
19:04:47 <mtaylor> hi there.
19:04:48 <clarkb> hello
19:04:54 <mtaylor> anybody else want to talk about, you know, things?
19:05:19 <Daisy> any agenda ?
19:05:20 <annegentle> stuff and things!
19:05:46 <mtaylor> we normally start through just with some updates from folks on anything they've done, then open up the floor for things
19:05:56 <Daisy> ok
19:05:57 <mtaylor> so... clarkb - what's been up in your world?
19:06:12 <clarkb> I get to go first whee!
19:06:33 <clarkb> I am trying to think about what happened week before last because OSCON
19:07:03 <clarkb> gerritlib is now its own project with tests and stuff as well as all the packaging foo
19:07:21 <jeblair> clarkb: is that ready for a release no that gerritbot can consume it?
19:07:28 <jeblair> s/no that/so that/
19:07:42 <clarkb> jeblair: I think so, unless we want to PBR it first
19:07:57 <mtaylor> nope. pbr is killing me at the moment
19:07:57 <clarkb> but functionally PBR isnt necessary
19:08:15 <jeblair> okay, i'll see about cutting a release then.
19:08:21 <clarkb> sounds good.
19:08:22 <mtaylor> clarkb: if it has the right jobs and stuff, you should be able to cut a release by tagging it
19:08:34 <jeblair> mtaylor: i think i need to register it first...?
19:08:50 <mtaylor> yup
19:09:23 <clarkb> oh yes, that was the big thing I was forgetting. Zuul is now a little smarter. If a job not at the front of the queue has a failure all of the jobs behind it are cancelled to free resources
19:09:35 <mtaylor> register it and then go to the project page and add openstackci as a maintainer
19:09:41 <clarkb> (they will be rerun again anyways so there is little sense in burning up CPU cycles running them multiple times)
19:09:50 <jeblair> mtaylor: (i'll do that)
19:10:00 <mtaylor> clarkb: awesome! I think that will be quite handy
19:10:20 <clarkb> so far it appears to have been working. I haven't seen any really long job queues since that patch went in
19:10:25 <jeblair> clarkb: indeed, it's already made a difference.
19:11:02 <clarkb> jeblair fixed a bug in Zuul to make this possible
19:11:39 <mtaylor> jeblair: sounds like the baton is being passed there
19:12:07 <clarkb> other than that I added asciidoc building dependencies to build slaves, just merged in the bits that should make selenium testing possible, and I can't think of anything else at them moment
19:12:41 <jeblair> mtaylor: zuul has three contributors now!
19:13:48 <mtaylor> jeblair: w00t!
19:14:03 <mtaylor> jeblair: watch out- you're going to eclipse openstack itself
19:14:18 <jeblair> mtaylor: don't get me started on eclipse.
19:14:29 <mtaylor> jeblair: you wanna use netbeans instead?
19:15:09 <jeblair> mtaylor: who has the floor? :)
19:15:50 <mtaylor> jeblair: you do
19:16:32 <jeblair> so, in addition to working with clarkb on some of the zuul stuff he already mentioned, i also make a few more changes to zuul:
19:16:50 <jeblair> suppression of duplicate events (so we don't test something twice if it's approved twice)
19:17:17 <jeblair> and the option to delay testing of changes until at least the -merge job of the change ahead has passed
19:17:23 <mtaylor> ++
19:17:27 <Daisy> hi
19:17:47 <jeblair> i'm currently working on getting zuul to change tests in a better order
19:18:00 <mtaylor> the change to gerrit for that seemed to be reasonably painless
19:18:05 <jeblair> specifically, to recognize dependencies between changes, and to merge-gate them in the correct order.
19:18:17 <jeblair> (and not merge-gate them until they can actually be merged)
19:18:24 <Daisy> I'm working on the document translation process. I come here to see if somebody can help me to integrate the translation process in CI.
19:18:49 <Daisy> I got some chance to read CI documents. I still have some questions.
19:19:12 <Daisy> The Puppet Modules "Doc Server" is not existed. Is it still being used ?
19:19:15 <jeblair> the change to gerrit is to facilitate zuul understanding when a change is ready to be merged (does it have the needed approvals)
19:19:47 <jeblair> Daisy: we'd love to talk about that! can you wait a few more minutes?
19:19:56 <mtaylor> jeblair: yeah, that seemed like a generally good (and thankfully small patch)
19:20:27 <jeblair> i'll start working on upstreaming it once we have a little experience with it.
19:20:40 <Daisy> jblair: sure
19:20:41 <jeblair> there are three core projects that are still not participating in the devstack gate
19:20:42 <mtaylor> agree. you put that on review-dev just now, yeah?
19:20:57 <mtaylor> jeblair: swift and what else?
19:20:59 <jeblair> mtaylor: hasn't merged yet, but i'll do it after the meeting
19:21:03 <jeblair> swift, cinder, and quantum
19:21:39 <jeblair> quantum has been outstanding since mid-april; supposedly if this change merges, the exercises should pass: https://review.openstack.org/#/c/8642/
19:21:57 <mtaylor> ah yes
19:22:05 <jeblair> cinder is being actively worked on by jaypipes and jgriffith
19:22:16 <jeblair> it passes exercises now, but has a problem with a tempest smoke test
19:22:32 <jeblair> and the last time i ran the swift check, it passed
19:22:35 <mtaylor> fancy!
19:22:41 <jeblair> notmyname: you around?
19:22:45 <notmyname> yup
19:22:58 <jeblair> what do you think about turning on devstack-gate for swift?
19:23:39 <notmyname> anything changed since we last talked about it?
19:23:49 <notmyname> failure modes, etc
19:24:28 <notmyname> is it currently running in a non-gating fashion now?
19:24:30 <jeblair> nope.  devstack has been fixed so that it doesn't try to use swift3 when swift is enabled, so the gate-test passes now (or did last time i ran it)
19:24:36 <notmyname> good
19:25:00 <jeblair> it's not running regularly with swift, only when this change is tested: https://review.openstack.org/#/c/8809/
19:25:52 <notmyname> I'd like to either wait a week before gating, but I'm ok with adding it in a non-gating manner now. we've got a release next monday, and I'd hate to add stuff that slows down that process right before the release
19:26:09 <notmyname> * either wait a week, or add it now in a non-gating manner
19:26:41 <jeblair> that works for me.  we can aim to add it after the release next week.
19:26:44 <notmyname> actually, is it possible to add it as a non-gating test before gating on it?
19:28:29 <jeblair> notmyname: it's possible, but quite a bit of effort for not much reward.  (it would require a separate job and consume twice the test resources)
19:29:23 <jeblair> triggering rechecks of https://review.openstack.org/#/c/8809/ will let us spot check that everything's still working, and of course, that change itself won't merge unless everything is working.
19:32:02 <mtaylor> any more on swift gating?
19:32:29 <mtaylor> from my end, I'm happy to report that we've moved all of our main servers over to puppetmaster now
19:32:30 <mtaylor> yay
19:32:50 <jeblair> mtaylor: the new layout looks lovely
19:33:18 <clarkb> grep helps when looking for things :)
19:33:43 <mtaylor> that's what happens when you run in to the puppet people at oscon
19:33:57 <mtaylor> so thanks bodepd
19:34:13 <mtaylor> I've also got the first pass at puppet-dashboard installed
19:34:25 <mtaylor> but it's having issues when it's run via apache
19:34:36 <mtaylor> so it seems there might be ruby debugging in my future
19:34:48 <notmyname> sorry, got called away for a customer issue. jeblair: mtaylor: let's enable it next week after the release
19:35:19 <jeblair> notmyname: sounds good
19:35:27 <mtaylor> ++
19:35:41 <mtaylor> I think that's all I've got on my end
19:35:48 <mtaylor> #topic documentation translations
19:35:54 <mtaylor> Daisy: howdy
19:35:56 <mtaylor> annegentle: you around?
19:36:08 <Daisy> hi
19:37:02 <annegentle> ye
19:37:04 <annegentle> yes, even
19:37:19 <Daisy_> Hi, I'm back
19:37:28 <mtaylor> Daisy_: awesome. we're all yours
19:37:37 <Daisy_> :)
19:37:53 <Daisy_> first of all, I have some questions after reading CI documents.
19:38:15 <Daisy_> The Puppet Modules "Doc Server" is not existed. Is this still used ?
19:39:15 <Daisy_> And, I cannot find openstack-manuals job definition in YAML scripts.
19:39:37 <mtaylor> openstack-manuals I believe is still manually done in jenkins, yeah?
19:39:42 <jeblair> i think so
19:39:48 <mtaylor> and also, the Doc Server moduel is not used and is gone
19:39:54 <Daisy_> oh.
19:39:56 <jeblair> we need to convert that to job filler -- we should be able to now that we have shell scripts
19:40:01 <mtaylor> jeblair: ++
19:40:06 <Daisy_> manually defined some jobs ?
19:40:06 <jeblair> and maven support
19:40:58 <mtaylor> Daisy_: yeah - the old way we used to make jobs in jenkins was just through the web ui
19:41:05 <Daisy_> ok. I see.
19:41:13 <mtaylor> it's not scalable, so we've been replacing it - but we havne't fully converted everything yet
19:41:14 <Daisy_> I see the job definitions through web UI.
19:41:26 <Daisy_> ok. thanks.
19:41:36 <Daisy_> Let me describe my requirements.
19:42:08 <Daisy_> Can I have a job run regularly, like, once per 12 hours in Jenkins?
19:42:38 <Daisy_> What language can be used to describe such job ? python script or YAML ?
19:43:12 <jeblair> Daisy_: yes, you can run a job on a schedule
19:43:37 <jeblair> Daisy_: (but we like to have jobs run in response to events as much as possible -- anything that happens in gerrit can generate an event that triggers a jenkins job)
19:44:10 <jeblair> Daisy_: and if you want to hook a job up to an outside event source -- like a translation service -- if it has events or hooks, we can look at triggering jobs from that too.
19:44:30 <jeblair> Daisy_: but otherwise, a schedule is easy to do.
19:44:31 <mtaylor> Daisy_: ++
19:44:54 <mtaylor> yeah - is the job wanting to grab translatoins from somewhere and publish them?
19:45:04 <jeblair> Daisy_: as for how to describe a job...
19:45:31 <Daisy_> Now we are using Transifex to host the translation. The DocBooks are sliced into pieces. I found it was not convenient to see the whole translated documents under such situation. I'm looking for a way to show the latest translation result.
19:45:55 <Daisy_> Even the translation is not completed, we can see a document with mixed languages, some parts are translated, some parts are still in Englisn.
19:46:06 <jeblair> Daisy_: the jenkins job_filler yaml files are the way we'd like to define the jobs in jenkins -- if the jobs are more than one or two lines of shell script, you should write a script (python or shell, whatever you need), and then call that from the jenkins job you specify with yaml.
19:46:09 <mtaylor> Daisy_: do you have a link to the transifex project?
19:46:15 <Daisy_> I have.
19:46:34 <Daisy_> https://www.transifex.net/projects/p/openstack-manuals-i18n/
19:48:21 <mtaylor> cool. so, in general it seems like we need to figure out how to get data back out of transifex
19:48:33 <mtaylor> is transifex watching the trunk git repos?
19:48:36 <Daisy_> And, what's more, after document transaltion, there will be documents in different languages. How to show these in website? I have no idea.
19:49:27 <mtaylor> now that's a question for annegentle
19:49:45 <Daisy_> Transifex uses its client to push the resources to transifex website and pull the translation back to local file disk.
19:50:07 <annegentle> Daisy_: I believe the openstack-manuals github repo's www folder will have to have new index.html that enables display of the translated documents
19:50:25 <annegentle> better yet, we'd have a CMS front end that could handle this, but for now it's hand-written HTML linking
19:50:51 * annegentle wonders how publican handles?
19:51:28 <mtaylor> well lookie there
19:51:29 <mtaylor> http://pypi.python.org/pypi/transifex-client/
19:52:37 <clarkb> so we would probably want a python script that pulls translations from transifex and submits them to gerrit?
19:53:05 <Daisy_> maybe. I remember the transifex client is also writen in python.
19:53:46 <Daisy_> http://help.transifex.com/features/client/index.html#user-client
19:53:50 <jeblair> yeah, there's a similar job that pulled translations from launchpad we can base it on
19:54:01 <mtaylor> how are the new things being update right now
19:54:06 <mtaylor> as in, who owns that?
19:54:06 <jeblair> basically, git checkout, pull translations, commit and git-review
19:54:30 <Daisy_> what is git checkout ?
19:54:38 <mtaylor> Daisy_: it looks like you are the owner of https://www.transifex.com/projects/p/openstack-manuals-i18n/
19:54:47 <Daisy_> Yes, I created it.
19:55:07 <mtaylor> Daisy_: how do you update the source strings to be translated when new changes are made in git
19:55:14 <mtaylor> do you personally run the tx command?
19:56:12 <Daisy_> msg mtaylor Yes for now.
19:56:21 <mtaylor> ok. so, steps moving foward are going to be:
19:56:33 <mtaylor> a) getting a transifex account made for jenkins
19:56:53 <mtaylor> b) getting that jenkins account added to the openstack-manuals-i18n project
19:56:59 <annegentle> sorry all, have to run to a meeting, but I will read the logs
19:57:16 <mtaylor> c) getting a jenkins job that pushes new base changes to transifex
19:57:31 <mtaylor> d) getting a jenkins job that pulls new translations from transifex and submits them to gerrit
19:57:56 <Daisy_> correct !
19:58:01 <jeblair> i'll take (a)
19:58:05 <mtaylor> actually - heckj and GabrielHurley run the openstack uhub
19:58:06 <mtaylor> hub
19:58:31 <mtaylor> so what we _really _ want is to get the openstackci user added to that hub
19:58:31 <clarkb> we should probably add this project to the hub if possible
19:58:33 <Daisy_> ok. I will request again.
19:58:38 <mtaylor> and the manuals project added to that hub
19:58:45 <mtaylor> and we need to get the CI team added as admins of that hub
19:58:52 <Daisy_> who can add that project to hub ?
19:58:58 <mtaylor> I'll take on tracking down heckj and gabriel
19:59:09 <Daisy_> thank you, mtaylor !
19:59:27 <mtaylor> Daisy_: I think we'll be doing good if we can just get account permissions sorted this week
19:59:31 <jeblair> Daisy_: can you join us in #openstack-infra ?
19:59:43 <Daisy_> when is #openstack-infra?
19:59:43 <mtaylor> let's check back in next week and ensure that we've got that done and can start making jobs
19:59:46 <Daisy_> I'd like to join.
19:59:48 <jeblair> Daisy_: we can continue to talk about this in that channel
20:00:01 <Daisy_> so the next meeting is #openstack-infra?
20:00:01 <jeblair> Daisy_: we're in that channel all the time
20:00:30 <Daisy_> great to know that ! a day meeting in Tuesday !
20:00:33 <jeblair> Daisy_: no, most of the infrastructure/ci people are in that channel all the time and available to talk about this sort of thing
20:00:50 <Daisy_> ok, thanks.
20:01:46 <mtaylor> cool. I think that's good for this week. thanks everybody!
20:01:49 <mtaylor> #endmeeting