Monday, 2018-10-08

tristanCpabelanger: have you seen https://review.openstack.org/#/c/532084 ?00:38
*** rlandy has quit IRC00:58
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: WIP: Test using install-kubernetes role  https://review.openstack.org/60580301:00
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: WIP: Test using install-kubernetes role  https://review.openstack.org/60580301:08
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: WIP: Test using install-kubernetes role  https://review.openstack.org/60580301:14
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: WIP: Test using install-kubernetes role  https://review.openstack.org/60580301:27
*** jiapei has joined #zuul01:39
tristanCShrews: here, nodepool created 2 nodes on minikube, one namespace and one pod: http://logs.openstack.org/03/605803/15/check/nodepool-functional-k8s/9b8cbed/ubuntu-xenial/nodepool/launcher.log01:42
*** Shrews has quit IRC02:32
pabelangertristanC: no, didn't see that one. Quick look, it is a little difference. Opted to just use the zuul-executor, since we got ansible-galaxy for free. playbook: https://github.com/ansible-network/zuul-config/blob/master/playbooks/publish/galaxy.yaml job: https://github.com/ansible-network/zuul-config/blob/master/zuul.d/jobs.yaml#L7002:32
*** Shrews has joined #zuul02:32
pabelangertristanC: however, i didn't consider using zuul.tag for --branch, will need to confirm with team that will work02:32
pabelangerif so, happy to switch to that also02:32
pabelangertristanC: https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/logs/8c/8c62c1f69a17ba41f1d1bf81485dff20f1ab69ff/post/release-ansible-role/c210f12/job-output.html is example job from zuul-executor02:36
pabelangerwill catch up in the morning, EOD02:37
*** rcarrillocruz has quit IRC02:51
tristanCpabelanger: why couldn't you use 532084 on the executor?03:02
*** rcarrillocruz has joined #zuul04:16
*** nilashishc has joined #zuul04:20
*** rcarrillocruz has quit IRC04:21
*** rcarrillocruz has joined #zuul04:25
*** nilashishc has quit IRC04:29
*** nilashishc has joined #zuul04:34
*** quiquell|off is now known as quiquell05:46
*** snapiri has quit IRC06:12
*** swest has quit IRC06:13
*** swest has joined #zuul06:15
*** klep has quit IRC06:24
*** quiquell is now known as quiquell|brb06:37
*** quiquell|brb is now known as quiquell07:09
*** electrofelix has joined #zuul07:20
*** goern has joined #zuul07:29
*** nilashishc has quit IRC07:34
*** nilashishc has joined #zuul07:36
*** chandankumar has joined #zuul07:40
*** jpena|off is now known as jpena07:44
*** snapiri has joined #zuul08:19
*** chandankumar has quit IRC08:51
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add install and deploy openshift roles.  https://review.openstack.org/60861008:52
*** sshnaidm is now known as sshnaidm|lnch09:40
*** bhavikdbavishi has joined #zuul09:47
*** bhavikdbavishi has quit IRC09:52
*** sshnaidm|lnch is now known as sshnaidm09:59
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066710:06
*** jpena is now known as jpena|off10:07
*** nilashishc has quit IRC10:14
*** nilashishc has joined #zuul10:15
*** quiquell is now known as quiquell|brb10:20
*** quiquell|brb is now known as quiquell10:21
*** ssbarnea_ has quit IRC10:24
*** quiquell is now known as quiquell|brb10:53
*** rlandy has joined #zuul12:04
*** quiquell|brb is now known as quiquell12:20
*** samccann has joined #zuul12:46
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add install and deploy openshift roles.  https://review.openstack.org/60861012:52
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066713:05
ShrewstristanC: cool!13:10
tristanCShrews: 570667 should get a similar result with openshift13:13
Shrewsi'm not certain that a role is going to end up being the best way to test a new driver in the long run, but at least it's something13:13
Shrewsi wasn't thinking something along the lines of a new tox environment (e.g, tox -ek8s) so we can do deep testing like we do with the openstack driver, but i haven't given much thought as to what that would require13:15
tristanCShrews: i don't mind either way, though i still think we should test zuul, zuul-jobs and zuul-base-jobs too for completeness13:17
Shrewss/wasn't thinking/was thinking/13:17
ShrewstristanC: oh yeah, totally13:17
Shrewsi'll remove the WIP comment from 605823 since that seems to work13:20
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul-jobs master: Add role to install kubernetes  https://review.openstack.org/60582313:21
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Ignore removed provider in _cleanupLeakedInstances  https://review.openstack.org/60867013:22
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add install and deploy openshift roles.  https://review.openstack.org/60861013:56
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066713:56
Shrewscorvus: mordred: how would you feel about removing the tox-cover job from nodepool? AFAIA, none of us ever really check the output, so it seems wasteful14:37
corvusShrews: wfm14:37
corvuseasy to add back if/when we care14:38
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Remove tox-cover job  https://review.openstack.org/60868814:38
clarkbfwiw I added the job back when nodepool was flaky and the coverage was useful to understand what was undertested. less of a problem today14:39
tobiashShrews: I looked at it sometimes (but also can just run that locally)14:41
corvuswe can also add it to 'experimental'14:41
tobiashI'm fine with removing it14:41
tobiashjust wanted to mention that it's not completely useless :)14:42
*** quiquell is now known as quiquell|off14:44
pabelanger+1 for experimental14:44
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: WIP: Second try to fix single cloud config reload  https://review.openstack.org/60869514:59
tobiashcorvus, Shrews: this would be another approach to fix the single cloud reconfiguration use case ^15:00
tobiashthis further doesn't rely on the taskmanager's stoppedexception15:00
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add tox-py36 job  https://review.openstack.org/60870015:14
*** nilashishc has quit IRC15:20
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add tox-py36 job  https://review.openstack.org/60870015:21
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066715:21
*** panda is now known as panda|off15:23
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Create ansible-galaxy-import role  https://review.openstack.org/60847215:34
corvuspabelanger: should we just start working on support for maser instead?  or do you have immediate use for current galaxy?15:36
pabelangercorvus: yah, imeediate use for current galaxy, ansible-network team releases every 2 weeks. I am also working on mazer role, but think it only works today against galaxy-qa server.15:37
pabelangerimmediate*15:37
pabelangercorvus: I also don't mind running that role downstream until mazer is live15:38
corvuspabelanger: i think that role is fine, was just curious15:38
corvuspabelanger: i was thinking in zuul itself we could probably skip supporting galaxy and only support mazer (for having zuul install roles for running a job)15:39
corvus(but again, a role for current galaxy in zuul-jobs seems like a good idea)15:39
pabelangerYah, I think both ideas are fine15:40
pabelangeras I under stand, once mazer is live, galaxy import will no longer work15:41
corvusi'm going to go into a corner and work on https://review.openstack.org/608344 for a bit15:46
Shrewsnobody puts corvus in a corner15:47
* Shrews apologizes for 80's movies reference15:48
*** sshnaidm is now known as sshnaidm|afk15:51
*** ssbarnea|bkp2 has joined #zuul15:54
openstackgerritMerged openstack-infra/nodepool master: Remove tox-cover job  https://review.openstack.org/60868816:07
*** panda|off has quit IRC16:22
*** panda has joined #zuul16:23
clarkbI've approved the additon of a test workspace setup role to zuul jobs so I can test a change to the actual role for that in base-test16:46
clarkbwill approve the base test update once that goes in16:47
*** sshnaidm|afk is now known as sshnaidm16:48
openstackgerritMerged openstack-infra/zuul-jobs master: Add test workspace setup role  https://review.openstack.org/60834217:03
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: docker-compose quickstart example  https://review.openstack.org/60834417:22
corvus\o/ i just ran a job on that ^17:22
corvusi think i've got the sequencing worked out, so 'docker-compose up' will bring everything up.  i worked around the ssh host key issue for now too, so we don't have to wait on that.17:23
corvusnext up is log publication, then writing some more words about setting up jobs :)17:24
Shrewscorvus: i left a few minor comments on the previous PS for that17:24
Shrewsi'm curious how it worked, given my comments17:25
corvusShrews: oh cool i'll take a look17:28
Shrewsif the only difference in the containers is the default command, perhaps we should reconsider how pbrx works17:28
*** ssbarnea_ has joined #zuul17:29
*** ssbarnea|bkp2 has quit IRC17:30
corvusShrews: ah yes!  zuul daemonizes by default, and that's not ideal in containers, so we override to use "-d".  the only difference in the containers is the command, so since we're not using that anyway, i just used zuul/zuul.  i think the best solution to this is to change the default behavior of zuul and nodepool to run in the foreground by default, and switch '-d' to mean daemonize.  when we do that, we can17:32
corvusswitch to using the different pbrx images.17:32
*** sshnaidm is now known as sshnaidm|afk17:32
corvus(also some systemd folks may prefer zuul to run in the foreground)17:33
corvusand finally, we should separate the daemonization flag from the debug log flag.17:34
Shrewscorvus: If that's the plan (which I like), then perhaps we should start off the document using the containers we intend to use (to prevent confusing new users)17:34
Shrewsor maybe they won't even bother looking at the docker compose file, in which case, it's irrelevant17:35
corvusShrews: good point.  i'll switch them.  in case they do look.  :)17:35
corvus(early on, it was helpful for me to have a shorter docker image list, but i'm past that now)17:35
openstackgerritClark Boylan proposed openstack-infra/zuul-jobs master: Do no merge testing with base-test  https://review.openstack.org/60873217:36
corvusdoes anyone happen to know if mordred's change to fix the javascript in the container merged and if we published a new container image with that?17:50
clarkbcorvus: https://review.openstack.org/#/c/608411/ seems to have merged which should have ended up in a new docker image17:52
clarkbunsure if that needs a release though https://review.openstack.org/#/c/607638/1/.zuul.yaml17:52
corvusclarkb: looks like openstackzuul-pbrx-push-container-images is the job and runs in post17:55
corvusso yeah, it should be there.  but i'm still getting 404s17:59
corvusif anyone feels like poking at that, that's a good parallel task that will help with the quickstart18:03
Shrewscorvus: you get 404s on your running container?18:04
corvusShrews: yep, localhost:900018:04
*** nilashishc has joined #zuul18:04
Shrewsdid you expose the port?18:04
corvusShrews: yes, the 404 is from cherrypy18:04
*** electrofelix has quit IRC18:05
corvusi'm assuming that since i switched the image to zuul-web, docker will have pulled the latest; i guess it's possible it didn't though.  i should figure out how to double check that18:05
corvuszuul/zuul-web            latest              6e629f6d6a98        8 days ago          236 MB18:06
corvusthat looks rather old actually18:06
corvusi'll go delete stuff and try again18:06
*** j^2 has joined #zuul18:07
tobiashthis one will fix the disk accountant in the zuul docker images: https://review.openstack.org/60631418:10
Shrewscorvus: i'm running a shell on a zuul-web container... i don't see any zuul static files18:11
Shrewstrying to figure out where they're supposed to be18:11
*** nilashishc has quit IRC18:13
tobiashShrews: I think I have a hack in my images for this too (in the dockerfile)18:13
tobiashShrews: I think they need to be in <installroot>/pythonx/site-packages/zuul/web/static/18:14
Shrewsdoesn't seem to me that the pbr setup_hook has been run at all.18:14
pabelangercurrently doing a budget for Berlin (zuul forum), which hotel have people booked with?  Seems all are a bit from the conference18:15
Shrewstobiash: yeah, they're not there18:15
Shrews# ls /usr/local/lib/python3.7/site-packages/zuul/web18:15
Shrews__init__.py  __pycache__  handler.py18:15
tobiashdefinitely missing18:16
tobiashis the source dir still in the image?18:16
Shrewsoh18:16
tobiashI think my hack was to move it from the source dir (I clone zuul in the dockerfile) to the correct dir18:16
Shrewsi wonder if this is it:18:16
Shrewsdef _build_javascript():18:16
Shrews    if subprocess.call(['which', 'yarn']) != 0:18:16
Shrews        return18:16
Shrews'which yarn' returns 1 (not found)18:16
tobiashmakes sense18:17
Shrewsso the code below it to setup the static files doesn't execute18:17
corvusShrews: my understanding is the build container is supposed to have yarn installed18:17
corvus(but, if it doesn't, that would certainly be a problem)18:17
corvusthe final zuul-web container shouldn't have it though18:17
tobiashis pbrx a two step process?18:17
Shrewscorvus: maybe the build container does, but zuul-web doesn't. i'm not sure when this setup part gets executed18:18
corvusShrews: it's supposed to happen at build time18:18
tobiashin this case the bug is probably that the js stuff is just not installed and thrown away with the source18:18
clarkbtobiash: yes there is a build container that is thrown away, and all of the artifacts from that container are installed cleanly into the target containers with wheels so that you don't have build artifacts left in the image18:18
clarkbthe change above https://review.openstack.org/#/c/608411/ was supposed to be the fix for that I think18:18
tobiashok, so that makes my hack impossible ;)18:18
clarkbmaybe check if building a local sdist/wheel works at all if yarn is installed18:19
tobiashbtw, the react rewrite fixes the installation of the js stuff18:19
Shrewsyarn is not installed on zuul-base either18:19
Shrews:(18:19
corvusShrews: it's not supposed to be18:20
corvusthe container with yarn installed is discarded; it should not be in any of our published images18:20
corvus(or, i should say, the container which is *supposed* to have yarn installed, i don't know that it does)18:21
Shrewscorvus: all of the images are based off of the *-base image18:21
Shrewscorvus: so your statement confuses me18:21
corvusShrews: building is a two step process: a "build container" is created with yarn installed.  it builds a wheel.  the wheel is installed into the final image that we publish.18:21
Shrewswhere is this process? pbrx certainly isn't doing that18:22
Shrewsand pbrx is the only process i'm aware of that builds images that we publish18:23
corvustobiash: mordred updated the react patch with the same fix for building/installing js that has already landed; it should work the same either way18:23
tobiashah ok18:23
Shrewscorvus: oh, maybe it's python-base container that has this.18:25
Shrewsi forgot about that "other" intermediary container18:25
corvusShrews: http://git.openstack.org/cgit/openstack/pbrx/tree/pbrx/container_images.py#n21518:25
corvusyes that18:25
*** panda has quit IRC18:26
corvusand yarn [compile test platform:apk]18:26
corvusis in zuul's bindep which should cause it to be installed there when we do the bdist_wheel18:27
*** panda has joined #zuul18:28
openstackgerritMerged openstack-infra/zuul master: Add coreutils to bindep on platform apk  https://review.openstack.org/60631418:42
corvusi've approved the react patch18:43
pabelangerYay18:45
Shrewsoh, hahah. corvus, i think i found the issue18:52
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Fix pbr setup hook  https://review.openstack.org/60875318:53
Shrewscorvus: ^^18:53
Shrewslet's wait to see the output to confirm it's getting called, but i think that's it18:54
openstackgerritMerged openstack-infra/zuul master: Revert "Revert "web: rewrite interface in react""  https://review.openstack.org/60747919:08
*** samccann has quit IRC19:10
*** samccann has joined #zuul19:10
tobiash\o/19:31
*** samccann_ has joined #zuul19:43
*** samccann_ has quit IRC19:43
tobiashcorvus: just tried the docker-compose but it doesn't work behind a mandatory proxy. I guess that's fine for the start?20:00
corvustobiash: ah yeah... though if you know how to fix that, we should update it to support that :)20:09
corvusShrews: wow nice20:09
clarkbtobiash: is it failing to dowload the images? everyting else should be local right?20:10
tobiashclarkb: some docker builds fail: http://paste.openstack.org/show/731712/20:11
corvuswe could build all the necessary images; it just seemed a little weird.  maybe we can pass the necessary env variable to docker20:14
tobiashcorvus: with a mandatory proxy we need to pass the proxy vars as build args to the docker build20:16
tobiashthey will be available as env vars then inside the build20:16
clarkbcorvus: or reuse the centos image that gerrit is already pulling in?20:16
Shrewscorvus: right? i can't find anything in the output to indicate it actually ran though20:18
tobiashcorvus: added a comment to  608344 that fixes the build of the node image for me behind the proxy20:18
corvusclarkb: can you elaborate?  are you suggesting the centos image has everything we need for a build node already installed?20:20
clarkbcorvus: yes because centos uses yum which requires python20:21
clarkb(however I don't know if it has an sshd in it)20:21
corvustobiash: that looks reasonable20:21
tobiashcorvus: same for gerrit20:21
corvusand gerritconfig?20:21
tobiashI'm waiting for the gerrit build to finish20:22
tobiashthe proxy via vpn is not that superfast ;)20:22
corvusoh.. you know what, we might be able to use the upstream gerrit image now20:24
corvusi think the only change in there was the ssh-keygen and i don't think it's necessary any more20:25
clarkbpassword: secret ftw20:25
corvusyep.  that's a day i'm never getting back.  but i learned a lot about gerrit and docker.20:26
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: docker-compose quickstart example  https://review.openstack.org/60834420:28
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Support mandatory proxy in docker-compose example  https://review.openstack.org/60876420:30
tobiashcorvus: that fixes the docker builds ^20:31
tobiashfeel free to squash or throw away20:31
corvustobiash: thanks i'll squash that into my change now, you can go ahead and abandon20:31
tobiashok20:31
tobiashcorvus: scheduler startup fails on my laptop: http://paste.openstack.org/show/731713/20:35
corvustobiash: ah i think i understand20:37
tobiashI don't ;)20:37
tobiashbut it's late20:37
corvusit's a misleading error which could mean any kind of authentication error20:37
corvusi don't think the user has been created yet; we probably need the scheduler to wait a bit more before starting20:38
corvuswhen i went through this the first time, i didn't have any projects in the tenant config.20:38
corvusso... there's two ways we could fix this: start with an empty tenant config and have the user add the necessary projects, or have the scheduler wait for the account to exist before starting.20:38
corvustobiash: if you ctrl-c and then 'docker-compose up' again i think it should work the second time20:39
tobiashtrying20:39
tobiashgerritconfig failed: http://paste.openstack.org/show/731714/20:43
tobiashbut that also could well be caused by the proxy20:43
corvustobiash: which task was that?20:45
tobiashit couldn't resolve 'gerrit'20:45
tobiashadd admin ssh key to gerrit20:46
corvustobiash: hrm.  docker is supposed to do some magic to do internal dns resolution20:47
corvusand gerritconfig "depends-on" gerrit so it should be up when it runs20:47
tobiashstrance is that 'get first login screen' doesn't output an error20:47
tobiashs/strance/strange20:47
corvusit has ignore_errors set to true20:48
corvus(because the first time that url is hit, it normally is an error)20:49
*** pcaruana has quit IRC20:49
tobiashah and it will be the same 40420:49
tobiashI think that 404 comes from the docker proxy of my docker for mac20:50
corvustobiash: is docker causing the request from the gerritconfig container to go through your corporate proxy on the way to the gerrit container?20:52
tobiashcurrently checking that20:52
tobiashmaybe the proxy vars are injected into the containers (which is bad)20:52
corvustobiash: i think maybe that's the case: https://docs.docker.com/docker-for-mac/#proxies20:52
corvustobiash: so it might just be ansible honoring the proxy env var20:53
tobiashyeah, docker for mac and proxies guarantees various problems...21:00
tobiashcannot get it to work today...21:00
corvustobiash: maybe you can set the proxy env variable for the gerritconfig container... it shouldn't need to use the network21:00
corvusthe external network that is21:01
tobiashit shouldn't be set (build args are not persistent)21:02
tobiashand I also tried to explicitly unset it in the ansible task21:02
clarkbyou should be able to se a noproxy var for specific ips or ramges21:03
corvustobiash: i'm not 100% sure setting it in the task will help depending on how the uri module is implemented (it might only look at the env var that ansible-playbook was invoked with)21:04
corvustobiash: i meant that docker-compose lets you set env variables for the containers too (not just the build)21:05
corvustobiash, clarkb: maybe we can add "no_proxy=${no_proxy},gerrit,..." to the docker-compose file...21:05
corvus(though it seems really weird to me that we would need to explicitly add the vars in the build but not running but whatever docker)21:07
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: docker-compose quickstart example  https://review.openstack.org/60834421:08
corvustobiash: ^ see what i did there for gerritconfig21:08
tobiashyes, that worked21:09
tobiashand scheduler is running21:10
corvusyay!  i think my scheduler.yaml playbook still isn't right21:10
corvusi'm trying cycles of "docker rm examples_gerrit_1; docker volume prune" to verify21:11
tobiashcorvus: but I would recomment a slightly different version: http://paste.openstack.org/show/731715/21:11
corvusthat's needed to remove all the persistent state in gerrit21:11
tobiashas I think completely unsetting these variables is cleaner and more robust21:11
corvustobiash: ok... i figured the no_proxy thing might be safest, in case something does want to access the network later?21:12
tobiashcorvus: well, if you want to add stuff later that wants to download things then yes21:13
corvustobiash: it seems like the most generally correct thing to do -- if it works, it should solve the problem and be future proof (and it might get copy/pasted to something else), so if it works i'd like to use just no_proxy.21:15
tobiashack21:15
corvustobiash: should the 'https_proxy' line use the https_proxy variable?  (it's currently <<https_proxy: "${http_proxy}">> )21:16
openstackgerritMerged openstack-infra/zuul master: Fix pbr setup hook  https://review.openstack.org/60875321:16
tobiashyes21:16
tobiashI was just lazy as it's the same here ;)21:17
tobiashI did a prune and docker-compose up starts up completely on docker on mac and with proxy21:18
tobiashI think that's the most challenging combination ;)21:18
corvustobiash: yay!  i think i just about have the scheduler playbook right, so my next patchset should work for your env and mine from scratch21:20
tobiashcorvus: cool, will try it tomorrow21:21
* tobiash calls it a day21:21
corvustobiash: thanks!21:22
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: docker-compose quickstart example  https://review.openstack.org/60834421:44
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Revert "Revert "Revert "web: rewrite interface in react"""  https://review.openstack.org/60877921:45
corvusmordred: when you're around, can we chat about the js tarball thing?  there are two issues we should resolve: 1) it's an undocumented deployment method.  2) it's untested.  openstack should, like everyone else, really be deploying zuul via a method that is both documented and tested.  (cc tristanC, tobiash, fungi)21:50
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: docker-compose quickstart example  https://review.openstack.org/60834422:11
mordredcorvus: I agree with taht premise - I'm afraid my in-flight wifi is potentially too spotty for me to be able to participate in a meaninful discussion on the correct fix ... but let me say a few thoughts and if we get lucky maybe it can even be close to a chat - but I might also disappear midthought22:53
mordredcorvus: for our draft jobs to work, we need to deploy the static javascript code to logs.o.o - perhaps we should rework those jobs to extract the contents of the built tarball into place?22:54
mordredcorvus: alternately we can keep the draft jobs as they are and change openstack's deploy to proxy the static content served by zuul-web instead of serving the content directly from apache22:55
mordredok. that's not a ton of thoughts - but those are my main two thoughts22:55
clarkbapache is set to cache the data coming frkm zuul right?22:57
clarkbmaybe thats good enough and zuul can serve the content22:57
mordredyah - it should be fine to do that22:59
mordredI think it should also make the rewrite rules much simpler23:00
*** rlandy is now known as rlandy|bbl23:11
*** quiquell|off has quit IRC23:27

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