Monday, 2015-08-17

*** markvoelker has quit IRC00:02
*** sdake_ has joined #openstack-ansible00:04
*** shoutm has quit IRC00:06
*** sdake has quit IRC00:07
*** sdake has joined #openstack-ansible00:20
*** sdake_ has quit IRC00:23
*** lkoranda has quit IRC01:01
*** lkoranda has joined #openstack-ansible01:02
*** woodard has joined #openstack-ansible01:07
*** woodard has quit IRC01:11
*** markvoelker has joined #openstack-ansible01:58
*** markvoelker has quit IRC02:03
*** logan2 has quit IRC02:18
*** markvoelker has joined #openstack-ansible02:31
*** Mudpuppy has quit IRC02:32
*** logan2 has joined #openstack-ansible02:57
*** JRobinson__ is now known as JRobinson__afk03:02
*** Mudpuppy has joined #openstack-ansible03:26
*** Mudpuppy has quit IRC03:30
*** JRobinson__afk has quit IRC04:08
*** britthouser has joined #openstack-ansible04:11
*** britthou_ has joined #openstack-ansible04:12
*** britthouser has quit IRC04:15
*** openstack has joined #openstack-ansible04:20
*** markvoelker has quit IRC04:31
*** JRobinson__afk has joined #openstack-ansible04:46
*** JRobinson__afk is now known as JRobinson__04:46
*** promethe1nfire is now known as prometheanfire04:50
*** neillc has joined #openstack-ansible04:59
neillchello05:00
*** daneyon_ has quit IRC05:13
*** daneyon has joined #openstack-ansible05:14
*** shausy has joined #openstack-ansible05:24
*** markvoelker has joined #openstack-ansible05:32
*** markvoelker has quit IRC05:36
*** shausy has quit IRC05:38
*** shausy has joined #openstack-ansible05:39
*** javeriak has joined #openstack-ansible06:30
*** sdake_ has joined #openstack-ansible06:44
*** sdake has quit IRC06:47
*** javeriak has quit IRC06:49
*** javeriak_ has joined #openstack-ansible06:49
*** javeriak has joined #openstack-ansible06:56
*** javeriak_ has quit IRC06:57
*** shoutm has joined #openstack-ansible07:01
odyssey4memorning all07:01
odyssey4mesvg master is unfortunately failing 7/10 times on build - usually in the tempest tests... I'm trying to figure out the cause. It may be resource related, or it may be code related (the underlying code is constantly in flux)... anyway, just so you know that you're not the only one getting failed builds07:02
-openstackstatus- NOTICE: Gerrit is currently under very high load and may be unresponsive. infra are looking into the issue.07:05
*** sdake_ has quit IRC07:08
evrardjpgood morning everyone07:31
*** markvoelker has joined #openstack-ansible07:33
*** markvoelker has quit IRC07:37
*** vdo has joined #openstack-ansible07:47
*** gparaskevas_ has joined #openstack-ansible07:52
odyssey4meo/ evrardjp07:53
*** shackit has joined #openstack-ansible07:56
*** JRobinson__ has quit IRC07:59
*** gparaskevas_ has quit IRC08:06
*** shausy has quit IRC08:10
*** shausy has joined #openstack-ansible08:10
*** javeriak has quit IRC08:26
*** javeriak has joined #openstack-ansible08:30
*** marekd_404 has quit IRC08:54
*** shausy has quit IRC09:06
odyssey4meandymccr are you happy with the changes to https://review.openstack.org/212452 from mattt ?09:07
matttwhenever we bump rabbit we should put a copy in http://mirror.rackspace.com/rackspaceprivatecloud/downloads/09:08
matttrabbitmq downloads are currently failing from the official site09:08
odyssey4memattt oh?09:09
odyssey4memattt there is a review in to bump the version09:09
mattt3.5.3 which we install in master isn't in /rackspaceprivatecloud/downloads/ tho09:10
*** javeriak has quit IRC09:10
*** javeriak has joined #openstack-ansible09:10
odyssey4memattt does the task remove the deb? if not then download manually, rename and run the tasks09:12
mattti can't download manually :P09:12
svggood morning09:12
odyssey4memattt or override the version/URL with one that is on the rax mirror?09:12
odyssey4mesvg morning!09:12
svgodyssey4me: thanks. yes, when i see it's about some timeout, i expect I'm not the culprit :)09:13
odyssey4mesvg nope - it seems to be some sort of issue in cinder/nova, but I've yet to dig deep enough to isolate the issue09:13
svgsounds like fun09:13
odyssey4meFYI: http://lists.openstack.org/pipermail/openstack-dev/2015-August/072185.html09:18
evrardjpthis brings more questions to how mirror.rackspace.com is managed with private cloud efforts, right?09:19
evrardjpI don't know if it's related but we could be mirror of your rpc-repo.rackspace.com/container_images/ too09:21
evrardjpor for everything under http://rpc-repo.rackspace.com for that matter09:21
odyssey4meevrardjp yes, that it is09:22
odyssey4me http://mirror.rackspace.com/rackspaceprivatecloud is a mirror of  http://rpc-repo.rackspace.com09:22
evrardjpthe rpc-repo is I guessed managed by a small team, that has other stuff to do than mirrors, compared to mirror.rackspace.com?09:23
evrardjp(just to understand)09:23
odyssey4meI've been meaning to get rid of our reliance on the rackspace mirror for ubuntu packages as that's hurting more than helping - we often hit the mirror during package updates. we should rather be using whatever mirror is provided on the host image. We implemented a common mirror to try to work around issues we get in hpcloud-b4, but it hasn't helped.09:24
evrardjpk09:24
odyssey4meevrardjp the RPC dev team manages the RPC repo09:24
evrardjpthat makes sense09:24
odyssey4meit's primarily a place to host the python wheels for RPC09:24
evrardjpyeah I understand what it does09:25
evrardjpI was wondering how it was managed09:25
odyssey4meie it's where the repo-build play gets run for each tagged version - and RPC uses the repo-sync to pull the wheels down09:25
odyssey4meah, mostly by hand at this point09:25
odyssey4methe plan is to get rid of the dependency on it down the line09:25
evrardjpit would be far more secure09:26
odyssey4meevrardjp this one on dependency removal: https://blueprints.launchpad.net/openstack-ansible/+spec/remove-upstream-repo-dependency09:26
odyssey4meanother is to implement the image building in a role instead of downloading an upstream image09:26
evrardjpyeah there are tools for it09:27
evrardjpand auditing is better09:27
evrardjpbut it takes longer to deploy09:27
evrardjpthere are lots of work to do everywhere ;)09:28
odyssey4meyes, there's a ton of work09:28
*** markvoelker has joined #openstack-ansible09:33
*** markvoelker has quit IRC09:38
*** c0m0 has joined #openstack-ansible09:42
-openstackstatus- NOTICE: review.openstack.org (aka gerrit) is going down for an emergency restart10:19
*** ChanServ changes topic to "review.openstack.org (aka gerrit) is going down for an emergency restart"10:19
svgok, gerrit is officially not very stable now10:20
*** marekd has joined #openstack-ansible10:39
*** marekd is now known as marekd_40410:40
*** ashishb has joined #openstack-ansible10:43
*** ChanServ changes topic to "Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible"10:46
-openstackstatus- NOTICE: Gerrit restart has resolved the issue and systems are back up and functioning10:46
*** daneyon has quit IRC10:59
*** daneyon has joined #openstack-ansible11:00
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Use slurp to get the content of the ceph.conf file  https://review.openstack.org/21317011:15
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Implement /usr/bin/env as the shebang in all bash scripts  https://review.openstack.org/21188511:20
*** markvoelker has joined #openstack-ansible11:34
*** markvoelker has quit IRC11:39
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Implement /usr/bin/env as the shebang in all bash scripts  https://review.openstack.org/21188511:52
*** benwh4 has joined #openstack-ansible11:59
benwh4hello everybody ! I have a question ... I try to set up a openstack cloud using OSAD but after the creation of the containers I have an error message saying that ssh could not be use into the containers but I could ssh into my target hosts12:00
benwh4and I wonder if I should fill the file into etc/network for my target hosts or I should on the tagert hosts set up the interfaces files manually ?12:01
evrardjpwhat do you mean by "ssh could not be use"?12:03
evrardjpcould you copy paste the output, this way we could help you better?12:03
evrardjp(maybe on a pastebin, like the openstack one)12:04
evrardjpyour target hosts should be network configured12:04
evrardjpthese are the host configuration guidelines: http://osad.readthedocs.org/en/latest/install-guide/targethosts.html12:04
evrardjpsometimes ansible fails because of the amount of connections, don't hesitate to rerun your playbooks12:05
benwh4fatal: [infra1_keystone_container-2d97108f -> infra1] => SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh12:05
evrardjpok12:06
evrardjpthis happens sometimes12:06
evrardjpjust rereun your playbook12:06
evrardjpI meant: run your playbook again12:06
evrardjpsorry for my english12:06
svgI confirm, that happens quite a lot. a rerun and then it just works. And in the next task it could fail again.12:07
benwh4but I didn't reboot the target hosts after configuring the network but I wonder if the configurations must be set up on the /etc/net/interfaces on the hosts directly or into the directory on the os-ansible-deployment12:07
svgI never managed to understand why that happens.12:07
evrardjpsvg: me neither12:08
evrardjpControlMaster maybe12:08
svgwhy?12:08
svgit is fishy though, that should not happen12:08
evrardjpyup12:08
evrardjpdid you try fireball mode?12:08
benwh4so what is the /opt/os-ansible-deployment/etc/network for ?12:08
evrardjpI should try12:08
evrardjpthis is used as an example12:09
evrardjpIIRC12:09
evrardjpif you follow the guide on the link I sent you, you'll eventually arrive here:12:09
benwh4ok it is not meant to be fill with the same changes as on the target hosts ?12:09
evrardjphttp://osad.readthedocs.org/en/latest/install-guide/targethosts-network.html12:09
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Add nova_libvirt_live_migration_flag variable  https://review.openstack.org/21245212:10
evrardjpby default, you shouldn't edit your /opt/os-ansible-deployment/12:10
evrardjpthe code arrives there, so it's not meant for configuration... that happens on the /etc/openstack_deploy/12:11
evrardjp(I meant the configuration stands in /Etc/openstack_deploy/ folder)12:12
evrardjpbut you need to contact your future cloud hosts on a network, and that is what you have to define manually...12:13
evrardjpwhich means: your future cloud hosts have to be network configured12:13
evrardjpthis way you can ssh onto them and then deploy the cloud12:13
evrardjpusing ansible12:13
evrardjpprovided by the project12:14
svgThat setup needs to be run by root. Why?12:15
evrardjpsvg: ?12:16
*** woodard has joined #openstack-ansible12:17
mgariepygood morning everyone12:17
evrardjpgood morning mgariepy12:17
evrardjpare the rabbitmq code/binaries uploaded on your repos, dear rackspace guys? :)12:18
evrardjplatest*12:18
evrardjpsvg: I've a question for you, for ansible... In roles/repo_server/tasks/repo_sync_manager.yml there is a when12:20
evrardjpunder a notify12:20
svg(deploying and working with osad assumes you run it with the root user)12:21
evrardjpit means the task runs when the "when" condition is met, right? Not that the "when" triggers for the notify event12:21
svgevrardjp: you mean there is a task with a condigitional and a notify12:22
benwh4another thing ... why there is a aio1 configuration running when the playbooks are set up for a normal deployment ?12:22
evrardjpsvg: yes, so the when is only for the task, not for the notify12:22
svgyes, the conditional controls task exectution, the changed status controls the notify12:22
evrardjpis there a way to have that only for notify event?12:22
evrardjpexcept by using a wrapper script12:22
svgyou can put a cnditional in the handler12:22
evrardjpthat's what I meant12:23
evrardjpso when in the handler section works12:23
evrardjpcool12:23
svgor you can use changed_when: as that is what controls the changed status which will fire the handler12:23
svgyou can even add a notify in a task12:23
evrardjpofc12:24
svg... in a handler12:24
svgI mean12:24
evrardjpI understood ;)12:24
svgand have a chain reaction12:24
svghandlers are tasks basically12:24
evrardjpthat are triggered at the end12:24
evrardjpOk12:24
svgyes12:24
evrardjpI think I'll remove the haproxy restart logic12:24
evrardjpit's a pain12:25
evrardjpit's not only done at the end12:25
evrardjpI guess when internal and external vip are different, there are post_ tasks that run after the notify event of the role has been sent12:26
evrardjp(IIRC)12:26
evrardjpanyway I'll check if I could cleanup this haproxy setup12:26
evrardjpto be a better fit with keepalived12:26
*** woodard has quit IRC12:27
*** gparaskevas has joined #openstack-ansible12:27
*** woodard has joined #openstack-ansible12:28
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Allow cinder-backup to use ceph  https://review.openstack.org/20953712:40
*** cfarquhar has quit IRC12:42
svgWould it be possible to add an osad specific topic to http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev? and/or -operators?12:53
*** tlian has joined #openstack-ansible12:54
*** tlian has quit IRC12:54
evrardjpyou think of sending with [OSAD] in title?12:58
odyssey4mesvg just use the tag [openstack-ansible] in your subject line12:58
odyssey4meyou'll find similar tags in the history12:58
svgyes, but given those tags are not registered in mailman, you can't say "I only want those mails"12:59
svgWhich one can at least on the -dev ML for other topics12:59
odyssey4mebenwh4 the ssh issue appears to be related to using too many forks - in 11.1.1 we've included a patch to remove the forks setting in ansible.cfg so that it goes back to the default of 5 (instead of 15)12:59
svgsure, I could handle that with a rule, but doing it it mailman would be cleaner13:00
*** sdake has joined #openstack-ansible13:00
svgodyssey4me: any idea why 15 is too many? I sometimes krank up the forks (for small runs in other projects) and never had an issue with that13:00
*** tlian has joined #openstack-ansible13:00
odyssey4mesvg the two tags mostly used are '[os-ansible-deployment]' and '[openstack-ansible]'13:01
*** ashishb has quit IRC13:02
svgI guess you just proved my point13:02
odyssey4meI use filters to mark emails on -dev and -operators that I'm not interested in as read.13:02
odyssey4mesvg - thw two tags are because we're between names :p13:02
svgThanks for answering, but I already refuted it :)13:03
odyssey4mesvg not sure why 15 forks is too many. I've recently applied the # of forks as being the same as the number of cpu's and that seems to have worked well13:03
odyssey4me(sorry, catching up on backscroll)\13:03
svgmakes sense13:04
evrardjpI've reduced and I have the feeling it's worse than before13:04
odyssey4mehttps://github.com/stackforge/os-ansible-deployment/blob/master/scripts/scripts-library.sh#L2713:04
*** britthouser has joined #openstack-ansible13:05
svgeither way, there is imho no good reason why the number of forks should interfere with connecion timeouts13:05
svg(unless they would be really too big)13:05
odyssey4mebenwh4 how do you mean you have an aio setup running? have you setup a multi-node environment, or an aio environment?13:06
odyssey4mesvg agreed, but after spending several weeks trying to figure it out we eventually have up and implemented the 'successerator' which automatically re-runs the playbooks for the gate check13:06
odyssey4memore recently we reduced the forks, which seems to have reduce the ssh connection failure incidents13:07
svgsure, just saying that sounds like a side effect, not the root cause13:07
odyssey4mewith ansible v2 a patch we PR'd to ansible will have an automated retry in the ssh pipeline which will further reduce the issues13:07
odyssey4meif you can figure out the root cause, that's be awesome :)13:07
*** sdake_ has joined #openstack-ansible13:15
benwh4when I run the setup-hosts playbook I have ...13:18
benwh4ok: [aio1_heat_engine_container-edeb3aaa -> aio1]13:18
*** sdake has quit IRC13:19
benwh4plus ok: [infra3_heat_apis_container-e77f9892 -> infra3]13:19
*** sdake_ has quit IRC13:19
benwh4is it normal to have aio1 running when I want a mutli node target ?13:19
odyssey4mebenwh4 it sounds to me like you've left the aio hosts in your openstack_user_config13:20
odyssey4mewhat branch/tag are you using for your installation?13:21
benwh4I use the master tag13:21
*** leakypipes is now known as jaypipes13:25
*** javeriak has quit IRC13:31
*** Mudpuppy has joined #openstack-ansible13:34
*** markvoelker has joined #openstack-ansible13:35
*** britthou_ has joined #openstack-ansible13:36
*** Mudpuppy has quit IRC13:38
*** britthouser has quit IRC13:39
*** markvoelker has quit IRC13:39
mgariepyodyssey4me, mattt , this patch seems really hard to get through. https://review.openstack.org/#/c/213170/13:46
matttmgariepy: it's not that review specifically13:48
matttwe're seeing a lot of gate failures in master at the minute13:48
*** sdake has joined #openstack-ansible13:49
*** sdake has quit IRC13:49
*** javeriak has joined #openstack-ansible13:49
*** sdake has joined #openstack-ansible13:49
odyssey4mebenwh4 did you copy the aio openstack_user_config for your setup?13:50
odyssey4mebenwh4 essentially https://github.com/stackforge/os-ansible-deployment/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio#L72 the name there is the name referred to for the host which has the IP address of https://github.com/stackforge/os-ansible-deployment/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio#L7713:51
odyssey4methe name can be anything13:51
odyssey4methe playbooks implement /etc/hosts entries for them13:51
benwh4no I used the openstack_user_config.yml not the aio13:52
odyssey4mebenwh4 you should perhaps read through http://osad.readthedocs.org/en/latest/install-guide/configure.html13:52
benwh4I will wait until the playbooks is finish then double check again13:53
odyssey4mebenwh4 well, the aio name will only come from an inventory reference as defined in openstack_user_config.yml - so you must have referred to a host as aio113:53
odyssey4meeither that or you have an inventory with entries from a previous test which has hosts called aio113:53
benwh4ok I will look into to see if I found an aio entry and remove it13:54
odyssey4mebenwh4 you'd have to then use the inventory-manage script to remove the host/containers from the inventory13:55
*** KLevenstein has joined #openstack-ansible14:04
*** woodard has quit IRC14:04
*** woodard has joined #openstack-ansible14:05
*** sdake has quit IRC14:10
*** shoutm has quit IRC14:12
*** sigmavirus24_awa is now known as sigmavirus2414:15
*** sdake has joined #openstack-ansible14:17
sigmavirus24mornings all14:19
*** Mudpuppy has joined #openstack-ansible14:19
svgGood afternoon sigmavirus24  :)14:24
sigmavirus24How're you svg?14:25
svgchilling! and you?14:25
*** phalmos has joined #openstack-ansible14:26
*** gparaskevas has quit IRC14:26
odyssey4meandymccr mattt sigmavirus24 palendae d34dh0r53 please review this backport asap https://review.openstack.org/21344214:28
odyssey4methen the SHA update to follow it: https://review.openstack.org/21343914:29
*** jwagner is now known as jwagner_away14:30
sigmavirus24odyssey4me: lolno =P14:30
matttodyssey4me: your wife must love you14:31
mattti'll have some tea, LIKE RIGHT THIS SECOND14:31
svg8-|14:31
evrardjp:)14:31
evrardjptoo much redbull14:31
odyssey4mehahaha14:31
odyssey4meoooh evrardjp  good idea!14:32
evrardjpbut he gets results!14:32
matttsvg: you back to work this week?  :)14:32
svgnope14:32
svgthe problem is, I have wifi here14:32
evrardjpbad idea!14:32
evrardjpbut it's in france, it doesn't mean that you'll have decent uplink to the interwebz14:32
matttsvg: still raining this week?14:32
svgbut, but, the pool water is too damn cold today!14:33
svgno, but cloudy14:33
evrardjpam I the only one to think that haproxy should be restarted only when it could bind to its correct ip address ?14:33
evrardjp(so I plan to remove all the handlers "restart haproxy" and create a task that checks if haproxy could bind, and then only restart14:34
evrardjp)14:34
*** javeriak has quit IRC14:37
mgariepyis there documentation somewhere to add external network in osad ?14:37
*** britthou_ has quit IRC14:39
*** britthouser has joined #openstack-ansible14:39
odyssey4memgariepy like http://osad.readthedocs.org/en/latest/install-guide/targethosts-network.html and http://osad.readthedocs.org/en/latest/install-guide/configure-networking.html perhaps?14:40
mgariepyodyssey4me, well, br-vlan/vxlan are there to host the tenant networks, i would like to know how to add the "external network"14:44
mgariepyi guess that i need to add a network on neutron_linuxbridge_agent, to be able to assign floating ips to routers and tenants vms.14:44
odyssey4memgariepy Sam-I-Am can likely help14:44
odyssey4meI think it's typically done by adding a flat network, but it all depends on how you want to do it really14:45
mgariepybasicly : br-ex on hosts > ethX interface in neutron containers.14:46
mgariepydoes linuxbridge allow to use DVR with neutron ?14:47
*** phalmos has quit IRC14:49
odyssey4memgariepy as I recall DVR is still somewhat broken in Kilo when using linuxbridge - there are upstream efforts to make it work better14:49
odyssey4medon't quote me on that though, I'm not the expert on anything neutron14:50
*** markvoelker has joined #openstack-ansible14:51
mgariepylol ok14:51
sigmavirus24odyssey4me: I'm reviewing your backport now that I'm off that video call14:55
*** markvoelker has quit IRC14:55
mgariepyodyssey4me,  is the comment: 'recheck test_volumes_backup.VolumesBackupsV1Test,test_minimum_basic_scenario' remove the "VolumesBackupsV1Test" tempest check from the gate-os-ansible-deployment-dsvm-commit ?14:58
odyssey4memgariepy nope, it's just a note on why the recheck is being done - the words after 'recheck' are a comment so that we can see if there's a pattern14:58
palendaemattt: No, that won't remove it. 'recheck' triggers the whole test suite to recheck, that's just a note14:58
odyssey4meclearly there is, so we need to figure out why the volume backup test is failing14:58
mgariepyi saw that https://review.openstack.org/#/c/211543/ had the same issue, and when jenkins recheck it, this test wasn't included.15:00
palendaeInteresting15:00
*** phalmos has joined #openstack-ansible15:00
odyssey4memgariepy the volumev1test was included: http://logs.openstack.org/43/211543/3/check/gate-os-ansible-deployment-dsvm-commit/e908b51/console.html.gz#_2015-08-13_15_10_02_59915:01
*** KLevenstein has quit IRC15:02
*** KLevenstein has joined #openstack-ansible15:03
benwh4how do you use the inventory-manage.py ?15:05
*** KLevenstein has quit IRC15:07
matttbenwh4: you can run it without args, it will spit out some help15:07
mgariepyhmm looks like i misread the logs..15:08
matttbenwh4: essentially, there's --list to list what's in your inventory, or --remove to remove entries15:08
evrardjpso odyssey4me: are you interested by a conditional restart of haproxy instead of a definitive restart?15:14
*** KLevenstein has joined #openstack-ansible15:14
odyssey4meevrardjp sure, although I'm more interested in haproxy's services being able to be configured/deconfigured for various deployments.15:15
*** markvoelker has joined #openstack-ansible15:15
odyssey4meie If I'm doing a swift-only deployment, I'd like haproxy to only deploy configuration for the services that are in the environment.15:15
evrardjpdamn that was what I dropped15:17
*** spotz_zzz is now known as spotz15:17
*** javeriak has joined #openstack-ansible15:20
*** javeriak has quit IRC15:25
*** javeriak has joined #openstack-ansible15:25
odyssey4meevrardjp as a separate patch I'd like to see the ability to deploy user-provided certificates for HAproxy - similar to how we do it for Horizon15:26
odyssey4meand yes, high availability would be nice - especially if haproxy only runs on the host being used at the time (ie it shuts down when not in use) so that it reduces the log noise from the service up checks15:27
*** javeriak_ has joined #openstack-ansible15:29
*** javeriak has quit IRC15:30
evrardjpodyssey4me: how would you see that a component is enabled or not? based on the presence of a valid file in env.d, or in a user_variable?15:41
evrardjpconf.d not env.d15:41
palendaeevrardjp: Generally, we've been detecting whether or not the hosts/containers are defined for it15:41
evrardjpso based on inventory15:42
palendaeYes15:42
palendaeLet me find an example15:42
odyssey4meevrardjp yeah, inventory would seem to be a good option - however that only caters for something that's already defined in vars/haproxy15:42
odyssey4mewhat about when we want to add a new service, for example elasticsearch15:43
odyssey4mewe need to define the confgs for the LB for that service, but also only implement the config if there's a container in the inventory for it15:43
evrardjpI should create a blueprint first, this way we can think of how we do it, right?15:43
palendaeodyssey4me: RPC implements elasticsearch as a new container/in inventory...15:43
palendaeevrardjp: Yeah, that'd be ideal15:43
odyssey4mepalendae yes, but it implements the LB for elasticsearch through a hack15:44
palendaeAh15:44
odyssey4meit doesn't use the current haproxy role15:44
palendaeWe should unhack that :)15:44
palendaeOh, no15:44
palendaeBecause RPC assumes F5s15:44
palendaeBecause there's some bias against haproxy15:44
odyssey4mesure, but that functionality is something we need15:44
palendaeI agree15:44
odyssey4mefor dev/test purposes and for gating15:44
palendaeFair enough15:44
evrardjpthis could make it provider independant15:45
evrardjpok15:45
palendaeevrardjp: yeah, I'd say BP it15:45
odyssey4meevrardjp I would suggest trying to work up a prototype to figure out how much needs to change15:45
palendaeodyssey4me: If you don't have any high priority reviews, I'm gonna look at BPs to review15:45
odyssey4methen write a blueprint based on your PoC and within the spec we can debate the merits of the approach and if anyone objects they can suggest an alternative15:45
odyssey4mepalendae uh https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment,n,z15:46
palendaeThanks15:46
evrardjpa lot, compared to the current role, but this isn't something really difficult I'd say15:46
odyssey4meI would recommend ignoring the build success/failure at this point - most of them are unrelated to the patch15:46
odyssey4mepalendae there are a lot of small reviews in flight, so once you've tackled the starred ones then feel free to just run through the normal list15:48
odyssey4mewe're well behind :/15:48
palendaeI know15:48
palendaeWe're behind all round15:48
*** benwh4 has quit IRC15:52
*** b3rnard0 is now known as b3rnard0_away4de15:54
*** woodard has quit IRC15:56
*** woodard has joined #openstack-ansible16:00
openstackgerritMerged stackforge/os-ansible-deployment: Add iptables rule to neutron agents containers  https://review.openstack.org/21344216:00
*** yaya has joined #openstack-ansible16:01
*** yaya has quit IRC16:02
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Enable debug logging for gate checks  https://review.openstack.org/21343816:03
*** yaya has joined #openstack-ansible16:04
*** alop has joined #openstack-ansible16:08
*** daneyon has quit IRC16:30
*** daneyon has joined #openstack-ansible16:30
*** ashishb has joined #openstack-ansible16:39
*** woodard has quit IRC16:42
*** c0m0 has quit IRC16:45
*** b3rnard0_away4de is now known as b3rnard016:45
*** vdo has quit IRC16:46
*** woodard has joined #openstack-ansible16:46
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment-specs: Add spec for Independent Role Repositories  https://review.openstack.org/21377916:48
palendaeodyssey4me: So, I feel weird voting on https://review.openstack.org/#/c/212919/ :p16:48
odyssey4melol - well, I took it over from you - note that if you like?16:48
palendaeYep16:49
odyssey4mepalendae ^ spec for your reading pleasure :)16:49
*** woodard has quit IRC16:50
*** woodard has joined #openstack-ansible16:52
openstackgerritMerged stackforge/os-ansible-deployment: Adds a pep8 target to tox.ini  https://review.openstack.org/20766216:53
*** javeriak has joined #openstack-ansible16:56
*** javeriak_ has quit IRC16:57
*** sdake_ has joined #openstack-ansible17:20
*** sdake has quit IRC17:24
*** sdake has joined #openstack-ansible17:31
*** sdake_ has quit IRC17:35
*** wmlynch has joined #openstack-ansible17:35
*** woodard has quit IRC17:40
*** javeriak_ has joined #openstack-ansible17:40
*** javeriak has quit IRC17:41
*** woodard has joined #openstack-ansible17:46
*** jwagner_away is now known as jwagner17:46
*** yaya has quit IRC18:05
*** woodard has quit IRC18:11
*** ashishb has quit IRC18:21
*** prometheanfire has quit IRC18:32
*** prometheanfire has joined #openstack-ansible18:32
*** d34dh0r53 is now known as VD18:42
*** britthou_ has joined #openstack-ansible18:43
*** VD is now known as Guest6944218:43
*** britthouser has quit IRC18:45
*** Guest69442 is now known as d34dh0r5318:47
*** jmccrory has quit IRC19:12
*** yaya has joined #openstack-ansible19:34
*** woodard has joined #openstack-ansible19:42
*** yaya has quit IRC19:56
*** KLevenstein has quit IRC19:59
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Keystone SSL cert/key distribution and configuration  https://review.openstack.org/19447419:59
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Removes trailing whitespace for bashate  https://review.openstack.org/20766320:06
openstackgerritMerged stackforge/os-ansible-deployment: Replace ADFS example DNS name with something appropriate  https://review.openstack.org/21110220:09
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Use slurp to get the content of the ceph.conf file  https://review.openstack.org/21317020:10
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Allow cinder-backup to use ceph  https://review.openstack.org/20953720:13
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add nova_libvirt_live_migration_flag variable  https://review.openstack.org/21245220:13
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Implement /usr/bin/env as the shebang in all bash scripts  https://review.openstack.org/21188520:14
*** daneyon has quit IRC20:14
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add support for additional nova.conf options  https://review.openstack.org/21049220:15
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Update the documented ceph user variables  https://review.openstack.org/20913020:15
*** spotz is now known as spotz_zzz20:28
*** yaya has joined #openstack-ansible20:29
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Update SHAs for kilo development  https://review.openstack.org/21385320:35
ApsuSo many reviews omgherd20:48
*** javeriak_ has quit IRC20:52
*** Mudpuppy has quit IRC20:55
sigmavirus24lol20:55
*** Mudpuppy has joined #openstack-ansible21:01
*** Mudpuppy has quit IRC21:05
*** britthou_ has quit IRC21:14
*** woodard_ has joined #openstack-ansible21:14
*** woodard has quit IRC21:17
*** woodard_ has quit IRC21:18
*** Mudpuppy has joined #openstack-ansible21:29
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Update SHAs for kilo development  https://review.openstack.org/21385321:32
*** shackit has quit IRC21:43
*** Mudpuppy has quit IRC21:45
*** tlian has quit IRC22:04
*** shoutm has joined #openstack-ansible22:06
*** sdake_ has joined #openstack-ansible22:10
*** sdake has quit IRC22:13
*** JRobinson__ has joined #openstack-ansible22:23
*** shoutm has quit IRC22:32
*** yaya has quit IRC22:32
*** shoutm has joined #openstack-ansible22:36
*** markvoelker has quit IRC22:51
*** sdake_ is now known as sdake23:01
*** sdake_ has joined #openstack-ansible23:22
*** sdake has quit IRC23:26
*** jwagner is now known as jwagner_away23:32
*** markvoelker has joined #openstack-ansible23:35
*** phalmos has quit IRC23:47
*** JRobinson__ has quit IRC23:52
*** britthouser has joined #openstack-ansible23:57
*** britthou_ has joined #openstack-ansible23:58

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