Tuesday, 2016-02-23

*** raddaoui__ has quit IRC00:01
*** raddaoui_ has quit IRC00:01
*** asettle has joined #openstack-ansible00:04
*** asettle has quit IRC00:09
*** raddaoui_ has joined #openstack-ansible00:13
*** raddaoui has joined #openstack-ansible00:13
*** weezS has quit IRC00:14
*** baker has joined #openstack-ansible00:15
*** jaypipes has quit IRC00:20
*** weezS has joined #openstack-ansible00:22
*** baker has quit IRC00:24
*** baker has joined #openstack-ansible00:25
*** woodard has joined #openstack-ansible00:25
*** galstrom is now known as galstrom_zzz00:28
*** baker has quit IRC00:35
*** baker has joined #openstack-ansible00:37
*** baker has quit IRC00:48
*** sdake_ has joined #openstack-ansible00:49
*** sdake_ has quit IRC00:49
*** sdake_ has joined #openstack-ansible00:49
*** sdake has quit IRC00:51
openstackgerritMerged openstack/openstack-ansible-memcached_server: Only update apt cache if necessary  https://review.openstack.org/28023400:52
openstackgerritHector I Gonzalez Mendoza proposed openstack/openstack-ansible: Backport: Store openstack_host_sysstat_enabled as lower case  https://review.openstack.org/28333700:53
*** weezS has quit IRC00:54
*** baker has joined #openstack-ansible00:54
*** sdake_ has quit IRC00:56
*** eil397 has quit IRC01:05
*** baker has quit IRC01:14
*** baker has joined #openstack-ansible01:17
*** baker has quit IRC01:21
*** baker has joined #openstack-ansible01:24
*** baker has quit IRC01:26
*** nn_brian has joined #openstack-ansible01:32
*** nn_brian has quit IRC01:33
*** nn_brian has joined #openstack-ansible01:34
*** baker has joined #openstack-ansible01:37
*** nn_brian has quit IRC01:38
*** kencjohnston has joined #openstack-ansible01:41
*** baker has quit IRC01:44
*** baker has joined #openstack-ansible01:46
*** baker has quit IRC01:54
*** baker has joined #openstack-ansible01:55
*** sdake has joined #openstack-ansible01:57
*** Bjoern_ has joined #openstack-ansible01:58
*** baker has quit IRC02:00
*** sdake has quit IRC02:04
*** kencjohnston has quit IRC02:05
*** sdake has joined #openstack-ansible02:07
openstackgerritTravis Truman (automagically) proposed openstack/openstack-ansible: Clarify user config loading in dynamic inventory  https://review.openstack.org/28331302:10
*** rohanp_ has quit IRC02:20
openstackgerritMerged openstack/openstack-ansible: DOCS: Correct location of variable overrides  https://review.openstack.org/28242602:23
openstackgerritMerged openstack/openstack-ansible: Docs: Keystone SSL configuration  https://review.openstack.org/28128802:23
*** nn_brian has joined #openstack-ansible02:24
*** galstrom_zzz is now known as galstrom02:31
*** sdake has quit IRC02:38
*** persia has quit IRC02:38
*** sdake has joined #openstack-ansible02:39
*** sdake has quit IRC02:41
*** ravikamachi has quit IRC02:41
*** persia has joined #openstack-ansible02:42
*** gfa is now known as gfa_02:44
*** phalmos has joined #openstack-ansible02:44
*** gfa_ is now known as gfa02:44
*** phalmos has quit IRC02:45
*** phalmos has joined #openstack-ansible02:45
*** nn_brian has quit IRC02:48
*** phalmos has quit IRC02:50
*** baker has joined #openstack-ansible02:52
*** fawadkhaliq has joined #openstack-ansible02:52
*** galstrom is now known as galstrom_zzz02:55
*** ShannonM has joined #openstack-ansible02:57
*** TheIntern has joined #openstack-ansible02:58
*** Bjoern_ has quit IRC03:05
*** phalmos has joined #openstack-ansible03:06
*** ShannonM has quit IRC03:24
*** fawadkhaliq has quit IRC03:40
*** Bjoern_ has joined #openstack-ansible03:42
*** TheIntern has quit IRC03:43
*** fawadkhaliq has joined #openstack-ansible03:44
*** fawadkhaliq has quit IRC03:44
*** fawadkhaliq has joined #openstack-ansible03:45
*** fawadkhaliq has quit IRC03:45
*** nn_brian has joined #openstack-ansible03:46
*** nn_brian has quit IRC03:48
*** nn_brian has joined #openstack-ansible03:48
*** sdake has joined #openstack-ansible04:00
prometheanfireuhh, can we run nova in a container now?04:03
prometheanfiretgt (1:1.0.63-1) unstable; urgency=medium04:03
prometheanfire  * New upstream release:04:03
prometheanfire    + Do not fail on EACCESS on oom_adjust; tgtd can now run in a different04:03
prometheanfire      user namespace (Closes: #813368).04:04
prometheanfirethat's user namespace at least04:04
prometheanfireprobably not netns04:04
prometheanfiregot excited there for a sec :P04:05
*** shausy has joined #openstack-ansible04:15
*** baker_ has joined #openstack-ansible04:17
*** baker has quit IRC04:20
*** baker has joined #openstack-ansible04:26
*** asettle has joined #openstack-ansible04:27
*** sdake has quit IRC04:28
*** baker_ has quit IRC04:29
*** asettle has quit IRC04:32
*** nn_brian has quit IRC04:36
*** baker has quit IRC04:42
*** shausy has quit IRC05:07
*** shausy has joined #openstack-ansible05:07
openstackgerritMichael Davies proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338405:08
*** javeriak has joined #openstack-ansible05:12
*** javeriak has quit IRC05:13
*** javeriak_ has joined #openstack-ansible05:13
*** woodard has quit IRC05:18
*** javeriak_ has quit IRC05:33
*** sdake has joined #openstack-ansible05:41
*** swati has joined #openstack-ansible05:46
swatiHI , I am working on ansible liberty05:46
swatiI have some query regarding getting the services of DNS component up on Horizon...anybody available?05:47
cloudnullprometheanfire: whats going ?05:49
cloudnullswati: what are you looking for ?05:50
swatiHi <cloudnull>....like if I have to enable designate functionality on "Devstack" Horizon, I enable those services in local.conf file... http://docs.openstack.org/developer/designate/devstack.html05:51
swatiThis is new in Liberty05:51
swatiIn ansible also, I have setup designate and its services are also up.......Now if I have to get its Horizon part working...in which file should I enable these services?05:52
cloudnullyou'd have to edit the horizon local_config.py to enable the designate pane05:52
cloudnullah looks like the desegnate panel is not in horizon05:54
cloudnullyou need05:54
cloudnullhttps://github.com/openstack/designate-dashboard05:54
cloudnullspecifically. https://github.com/openstack/designate-dashboard/tree/stable/liberty05:54
cloudnullso to do the needful, you need to install that package in the venv and add the required config options05:55
prometheanfirecloudnull: I maintain tgt and was looking at the changelog, looks like it got some namespace support05:56
prometheanfirenot netns though05:56
prometheanfireust a userns bugfix05:57
swatiThanks <cloudnull>... il check this now05:57
*** sdake has quit IRC05:57
*** javeriak has joined #openstack-ansible05:57
swatiKevin_ should I install designate_dashboard in venv of designate_container and mention if in the local_config.py file of horizon container?05:59
cloudnullyes06:02
cloudnullonce you activate it06:02
cloudnullyou can do pip install git+https://github.com/openstack/designate-dashboard@stable/liberty06:02
cloudnullwhich will install it .06:03
cloudnullthen all you should have to do is step 2 from -- https://github.com/openstack/designate-dashboard/tree/stable/liberty#howto06:03
cloudnullprometheanfire: ah.06:07
*** izaakk has quit IRC06:17
*** fawadkhaliq has joined #openstack-ansible06:18
*** woodard has joined #openstack-ansible06:19
*** raddaoui_ has quit IRC06:22
*** raddaoui has quit IRC06:22
*** woodard has quit IRC06:24
*** mariusv has quit IRC06:25
*** phiche has joined #openstack-ansible06:25
*** mariusv has joined #openstack-ansible06:32
*** mariusv is now known as Guest9803906:32
*** javeriak_ has joined #openstack-ansible06:35
*** javeriak has quit IRC06:35
*** javeriak has joined #openstack-ansible06:38
*** javeriak_ has quit IRC06:41
swatiKevin_ is it necessary to include venv files in all openstack components?06:45
swatifor Liberty?06:45
swatias initially, I had included a component in Kilo without venv ....n it was working.....but I guess some change like this has been made in Liberty release...can u pls confirm?06:46
*** asettle has joined #openstack-ansible06:51
*** Guest98039 has quit IRC06:53
*** marius- has joined #openstack-ansible06:53
*** marius- has quit IRC06:54
*** severion has quit IRC06:54
*** severion has joined #openstack-ansible06:55
*** asettle has quit IRC06:56
*** phiche has quit IRC06:57
*** phiche has joined #openstack-ansible07:07
*** fawadkhaliq has quit IRC07:11
*** cemmason has joined #openstack-ansible07:16
*** javeriak_ has joined #openstack-ansible07:19
*** cemmason has quit IRC07:19
*** cemmason1 has joined #openstack-ansible07:19
*** woodard has joined #openstack-ansible07:20
*** javeriak has quit IRC07:21
*** cemmason has joined #openstack-ansible07:22
*** cemmason1 has quit IRC07:22
*** cemmason1 has joined #openstack-ansible07:25
*** woodard has quit IRC07:25
*** cemmason has quit IRC07:27
*** cemmason1 has quit IRC07:32
*** mrda has quit IRC07:32
*** cemmason has joined #openstack-ansible07:32
*** cemmason1 has joined #openstack-ansible07:34
*** cemmason has quit IRC07:34
*** swati has quit IRC07:38
*** Bjoern_ has quit IRC07:42
*** mikelk has joined #openstack-ansible07:43
*** asettle has joined #openstack-ansible07:47
*** asettle has quit IRC07:52
*** tomoe_ has joined #openstack-ansible07:54
*** admin0 has joined #openstack-ansible07:56
*** admin0 has quit IRC07:56
*** javeriak has joined #openstack-ansible07:58
*** pcaruana has joined #openstack-ansible07:58
*** admin0 has joined #openstack-ansible07:59
*** javeriak_ has quit IRC08:02
*** javeriak has quit IRC08:04
*** javeriak has joined #openstack-ansible08:07
*** pcaruana is now known as pcaruana|afk|08:08
*** pcaruana|afk| is now known as pcaruana08:08
*** asettle has joined #openstack-ansible08:10
*** Oku_OS has quit IRC08:13
*** javeriak has quit IRC08:13
*** asettle has quit IRC08:15
*** mariusv has joined #openstack-ansible08:20
*** woodard has joined #openstack-ansible08:22
*** woodard has quit IRC08:26
*** javeriak has joined #openstack-ansible08:29
*** subscope has joined #openstack-ansible08:32
*** subscope has quit IRC08:36
*** swati has joined #openstack-ansible08:38
swatiHi...I am getting error "openstack-ansible failed to find required executable rabbitmqctl"....any idea?08:43
*** subscope has joined #openstack-ansible08:47
*** swati has quit IRC08:48
*** javeriak has quit IRC08:56
*** javeriak has joined #openstack-ansible08:59
*** evrardjp has joined #openstack-ansible09:06
*** mrda has joined #openstack-ansible09:16
openstackgerritJaveria Khan proposed openstack/openstack-ansible: Update PLUMgrid Appendix Doc paths  https://review.openstack.org/28346509:16
*** subscope has quit IRC09:20
*** woodard has joined #openstack-ansible09:23
*** woodard has quit IRC09:27
*** eford has joined #openstack-ansible09:28
*** dford has quit IRC09:31
*** phalmos has quit IRC09:33
*** asettle has joined #openstack-ansible09:34
odyssey4meBofu2U did you find the cause of the instance<->volume traffic going over br-mgmt instead of br-storage ?09:36
*** eford has quit IRC09:38
*** eford has joined #openstack-ansible09:39
*** asettle has quit IRC09:42
*** asettle has joined #openstack-ansible09:42
*** subscope has joined #openstack-ansible09:43
*** mikelk has quit IRC09:45
*** mikelk has joined #openstack-ansible09:45
*** elo has quit IRC09:49
odyssey4meBofu2U bgmccollum tiagogomes it seems that you all may have hit the same bug at the same time, as http://paste.openstack.org/show/487757/ and https://review.openstack.org/283234 relate to the same problem, although they are different solutions09:50
openstackgerritMichael Davies proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338409:52
tiagogomesHmm, I can't see how they are related.09:53
odyssey4merohanp ping?09:54
tiagogomesBut coffee didn't kick in yet09:54
odyssey4metiagogomes so is mine, so I might be completely off :)09:55
odyssey4memrda I was going to aubmit an updated tox/test config for the ironic repo today... good to see you're on it :)09:56
*** subscope has quit IRC09:57
*** cemmason1 has quit IRC09:57
mrdawell, I'm about to give up, so feel free to continue while I sleep.09:57
odyssey4memrda you may wish to take a look at https://github.com/openstack/openstack-ansible-galera_server for the updated tox config, and updated test configuration...09:57
tiagogomesodyssey4me one is for neutron, another for cinder09:57
odyssey4meah ok, I'll take it over :)09:57
mrdaFeel free to push a new revision to https://review.openstack.org/#/c/28338409:57
*** cemmason has joined #openstack-ansible09:57
mrda...which is just to get things running09:57
odyssey4metiagogomes sure, but I think they related to the same problem - finding the right IP to push traffic over, right?09:58
tiagogomesok same problem, but different bugs :)09:59
* mrda heads off for the night, especially now odyssey4me can beat tox into submission on my behalf :)09:59
odyssey4metiagogomes but if you check my comments, I think they related to the same mechanism which originated from the same patch10:00
*** cemmason1 has joined #openstack-ansible10:02
*** subscope has joined #openstack-ansible10:02
*** cemmason has quit IRC10:02
odyssey4metiagogomes ah, I see that the Neutron local_ip fact determination was done at a different time. See this for the Nova one: https://github.com/openstack/openstack-ansible/commit/c506dda61d303735189abbee7c70d972b3096a4010:03
*** eford has quit IRC10:03
*** eford has joined #openstack-ansible10:03
*** fawadkhaliq has joined #openstack-ansible10:03
odyssey4mejaveriak good morning :) I had hoped you'd be able to make the mid cycle either in person or remotely, but alas it didn't happen :(10:05
*** cemmason has joined #openstack-ansible10:05
odyssey4mejaveriak you may wish to be rid of https://github.com/plumgrid/plumgrid-ansible/blob/master/plumgrid_playbooks/ansible.cfg#L28 as it causes connectivity issues10:06
*** cemmason1 has quit IRC10:06
odyssey4mejaveriak see https://github.com/openstack/openstack-ansible/commit/c7ce0982ff0c5e357fe957c9f929a9bf71deed7c#diff-c65aaeaf20dfc7d75fca73c229cb9e8510:06
*** javeriak has quit IRC10:08
*** cemmason has quit IRC10:09
*** asettle has quit IRC10:09
*** cemmason has joined #openstack-ansible10:09
*** asettle has joined #openstack-ansible10:09
odyssey4metiagogomes bgmccollum tiagogomes I've added more comments to https://review.openstack.org/283234 to clarify. Hopefully that helps with further digging.10:11
tiagogomesSeeing this: "_overlay_network: "{{ container_networks.tunnel_address|default({}) }}" , I grepped for tunnel_address but didn't find anything useful10:11
*** cemmason has quit IRC10:13
*** cemmason1 has joined #openstack-ansible10:13
*** swati has joined #openstack-ansible10:13
*** fawadkhaliq has quit IRC10:14
swatiHi....I am facing a similar error for Designate in Liberty : https://bugs.launchpad.net/openstack-ansible/+bug/152780910:14
openstackLaunchpad bug 1527809 in openstack-ansible "repo_build - create role based venv role in liberty branch fails" [Low,Fix released] - Assigned to Kevin Carter (kevin-carter)10:14
*** fawadkhaliq has joined #openstack-ansible10:14
*** cemmason has joined #openstack-ansible10:16
odyssey4meHi swati - that's a pretty old bug. What's the issue you're facing?10:17
*** cemmason1 has quit IRC10:17
*** electrofelix has joined #openstack-ansible10:18
*** cemmason1 has joined #openstack-ansible10:20
*** cemmason has quit IRC10:20
odyssey4meswati with regards to the venvs, you would not have to implement venvs for a new role - that could be added later... I have answered your question several times before10:20
odyssey4meI'm not quite sure why you keep going back to that. Your role was close to being in a ready state!10:21
odyssey4meswati I asked before whether you'd be happy to pair up with someone to help you finalise the role?10:21
odyssey4meI haven't yet received an answer, and would appreciate it if you could answer.10:22
swatifailed: [infr002-clddev_repo_container-32598725] => (item={'key': 'os_designate', 'value': ['MySQL-python', 'designate', 'httplib2', 'pycrypto', 'python-designateclient', 'python-keystoneclient', 'python-memcached', 'virtualenv', 'virtualenv-tools', 'warlock']}) => {"attempts": 5, "cmd": "/tmp/openstack-venv-builder/venvs/designate/bin/pip install --timeout 120 --find-links /var/www/repo/os-releases/12.0.5 --no-index --log10:22
swatiThis is the error I am getting while running setup-infrastructure.ymkl.10:22
swatiI have added vens in playbook only now..for liberty release..10:23
*** woodard has joined #openstack-ansible10:23
odyssey4meswati ok, so that's telling you that there's an issue with building the venv... so the question is which of the packages did it actually fail on10:23
odyssey4medo you have a -vv log that you can pastebin ?10:24
odyssey4meand you'll only need to run the repo-build playbook10:24
*** cemmason1 has quit IRC10:24
*** cemmason has joined #openstack-ansible10:24
swatiit is failing while running repo_build ( create role based venv)10:25
odyssey4meswati are you still pushing all your work to https://github.com/sharmaswati6/designate_files ?10:25
swatik..i ll paste the logs..10:25
odyssey4meswati what time zone do you work in? is it morning/afternoon/evening for you now?10:26
swatino..i am not..i ll push the changes when the playbook will run without any error..10:26
*** woodard has quit IRC10:28
odyssey4meswati ah, I thought it'd be easier to help diagnose if I could see where your work currently is10:28
*** cemmason1 has joined #openstack-ansible10:29
swatithe logs for repo_venv_builder.log are showing the names of the packages which have been successfully installed.  There is no error logged .10:29
*** cemmason has quit IRC10:29
swatiI will try to update the files as soon as possible.10:30
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Store openstack_host_sysstat_enabled as lower case value for sysstat.default.j2  https://review.openstack.org/28333710:31
*** cemmason has joined #openstack-ansible10:33
*** cemmason1 has quit IRC10:34
*** cemmason has quit IRC10:38
*** cemmason has joined #openstack-ansible10:39
*** eford has quit IRC10:41
*** cemmason1 has joined #openstack-ansible10:42
*** cemmason has quit IRC10:42
*** cemmason1 has quit IRC10:44
*** cemmason has joined #openstack-ansible10:44
*** cemmason1 has joined #openstack-ansible10:46
*** cemmason has quit IRC10:46
openstackgerritMerged openstack/openstack-ansible-openstack_hosts: Only update apt cache if necessary  https://review.openstack.org/28023510:46
*** cemmason1 has quit IRC10:48
*** cemmason has joined #openstack-ansible10:49
*** cemmason has quit IRC10:51
*** cemmason has joined #openstack-ansible10:52
*** Oku_OS has joined #openstack-ansible10:52
*** cemmason1 has joined #openstack-ansible10:55
*** cemmason has quit IRC10:55
*** cemmason has joined #openstack-ansible10:59
*** cemmason1 has quit IRC11:00
*** cemmason has quit IRC11:02
*** cemmason has joined #openstack-ansible11:02
*** fawadkhaliq has quit IRC11:03
openstackgerritMatt Thompson proposed openstack/openstack-ansible: [WIP] Automate setting of glance_api_version  https://review.openstack.org/28350811:03
*** cemmason1 has joined #openstack-ansible11:06
*** cemmason has quit IRC11:06
*** subscope has quit IRC11:21
*** woodard has joined #openstack-ansible11:24
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338411:28
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338411:28
*** woodard has quit IRC11:29
*** jaypipes has joined #openstack-ansible11:32
matttodyssey4me: so how should we proceed with https://review.openstack.org/#/c/283039/ ?  shall we pin more stuff ?11:34
*** javeriak has joined #openstack-ansible11:35
javeriakhey odyssey4me, yea sorry to have missed it :(; things got super busy at work; havent even been able to be much active here as well11:37
javeriakodyssey4me  thanks for that tip; will take it out11:38
odyssey4memattt good question, have you had another chat in that regard in #pypa or with sigmavirus24_awa about that?11:38
matttodyssey4me: no, it was your suggestion :)11:39
matttodyssey4me: we can speculate all day but i guess the question is do we want to unblock kilo or not?11:39
*** mancdaz has joined #openstack-ansible11:42
odyssey4memattt sure, but I think that this issue applies to more than just kilo11:42
matttodyssey4me: the wheel issue affects everything indirectly11:43
matttodyssey4me: it only breaks kilo build, but logan- was having issues with additional packages he was building on liberty11:43
odyssey4meso whatever we do, I'd like it to fit wherever it needs to go11:43
odyssey4memattt kevin also hit issues which relate a little to this: https://review.openstack.org/27968311:43
odyssey4mecloudnull ^11:44
matttany plans to use pip 8 in master?11:45
matttfeels a bit wrong to pin it there11:45
mattt(wheel, that is)11:45
odyssey4meyeah, I'm kinda thinking that perhaps master should move its pin to >8,<911:51
odyssey4meI think we should discuss this in the Thu meeting.11:51
* odyssey4me heads over to add it to the agenda.11:51
matttodyssey4me: i WIP'd https://review.openstack.org/#/c/283039 until we can discuss it further11:52
*** mancdaz has quit IRC11:56
*** subscope has joined #openstack-ansible11:58
*** mancdaz has joined #openstack-ansible11:58
odyssey4memattt kicking of a query in #pypa-dev, maybe we can resolve this sooner12:00
matttodyssey4me: what precisely did you ask?12:00
odyssey4meif we're in a situation where we need to pin pip to a major version (eg: >7,<8) then what companion packages should also be pinned? it seems that setuptools and wheel are closely related and should be on that list12:01
matttk12:01
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338412:02
matttodyssey4me: #pypa is quite active, could ask in there if no response in -dev12:04
odyssey4methanks mattt - I've posed the same question there12:05
odyssey4meI know that pypa-dev becomes active once the dev's are around, which is mostly US timezones as far as I've seen12:06
openstackgerritMerged openstack/openstack-ansible: Removing unused galera_lb_address var from galera playbook  https://review.openstack.org/28322712:18
odyssey4memattt did you try using wheel v0.27 / 0.28 instead of just 0.26? how did you determine the cap?12:19
odyssey4memattt / hughsaunders are any RPC builds working that are using the OSA 11.2.10 tag for rpc-repo?12:22
odyssey4meie is a repo-clone working, rather than a repo-build?12:23
odyssey4meactually, we have a WIP review in for that from mancdaz - let's retry that12:23
*** javeriak has quit IRC12:23
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: [WIP] [DO NOT MERGE] testing review 278343  https://review.openstack.org/27898112:25
odyssey4memattt according to the last test of https://review.openstack.org/278981 the current versions in http://rpc-repo.rackspace.com/os-releases/11.2.10/ may actually be fine - re-running a fresh test to confirm12:26
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338412:29
*** Nepoc has quit IRC12:34
matttodyssey4me: i went w/ what logan- suggested, and also based on the changelog on https://pypi.python.org/pypi/wheel12:35
matttodyssey4me: the bulk of the changes were introduced in 0.27.0, so it seemed sensible to cap at the previous version12:35
odyssey4meyeah, that does seem sensible - although it seems that the more up to date wheel version may be ok, it might actually be setuptools that's an issue12:36
odyssey4melet's see how the test works out12:36
matttodyssey4me: dstufft seemed familiar w/ the issue we were hitting, and he said either pin wheel or bump pip to >= 812:37
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Remove MySQL-python from Aodh pip requirements  https://review.openstack.org/27733912:41
mgariepygood morning everyone.12:47
*** gparaskevas has joined #openstack-ansible12:51
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix tests for os_ironic  https://review.openstack.org/28338412:51
bgmccollumodyssey4me tiagogomes regarding cinder storage network...it doesn't even look like those facts are being used after being set. i think all that is needed is dropping the ` | default()` bits12:53
odyssey4mebgmccollum perhaps, I'd like cloudnull to weigh in as he did those patches and has more depth of understanding into the underlying purpose12:54
bgmccollumodyssey4me i understand now what its doing...its trying to discover a suitable storage network IP...which it looks to be doing correctly, but that fact isnt used anywhere after being discovered...12:55
bgmccollumalso, the new role var allows splitting management type traffic (rabbit, db) from dataplane traffic (iscsi)...12:55
bgmccollumbut yes, we'll wait for cloudnull to comment12:56
odyssey4meandymccr are you around? I'd like to try and fathom how mrda wanted a functional test in the gate to work... it looks like we're missing a few elements here12:59
odyssey4me(for the ironic role)12:59
matttodyssey4me: he's afk at the minute13:00
*** woodard has joined #openstack-ansible13:00
*** woodard has quit IRC13:01
*** woodard has joined #openstack-ansible13:02
*** johnmilton has joined #openstack-ansible13:03
*** subscope has quit IRC13:05
*** asettle has quit IRC13:07
*** shausy has quit IRC13:16
tiagogomesis cloudnull in holiday or different timezone?13:21
*** subscope has joined #openstack-ansible13:22
odyssey4metiagogomes he's from the US, so different time zone - he's been ill lately though, so I'm not sure if he'll be around today13:23
tiagogomesok13:23
odyssey4metiagogomes bgmccollum the best may be to figure out a solution which you think works in accordance with the intent, then we can continue discussion in review13:24
*** jaypipes has quit IRC13:24
bgmccollumodyssey4me adding my notes in review right now13:24
*** jwitk0 has quit IRC13:29
bgmccollumodyssey4me some clarification notes added13:30
*** subscope has quit IRC13:32
openstackgerritByron McCollum proposed openstack/openstack-ansible: Cinder should use the storage network for iscsi traffic if available  https://review.openstack.org/28323413:32
*** cemmason has joined #openstack-ansible13:33
*** cemmason1 has quit IRC13:34
matttlogan- mgariepy : added you both to https://review.openstack.org/#/c/283508/, can you have a peek when you're around?13:35
*** cemmason has quit IRC13:37
*** cemmason has joined #openstack-ansible13:37
mgariepylooking at it now ;)13:37
*** Nepoc has joined #openstack-ansible13:40
*** cemmason1 has joined #openstack-ansible13:41
*** cemmason has quit IRC13:41
*** subscope has joined #openstack-ansible13:45
*** cemmason1 has quit IRC13:45
*** cemmason has joined #openstack-ansible13:45
matttmgariepy: tested on kilo, worked OK ... just waiting for this gate to pass13:48
*** tiagogomes has quit IRC13:50
*** cemmason has quit IRC13:50
*** cemmason has joined #openstack-ansible13:50
*** klamath has joined #openstack-ansible13:51
*** automagically has left #openstack-ansible13:52
*** automagically has joined #openstack-ansible13:52
*** asettle has joined #openstack-ansible13:52
andymccrodyssey4me: im not sure - i will follow up with mrda tonight.13:55
*** subscope has quit IRC13:55
openstackgerritTravis Truman (automagically) proposed openstack/openstack-ansible: Clarify user config loading in dynamic inventory  https://review.openstack.org/28331313:56
*** asettle has quit IRC13:56
*** cemmason has quit IRC13:56
*** cemmason has joined #openstack-ansible13:56
*** asettle has joined #openstack-ansible13:57
odyssey4meandymccr I'm taking the path of what I hope to be least resistance which is to have the initial functional test be a standalone install.13:58
odyssey4meandymccr I expect thereafter that there should also be a distributed install using containers, but we can add that as a subsequent set.13:58
andymccrodyssey4me: ok fair enough - i think that is the path of least resistance, since i know that works13:58
andymccrim working on neutron integration rn13:58
odyssey4meandymccr I'm kinda thinking that it might be a good idea to just make the funcational test do nothing and pass, then the functional tests can be worked on as subsequent patches - otherwise this is going to end up being a frankenpatch13:59
odyssey4methat at least allows others to start pitching in as well to fix anything found14:00
andymccrthats probably sensible.  the only other thing would've been to get everything in in such a way that its tested and working in 1 go.14:00
odyssey4meyeah, I think a fully functional test is going to take a few days considering the quirks of openstack-ci14:00
*** cemmason1 has joined #openstack-ansible14:00
*** evrardjp has quit IRC14:00
odyssey4meok, let me get that going, then we can move on from there14:01
*** cemmason has quit IRC14:01
*** pcaruana has quit IRC14:02
*** subscope has joined #openstack-ansible14:04
*** cemmason1 has quit IRC14:06
*** cemmason has joined #openstack-ansible14:06
*** evrardjp has joined #openstack-ansible14:07
*** b3rnard0_away is now known as b3rnard014:09
*** cemmason has quit IRC14:09
*** cemmason has joined #openstack-ansible14:09
logan-morning14:10
logan-odyssey4me: when i opened the wheel bug, i chose 0.26.0 because of https://github.com/openstack/requirements/blob/stable/liberty/upper-constraints.txt#L334 .. I did not test the versions in between14:11
odyssey4meheh, I got so sucked into the multiple things I'm working on in parallel that I forgot about my coffee14:11
odyssey4methanks goodness for my keep warm cafetiere :)14:13
*** cemmason1 has joined #openstack-ansible14:13
*** cemmason has quit IRC14:13
*** cemmason has joined #openstack-ansible14:17
*** cemmason1 has quit IRC14:18
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix docs & linting tests  https://review.openstack.org/28338414:18
odyssey4meandymccr ^ let's see how well that works14:19
*** Bjoern_ has joined #openstack-ansible14:20
*** Bjoern_ is now known as Bjoern_zZzZzZzZ14:20
*** weshay has joined #openstack-ansible14:20
*** kencjohnston has joined #openstack-ansible14:24
*** kencjohnston has quit IRC14:24
*** cemmason has quit IRC14:25
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Fix docs & linting tests  https://review.openstack.org/28338414:25
*** cemmason has joined #openstack-ansible14:25
*** kencjohnston has joined #openstack-ansible14:26
*** kencjohnston has quit IRC14:26
*** cemmason has quit IRC14:31
*** cemmason1 has joined #openstack-ansible14:31
*** jaypipes has joined #openstack-ansible14:32
*** Bjoern_zZzZzZzZ is now known as Bjoern_14:33
*** cemmason1 has quit IRC14:34
*** cemmason has joined #openstack-ansible14:34
odyssey4melbragstad you've been working with cloudnull on https://github.com/os-cloud/openstack-ansible-os_keystone - I'm taking some of the concepts from there for some other work and have noticed that https://github.com/os-cloud/openstack-ansible-os_keystone/blob/master/tasks/keystone_install_apt.yml#L68-L81 has no corresponding list in the defaults... is that intentional?14:35
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Ironic: Fix docs & linting tests  https://review.openstack.org/28338414:36
*** Mudpuppy has joined #openstack-ansible14:38
*** Mudpuppy has quit IRC14:38
*** Mudpuppy has joined #openstack-ansible14:38
*** izaakk has joined #openstack-ansible14:43
*** dmsimard is now known as dmsimard|afk14:48
*** ShannonM has joined #openstack-ansible14:50
odyssey4meandymccr mrda alright, that gets a gate pass - https://review.openstack.org/283384 - please reviews and provide thoughts14:53
*** kencjohnston has joined #openstack-ansible14:54
*** kencjohnston has quit IRC14:54
*** KLevenstein has joined #openstack-ansible14:54
*** sdake has joined #openstack-ansible14:55
openstackgerritByron McCollum proposed openstack/openstack-ansible: Cinder should use the storage network for iscsi traffic if available  https://review.openstack.org/28323414:56
openstackgerritMatt Thompson proposed openstack/openstack-ansible: [WIP] Automate setting of glance_api_version  https://review.openstack.org/28350814:57
*** kencjohnston has joined #openstack-ansible14:57
*** raddaoui has joined #openstack-ansible14:58
*** raddaoui_ has joined #openstack-ansible14:58
*** evrardjp has quit IRC14:58
*** sigmavirus24_awa is now known as sigmavirus2415:01
*** raddaoui__ has joined #openstack-ansible15:02
sigmavirus24odyssey4me: mattt no one told me about that problem with the wheel package15:03
matttsigmavirus24: i only saw it yesterday15:03
matttbut there has been an osa bug open about it for some time15:04
automagicallyTIL about inventory-manage.py. Thanks to whomever wrote it. Very useful little tool15:04
odyssey4me:) morning automagically15:04
automagicallymorning15:04
*** jthorne has joined #openstack-ansible15:04
*** elopez_ has joined #openstack-ansible15:04
matttlogan-: wonder if i should do this instead: cinder_glance_api_version: "{{ glance_enable_v2_api|bool | ternary('2','1') }}"15:05
openstackgerritMerged openstack/openstack-ansible: Remove MySQL-python from Aodh pip requirements  https://review.openstack.org/27733915:05
odyssey4mewow, that finally merged15:06
odyssey4meI have no idea why it kept failing.15:06
matttodyssey4me: i was starting to wonder about that one15:06
logan-mattt: not sure.. that is a lot more impactful than only changing the default cinder behavior to accommodate rbd compatibility.. but also don't know if tehre would be a reason not to use glance v215:07
*** elopez has quit IRC15:07
*** raddaoui_ has quit IRC15:08
*** raddaoui has quit IRC15:08
odyssey4memattt sigmavirus24 logan- so, interestingly - https://review.openstack.org/278981 does a clone from http://rpc-repo.rackspace.com/os-releases/11.2.10/ which includes setuptools 20.0 and wheel 0.29 and it works just fine, at least from a gate test standpoint... so it would seem to me that the issue is not necessarily the wheel version... unless I'm missing something?15:08
logan-the issue for me was 100% wheel, i was building the broken package manually using pip wheel and the only thing i did to fix it was downgrade wheel... let me see what version of setuptools is on the repo15:09
matttodyssey4me: dunno, it failed for me when i tried doing a repo-build15:10
matttor rather, it did the repo-build but then another playbook failed due to being unable to install the right wheels15:10
odyssey4memattt yeah, repo-build is using newer versions of both packages15:10
mattti downgraded wheel as logan- suggested and it worked15:10
*** raddaoui__ has quit IRC15:10
*** subscope has quit IRC15:11
matttodyssey4me: so whatever is in rpc-repo isn't what you'd actually get if you did a repo-build :)15:11
odyssey4mesigmavirus24 back to the question at hand - if we are putting constraints of >7,<8 around pip, which packages should be constrained with pip (and with what constraints)? it seems that setuptools and wheel are rather tightly connected15:11
odyssey4memattt yes, but what's in rpc-repo is a result of a repo-build at a point in time... so it adds data to the problem at hand15:12
matttyeah so all those wheels were built with wheel 0.26.015:13
matttwhich is why they're installable15:13
*** raddaoui has joined #openstack-ansible15:13
logan-yep thats my guess15:13
*** raddaoui_ has joined #openstack-ansible15:13
logan-it is placing 0.29.0 in the repo but using 0.26.0 to build15:13
*** raddaoui__ has joined #openstack-ansible15:13
odyssey4meah, so that's entirely plausible15:14
logan-i am guessing rpc-repo is not building from a fresh repo container every time?15:14
odyssey4methe rpc-repo build server is long lived15:14
odyssey4menope - it's an instance which remains alive and has done so for a very long time15:14
*** swati has quit IRC15:15
logan-gotcha. yeah i think it is just making sure wheel=present not wheel=latest so this would only affect new installs after 0.29.0 dropped15:15
logan-or rather... new repo container builds after 0.29.0 dropped15:16
*** mgoddard__ has joined #openstack-ansible15:16
odyssey4mealright, so I can totally accept that - but then I am still concerned that we may need to also pin setuptools15:17
odyssey4mecan we validate or invalidate that?15:17
matttodyssey4me: well we don't explicitly install setuptools15:17
*** raddaoui_ has quit IRC15:18
*** raddaoui has quit IRC15:18
matttso presumably installing wheel will pull in the right version of setuptools?15:18
odyssey4meI suppose the gate test is working with mattt's patch, so it would seem that no setuptools cap is required15:18
*** weezS has joined #openstack-ansible15:18
*** raddaoui__ has quit IRC15:18
*** raddaoui has joined #openstack-ansible15:18
*** raddaoui_ has joined #openstack-ansible15:18
*** pcaruana has joined #openstack-ansible15:18
logan-yeah it does not look like repo does a pip install of setuptools, my container just uses the os setuptools it looks like15:18
odyssey4melogan- mattt so that would mean that https://review.openstack.org/283039 is applicable to the liberty & master branches too, right?15:19
odyssey4mehmm, but why are those two branches working?15:20
*** mgoddard_ has quit IRC15:20
odyssey4meI take it that venvs are making a difference there?15:20
matttodyssey4me: upper constraints i think15:20
matttodyssey4me: the package i was having issues w/ is cffi15:20
*** pcaruana has quit IRC15:20
odyssey4meah, that makes sense15:20
matttand that version is actually lower in liberty/master iirc15:20
*** raddaoui__ has joined #openstack-ansible15:21
odyssey4meso it's an issue that will come when we next do a sha update15:21
*** pcaruana has joined #openstack-ansible15:21
matttodyssey4me: yeah i believe it would need to be addressed everywhere15:21
logan-maybe osa should follow openstack/requirements upper constraints for repo pip install?15:21
*** pcaruana|afk| has joined #openstack-ansible15:21
logan-that would make this an issue in master only15:21
matttlogan-: side note, my repo server has another setuptools installed under /usr/local/lib15:21
logan-where you are talking about moving the pip pin15:21
odyssey4melogan- the upper constraints are only available from liberty onwards15:21
matttbut i also have the ubuntu package installed15:21
odyssey4melogan- kilo doesn't have that option as it still follows the only whack-a-mole upper cap model15:22
*** cemmason has quit IRC15:22
odyssey4melogan- so yeah, we do use uppser constraints already - which is why master & liberty don't have an issue15:22
odyssey4meso my suggestion is as follows - for liberty we also ensure that wheel is constrained to a specific version, and for master we shift the pip pin to >8,<915:23
*** raddaoui__ has quit IRC15:23
*** raddaoui__ has joined #openstack-ansible15:24
logan-it doesn't seem like the upper constraints are being used in liberty for the repo-install, only repo-build15:24
odyssey4melogan- ah, you're quite correct - that is a good point15:24
odyssey4meconsidering that the local repo is not available, we'd have to devise a way of doing that15:25
odyssey4meie pull the appropriate sha's upper constraints from the upstream repo and make use of those constraints when doing the repo-install15:26
sigmavirus24odyssey4me: so setuptools has no dependency on wheel15:26
sigmavirus24wheel is something that hooks into setuptools15:26
*** admin0 has quit IRC15:26
sigmavirus24I would think we should figure out what changed, how, etc. and file a bug https://bitbucket.org/pypa/wheel/issues?status=new&status=open15:27
matttsigmavirus24: well we figured that all out already :)15:28
sigmavirus24You should be able to use moderately recent version of setuptools, any version of pip, and any version of wheel that doesn't cause the problem :P15:28
sigmavirus24setuptools/pip/wheel are pretty loosely coupled in reality15:28
sigmavirus24even if it doesn't appear that way on the surface15:28
odyssey4melol15:28
*** pcaruana|afk| has quit IRC15:29
odyssey4meso I think we can more closely define the problem now I guess?15:30
odyssey4mecffi-1.5.2 built by wheel 0.29.0 is not installable by pip 7.x15:31
odyssey4meis that right, mattt?15:31
matttodyssey4me: that is precisely what i put in the commit message :)15:31
hughsaundersM04R specifics required mattt15:32
matttwonder if i can put my #pypa transcript in a commit message :)15:32
odyssey4memattt yep, that's where I got those details from - now I have a far better understanding of all the bits around it15:32
matttodyssey4me: sweet15:33
odyssey4meand yeah, a link to an eavesdrop log or something would be amazing15:33
matttperhaps we need to look at a venv for the repo server15:33
matttwhich gets sucked in from an external source15:33
odyssey4mesigmavirus24 wheel 0.26 created a wheel called cffi-1.5.2-cp27-none-linux_x86_64.whl and wheel 0.29 created one called cffi-1.5.2-cp27-cp27mu-linux_x86_64.whl - what's the extra bit in the middle signify?15:34
andrei_hey guys! Is there any way to _not_ copy ceph keyrings from monitor nodes? In current playbook https://github.com/openstack/openstack-ansible/blob/master/playbooks/roles/ceph_client/tasks/ceph_auth.yml#L25-L77 where is connection toward monitors and ceph auth get. I want to create users on ceph, copy them somewhere so OA can read them.15:36
*** spotz_zzz is now known as spotz15:36
*** mgugino has joined #openstack-ansible15:36
*** pcaruana has quit IRC15:37
*** mgoddard__ has quit IRC15:37
sigmavirus24odyssey4me: it's part of the platform identifier but I'm honestly not sure exactly what it means. I suspect it has to do with the fact that it's identifying C-extensions and that it adds that information to the identifier for pip/other tools15:38
*** mgoddard has joined #openstack-ansible15:38
hughsaundersapparently the m signifies --wtih-pymalloc and u --with-wide-unicode15:39
hughsaundersaccording to https://www.python.org/dev/peps/pep-3149/15:39
matttodyssey4me: so i put that wheel review through on kilo, since that is the most pressing branch ... i'll remove WIP and manually cherry-pick to liberty and create a separate review for the repo_server role in master15:41
cloudnullo/ all15:42
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: Ironic: Fix docs & linting tests  https://review.openstack.org/28338415:42
odyssey4methanks mattt15:44
cloudnullodyssey4me: from the keystone role keystone_developer_apt_packages is in the vars15:45
cloudnullhttps://github.com/os-cloud/openstack-ansible-os_keystone/blob/master/vars/ubuntu-14.04.yml15:45
stevelleandrei_: doesn't look like we have support for that right now.15:45
odyssey4melol cloudnull I should have thought to look there :p15:45
cloudnulli followed the other patterns for package installs15:45
Bofu2Umorn15:46
*** pcaruana has joined #openstack-ansible15:49
palendaeraddaoui: I didn't get to testing https://review.openstack.org/#/c/282067/ yesterday, but spinning up an AIO to play with it now15:49
raddaoui__okay thanks palendae let me know if you need any explanation on it15:53
cloudnullodyssey4me: what patches did you need me to review?15:53
cloudnullreffering back to your convo with bgmccollum15:54
spotzo/15:55
openstackgerritMatt Thompson proposed openstack/openstack-ansible: Pin wheel version in repo_server role  https://review.openstack.org/28365715:57
izaakko/15:57
*** gparaskevas has quit IRC15:58
cloudnullalso mattt odyssey4me what issues were you seeing with https://review.openstack.org/#/c/279683/15:59
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Resolve packaging problems in virtualenv(s)  https://review.openstack.org/27968316:00
*** mgoddard_ has joined #openstack-ansible16:01
*** phalmos has joined #openstack-ansible16:01
*** raddaoui__ has quit IRC16:01
*** raddaoui__ has joined #openstack-ansible16:01
*** mgoddard has quit IRC16:04
rromans.16:04
*** raddaoui__ has quit IRC16:05
*** raddaoui has quit IRC16:05
*** raddaoui_ has quit IRC16:06
*** raddaoui has joined #openstack-ansible16:06
*** raddaoui_ has joined #openstack-ansible16:06
*** raddaoui has quit IRC16:06
*** raddaoui_ has quit IRC16:06
*** raddaoui_ has joined #openstack-ansible16:07
*** raddaoui has joined #openstack-ansible16:07
*** severion has quit IRC16:10
*** kysse_ has joined #openstack-ansible16:10
*** tiagogomes has joined #openstack-ansible16:12
*** subscope has joined #openstack-ansible16:14
*** baker has joined #openstack-ansible16:14
tiagogomesA question: is master already targeting Mitaka? And if so, is the development being made on a Ubuntu 16.04 image?16:14
*** nn_brian has joined #openstack-ansible16:14
palendaetiagogomes: Yes, no16:15
*** phiche has quit IRC16:15
palendaetiagogomes: The release windows are super tight, and there was the indpendent role repository work going into mitaka, too16:15
*** phalmos has quit IRC16:16
tiagogomesthanks palendae16:18
matttspotz: argh :P16:18
*** KLevenstein_ has joined #openstack-ansible16:19
openstackgerritMatt Thompson proposed openstack/openstack-ansible: Pin wheel version in repo_server role  https://review.openstack.org/28365716:19
openstackgerritMatt Thompson proposed openstack/openstack-ansible: Pin wheel version in repo_server role  https://review.openstack.org/28303916:20
spotzmattt That's why you guys keep me around:)16:20
matttspotz: nah, good catch, thanks !  :)16:21
nn_brianHey, folks. Executing my first openstack-ansible install. Attempting AIO on an Ubuntu 14.04 VM on KVM. The run-playbooks.sh step fails with dozens of errors like the following:16:21
mattti need a vim spell checker :)16:21
nn_brian<172.29.238.182> REMOTE_MODULE pip name=pycrypto state=present extra_args=''16:21
nn_brian<172.29.238.182> EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/root/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o KbdInteractiveAuthenticati16:21
nn_brianon=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=120 172.29.238.182 /bin/sh -c 'LANG=en_US.UTF-8 LC_CTYPE=en_U16:21
nn_brianS.UTF-8 /usr/bin/python'16:21
nn_brianResult from run 1 is: {'msg': "stdout: Ignoring indexes: https://pypi.python.org/simple\nCollecting pycrypto\n\n:stderr: Retrying (Retry(total=4, connect=None, read=None, redirect=None)) afte16:21
nn_brianr connection broken by 'ProtocolError('Connection aborted.', error(111, 'Connection refused'))': /os-releases/11.2.10/\n Retrying (Retry(total=3, connect=None, read=None, redirect=None)) afte16:21
nn_brianr connection broken by 'ProtocolError('Connection aborted.', error(111, 'Connection refused'))': /os-releases/11.2.10/\n Retrying (Retry(total=2, connect=None, read=None, redirect=None)) afte16:21
nn_brianr connection broken by 'ProtocolError('Connection aborted.', error(111, 'Connection refused'))': /os-releases/11.2.10/\n Retrying (Retry(total=1, connect=None, read=None, redirect=None)) afte16:21
nn_brianr connection broken by 'ProtocolError('Connection aborted.', error(111, 'Connection refused'))': /os-releases/11.2.10/\n Retrying (Retry(total=0, connect=None, read=None, redirect=None)) afte16:21
nn_brianr connection broken by 'ProtocolError('Connection aborted.', error(111, 'Connection refused'))': /os-releases/11.2.10/\n Could not find a version that satisfies the requirement pycrypto (from16:21
nn_brian versions: )\nNo matching distribution found for pycrypto\n", 'failed': True, 'attempts': 1, 'cmd': '/usr/local/bin/pip install pycrypto'}16:21
nn_brianNot sure where to look for root causes. Any ideas?16:22
*** KLevenstein has quit IRC16:22
*** KLevenstein_ is now known as KLevenstein16:22
spotzmattt but then I won't have a job!16:23
*** phiche has joined #openstack-ansible16:25
*** subscope has quit IRC16:27
nn_brianThe output I submitted, above, is the result of setting the -vvvv flag on the ansible calls in the script. The error is not limited to pycrypto. A number of other packages also elicit the complaint that a matching distro can't be found. I've tried installing the packages by hand in advance, but still I see these errors.16:30
odyssey4menn_brian convention when working via IRC would be to paste logs into pastebin rather than in the channel16:30
odyssey4methen you just link the pastebin link16:31
nn_brianOops. Thanks, odyssey4me. I'll figure out how to do that and repost.16:33
odyssey4menn_brian this is an AIO, correct? did you complete the boostrap-ansible then bootstrap-aio steps without a problem?16:33
*** retreved has joined #openstack-ansible16:33
odyssey4menn_brian also, does your AIO have more than one network interface? is it virtualbox/vmware/a public cloud/what exactly?16:34
nn_brianodyssey4me yes, both bootstrap steps completed without error. The VM is running on KVM on a CentOS server in my lab. No public access. Checking on the number of interfaces...16:36
odyssey4menn_brian it will need public access - it needs to fetch packages from pypi, keys from key servers, etc16:37
nn_brianodyssey4me It has one virtual NIC. It is configured for NAT and can get out. What I meant by "no public access" is that there isn't an easy way for someone on the outside to get in.16:38
nn_brianodyssey4me I can, for example, do a command line pip install. No problems there.16:39
odyssey4menn_brian ah, that's no problem - assuming you don't want to get to Horizon and are prepared to do all testing from inside the environment16:39
odyssey4mealright, that's a start - now it'd be useful to know which branch/tag you cloned and where it actually failed the install process16:40
nn_brianodyssey4me after the clone I did a git checkout kilo16:40
odyssey4merun_playbooks runs through a sequence of playbooks - it failed on one of them... it'd be good to know which one it failed in16:41
cloudnullbgmccollum: you around ?16:41
nn_brianodyssey4me let me check16:41
cloudnullon https://review.openstack.org/#/c/283234/16:41
cloudnulli think all we need is https://review.openstack.org/#/c/283234/1/playbooks/os-cinder-install.yml16:41
cloudnulland the rest is done for us16:41
odyssey4menn_brian ah ok, in that case it's a known issue being dealt with by https://review.openstack.org/28303916:41
odyssey4menn_brian is there a particular reason you're going for kilo rather than something later?16:42
cloudnullseems there was a regression/typo when the storage address bits were addressed a while ago16:42
nn_brianodyssey4me no. I started with kilo because I assumed stability. What would you recommend as a starting place? This is for Nuage integration work with RackSpace...16:43
*** subscope has joined #openstack-ansible16:45
matttcloudnull: sorry, just saw your message ... not seeing any issues w/ https://review.openstack.org/#/c/279683/, but i think odyssey4me mentioned it as potentially being related to https://review.openstack.org/#/c/283039/16:45
odyssey4menn_brian kilo is stable for production, but the production deployment mechanism does not use run_playbooks (which is for development/testing purposes)16:45
nn_brianodyssey4me ah. I didn't know that.16:46
odyssey4menn_brian kilo, though, is already in security-only fixes in OpenStack, and close to it in OpenStack-Ansible... so Liberty would be a better bet for stability16:46
cloudnullseems like those patches should go hand in hand.16:46
odyssey4menn_brian especially when you're doing an eval for production purposes16:47
cloudnullvirtualenv is pulling in pip8 by default for new venvs16:47
cloudnullso pinning wheel makes sense16:47
nn_brianodyssey4me so I should clean up, switch to liberty, and execute run-playbooks. Cool. Thanks.16:48
*** javeriak has joined #openstack-ansible16:48
odyssey4menn_brian yep, there is a teardown script in scripts that'll do a rather destructive teardown16:48
nn_brianodyssey4me very good. thanks for the help. And I'll use pastebin next time. :-)16:49
odyssey4menn_brian considering that you're building an AIO with no tweaks - I'd suggest just tearing down the whole VM and restarting from scratch - otherwise you'll be missing config bits16:49
odyssey4menn_brian no problem :) happy to help and advise - looking forward to further interaction :)16:49
nn_brianodyssey4me I have a clone of just the OS bits. I can recreate the VM quickly and start with the clone, bootstraps, and all that.16:50
nn_brianodyssey4m many thanks!16:50
odyssey4menn_brian yeah, just don't forget to checkout to liberty or the most recent liberty tags (12.x)16:50
*** chhavi has joined #openstack-ansible16:51
nn_brianodyssey4me yeah, i saw that in the quick-start guide. I'll grab the latest 12.x tag16:51
tiagogomescloudnull, my deployment is failing in the "set local_ip fact (is_metal)" task, on os-neutron-install.yml. The error is that _overlay_network does not have a bridge defined. I can't see how _overlay_network would get any meanful value, as 'tunnel_address' does not seem to be defined anywhere16:54
*** mgoddard has joined #openstack-ansible16:55
*** mgoddard_ has quit IRC16:55
bgmccollumcloudnull16:56
cloudnullbgmccollum: ohai .16:56
bgmccollumcloudnull i was trying to also separate management and storage traffic...hence the separate cinder_iscsi_ip_address role variable...16:57
*** javeriak_ has joined #openstack-ansible16:57
bgmccollumdb, rabbit, api over mgmt, iscsi over storage16:57
*** javeriak has quit IRC16:57
cloudnullbgmccollum: all we should have to do is that one change to set the myip16:58
cloudnullhttps://review.openstack.org/#/c/28323416:58
cloudnulli updated that16:58
cloudnullsorry16:58
cloudnulli can revert it16:58
cloudnullbut thats what we had set in juno/icehouse.16:59
cloudnulltiagogomes: tunnel_address is set within the openstack_user_config16:59
bgmccollumlooking16:59
tiagogomescloudnull I don't use tunnels for tenant networks, only VLANs17:00
cloudnullah.17:01
*** mikelk has quit IRC17:05
bgmccollumcloudnull so, i was under the assumption that things like db, rabbit, internal api would use the br-mgmt...and just the storage type traffic would use the storage network. they way it is now, either everything is storage network, or everything is management network.17:05
bgmccollumlook again at patch set 417:06
odyssey4mebgmccollum if that is the case, then I'd prefer your model - mgmt related traffic should be isolated onto the appropriate network, and data on its own - it's important for security and performance to isolate them properly17:07
odyssey4memhayden ^ your thoughts?17:07
*** asettle has quit IRC17:08
odyssey4memhayden also, I thought you may be keen to look into a PoC for implementing something like https://www.hastexo.com/blogs/florian/2016/02/21/containers-just-because-everyone-else/ suggests ?17:09
* mhayden ganders17:09
mhaydenah, overlayfs?17:09
odyssey4meit would have to be an optional feature, not enabled by default (at least initially while it's being battle tested), but if implemented properly it could probably be a massive optimisation17:10
mhaydenit might be easier to get to systemd-nspawn at some point instead17:10
*** nn_brian has quit IRC17:11
*** phalmos has joined #openstack-ansible17:11
odyssey4meautomagically that may be of interest to you guys too17:13
cloudnullbgmccollum:  I see what your getting at17:14
openstackgerritKevin Carter proposed openstack/openstack-ansible: Set the storage address for cinder  https://review.openstack.org/28323417:15
cloudnullbgmccollum: ^17:18
cloudnulltiagogomes: it seems we've made the assumption that an overlay network will be there.17:19
bgmccollumYeah one issue...since we're using multi-backend style configs, you have to specify the iscsi_ip_address inside each backend section17:19
cloudnullreally  ?17:19
bgmccollumyeah its stupid17:19
cloudnullwe didnt have to do that in Juno ?17:19
*** severion has joined #openstack-ansible17:20
bgmccollumhttp://lists.openstack.org/pipermail/openstack-operators/2013-August/003410.html17:20
cloudnullbummer17:21
bgmccollumalso, i tried limiting it to just the LVM iSCSI driver...but i dont know if thats futile, or if there is any harm to set for every backend type17:21
bgmccollumlike, are there other drivers that use the option, and do we need to maintain a list, or just fire and forget17:22
cloudnullso that needs to be set in the openstack_user_config17:22
cloudnullfor the various drivers.17:22
bgmccollumwill the variable "resolve" before the set fact tasks that discover `cinder_storage_address`?17:22
bgmccollumtemplated variable precedence in ansible is hard to wrap my head around sometimes17:23
*** nn_brian has joined #openstack-ansible17:26
automagicallyodyssey4me: Thanks for the pointer17:27
*** sdake_ has joined #openstack-ansible17:28
*** GheRivero has joined #openstack-ansible17:28
cloudnullbgmccollum: yes we can set it here https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio#L11417:29
*** phalmos has quit IRC17:30
*** sdake has quit IRC17:30
*** Nepoc has quit IRC17:30
bgmccollumok, but set it to what? isn't this the input to generate the inventory? can you even reference a yet to be defined variable here?17:31
bgmccollum"{{ cinder_storage_address }}" ?17:31
odyssey4mebgmccollum so the one option is for a deployer to set it themselves, and we take all the guessing out of the playbooks/tasks... this is simple, but not particularly friendly17:32
*** sdake_ is now known as sdake17:33
odyssey4meanother option is to try and derive it - this is friendly, but causes a frankenmess of code17:33
*** subscope has quit IRC17:33
* stevelle votes for explicit deployer choice17:34
odyssey4meI'm actually leaning towards taking the code-based guessing out and implementing documentation, and perhaps show by example in the AIO, to show that if you want the traffic segregation then you need to change your user config17:34
automagicallySeems like the most desirable case would be for traffic segregation17:35
bgmccollumso...to actually make it work, are you saying you have to specify the as yet unknown storage IP address in your use config...or is there a was to reference the storage address after the dynamic inventory has created it...17:35
odyssey4meif we do anything to simplify this, then this is another case where an improvement to the dynamic inventory could be used17:35
automagicallyAnd as much as possible, I’d expect OSA to be opinionated in that regard and do the best practice thing17:36
stevelle^ or at least document and make it somewhat easy17:36
automagicallyArriving at a clean implementation seems to be the sticky bit17:36
bgmccollumhow do you set the iscsi_ip_address user config if you dont know it yet because it hasn't been assigned17:36
odyssey4meyeah, but what I'm seeing at the moment is a set of tasks which don't quite reach the desired result and are complex and hard to follow17:37
openstackgerritKevin Carter proposed openstack/openstack-ansible: Set the storage address for cinder  https://review.openstack.org/28323417:37
bgmccollumalthough, cinder-volume LVM iSCSI runs on metal now by default...but the issue still stands17:37
cloudnullbgmccollum:  ^17:37
*** Nepoc has joined #openstack-ansible17:38
bgmccollumi was unsure if something like that would work...17:38
odyssey4mebgmccollum Using Cinder backed by LVM is, according to most everyone I talk to in OpenStack development, supposed to be for reference only - not production17:38
odyssey4mebut that's a side issue anyway17:39
bgmccollumwell, this all started because Bofu2U was confused why his really expensive storage network wasn't being used at all, and i recall this being fixed in icehouse...so dug in.17:40
bgmccollumcloudnull patch set 8 looks good...ill queue up a build with that and test...17:42
odyssey4mebgmccollum yeah, and thanks for doing so - I'm just expressing a desire for a fresh look at how we do things sometimes17:43
*** admin0 has joined #openstack-ansible17:44
*** admin0 has quit IRC17:49
bgmccollumunderstood17:49
bgmccollummo betta17:49
bgmccollumnoms17:49
*** admin0 has joined #openstack-ansible17:50
*** tiagogomes has quit IRC17:55
*** chhavi has quit IRC18:02
*** chhavi has joined #openstack-ansible18:03
Bofu2Uyeah it makes me want to cry18:05
Bofu2Uthough I'm going to get one of these reattached to see if it worked18:05
odyssey4meandymccr mrda I have achieved convergance for Ironic in standlone mode.... it doesn't work, but the plays execute - which is a start18:09
odyssey4melemme get a WIP patch up18:10
cloudnullim going to sleep a bit more, still feeling terribad. will try to be back later.18:12
odyssey4methanks for checking in cloudnull - get well soon!18:13
cloudnullnp. ill try to do more later today18:13
cloudnullbgmccollum Bofu2U: let me know how the storage thingamies go18:14
cloudnulltiagogomez i think we need to revisit the nova play to make it so that we're not assuming a tenant network isnt always there.18:14
cloudnullthats all i got.18:14
sigmavirus24odyssey4me: I think if you're worried about pip breaking things then your concerns are misplaced. What you should do is black list the known bad versions of pip8 because those bugs you linked in #pypa-dev are fixed appropriately18:17
sigmavirus24so blacklist 8.0.0, 8.0.1, 8.0.2, (I think 8.0.3 works fine iirc)18:17
odyssey4mesigmavirus24 sure, that is an option - except what's to prevent the same thing happening again18:18
sigmavirus24But trying to cap pip and setuptools and wheel and whatever else you can imagine is going to breed pain, suffering, and a need in the future to remove those18:18
odyssey4methe whole point of constraints is to be preventative in a stable environment18:18
sigmavirus24odyssey4me: except the only problem that led to the capping has been fixed (and it won't be reverted until we can get downstreams on board with a lot of packaging changes for their distros - in other words, we have several years before we'll get to a state where that change can be reintroduced)18:19
sigmavirus24Further, wheel being uncapped is only problematic because we're on an old unsupported version of pip. It's a version distros are not supporting and neither is the PyPA18:19
sigmavirus24So being preventative of possible issues in a stable environment is fine so long as we're committed to supporting unsupported versions in this project18:20
sigmavirus24(note this is part of why OpenStack is using constraints and not upper caps at the gate)18:20
*** elo has joined #openstack-ansible18:30
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: [WIP] Ironic: Add standalone convergance test  https://review.openstack.org/28374218:31
*** phalmos has joined #openstack-ansible18:32
odyssey4mesigmavirus24 so I think we'd be ok with sticking with an older version of pip & wheel, assuming it works for the lifetime of the stable branch in question18:33
odyssey4meit's a question of risk and the management of that risk18:33
odyssey4meif we feel that the risk warrants staying at a cap, then we do that18:34
odyssey4meif we don't, then we uncap it and deal with that18:34
sigmavirus24odyssey4me: except upstream is releasing things (like glance_store) that are being used on stable branches and tested with newer versions of pip and wheel meaning that anything we run into with our capped versions is going to hurt us18:35
odyssey4mebut the theory is that if you deploy a tagged kilo branch at any time in the lifetime of the branch's support life cycle, you should end up with a functional result that it equal to the day the tag was pushed18:35
odyssey4meyeah, this is why this is specifically hurting us in the kilo branch where there are no upper constraints to rely on18:36
sigmavirus24odyssey4me: speaking for openstack that isn't entirely true the way we do deploys because you'd have to coordinate upper-constraints and everything else18:36
odyssey4mein other branches we should better implement the use of upper constraints for all elements18:36
*** phiche1 has joined #openstack-ansible18:37
*** phiche has quit IRC18:37
*** KLevenstein has quit IRC18:39
*** nn_brian has quit IRC18:41
*** javeriak_ has quit IRC18:43
odyssey4mehmm, so there's a thing - all the devstack vm's have the current uppser constraints file on them and that file is used for the build18:46
*** chhavi has quit IRC18:47
odyssey4meI would guess that this means that the current master branch upper constraints are being used when testing stable/kilo patches18:47
*** javeriak has joined #openstack-ansible18:48
odyssey4meif that is true, then all we'd need to do is find a way to grab that file and consume it for the repo build process in kilo18:49
odyssey4methat said, this would be a partial reimplementation of what's already been done with the repo build process do-over18:49
*** admin0 has quit IRC18:50
odyssey4mestevelle FYI rechecking https://review.openstack.org/278037 doesn't give you much as it only affects the sources on the host - it's partnered with https://review.openstack.org/278033 which affects the containers18:51
odyssey4mestevelle once those are through I can continue work on https://review.openstack.org/279633 which is where the real optimisation starts to happen18:51
stevelleodyssey4me: Yeah, just doing some data collection and I wanted 3 samples for the hosts.18:52
odyssey4mestevelle sure - what's the data looking like so far?18:52
stevelleso far 1:08-1:10 are dominant timings18:52
stevelleoutliers over 1:2018:52
odyssey4meall the same provider?18:52
stevellethats for all providers so far,18:53
*** asettle has joined #openstack-ansible18:53
stevelleneed more samples (10+) to say anything meaningful for specific providers18:53
odyssey4meI don't see it making a big difference for an AIO. I think it'll be a nice difference when you combine the two, and when you have more hosts.18:54
stevelledocs changes are fast but don't tell us much :)18:54
stevelleyeah, betting the containers change will help a little bit more18:54
*** kencjohnston has quit IRC18:55
odyssey4methe apt cache update dependent on whether the cache has expired seems to have helped just a little bit18:55
*** subscope has joined #openstack-ansible18:56
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Gate: Use apt sources configured on the host  https://review.openstack.org/27963318:57
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Gate: Use apt sources configured on the host  https://review.openstack.org/27963318:58
bgmccollumre caps...why cant *everything* be capped after the last successful build before being tagged...then caps removed after tagging for dev work...this is environment rot because of uncapped constraints.18:58
odyssey4mebgmccollum because then we'd need to have a task (figure out the current caps required and put together a patch) for someone to do before a tag, we'd have to ensure that everything else is blocked from merging into the branch, then merge the patch, then tag, then undo all the above18:59
odyssey4meupper constraints was built to reduce that overhead, but unfortunately is not in kilo19:00
bgmccollumok so its just a problem for kilo ATM19:00
odyssey4meit's only a problem for kilo when doing a repo-build, which is not what is used for production (that uses a repo-clone from rpc-repo)19:01
odyssey4meso it's very specifically an issue for gating and development19:01
odyssey4meand anyone who's using run-playbooks, and I hope to goodness that no-one is using that in production!19:02
odyssey4mestevelle I'm not sure if you've seen https://review.openstack.org/276766 - but it is another very small optimisation19:06
stevellehadn't pulled that one up yet odyssey4me19:06
*** electrofelix has quit IRC19:07
*** admin0 has joined #openstack-ansible19:07
*** subscope has quit IRC19:08
admin0can we DVR using the ansible playbooks ?19:12
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Remove dependency on python2_lxc git source  https://review.openstack.org/27676619:13
odyssey4meadmin0 not at this stage - DVR is not supported by Neutron when using the Linuxbridge Agent19:14
admin0ok19:14
admin0is it on the roadmap ?19:14
odyssey4meadmin0 there are some guys in the project working on adding OVS support, and then DVR on top of that19:14
admin0ok19:14
odyssey4meadmin0 you can see their progress in the etherpad linked from the meeting agenda19:15
admin0aha :)19:15
admin0\o/19:15
odyssey4mesigmavirus24 we're going to discuss the pip capping, etc in the weekly meeting on thu - can you make it to help with the discussion? I'd like us to be in a position to make informed choices. :)19:17
sigmavirus24odyssey4me: I'll add it back to my calendar I think I have a different meeting at the same time though19:19
sigmavirus24Just ping me anyway19:19
odyssey4mesigmavirus24 I'll ping you when the topic comes up. Thanks!19:20
sigmavirus24Any idea why "{# keystone_service_internaluri_v3 #}" would end up in a config file when we were using {{ keystone_service_internaluri_v3 }}?19:20
sigmavirus24did we kill that var?19:21
*** neerbeer has joined #openstack-ansible19:22
*** javeriak_ has joined #openstack-ansible19:22
odyssey4mesigmavirus24 that var should only be used inside the keystone role as I recall19:22
sigmavirus24odyssey4me: aha, this was working a week ago19:23
odyssey4meliberty+ the internaluri var is v3 anyway19:23
meteorfoxif have a standalone-swift with 5 nodes, and they are configured as 1 swift_host per zone. If I change the zone values on the swift.yml and re-run os-swift-install playbook, will it work? or do I have to start from scratch? Also same question for the repl_ip? I'm trying to reconfigure it to match another lab which has 1 zone per Rack, so I can  configure19:23
meteorfoxthem in a multi-region configuration19:23
sigmavirus24Guess anyone developing third party roles shouldn't try to depend on any vars :+1:19:23
odyssey4mesigmavirus24 yep - no such var any more - if it worked previously, you must be using something horribly old: https://github.com/openstack/openstack-ansible/blob/master/playbooks/inventory/group_vars/hosts.yml#L190-L19619:24
*** javeriak has quit IRC19:24
sigmavirus24Might be two weeks old but was definitely working last I used this role19:24
odyssey4meodd, as this change was implemented for the Liberty release - so it's been there for quite some time19:26
*** Nepoc has quit IRC19:26
*** javeriak has joined #openstack-ansible19:26
stevellesigmavirus24: sounds like a topic we need to establish a set of expectations on (dependence on vars)19:27
*** Nepoc has joined #openstack-ansible19:27
sigmavirus24stevelle: yeah or we just document what ones other people can expect to work19:27
sigmavirus24the latter would be nicer honestly19:27
*** javeriak_ has quit IRC19:27
stevelle+1 ^19:27
stevellewe will need to establish an api contract of sorts if we expect to make IRR work, let alone allow 3rd party roles to build on osa reliably19:28
palendaeYou mean like a public API?19:28
stevellejinx palendae19:28
palendaemrda was having a lot of headaches building ironic last night19:29
odyssey4meyeah, we started a discussion around approximately that topic at the mid cycle - but never quite finished it19:29
palendaeNo, and I'm not sure how many in the greater ansible community are approaching it, either19:29
palendaeThe only project I know of that's making roles on this scale is debops19:29
odyssey4meloads of people are making many roles, but most roles are only applied to small numbers of servers19:30
*** Nepoc has quit IRC19:30
stevelleI think a small working group of a couple folks can probably start to enumerate the kinds of things we know we will need (things like identity endpoints, db and mq endpionts, etc)19:30
*** KLevenstein has joined #openstack-ansible19:30
*** asettle has quit IRC19:30
odyssey4mewe have scale complexities in many directions in the project19:30
stevelleand it can grow from that starting point19:30
palendaeodyssey4me: True, but are they public like this?19:30
palendaeMy sense is that most ansible stuff is being written for private use19:31
odyssey4mestevelle yeah, I'm in favour of a small working group being put together to put together a starting doc which can then be put into a review19:31
odyssey4mepalendae lots is in the public domain too, but not too many of those are reusable by other environments19:31
odyssey4meand certainly not very reusable at scale19:32
palendaeYeah19:32
odyssey4memost of the role do simple things like setup Apache - they don't care too much about more complex changes thereafter.... when you deal with small number of servers, you don't care that your config is rewritten every time you execute a playbook because you only ever do that once in a while19:33
palendaeRight19:34
odyssey4mewe're trying to achieve lofty goals like idempotence, maximum uptime, and stable interfaces into roles and to implement playbook entry points that go through a deprecation cycle19:35
odyssey4memost roles I've seen don't even bother tagging or considering a 'stable' policy19:35
odyssey4methey're either roles that never change, or they're roles used in very tight ecosystems19:36
stevellewe be pioneerin19:37
stevelle...lunch time19:37
automagicallyThe var dependency and namespacing thing is a must19:39
automagicallyThe problem is that you end up with lots of assign this var to this role namespaced var all over the place19:39
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Remove dependency on python2_lxc git source  https://review.openstack.org/27676619:42
*** eil397 has joined #openstack-ansible19:43
*** Nepoc has joined #openstack-ansible19:44
*** phiche1 has quit IRC19:46
*** phiche has joined #openstack-ansible19:46
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-ironic: [WIP] Ironic: Add standalone convergance test  https://review.openstack.org/28374219:47
odyssey4meautomagically yeah, so it falls to us to figure out a pattern which works for us19:47
odyssey4mesomething that is more predictable, easy to understand and easy to also troubleshoot when precedence gets hairy19:48
automagicallyCompletely agree, well worth a blueprint/spec writeup19:50
*** fawadkhaliq has joined #openstack-ansible19:52
*** javeriak_ has joined #openstack-ansible19:53
*** javeriak has quit IRC19:56
openstackgerritNolan Brubaker proposed openstack/openstack-ansible: [WIP] Add support for upgrading from Kilo to Liberty  https://review.openstack.org/27218219:57
odyssey4mepalendae would it be possible to break that upgrade patch down into some foundational elements (scaffolding for docs and initial script that does nothing) in order to allow focused patches on top of it that deal with specific elements?19:59
odyssey4methat makes it easier to evaluate and review items in isolation19:59
palendaeodyssey4me: I'm thinking about it; I really hate the idea of a commit for a scaffold, but if that's what people want I can do it20:00
palendaeI'm almost to the point of letting it go for review20:00
palendaeIn which case I'll break it up20:00
odyssey4meah ok, in that case keep at it20:00
odyssey4meI'd just rather not have patches being held back because people are waiting to see if you do it20:00
palendaeI'm testing my last changes, then going to do a release note once those are done20:00
palendaeRight - my intention with it now is to stop adding new things20:01
palendaeIf there's problems with what's there I'll fix it20:01
openstackgerritMerged openstack/openstack-ansible: Docs: IP range values should be consistently formatted  https://review.openstack.org/28323720:01
palendaeBut getting it merged and unblocking stuff is the priority20:01
openstackgerritMerged openstack/openstack-ansible: Fix bootstrap-ansible.sh invocation directory  https://review.openstack.org/27852320:01
palendaeGot a little carried away with it, admittedly20:01
odyssey4mepalendae cool - it doesn't have to be perfect, just having it work on a prestine AIO is certainly good enough as a starting point20:01
palendaeRight20:01
*** javeriak has joined #openstack-ansible20:01
palendaeThat's what I'm trying now20:01
palendaeI'm hoping my latest changes also negate the need for RUN_TASKS, but I'm not gonna make a big deal of that point in this round20:02
*** javeriak_ has quit IRC20:02
odyssey4meI'm hoping that we can implement the scaffolding in Mitaka asap too, so that we can also require upgrade tasks (along with docs and release notes) where necessary for new patches coming in20:04
palendaeAnnnd of course as soon as I get it on an AIO, I see dumb typose20:04
palendaeYeah, I was considering doing some Mitaka work in parallel20:04
palendaeBut I'd rather not take all of that on myself20:04
odyssey4methat way the upgrade burden is far less when we start actually testing master branch upgrades20:04
palendaeYep20:05
palendaeThat was my hope for liberty, too20:05
palendaeBut alas, did not happen20:05
*** Bjoern_ has quit IRC20:05
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible: Check local and upstream repo for pip before using pypi  https://review.openstack.org/27790520:06
palendaeUpgrade gating would be awesome20:06
palendaeBut that's a task in and of itself20:06
*** Nepoc has quit IRC20:12
*** Nepoc has joined #openstack-ansible20:12
palendaeodyssey4me: I have made what I believe is my last code change that I know is necessary. Want me to get a release note in before I remove the WIP tags?20:14
odyssey4mepalendae please - the release note should add a 'feature' not (or set of feature notes) and refer to the URL for the documentation... no need to retype all the docs stuff20:15
odyssey4merelease notes should just be a short reference summary with links for further details20:15
palendaeOk. I have no docs stuff right now; it's certainly need but also a big patchset >.<20:15
palendaeneeded*20:15
*** subscope has joined #openstack-ansible20:16
odyssey4menow you see why I suggested the scaffolding :)20:16
palendaeYeah, I get it20:16
odyssey4meif it's in a working proof of concept state, then it may be easier to break up now20:16
palendaeYeah, I'll upload this last change so it's not just on my computer and go back and do that20:17
palendaeNot sure if that'll abandon https://review.openstack.org/#/c/272652/2 or not20:17
palendaeI could even start with that one20:17
odyssey4methanks palendae, I know this is tough work and I'm happy to see it taken on - I hope that we're learning enough through each iteration in order to provide feedback into the development process20:18
palendaeYeah; I have some notes on the specific things, so I'll try to get the commit messages focused around that20:18
openstackgerritNolan Brubaker proposed openstack/openstack-ansible: [WIP] Add support for upgrading from Kilo to Liberty  https://review.openstack.org/27218220:19
palendaeOk, abandoned with a note, but I'll start into breaking that up this afternoon. That may break https://review.openstack.org/#/c/272652/ then20:21
*** javeriak has quit IRC20:21
*** javeriak has joined #openstack-ansible20:24
*** javeriak_ has joined #openstack-ansible20:26
odyssey4memrda please feel free to continue work on https://review.openstack.org/283742 when you come online, or start putting together an alternative, or just comment on the existing review - I'm working a little blind on it but I think it's important to have a convergence and functional test (in the end) for the standalone and distributed code paths).20:27
odyssey4meI simply picked the standalone code path because I figured it'd be a simpler start.20:27
odyssey4meI'm going offline now. afk until morning.20:28
spotzNight odyssey4me20:29
*** javeriak has quit IRC20:29
*** flwang has quit IRC20:31
*** javeriak_ has quit IRC20:31
*** javeriak has joined #openstack-ansible20:35
openstackgerritKevin Carter proposed openstack/openstack-ansible: Add condition to local IP for overlay net  https://review.openstack.org/27379320:50
*** javeriak_ has joined #openstack-ansible20:50
mrdaodyssey4me: thanks for your work on this today!  Greatly appreciated - there were some assumptions about environments (linters, functional etc) that didn't click until late yesterday.  Thanks for your help!20:50
sigmavirus24spotz: someone said you were interested in/working on barbican? Is that true?20:54
*** javeriak has quit IRC20:54
*** dmsimard|afk is now known as dmsimard20:57
*** flwang has joined #openstack-ansible20:58
flwanghi guys, i have a question about this doc   http://docs.openstack.org/developer/openstack-ansible/developer-docs/quickstart-aio.html21:00
flwangnow i'm working on ansible zaqar and i'm wondering the dev/test steps21:00
flwangafter download the openstack-ansible code,  then i ran $ scripts/bootstrap-ansible.sh21:01
flwangso for the next step, do i have to run   $ scripts/bootstrap-aio.sh ?  can i just run   $ cd /opt/openstack-ansible/playbooks $ openstack-ansible os-zaqar-install.yml21:01
sigmavirus24flwang: bootstrap-aio.sh is a good idea but it depends on how os-zaqar-install works :)21:02
bgmccollumbootstrap-aio.sh only if you're actually setting up an AIO21:03
*** leifmadsen has quit IRC21:04
bgmccollumand as long as you have an appropriate env.d and conf.d files for your zaqar role...then it should work...21:04
bgmccollum"should" â„¢21:05
*** leifmadsen has joined #openstack-ansible21:05
sigmavirus24And user vars and other stuff21:06
sigmavirus24But yeah, I'm too lazy to be certain everything's correct :)21:06
cloudnullflwang:  i21:07
cloudnullsorry.21:07
cloudnullflwang: I'd just run the gate-check-commit.sh script which will do all that for you, as you stand up a test env21:07
openstackgerritMerged openstack/openstack-ansible-lxc_hosts: Set container apt sources to use a configured list of components  https://review.openstack.org/27803321:08
*** Bofu2MBP has joined #openstack-ansible21:10
flwangcool, thank you guys.21:10
flwangthe next question21:10
flwangnow i'm putting all the ansible zaqar code in a separate repo21:10
flwangso when I test the code, should i copy the code into openstack-ansible tree? or there is another good way?21:11
sigmavirus24ansible-galaxy flwang21:11
sigmavirus24assuming it's in a role structure21:11
sigmavirus24flwang: something structured roughly like https://github.com/sigmavirus24/openstack-ansible-magnum will allow you to do `ansible-galaxy install https://github.com/sigmavirus24/openstack-ansible-barbican` and then put your playbook in `openstack-ansible/playbooks/` and run it from that directory with `openstack-ansible os-zaqar-install.yml`21:12
flwangsigmavirus24: cool, but the help usage of ansible-galaxy is not very detailed21:12
flwangand then put your playbook in `openstack-ansible/playbooks/`   so for this step, i still need to manually copy the code, right?21:13
*** neerbeer has quit IRC21:13
spotzsigmavirus24 I used to be involved with the team, I sit over with them still21:14
sigmavirus24spotz: someone mentioned you might be interested in hacking on an OSA role to deploy it21:15
sigmavirus24flwang: yes you would need to manually copy your playbook21:15
spotzsigmavirus24 I did look at it one day when I was bored21:15
flwangsigmavirus24: got it, thanks a lot21:16
*** javeriak has joined #openstack-ansible21:18
*** javeriak_ has quit IRC21:20
openstackgerritKevin Carter proposed openstack/openstack-ansible: Set the storage address for cinder  https://review.openstack.org/28323421:20
*** asettle has joined #openstack-ansible21:23
palendaemrda: The tox stuff's making some more sense now?21:23
mrdamy patch set doesn't fail now :)21:24
palendaeProgress at least!21:26
*** javeriak has quit IRC21:26
mrdaactually I lie, it is failing, but I understand it a little more.  My goal today is to get them all passing in the gate21:27
palendaeA worthy goal!21:27
palendaeI'll probably try to not be on IRC at midnight this evening :p21:27
palendaeBut glad there's progress21:27
mrdaI'm depending on you being there palendae! :-P21:28
* mrda hopes my AU humour isn't taken incorrectly21:28
palendae:p21:28
palendaeIn May I will be working on your timezone at least21:28
mrdaoh good!21:28
sigmavirus24palendae: that's actually happening then?21:29
palendaeOff by an hour21:29
* mrda hopes things are working by then :)21:29
sigmavirus24Congrats!21:29
palendaesigmavirus24: Me going to Japan? Yeah.21:29
sigmavirus24last I had heard it was uncertain21:29
palendaeMay 12 to 2621:29
palendaeAh, yeah21:29
palendaeMostly I was trying to decide on before or after summit21:29
*** kencjohnston has joined #openstack-ansible21:33
*** raddaoui__ has joined #openstack-ansible21:37
*** sdake has quit IRC21:37
*** fawadkhaliq has quit IRC21:39
openstackgerritRobb Romans proposed openstack/openstack-ansible: Flatten deployment host section  https://review.openstack.org/28381421:40
*** raddaoui_ has quit IRC21:41
*** raddaoui has quit IRC21:41
*** raddaoui has joined #openstack-ansible21:42
*** raddaoui_ has joined #openstack-ansible21:42
*** jthorne_ has joined #openstack-ansible21:42
*** jthorne has quit IRC21:42
*** raddaoui__ has quit IRC21:43
*** lane_kong has joined #openstack-ansible21:44
*** jthorne_ has quit IRC21:47
*** johnmilton has quit IRC21:47
*** jthorne has joined #openstack-ansible21:47
*** retreved has quit IRC21:54
openstackgerritNolan Brubaker proposed openstack/openstack-ansible: Add Kilo to Liberty upgrade scaffold  https://review.openstack.org/28382321:56
stevelleflwang: I hope you noticed I added you as a reviewer on https://review.openstack.org/#/c/280770/22:04
flwangstevelle: yep, i saw that22:06
flwangstevelle: and i'm going to comment it based on my above questions22:06
stevelleI suppose I could add a little more detail on copying the playbook over manually, and likely some of the other steps22:06
stevelleperfect22:07
stevellethanks for that22:07
flwangstevelle: it would be nice22:07
*** pellaeon has quit IRC22:07
flwangstevelle: i would like to know how to setup the test env if i only care about my project22:07
stevelleflwang: how do you mean if you only care about your project.22:09
stevelleI assume you want to test against a keystone + heat + ceilometer environment at least22:10
openstackgerritNolan Brubaker proposed openstack/openstack-ansible: Add Kilo to Liberty upgrade scaffold  https://review.openstack.org/28382322:11
*** sigmavirus24 is now known as sigmavirus24_awa22:13
flwangstevelle: for example22:19
flwangstevelle: zaqar only need keystone22:19
flwangstevelle: so in my dev/test, i would like to know, how to build a minimum test env with only keystone + zaqar22:20
flwangjust like devstack22:20
*** JBenson has joined #openstack-ansible22:20
flwangi can config in localrc22:20
stevelleflwang: we don't do that sort of thing typically. That would be a degenerate form of openstack, and because our AIOs use venvs inside containers by default having cinder around doesn't interfere, though it does take longer to build a new stack22:24
flwangstevelle: yep, i see.22:25
stevellebut you can do it, after you run bootstrap-ansible and bootstrap-aio playbooks, go to /etc/openstack_deploy/conf.d/ and remove the files for services you want to omit.22:25
stevellethen you can run scripts/run-playbooks.sh to continue the AIO install22:25
flwangstevelle: so at the init stage, at least i need to run scripts/bootstrap-aio.sh one time, right?22:26
flwangand after that, i can only run my playbook, is it?22:26
stevelleflwang: that sounds right.  By bootstrapping AIO one time, you lay down our configuration for OpenStack22:26
flwangstevelle: like  openstack-ansible os-zaqar-install.yml22:26
stevelleafter that you can just run playbooks22:26
stevelleright22:27
flwangstevelle: cool, i see22:27
flwangstevelle: i will give it a try today and bug you guys later :)22:27
flwangthank you very much22:27
stevelleflwang: just let us know what we can do to help22:30
flwangstevelle: sure, thanks22:30
*** sdake has joined #openstack-ansible22:30
*** neerbeer has joined #openstack-ansible22:35
*** woodard_ has joined #openstack-ansible22:43
*** Mudpuppy has quit IRC22:44
*** spotz is now known as spotz_zzz22:45
*** raddaoui_ has quit IRC22:45
*** raddaoui has quit IRC22:45
*** woodard has quit IRC22:47
*** subscope has quit IRC22:48
*** phiche has quit IRC22:49
*** phiche has joined #openstack-ansible22:49
*** phiche has quit IRC22:50
*** asettle has quit IRC22:57
*** mancdaz has quit IRC22:58
*** persia has quit IRC22:58
*** lkoranda has quit IRC22:58
*** dstanek has quit IRC22:58
*** andymccr has quit IRC22:58
*** leifmadsen has quit IRC22:58
*** klamath has quit IRC22:58
*** mariusv has quit IRC22:58
*** MCoLo has quit IRC22:58
*** john51 has quit IRC22:58
*** timrc has quit IRC22:58
*** gtt116_ has quit IRC22:58
*** eil397 has quit IRC22:58
*** baker has quit IRC22:58
*** pcaruana has quit IRC22:58
*** grumpycatt has quit IRC22:58
*** _hanhart has quit IRC22:58
*** prometheanfire has quit IRC22:58
*** portante has quit IRC22:58
*** rohanp has quit IRC22:58
*** neerbeer has quit IRC22:58
*** flwang has quit IRC22:58
*** weshay has quit IRC22:58
*** mrda has quit IRC22:58
*** lbragstad_ has quit IRC22:58
*** dweaver has quit IRC22:58
*** markvoelker has quit IRC22:58
*** jwagner has quit IRC22:58
*** d34dh0r53 has quit IRC22:58
*** bgmccollum has quit IRC22:58
*** stevelle has quit IRC22:58
*** Guest51435 has quit IRC22:58
*** eglute has quit IRC22:58
*** rackertom has quit IRC22:58
*** darrenc has quit IRC22:58
*** d9k has quit IRC22:58
*** logan- has quit IRC22:58
*** evilrob has quit IRC22:58
*** arif-ali has quit IRC22:58
*** severion has quit IRC22:58
*** izaakk has quit IRC22:58
*** jamielennox has quit IRC22:58
*** finchd has quit IRC22:58
*** daneyon_ has quit IRC22:58
*** kysse_ has quit IRC22:58
*** h1nch has quit IRC22:58
*** errr has quit IRC22:58
*** rETROpunK has quit IRC22:58
*** sigmavirus24_awa has quit IRC22:58
*** mattoliverau has quit IRC22:58
*** GheRivero has quit IRC22:58
*** maximov_ has quit IRC22:58
*** jmccrory has quit IRC22:58
*** dalees has quit IRC22:58
*** jroll has quit IRC22:58
*** Bofu2MBP has quit IRC22:58
*** phalmos has quit IRC22:58
*** itsuugo has quit IRC22:58
*** kysse has quit IRC22:58
*** rromans has quit IRC22:58
*** miguelgrinberg has quit IRC22:58
*** dmsimard has quit IRC22:58
*** richoid has quit IRC22:58
*** bogeyon18 has quit IRC22:58
*** mcarden has quit IRC22:58
*** bryan_att has quit IRC22:58
*** etoews has quit IRC22:58
*** agireud has quit IRC22:58
*** b3rnard0 has quit IRC22:58
*** gus has quit IRC22:58
*** cloudnull has quit IRC22:58
*** palendae has quit IRC22:58
*** andrei_ has quit IRC22:58
*** mfisch has quit IRC22:58
*** galstrom_zzz has quit IRC22:58
*** metral has quit IRC22:58
*** spotz_zzz has quit IRC22:58
*** JBenson has quit IRC22:58
*** admin0 has quit IRC22:58
*** elo has quit IRC22:58
*** mgugino has quit IRC22:58
*** weezS has quit IRC22:58
*** zhangjn has quit IRC22:58
*** toddnni has quit IRC22:58
*** yarkot has quit IRC22:58
*** meteorfox has quit IRC22:58
*** jduhamel has quit IRC22:58
*** xar- has quit IRC22:58
*** antonym has quit IRC22:58
*** coolj has quit IRC22:58
*** woodard_ has quit IRC22:58
*** jthorne has quit IRC22:58
*** KLevenstein has quit IRC22:58
*** mgoddard has quit IRC22:58
*** ShannonM has quit IRC22:58
*** Oku_OS has quit IRC22:58
*** krotscheck has quit IRC22:58
*** loquacities has quit IRC22:58
*** McMurlock has quit IRC22:58
*** mgariepy has quit IRC22:58
*** gfa has quit IRC22:58
*** sshen has quit IRC22:58
*** neillc has quit IRC22:58
*** gmmaha has quit IRC22:58
*** arbrandes has quit IRC22:58
*** hughsaunders has quit IRC22:58
*** admiralboom has quit IRC22:58
*** dolphm has quit IRC22:58
*** nwonknu has quit IRC22:58
*** kmARC has quit IRC22:58
*** jcannava has quit IRC22:58
*** bapalm has quit IRC22:58
*** ggillies has quit IRC22:58
*** Tridde has quit IRC22:58
*** alextricity25_ has quit IRC22:58
*** odyssey4me has quit IRC22:58
*** jasondotstar has quit IRC22:58
*** dolpher has quit IRC22:58
*** lane_kong has quit IRC22:58
*** serverascode has quit IRC22:58
*** mhayden has quit IRC22:58
*** xek has quit IRC22:58
*** e-vad has quit IRC22:58
*** lbragstad has quit IRC22:58
*** charz has quit IRC22:58
*** ravla has quit IRC22:58
*** git-harry has quit IRC22:58
*** ChanServ has quit IRC22:58
*** sdake is now known as jpeeler22:58
*** jpeeler is now known as 64MAAECDI23:00
*** git-harry has joined #openstack-ansible23:00
*** ravla has joined #openstack-ansible23:00
*** charz has joined #openstack-ansible23:00
*** lbragstad has joined #openstack-ansible23:00
*** e-vad has joined #openstack-ansible23:00
*** xek has joined #openstack-ansible23:00
*** mhayden has joined #openstack-ansible23:00
*** serverascode has joined #openstack-ansible23:00
*** dolpher has joined #openstack-ansible23:00
*** jasondotstar has joined #openstack-ansible23:00
*** odyssey4me has joined #openstack-ansible23:00
*** alextricity25_ has joined #openstack-ansible23:00
*** lane_kong has joined #openstack-ansible23:00
*** portante has joined #openstack-ansible23:00
*** prometheanfire has joined #openstack-ansible23:00
*** _hanhart has joined #openstack-ansible23:00
*** grumpycatt has joined #openstack-ansible23:00
*** pcaruana has joined #openstack-ansible23:00
*** baker has joined #openstack-ansible23:00
*** eil397 has joined #openstack-ansible23:00
*** arif-ali has joined #openstack-ansible23:00
*** evilrob has joined #openstack-ansible23:00
*** logan- has joined #openstack-ansible23:00
*** darrenc has joined #openstack-ansible23:00
*** d9k has joined #openstack-ansible23:00
*** rackertom has joined #openstack-ansible23:00
*** eglute has joined #openstack-ansible23:00
*** stevelle has joined #openstack-ansible23:00
*** Guest51435 has joined #openstack-ansible23:00
*** bgmccollum has joined #openstack-ansible23:00
*** d34dh0r53 has joined #openstack-ansible23:00
*** jwagner has joined #openstack-ansible23:00
*** markvoelker has joined #openstack-ansible23:00
*** dweaver has joined #openstack-ansible23:00
*** 32NAAC6RR has joined #openstack-ansible23:00
*** mrda has joined #openstack-ansible23:00
*** weshay has joined #openstack-ansible23:00
*** flwang has joined #openstack-ansible23:00
*** neerbeer has joined #openstack-ansible23:00
*** spotz_zzz has joined #openstack-ansible23:00
*** galstrom_zzz has joined #openstack-ansible23:00
*** metral has joined #openstack-ansible23:00
*** mfisch has joined #openstack-ansible23:00
*** andrei_ has joined #openstack-ansible23:00
*** cloudnull has joined #openstack-ansible23:00
*** gus has joined #openstack-ansible23:00
*** palendae has joined #openstack-ansible23:00
*** b3rnard0 has joined #openstack-ansible23:00
*** agireud has joined #openstack-ansible23:00
*** etoews has joined #openstack-ansible23:00
*** bryan_att has joined #openstack-ansible23:00
*** mcarden has joined #openstack-ansible23:00
*** bogeyon18 has joined #openstack-ansible23:00
*** 64MAAECDI is now known as sdake23:01
*** GheRivero has joined #openstack-ansible23:01
*** severion has joined #openstack-ansible23:01
*** kysse_ has joined #openstack-ansible23:01
*** izaakk has joined #openstack-ansible23:01
*** jamielennox has joined #openstack-ansible23:01
*** finchd has joined #openstack-ansible23:01
*** daneyon_ has joined #openstack-ansible23:01
*** errr has joined #openstack-ansible23:01
*** h1nch has joined #openstack-ansible23:01
*** sigmavirus24_awa has joined #openstack-ansible23:01
*** rETROpunK has joined #openstack-ansible23:01
*** mattoliverau has joined #openstack-ansible23:01
*** maximov_ has joined #openstack-ansible23:01
*** jmccrory has joined #openstack-ansible23:01
*** dalees has joined #openstack-ansible23:01
*** jroll has joined #openstack-ansible23:01
*** mancdaz has joined #openstack-ansible23:01
*** persia has joined #openstack-ansible23:01
*** lkoranda has joined #openstack-ansible23:01
*** andymccr has joined #openstack-ansible23:01
*** dstanek has joined #openstack-ansible23:01
*** leifmadsen has joined #openstack-ansible23:02
*** klamath has joined #openstack-ansible23:02
*** mariusv has joined #openstack-ansible23:02
*** john51 has joined #openstack-ansible23:02
*** MCoLo has joined #openstack-ansible23:02
*** timrc has joined #openstack-ansible23:02
*** gtt116_ has joined #openstack-ansible23:02
*** john51 has quit IRC23:02
*** woodard_ has joined #openstack-ansible23:03
*** jthorne has joined #openstack-ansible23:03
*** KLevenstein has joined #openstack-ansible23:03
*** mgoddard has joined #openstack-ansible23:03
*** ShannonM has joined #openstack-ansible23:03
*** Oku_OS has joined #openstack-ansible23:03
*** krotscheck has joined #openstack-ansible23:03
*** loquacities has joined #openstack-ansible23:03
*** McMurlock has joined #openstack-ansible23:03
*** mgariepy has joined #openstack-ansible23:03
*** gfa has joined #openstack-ansible23:03
*** sshen has joined #openstack-ansible23:03
*** neillc has joined #openstack-ansible23:03
*** gmmaha has joined #openstack-ansible23:03
*** arbrandes has joined #openstack-ansible23:03
*** hughsaunders has joined #openstack-ansible23:03
*** admiralboom has joined #openstack-ansible23:03
*** dolphm has joined #openstack-ansible23:03
*** nwonknu has joined #openstack-ansible23:03
*** kmARC has joined #openstack-ansible23:03
*** jcannava has joined #openstack-ansible23:03
*** bapalm has joined #openstack-ansible23:03
*** ggillies has joined #openstack-ansible23:03
*** Tridde has joined #openstack-ansible23:03
*** zhangjn has joined #openstack-ansible23:03
*** toddnni has joined #openstack-ansible23:03
*** yarkot has joined #openstack-ansible23:03
*** meteorfox has joined #openstack-ansible23:03
*** jduhamel has joined #openstack-ansible23:03
*** xar- has joined #openstack-ansible23:03
*** antonym has joined #openstack-ansible23:03
*** coolj has joined #openstack-ansible23:03
*** rohanp has joined #openstack-ansible23:03
*** john51 has joined #openstack-ansible23:03
*** JBenson has joined #openstack-ansible23:03
*** admin0 has joined #openstack-ansible23:03
*** elo has joined #openstack-ansible23:03
*** mgugino has joined #openstack-ansible23:03
*** weezS has joined #openstack-ansible23:03
*** kysse__ has joined #openstack-ansible23:03
*** john51 has quit IRC23:03
*** rromans_ has joined #openstack-ansible23:03
*** sigmavirus24_awa has quit IRC23:04
*** GheRivero has quit IRC23:04
*** sigmavirus24_awa has joined #openstack-ansible23:05
*** h1nch has quit IRC23:06
*** ChanServ has joined #openstack-ansible23:06
*** asimov.freenode.net sets mode: +o ChanServ23:06
*** h1nch has joined #openstack-ansible23:06
*** sigmavirus24_awa has quit IRC23:06
*** sigmavirus24_awa has joined #openstack-ansible23:06
*** Bofu2MBP has joined #openstack-ansible23:06
*** phalmos has joined #openstack-ansible23:06
*** itsuugo has joined #openstack-ansible23:06
*** kysse has joined #openstack-ansible23:06
*** rromans has joined #openstack-ansible23:06
*** miguelgrinberg has joined #openstack-ansible23:06
*** dmsimard has joined #openstack-ansible23:06
*** richoid has joined #openstack-ansible23:06
*** dmsimard1 has joined #openstack-ansible23:06
*** miguelgrinberg has quit IRC23:07
*** kysse has quit IRC23:07
*** rromans has quit IRC23:07
*** dmsimard has quit IRC23:07
*** dmsimard1 is now known as dmsimard23:07
*** john51 has joined #openstack-ansible23:07
*** kencjohnston has quit IRC23:07
*** miguelgrinberg has joined #openstack-ansible23:08
*** baker has left #openstack-ansible23:09
*** klamath has quit IRC23:09
*** phalmos has quit IRC23:12
openstackgerritMerged openstack/openstack-ansible: Check local and upstream repo for pip before using pypi  https://review.openstack.org/27790523:12
*** darrenc is now known as darrenc_afk23:13
*** KLevenstein has quit IRC23:21
*** retreved has joined #openstack-ansible23:25
*** retreved has quit IRC23:27
*** rohanp_ has joined #openstack-ansible23:27
*** weezS has quit IRC23:28
*** GheRivero has joined #openstack-ansible23:31
*** john51_ has joined #openstack-ansible23:37
*** john51 has quit IRC23:41
*** ShannonM has quit IRC23:48
*** gmmaha has quit IRC23:57

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