Friday, 2015-04-24

*** sdake has quit IRC00:03
cloudnullThere were hash problems earlier today but I'm not sure at this point. I can help dig into it in a little while.00:11
openstackgerritMerged stackforge/os-ansible-deployment: Add newline to /etc/ssh/sshd_config if necessary  https://review.openstack.org/17675800:13
*** sdake has joined #openstack-ansible01:22
*** sdake_ has quit IRC01:26
openstackgerritMerged stackforge/os-ansible-deployment: Allow users to configure the Glance flavor in use  https://review.openstack.org/17646401:42
*** sdake_ has joined #openstack-ansible01:50
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updates for tag 10.1.4  https://review.openstack.org/17705001:51
*** sdake has quit IRC01:53
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Update for tag 9.0.8  https://review.openstack.org/17705101:55
*** JRobinson__ has quit IRC02:07
*** devlop has joined #openstack-ansible02:39
*** galstrom_zzz is now known as galstrom02:47
*** devlop has quit IRC03:00
*** devlop has joined #openstack-ansible03:00
*** sdake has joined #openstack-ansible03:00
*** galstrom is now known as galstrom_zzz03:02
*** javeriak has quit IRC03:03
*** sdake_ has quit IRC03:04
*** sdake_ has joined #openstack-ansible03:04
*** bilal_ has quit IRC03:06
*** sdake has quit IRC03:08
*** galstrom_zzz is now known as galstrom03:48
*** devlop has quit IRC04:00
*** galstrom is now known as galstrom_zzz04:10
*** subscope_ has joined #openstack-ansible04:30
*** JRobinson__ has joined #openstack-ansible04:45
*** markvoelker_ has quit IRC04:51
*** subscope_ has quit IRC06:11
*** stevemar has quit IRC06:32
*** JRobinson__ has quit IRC07:05
*** sdake_ has quit IRC07:20
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672008:03
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Make script executable and BSD sed compatible  https://review.openstack.org/17711508:07
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Make script executable and BSD sed compatible  https://review.openstack.org/17711508:19
*** javeriak has joined #openstack-ansible08:32
*** javeriak has quit IRC09:12
svgcan anyone give me some hints on the disk space sizing for metal hosts? I assume logging hosts (elasticsearch) and especially infra hosts (database) are specific here09:13
svgseems I can't find any hints on how big mysql could grow09:13
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Set external roles to import into ansible namespace  https://review.openstack.org/17713109:14
odyssey4mesvg it all depends on how big your openstack environment will grow, but any sizing recommendations that you'll find for openstack in general would apply09:15
svgwell, thats the thing, I cant find anythong that gives even the wildest guess/idea.09:16
matttodyssey4me: do deleted records now actually removed from the dbs?09:16
odyssey4meyou've identified the two main ones, the only other one is where the glance container lives due to the fact that by default we set glance to cache images - you can override it though and you can also set your glance container sizing appropriately09:16
svghm, given we use ceph, I think I disable glance caching09:17
svgor at least it should be09:17
odyssey4memattt honestly I have no idea - I know that since Havana (or was it Icehouse) there is a set of shadow tables which acts as some sort of revert archive for the projects09:17
odyssey4mesvg ah yes, I think I saw you doing that in your code :)09:17
svgdeploying an image to a vulume is a pure ceph thing09:17
svgbasically, I want to know how many disk space I should provision on the infrahosts, at least enough to get us started for a while09:18
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Set external roles to import into ansible namespace  https://review.openstack.org/17713109:18
svgupstream openstack mentioned avuelt '100gb' for a controller node, but that's the best I could find09:18
svg.. mentioned a vague..09:19
odyssey4mesvg I'm not sure what defaults we use at RAX, but in most cases I expect that the typically lowest size SAS drive of 160GB will do as a starting point?09:19
odyssey4meI have no empirical data to work from though.09:19
odyssey4meYou may wish to have something like 60GB for your OS and 100GB for your lxc VG. Test that and see how it goes?09:20
svgodyssey4me: we have blades with one ssd of 75GB, so we plan to mount a ceph block device on /var/lib/lxc/09:21
svgso yes, at least 100gb was the idea for now09:22
odyssey4mesvg in my own experience I found that using a ceph block device in a block like that wasn't very reliable... but that experience is around a year old09:22
odyssey4meissues we found were:09:23
svgI have a metal host with around 22 containers taking at fresh deploy around 30gb09:23
svg(infra+storage host combined)09:23
odyssey4me1) resizing that block device was a bit of a pain, it is definitely better to have a block device per instance to simplify resizing when need be so that your down-time isn't for the whole controller but instead just for the instance that needs a resize09:24
svghm, goven the random container names, that moight be a pain to provision09:24
svgbut good point09:24
odyssey4me2) when you reboot the host with a block device mount, sometimes it causes a kernel panic and other times it causes an unclean shutdown... you have to very manually shut down each container before manually dismounting the device (which is when the kernel panic happens), then reboot the host09:25
odyssey4me3) on boot up the mounting of the block device doesn't happen properly because it's not a normal block device... you may need to set the containers not to start automatically on boot and you may also have to remount the block device manually09:26
odyssey4meto be fair though, this is the experience based on Ceph Calamari, I think the code-name was09:26
odyssey4meYMMV based on newer Ceph versions09:27
svg2 and 3 sounds very to the point09:27
svgnot sure why resizing was a pain though09:27
odyssey4mea pain for a few reasons:09:27
odyssey4me1) the resize operation when I was doing it was not an online thing - you had to shut the containers down, take the pool off-line, copy the pool to a new one that's larger, remove the old pool, set the new pool to be mounted in place of the old one, then mount it and bring the containers online again09:29
odyssey4meoh, and of course you had to extend the partitions inside the containers, or something like that09:30
odyssey4menot sure if that's still the process - check that out as it's an important operational process to be aware of when using ceph for your controllers09:30
svgafaik, resizing an rbd is just one command now09:31
odyssey4meok, is it online09:32
odyssey4mebear in mind that all it'll do is increase the available disk - you still then need to do partition and file system expansions09:32
svgI'm more worries about your 2/ and 3/ though09:33
odyssey4melvm should make that easier09:33
odyssey4mesvg yeah, those were a pain - generally in that environment we resolved to rather use local disks for controllers to maintain reliability and seperation of concerns09:34
svgsure, but that's pretty straightfoward09:34
svgbtw, kilo release is imminent right? does osad follow that quickly?09:34
odyssey4mewithin openstack there weren't issues as it was one rbd image per volume and the attach/detach/reattach was reliable for the most part09:34
odyssey4mesvg yeah, kilo is in RC2 I think and we've already got QE teams testing based on the latest kilo patch sets... so the osad kilo release will likely follow very quickly after upstream kilo releases09:35
odyssey4mewe're just busy fighting some changes to Horizon dependencies upstream which appear to have broken things... busy tracking that down and figuring out how we can get past it09:36
*** sdake has joined #openstack-ansible09:37
odyssey4memattt any luck tracking down a fix for the Horizon issue - or are you chasing the master/heat squirrel?09:37
svgok, so now I'm still working on a juno setup, with my ceph patch, but given we hope do to a production setup  by the end of May, that probably will be based on kilo09:38
svgwhich also means, I'll need to reimplement the ceph patch on kilo, and I guess that will be closer to upstream it first on master, and backport it in kilo09:39
*** sdake_ has joined #openstack-ansible09:39
odyssey4mesvg yeah, that's the usual workflow09:39
svgwhich means I can work on it more seriously in the coming weeks09:40
odyssey4meonce we release kilo we'll also start working on implementing Ceph in master - we're targeting that for a feature release so we'll likely be collaborating on doing that at the same time09:40
odyssey4meI'm not sure of the exact timelines, so you may end up doing the first draft before we dig into it - but your work so far has been a really good start!09:41
svgI didn't get much feedback on the ceph WIP patch - my primary concern was to know if the style of roles/playbooks/vars is in line with what is expected09:42
*** sdake has quit IRC09:43
odyssey4mesvg yeah, we've been very busy focusing on kilo so we haven't had much time to go through it properly09:43
odyssey4mefrom what I've seen and some off-the-cuff discussions we had the style is good in general, but yeah we haven't had much time to dig into it09:44
svgI probably will on an updated kilo patch, as one of the things we want to test in coming weeks is upgrading the stack, so with juno>kilo now is a good time09:44
odyssey4mesorry about that, but you know how resourcing priorities work - we all have deadlines and yours and ours aren't quite matching just yet :/09:45
svgno need to apologise, just wanted to know how things get going, and how I can optimize my private work to show it upstream09:45
odyssey4mesvg we have this to help with upgrading: https://github.com/stackforge/os-ansible-deployment/blob/kilo/scripts/run-upgrade.sh09:46
odyssey4methat'll be something to consider as part of your upgrade testing and kilo patch09:46
matttodyssey4me: i don't think we need scss09:47
matttodyssey4me: looks like it should be using pyScss instead09:47
odyssey4memattt oh? this is the error I'm getting: django_pyscss.compressor.DjangoScssFilter: not found09:47
matttodyssey4me: which version of django-scss are you using?09:48
odyssey4meaha, I see it - let me try that out09:48
mattti've not gotten that far, but i just noticed that scss isn't even in global-requirements.txt09:48
odyssey4meyup, I think you may be right09:48
svgthat script looks very throrough. the process still sounds scary though :)09:49
odyssey4mesvg it's not that bad - openstack upgrades are pretty good these days09:51
svgopenstack in general or thanks to osad?09:51
odyssey4mein the old days with essex and before it was nasty, but the upgrade process got to be a lot more reliable from around Havana I think it was09:51
odyssey4meopenstack in general09:52
svgok, so most people I hear talking ugly stories about this, are talking aout older experiences I guess09:52
odyssey4meosad, well, we've done the script because the v10/juno to the v11/kilo upgrade involves a few architecture changes and the script takes care of doing that all for you09:52
odyssey4mesvg yeah, most of the time the upgrades are painful due to fiddles people have done to fix bugs they found which weren't backported to whatever release they were using... so you have to review code, etc09:53
odyssey4mewith osad we're deploying from git sources so you could, in theory, have your own git repo with openstack source and deploy from there09:54
svguhuh09:54
odyssey4meso your bugfixes can go through a normal development process and you can throw developers against it instead of throwing operations guys at it09:54
odyssey4mealternatively you could just track the upstream repo at whatever level you want - whether it be a tagged version, the 'stable/blah' branch, or a sha which has the fix you need09:55
odyssey4meosad makes it flexible to do that09:55
svgfor now, given our limited experience, we'll stick to the well tested upstream version :)09:56
odyssey4meyup, with great power comes great responsibility :)09:58
svgow, I see e.g. the mysql db folder in the container is mounted separately from /opemstack/...10:00
odyssey4memattt I removed scss and ensure that pyScss was installed, but no go10:00
svgso extra disk space is more needed on that mount point10:00
odyssey4mesvg yeah the mysqldb folder it a bind mount to the host - different to most of the others10:01
odyssey4methe idea there is that the container can be replaced, but the data folder will stay behind... also you can backup the data using a backup agent on the host10:01
svgoh, and there are even daily backups10:03
matttodyssey4me: what version of django-pyscss ?10:06
matttneeds to be <2.0.010:06
*** markvoelker has joined #openstack-ansible10:06
odyssey4medjango-compressor==1.510:06
odyssey4medjango-pyscss==1.0.610:06
odyssey4mepyScss==1.2.110:06
odyssey4meXStatic-Bootstrap-SCSS==3.2.0.010:06
matttthat all looks ok, hmm10:06
matttbut no django-pyscss10:07
matttodyssey4me: https://github.com/openstack/horizon/blob/ea92edacbb3daf77326549f4b6b61e210068ebba/requirements.txt#L1710:07
odyssey4methere is - second line I posted10:07
matttderp10:07
* mattt drinks more coffee10:09
*** markvoelker has quit IRC10:11
odyssey4methe class it's looking for definitely exists... grrrr10:12
matttodyssey4me: yeah seeing that now10:15
odyssey4mestevelle stable/kilo's horizon does not complete our play due to the execution of 'horizon-manage.py compress --force' failing10:21
odyssey4methe error is CommandError: An error occured during rendering /usr/local/lib/python2.7/dist-packages/openstack_dashboard/templates/_stylesheets.html: /bin/sh: 1: django_pyscss.compressor.DjangoScssFilter: not found10:22
matttCompressing... CommandError: An error occured during rendering /usr/local/lib/python2.7/dist-packages/openstack_dashboard/templates/_stylesheets.html: /bin/sh: 1: django_pyscss.compressor.DjangoScssFilter: not found10:29
mattt/bin/sh ??10:29
odyssey4memattt interesting: sh -> dash10:31
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716010:35
stevelledjango-pyscss released a 2.0.1 since yesterday10:38
stevelleinteresting10:38
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716010:42
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716310:45
odyssey4mestevelle mattt busy in #openstack-horizon trying to track the issue down10:47
matttodyssey4me: following along :)10:49
*** sdake_ has quit IRC10:53
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17717210:58
odyssey4memattt stevelle how do we generate a fresh example local_settings.py file from source?11:00
matttodyssey4me: ansible creates taht11:01
matttthere is a .example in /usr/local/lib/python2.7/dist-packages/openstack_dashboard/local11:02
*** markvoelker has joined #openstack-ansible11:07
matttlooks like we're still configuring horizon w/ a db even tho the db is no longer getting created11:09
matttat least, i'm assumign that's why it's failing to connect to it :)11:10
stevelleI'm still kinda stumped11:11
*** markvoelker has quit IRC11:12
odyssey4memattt oh? that and https://github.com/openstack/horizon/blob/stable/kilo/openstack_dashboard/settings.py#L27 appears to be missing from our local_settings.py template11:12
stevellehttps://review.openstack.org/#/c/170988/11:16
stevellewe need to get that change in I think11:17
stevellefor other reasons11:17
odyssey4mestevelle in the testing I'm doing we're using sha's from this morning11:18
odyssey4mebut, as you've mentioned - since we prepared our templates there have been updates and we need to review those11:18
matttodyssey4me: https://gist.github.com/mattt416/58fd9314f947d4ee0d4d11:18
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17717211:18
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716011:20
stevelleodyssey4me: the exceptions on lines 77-79 of local_settings.py.example from that patch11:20
stevelleguessing that would be unrelated though11:20
odyssey4mestevelle prepa a patch for master while you're there :)11:21
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716311:22
odyssey4mecloudnull ping when you're online, we need to track down which package is pulling in scss as a dependency as we're not explicitly pulling it in11:45
Sam-I-Amstevelle: isnt it kind of early there?11:49
stevelleum, yup11:49
Sam-I-Amless work, moar zzz?11:49
stevelleI might just start happy hour early11:50
Sam-I-Ami'm planning that for 9 am11:50
matttstevelle: i want to visit portland, maybe i can go to the next pycon11:50
mattteven tho i don't py11:50
stevelleI look forward to it mattt.11:50
Sam-I-Ammattt: but pie is so tasty11:51
Sam-I-Amodyssey4me: whats this issue?11:51
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672011:52
odyssey4meSam-I-Am so regardless of the fact that we don't ask for the python module scss to be around, it ends up on the horizon containers - and it and pyScss conflict in name spaces11:53
odyssey4meso we get a failure when trying to do the css compression11:53
matttodyssey4me: nuked horizon containers, rebuilt, ran os-horizon.yml, and everything installed fine11:53
odyssey4memattt I've revised the patch and updated the sha's as well for good measure11:53
odyssey4melet's see how it looks11:54
matttsweet11:54
Sam-I-Aminteresting11:54
odyssey4meI'm going to rebuild my containers as well11:54
odyssey4meactually, I'll rebuild the whole AIO11:54
*** markvoelker has joined #openstack-ansible11:54
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Make script executable and BSD sed compatible  https://review.openstack.org/17711511:55
*** mnestheu1 has joined #openstack-ansible12:02
*** galstrom_zzz is now known as galstrom12:06
cloudnullmornings12:06
cloudnullodyssey4me: ping12:07
cloudnulljust read scroll back. whats the word on scss and horizon broken for all the things ?12:07
*** subscope has quit IRC12:11
odyssey4mecloudnull we're testing now, we've definitely found that scss must not be on the horizon containers - the right python package is pyScss12:12
cloudnullah thats exciting12:13
odyssey4meis there a way to determine on the repo container why a package was included?12:13
odyssey4meunfortunately both packages use the same namespace, so they conflict if they're both there12:13
odyssey4meyou have to literally remove both, then add pyScss back12:13
odyssey4mehaha: from https://pypi.python.org/pypi/scss/12:14
odyssey4meWarning: Im not support python-scss anymore. Use pyscss by Kronus.12:14
cloudnullso this makes a lot of sense, i was looking back over logs yesterday and I had http://cdn.pasteraw.com/3jmmaktxjg2zmqn2atvxep2apr01xv8 as a diff for a broken kilo and a working master system.12:17
cloudnullodyssey4me yes, you can look at the report12:17
cloudnullwhich has all the packages and what was listing them as a dep.12:17
cloudnullIE something like this http://104.130.161.213:8181/reports/release-kilo-report.json12:18
odyssey4meok, good news - with pyScss now in our requirements the older defunct scss is no longer being pulled in12:18
odyssey4mestill verifying whether we get a successful build completion12:18
cloudnullin reading the report anything thats under "_requirements_" is user defined12:19
cloudnullwhich i have "scss" as being user defined (because we were adding it to the PR for kilo) and "pyScss" as a dep for horizon.12:19
odyssey4mecloudnull yeah, I've updated the review to switch to the right package12:20
cloudnullnice12:20
* cloudnull fingers crossed12:20
odyssey4mesee https://review.openstack.org/176720 which is around half-way through the gate check12:20
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add basic orchestration tests to the gate check  https://review.openstack.org/17616612:22
*** andymccr has quit IRC12:24
cloudnullwell thats exciting http://logs.openstack.org/60/177160/3/check/os-ansible-deployment-dsvm-check-commit/e6ea45c/console.html12:25
*** subscope has joined #openstack-ansible12:25
matttcloudnull: oh boy12:27
cloudnullall console logs are throwing 5xx12:27
Sam-I-Amyou didnt need them anyway12:27
matttopenstackgerrit: you shouldn't have to specify pyScss12:27
mattt^^^ odyssey4me12:28
matttit'll get pulled in via requirements12:28
*** galstrom is now known as galstrom_zzz12:28
mattthorizon has a proper dependency on it12:28
odyssey4memattt alright, I can set that - has pathlib also been set properly?12:28
odyssey4meit doesn't appear so12:29
matttodyssey4me: i wanted to test if we needed that explicitly, not had a chance yet :(12:29
cloudnullasked in infra12:30
matttodyssey4me: let's see if this guy builds correctly before we restart the build12:30
matttcurrently doing neutron12:30
odyssey4memattt fair enough :)12:30
odyssey4mepathlib doesn't appear to be anywhere12:30
odyssey4meshould that be a horizon bug perhaps?12:31
mattti think it was, sec12:31
matttfinding it12:31
odyssey4mehttps://bugs.launchpad.net/devstack/+bug/144747612:31
openstackLaunchpad bug 1447476 in OpenStack Dashboard (Horizon) "No module named pathlib" [Critical,Fix released]12:31
matttthat's it!12:32
matttso caused by django-pyscss 2.0.112:32
matttnow we're back down to < 2.0.0 it shouldn't be needed12:32
odyssey4meyeah, it appears that it should be pulled in from django-pyscss12:33
odyssey4meso the updated sha's should take care of it - but let's wait and see the result of the build before doing a new patch set12:33
mattthere we go12:35
odyssey4memattt in my test AIO it appears to be working12:36
odyssey4meyup, horizon play is done with no errors12:36
matttok great12:36
matttso now back to master to see if the heat issue persists :P12:36
* cloudnull happy dance12:36
odyssey4meok, so we remove the deps and see whether that passes now?12:37
matttcool!12:37
odyssey4meoh, fail?12:38
matttWUUUUT12:38
matttthese are debian packages12:39
odyssey4mefailed: [aio1] => (item=curl,gcc,git-core,liberasurecode1,liberasurecode-dev,libffi-dev,openssh-server,python-dev,rsync) => {"attempts": 5, "failed": true, "item": "curl,gcc,git-core,liberasurecode1,liberasurecode-dev,libffi-dev,openssh-server,python-dev,rsync"}12:39
* odyssey4me sighs12:40
odyssey4memy aio passed, so it would seem this is a transitional error in openstack-ci12:40
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672012:41
matttodyssey4me: i saw this error somewhere else today12:41
matttso it's not the first time12:41
cloudnullmiguelgrinberg's patch for heat testing has been running into this too12:41
matttcloudnull: ah that's it12:41
odyssey4meupdated review without the explicit deps12:41
mattti can't tell what it's actually failing on tho12:43
mattthttp://logs.openstack.org/20/176720/7/check/os-ansible-deployment-dsvm-check-commit/ca7cc54/logs/ansible-logging/ansible.log doesn't reveal much12:43
odyssey4meyeah, my AIO even passed tempest tests so it seems that we may have finally beaten down the kilo branch gate block12:44
matttso master is failing on heat install due to12:57
mattt  Could not find a version that satisfies the requirement python-saharaclient>=0.9.0 (from heat) (from versions: 0.8.0)12:57
matttwe only have 0.8.012:57
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Set gerrit default branch to kilo  https://review.openstack.org/17624612:57
matttgoing to bump it in master12:58
odyssey4mestevelle are you prepping a patch for master for the horizon local_settings changes needed?13:00
odyssey4meI think we need to get that in and backport it to kilo before we do the next kilo rc13:00
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Bump python-saharaclient  https://review.openstack.org/17724113:04
matttfailing to create launchpad bugs, so no Closes-Bug in the above review13:04
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17665713:06
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Bump python-saharaclient  https://review.openstack.org/17724113:08
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Removed hard coded package pinning for mariadb/galera  https://review.openstack.org/17725913:27
matttbah, what is this swift failure13:33
odyssey4memattt cloudnull yep: http://logs.openstack.org/20/176720/8/check/os-ansible-deployment-dsvm-check-commit/328bb37/console.html#_2015-04-24_13_28_33_82113:37
*** KLevenstein has joined #openstack-ansible13:37
odyssey4meprobably another upstream mirror bork13:37
*** andymccr has joined #openstack-ansible13:42
odyssey4memattt cloudnull so the packages being installed at the time are: liberasurecode1,liberasurecode-dev13:45
odyssey4methe other packages in the list are already there13:46
*** Mudpuppy has joined #openstack-ansible13:47
cloudnullyea, curious if those are being missed due to a repo not enabled on the new dsvm image?13:47
matttit seems to download them tho doesn't it13:47
odyssey4meyeah, it seems to actually do all the bits in the container - but it fails on the host with no output13:48
odyssey4meso cloudnull  may be right - it's another funny in the image13:48
matttsee bottom of http://logs.openstack.org/20/176720/8/check/os-ansible-deployment-dsvm-check-commit/328bb37/logs/ansible-logging/ansible.log13:48
odyssey4memaybe missing the backports pool - it seems to be coming from there in the container13:48
matttoh derp, that's the container :(13:49
*** Mudpuppy has quit IRC13:49
matttso installs successfully in container but not on host13:49
cloudnullwe could also re-enable the retry max for the successerator which will enable super debug on failure.13:49
*** Mudpuppy has joined #openstack-ansible13:49
odyssey4methis will tell us more about the repositories and packages: https://review.openstack.org/17665713:50
odyssey4mewe just have to wait for it to finish13:50
matttnice13:51
*** yaya has joined #openstack-ansible13:52
odyssey4meconfirmed that both packages happen to be from trusty-backports/universe and don't exist in any other pool13:52
odyssey4meodd: this one worked and has the other patch as a dependant: https://review.openstack.org/17624613:53
odyssey4merax-ord vs hpcloud-b113:54
matttyep13:54
odyssey4merax-rd worked, hpcloud didn't13:54
cloudnullhttps://review.openstack.org/#/c/176246/ <- kilo is happy13:54
odyssey4meyup, it appears that we have another hpcloud surprise13:54
matttcloudnull: about time13:54
cloudnullyay for hpcloud13:54
matttso do we ask infra to include that repo in their apt sources?13:55
matttor do we manually add it?13:55
odyssey4mecheck the initial apt-get updates in both logs13:55
matttthe latter would feel janky13:55
odyssey4mehpcloud has no backports repo13:55
odyssey4memattt for now to get things moving we should add it if it isn't there so we don't get more surprises13:55
cloudnullso we could, in the swift role, add the backports as its really only needed there13:55
odyssey4mebut yeah we should let openstack-infra know13:55
odyssey4mecloudnull I'd suggest doing it in the AIO bootstrap13:56
odyssey4meotherwise we're going down the road of doing deployer stuff again in the ansible things13:56
*** stevemar has joined #openstack-ansible13:57
cloudnullthis is true. we'll need to note something somewhere that swift, for kilo, needs the backports repo .13:57
cloudnullas this will likely be a problem in production if a host is not already setup to consume ubuntu backports13:57
matttis there no way to pull in swift with all the erasurecoding stuff?13:57
matttsince we're not using it13:58
mattt*witout13:58
odyssey4memattt yeah I suppose we could, but what happens if a customer does want to configure it?13:58
odyssey4me*deployer13:58
matttandymccr: is that a facility that's enabled in teh swift config?13:58
matttor does it just work out of the bo?13:58
mattt*box13:58
matttdang can't type today13:58
andymccri dont think it just works mattt and its not setup atm13:59
andymccrcos it was only just added as a feature13:59
andymccrbut tbh i havnt looked at it so im not 100% sure13:59
andymccrid be surprised if it just works out thebox though13:59
odyssey4meis anyone logging a bug for this already, or shall I?13:59
andymccrand atm you cant configure the ring to use erasurecode13:59
cloudnullmattt also its a py dep https://github.com/openstack/swift/blob/master/requirements.txt#L12 which has a hard dependency on the library being available https://bitbucket.org/kmgreen2/pyeclib/src/041d44311bf3d7d3f655dfc6c692d8693b9e0634/setup.py?at=master#cl-6213:59
matttthat sucks cloudnull13:59
matttodyssey4me: i can log a bug13:59
matttandymccr: ok but guess we have to pull it in :(13:59
odyssey4meshall I prep a patch for the AIO bootstrap?14:00
cloudnull+114:00
andymccryeh mattt i think its a swift dep itself isnt it?14:00
matttodyssey4me: https://bugs.launchpad.net/openstack-ansible/+bug/144815214:02
openstackLaunchpad bug 1448152 in openstack-ansible "swift installation failing in kilo branch" [Undecided,New]14:02
*** sigmavirus24_awa is now known as sigmavirus2414:03
matttthis is presumably an issue on master too i'd imagine14:03
cloudnull+114:04
andymccrand not just for us i'd imagine?14:05
Sam-I-Amkind of shitty when places have different images14:05
odyssey4meany thoughts on the best way to figure out of the backports repo is active - I'm thinking a grep of the output of 'apt-get -q update' at this stage because a trawl of the config files is less reliable14:09
matttodyssey4me: if a grep doesn't find it in /etc/apt/sources* then add it14:09
andymccrcant we just ensure it is?14:09
andymccrit shouldnt then add it twice14:10
cloudnullodyssey4me: # if ! grep -rni backports /etc/apt/sources.list*; then echo blah; fi14:11
odyssey4mecloudnull yeah, but the backports word could be in text description or in a commented line14:12
odyssey4meperhaps this is ok? grep -rni "^deb.*backports" /etc/apt/sources.list*14:13
cloudnullodyssey4me: # if ! grep -rn '^deb' /etc/apt/sources.list*| grep -i backports; then echo blah; fi14:13
andymccrthis is just for the gate?14:13
odyssey4meandymccr yep14:13
andymccrwhy cant we add an ansible task that just ensures that repo is there?14:13
andymccrlike if its a common thing its not going to just be a thing for the gate14:13
odyssey4meandymccr because then we're doing deployer work14:14
odyssey4mewe're interfering with the ubuntu repository configuration which for everything else we assume is already in place14:14
andymccrhmm14:14
andymccrbut as an example we have a default for mariadb repo - which isnt included by default in the ubuntu repo, you can set this as the deployer so its not hardcoded14:15
andymccrthe same would apply if you were trying to deploy the erasurecode packages which are not by default in there unless you include -backports14:15
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add ubuntu backports repository to AIO if it's not present  https://review.openstack.org/17728414:24
odyssey4meandymccr but the mariadb repo is something we added, the ubuntu is not a repo we added14:25
andymccrodyssey4me: sure, but the principle is the same - if the default is not always going to ensure that erasurecode packages are there - it would be helpful for the deployer to be able to configure the repository that contains those14:25
andymccrwe can set a sensible default as -backports, and you can even choose not to add it if the var doesnt exist14:26
odyssey4mebut then we're adding stuff to configure things that a deployer could do themselves and we step into the realm of fielding issues relating to some random thing they added14:26
andymccrhow? i dont see how thats any different to a deployer changing the mariadb repo and then asking us to field an issue on something random they added14:27
odyssey4mewe can't really set a sensible default either, I don't think - the patch I've done ^ grabs the info from the existing environment instead of relying on some arbitrary default set in the project14:27
andymccrput it this way if somebody tries to deploy os-a-d today and runs into that issue, they should manually add the repo?14:27
odyssey4meyes, they should have a play/role as part of their general infrastructure management which handles repository configuration14:28
andymccrthats the first time we've needed that though if im not mistaken?14:28
odyssey4mesomething that helps them do apt-get upgrades and all that14:28
odyssey4meandymccr yeah, this is thanks to the recent refresh of images in openstack-ci14:28
andymccrits also because the only packages from the backports repo that we needed are for the erasurecode stuff.14:29
andymccrand they got added in the latest swift release14:29
andymccrso before that you wouldnt have seen those issues14:29
matttodyssey4me: apt-get --print-uris update14:29
odyssey4memattt ooh, that's pretty cool14:30
odyssey4medo you think that'd be preferred over grep -qrni "^deb.*backports" /etc/apt/sources.list* ?14:31
odyssey4meI need to update the kilo patch with this, so I'd like to get it right14:32
matttodyssey4me: i think either is fine, but do "^deb .*"14:32
matttso you're not matching on deb-src14:32
odyssey4meandymccr fyi if you add a second copy of the repo source you get 'Duplicate sources.list entry' errors for apt14:33
mattt"^deb .*backports"14:33
andymccrid hope the ansible module doesnt let you add it twice?14:33
odyssey4memattt good call14:33
matttodyssey4me: may be worth being explicit and saying trusty-backports14:34
andymccrit just seems weird to me that we're adding it to containers but not hosts.14:34
odyssey4memattt good call14:34
andymccrso we're saying containers need the -backports but hosts arent getting it cos oyu shouldve added it manually?14:34
matttandymccr: problem is the host is preconfigured, the container isn't14:35
matttit would be complicated to _update_ someone's apt sources14:35
matttand you certainly can't blow it away and recreate14:35
andymccrmattt:  theres an apt module isnt there?14:36
matttandymccr: open source patches welcome?14:36
mattt:)14:36
andymccrim trying to figure out why nobody else thinks thats a sensible idea?14:36
andymccrim clearly missing something14:36
*** galstrom_zzz is now known as galstrom14:36
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672014:38
odyssey4meandymccr I think it's a great idea for something outside OSAD like rpc-extras, but not for OSAD14:38
andymccrodyssey4me: ok so why? like if we're defining it for the containers14:38
andymccrwhich we are.14:38
odyssey4meI don't even think we should be as prescriptive as we are for the containers14:38
odyssey4methe repo used is a deployer's choice14:39
odyssey4mein a previous life we refused to use backport repositories in order to reduce risk and increase stability - it was seen by some that backports weren't adequately tested14:40
andymccrwe're not letting that happen for the containers though? aside from that you could change a var, which is great - but you could use that same var14:40
matttandymccr: oh you meant ansible module, not python module14:40
andymccrmattt: yeah14:40
odyssey4memy mission right now is to unblock the gate though - if it's decided to do it differently that's great, but the decision needn't be made right now14:40
matttandymccr: yeah you could easily do this w/ ansible, but it's likely that the host's sources aren't configured with the same apt sources that are defined in os-a-d by default14:41
palendaeThe gate is blocked because we bumped the swift SHAs again right?14:41
andymccrmy point really is that as it stands it wont deploy at all without the backports repo - so anybody trying to adopt os-a-d may run into this issue and just be like f-it14:41
matttandymccr: so do you just blindly add a backports repo if it's missing, or do you figure out what other ubuntu mirror is being used, then use that?14:41
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672014:42
andymccrmattt: we're setting one for the containers, id just use that one14:42
odyssey4mepalendae nope, the gate is blocked because of loads of changes upstream in various ways14:42
andymccrit seems odd that somebody would want a diff repo for containers and hosts, so if htey havnt set it, they probably dont care?14:42
matttandymccr: yeah we could, i'm not aware of any glaringly obvious reasons why that'd be bad14:42
palendaeodyssey4me: Because we bumped SHAs...14:42
odyssey4mepalendae that may be, but for a kilo RC we need to bump sha's regardless and deal with the consequences14:43
matttandymccr: we should get more input then14:43
matttandymccr: and if the consensus is to add it then we get a review in14:44
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add ubuntu backports repository to AIO if it's not present  https://review.openstack.org/17728414:45
palendaeI came in halfway through this discussion, but are you guys suggesting that repos be left up to the deployer? If so, would OSAD even work standalone at that point?14:45
matttandymccr: what if we bail if the repo doesn't exist?14:46
odyssey4mepalendae my suggestion is that ubuntu repositories not be adjusted in our playbooks/roles14:46
matttw/ a helpful message for the deployer14:46
matttandymccr: is that a reasonable compromise ?14:46
andymccrmattt: naw cos if you had controlled your repos in a clever way and had those packages in a repo that wasnt "backports" it'd fail unnecessarily14:46
lbragstadcloudnull: quick ansible question for you when you have a minute. The current keystone-deploy stuff is broken up into roles (sql/http/memcache/etc..) but we also want the ability to support Centos. Do you have a recommendation for organizing the plays without doubling each role?14:46
palendaeodyssey4me: Ok, so for libraries like erasure coding that are necessary for swift, how do we get them?14:47
lbragstadcc dolphm ^14:47
odyssey4memattt then we get stuck in trying to keep up an exhaustive checklist in our plays, which is a very bad idea IMO14:47
dstaneklbragstad: i do it all of the time by keeping the dependent packages separately14:48
odyssey4melbragstad why not just add the code to the same roles, but adjust the tasks to accommodate the differences between platforms?14:48
odyssey4meif execute task when platform = ubuntu14:48
odyssey4me*ie14:48
cloudnulllbragstad to add additional OS support you'd need to add in seperation logic into the various roles and a new package set.14:48
lbragstaddstanek: you're recommending the when ansible_os_family == 'Debian' path, right/14:48
cloudnull^ yes14:48
odyssey4mepalendae we fail if the deployer's apt repository doesn't have the packages we want - just like we would for any other packages14:49
andymccrodyssey4me: yeah but we have a working by default thing (before this)14:49
lbragstadcloudnull: odyssey4me dstanek cool, that's the path that I start working down but it doubled the playbook sizes. I just wasn't sure if there was a better way?14:49
lbragstadhttp://cdn.pasteraw.com/7zp564z3pqylyj7pniaovnyiuln32hz14:49
palendaeodyssey4me: But for OSAD14:49
andymccrso does the default ubuntu image for 14.04 include the -backports repo by default?14:49
palendaeAre we defining nothing?14:49
odyssey4mebest we can do is note that the backports repo is required on swift containers and hosts14:49
odyssey4meandymccr yes14:50
andymccrit does? then i concur with your patch14:50
palendaeOr are we saying OSAD is no longer installable by itself?14:50
odyssey4meyup, the default Ubuntu deployment includes the backports repo - if it's not there then someone has changed it14:50
andymccrif its already there on a default ubuntu 14.04 install then i think its acceptable14:50
dstaneklbragstad: cloudnull: i do stuff like this: http://paste.openstack.org/show/205716/14:50
andymccrwhich image for gating is failing?14:50
matttandymccr: HP pub cloud image14:51
andymccralways :/14:51
andymccrok that makes sense at least14:51
odyssey4meyup, no surprises there :p14:51
lbragstaddstanek: ah... that makes sense14:51
dolphmdstanek: how are you using the 'packager' variable, for example?14:52
cloudnulldstanek you can break them up into vars, but you'd still need logic in the tasks to go to different tasks for rhel vs ubuntu.14:52
dolphmdstanek: using it in a 'when' for an apt task?14:52
dstanekforgot the important part: http://paste.openstack.org/show/205717/14:52
lbragstad{{ packager }} would be defined at the http role layer?14:52
dolphmcloudnull: breaking things up by distro sounds like a slippery slope to non-dry-ness14:52
cloudnullit is14:53
lbragstad:-/14:53
dolphmwell then it sounds like an anti-pattern :P14:53
cloudnullbut it would really only be for the instalaltion of OS packages.14:53
dstanekcloudnull: i have not come across the need to do that yet - my ansible needs so far have been to setup my dev environments and not control an infrastructure :-)14:53
dstanekputting the packages and packages in vars should be enough in this case14:54
dstaneks/packages and packages/packager and packages/14:54
cloudnullyes. but the task to install said packages, ubuntu vs centos, would be different and need something like a conditional when ansible_os_family == 'Debian'14:55
dolphmdstanek: but there are more differences between platforms than just package names :(14:55
cloudnulletc..14:55
dstanekdolphm: i've only found a few that i care about - http service name, a handful of paths, etc.14:55
cloudnulldolphm there are also init scripts, and a few others, but the bulk of our current roles should work.14:55
lbragstadso, the other part I was thinking about was being able to isolate distro specific plays in a distro specific role?14:55
dstanekall configuration stuff - so my playbooks are still dry14:56
dolphmlbragstad: let's keep both OS's all in one task file until it works, and then look to see if it makes sense to break it apart after14:56
lbragstaddolphm: ++ I agree with that14:56
palendaeIs there a spec for adding CentOS support to OSAD?14:57
sigmavirus24so14:57
sigmavirus24I would suggest the first spec should be to refactor OSAD to allow for distro-specific roles14:57
dolphmpalendae: no, this isn't OSAD14:58
sigmavirus24Then to add specs for specific distros14:58
dolphmpalendae: looking to deploy keystone to centos for public cloud14:58
dolphmsigmavirus24: ^14:58
sigmavirus24roger that14:58
lbragstadsigmavirus24: palendae based on the exiting keystone-deploy work which targets debian (we test with Travis) https://github.com/dolph/keystone-deploy14:59
palendaeGotcha14:59
cloudnulllbragstad dolphm dstanek Im quite fond of single role with conditional logic in the main tasks.14:59
cloudnullIE https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/os_nova/tasks/main.yml14:59
cloudnullanother example https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/os_nova/tasks/nova_compute.yml15:00
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add ubuntu backports repository to AIO if it's not present  https://review.openstack.org/17728415:00
dolphmcloudnull: ack15:00
cloudnullin that case centos vs ubuntu would == kvm vs qemu15:00
mancdazcloudnull not that I'm saying it's right or wrong, but that kind of logic was what people didn't like about rcbops chef cookbooks15:01
dolphmthose are both pretty elegant15:01
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672015:01
cloudnullmancdaz i'd argue that the osops_utils usage ontop of that kind of logic is what people didnt like about the chef cookbooks.15:01
palendaemancdaz: I haven't seen a solution that wasn't kinda dirty in any of the config management things15:01
dstanekcloudnull: i like having the playbooks be the recipe template and keeping the configuration is vars files15:02
palendaeI didn't like how puppet did it either15:02
mancdazcloudnull ok I should have said 'one of the things' :P15:02
cloudnull:-)15:02
mancdaza lot of the discussion was based around the fact that you should know what a role is going to do15:03
sigmavirus24mancdaz: since when were there things people didn't like about the chef cookbooks?15:03
mancdazif you want it to do something else, you have a different role15:03
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672015:03
mancdazactually role/role is not interchangeable between chef and ansible, but for the purposes of this15:03
cloudnullmancdaz this is true, but that would mean that roles would be broken up into os_nova_ubuntu os_nova_rhel etc..15:04
mancdazwell ok I missed the bit where this was about different oses15:04
lbragstaddolphm: are you leaning on way or the other?15:04
dstanekcloudnull: are things that different so that the vars trick won't work?15:04
mancdazI was looking at the nova example15:04
sigmavirus24cloudnull: would it be possible to do a conditional include based on the operating system inside the os_nova role?15:05
dolphmlbragstad: i think so - cram everything into one task file, then look at the platform differences and see how it makes sense to refactor into something like https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/os_nova/tasks/main.yml afterword15:05
cloudnulldstanek the task name are different between rhel and deb15:05
cloudnullsigmavirus24 yes15:05
mancdazin chef we used a platform hash that contained all the things15:05
cloudnullIE what packages are installed and how init systems work .15:05
lbragstaddolphm: cool, well in that case, I'll keep hacking on http://cdn.pasteraw.com/7zp564z3pqylyj7pniaovnyiuln32hz15:05
mancdazand then just populated that inside the cookbook depending on what platform you were running - is this approach not possible in ansible?15:06
dstanekmancdaz: that's the approach i was advocating15:06
lbragstadanother question I had, after we have one big playbook with tasks for both distros, how would we go about adding support for nginx versus apache and uwsgi versus mod_wsgi?15:06
galstromwe could use a case statement on the os platform.. then use a packages hash with top level keys of the os platforms..15:06
dstanekmancdaz:  see my two links from above15:06
cloudnulllbragstad what you can do is the conditional on the os for a particular included file. which would limit the use of things like  "when: ansible_os_family == "Debian""15:06
galstromthat lets you map package name differences between os's15:07
mancdazdstanek ah ok yeah15:07
cloudnulllbragstad ie https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/os_nova/tasks/nova_compute.yml#L16-L1715:07
cloudnullthen do all of the deb things in that one include or all of the rhel things in some other include.15:07
dolphmcloudnull: ++ we'll work towards that15:08
cloudnullgalstrom you stop your chef sillyness. :)15:09
galstromcloudnull :)15:09
galstromthat is how it is done sir15:09
cloudnulldistro names in a hash and conditional logic wrapped up in a syscall to ruby == winning15:10
*** sandywalsh has quit IRC15:10
cloudnullput a little osops_utils on top and an upstream mysql cookbook / gem and you have yourself a recipe for a good time.15:11
*** jwagner_away is now known as jwagner15:12
andymccrwho doesnt love a good time15:13
palendaechef's all about recipes for a good time15:13
palendaeWhy'd you guys get rid of good times?15:13
dstanekcloudnull: so in my case instead of using vars for the configuration i would move that logic into the task?15:14
*** yaya has quit IRC15:15
cloudnulldstanek in your case you could use both, include the vars based on the OS and then also conditionally do things based on the platform family. you'd have a common set of tasks that could be done on both platforms and conditional tasks.15:17
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment-specs: Add spec for BP implement-ceilometer  https://review.openstack.org/16941715:20
*** yaya has joined #openstack-ansible15:26
*** jlvillal has quit IRC15:31
*** sacharya has joined #openstack-ansible15:33
openstackgerritMerged stackforge/os-ansible-deployment: Updates for tag 10.1.4  https://review.openstack.org/17705015:34
openstackgerritJacob Wagner proposed stackforge/os-ansible-deployment-specs: added spec build-facts-archive  https://review.openstack.org/17702315:35
*** galstrom is now known as galstrom_zzz15:39
*** galstrom_zzz is now known as galstrom15:40
*** KLevenstein has quit IRC15:45
*** sdake has joined #openstack-ansible15:51
*** KLevenstein has joined #openstack-ansible15:52
matttodyssey4me: lol, the swift fix just failed on a heat issue15:53
sigmavirus24inconceivable15:53
odyssey4memattt bah, have you guys figured out the heat issue - is it transient?15:54
odyssey4meanother dependency failure?15:55
matttodyssey4me: i put in https://review.openstack.org/#/c/177241/, but it failed on the swift stuff15:56
matttwe probably need to bundle these together15:56
mattti thought your review was targetting kilo specifically15:57
matttodyssey4me: i'm going to update https://review.openstack.org/#/c/177284/ to bump saharaclient15:57
odyssey4memattt go for it15:57
odyssey4mewe have a successful build check for https://review.openstack.org/176720 mattt andymccr cloudnull palendae hughsaunders d34dh0r53 can we get some reviews please to unblock the gate for kilo, finally?16:01
odyssey4meit's still copying logs or something in zuul, in case you're wondering where the result logs are16:01
hughsaundersahh16:01
alextrcitiyHey, is master gate still blocked?16:02
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Add ubuntu backports repository to AIO if it's not present  https://review.openstack.org/17728416:02
matttalextrcitiy: yessir16:02
alextrcitiyAh. thanks16:02
odyssey4mealextrcitiy this patch is aiming to unblock master: https://review.openstack.org/17728416:04
alextrcitiyCool. I'll keep a close eye on it16:04
matttwhy do we keep rechecking things like https://review.openstack.org/176166 ?16:05
mattt:)16:05
odyssey4mehmm, it looks like the zuul status page is broken16:05
odyssey4mehaha mattt good question, I guess it's a habit :p16:06
*** galstrom is now known as galstrom_zzz16:06
matttafk for a bit16:06
andymccrwith that fix, do we have to bump the sha's and therefore have to do the swift fix at the same time?16:09
andymccrnm its already been approved16:09
odyssey4meandymccr master tracks master, so no sha's16:09
andymccrthis is kilo though16:10
sigmavirus24mattt: we keep rechecking it because we're optimists16:10
odyssey4meandymccr oh, that one - part of the reason for bumping the sha's is that the build wasn't working due to the requirements changes - so we can't pin mariadb on its own16:11
andymccrok - i mean ideally i would prefer the swift fix and the galera fix to be separate patches but if its not possible its not possible16:11
*** Mudpuppy has quit IRC16:12
odyssey4meI suppose that technically we could have not bumped the sha's for everything and only done the global requirements, but that would've meant another round of testing16:12
*** sandywalsh has joined #openstack-ansible16:13
odyssey4meyeah, if we had caught the galera issue sooner and got the patch in before horizon's libraries upped their versions, we would have had an easier time16:13
andymccrwell its done now so its purely academic discussing it. but 1:1 issue:PR ratio is how i would personally prefer it.16:13
odyssey4meandymccr yup, agreed :)16:13
odyssey4mewe need to try and respond more quickly next time16:13
sigmavirus24andymccr: I think that's how everyone would prefer it but in reality it isn't always possible =(16:14
andymccrsigmavirus24: i agree which is why im asking if it was possible - it felt like it might've been there16:14
andymccrbut that was before i saw it was approved already :P16:15
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Update for tag 9.0.8  https://review.openstack.org/17705116:16
sigmavirus24We should build a system that otter-approves patches16:16
hughsaundersotter?16:16
odyssey4meotrs?16:17
*** Mudpuppy has joined #openstack-ansible16:17
odyssey4mehaha cloudnull nice sneak-tweak :p16:17
sigmavirus24hughsaunders: bad reference to https://github.com/rackerlabs/otter16:17
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Removed hard coded package pinning for mariadb/galera  https://review.openstack.org/17725916:18
hughsaundersokays16:18
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Update for tag 9.0.8  https://review.openstack.org/17705116:18
sigmavirus24hughsaunders: you don't have to like the joke, you just have to laugh16:18
cloudnullthere we go.16:18
cloudnulli dep'd one on the other.16:18
cloudnullicehouse has convergence issues and i think we can safely affirm that the ssh retry is not enough.16:20
*** javeriak has joined #openstack-ansible16:20
odyssey4mecloudnull yep, for icehouse especially16:21
odyssey4mewe don't seem to have the same reliability issues for kilo16:21
*** javeriak has quit IRC16:21
cloudnullnope16:21
*** daneyon_ has joined #openstack-ansible16:22
*** galstrom_zzz is now known as galstrom16:22
*** KLevenstein has quit IRC16:24
*** daneyon has quit IRC16:25
hughsaunders"fatal: [node07_rsyslog_container-55585dda] => SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh" QQ16:33
*** javeriak has joined #openstack-ansible16:33
* hughsaunders contemplates putting ssh_retry into jenkins-rpc16:33
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add basic orchestration tests to the gate check  https://review.openstack.org/17616616:36
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716016:36
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment: Implement Ceilometer[WIP]  https://review.openstack.org/17306716:36
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Make script executable and BSD sed compatible  https://review.openstack.org/17711516:36
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17665716:37
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Set external roles to import into ansible namespace  https://review.openstack.org/17713116:37
cloudnull^ updated dep to ensure the repo/req bump is in place.16:39
cloudnullhughsaunders thats not a bad idea for the jenkins-rpc sy stem16:40
cloudnull*system16:40
cloudnullsigmavirus24 andymccr https://review.openstack.org/#/q/owner:%22Ian+Cordasco%22+status:open+project:stackforge/os-ansible-deployment,n,z <- do you guys have a consensus on the glance patches  ?16:42
sigmavirus24other than the ones failing?16:42
sigmavirus24oh yeah, I need to update those16:42
sigmavirus24sorry, got side tracked yesterday16:42
* sigmavirus24 heads off to fix the glance patches16:43
cloudnullnp. i didn't add the dep there because those patches were -1 on cr16:43
andymccrcloudnull: i think the sha bump can be abandoned, its already been applied in a separate patch16:43
cloudnull +116:43
andymccrand the others are a good solution to the problem so once thats fixed up its good to go.16:43
andymccror at least a better solution to the problem (in my opinion)16:43
cloudnullokiedokie.16:47
cloudnullthanks andymccr  sigmavirus2416:47
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Set gerrit default branch to kilo  https://review.openstack.org/17624616:49
sigmavirus24andymccr: before you hop off, do we want to stagger the times the cron job runs or should we just do */6?16:51
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17717216:51
* odyssey4me feeds zuul some more red bull and a jalapeno for a little extra fire16:51
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add basic orchestration tests to the gate check  https://review.openstack.org/17702116:52
andymccrsigmavirus24: hmm...16:52
sigmavirus24because */6 means every 6 hours16:52
andymccryeh16:52
sigmavirus24which is what we really wanted16:52
sigmavirus24and changing the granularity is simpler that way than generating the comma-separated list16:52
andymccrdoes it matter if the image cache pruner runs at the same time on each host?16:52
andymccryoure gonna get round robin balanced to those nodes anyway16:52
sigmavirus24andymccr: I'm not sure to be honest16:53
*** sdake has quit IRC16:53
odyssey4meandymccr sigmavirus24 maybe use ansible to randomise the minute in the cron job?16:53
odyssey4meso something like running it every 5 hours and <random> minutes16:54
andymccrimo simpler is better and i cant think of a reason why you'd need to have them run at diff times per host.16:54
andymccrsure that'd work16:54
sigmavirus24sounds good to me16:54
odyssey4memaybe the random should be between 40 and 60 or something like that16:54
openstackgerritMerged stackforge/os-ansible-deployment: Add release pinning to galera roles  https://review.openstack.org/17672016:56
cloudnullyay! kilo is now unblocked.16:58
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17636816:59
cloudnullcan we make this go https://review.openstack.org/#/c/177163/17:00
cloudnull^ odyssey4me d34dh0r53 palendae hughsaunders17:00
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17637017:00
sigmavirus24odyssey4me: didn't realize that you suggested between 40 and 6017:01
sigmavirus24right now it's going between 0 and 59 I believe17:01
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17636517:04
*** yaya has quit IRC17:05
odyssey4mecloudnull I take it that https://review.openstack.org/177163 is essential in some way - how tested is it?17:09
*** britthouser has joined #openstack-ansible17:10
cloudnulli cant say that its been really put through its paces in overall testing but as it relates to the bug raised by rax support it should limit issues in contract tables .17:11
cloudnullfrom https://bugs.launchpad.net/openstack-ansible/+bug/144136317:11
openstackLaunchpad bug 1441363 in openstack-ansible trunk "nf_conntrack schould be unloaded on swift object server" [Medium,In progress] - Assigned to Andy McCrae (andrew-mccrae)17:11
cloudnullApsu if you could comment on the review  https://review.openstack.org/177163  it'd be much appreciated.17:11
odyssey4mecloudnull actually I remember implementing this some time ago - at least I think it was this.17:12
*** sdake has joined #openstack-ansible17:12
*** britthou_ has quit IRC17:12
odyssey4mewe still have master failures: https://review.openstack.org/17728417:14
odyssey4mebah ssh failure17:14
cloudnullwe could enable successerator for 1 retry ? but its kinda inevitable until we land ssh_retry upstream17:17
odyssey4mecloudnull it's so very rare though, and doing the retries more often ends up in masking issues17:17
cloudnullit does17:17
cloudnullhughsaunders whats the state of that upstream patch ? any movement ?17:18
odyssey4mehappy for that for icehouse/juno because they're relatively mature - but for kilo/master I'm definitely against17:18
cloudnull++ for sure.17:18
odyssey4mecloudnull hughsaunders it may be prudent to try and submit a similar PR for ansible 2 as well as 1.9; that way it may merge in 2 sooner :)17:18
cloudnull+117:19
odyssey4methis is assuming they have differing branches or something17:19
odyssey4mecloudnull it's a bit disconcerting to see the failures from the external CI17:22
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Implement Ceilometer[WIP]  https://review.openstack.org/17306717:22
cloudnullodyssey4me failure in # /usr/local/bin/pip install heat17:24
cloudnullwhich is one of our fixes.17:24
odyssey4mecloudnull on which one?17:24
cloudnullhttp://jenkins.propter.net/job/commit-multinode/648/consoleText17:24
odyssey4mecloudnull ah, but the multinode uses the rpc-mirror as I recall17:24
odyssey4medon't you need to rebuild the master repo there with the update?17:25
cloudnullyes i will once https://review.openstack.org/#/c/177284/4/playbooks/vars/repo_packages/openstack_clients.yml is in17:25
odyssey4meI might be wrong :p17:25
cloudnullit also dosent look like the external ci can process dependent changes.17:26
cloudnullhughsaunders? mattt ?17:26
odyssey4mecloudnull you may wish to check which patch set it's reporting on17:27
odyssey4meit doesn't cancel when a new patch set is uploaded17:27
cloudnullah. maybe thats it17:27
cloudnullicehouse success https://review.openstack.org/#/c/177259/ <- typie typie make it go17:30
odyssey4med34dh0r53 mattt andymccr https://review.openstack.org/177259 make the go!17:31
andymccrodyssey4me:  say please17:32
odyssey4mehughsaunders palendae ^17:32
andymccrahahahaha17:32
odyssey4meandymccr with beer on top :p17:32
andymccrMANNERS SIR17:32
odyssey4mewhat manner of people are we, working on a friday night?17:32
andymccrthe best. arrounnndd17:34
cloudnullandymccr :pretty please ?!17:34
andymccrcloudnull: i wanted it from odyssey4me :P17:34
odyssey4mecloudnull already done :p17:34
cloudnulloh, in that case GTY17:34
cloudnull:D17:34
andymccrhahaha17:34
andymccrhttps://www.youtube.com/watch?v=VIYqtkdMxQg17:35
odyssey4menow cloudnull will need to beg for https://review.openstack.org/17705117:35
andymccrlgtm if it passes gate17:35
cloudnullandymccr +900017:36
odyssey4meandymccr yeah, it seems we'll see that shortly17:36
cloudnullyour the best around!17:36
andymccrthats a song written about os-a-d17:37
cloudnullhttps://www.youtube.com/watch?v=oomCIXGzsR017:37
odyssey4meand that one's on the way too now :)17:37
Apsucloudnull: Just got back from lunch. I'll take a look-see17:37
Apsucloudnull: Done and doner.17:40
cloudnulltyvm!17:40
ApsuYou bet17:41
odyssey4mesigmavirus24 have you finalised your glance cron patches yet?17:44
stevelleam I going to need to base any changes in master on https://review.openstack.org/#/c/177284/ (add backports repo) in order to get through the gate right now?17:58
odyssey4mestevelle yep18:00
sigmavirus24odyssey4me: A) I thought you were leaving. B) No one concretely said to restrict the range from which the minute could be randomly selected18:00
stevelleI'll just hold that horizon change then18:01
openstackgerritMerged stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716318:02
odyssey4mesigmavirus24 I'm barely here, just waiting for https://review.openstack.org/177284 to gate18:02
odyssey4mealright, https://review.openstack.org/177284 is passed - just needs another +2+w to commit18:05
odyssey4mecloudnull anyone else still around?18:05
odyssey4meandymccr ^ ?18:05
cloudnulld34dh0r53 ^18:05
d34dh0r53on it18:06
*** sandywalsh has quit IRC18:06
d34dh0r53Wherenow.org CI is now voting?18:07
stevelleyes18:07
odyssey4med34dh0r53 only for code review, and it's only working properly on some branches18:07
odyssey4meit seems to be broken on master, and not responding to kilo18:07
d34dh0r53ahh18:07
cloudnulland its only cr voting.18:08
*** britthou_ has joined #openstack-ansible18:08
odyssey4meit's set to vote +1/-1 whereas it previously was only set to vote +1 or nothing18:08
*** sandywalsh has joined #openstack-ansible18:08
d34dh0r53cool, when did it change?18:08
odyssey4med34dh0r53 during the course of today - around lunch time UK I think18:09
d34dh0r53👍18:09
*** britthouser has quit IRC18:09
*** erikmwilson is now known as Guest885318:11
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17636518:11
*** erikmwilson_ has joined #openstack-ansible18:11
cloudnullsigmavirus24 updated dep so that the job will gate on https://review.openstack.org/#/c/176365/18:12
cloudnulljust so you know.18:12
sigmavirus24Thanks18:12
d34dh0r53Thanks to both of you18:12
sigmavirus24opinions on whether the random selection should be from [0, 59] or [40, 59]?18:12
d34dh0r53for being you18:12
*** KLevenstein has joined #openstack-ansible18:12
sigmavirus24d34dh0r53: thank you for being a random location in memory =P18:12
stevelle[0, 59]18:13
d34dh0r53sigmavirus24: I would actually do [1,59] as 0 will be a default for some jobs18:13
odyssey4mesigmavirus24 no strong opinion either way - I was basing the partial restriction based on your original set time18:13
sigmavirus24d34dh0r53: good point. *starts condorcet poll to see if d34dh0r53's suggestion would win*18:14
d34dh0r53lol18:14
stevellefwiw [0,59] is the same as [0,14] for these purposes because you're going to run every 15 minutes, right?18:14
stevelle[1,59] just gives a slightly lower chance of not running a cycle on the hour18:14
odyssey4mestevelle every 6 hours as I recall18:15
sigmavirus24stevelle: every 5 hours and a random number of minutes18:15
stevellecorrected: thats what I get for reading code at 3am18:15
sigmavirus24so 5h random(1, 59)18:16
sigmavirus24If no one objects to [1, 59], then I'm going to update the patches with that18:17
odyssey4mesigmavirus24 not me18:17
odyssey4me+118:17
sigmavirus24And just to check my own Friday afternoon reading comprehension skills, http://docs.ansible.com/playbooks_filters.html#random-number-filter means that {{ 59 |random(start=1) }} would be what we want, correct?18:22
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Bump the tempest defcore repository version to master  https://review.openstack.org/17498318:23
openstackgerritMerged stackforge/os-ansible-deployment: Removed hard coded package pinning for mariadb/galera  https://review.openstack.org/17725918:27
openstackgerritMerged stackforge/os-ansible-deployment: Update for tag 9.0.8  https://review.openstack.org/17705118:34
matttFINALLY18:36
matttFINALLY18:36
*** jlvillal has joined #openstack-ansible18:42
sigmavirus24mattt: go home18:43
cloudnullpeoples if your around, love pushing buttons, and reading code https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z <- there are lots of master / kilo related reviews that need some reviewers :)18:48
*** galstrom is now known as galstrom_zzz18:49
*** alextrcitiy has quit IRC18:53
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17636518:55
*** erikmwilson_ is now known as erikmwilson18:55
openstackgerritMerged stackforge/os-ansible-deployment: Add ubuntu backports repository to AIO if it's not present  https://review.openstack.org/17728418:57
*** daneyon has joined #openstack-ansible18:58
openstackgerritMerged stackforge/os-ansible-deployment: Add basic orchestration tests to the gate check  https://review.openstack.org/17616618:58
*** daneyon_ has quit IRC18:59
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17637019:04
d34dh0r53rabbit on gate seems to be failing a lot today19:05
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated icehouse for new dev work  https://review.openstack.org/17738419:06
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17636819:09
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Update Horizon configuration  https://review.openstack.org/17738619:13
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated icehouse for new dev work  https://review.openstack.org/17738419:15
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated juno for new dev work  https://review.openstack.org/17738819:15
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated juno for new dev work  https://review.openstack.org/17738819:17
stevelleI presume the fact that this task no longer exists in kilo/master is intentional https://github.com/stackforge/os-ansible-deployment/blob/juno/rpc_deployment/roles/container_archive/tasks/main.yml19:44
stevelleplease correct me if I'm wrong19:44
Sam-I-Amcloudnull: ^ o master ptl19:46
bgmccollumRe MaaS rabbitmq_status.py, any plans to make CLUSTERED and CLUSTER_SIZE dynamic?19:55
bgmccollumits hard coded to True and 3 respectively. Which causes alerts for any environments that don't meet those criteria.19:55
bgmccollumbug already reported...thanks19:57
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Update Horizon configuration  https://review.openstack.org/17738620:02
openstackgerritMerged stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17716020:06
*** nosleep77 has joined #openstack-ansible20:11
sigmavirus24stevelle: still trying to understand what relation https://bugs.launchpad.net/bugs/1439905 has to 17738620:17
openstackLaunchpad bug 1439905 in OpenStack Dashboard (Horizon) "[Launch Instance Fix] Show Admin Password" [Medium,In progress] - Assigned to Shaoquan Chen (sean-chen2)20:17
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17743420:17
sigmavirus24mattt: stop working20:17
stevellesigmavirus24: s/177386/177388/ ?20:19
stevelleerr nm I pasted wrong place20:19
stevellesigmavirus24: this is the basis of relation: https://github.com/openstack/horizon/commits/stable/kilo/openstack_dashboard/local/local_settings.py.example20:20
sigmavirus24Launchpad is failing at showing that commit (given the only two that are linked are either a different bug or unmerged)20:23
sigmavirus24Sorry for the hassle20:23
stevelleI see that the commit is not linked now.20:26
stevellehad overlooked that20:26
sigmavirus24Yeah20:32
sigmavirus24The reviews that are linked by jeepyb didn't seem related to local_settings.py.example which is why I was thoroughly confused20:33
*** javeriak has quit IRC20:33
*** KLevenstein has quit IRC20:37
*** KLevenstein__ has joined #openstack-ansible20:38
*** KLevenstein__ is now known as KLevenstein20:38
matttsigmavirus24: figured i'd do a backport while i go up and down a million times trying to get my daughter to sleep :)20:47
openstackgerritMerged stackforge/os-ansible-deployment: Set tcp_tw_reuse for swift storage hosts  https://review.openstack.org/17717220:53
openstackgerritMerged stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17665720:57
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17743420:59
*** sacharya has quit IRC21:00
*** britthou_ has quit IRC21:01
*** sdake_ has joined #openstack-ansible21:04
*** Mudpuppy_ has joined #openstack-ansible21:05
*** Mudpuppy_ has quit IRC21:07
*** Mudpuppy_ has joined #openstack-ansible21:07
*** sdake has quit IRC21:08
*** Mudpuppy has quit IRC21:08
*** KLevenstein has quit IRC21:14
*** sdake has joined #openstack-ansible21:19
*** sdake_ has quit IRC21:23
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Lower PyYAML requirement to satisfy Heat  https://review.openstack.org/17746721:44
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17743421:47
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Lower requirements pins to satisfy global-requirements  https://review.openstack.org/17746721:50
*** stevemar has quit IRC21:53
sigmavirus24mancdaz: cloudnull https://review.openstack.org/177467 is the final list of our pins that needed to be changed to satisfy stable/juno g-r21:54
*** javeriak has joined #openstack-ansible22:05
*** sdake_ has joined #openstack-ansible22:11
*** sdake has quit IRC22:15
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Update Horizon configuration  https://review.openstack.org/17747322:17
*** mnestheu1 has quit IRC22:19
*** sdake has joined #openstack-ansible22:23
*** sdake_ has quit IRC22:27
*** sdake_ has joined #openstack-ansible22:53
*** sdake__ has joined #openstack-ansible22:55
*** sdake has quit IRC22:56
*** sdake_ has quit IRC22:59
*** Mudpuppy_ has quit IRC23:05
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Run the glance cache cron jobs more frequently  https://review.openstack.org/17637023:07
openstackgerritMerged stackforge/os-ansible-deployment: Set gerrit default branch to kilo  https://review.openstack.org/17624623:15
*** sigmavirus24 is now known as sigmavirus24_awa23:25
openstackgerritMerged stackforge/os-ansible-deployment: Add package list and repos to AIO diagnostics  https://review.openstack.org/17743423:50
openstackgerritMerged stackforge/os-ansible-deployment: Update Horizon configuration  https://review.openstack.org/17747323:50
openstackgerritMerged stackforge/os-ansible-deployment: Add basic orchestration tests to the gate check  https://review.openstack.org/17702123:50
*** sdake__ has quit IRC23:52

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