Wednesday, 2015-09-09

mrstanwellmulti-projection00:02
*** markvoelker has quit IRC00:10
*** mrstanwell has quit IRC00:13
*** shoutm has quit IRC00:18
*** shoutm has joined #openstack-ansible00:21
*** markvoelker has joined #openstack-ansible00:31
*** shoutm_ has joined #openstack-ansible00:38
*** shoutm has quit IRC00:40
openstackgerritMerged stackforge/os-ansible-deployment: Update tempest configuration  https://review.openstack.org/22055900:44
*** BjoernT has quit IRC00:44
*** abitha has quit IRC00:45
*** spotz_zzz has quit IRC00:47
*** lbragstad has quit IRC00:48
*** palendae has quit IRC00:48
*** eglute_s has quit IRC00:48
*** gus has quit IRC00:48
*** neillc has quit IRC00:48
*** darrenc has quit IRC00:48
*** Guest75828 has quit IRC00:48
*** mattoliverau has quit IRC00:48
*** bgmccollum has quit IRC00:49
*** darrenc has joined #openstack-ansible00:49
*** sigmavirus24_awa has quit IRC00:49
*** dolphm has quit IRC00:49
*** shoutm_ has quit IRC00:50
*** shoutm has joined #openstack-ansible00:50
*** d34dh0r53 has quit IRC00:50
*** jroll has quit IRC00:50
*** neillc has joined #openstack-ansible00:50
*** mgagne has quit IRC00:50
*** mattoliverau has joined #openstack-ansible00:51
*** gus has joined #openstack-ansible00:51
*** metral is now known as metral_zzz00:51
*** blewis has joined #openstack-ansible00:53
*** spotz_zzz has joined #openstack-ansible00:53
*** jroll has joined #openstack-ansible00:53
*** d34dh0r53 has joined #openstack-ansible00:53
*** eglute has joined #openstack-ansible00:53
*** blewis is now known as Guest1849900:53
*** bgmccollum has joined #openstack-ansible00:54
*** mgagne has joined #openstack-ansible00:54
*** palendae has joined #openstack-ansible00:54
*** lbragstad has joined #openstack-ansible00:54
*** dolphm has joined #openstack-ansible00:54
*** metral_zzz is now known as metral00:55
*** sigmavirus24_awa has joined #openstack-ansible00:57
*** metral is now known as metral_zzz00:57
*** metral_zzz is now known as metral01:08
*** alop has quit IRC01:32
openstackgerritMiguel Grinberg proposed stackforge/os-ansible-deployment: Fix the heat stack user create  https://review.openstack.org/21818401:34
*** darrenc is now known as darrenc_afk01:42
*** sdake_ is now known as sdake02:06
*** darrenc_afk is now known as darrenc02:17
*** sdake_ has joined #openstack-ansible02:25
*** sdake has quit IRC02:29
*** markvoelker has quit IRC02:31
*** sdake has joined #openstack-ansible02:32
*** sdake_ has quit IRC02:35
*** Apsu has quit IRC02:37
*** Apsu has joined #openstack-ansible02:37
*** Apsu has quit IRC02:39
*** Apsu has joined #openstack-ansible02:40
*** shoutm has quit IRC02:55
*** shoutm has joined #openstack-ansible03:06
*** bgmccollum has quit IRC03:29
*** markvoelker has joined #openstack-ansible03:31
*** dolphm has quit IRC03:33
*** sdake_ has joined #openstack-ansible03:34
*** sdake has quit IRC03:35
*** sdake has joined #openstack-ansible03:35
*** markvoelker has quit IRC03:36
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Create config_template plugin  https://review.openstack.org/22021203:37
*** dolphm has joined #openstack-ansible03:38
*** bgmccollum has joined #openstack-ansible03:38
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Replaced the copy_update module  https://review.openstack.org/21679003:38
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Adds the config_template to ceilometer  https://review.openstack.org/21703003:39
*** sdake_ has quit IRC03:39
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Create config_template plugin  https://review.openstack.org/22021203:41
coolj<3 cloudnull03:42
cloudnullsay what ?03:42
coolj^ comfig_template proposals03:42
cooljconfig even03:42
cloudnullha. ya, hopfully coming soon.03:45
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Replaced the copy_update module  https://review.openstack.org/21679003:45
cloudnullif you have some spare cycles I'd love some review on that03:45
cooljrelatives coming to town and am gonna be out a couple days, but i might have some time at night. i would love to check it out03:46
cloudnullplease do and feel free to ping me if you have questions.03:52
cooljcool, will do!03:58
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Replaced the copy_update module  https://review.openstack.org/21679004:00
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Replaced the copy_update module  https://review.openstack.org/21679004:02
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Adds the config_template to OpenStack Services  https://review.openstack.org/21703004:09
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Added in keystone reserved port  https://review.openstack.org/19670204:17
*** shoutm has quit IRC05:01
*** shoutm has joined #openstack-ansible05:05
*** tlian2 has quit IRC05:12
*** shoutm has quit IRC05:22
*** markvoelker has joined #openstack-ansible05:32
*** markvoelker has quit IRC05:37
openstackgerritMiguel Grinberg proposed stackforge/os-ansible-deployment: Fix the heat stack user create  https://review.openstack.org/21818405:56
*** shoutm has joined #openstack-ansible06:13
openstackgerritMerged stackforge/os-ansible-deployment: Changed certificate order for pem generation with CA files  https://review.openstack.org/22136106:19
openstackgerritMerged stackforge/os-ansible-deployment: Set the Ubuntu mirror used based on the environment  https://review.openstack.org/21861106:19
*** cristicalin has joined #openstack-ansible06:24
*** javeriak has joined #openstack-ansible06:39
*** javeriak has quit IRC06:40
*** shausy has joined #openstack-ansible06:55
*** javeriak has joined #openstack-ansible07:09
*** sdake_ has joined #openstack-ansible07:23
*** javeriak has quit IRC07:25
*** sdake has quit IRC07:27
*** shoutm has quit IRC07:28
*** shoutm has joined #openstack-ansible07:29
*** shoutm_ has joined #openstack-ansible07:31
*** shoutm has quit IRC07:33
*** markvoelker has joined #openstack-ansible07:33
*** sdake has joined #openstack-ansible07:36
*** markvoelker has quit IRC07:38
*** gparaskevas has joined #openstack-ansible07:39
*** sdake_ has quit IRC07:39
*** javeriak has joined #openstack-ansible07:58
*** shoutm has joined #openstack-ansible08:21
*** shoutm_ has quit IRC08:24
*** javeriak has quit IRC08:26
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Create config_template plugin  https://review.openstack.org/22021208:30
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Fix of haproxy ssl misconfiguration with nova_console  https://review.openstack.org/22138608:30
evrardjpgood morning08:30
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Replaced the copy_update module  https://review.openstack.org/21679008:31
evrardjpI'm deploying a new version of our cloud, but I have weird issues08:31
evrardjpthe flush net cache fails for the memcached containers in setup infrastructure08:31
evrardjpif I'm manually connecting to ssh on the hosts with the ipv4 or ipv6, it doesn't seem to be an issue08:32
evrardjphas anyone experienced this?08:32
evrardjp(I even restarted setup-hosts to make sure my containers are fine, no change)08:33
evrardjpadding verbosity just show me "ssh error: data could not be sent to the remote host"08:33
odyssey4memorning evrardjp08:37
odyssey4meevrardjp that's not the first time I'm hearing that in the last few days08:38
odyssey4meare you using run-playbooks, or are you running plays directly?08:38
evrardjpsetup-* playbooks08:38
evrardjphere it's the setup-infrastructure08:39
odyssey4meok, is that with or without the repo-sync?08:39
evrardjpI'll check with the first one if it08:39
odyssey4meie are you using repo-build instead of repo-sync?08:39
evrardjpI'm even to that point08:39
odyssey4meour kilo branch currently does repo-sync, and I think our upstream repo needs an update with the most recent merges08:39
evrardjpI'm at memcached-install08:40
evrardjpI'm not even to that point*08:40
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Shift irqbalance package from lxc_hosts to openstack_hosts  https://review.openstack.org/21835408:40
odyssey4meodd, ok have you set FORKS at all, or are you using the default value?08:41
evrardjpdefault08:41
evrardjpbut08:42
evrardjpI added ssh_delay08:42
evrardjpI'll remove it, just to see what it changes08:42
evrardjpdoesn't change anything... It's maybe a network issue at my side, but then I don't understand why I don't have issues connecting with ssh to the host08:43
odyssey4messh_delay just changes the amount of time it waits before testing for the ssh connection08:43
evrardjpyeah I removed it, just in case08:43
odyssey4mewhat did you have it set to?08:44
matttdoes anyone want to comment on https://review.openstack.org/#/c/220050/ ?08:45
evrardjpit was 5, but it doesn't change anything08:46
evrardjpmattt: I'll check08:46
matttif there is enough agreement w/ kevin we may need to unwind the commits in juno/master08:46
matttevrardjp: thanks!08:47
matttit _seems_ easier to let global-requirements do the work, but perhaps there may be issues resulting from that08:48
evrardjpmattt: can we rely on these upstream changes? or if not, is there a way to override ?08:48
odyssey4memattt so in my opinion allowing global requirements to manage it still puts us in a situation where it is a known version - because it's a sha fixed version of global requirements08:48
evrardjpit's true08:48
evrardjpbut it doesn't mean that we want to consume exactly the same version08:48
matttevrardjp: of course there will be situations where global-requirements will be wrong08:49
matttevrardjp: but we can certainly work around these situations by pinning a specific client08:49
odyssey4methis mechanism puts us in a position where we have to manage less - note that I proposed that mechanism to solve another issue which we got into because we weren't doing this08:49
evrardjpwhat I don't see in the commit, is the impact on the other containers, like the utility containers08:49
odyssey4meevrardjp the only impact is the version of the client installed08:49
evrardjpI mean, does it work directly?08:50
odyssey4medirectly?08:50
odyssey4mewhen repo-build is run, it collects all the requirements and builds the repo based on the most common versions required08:51
matttodyssey4me: yeah, i'm not opposed to this, i think the less moving pieces on our part the better08:51
odyssey4meso every client (except in the tempest venv) is the same version08:51
evrardjpmattt: I agree08:51
evrardjpI just think an override of clients could be nice08:51
mattti just figured it would be good to get more input incase people disagreed with what has been done in juno/master, so we can hold this review going through and unwind the other branches08:52
evrardjpI'll check the repo-build again08:52
odyssey4meevrardjp we can easily override the global requirements to include a specific client or library version if we need to - we do that from time to time to work around upstream issues or to ensure that we have a version of something that includes a fix we need.08:53
evrardjpodyssey4me: yeah, I remember that happened in the past... I just wanted to make sure the opportunity still exists, because it's really good :)08:54
matttodyssey4me: i've not tested and don't know the repo building stuff well enough, but can you just drop the necessary entries into your user_variables.yml and have that work?08:54
evrardjpmattt: I'm not expert enough to give my review on it... but I guess it's ok08:55
matttevrardjp: i have a feeling that's not going to work, since the repo building stuff happens inside a container and wouldn't know of those variables outside08:55
odyssey4memattt no, the repo is built from in-tree values at this stage - we could perhaps include some way of allowing user-based overrides08:55
odyssey4megotta run for a hair cut - bbiab08:56
matttnjoy08:56
evrardjpit's not that I require this08:56
evrardjphave fun!08:56
matttevrardjp: it sounds like a handy feature, but perhaps no point crafting solutions until we know it's actually necessary!08:57
evrardjpyeah08:57
evrardjpI remember a time we had a messup with the versions08:57
evrardjpso I thought an override of clients versions is always good08:57
evrardjpI trust the kilo build we are making, so I guess it's not really an issue for me08:58
evrardjpanyway, I'll continue on my issue08:58
evrardjp(sorry to be selfish ;) )08:59
*** markvoelker has joined #openstack-ansible09:04
*** markvoelker has quit IRC09:08
evrardjphow come the teardown.sh is working fine, while the memcached-install can't even connect to my hosts when doing the flush net cache???09:12
odyssey4meteardown only deals with the hosts09:33
odyssey4meso the flush net cache is causing connections to hosts to fail?09:34
odyssey4methat's odd, because the flush net cache action is delegated to the host09:34
odyssey4meevrardjp can you please backport https://review.openstack.org/221361 to kilo?09:35
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Set the Ubuntu mirror used based on the environment  https://review.openstack.org/22166609:35
evrardjpif you allow me to merge that one before09:36
evrardjphttps://review.openstack.org/#/c/215525/09:36
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Adds the ability to provide user certificates to HAProxy  https://review.openstack.org/22166709:39
odyssey4mehughsaunders can you please backport https://review.openstack.org/217310 to kilo now that its dependent changes are merged09:39
hughsaundersyep09:40
odyssey4meevrardjp ah, you need https://review.openstack.org/221667 in before https://review.openstack.org/22136109:41
evrardjpyes, I'm looking again at what you explained me before09:41
evrardjpthe dependencies09:41
openstackgerritHugh Saunders proposed stackforge/os-ansible-deployment: Add variable for cirros url  https://review.openstack.org/22166909:42
evrardjplet me try it again09:42
odyssey4meif you do 'git review -d 221667', then 'git checkout -b kilo_bug/1493421', then cherry pick -x https://review.openstack.org/221361 then git review that, it'll mark the patches as dependent09:42
evrardjpok09:46
evrardjpI was there: https://www.mediawiki.org/wiki/Gerrit/Advanced_usage#Create_a_dependency09:46
evrardjpbut I have an issue, I can't do the git review -d...  FETCH_HEAD being ambiguous09:56
evrardjpit's maybe because 221667 already has a dependency ?09:57
odyssey4meyou get an error when doing 'git review -d 221667' ?09:58
odyssey4meor when doing the cherry-pick?09:58
evrardjpwhen doing the git review10:00
evrardjpshould I be on some branch?10:00
evrardjpfor example a new branch, before doing the git review -d?10:01
odyssey4meevrardjp nope, it'll effectively do a checkout with all the extra metadata10:01
evrardjpok10:01
evrardjpthat's what I thought10:01
odyssey4meyou should probably do a 'git fetch gerrit' first though, or checkout to master and git pull10:01
evrardjpI did a git fetch --all10:02
evrardjpand did that too10:03
odyssey4meevrardjp odd10:04
odyssey4metry a fresh clone to a different folder, run git review -s to setup gerrit, then try again?10:04
evrardjpgit pull tells me "already up to date"10:04
evrardjpyeah will try that10:05
*** javeriak has joined #openstack-ansible10:05
evrardjpseems better10:06
evrardjpdon't know why10:06
evrardjpno pending changes on my environments10:06
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Changed certificate order for pem generation with CA files  https://review.openstack.org/22168210:09
evrardjpI like gerrit :)10:09
odyssey4meevrardjp it may be that you have another branch with the same change id or something10:10
evrardjpshould I kill my old folder?10:11
*** arbrandes1 has joined #openstack-ansible10:24
*** logan2 has quit IRC10:24
odyssey4meevrardjp that's up to you - I do that often :)10:25
odyssey4mefyi evrardjp https://bugs.launchpad.net/openstack-ansible/+bug/148945110:25
openstackLaunchpad bug 1489451 in openstack-ansible "Not able to connect memcached_container while running setup-infrastructure.yml " [Undecided,New]10:25
*** logan2 has joined #openstack-ansible10:28
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Fix the heat stack user create  https://review.openstack.org/21818410:29
*** markvoelker has joined #openstack-ansible11:04
*** markvoelker has quit IRC11:09
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Ensure cinder-backup-related variables are defined  https://review.openstack.org/22170511:14
evrardjpodyssey4me: thanks, but I think I found my issue(s)11:21
evrardjpfirst, the number of forks11:21
evrardjpreduced to 5 it works flawlessly (so far less than the amount of my destination available cpus)11:21
evrardjpsecond, I've regenerated ssh_keys on each of my physical_hosts11:22
evrardjp(if you follow the documentation, they key generation happen automatically when installing openssh server)11:23
evrardjpthird, I've found that my inventory had an issue with used_ips: used_ips doesn't count the host that deploys the cloud ;)11:23
odyssey4meevrardjp ah, nice - perhaps you can add those notes to the bug I pointed out?11:26
evrardjpIt looks unrelated... it looks a python issue, mine is just ... my mess up ;)11:28
evrardjpbut I could add a comment on the doc11:28
odyssey4meevrardjp I've seen this reported more than once recently, so everyone's experience and solutions can help us figure it out11:28
evrardjpmentionning that you should put the deploy hosts in the used_ips (although this is obvious) could be good in the doc11:29
evrardjpwhat do you think?11:29
odyssey4meagreed :)11:30
evrardjpodyssey4me: it's not because the result is the same that the cause is the same... so I'm not sure commenting unrelated stuff on the bug would help the others in the future11:30
evrardjpok I'll write something on the doc11:30
odyssey4meevrardjp so while doing the python thing worked for the bug author, it's not something that others seeing the same issue have been able to replicate - but others are seeing the same result without the same solution11:31
evrardjpyeah, I think we should pay more attention the causes, and mentionning them somewhere... probably in the doc11:32
evrardjp'known issues'11:33
evrardjpif it's not really known, then it's a bu11:33
evrardjpbug*11:33
odyssey4megood idea11:33
evrardjpnew bugs are fine, right?11:33
evrardjp:D11:33
*** logan2 has quit IRC11:38
openstackgerritMerged stackforge/os-ansible-deployment: Updated the configuration to current dynamic inventory standards  https://review.openstack.org/22140211:40
*** logan2 has joined #openstack-ansible11:40
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Be more clear about used_ips, mostly in the example file  https://review.openstack.org/22171311:43
javeriakhey guys, odyssey4me. I'm about to port these changes to kilo: https://review.openstack.org/#/c/184665/8 . Wanted to ask if there were any other things I should take into consideration since kilo is the main active OSAD branch?11:46
mgariepygood morning everyone !11:47
javeriakI can see that kilo already provides the capability to enable/disable neutron agent services, I'd like to apply that option to the neutron agent deploying playbooks as well.11:47
evrardjpgood morning mgariepy11:49
*** logan2 has quit IRC11:50
mgariepyhow are you doing evrardjp ?11:50
odyssey4mejaveriak I would suggest that the work be done to get that included in master first. The playbooks and roles are almost the same at this stage - but it's important that any new feature work is done against master first, before backporting to kilo.11:51
evrardjpmgariepy: fine, deploying to prod now, and you?11:51
javeriakodyssey4me, okay sounds good11:52
odyssey4mejaveriak the only complexity is that master is running Liberty-3 code, so you might encounter some implementation differences11:52
javeriakodyssey4me, are there any deployment complexities for master? as in can i use that branch to setup a new cluster?11:53
mgariepyi'm doing fine.11:53
mgariepyi have issue with keepalived tho ;)11:53
evrardjpoh?11:53
evrardjpwhat happened?11:53
mgariepywhen a server is in backup mode why does haproxy does have to be stopped ?11:54
evrardjpin order to reduce backend checks11:54
odyssey4mejaveriak yes, you can use it to deploy a new cluster - if you find any issues we'd like to know!11:54
evrardjpmgariepy: it's not mandatory11:54
evrardjpyou can use another notification script11:54
*** logan2 has joined #openstack-ansible11:54
javeriakcool :). btw do i need to update my relevant BP?11:54
odyssey4mejaveriak this is all part of the preparation work to release liberty, so any issues discovered would be great to know (bugs) and great to have patches for :)11:54
mgariepyyeah but if it's stopped the killall -0 haproxy result in faulty state ;)11:55
evrardjpit does, but normally my script checks the state11:55
evrardjpprevious state11:55
evrardjpso at some point you can restore from fault state11:56
odyssey4mejaveriak considering that your blueprint was implemented some time ago, I think it'd be best to register a new one for the liberty cycle, assuming you'll be able to get the work completed within the next few weeks?11:56
evrardjpand understand it's a backup status11:56
evrardjpbut if you prefer using a simpler approach, it would also work... you just have to let haproxy run all the time11:56
evrardjp(which is perfecly fine)11:56
javeriakodyssey4me  sure, will do. btw any ETA when kilo becomes rackspace11 officially?11:57
odyssey4mejaveriak I expect that you could largely copy the old spec and just update it - this time you won't need to refer to branch names... just focus on the planning to implement it - the decision to backport the feature to kilo is something that comes after it's implemented into master11:57
mgariepyyeah but the issue i have is if my server is backup + haproxy stopped, when it need to switch to master, it fails because haproxy is not running.11:57
evrardjpmgariepy: that shouldn't happen11:58
mgariepyi might be missing something tho..11:58
odyssey4mejaveriak RPC11's release is imminent, so I expect that with your feature it'd come in a minor point release rather than initial release11:58
evrardjpmgariepy: if he needs to switch to master, it checks the old state when transitionning11:58
evrardjpgo through faulty, and then immediately master11:59
evrardjpthat's what I see here11:59
javeriakodyssey4me, also you guys seem to have taken out the CloudFiles backend setup doc from kilo; are the rackspace_cloud_* parameters still relevant for uservariables.yml ?11:59
evrardjpbut I can check with you if you want11:59
odyssey4mejaveriak it would be great if you guys could setup some sort of External CI for commit tests to verify whether patches in the project affect the code paths for PlumGrid11:59
odyssey4mejaveriak yeah, afaik it's still possible to use them - the docs just need revision12:00
odyssey4methe variable names may be different though12:00
evrardjpmy clean install just went from fault (after installing keepalived without haproxy) to master/backup (after the completion of the haproxy playbook)12:02
evrardjpI'm killing now master12:02
mgariepyevrardjp, haproxy is running ?12:02
evrardjpstate changed from backup to master12:02
evrardjpmgariepy: it wasn't running on my backup12:02
*** markvoelker has joined #openstack-ansible12:02
evrardjpmmm12:03
mgariepywhen i start keepalived, if haproxy is not running it's going into fault state.12:03
mgariepywhen i start haproxy it goes to backup12:03
javeriakodyssey4me, yes work should complete latest by two week, its being chased actively. As far as the CI is concerned, yes we've started an internal effort for setting up a jenkins pipeline for OSAD. where its going to be run is being discussed with your folks too12:04
mgariepyif haproxy is stopped , it's stays backup, but when the master dies, it goest to fault.12:04
evrardjpok will try12:04
odyssey4mejaveriak good news :)12:05
javeriakwill get back to you guys with some more questions I'm going to have for kilo PLUMgrid support. Our package requirements change slightly for kilo..12:08
evrardjpmgariepy: sadly someone toyed with my LB server just right now12:08
evrardjpso the only thing I can tell you, is that the backup went to master ;)12:08
mgariepywell i  think i found the issue ;)12:08
evrardjpyup?12:09
evrardjpwhat's that?12:09
*** woodard has joined #openstack-ansible12:09
mgariepythe if statement to check if the state was Fault, is not right ;)12:12
mgariepyif []; then, after this , -ne is supposed to be used to compare int not strings ;)12:12
mgariepybut it's not working anyway:s12:13
mgariepythe only way i have to switch to backup to master is to have haproxy running.12:14
*** logan2 has quit IRC12:17
*** woodard has quit IRC12:20
*** logan2 has joined #openstack-ansible12:20
*** woodard has joined #openstack-ansible12:22
*** javeriak has quit IRC12:28
evrardjpwe should maybe simplify this12:31
evrardjplet me get my load balancer back from maintenance and I'll check with you12:31
evrardjpsome stuff always happen at the wrong time :/12:31
mgariepyhaha indeed12:31
evrardjpgood disk was switched with replacement disk instead of the bad disk :D12:33
*** shausy has quit IRC12:33
*** shausy has joined #openstack-ansible12:33
mgariepyevrardjp, jinja lstrip : http://paste.ubuntu.com/12320472/12:35
mgariepythis way jinja2 block won't produce whitespace in the rendered file12:35
evrardjpdoes this change something?12:37
mgariepynot for the behavior , just make the keepalived.conf file readable.12:37
evrardjpor it's because the jinja is ugly?12:37
evrardjpfile*12:37
evrardjpyeah ok12:37
mgariepyevery "  {% if..." will print 2 spaces in the file.12:38
odyssey4memgariepy you can also do "  {%- if ..."12:38
*** javeriak has joined #openstack-ansible12:38
odyssey4methat strips the whitespace to the left12:38
mgariepyodyssey4me, yeah but when you have 25 blocks.. is better a new line in top of the line ;)12:39
odyssey4memgariepy does it respect the whitespace you actually want though?12:39
mgariepyit only lstrip  whitespace in front of block.12:39
odyssey4megood to know :)12:40
mgariepyit the equivalent of putting - in all the blocks.12:41
*** logan2 has quit IRC12:41
*** logan2 has joined #openstack-ansible12:42
evrardjpmgariepy: you were right, haproxy needs to run at all times12:44
evrardjpat least that's what it seems12:45
evrardjpI'll check because I think this was fixed with the state checking12:48
evrardjpit's maybe because we are trying to simulate too fast12:48
mgariepymaybe.12:49
mgariepythe script is triggered only when a check script state changes ?12:50
evrardjpyup12:50
evrardjpwhat would be best is to have the old state12:50
evrardjpin this notify script12:51
evrardjpinstead of only the new state12:51
evrardjpwhat I did is just a workaround12:51
openstackgerritMajor Hayden proposed stackforge/os-ansible-deployment: Add profiling for Ansible tasks  https://review.openstack.org/21684912:52
mgariepyhaproxy_check script should look in the state file and check haproxy only if it is in master state ?12:53
mhaydenjust rebased and killed the conflict ^^12:53
evrardjpmgariepy: that would be a solution12:55
mgariepyor another hack haha12:55
evrardjp:)12:56
evrardjpthe fact is, I didn't try that someone would kill haproxy with no reason12:56
mgariepyi didn't do it for no reason, juste because when it goes from master to backup the notify script stops it.12:57
mgariepyand haproxy is noisy12:57
evrardjpmaybe I'm dreaming but I don't see the status going from backup to FAULT13:02
mgariepyi have it if haproxy is stopped, then i start keepalived, and i kill the master.13:03
evrardjphaproxy is stopped on both?13:04
mgariepynop13:04
evrardjpjust on the backup13:04
evrardjphow do you kill the master? killing keepalived/haproxy/both ?13:04
mgariepystopping keepalive13:05
openstackgerritMajor Hayden proposed stackforge/os-ansible-deployment: Add profiling for Ansible tasks  https://review.openstack.org/21684913:08
*** tlian has joined #openstack-ansible13:11
*** Mudpuppy has joined #openstack-ansible13:12
evrardjpmgariepy: Ok I've got the issue too13:15
mgariepyok13:15
evrardjpI thought all the cases were tested13:16
evrardjpapparently this simple one isn't13:16
evrardjpI'll check on that later mgariepy, if you don't mind13:20
evrardjpdo you have a deadline?13:20
mgariepyi'll continue poking it.13:25
mgariepywell not for now ;) haha13:25
mgariepyi have another month or so to play around.13:25
*** scarlisle has joined #openstack-ansible13:31
*** cloudtrainme has joined #openstack-ansible13:41
cloudnullmorning13:41
*** cloudtrainme has quit IRC13:41
mgariepygood morning cloudnull13:42
matttcloudnull: regarding https://review.openstack.org/#/c/202822/13:52
matttcloudnull: what is the benefit of having a role that has no dependencies ?13:52
*** woodard has quit IRC13:55
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-liberty specification  https://review.openstack.org/22177713:57
*** shoutm has quit IRC13:58
*** woodard has joined #openstack-ansible13:59
*** mrstanwell has joined #openstack-ansible14:15
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add PLUMgrid Neutron Plugin to neutron playbooks  https://review.openstack.org/22178814:22
*** sigmavirus24_awa is now known as sigmavirus2414:23
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825914:25
cloudnullmattt:  say what ?14:26
cloudnullyou want to add deps to the role ?14:26
matttcloudnull: "There is duplicate code in the various roles however those bits ensure that the role can be independently deployed without the need for additional dependencies."14:26
cloudnullah.14:27
mattti was just wondering what the benefit of that is14:27
*** javeriak has quit IRC14:27
cloudnulla role dep is defined as another role. which means to use a given role with deps you must have all of the roles on your deployment host.14:28
cloudnullessentially I want to keep as few roles as possible and not go back to having this https://github.com/stackforge/os-ansible-deployment/tree/juno/rpc_deployment/roles14:29
cloudnullin which we had single purpose roles and magic variables.14:29
cloudnullall of that role nightmare was created in an effort to stay DRY, however with ansible not being code but rather a simple config management system written in YAML staying DRY is not really a thing we can or should do. IMHO14:31
matttyeah, that was a lot of roles :P14:32
cloudnulland most of them were single purpose roles using the ansible standard lib. we've dropped that structure in favor of this https://github.com/stackforge/os-ansible-deployment/tree/master/playbooks/roles which is far simpler to understand. again IMHO.14:36
palendaeInterjecting here, but I like the post-kilo break up14:37
palendaeMuch more focused, though there is a loss of 'DRY'14:37
cloudnull++14:38
*** phalmos has joined #openstack-ansible14:38
palendaeAnsible's got some sharp edges if you want to try it as a programming language14:38
matttpalendae: yeah, i've not really noticed before how unDRY we are until i saw this: https://review.openstack.org/#/c/202822/14:38
palendaeYeah :(14:39
cloudnullALL if you have a chance today please review the following items https://review.openstack.org/#/q/starredby:cloudnull+status:open,n,z and https://review.openstack.org/#/q/starredby:odyssey4me+status:open,n,z14:39
palendaeIf we really want to break up into independent roles, it'll have to be not DRY though :(14:39
cloudnullopps https://review.openstack.org/#/q/starredby:"Jesse+Pretorius"+status:open,n,z14:40
cloudnullwhat palendae said.14:40
odyssey4mewell, Ansible lends itself in style to not be DRY - but instead to be simple14:41
git-harryRole dependencies strike me as perfect for not repeating oneself and having independent roles.14:41
*** cloudtrainme has joined #openstack-ansible14:42
git-harryAs I understand it roles are for collections of commonly repeated ordered tasks - that sounds DRY to me14:42
*** cloudtrainme has quit IRC14:43
cloudnullgit-harry:  +1 roles are the ansible interface into attempting to stay DRY14:43
cloudnullhowever creating a new role to simply create a rabbitmq user and vhosts seems like a waste.14:43
cloudnullshould we also create a common role for directory creates and system users?14:43
cloudnullIMO i say no.14:44
palendaecloudnull: Mmm, I haven't looked at this change in depth, but that seems a little crazy on the surface14:44
palendaeA role that creates all the common stuff for OSAD/OA is moving away from independent roles14:44
palendaeOr those roles would have to try to create the files/dirs on their own anyway14:45
openstackgerritMajor Hayden proposed stackforge/os-ansible-deployment: Install auditd on the host  https://review.openstack.org/22180514:45
matttso what is the point of a standalone role?  i thought it was so i could deploy (for example) glance without needing keystone, etc.14:47
palendaemattt: Yeah. But our project started all inter-connected14:47
mattti didn't think it was to avoid pulling in dependencies14:47
git-harrycloudnull: Personally I think that this code should actually be part of a separate play. I think the attempt to make individual service roles means trying to for the orchestration layer, by which I mean plays, into roles. For the general concept of putting a few tasks in a role and the including that as a dependency, I think that is a good idea because there is now only one location to manage that config and it means14:48
git-harrys/to for the/to force the/14:49
openstackgerritMajor Hayden proposed stackforge/os-ansible-deployment: Install auditd on the host  https://review.openstack.org/22180514:50
matttgit-harry: yeah, i tend to agree that perhaps this shouldn't even be in the roles at all ...14:50
matttgit-harry: like the way the stackforge chef stuff operated ... no openstack service role managed db creates, rabbit user creates, etc. ... it was assumed that was handled elsewhere14:51
cloudnullwe could move those tasks into the plays and out of the roles. however it would be the same tasks in the various plays which would still not be a standalone role.14:51
odyssey4meif I think of someone wanting to consume, say, the keystone role - would it not be fair to think that when consuming the role that it should do all the things needed to run keystone?14:51
odyssey4meI think this is much more along the lines of where we draw the line14:52
cloudnullhowever: what odyssey4me said14:52
odyssey4meshould that keystone role setup the database server?14:52
odyssey4meshould it setup the database on the database server?14:53
git-harryodyssey4me: I think that is a misunderstanding of a role14:53
odyssey4meshould it setup the user for itself?14:53
openstackgerritMerged stackforge/os-ansible-deployment: Fix of haproxy ssl misconfiguration with nova_console  https://review.openstack.org/22138614:53
git-harryI don't thing everything can or should be shoehorned into a role14:53
odyssey4megit-harry agreed, but I think that as a project we need to decide where that line is and stick to it as a standard14:53
matttodyssey4me: well if we want to make roles standalone then having glance create rabbit users, etc. breaks that design goal14:54
git-harryodyssey4me: I think the 'role' that you want is actually a collection of playbooks and roles14:54
odyssey4methere is a place for the use of dependent roles, group vars, and playbook orchestration - but we need to balance over engineering against ease of use14:54
mattta concern with having all that boiler plate code through the roles is when we break them up and have different projects consume different roles, they're going to become an absolute mess14:55
git-harryodyssey4me: yes, I think stuffing everything into a single service role is over-engineering and not what ansible was designed to do14:55
cloudnullmattt:  i disagree. i think it promotes that goal. I mean to deploy glance you need all those parts and removing them makes it impossible to use without first doing what the role already accomplishes.14:56
odyssey4meit may make sense, for instance, to have a rabbitmq_admin role - then for the glance playbook to consume that role to setup the users/vhosts/etc - then the glance role is built with the assumption that the rabbit stuff is all there14:56
cloudnullgit-harry:  i disagree there too.14:56
matttcloudnull: deploying something and something being useable are not necessarily the same thing :)14:56
odyssey4mebut I think these are things we need to work on standardising in the Mitaka cycle and it should be a summit discussion14:56
cloudnullmattt:  true14:56
matttyeah i think these are good discussions to have14:57
odyssey4meworking within the current conventions for current patches is the best we can do for the delivery of liberty14:57
odyssey4meFor the Mitaka cycle we need to have a strong focus on reducing technical debt build up - and standards is one of many ways of doing that14:57
matttdunno if the ansible guys will be at the summit again, but it would be great to pull them into discussions if at all possible14:58
mattts/guys/folk/ :)14:58
palendaeHonestly we're in a little bit of uncharted territory - most ansible roles and playbooks seem to sit in private repos, not public, as seen with Galaxy's poor adoption14:58
cloudnullgit-harry:  as defined by ansible "Roles are just automation around ‘include’ directives"..."and really don’t contain much additional magic beyond some improvements to search path handling for referenced files"14:58
cloudnullso in the play or in the role its really the same thing.14:59
git-harrynot if the role is making decisions about which host the role applies to14:59
cloudnullof course it is .15:00
cloudnullyou can use delegate in play tasks just like you can in a role.15:00
git-harryI'm not thinking about delegate_to here so much as conditionals based on group membership15:01
palendaeDidn't think roles were supposed to know about group membership15:01
palendaeIf not by ansible standards, then ours15:01
mattti do also think that roles knowing about specific hosts feels slightly wrong too15:01
git-harryI think roles should be like modules from that perspective15:02
cloudnullsvg might have some thoughts on that but in reviewing plenty of roles out in the wild many of them have groups defined within them.15:02
*** jwagner_away is now known as jwagner15:02
matttwe ultimately need to agree on some patterns and document them15:02
matttthen enforce them via the review process15:02
odyssey4memattt ++15:03
odyssey4mewhat is or isn't best practise is subjective15:03
palendaeYeah, project standards would help15:03
odyssey4mewe need to decide what our patterns and conventions are15:03
odyssey4methen to apply them properly15:03
odyssey4methey can adjust over time as we learn to do betterer, and as ansible gains more features15:03
palendaeFrom what I know of the current state of Ansible 2.0, gaining features will be a while15:04
matttdangit wish i were going to tokyo now :P15:05
palendaeafaik, Ansible 2.0 was "Rewrite it so the code is how we want it, then add support back in for existing stuff"15:06
palendaeThey're on the latter part now15:06
odyssey4meevrardjp can you backport https://review.openstack.org/221386 and https://review.openstack.org/221402 please :)15:06
*** scarlisle has quit IRC15:07
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Shift irqbalance package from lxc_hosts to openstack_hosts  https://review.openstack.org/21835415:08
cloudnullmattt odyssey4me: I agree that we need to agree on a standard however I think we default to ansible best practices and define our own where needed. http://docs.ansible.com/ansible/playbooks_best_practices.html15:09
svgcloudnull: what's the specific question?15:10
cloudnullsvg: whats your stance on using group names within a role.15:10
cloudnull's/./?/'15:11
svgavoid15:11
svgbut thats not always easy15:11
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add galera_address to all playbooks installing galera_client  https://review.openstack.org/22130115:11
svgI read sth ^^ about include paths - I once wrote some patch to have the full  role_path availabla as a var to help with that15:12
svgbut yes, that basically sucks15:12
svgthe difference between files/ and templates/ is bad, as different modules, lookup plugins etc are not consequent15:13
svgcloudnull: is there a more specific use case you are discussing here?15:14
cloudnullso in our case where a role executes a particular code path on group_name[0] and another on != group_name[0] would the "best practice" be to break the role into multiple roles, move those tasks into the plays, or to currently carry on knowing that the current situation "basically sucks"?15:14
cloudnullsvg: being that you've been in the anisble community / ecosystem a lot longer than most of us, your expertise would be appreciated here.15:15
svghm, that's  hard one indeed15:16
cloudnullIMO it would help direct us at the desing summit going into M15:16
svgI think splitting up a role for that would be the baddest thing actually15:17
*** alop has joined #openstack-ansible15:17
svgI'd rather stick to hardcoding then15:17
svgI guess that's also a part where one needs more information from inventory, how hosts relate to parent groups, into the exectution (playbooks/roles)15:18
*** richoid has joined #openstack-ansible15:19
palendaecloudnull: Also worth noting - we've been inconsistent in reaching out to the Ansible community, rather than just the OpenStack one15:19
palendaeWe have one foot in each really, or should15:19
cloudnullsvg: indeed the inventory group membership is then tightly to what the role requires.15:19
*** richoid has quit IRC15:19
git-harryI'm not sure what benefit roles give the project over using playbooks because the roles are so tied to the project they'll never be used anywhere else.15:20
svgbtw, I noticed you guys often talk about making rols more generic, putting them in their own repo, publishing hem on galaxy... I'm not sure why that is so important. Especially for very specific deploys like this project. Even the best stuff on galaxy will probably never suit what a project as osad needs. IMHO.15:20
svgheh, so, what git-harry said15:20
palendaesvg: I think that comes from trying to accomodate more deployer needs more easily15:20
*** richoid has joined #openstack-ansible15:20
svg(I never was a big fan of galaxy)15:20
palendaeInstead of having extension points all over in this big repo15:21
palendaeBut I'm starting to wonder the same15:21
palendaeThe concept, or the implementation?15:21
odyssey4meyeah, so the general idea is that if someone wants to just deploy keystone and swift then they can only pull those roles down (and the infra roles they need to make it go)15:21
odyssey4meit's not necessarily to tie it to galaxy itself, but rather to allow more selective use of the roles we work on15:22
*** gparaskevas has quit IRC15:23
odyssey4meit also makes it more obvious for someone who wants to put together their own playbooks instead of using the ones we have, which are very specifically tied to the architecture we use - someone could deploy using whatever architecture they prefer15:23
cloudnullgit-harry:  thats not true. presently there are teams using our os_keystone and galera_server roles as standalone for deployments on baremetal. which we know works because they're testing it right now. so having the roles gives people like that an inteface to use our things without deploying OSAD specifically.15:24
odyssey4metechnically that's possible now, but it's not obvious that it's possible15:24
palendaecloudnull: Can you say which teams? It'd be great to have them in here and discussing their experience15:24
jbweber_outsider perspective, we use ansible to deploy among other things openstack and ceph and tend to never be able to reuse directly anyones roles mostly because of operating specific choices or environment issues. the way stuff is setup right now even with the split you're discussing it still wouldn't be directly usable15:24
richoidhey all - any plans on multi region compute being prioritized?15:24
cloudnulllbragstad: and crew15:24
palendaejbweber_: Yeah, I think that's what we're going to find15:25
jbweber_our stuff is osad based (kinda) but uses RDO + RHEL instead of source and ubuntu15:25
palendaeMaking them generic is going to be a long and painful process. That's mostly conjecture, though, since I've not tried15:25
palendaeI'd love to be wrong!15:25
odyssey4mejbweber_ right now they're heavily tied into the architecture - but the idea of breaking them out is to be more disciplined at making them more reusable outside of the same architecture15:25
cloudnullpalendae: ++15:25
cloudnulllong and painful. :)15:26
jbweber_I've been lurking because I've been wondering if the coming changes will make anything easier for us or not and we can dump our custom stuff. So this is an interesting topic to me15:26
odyssey4mejbweber_ we'd be very interested in more collaboration around making it more OS independent15:27
git-harrycloudnull: my point is that by tying the roles to the inventory etc the project forces the roles consumers to use absorb a some of osad's structure in the same way that consuming playbooks would. Therefore putting the code in roles doesn't provide any additional benefit.15:27
odyssey4mesome research has already been done which can make it less painful with very little adjustment... at least for packages and templates15:28
git-harryand I think is a detriment because playbooks aren't made best use of15:28
svgI think roles should do one thing and to it well. If they become too bug or too complex, then something is wrong.15:29
svge.g. if one has a role to deploy a webapp, don't code things into it that deploy and configure the $httpd for it15:30
svgideally, a consumer should be able to choose his $httpd of choice15:30
odyssey4mepalendae cloudnull while I agree that breaking out the current roles may be a long and painful process, agreeing that independent role repositories can form part of the openstack-ansible umbrella would be a great first step to being more inclusive of work that others have done for projects not currently included in the architecture15:31
palendaeIIS15:31
cloudnullpalendae:  this is a serious converstaion ;)15:31
palendaecloudnull: I'm switching to PowerShell DSC15:31
odyssey4meif we can agree that it's ok for there to be more role repositories, then others can independently put together roles for optional use and we don't have to be tied into the review process for them if we don't want to be15:31
*** arbrandes1 has quit IRC15:31
*** phalmos has quit IRC15:32
* svg installs Windows 10 on palendae laptop15:33
* cloudnull takes ball and goes home...15:33
openstackgerritHugh Saunders proposed stackforge/os-ansible-deployment: Install nfs-common with nova-compute  https://review.openstack.org/22184415:33
odyssey4mesvg agreed - for example we have several roles deploying apache for openstack services... we could probably break that out into a role and have the openstack service playbooks do the apache bits15:33
palendaesvg: Oh, you're not aware of my laptop shopping righ tnow..15:33
git-harryodyssey4me: I do agree with that concept. The project is sort of reversing big tent if a project needs to be in osad to be deployed using it15:33
palendaeodyssey4me: It all sounds good in theory, sure15:33
svgpalendae: considering a tablet?15:33
palendaesvg: Upgrading my current X1 Carbon to be a Linux/Windows workstation for work15:34
palendaeWe'll see though15:34
svgpalendae: in what sense 'upgrading'?15:34
cloudnullgit-harry:  +1 I agree.15:34
palendaesvg: I have an X1 with 8GB RAM/256GB SSD. Would double those15:35
* cloudnull runs knowing that lightning is about to strike due to git-harry and cloudnull agreeing.15:35
svgpalendae: I thought RAM upgrade was not possible with the X1? of perhaps that's an older model?15:35
odyssey4megit-harry cloudnull that's why https://review.openstack.org/213779 was proposed - to allow independent repositories and to consider breaking out the existing roles15:36
*** skamithi13 has quit IRC15:36
palendaesvg: No, I'd be stupid and buy a whole new machine :)15:36
*** skamithi13 has joined #openstack-ansible15:36
palendaeWhen I got mine 8GB was the highest option15:36
*** sdake_ has joined #openstack-ansible15:36
odyssey4methe existing roles would still require their own blueprint/spec as it's a complex affair15:36
cloudnullpalendae:  if you get another machine and end up selling the x1 let me know :)15:36
palendaecloudnull: You may be in luck!15:36
svgsame was with my x220, officially no support for more than 8g, but doubling it just works15:36
cloudnulli have an x230 which i love15:37
cloudnullbut the res is kinda a drag15:37
palendaeThat x230 is nice15:37
palendaeI just replaced my Thunderbolt monitor with a Dell 27" 4k one15:37
palendaeSo I can finally use something other than macbooks on my large screen15:37
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Fix keystone shibboleth template to detect ssl usage correctly  https://review.openstack.org/22134715:38
*** arbrandes has joined #openstack-ansible15:38
*** sdake__ has joined #openstack-ansible15:39
*** sdake has quit IRC15:40
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Add profiling for Ansible tasks  https://review.openstack.org/21684915:40
*** sdake_ has quit IRC15:43
*** phalmos has joined #openstack-ansible15:45
*** shoutm has joined #openstack-ansible15:46
*** sdake has joined #openstack-ansible15:47
evrardjptoo bad I missed the nice discussion15:48
evrardjpI'll give my opinion anyway :p15:49
*** sdake__ has quit IRC15:49
*** cristicalin has quit IRC15:49
evrardjpI think that separating in different independant roles is good. It doesn't force the deployer to use the inventory as it currently is. (if the deployer has other dynamic inventories, it's far more helpful to not impose him that)15:49
evrardjphowever the orchestration of roles is difficult15:50
evrardjpbut that's why there are tools in ansible that can help us: roles dependencies, tags for skipping parts of a role ...15:50
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Allow testing of cinder multi backends w/ tempest  https://review.openstack.org/22185115:51
palendaeevrardjp: The inventory thing is orthagonal, I think - it needs to be revisited, too15:51
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Fix of haproxy ssl misconfiguration with nova_console  https://review.openstack.org/22185315:51
openstackgerritMatthew Thode proposed stackforge/os-ansible-deployment-specs: Add spec for IPv6 support for projects  https://review.openstack.org/22151615:52
openstackgerritJean-Philippe Evrard proposed stackforge/os-ansible-deployment: Updated the configuration to current dynamic inventory standards  https://review.openstack.org/22185415:52
evrardjppalendae: I don't know what you mean by that, but I understand that it's also a keystone (pun intended) of the ansible deployment15:52
palendaeevrardjp: It is, but our in-tree dynamic inventory script is kind of a snowflake compared to most ansible ones, afaik15:53
evrardjpwe are using dynamic inventory here15:53
palendaeIt uses the /etc/*_deploy/*_user_config.yml file to generate and populate container IPs and names15:53
evrardjpso it's not a standard inventory either15:53
evrardjppalendae: yeah I know how it works :)15:54
evrardjpmore or less15:54
odyssey4meevrardjp you probably know better than I do at this point :)15:55
cloudnullI would like inventory and the generation of inventory to be better. i just cant put my finger on how yet.15:55
evrardjpI don't think it needs to be changed15:55
palendaeevrardjp: Yeah - for most of the upstream examples from Ansible don't have the dynamic inventory scripts generate inventory, just query for it15:55
evrardjpright now15:55
palendaeI think it needs to be refactored and have some tests wrapping it15:55
evrardjpI think the focus would be to be as modular as possible, to use other inventories, and still deploy without problems15:55
palendaeLots of things to be done, just time :(15:56
evrardjppalendae: in upstream example that's often what happens: json generation, caching and reuse15:57
evrardjpin upstream examples for dynamic inventories*15:57
palendaeevrardjp: Right, but (again, afaik) they don't then create the machines15:57
palendaeOur LXC vs AWS, from what I could tell was the AWS ones simply use what's in AWS's db15:57
palendaeMaybe this is all ok and i'm chasing ghosts15:57
*** sdake has quit IRC15:58
cloudnulleveryone should adopt the standard Venus  time. then there wouldn't be an issue with time.15:58
evrardjplxc is just a tool, a convenient one15:58
odyssey4meas far as I can tell from the little bit of reading I've worked through, everything we currently do in our inventory can be expressed in the ini format... it's standard ansible15:59
lbragstadcloudnull: o/15:59
evrardjpcreating a lxc container just bring something to your inventory, that's just something you could skip if not using lxc15:59
palendaeodyssey4me: Yeah15:59
palendaeevrardjp: Sure15:59
palendaeI'm probably chasing ghsots then :)15:59
*** Mudpuppy has quit IRC15:59
odyssey4methe only trouble we have with it is that the way we put it together is a bit obscure15:59
cloudnullo/ lbragstad15:59
palendaeodyssey4me: I would like to move our defaults out of the scripts themselves and into an ini file in /etc/ansible15:59
palendaeodyssey4me: Yes15:59
lbragstadcloudnull: you pinged earlier?15:59
odyssey4meso you're right palendae - we should document how it's put together and have some tests on it16:00
evrardjpI'm mean, yes it's not only reading from inventory source A, sometimes you should also write to an inventory ;)16:00
*** Mudpuppy has joined #openstack-ansible16:00
cloudnulljust talking about the use of the os_keystone roles.16:00
palendaelbragstad: He pinged cause I was asking about groups using independent roles16:00
palendaeEvidently you guys are16:00
lbragstadpalendae: ahh16:00
lbragstadpalendae: independent roles?16:01
palendaeWould love feedback on what works and doesn't as we try to figure out separating our repo16:01
palendaelbragstad: So we understood that you're 'just' using the os_keystone role?16:01
odyssey4mepalendae well, it would be ideal if we could move away from using -e overrides, and instead use group vars better16:01
lbragstadpalendae: oh, yes! sorry I was thinking groups and roles in the terms of keystone entities16:01
palendaeodyssey4me: That'd be good too16:01
*** alextricity has joined #openstack-ansible16:01
evrardjpodyssey4me: +116:01
palendaeodyssey4me: Like I said, lots and lots of room for improvement :)16:01
evrardjpgroup_vars are powerfulz16:02
evrardjpansible variable merging would also be great if it could come from the ansible guys16:02
palendaelbragstad: It was really more of a 'we should sit down sometime and get focused feedback', nothing to solve right now16:02
evrardjp(on a task/play basis)16:02
palendaelbragstad: Maybe at summit if you can make time16:02
lbragstadpalendae: we are using the standalone keystone stuff the cloudnull pushed to his repository. brianl or blewis is the guy who is working one that from our team.16:03
palendaeAhh, so the os_cloud stuff?16:03
palendaeOr os-cloud16:03
*** skamithi14 has joined #openstack-ansible16:03
cloudnullpalendae:  test play for stand alone keystone https://github.com/cloudnull/osad_standalone_keystone16:04
lbragstadpalendae: yep https://github.com/cloudnull/osad_standalone_keystone16:04
*** skamithi13 has quit IRC16:04
cloudnullthat one :)16:04
odyssey4melbragstad what held you guys back from using the osad repo as it is?16:04
lbragstadodyssey4me: we did, i spent a weekend diving into it and we deployed keystone with it16:04
*** skamithi13 has joined #openstack-ansible16:04
cloudnullrichoid: sorry totally missed the message around multi region compute. .16:05
*** skamithi15 has joined #openstack-ansible16:05
evrardjpquick question, not related, any doc of the complete list of the variables I should set to bring all the service endpoints to SSL (and work with ssl, not just have https:// in its url)?16:05
cloudnullrichoid:  we had a spec for this https://review.openstack.org/#/c/192421/16:06
cloudnullbut it was abandoned due to priorities shifting to federation and other things16:06
cloudnullif thats something that you'd be interested in we can revive the spec16:06
cloudnullideally we'd need some input on making it go.16:07
cloudnulltechnically multi region work, you simply have to define variables to make it work but shared infra pieces need to be updated to better accomodate the deployment process.16:08
*** skamithi14 has quit IRC16:08
*** phalmos has quit IRC16:08
cloudnullheres an example of making multi-region work with kilo https://github.com/cloudnull/osad-regions16:08
cloudnullsimple test play but it does the job of illustrating how it works.16:09
*** skamithi13 has quit IRC16:09
odyssey4merichoid cloudnull  yeah, most of the work is already done - the only part you can't do right now is use the same ansible inventory to deploy a seperate global galera cluster16:09
odyssey4meif you build your global galera cluster seperately, the rest is just variable changes16:10
odyssey4meevrardjp documented - no, not to my knowledge16:10
lbragstadodyssey4me: we got it to work fine with the osad-keystone role but cloudnull pretty much did the same thing we did, just better.16:10
odyssey4meevrardjp assuming that you have your LB setup to do the ssl offloading and don't want to use ssl internally, it should just be a case of modifying the public endpoints in the service catalogues after you've deployed16:11
odyssey4meevrardjp if you actually want to have all the services use ssl endpoints internally, I'm not sure we have all the bits there to make that go16:12
evrardjpthat's what I thought odyssey4me16:12
cloudnullevrardjp:  at last check not all of the OS services correctly support ssl16:12
evrardjpMaybe I should focus on improving haproxy to use ssl16:12
evrardjpfor those services16:12
odyssey4meevrardjp only keystone is instrumented for that, primarily because I don't think anyone has thought that anything other than identity traffic securing is important16:13
evrardjpto terminate*16:13
*** kukacz has joined #openstack-ansible16:13
evrardjpI think horizon already works with https too16:13
odyssey4meyeah, another reason is that much of the time when you try to make clients use ssl, then break16:13
evrardjpin our playbooks16:13
odyssey4me*they16:13
odyssey4meah yes, horizon does work too16:13
evrardjpthat's my issue16:13
evrardjpI want to give my users an opportunity to use their client16:14
evrardjpbut it miserably fails16:14
odyssey4memy general recommendation has been to only do ssl from the outside, so that it only affects the end-users who would occasionally use the CLI (if that's your use-case)16:14
odyssey4mebut definitely don't do it on the inside for all services, because then your back-end breaks16:14
evrardjpok16:15
evrardjpthat's also what I thought16:15
openstackgerritHugh Saunders proposed stackforge/os-ansible-deployment: Remove auth_url from auth_token config  https://review.openstack.org/22186916:21
*** cloudtrainme has joined #openstack-ansible16:26
*** sdake has joined #openstack-ansible16:30
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Be more clear about used_ips, mostly in the example file  https://review.openstack.org/22171316:35
*** CheKoLyN has joined #openstack-ansible16:35
odyssey4melbragstad so the idea of cloning the whole osad repo was not a viable option for you guys16:36
odyssey4me?16:37
lbragstadodyssey4me: i could have been, i was just assisting our ops team with the initial spike to get things moving16:39
Sam-I-Amhughsaunders: ping16:41
hughsaundersSam-I-Am: sup16:41
Sam-I-Amhughsaunders: i see your auth_url patch16:42
Sam-I-Amfor a long time, even though middleware doesnt seem to read it, every service spewed out some crazy warning when it wasnt there16:42
Sam-I-Amare those warnings gone in liberty?16:42
hughsaundersoh :(16:42
hughsaundersnot sure, will check the logs once jenkins has gone though16:43
Sam-I-Amok. if it works i need to incorporate those changes into the upstream install guide16:43
hughsaundersI'll add docimpact in the commit message if the logs are clean16:43
richoidcloudnull odyssey4me thanks - that last bit is what I would care about the most, similar to tricircle16:46
cloudnullah is tricircle the successor to the cascading project proposed by huawei?16:48
richoidyea16:48
cloudnullI wasnt aware of tricircle.16:48
* cloudnull reading16:48
richoidits very incomplete16:48
*** shausy has quit IRC16:49
richoidwhat you explained isn't really similar to tricircle though16:49
richoidthanks for link to osad-regions16:49
Sam-I-Amhughsaunders: actually, its not a docimpact for osad... but it sort of is for upstream upstream :)16:50
palendaeSam-I-Am: So for like, somethinig openstack projects depend on?16:50
palendaeOr do you mean downstream?16:50
Sam-I-Ampalendae: there's no docs for keystone middleware16:50
palendaeOh, ok16:50
Sam-I-Amso i sort of navigate by feel for every release16:50
palendaeYeah, upstream16:50
odyssey4merichoid so it is possible to deploy portions of osad using a seperate inventory - eg: you could deploy galera on a special cluster for a globally synchronised db, then each localised compute cluster would simply refer to that db for keystone (or whichever services you want a globally synced db for)16:51
Sam-I-Amjamie lennox usually updates the gate jobs with the new config directives, but doesnt document them anywhere else16:51
Sam-I-Amso around this time in the cycle i'll poke around a bit and often just try stuff16:51
Sam-I-Amsometimes i fix things upstream and then apply those changes to osad... other times it goes the other way16:52
Sam-I-Amdepends on who catches what when16:53
odyssey4merichoid you can then set the galera_wsrep_provider_options to include gmcast.segment, etc in the host vars16:53
Sam-I-Ami still need to make some changes to osad for neutron16:54
Sam-I-Amthey finally solidified the mystery around config files16:54
richoidodyssey4me thanks - as an end user it's difficult to know those possibilities16:55
odyssey4merichoid yep - unfortunately we never quite got down to documenting this stuff because the focal shift of the work switched to federation16:56
richoidI guess I should dig into each role configs16:56
richoidI wouldn't have known to do that either, not a galera expert :)16:57
odyssey4merichoid nor me, but in doing the research that's what I found out - along with some other settings we never did get to test17:00
odyssey4meit's highly likely that the multi-region compute blueprint will get attention again - we just need people to spend time on it17:00
odyssey4metime enough to lab it, and document it - that's pretty much it17:01
*** javeriak has joined #openstack-ansible17:07
*** cfarquhar has joined #openstack-ansible17:08
*** cfarquhar has quit IRC17:08
*** cfarquhar has joined #openstack-ansible17:08
richoidunderstood17:18
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add PLUMgrid Neutron Plugin to neutron playbooks  https://review.openstack.org/22178817:21
*** skamithi15 has quit IRC17:22
*** skamithi13 has joined #openstack-ansible17:22
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-liberty specification  https://review.openstack.org/22177717:22
*** javeriak has quit IRC17:28
*** javeriak has joined #openstack-ansible17:31
*** devlaps has joined #openstack-ansible17:32
*** abitha has joined #openstack-ansible17:37
*** sdake_ has joined #openstack-ansible17:37
*** sdake has quit IRC17:41
*** sdake_ is now known as sdake17:45
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825917:49
cloudnullCores please review the following commits as they're working on completing several of the Liberty approved specs https://review.openstack.org/#/q/starredby:cloudnull+status:open,n,z17:53
cloudnulladditionally these items need love too https://review.openstack.org/#/q/starredby:"Jesse+Pretorius"+status:open,n,z17:53
*** shoutm has quit IRC17:55
*** agireud has joined #openstack-ansible18:08
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Update Ansible to v1.9.3-1  https://review.openstack.org/22189918:14
*** alextricity has quit IRC18:23
*** javeriak_ has joined #openstack-ansible18:27
*** javeriak has quit IRC18:30
*** javeriak_ has quit IRC18:32
*** agireud has quit IRC18:36
*** agireud has joined #openstack-ansible18:42
*** javeriak has joined #openstack-ansible18:42
*** phalmos has joined #openstack-ansible18:45
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated MariaDB to the new release version (10.0)  https://review.openstack.org/17825918:47
*** cloudtrainme has quit IRC18:49
*** arbrandes has quit IRC18:50
*** chachaji has joined #openstack-ansible18:50
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Compartmentalizing RabbitMQ  https://review.openstack.org/20282218:54
* cloudnull lunching18:58
openstackgerritMerged stackforge/os-ansible-deployment: Add variable for cirros url  https://review.openstack.org/22166919:01
openstackgerritMerged stackforge/os-ansible-deployment: Disable python buffering for gate checks  https://review.openstack.org/22008319:03
*** arbrandes has joined #openstack-ansible19:07
*** javeriak has quit IRC19:08
*** javeriak has joined #openstack-ansible19:16
*** javeriak_ has joined #openstack-ansible19:33
openstackgerritMajor Hayden proposed stackforge/os-ansible-deployment: Enabling log compression by default  https://review.openstack.org/22192419:34
*** lkoranda has quit IRC19:35
*** javeriak has quit IRC19:36
*** javeria__ has joined #openstack-ansible19:36
*** javeriak_ has quit IRC19:40
*** lkoranda has joined #openstack-ansible19:40
*** phalmos has quit IRC19:40
*** lkoranda_ has joined #openstack-ansible19:41
*** phalmos has joined #openstack-ansible19:42
*** devlaps has quit IRC19:43
*** lkoranda has quit IRC19:45
*** lkoranda_ has quit IRC19:46
*** phalmos has quit IRC19:49
*** lkoranda has joined #openstack-ansible19:50
*** lkoranda has quit IRC19:55
*** lkoranda has joined #openstack-ansible19:59
*** pabelanger has joined #openstack-ansible20:00
*** arbrandes has quit IRC20:09
*** cloudtrainme has joined #openstack-ansible20:10
*** javeria__ has quit IRC20:13
*** alextricity_h has joined #openstack-ansible20:21
openstackgerritMerged stackforge/os-ansible-deployment: Fix the heat stack user create  https://review.openstack.org/21818420:24
*** arbrandes has joined #openstack-ansible20:25
*** javeriak has joined #openstack-ansible20:30
*** kukacz has quit IRC20:43
*** woodard has quit IRC20:48
*** javeriak has quit IRC20:52
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Set affinity to 1 if running on hpcloud  https://review.openstack.org/22195720:54
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Fix keystone shibboleth template to detect ssl usage correctly  https://review.openstack.org/22134720:57
*** darrenc_ has joined #openstack-ansible21:02
*** darrenc has quit IRC21:03
*** agireud has quit IRC21:05
*** sdake has quit IRC21:08
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Archive Keystone to Keystone Federation rst content  https://review.openstack.org/21174721:10
*** skamithi13 has quit IRC21:16
*** agireud has joined #openstack-ansible21:27
*** CheKoLyN has quit IRC21:36
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment: Fixes jinja typo in keystone-httpd.conf.j2  https://review.openstack.org/22197421:45
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment: Fixes jinja typo in keystone-httpd.conf.j2  https://review.openstack.org/22197421:47
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment: Fixes jinja typo in keystone-httpd.conf.j2  https://review.openstack.org/22197721:49
*** agireud has quit IRC21:50
*** jwagner is now known as jwagner_away21:55
*** sdake has joined #openstack-ansible22:05
*** galstrom_zzz is now known as galstrom22:11
*** shoutm has joined #openstack-ansible22:12
*** shoutm has quit IRC22:12
*** galstrom is now known as galstrom_zzz22:13
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: set unique galera server-id  https://review.openstack.org/20940422:20
cloudnullEOD can rattling for reviews - https://review.openstack.org/#/q/starredby:cloudnull+status:open,n,z - Core team/Anyone?! please?! thank you. :)22:20
cloudnullSam-I-Am: yes this keeps failing . looks like we may still need those vars in liberty https://review.openstack.org/#/c/221869 -cc odyssey4me hughsaunders22:21
*** chachaji has quit IRC22:33
cloudnullSam-I-Am: https://review.openstack.org/#/c/211747/ this is doc failure if you have a sec can you make it go ?22:41
*** darrenc_ is now known as darrenc22:51
*** markvoelker has quit IRC22:56
*** Mudpuppy has quit IRC23:11
Sam-I-Ammoo23:14
*** Mudpuppy has joined #openstack-ansible23:20
*** darrenc is now known as darrenc_afk23:20
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Fixes jinja typo in keystone-httpd.conf.j2  https://review.openstack.org/22197423:27
*** cloudtrainme has quit IRC23:28
*** Mudpuppy_ has joined #openstack-ansible23:31
*** Mudpuppy has quit IRC23:34
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Adds the ability to provide user certificates to HAProxy  https://review.openstack.org/22166723:35
*** Mudpuppy_ has quit IRC23:42
*** shoutm has joined #openstack-ansible23:44
*** markvoelker has joined #openstack-ansible23:57

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