Tuesday, 2015-09-08

*** shoutm has quit IRC00:18
*** sdake has joined #openstack-ansible00:18
*** shoutm has joined #openstack-ansible00:21
*** waded_ has joined #openstack-ansible01:12
*** waded has quit IRC01:12
*** galstrom_zzz is now known as galstrom01:15
*** shoutm has quit IRC01:23
*** shoutm has joined #openstack-ansible01:28
*** galstrom is now known as galstrom_zzz01:33
*** shoutm has quit IRC01:48
*** shoutm has joined #openstack-ansible01:50
*** prometheanfire has quit IRC01:58
*** woodard has joined #openstack-ansible02:01
*** woodard has quit IRC02:05
*** Mudpuppy has quit IRC02:13
*** palendae_ is now known as palendae02:39
*** galstrom_zzz is now known as galstrom02:51
*** shoutm_ has joined #openstack-ansible02:53
*** galstrom is now known as galstrom_zzz02:53
*** shoutm has quit IRC02:54
*** shoutm_ has quit IRC03:03
*** shoutm has joined #openstack-ansible03:03
*** Mudpuppy has joined #openstack-ansible03:14
*** shoutm_ has joined #openstack-ansible03:22
*** shoutm has quit IRC03:24
*** persia has quit IRC03:30
*** persia has joined #openstack-ansible03:32
*** prometheanfire has joined #openstack-ansible03:39
*** skamithi12 has joined #openstack-ansible03:39
*** skamithi12 has left #openstack-ansible03:43
*** shoutm_ has quit IRC03:46
*** shoutm has joined #openstack-ansible04:03
*** shoutm_ has joined #openstack-ansible05:31
*** shoutm has quit IRC05:34
*** javeriak has joined #openstack-ansible06:12
*** mattoliverau has quit IRC06:13
*** mattoliverau has joined #openstack-ansible06:14
*** javeriak has quit IRC06:17
*** Mudpuppy has quit IRC06:17
*** Mudpuppy has joined #openstack-ansible06:47
*** Mudpuppy has quit IRC06:52
*** javeriak has joined #openstack-ansible08:13
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment-specs: Add Liberty Release spec  https://review.openstack.org/22118908:17
*** javeriak has quit IRC08:21
git-harryodyssey4me: what is the impact of this - https://bugs.launchpad.net/openstack-ansible/+bug/148735308:52
openstackLaunchpad bug 1487353 in openstack-ansible trunk "MySQL host address is not set properly for all .my.cnf files" [Low,In progress] - Assigned to Jesse Pretorius (jesse-pretorius)08:52
*** gparaskevas has joined #openstack-ansible08:53
odyssey4megit-harry the impact is that operators can't access galera as they expect to - it's also a change of behavior from juno to kilo09:07
odyssey4meie juno had the ip set correctly, kilo does not09:08
git-harryodyssey4me: okay, so it has no impact on the actual services09:10
odyssey4megit-harry nope - all the services use the ansible module with the host set as an arg09:12
evrardjphello everyone09:14
evrardjpI was trying to improve my storage performance this morning, and I grepped mtu on the os-ansible-deployment repo09:14
evrardjpI've seen there was an option to set container's mtu (container_mtu)09:15
evrardjpbut I don't see anything that uses that, except lxc creation (so, there is no configuration of the os with that)09:15
evrardjpis that normal?09:15
evrardjpnever tried it before09:15
evrardjpI also remember that it was a pain to move on the hosts from a standard 1500 mtu to a 9000 mtu, someone has advices? scripts in /etc/network/interfaces?09:17
evrardjpit was not so simple as adding mtu in /etc/network/interfaces, with bridges09:18
odyssey4meevrardjp as I recall you have to ensure that the entire chain of dependencies has the right mtu09:27
evrardjpindeed09:27
evrardjpthe last part of my chain is the host and the container09:27
odyssey4meand you have to use post-up in most cases because the mtu doesn't properly apply on bridges with the simple mtu config option in /interfaces09:27
evrardjpthe host causes my pain, and the container I didn't try09:27
evrardjpodyssey4me: that's exactly what I meant by "the host causes my pain"09:28
evrardjp;)09:28
evrardjpshould I stop trying?09:28
odyssey4methe only places where it may be important to do this is for the vxlan interfaces - neutron container and compute hosts I think09:29
odyssey4mebut sometimes you may wish to do it for your storage networks too09:29
evrardjpwould you care to explain me more?09:29
evrardjpI guess that there is an impact of encapsulation09:29
evrardjpbut I'm sure if there is a performance impact09:29
evrardjpwhat I mean is, yes if you don't pay attention, the system won't work09:30
odyssey4meyes, for vxlan due to the encapsulation and the fact that vm's typically have 1500 mtu set09:30
evrardjpbut I'm not sure that increasing mtu will increase performance of vxlans09:30
evrardjpso your advise is to change that default value09:30
odyssey4melinux vm's generally behave quite well if you set a lower mtu value for the dnsmasq service09:31
evrardjpand define container_mtu09:31
evrardjpok09:31
odyssey4mebut not all operating systems listen to that09:31
evrardjpok09:31
evrardjpso you don't advise to change the mtu at all, or at least not increase it09:31
evrardjpfor at least linux OSes guested in the cloud09:31
odyssey4mewindows ignores it, so if your network mtu is 1500 and you therefore need the vm's to have a lower mtu - you'd have to hard set it in the images09:31
evrardjpok09:32
odyssey4methe vxlan network mtu increase is simply to alleviate that issue - not for performance09:32
odyssey4meit's to allow the vm's and virtual networks to use an mtu of 1500, meaning you deal with less support calls09:32
odyssey4methe alternative is to ensure that every image you provide has the default mtu set to 1452 (I think that's the max value) to accommodate the vxlan encapsulation09:33
evrardjpI don't see a problem for setting a larger mtu, but it need to work... and for your last concern, I'm afraid that neutron isn't configured to take the extra bytes I put on my mtu09:34
evrardjpso I guess it's better to stick to 150009:35
evrardjpeverywhere, except for vms -> 145209:35
evrardjpthanks for the info09:36
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Set the Ubuntu mirror used based on the environment  https://review.openstack.org/21861109:38
odyssey4meevrardjp once you've worked it out, it seems to me that this may be a useful documentation entry :)09:39
evrardjp:)09:41
*** sdake has quit IRC09:42
git-harryodyssey4me: does anyone use teardown.sh?09:49
*** jlvillal has quit IRC09:50
*** jlvillal has joined #openstack-ansible09:50
matttgit-harry: yeah, because we have an open review for it atm09:50
git-harrymattt: yeah, I sort of referring to that.09:50
git-harryThe script seems like a bad idea in general. I'd argue it should just be deleted09:51
git-harryIt seems it's just easier to rebuild09:51
*** skamithi12 has joined #openstack-ansible09:53
odyssey4megit-harry yes, apparently some people do - it's seen as a way to re-do a lab without rekicking09:54
odyssey4mewhen you're dealing with hardware labs, a rebuild takes a lot of time - teardown is built for that scenario09:54
*** gparaskevas has quit IRC09:54
odyssey4meit's known that it's not perfect, but it's better than nothing09:55
git-harryodyssey4me: I think nothing would be better09:55
*** shoutm_ has quit IRC09:57
skamithi12odyssey4me:  gm. ready to talk about deployment through vagrant.10:02
skamithi12changing the license on the project now as the first step to apache10:03
odyssey4meskamithi12 welcome! :)10:03
evrardjpgit-harry: I'm using it10:05
evrardjpI was using my own script that was destroying the containers before10:05
evrardjpteardown is just another way to do it10:06
skamithi12odyssey4me: license on the project changed.  i looked at an example blueprint https://blueprints.launchpad.net/openstack-ansible/+spec/remove-upstream-repo-dependency is this the kind of format i should follow or you had something else in mind?10:11
odyssey4meskamithi12 so your blueprint has already been registered: https://blueprints.launchpad.net/openstack-ansible/+spec/deploy-with-vagrant10:12
odyssey4mehave you configured gerrit yet?10:12
odyssey4meie configured 'git review'10:12
skamithi12no not yet.10:12
openstackgerritMerged stackforge/os-ansible-deployment: Remove double register in swift handlers  https://review.openstack.org/22044910:13
odyssey4meok, to put the spec together and submit it you'll need to do that10:13
odyssey4melet me give you a basic overview of the process10:13
odyssey4meskamithi12 under 'submitting code' there are some guiding bits which you should ideally work through and understand: https://github.com/stackforge/os-ansible-deployment/blob/master/CONTRIBUTING.rst10:14
evrardjpgit-harry: why do you prefer "nothing" instead of teardown? If some stuff are not correctly cleaned, then it's maybe time to register a bug? :d10:14
odyssey4meskamithi12 the spec repo is here: https://github.com/stackforge/os-ansible-deployment-specs10:15
odyssey4meskamithi12 https://github.com/stackforge/os-ansible-deployment-specs/blob/master/specs/template.rst is the template for the spec that you'll need to copy and edit10:16
odyssey4meeveryone, meet skamithi12 who'll be working on https://blueprints.launchpad.net/openstack-ansible/+spec/deploy-with-vagrant to bring his work on deploying openstack-ansible with vagrant into the project :)10:18
matttskamithi12: hey there!  thanks in advance for your work here :)10:19
evrardjphello skamithi12 :)10:19
odyssey4memancdaz with regards to https://bugs.launchpad.net/openstack-ansible/+bug/1491882 we saw that some time ago with neutron on compute nodes as I recall10:20
openstackLaunchpad bug 1491882 in openstack-ansible "some services don't deploy cleanly on bare_metal if there are other services on same host" [Undecided,New]10:20
odyssey4meI can't remember how it was resolved, but it seems that the conversion of cinder_volume to default to on_metal has left that as a new issue.10:21
evrardjpskamithi12: good luck with vagrant-libvirt then :)10:21
git-harryevrardjp: teardown scripts on complicated systems such as this are hard to maintain and generally get little attention. For testing they are not a fair test when compared to a new build and I've personally been bitten too many times in the past from this type of cleanup script.10:21
evrardjpyup I understand10:22
*** jlvillal has quit IRC10:22
evrardjpgit-harry: but it's not that hard with our lxc system, just destroying every container is easy10:22
skamithi12mattt, evrardjp: thx.  i don't like virtualbox, but would love a Vagrantfile using virtualbox. a colleague at work is working on developing a vagrant plugin where you give a graphviz file and it spits out a vagrantfile in virtualbox format or libvirt format.10:22
skamithi12not sure how soon his work will be opensourced10:22
evrardjpskamithi12: same, don't like virtualbox but I have been bitten by vagrant-libvirt in the past... so having some ppl generating the good tools for it is really great10:24
git-harryevrardjp: yes, a lot of the configuration is done in containers and that helps but there is still a significant numbers of changes that are made to the hosts. I don't use the teardown.sh script myself so in that sense I'm not impacted. I was wondering if anyone else used it because if not it would be easier just to remove.10:24
openstackgerritHugh Saunders proposed stackforge/os-ansible-deployment: Remove double register in swift handlers  https://review.openstack.org/22123710:24
evrardjpso to answer your question git-harry, Until I have my testlab hosted in openstack, I'll continue to use teardown.sh ;)10:25
evrardjpthen I'll probably won't care anymore10:26
mancdazodyssey4me yes, that's that same bug, only for cinder10:28
skamithi12evrardjp: the latest master branch of libvirt-vagrant has stable libvirt isolated network support, so building isolated bridges, like I do in vagrant-osad project is rock solid.  I'm adding libvirt/QEMU udp unicast tunnel support to vagrant-libvirt this week, for stable point to point VM connections in case someone wants to go to the next level and add switches like cumulus linux/junos.  i'll have a blog post about it soon10:33
skamithi12n linuxsimba.com/vagrant.html. libvirt just got the patch last week thx to another colleague of mine.  http://libvirt.org/git/?p=libvirt.git;a=commit;h=5c668a78d85b0d71e6ac8e23f2c605058b44df65. I have a ppa for this if you run Ubuntu 14.04.10:33
evrardjpnice10:34
evrardjpworking for cumulus? interesting :D10:35
skamithi12evrardjp:  yes i do. do alot of network testing in virtual env. networking is growing up..becoming more like regular devops.10:37
*** shoutm has joined #openstack-ansible10:39
evrardjp:)10:39
*** gparaskevas has joined #openstack-ansible10:40
evrardjpthere will be plenty of work to do relative to osad... whether it's integrating and testing some components or simply have additional playbooks outside osad with roles to install additional software10:40
evrardjpa bright future :)10:40
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: include cinder_all group vars file in cinder-common playbook  https://review.openstack.org/22124210:43
mancdazandymccr odyssey4me https://review.openstack.org/#/c/221242/110:44
mancdazodyssey4me andymccr just in case this becomes something that needs to be fixed for upgrades10:44
mancdazeven though in most deployment scenarios, cinder-volumes will be on it's own host10:44
skamithi12evrardjp: i'm still learning openstack, is there a irc channels where openstack operators hang out. want to learn how how ppl manage openstack and then see how i can help improve openstack network troubleshooting.10:45
openstackgerritMerged stackforge/os-ansible-deployment: Updated juno for new dev work - 3 Sep 2015  https://review.openstack.org/22015110:46
skamithi12odyssey4me: signed up on reviews.openstack.org10:47
skamithi12read the coding guidelines and template.rst.  anything else i need to review?10:48
*** Mudpuppy has joined #openstack-ansible10:49
*** Mudpuppy has quit IRC10:54
*** jlvillal has joined #openstack-ansible11:03
odyssey4memancdaz ah yes, that's it :)11:08
*** javeriak has joined #openstack-ansible11:10
odyssey4meskamithi12 if you have that ready then you can clone the specs repo, checkout a branch to add your spec and git review it so that we can all take a look at your proposed changes11:10
odyssey4meskamithi12 operators typically hang out in #openstack11:11
*** javeriak has quit IRC11:13
*** javeriak has joined #openstack-ansible11:24
openstackgerritMerged stackforge/os-ansible-deployment: Set client versions deployed to use global requirements  https://review.openstack.org/22004911:24
openstackgerritMerged stackforge/os-ansible-deployment: Update master for liberty-3 testing  https://review.openstack.org/22050411:24
*** skamithi12 has quit IRC11:37
git-harryhughsaunders: https://review.openstack.org/#/c/218354/11:42
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: include cinder_all group vars file in cinder-common playbook  https://review.openstack.org/22124211:44
*** cloudtrainme has quit IRC12:03
*** javeriak has quit IRC12:04
*** javeriak has joined #openstack-ansible12:07
*** markvoelker has joined #openstack-ansible12:19
*** markvoelker has quit IRC12:20
*** markvoelker has joined #openstack-ansible12:20
*** woodard has joined #openstack-ansible12:25
*** tlian has joined #openstack-ansible12:32
*** tlian has quit IRC12:32
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: include cinder_all group vars file in cinder-common playbook  https://review.openstack.org/22124212:32
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: include cinder_all group vars file in cinder-* playbooks  https://review.openstack.org/22124212:33
*** tlian has joined #openstack-ansible12:37
*** shoutm has quit IRC12:39
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825912:46
odyssey4mecloudnull it appears that keys.gnupg.net does not serve keys properly via port 80, so I've switched the key server to ubuntu's which appears to work in https://review.openstack.org/17825912:48
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825912:51
mgariepygood morning everyone12:51
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825912:52
*** Mudpuppy has joined #openstack-ansible12:58
*** Mudpuppy has quit IRC12:59
*** spotz_zzz is now known as spotz12:59
*** Mudpuppy has joined #openstack-ansible13:00
*** KLevenstein has joined #openstack-ansible13:05
hughsaundersif using a flat network for public, and not aio, br-vlan-veth <--> eth12 (or whatever the container inteface is called) needs to be created manually on compute hosts?13:07
odyssey4megood morning mgariepy :)13:07
mgariepyhow was your weekend ?13:08
odyssey4memgariepy pretty good - kept away from work and relaxed :)13:10
*** woodard has quit IRC13:11
mgariepyyou do that ? i though you were working 24/7 ;p13:11
hughsaundersmgariepy: this is progress for odyssey4me :)13:15
*** woodard has joined #openstack-ansible13:15
mgariepyhehe ;)13:16
odyssey4memgariepy I go through obsessive phases. :p13:19
mgariepyfollowing the moon ?13:20
hughsaundersodyssey4me is waning13:20
odyssey4mehahahaha13:20
*** pradk has joined #openstack-ansible13:22
odyssey4memancdaz build success! https://review.openstack.org/221242 andymccr are you happy with the final implementation?13:27
andymccrodyssey4me: that one worked for me!13:30
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825913:31
odyssey4meandymccr great :) now I have to wonder whether the issue also counts for kilo and above?13:32
andymccrodyssey4me: nope shouldnt count for kilo13:32
andymccrwe would've run into it for certain if it did13:32
andymccrbecause cinder is now on metal :)13:32
andymccrand an aio would definitely hit that problem13:32
andymccrwe changed teh structure of our vars though13:33
andymccr*the13:33
odyssey4mecool - will mark as invalid as I suspected that the vars structure change makes that a non-issue13:33
*** kerwin_bai has joined #openstack-ansible13:33
openstackgerritMerged stackforge/os-ansible-deployment: Used named veth pairs that match container  https://review.openstack.org/21945713:34
openstackgerritMerged stackforge/os-ansible-deployment: Add galera_address to all playbooks installing galera_client  https://review.openstack.org/20793913:34
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add galera_address to all playbooks installing galera_client  https://review.openstack.org/22130113:37
*** skamithi13 has joined #openstack-ansible13:45
*** javeriak has quit IRC13:48
*** mrstanwell has joined #openstack-ansible13:57
*** javeriak has joined #openstack-ansible13:57
*** galstrom_zzz is now known as galstrom13:58
odyssey4memiguelgrinberg when you're in, if you have a gap - can you take a look at https://review.openstack.org/218184 and try to figure out why it's not working properly, then revise the patch to make it work13:59
odyssey4memiguelgrinberg I could be lazy and just make it use the openstack client for everything, but I think we need to fix that - feel free to make the patch your own14:00
javeriakguys, need a little help, one of my infra's continously errors out on ansible ssh, after the Flush net cache task14:06
*** cloudtrainme has joined #openstack-ansible14:07
*** galstrom is now known as galstrom_zzz14:11
*** sigmavirus24_awa is now known as sigmavirus2414:11
*** cloudtrainme has quit IRC14:11
cloudnullmorning14:14
odyssey4mejaveriak are you deploying from a tag, or branch?14:16
odyssey4mewhat was your last commit in the log?14:16
javeriakodyssey4me, HEAD kilo14:16
odyssey4mejaveriak and your last commit?14:17
javeriak"Merge "Additional retries for ssh wait check" into kilo"14:17
odyssey4mejaveriak are you working with old-ish hardware or something?14:18
odyssey4memaybe highly contended virtual environment?14:18
javeriakby oldish do you mean if the OS is new, then nope, i cleaned up a juno deployment before this on it14:19
javeriakodyssey4me, no the hardware is server grade, not having a problem with of my other machine, just the one, and even with that just the memcached container14:19
odyssey4meif so, you may wish to try setting ssh_delay to a higher value than 5 in user_variables.yml - otherwise you may need to validate that your ssh connection to the servers have 'OpenSSH' in the response14:20
*** woodard has quit IRC14:20
odyssey4mejaveriak so you're only seeing the issue with a single container?14:20
javeriakodyssey4me, well yes, it fails out on memcached infra314:21
javeriaki dont a problem ssh'ing into it otherwise, ping also works14:21
*** cloudtrainme has joined #openstack-ansible14:21
odyssey4mejaveriak that's odd - can you confirm that the container does not have a conflicting ip address with something else?14:22
*** woodard has joined #openstack-ansible14:22
javeriakyep, that was my first thought, no conflicts14:22
odyssey4memhayden now you see why I was reticent from the start to include an alternatively licensed file (re: https://review.openstack.org/216849) - it's complicated14:23
odyssey4memhayden would it be possible for us to simply pull the file down within the gate check script instead of carrying it?14:23
mhaydenodyssey4me: bleh14:23
mhaydenodyssey4me: could i ping openstack legal about it and figure out the best path?14:24
odyssey4memhayden you could, although perhaps a discussion in #openstack-infra would give you a pointer too14:25
odyssey4methis is not something that openstack is unfamiliar with14:25
mhaydenhah okay14:25
cloudnull++ or rope in van from OpenStack Dev ?14:26
odyssey4mesure, if there is a more particular person that we know about - go there14:26
odyssey4methe point is that this is something the community has dealt with many times over14:27
odyssey4meyou could even ML the question :)14:27
odyssey4meI'm sure that'd generate a nice little /. style flame war as a tangent :)14:27
* odyssey4me buys popcorn in preparation14:28
odyssey4mecloudnull did you see my note about gnupgp earlier?14:28
odyssey4mejaveriak that is very, very odd - something must be interfering on that host14:29
odyssey4memaybe an iptables leftover rule or something?14:29
cloudnullI did. I fired off a retry last night thinking that gnupg was the issue but went to bed before confirming the issue. Thanks for updating that patch.14:29
odyssey4memaybe you can rekick the host and rebuild all the containers on it?14:29
odyssey4mecloudnull yeah, I tested a few things to confirm that the issue was the protocol/port with that host - I did confirm that the ubuntu and the normal secondary we use both serve the key, so we're all good14:30
javeriakodyssey4me, thats possible, but wouldn't I see an issue in the setup-hosts playbook, that runs fine, just re-ran it to confirm and no issues14:30
javeriakyea I'll tear it down if all else fails14:31
palendaeodyssey4me: Could have sworn that the FAQ I linked addressed the MIT license in OpenStack projects14:31
odyssey4mejaveriak note that the tear down script is best effort - it's not perfect14:32
odyssey4mepalendae yes, but mattt raised a good question from the FAQ14:33
palendaeAh14:33
matttodyssey4me mhayden palendae : in my comment i wasn't suggesting to update our top level license, was just throwing it out there to avoid us getting into a legal battle :)14:40
odyssey4memattt sure, so we need a definitive direction from someone who knows stuff14:41
*** javeriak_ has joined #openstack-ansible14:42
*** javeriak has quit IRC14:44
*** javeriak has joined #openstack-ansible14:45
*** phalmos has joined #openstack-ansible14:46
*** javeriak_ has quit IRC14:46
mhaydensheesh, mattt  :P14:48
mhaydenj/k14:48
*** phalmos_ has joined #openstack-ansible14:49
*** phalmos has quit IRC14:51
openstackgerritMerged stackforge/os-ansible-deployment: Fix keystone shibboleth template to detect ssl usage correctly  https://review.openstack.org/22048014:53
*** k_stev has joined #openstack-ansible14:53
palendaeodyssey4me: Yeah, that's a fair statement. None of us are lawyers14:54
palendaeTuring should have GPL'ed his whole machine and everything would be easy!14:54
openstackgerritMerged stackforge/os-ansible-deployment: Remove double register in swift handlers  https://review.openstack.org/22123714:54
openstackgerritMerged stackforge/os-ansible-deployment: include cinder_all group vars file in cinder-* playbooks  https://review.openstack.org/22124214:54
openstackgerritMerged stackforge/os-ansible-deployment: Switch Nova/Tempest to use/test Cinder API v2  https://review.openstack.org/22008114:54
*** CheKoLyN has joined #openstack-ansible14:54
mhaydenodyssey4me / mattt: http://lists.openstack.org/pipermail/legal-discuss/2015-September/000397.html15:00
*** javeriak_ has joined #openstack-ansible15:01
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Fix keystone shibboleth template to detect ssl usage correctly  https://review.openstack.org/22134715:02
mhaydenodyssey4me / mattt: and there you have it -> http://lists.openstack.org/pipermail/legal-discuss/2015-September/000398.html15:02
* mhayden gets to work15:02
*** javeriak_ has quit IRC15:03
palendaeLinderg'd!15:03
*** javeriak_ has joined #openstack-ansible15:03
*** javeriak has quit IRC15:03
*** KLevenstein has quit IRC15:04
mhaydenDUN GOT VAN'D15:04
odyssey4memhayden orsm :)15:04
mhaydenorsm? :)15:05
* mhayden googled and wished he hadn't15:05
odyssey4memhayden orsm = awesome15:05
mhaydenoh, gotcha15:05
mhayden:)15:05
palendaeYou can google Lindberg'd and be safe15:05
palendaeDon't google pythong though15:05
odyssey4melol, now I'm curious15:06
*** javeriak_ has quit IRC15:06
openstackgerritMajor Hayden proposed stackforge/os-ansible-deployment: Add profiling for Ansible tasks  https://review.openstack.org/21684915:09
mhaydenodyssey4me: bumped with license fun ^^15:10
*** KLevenstein has joined #openstack-ansible15:23
*** skamithi13 has quit IRC15:24
*** skamithi14 has joined #openstack-ansible15:24
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Changed certificate order for pem generation with CA files  https://review.openstack.org/22136115:24
evrardjpthis ^is important to me, because I introduced a regression in certificate generation for haproxy15:25
evrardjpit didn't appear in my previous testing15:25
*** cloudtrainme has quit IRC15:26
*** cloudtrainme has joined #openstack-ansible15:28
evrardjpI've found another bug, but I'm maybe the only to have that: does someone have haproxy_ssl: True with nova_spice_html5proxy_base_proto: https?15:36
evrardjpif someone has, there are chances that you have protocol mismatch issues, but also haproxy misconfiguration... so I don't know if I should fix haproxy misconfiguration15:36
*** devlaps has joined #openstack-ansible15:43
odyssey4meevrardjp the spice/haproxy mismatch sounds legit - only the keystone config currently adapts the backend haproxy config if keystone is serving via https15:43
evrardjpI'll solve it then15:43
odyssey4meevrardjp as I recall with novnc there was a setting in nova.conf which was used for publishing the URL for the console - but not used for anything else... maybe there's an easier override for spice?15:44
odyssey4meie spice is still served via http but https is done at haproxy15:45
*** KLevenstein is now known as KLev-dentist15:45
evrardjpthere is a variable15:46
evrardjpthere are a few variables that changes what's shown on novnc15:46
evrardjpI'll post a fix, you'll see15:46
evrardjp:)15:46
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Update tempest configuration  https://review.openstack.org/22055915:48
*** alop has joined #openstack-ansible15:48
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add galera_address to all playbooks installing galera_client  https://review.openstack.org/22130115:49
*** kerwin_bai has quit IRC15:52
evrardjpis there a way to define a part of a dict conditionnally (in variables)? Or should define it the variable in my dict anyway and change the checks from is defined to is true in the usage part (like a template)?15:55
odyssey4meevrardjp I'm not aware of a way of conditionally including a piece of dict.16:01
evrardjpok thanks16:01
evrardjpthat's what I thought too16:01
odyssey4meexcept if the dict is something like the backend haproxy config16:01
odyssey4melike what's done here: https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/haproxy-install.yml#L4616:02
evrardjpbecause the check is already done in the template, that's what you mean, right?16:02
odyssey4methe value for the backend options happens to be a dict16:02
odyssey4meso it includes either one value or the other based on a condition16:02
evrardjpyeah, it's not really what I meant ;)16:02
odyssey4meok, just thought I'd throw it out there16:03
evrardjpin your example I meant defining or not the variable haproxy_backend_options16:03
odyssey4meit was a hack16:03
*** shoutm has joined #openstack-ansible16:03
evrardjpit's a good hack I sometimes use ;)16:03
*** gparaskevas has quit IRC16:03
odyssey4meyeah, I haven't found a way to do that - you can't really append to a dict without using a module16:04
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Fix of haproxy ssl misconfiguration with nova_console  https://review.openstack.org/22138616:04
odyssey4mesorry, append's the wrong word for a dict I guess - perhaps the right word for a list16:04
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Fix of haproxy ssl misconfiguration with nova_console  https://review.openstack.org/22138616:04
evrardjpI'm learning, so I thought it was maybe possible with some power user skillz !16:05
evrardjpbut it isn't16:05
evrardjpthere are workarounds in any case16:06
*** sdake_ has joined #openstack-ansible16:06
*** jwagner_away is now known as jwagner16:07
*** phalmos_ has quit IRC16:08
cloudnullsorru for the late meeting ping for bug triage today: cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, mhayden16:09
d34dh0r53o\16:09
prometheanfirehi16:09
hughsaundershey16:09
evrardjphi16:09
cloudnullhey hey16:10
cloudnull:)16:10
Sam-I-Ammoo16:10
dstanekhey16:10
palendaeHere-ish16:10
cloudnullits like a monday, yesterday was one of the rare US bank holidays :)16:10
*** waded_ has left #openstack-ansible16:10
prometheanfirethat what we are calling it?16:11
Sam-I-Amit was not-computer day16:11
Sam-I-Amactually not-computer weekend16:11
odyssey4meo/16:11
hughsaunders\o/ bank holiday16:12
cloudnull(╯°□°)╯︵ ┻━┻>>bank holiday16:12
cloudnullok https://bugs.launchpad.net/openstack-ansible/+bug/149341116:12
openstackLaunchpad bug 1493411 in openstack-ansible " Switch Nova/Tempest to use/test Cinder API v2" [Undecided,New]16:12
*** cloudtrainme has quit IRC16:13
cloudnulldoc bug that needs to be sorted.16:13
*** shoutm has quit IRC16:13
cloudnullissue origination https://review.openstack.org/#/c/214045/16:13
cloudnullSam-I-Am: you have bandwith to try and bang that out? --cc odyssey4me16:14
Sam-I-Amnope16:14
Sam-I-Amthat would be more of an rpc release notes thing16:14
odyssey4mecloudnull the standard for docs bugs at this stage is to set them to low and add the rpcdocs group16:14
Sam-I-Ami dont think we have a place in upstream osad for things like that16:15
odyssey4meie confirmed, low, rpcdocs16:15
odyssey4methey then get picked up whenever someone has time, and that list is also given to the osic team to pick up16:15
cloudnullwe should touch on that, maybe on the thursday meeting . as it seems that our "doc" related issues are growing.16:16
odyssey4meagreed16:16
Sam-I-Amcloudnull: there's no agreement on what in-tree docs should provide16:16
cloudnullok Ill get to adding that to the agenda16:16
cloudnullnext https://bugs.launchpad.net/openstack-ansible/+bug/149208016:17
openstackLaunchpad bug 1492080 in openstack-ansible "radvd not installed in neutron_agents_container" [Undecided,New]16:17
Sam-I-Amdo we support v6?16:17
Sam-I-Ami dont recall testing it16:17
prometheanfireiirc it is a req of neutron16:17
prometheanfireeven if we don't support it16:17
prometheanfireor used to be16:18
cloudnullevrardjp: mrstanwell: rackertom: getting that into liberty-x for "official" ipv6 support would be interesting.16:18
evrardjpit should be supported, v6 is the future16:18
cloudnull^ ++16:18
evrardjpI'll work on it anyway16:18
odyssey4me++16:18
mrstanwelltechnically, v6 is the past...16:18
Sam-I-Amsomeday we need to test v616:18
hughsaundersv6 has been the future for a while16:18
mrstanwellwe just haven't got there yet.16:18
cloudnullhahaha16:18
evrardjpmrstanwell: true16:18
Sam-I-Ampatches welcome :)16:18
evrardjpI don't see a problem in anycase to introduce radvd16:19
cloudnullI'd like to ipv6 support in the near future. its been mostly functional since kilo so i think its time we take a look at it espially with interested parties involved in making it go.16:19
prometheanfirelooks like neutron needs it16:19
prometheanfirehttps://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra https://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes16:19
evrardjpcloudnull: it's really not that simple for tenants16:19
odyssey4memy only concern would be whether radvd needs to run as a service, or whether it's started within the customer networks and managed that way16:19
mrstanwellI installed radvd by hand in the container, and slaac started working.  that's low-hanging fruit.16:19
odyssey4meI haven't looked into the implementation requirements, but I'd be concerned with data leaks between tenants.16:20
cloudnull*especially16:20
mrstanwellI haven't gotten back to it yet to see what other evils lurk, however.16:20
Sam-I-Amit probably does what it does with every other service... launch the daemon with a generated config file somewhere in /var/lib/neutron16:20
odyssey4meSam-I-Am I would hope so16:20
prometheanfireodyssey4me: flat network problems, not really ipv6 specific16:20
mrstanwellsam: yes, that's what it does16:20
evrardjpI've got tenant IPv6 working without installing rdavd IIRC16:20
evrardjpthat's why I asked if it was really necessary16:21
prometheanfireI have v6 working with external radvd16:21
evrardjpsame16:21
evrardjpso I don't see a problem to introduce radvd, but not as a mandatory item16:21
cloudnullprometheanfire can you join the party on that issue?16:21
prometheanfiresure16:21
Sam-I-Amif we're going to support v6, we can't be choosy on how people do it16:22
mrstanwellneutron tries to start it, whether it's there or not...16:22
odyssey4meit'd be nice to see this come in with liberty16:22
cloudnull++16:22
prometheanfirewonder what'd happen if it's already running as a service...16:22
odyssey4meanyone volunteer to pick it up?16:22
Sam-I-Amprometheanfire: probably nothing as long as the config files dont conflict16:22
evrardjpprometheanfire: or running somewhere else... it needs to be carefully studied... I can't do it right now, sorry16:23
prometheanfireya, also, could be listening on other interfaces16:23
Sam-I-Amhowever, two radvd services on the same network... nope.16:23
Sam-I-Amunless they're advertising the same thing16:23
evrardjpit will work, but it sounds bad16:23
prometheanfireindeed16:23
prometheanfirethat's a general ops problem though, we can't control outside resources16:23
evrardjpmaybe there should be spec for it16:24
evrardjpexplaining what we see as a possible issue16:24
odyssey4meI'd agree to an overall ipv6 spec.16:24
prometheanfireya, that could be useful16:25
odyssey4meBut if Neutron is trying to start this and fails (because it's not there), then this is a bug.16:25
prometheanfirewould be nice if tempest did v6 testing16:25
Sam-I-Ami havent seen neutron fail without this16:25
evrardjpSam-I-Am: +116:25
prometheanfireeither have I16:25
odyssey4meI'd suggest doing an initial simple solution for the bug - then doing the more careful inspection as part of the spec.16:25
Sam-I-Amit might with v6 things configured and no radvd16:25
mrstanwellNeutron definitely tries to start it.  That's what tipped me off.  It was in the sudo log.16:25
prometheanfireand I set v6 addresses in neutron16:25
Sam-I-Ambut as-is, osad does not gail here.16:25
Sam-I-Amfail16:25
cloudnullwould somone want to draft the initial spec ?16:26
evrardjpodyssey4me: I agree16:26
evrardjpmaybe mrstanwell, because he saw the bug? :D16:26
prometheanfiresure, guess I can do it16:26
mrstanwell;-)  I'm happy to help.  Not terribly experienced with either osad or ostack....16:26
prometheanfireneed to start working on the standalone swift testing spec sometime though16:26
odyssey4meprometheanfire you may wish to review https://review.openstack.org/221009 as it's a dependency for that16:27
cloudnullprometheanfire | mrstanwell: you guys have some cycles to put into a quick spec? would be nice to have some different oppinions on it so that we get the best solution going forward .16:27
odyssey4me+116:27
prometheanfirecloudnull: ya, many people on one lab makes time16:28
*** phalmos has joined #openstack-ansible16:28
prometheanfireodyssey4me: if that's only dependant then fine, but that's a distraction from v6 atm :P16:28
cloudnullmrstanwell: experience in osad or ostack is not required :)16:28
cloudnullbut we can help in the spec draft16:29
cloudnullok marked issue as wishlist / confirmed.16:29
prometheanfireya, added to todo list16:29
mrstanwellnot clear on the scope of the spec.  is this new support, really?16:29
odyssey4memrstanwell the spec would be for ipv6 support end to end16:30
*** mnestheu1 has joined #openstack-ansible16:30
prometheanfirenot really, more of a verification and definition of what is supported16:30
odyssey4meand you can define the scope in the spec16:30
prometheanfireodyssey4me: openstack services listening on v6?16:30
odyssey4meprometheanfire heh, no idea - scope it in the spec according to what you think is practical and useful16:30
*** mnestheu1 is now known as scarlisle16:31
prometheanfireya, gonna start with guests, since that's easy :P16:31
cloudnullprometheanfire: i'd say no. I'd start with tenant support for v6 and go from there.16:31
evrardjpI think 2 specs (or more) would be great: One with the analysis of radvd and another to complete with other ipv6 analysis16:31
odyssey4me++ cloudnull16:31
evrardjpcloudnull: ++16:31
prometheanfirewould need ipv6 ansible inventory, probably16:31
cloudnullevrardjp:  that'd be great IMO if we have cycles to get that done.16:31
mrstanwelltenant support is one thing.  ostack service v6 support in osad is a whole 'nother ballgame.16:31
prometheanfireanyway, next?16:31
prometheanfiremrstanwell: exactly16:32
miguelgrinbergodyssey4me: hey, happy to look at that heat problem. I'll let you know what I find.16:32
odyssey4methanks miguelgrinberg16:32
*** javeriak has joined #openstack-ansible16:32
cloudnullcool! prometheanfire evrardjp mrstanwell | typie typie make the v6 go :)16:32
prometheanfireafter lunch kthnxbai16:33
mrstanwellhey, cut us some slaac.  }-)16:33
cloudnullnext https://bugs.launchpad.net/openstack-ansible/+bug/149059116:33
openstackLaunchpad bug 1490591 in openstack-ansible trunk "Update 'Add a compute host' operations guide section for kIlo" [Low,New]16:33
evrardjpwe'll have to define a timeline to see if that meets my time availability ;)16:33
cloudnullmrstanwell:  lol16:33
evrardjpmrstanwell: :D16:33
cloudnulldoc issue. palendae you have some time to fixerate that ?16:34
palendaecloudnull: Maybe, still poking upgrade issues16:34
Sam-I-Amcloudnull: this probably also applies to rpc16:35
Sam-I-Amtoo many things to track16:35
palendaeSam-I-Am: It does16:35
Sam-I-AmDocImpact is for osad bugs, not for rpc bugs16:36
palendaeSam-I-Am: rpc is rpc's concern16:36
palendaeThis is upstream triage16:36
Sam-I-Amso just tagging something DocImpact does not necessarily mean it will also be analyzed for rpc16:36
Sam-I-Ampalendae: yeah, i know. but this is extremely hard to follow.16:36
palendaeSam-I-Am: I understand. Just saying it's not necessarily an openstack-ansible problem to fix RPC's docs16:36
palendaeI realize having our feet in both camps is hard16:37
odyssey4meall the openstack-ansible docs need an overhaul16:37
cloudnullmore on that thursday :)16:37
odyssey4meI'd suggest that we look at it as a 'feature' as we do work on the upgrade mechanism for liberty16:37
cloudnullthats a good idea16:38
odyssey4methree tracks - one for the configs, one for the docs and one for the upgrade mechanism16:38
palendaeSure...right now the problem is bodies16:38
palendaeOnly Sam-I-Am and I bother with actually committing docs16:38
palendaeAnd we're both tied up16:38
cloudnullwe just need more hours in the day .16:38
Sam-I-Amcan we script that?16:39
cloudnullok triaged confirmed low, added to list for meeting thrusday16:39
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/148945116:39
openstackLaunchpad bug 1489451 in openstack-ansible "Not able to connect memcached_container while running setup-infrastructure.yml " [Undecided,New]16:39
odyssey4mepalendae evrardjp and I have too, but yes we could do with more people paying attention to working on docs more consistently16:39
Sam-I-Amdownloadmorehours.com ?16:39
palendaeAnyway, if I get the time, yes, I can tackle that. If someone gets to it before me, even better16:39
odyssey4methis one was raised earlier16:39
odyssey4meit seemed to have been one container on one host in the infra16:40
*** Guest60469 is now known as mgagne16:40
*** mgagne has joined #openstack-ansible16:40
odyssey4mebut it may relate to the forks value when using real hardware16:40
odyssey4meie https://bugs.launchpad.net/openstack-ansible/+bug/147981216:40
openstackLaunchpad bug 1479812 in openstack-ansible trunk "ssh connection failures during deployments" [Low,New] - Assigned to Jesse Pretorius (jesse-pretorius)16:40
cloudnullthis issue seems like an issue with the image on the disk and ties to a larger effort to remove the requirement to download a cached image in favor of creating an image within the environment which can be updated and managed strictly through osad.-cc mhayden odyssey4me andymccr.16:40
odyssey4methere's been discussion there and there's an outstanding query of bgmccollum_16:40
odyssey4methat may be, and yes given a little time andymccr, mhayden and I have discussed perhaps including an image build process into openstack-ansible instead of using the download mechanism16:42
palendaeWhat kind of image?16:43
palendaeContainers?16:43
odyssey4meinitially just the base lxc image we're downloading16:43
palendaeWould that interfere with the ability to split out all services into their own physical nodes (if a deployer wanted)?16:43
odyssey4mebut perhaps expanding that to a broader process, which would need a blueprint/spec16:43
palendaeI seem to remember that being a thing we wanted to keep compatiblke16:43
odyssey4mepalendae it should not - it's an implementation detail handled in the playbooks currently16:44
odyssey4meit's only used in the container create role16:44
palendaeOk16:44
palendaeAnd the environment, since you'd have to modify that to get the bare metal properties...but continue :)16:44
odyssey4mewell, the project should not try to cater for every possible install method with the same playbooks IMO - but that's another discussion16:45
evrardjpcloudnull: if you are talking of template distribution/caching improvement process, you can count me in. In terms of schedule, starting with the next summit16:45
cloudnullnice !16:45
odyssey4meevrardjp nice - I think that perhaps this is a worthy topic for discussion at the summit16:46
evrardjpthis needs to be solved, at least for security awareness16:46
odyssey4mewe can work on it during the Mitaka timeframe16:46
cloudnullyes i think thats a major improvement we should be able to tackle in the M cycle.16:46
cloudnulland potentially backport to Liberty if at all possible. but that may be too far forward looking.16:47
palendaeLiberty needs an upgrade path too16:47
palendaeAn implementation of one16:47
odyssey4meyeah, we make the backport call once we have it working16:47
cloudnull++16:48
odyssey4mepalendae agreed, your spec needs reviews16:48
palendaeodyssey4me: It does and I need to finish it16:48
odyssey4me+116:48
palendaeI lost some work because of the latest patchset conflict16:48
palendaeBiggest thing I think I lost was the ML discussion links for the epoch things16:49
cloudnulllast issue on deck https://bugs.launchpad.net/openstack-ansible/+bug/148940616:49
openstackLaunchpad bug 1489406 in openstack-ansible "Horizon configuration to support Keystone V3 multiple domains" [Undecided,New]16:49
cloudnullis Cristian Calin (cristi-calin)  here ?16:50
odyssey4methere's a patch included there, which I asked the author to try and submit for review16:50
cloudnull^ that16:50
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Updated the configuration to current dynamic inventory standards  https://review.openstack.org/22140216:50
odyssey4meunfortunately the author went offline and I have not seen him on since16:50
cloudnullif not we can make it go, but would not want to snake the commit from them16:51
odyssey4meso I think one of us needs to just submit on his behalf16:51
odyssey4mejust have him as the author16:51
odyssey4meI'm happy to do that if no-one else picks it up16:52
odyssey4meit's pretty key for Liberty as Keystone v2 is most likely to be deprecated for Liberty16:53
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment-specs: Add spec for major update of haproxy role  https://review.openstack.org/21408916:53
cloudnullI responded to the issue we'll see what happens and if nothing we'll pickup the changeset16:53
cloudnullok so thats it16:54
cloudnullanything anyone want to raise ?16:54
evrardjpnone16:55
evrardjpkeystone v2.0 will be deprecated in Liberty, really?16:56
cloudnullthanks everyone !16:56
*** woodard has quit IRC16:56
evrardjpthanks to you too16:56
cloudnulldolphm: lbragstad: -cc ^^16:56
odyssey4meevrardjp assuming they reach their target, yes16:56
evrardjpinteresting16:56
* cloudnull being cross functional16:56
cloudnull:D16:56
dolphmevrardjp: the v2 client (especially the CLI) is facing imminent deprecation, but the API is not quite there yet16:57
odyssey4meKEystone v3 has been out for several cycles16:57
evrardjpanyway I'll need to test the federation stuff with multiple IdP and a DS later... so I guess I'll be for v3 too16:57
*** woodard has joined #openstack-ansible16:57
evrardjpodyssey4me: indeed, but not in the clients and some of the consumers of keystone16:57
odyssey4meevrardjp yeah, there has been some effort in gate checks and the ML to change that16:58
prometheanfirementioning this I guess https://etherpad.openstack.org/p/openstack-ansible-mitaka-summit16:58
prometheanfirenot that etherpad is working16:58
odyssey4methe encouragement is generally for the projects to support the use of the openstack client instead, but that's taking some time16:58
odyssey4meprometheanfire yeah I noticed that earlier and thought it might be transitional as -infra is doing aquite a bit of work on etherpad at the moment16:59
prometheanfireneat16:59
evrardjpwe should put the names of those who have written the text....16:59
evrardjpI didn't write anything!17:00
prometheanfire?17:00
prometheanfireI have my name in the little dropdown17:00
evrardjpyes, but it's far harder to know what you changed17:01
odyssey4meme too17:01
evrardjpwith only colors17:01
* prometheanfire shrugs17:01
odyssey4meyeah, etherpad sucks quite a bit actually17:01
*** skamithi12 has joined #openstack-ansible17:02
*** harlowja has joined #openstack-ansible17:03
*** javeriak has quit IRC17:03
evrardjpI'm off for today, see you tomorrow!17:07
*** woodard has quit IRC17:10
*** jwagner is now known as jwagner_away17:16
*** jwagner_away is now known as jwagner17:17
*** jwagner is now known as jwagner_away17:18
*** sdake_ has quit IRC17:19
*** jwagner_away is now known as jwagner17:19
*** woodard has joined #openstack-ansible17:21
*** skamithi12 has quit IRC17:22
*** abitha has joined #openstack-ansible17:30
*** abitha has quit IRC17:31
*** abitha has joined #openstack-ansible17:31
*** KLev-dentist is now known as KLevenstein17:41
*** sdake has joined #openstack-ansible17:44
mhaydenodyssey4me: sorry i missed the discussion above -- here's what i got from some quick benchmarking -> https://bugs.launchpad.net/openstack-ansible/+bug/148916917:46
openstackLaunchpad bug 1489169 in openstack-ansible "Speed up deployment by upgrading cached container image" [Wishlist,Confirmed] - Assigned to Major Hayden (rackerhacker)17:46
*** CheKoLyN has quit IRC17:51
*** javeriak has joined #openstack-ansible17:57
*** cloudtrainme has joined #openstack-ansible18:00
*** cloudtrainme has quit IRC18:01
*** pabelanger has joined #openstack-ansible18:03
pabelangerohai18:03
*** javeriak has quit IRC18:04
*** javeriak has joined #openstack-ansible18:05
*** CheKoLyN has joined #openstack-ansible18:05
*** CheKoLyN has quit IRC18:22
cloudnullo/ pabelanger18:23
pabelangercloudnull: good to read you have a plan for ansible roles under big tent.  Looking forward to this18:25
cloudnullits a wip so far but its getting there18:25
*** sdake_ has joined #openstack-ansible18:25
pabelangerFor the most part, the roles I am working on are -infra related. Nodepool, zuul, jenkins, etc. But as long as we have a general ansible team, I don't see a problem18:25
cloudnullthats awesome!18:27
cloudnullif we can help any please let us know.18:28
*** sdake has quit IRC18:29
*** openstackgerrit has quit IRC18:31
*** openstackgerrit has joined #openstack-ansible18:31
*** cloudtrainme has joined #openstack-ansible18:34
*** CheKoLyN has joined #openstack-ansible18:39
*** sdake_ is now known as sdake18:40
*** javeriak_ has joined #openstack-ansible18:40
*** cloudtrainme has quit IRC18:40
*** cloudtrainme has joined #openstack-ansible18:41
*** javeriak has quit IRC18:43
*** javeriak has joined #openstack-ansible18:46
*** sdake_ has joined #openstack-ansible18:46
*** javeriak_ has quit IRC18:46
*** sdake has quit IRC18:49
*** abitha has quit IRC18:56
*** KLevenstein_ has joined #openstack-ansible18:59
*** KLevenstein has quit IRC18:59
*** KLevenstein_ is now known as KLevenstein18:59
*** abitha has joined #openstack-ansible19:01
*** cloudtrainme has quit IRC19:02
*** cloudtrainme has joined #openstack-ansible19:03
*** cloudtrainme has quit IRC19:04
*** pabelanger has quit IRC19:06
*** cloudtrainme has joined #openstack-ansible19:15
scarlisleGreetings all.  Do the playbooks or the lxc-template setting file descriptor limits for containers?19:15
scarlisleer19:16
scarlisleeh, you know what I mean19:16
cloudnullscarlisle: you want to set the ulimit within the container ?19:22
*** Mudpuppy_ has joined #openstack-ansible19:22
cloudnullor are you looking at modifying the inotify limits on the container host ?19:23
cloudnullor all of the above ?19:23
scarlislecloudnull trying to figure this out because even though the playbooks are setting rabbit's file descriptor limit at 4096, its only getting 399619:23
cloudnullJuno? Kilo? master? -- version?19:26
* cloudnull Assuming Juno19:26
cloudnullhttps://github.com/stackforge/os-ansible-deployment/blob/juno/rpc_deployment/roles/rabbit_common/templates/rabbitmq-server should set it to 409619:26
*** Mudpuppy has quit IRC19:26
*** arbrandes has joined #openstack-ansible19:26
*** Mudpuppy_ has quit IRC19:27
scarlisleyep, Juno19:28
scarlislenoticing it in 10.1.6 and 10.1.11 at least19:29
*** bgmccollum_ is now known as bgmccollum19:29
scarlisleand yeah, that file is there19:29
scarlislewell, present inside the rabbit containers19:29
*** Mudpuppy has joined #openstack-ansible19:29
*** javeriak has quit IRC19:30
*** k_stev has quit IRC19:31
*** k_stev has joined #openstack-ansible19:35
*** arbrandes1 has joined #openstack-ansible19:35
*** arbrandes has quit IRC19:36
*** k_stev has quit IRC19:39
cloudnullscarlisle: how are you determining that its set to 3996 in the rabbit contianer?19:47
* cloudnull trying to recreate19:47
*** sdake_ is now known as sdake19:49
scarlislecloudnull rabbitmqctl status | grep -A5 file_descriptors19:51
scarlisleroot@<redacted>:~# rabbitmqctl status | grep -A5 file_descriptor19:52
scarlisle {file_descriptors,19:52
scarlisle     [{total_limit,3996},19:52
scarlisle      {total_used,251},19:52
scarlisle      {sockets_limit,3594},19:52
scarlisle      {sockets_used,249}]},19:52
scarlisle {processes,[{limit,1048576},{used,4605}]},19:52
*** Mudpuppy has quit IRC19:56
*** jmckind has joined #openstack-ansible19:57
stevellethis sounds like something I might have fixed for kilo/master19:58
*** Mudpuppy has joined #openstack-ansible19:59
cloudnullscarlisle:  it looks like based on the setting there are some reserved file descriptors on process start up.20:02
cloudnullIE i set it to 102400 and the running value is 10230020:02
matttmhayden: nice, that was straight-forward enough :)20:02
cloudnullscarlisle:  and setting somthing off like 4224 results in the same 3996 running value20:03
scarlisleinteresting20:07
scarlisleso if we need to bump an environment beyond 4096 we have to bump it much higher in order to get something close to 4096?  Or am I misunderstanding?20:08
cloudnullyes its seems to go in steps.20:09
cloudnullDepending on the host, I'd assume that you can set it to 8196 which should be more than enough.20:11
cloudnulland in my basic testing that seems to work20:11
cloudnullscarlisle: the resultant of setting it to 8196 is 728420:19
scarlisleweird20:31
scarlisleI just tried it20:31
scarlisleset ulimit to 819620:31
scarlisleand now my rabbit is at 809620:31
*** Bjoern_ has joined #openstack-ansible20:31
*** Bjoern_ is now known as BjoernT20:31
*** k_stev has joined #openstack-ansible20:31
scarlislewas hoping there was a correlation20:31
scarlislecloudnull what do you get when you run cat /proc/sys/fs/file-nr?20:32
cloudnullscarlisle: http://paste.openstack.org/show/450752/20:34
cloudnullthe value on the host is inheritted within the container20:34
*** k_stev has quit IRC20:36
scarlisleyep20:38
scarlisleso the value in the left column is basically spread across the host as well as its containers, right?20:40
scarlisleshared, rather20:40
cloudnullyes20:41
*** tlian2 has joined #openstack-ansible20:55
*** tlian has quit IRC20:57
*** woodard has quit IRC21:06
*** sdake_ has joined #openstack-ansible21:16
*** sdake has quit IRC21:20
*** arbrandes1 has quit IRC21:28
*** cloudtrainme has quit IRC21:36
*** devlaps has quit IRC21:38
*** cloudtrainme has joined #openstack-ansible21:43
scarlisleso we have to manually change that 409621:44
scarlisleran a python child bomb against rabbit with an fd of 1500021:44
scarlislethings scaled rather nicely, actually21:44
*** cloudtrainme has quit IRC21:46
*** darrenc_ is now known as darrenc21:47
openstackgerritMatthew Thode proposed stackforge/os-ansible-deployment-specs: Add spec for IPv6 support for tenants  https://review.openstack.org/22151621:51
prometheanfiremrstanwell: ^21:51
*** cloudtrainme has joined #openstack-ansible21:52
*** sdake_ is now known as sdake21:55
*** cloudtra_ has joined #openstack-ansible21:57
*** jmckind has quit IRC22:00
*** cloudtrainme has quit IRC22:01
*** sdake_ has joined #openstack-ansible22:02
*** sdake has quit IRC22:05
cloudnulltyvm prometheanfire22:10
prometheanfirecloudnull: ja22:10
prometheanfirenot really sure on how to do ipv6 testing, but that's for the future22:10
*** jwagner is now known as jwagner_away22:11
*** spotz is now known as spotz_zzz22:16
mrstanwellprometheanfire: that makes sense, thanks.22:17
prometheanfire:D22:17
*** Mudpuppy_ has joined #openstack-ansible22:19
*** Mudpuppy has quit IRC22:22
*** pradk has quit IRC22:22
*** Mudpuppy_ has quit IRC22:23
*** skamithi13 has joined #openstack-ansible22:26
Sam-I-Amprometheanfire: s/tenants/projects :)22:27
prometheanfireSam-I-Am: meh22:28
openstackgerritMatthew Thode proposed stackforge/os-ansible-deployment-specs: Add spec for IPv6 support for tenants  https://review.openstack.org/22151622:29
prometheanfireSam-I-Am: better?22:29
*** sigmavirus24 is now known as sigmavirus24_awa22:30
*** skamithi14 has quit IRC22:30
Sam-I-Amstill says tenants?22:30
prometheanfirewhere?22:31
prometheanfirethe tag will remain I think22:31
prometheanfirealso, title22:31
prometheanfireraise an issue and if acked I'll modify22:31
Sam-I-Amso... theres a commit message and a filename22:32
Sam-I-Ami suppose you could change both unless i'm missing something22:32
prometheanfirebah, guess I'll do it22:32
prometheanfirejust to make you go away22:32
openstackgerritMatthew Thode proposed stackforge/os-ansible-deployment-specs: Add spec for IPv6 support for projects  https://review.openstack.org/22151622:34
prometheanfireSam-I-Am: now leave me alone22:34
Sam-I-Amprometheanfire: no22:35
Sam-I-Ambut thanks22:35
*** cloudtra_ has quit IRC22:45
*** ggillies has joined #openstack-ansible22:48
*** jwagner_away is now known as jwagner22:51
*** jwagner is now known as jwagner_away22:56
*** CheKoLyN has quit IRC23:14
*** scarlisle has quit IRC23:38
*** KLevenstein has quit IRC23:42
cooljnow come up an equivalent word to multitenancy based on the word project23:43
*** phalmos has quit IRC23:47
*** shoutm has joined #openstack-ansible23:49
Sam-I-Amcoolj: multiprojectcy23:55
Sam-I-Amduhh23:56

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