Friday, 2015-05-29

*** markvoelker has quit IRC00:12
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Add Sphinx machinery and initial docs.  https://review.openstack.org/18368700:31
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Add Sphinx machinery and initial docs.  https://review.openstack.org/18368700:33
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Add an extension section to the developer docs.  https://review.openstack.org/18385700:35
*** sdake_ has quit IRC00:38
*** sdake has joined #openstack-ansible00:38
*** sigmavirus24 is now known as sigmavirus24_awa00:41
*** jimi|ansible has joined #openstack-ansible00:45
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Add an extension section to the developer docs.  https://review.openstack.org/18385700:46
*** sdake_ has joined #openstack-ansible00:52
*** sdake has quit IRC00:57
*** markvoelker has joined #openstack-ansible01:13
*** sdake_ has quit IRC01:17
*** markvoelker has quit IRC01:18
*** sdake has joined #openstack-ansible01:18
*** dkalleg has quit IRC01:21
*** hoppers99 has left #openstack-ansible02:01
*** javeriak has quit IRC02:05
*** dkalleg has joined #openstack-ansible02:22
*** dkalleg has quit IRC02:26
*** sdake_ has joined #openstack-ansible02:40
*** sdake has quit IRC02:43
*** sdake has joined #openstack-ansible02:43
*** sdake_ has quit IRC02:47
*** galstrom_zzz is now known as galstrom02:57
*** markvoelker has joined #openstack-ansible03:02
*** markvoelker has quit IRC03:06
*** fawadkhaliq has joined #openstack-ansible03:07
*** markvoelker has joined #openstack-ansible04:02
*** markvoelker has quit IRC04:07
*** galstrom is now known as galstrom_zzz04:24
*** sdake_ has joined #openstack-ansible04:29
*** appprod0 has joined #openstack-ansible04:30
*** appprod0 has quit IRC04:31
*** sdake has quit IRC04:33
*** JRobinson__ is now known as JRobinson__afk05:14
*** JRobinson__afk is now known as JRobinson__05:42
*** sdake has joined #openstack-ansible05:46
*** sdake_ has quit IRC05:50
*** markvoelker has joined #openstack-ansible05:52
*** markvoelker has quit IRC05:56
*** radek__ has joined #openstack-ansible06:10
*** javeriak has joined #openstack-ansible06:14
*** JRobinson__ has quit IRC07:34
*** markvoelker has joined #openstack-ansible07:40
*** igorr1 has joined #openstack-ansible07:42
*** markvoelker has quit IRC07:45
*** sdake_ has joined #openstack-ansible07:55
*** stevemar has quit IRC07:55
*** javeriak has quit IRC07:58
*** sdake has quit IRC07:59
*** sdake_ has quit IRC08:17
odyssey4memorning all08:27
*** igorr1 has quit IRC08:30
svgmorning ^_^08:30
evrardjpmorning08:33
*** fawadkhaliq has quit IRC08:36
matttmorning odyssey4me, svg, evrardjp08:39
svghi mattt08:43
odyssey4meo/08:44
odyssey4mesvg you're from Belguim right?08:57
odyssey4me*Belgium (sorry)08:57
svgyes08:57
odyssey4meevrardjp where are you from?08:59
odyssey4me(if you don't mind my asking?)08:59
evrardjpfrom or in?09:00
evrardjpin -> hell, atm09:00
evrardjpcinder causing me pain09:00
mattthaha09:00
evrardjpEurope otherwise09:01
evrardjpwhy ?09:01
evrardjpwhy?*09:01
odyssey4mehaha, just curious09:01
odyssey4meyou're clearly in a similar time zone09:01
odyssey4meor you work some quirky hours ;)09:02
evrardjpI do have some quirky hours sometimes... but that's not the point of the conversation, right? ;)09:03
*** igorr1 has joined #openstack-ansible09:05
svgevrardjp: my rabbits seem to alive and well09:09
svgI used the f5 script - from rpc-extras -  to generate lb config, and I notice this generates a lot less than it did in Juno09:16
matttif i cherry-pick a change, is it acceptable for me to +2 it and merge?09:17
svge.g. for nova, I only get the metadata en api_compute definitions, whil in juno there's also the spice console and the ec2 service09:17
svg(wondering if this could cause my compute hosts to be marked down)09:18
*** dkalleg has joined #openstack-ansible09:20
andymccrsvg: that shouldn't be the case - the spice_console thing is a bug, but I thought we had fixed that (the name on the spice_console group changed so it doesn't find any nodes)09:23
andymccri believe ec2 was deprecated from nova, so its not setup in kilo09:24
svgI suspected something like that09:24
*** dkalleg has quit IRC09:24
andymccrcompute itself should get handled by the scheduler so isn't actually load balanced09:25
svgandymccr: looks like that group name was changed in master but not in kilo: https://github.com/rcbops/rpc-extras/blob/kilo/scripts/f5-config.py#L15109:26
andymccrsvg: ahh good catch - i'll fix it up09:27
andymccrthanks!09:27
svgthe funny thing is, I think I used the one from master :-s09:28
andymccrhahaha09:28
andymccrif that didnt work i can take a look and see why09:28
*** markvoelker has joined #openstack-ansible09:29
svghm, it creates a OPENSTACK_POOL_NOVA_SPICE_CONSOLE, but no matching VS09:31
svgah, pool is empty09:32
*** markvoelker has quit IRC09:34
*** fawadkhaliq has joined #openstack-ansible09:49
odyssey4memattt typically a cherry-pick needs 2x+2 from others, much like any other patch09:51
matttyeah i opted against it :)09:55
odyssey4meurgh, it looks like we're getting build failures in master/kilo - possibly a dependency update somewhere09:56
matttmaster also?  hrrrmph.10:04
matttodyssey4me: not understanding this issue10:38
odyssey4memattt yeah, took a peep and didn't see anything obvious - but on a deadline for log processing so it'll have to wait or someone else will need to look into it10:39
mattti'm still digging10:39
odyssey4mesweet, thanks10:39
*** fawadkhaliq has quit IRC10:42
*** markvoelker has joined #openstack-ansible11:18
*** markvoelker has quit IRC11:22
*** fawadkhaliq has joined #openstack-ansible11:43
*** fawadkhaliq has quit IRC11:48
matttok the repo issue may be due to python-qpid-proton11:50
*** markvoelker has joined #openstack-ansible11:59
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated repo server deps  https://review.openstack.org/18674012:21
*** sigmavirus24_awa is now known as sigmavirus2413:01
matttcloudnull: question13:02
cloudnullyes?13:02
matttcloudnull: why do we build requirements and branches/releases in two steps in our playbooks?13:03
cloudnullyou mean https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/repo-build.yml#L38 and https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/repo-build.yml#L58 ?13:04
matttcloudnull: correct, i see there arent' two steps in https://github.com/cloudnull/yaprt/blob/master/EXAMPLE-SCRIPTS/openstack-repo-build.sh13:04
matttwas wondering if it was a timing thing or something?13:04
cloudnullno.13:04
cloudnullthe first one resolves all deps and uses a graph to determine in deps can or should be built as they're stated.13:05
cloudnullthe second builds all of the git repos that have a setup.py13:05
cloudnullwith no deps13:05
cloudnullbecause they've already been resolved.13:05
cloudnullessentially one is an online build using pip and the other is using bdist_wheel13:06
cloudnullfrom within the contex of the stored git repo.13:06
mattthmm, ok13:07
mattti don't know enough about pip to actually understand your answer13:07
* mattt reads13:08
mattthehe13:08
cloudnullso the first one creates this http://rpc-repo.rackspace.com/os-releases/master/build_reqs.txt13:08
cloudnulland then builds everything as a wheel.13:09
cloudnullthen the second one uses the git repo to build the individual clients and services13:09
cloudnullwhile we reference upstream global requirements and pull that into our process we also query all of the projects we support to make sure that the global requirements is correct and that the projects are compatible with it.13:11
matttthat's awesome cloudnull, yaprt looks like a pretty cool tool13:12
cloudnulland then build a for real global requirements based on all of the projects checked out sha|branch|tag13:12
cloudnullits getting there.13:12
* cloudnull brb13:14
*** fawadkhaliq has joined #openstack-ansible13:14
*** fawadkhaliq has quit IRC13:19
*** KLevenstein has joined #openstack-ansible13:21
*** subscope has quit IRC13:35
*** jimi|ansible has quit IRC13:45
*** galstrom_zzz is now known as galstrom13:49
*** subscope has joined #openstack-ansible13:52
*** fawadkhaliq has joined #openstack-ansible13:57
*** Mudpuppy has joined #openstack-ansible13:59
*** Mudpuppy has quit IRC13:59
*** Mudpuppy has joined #openstack-ansible14:00
*** sigmavirus24 is now known as sigmavirus24_awa14:06
matttzuul isn't looking happy14:15
*** subscope has quit IRC14:15
odyssey4memattt yep, in #openstack-infra they seem to be discussing an issue across both providers14:21
*** galstrom is now known as galstrom_zzz14:24
*** galstrom_zzz is now known as galstrom14:25
*** sigmavirus24_awa is now known as sigmavirus2414:25
*** galstrom is now known as galstrom_zzz14:28
*** galstrom_zzz is now known as galstrom14:30
*** subscope has joined #openstack-ansible14:31
*** stevemar has joined #openstack-ansible14:39
*** jimi|ansible has joined #openstack-ansible14:40
*** jimi|ansible has quit IRC14:45
*** sdake has joined #openstack-ansible14:46
*** galstrom is now known as galstrom_zzz15:07
*** alextricity has joined #openstack-ansible15:10
*** sdake_ has joined #openstack-ansible15:26
*** sdake has quit IRC15:30
*** fawadkhaliq has quit IRC15:30
*** subscope has quit IRC15:35
*** jimi|ansible has joined #openstack-ansible15:37
*** daneyon has joined #openstack-ansible15:50
*** daneyon_ has joined #openstack-ansible15:53
*** jwagner_away is now known as jwagner15:54
*** daneyon has quit IRC15:55
svgafaics, the run-upgrade.sh script does not touch the providers_network in openstack_user_config.yml, whilst there is a difference between the juno and kilo version16:09
svgin particular, the net_name: "flat" was updated (originally net_name: "vlan")16:10
svgnoticed, as the neutron agents on the compute hosts (at least) fail to start because of an overlapping mapping (vlan and flat)16:13
svgneutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent Parsing physical_interface_mappings failed: Key vlan in mapping not unique.16:13
cloudnullsvg:  those entries havent changed the examples have been updated with a few more syntatic bits but if it worked in juno itll work in kilo. That said, the mapping issue was a problem in juno too however juno neutron didnt complain about it where in kilo it does .16:13
cloudnullthe neutron ml2 driver wont allow for overllapping networks mapped to different network types.16:14
cloudnullwhich is why we created the overrides in the provider networks and created an example of veth pairs off a single device to show how it could be done.16:15
cloudnullApsu:  worked on that16:15
Sam-I-Amyou can still do flat and vlan on the same interface, no?16:16
* Apsu nods16:16
Sam-I-Amjust not more than one of those16:16
ApsuSam-I-Am: Yes. Just takes a little workaround16:16
ApsuEssentially the answer is actually "no".16:16
ApsuYou can't tell Neutron to do two mappings to the same interface.16:16
Sam-I-Amor... you can't have one network name mapped to multiple interfaces16:16
ApsuBut you can make a veth pair leg off of a bridge and map to the other end of the veth16:17
svgafaics I ned to update the net_name for tha flat one, from vlan to flat16:17
ApsuSo Neutron thinks it's different16:17
cloudnull^ that16:17
Sam-I-Amyou'd think it would just map 1 flat and 1 vlan to the same interface, since flat is more or less the untagged vlan... but neutron.16:17
*** sigmavirus24 is now known as sigmavirus24_awa16:18
ApsuSam-I-Am: Yep, it's too dumb for that at present.16:18
svgalso, container_type: "veth", seems to be a new parameter?16:19
Sam-I-AmApsu: patches welcome16:21
*** igorr1 has quit IRC16:22
*** sigmavirus24_awa is now known as sigmavirus2416:28
cloudnullsvg the default is veth but you can now hand other network types to a container, ie macvlan, vlan, host, etc.16:31
odyssey4memy brain is fried - a time out is overdue16:41
cloudnulltake it easy odyssey4me16:42
cloudnulland a beer16:42
*** sigmavirus24 is now known as sigmavirus24_awa16:43
*** javeriak has joined #openstack-ansible16:54
*** galstrom_zzz is now known as galstrom16:56
*** fawadkhaliq has joined #openstack-ansible16:59
*** KLevenstein has quit IRC17:00
*** daneyon_ has quit IRC17:05
*** sdake has joined #openstack-ansible17:09
*** jimi|ansible has quit IRC17:11
*** sdake_ has quit IRC17:12
*** sdake_ has joined #openstack-ansible17:20
*** sdake has quit IRC17:23
*** sdake has joined #openstack-ansible17:26
*** dkalleg has joined #openstack-ansible17:26
*** sigmavirus24_awa is now known as sigmavirus2417:26
*** sdake_ has quit IRC17:29
*** KLevenstein has joined #openstack-ansible17:35
openstackgerritMerged stackforge/os-ansible-deployment: Handle proxies through environment variables  https://review.openstack.org/18160317:49
openstackgerritMerged stackforge/os-ansible-deployment: Allow configuration of Nova SQLAlchemy options  https://review.openstack.org/18658317:50
openstackgerritMerged stackforge/os-ansible-deployment: Set Rabbit recovery method for network partitions  https://review.openstack.org/18624317:50
*** galstrom is now known as galstrom_zzz17:54
openstackgerritMerged stackforge/os-ansible-deployment: Perform sort when creating hostnames_ip file  https://review.openstack.org/18659117:55
*** sdake_ has joined #openstack-ansible18:07
svg+2 for handling proxies18:10
*** sdake has quit IRC18:12
sigmavirus24svg: I'm sorry18:22
sigmavirus24We had to revert that because you +2'd it ;)18:22
* svg slaps sigmavirus24 with a large trout18:22
sigmavirus24(svg, now that you're going to be a core, I have to give you a good ribbing)18:22
sigmavirus24WELCOME TO THE TEAM18:23
svgWell, that was not decided yet :)18:23
sigmavirus24I've seen no objections18:23
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Handle proxies through environment variables  https://review.openstack.org/18686818:23
svgI don't see any either :)18:36
*** KLevenstein__ has joined #openstack-ansible18:40
*** galstrom_zzz is now known as galstrom18:41
*** KLevenstein has quit IRC18:42
*** KLevenstein__ is now known as KLevenstein18:42
sigmavirus24http://lists.openstack.org/pipermail/openstack-dev/2015-May/065144.html18:44
cloudnullsigmavirus24: yup, thats ok with us now, IMO. we've been tracking the stable/* branches for some time so sticking to tags is not going to be something effects us.18:53
sigmavirus24cloudnull: I know :D18:53
sigmavirus24I'm just happy to see it is being abandoned18:53
cloudnullbut debian, ubuntu, and rdo are fucked.18:53
sigmavirus24cloudnull: Like I said, I'm happy to see it18:53
sigmavirus24;)18:53
cloudnullthe last message in that thread is an rdo guy complaining how his life is about to get hard.18:54
cloudnullso im with you18:54
cloudnull:)18:54
cloudnulllooks like you won the packaging argument war after all sigmavirus2418:54
*** KLevenstein has quit IRC19:15
*** KLevenstein has joined #openstack-ansible19:15
svghmz, so now I have19:32
svg/etc/neutron/plugins/ml2/ml2_conf.ini:physical_interface_mappings = flat:br-vlan,vlan:br-vlan19:32
svgbut it still complains about vlan not being unique19:32
svg2015-05-29 21:32:32.855 33134 ERROR neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [-] Parsing physical_interface_mappings failed: Value br-vlan in mapping: 'vlan:br-vlan' not unique. Agent terminated!19:32
svgargh tha valu emust be unique19:33
svgI actually don;t use flat networks so let's just get rid of that19:33
sigmavirus24svg: good idea :D19:37
svgcoz what else could I do on a Friday night?19:37
sigmavirus24svg: uhm, enjoy liquids?19:37
* svg does that, too19:37
svgnow you mention it, I need a refill19:38
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add PLUMgrid Neutron Plugin to neutron playbooks  https://review.openstack.org/18472619:41
cloudnullsvg: https://www.youtube.com/watch?v=m1vRvW3QUys19:41
sigmavirus24svg: enjoy!19:41
svgthans guys19:42
svgbtw, cloudnull : is there a reason the -dev and -operators list not having an [osad] topic?19:42
javeriakhey guys, i was hoping to get some feedback on my BP: https://review.openstack.org/#/c/184726/6/specs/kilo/add-plumgrid-neutron-plugin.rst, was hoping to target this for 10.1.719:42
javeriakshould i wait for a group meeting?19:43
*** sdake_ is now known as sdake19:43
cloudnullsvg: we could add one. but i failed to add it to the subject line .19:43
cloudnulljaveriak: i will give it a review.19:43
svgI don;t have the impression there is lots of discussion per mail for now?19:43
cloudnullthere is not.19:43
cloudnullalmost everything is here on IRC19:43
svgjaveriak: kilo != 10.x19:43
svgwhwich works as the group is small I guess19:44
cloudnullit is , likely we'll be going to the ml as we grow.19:44
javeriaksvg: yes, BP targets both juno and kilo, was going to implement juno first19:44
svgperhaps I'm missing what19:45
javeriakWe have some customers still using the Juno train for Rackspace deployment19:45
svgperhaps I'm missing what 'BP' means?19:45
javeriaksvg: sorry BP: blue print, thought that was like a community accepted acronym :)19:45
cloudnullsvg: Blue Print19:45
*** sdake_ has joined #openstack-ansible19:46
svgprobably, but i consider myyself still new :)19:46
svgso that's on me19:46
* svg should file a bug to get reruns from unchanged config all green19:47
javeriaksvg: no worries :), maybe we should take them out from geek lore and publish these :)19:48
*** sdake has quit IRC19:49
*** sdake has joined #openstack-ansible19:49
sigmavirus24cloudnull: were you at the requirements handling session?19:50
cloudnullno19:50
cloudnullanything to write home about ?19:50
sigmavirus24https://review.openstack.org/#/c/186635/19:51
sigmavirus24I think it'll make our lives easier?19:51
sigmavirus24easier to read: http://docs-draft.openstack.org/35/186635/3/check/gate-openstack-specs-docs/84eb447//doc/build/html/specs/requirements-management.html19:52
*** sdake_ has quit IRC19:53
*** KLevenstein has quit IRC19:57
*** openstack has joined #openstack-ansible20:06
sigmavirus24I think g-r will continue to operate as it is now20:11
sigmavirus24and test-requirements will be g-r pinned + test requirements pinned20:11
sigmavirus24I'm guessing20:12
sigmavirus24I haven't finished reading the spec20:12
*** jmccrory has joined #openstack-ansible20:19
svgdoes this ring some bells? https://dl.dropboxusercontent.com/u/13986042/20150529222214.png20:23
*** sigmavirus24 is now known as sigmavirus24_awa20:23
*** openstack has joined #openstack-ansible20:31
svgI suspected that :)20:32
svgthe other one is mentioning the agent is out of sync20:32
svgthis is from the neutron bridge agent on the compute hosts20:33
ApsuLooks like that's right after an agent restart20:33
svgok20:33
svgthat service was crashing constantl bc of the mapping error I mentioned previously20:33
svgso now that is solved20:33
* Apsu nods20:33
svgbut my compute hosts still remain in a down state, so that was not ythe problem cuasin git20:34
svgcausing it20:34
ApsuDown as seen from "nova service-list" for nova-compute entries?20:34
svgyes20:34
svgif I disable the service, it gets marked up; when I re-enable the service, it goes down again after a couple of minutes20:35
ApsuCheck your nova-compute logs, but, you might need to restart the nova-conductor along with the nova-compute services20:35
svgcompute logs say nothing except initializing20:36
*** sdake_ has joined #openstack-ansible20:36
openstackgerritMerged stackforge/os-ansible-deployment: Add Sphinx machinery and initial docs.  https://review.openstack.org/18368720:36
ApsuMight need to add verbose = True or debug = True to ferret out what's up, but first step would be to restart the conductor20:36
Apsunova-compute communicates via the conductors, and if you had transient rabbit issues or something got mucked up, conductor failures may cause compute to eventually bail out20:37
*** sdake has quit IRC20:40
svgnothing so far20:40
ApsuIf you've enabled verbose/debug logging and restarted conductor, let us know if it bails again and if there's any logs to look at and whether conductor/compute are still running when the service-list shows "Down".20:42
svghold on, redeploying all of nova with debug true20:44
ApsuAlrighty20:44
svgok, so the compute log basically just starts up and mentions  Libvirt host capabilities20:49
svg| 52 | nova-compute     | dc1-rk2-ch1-bl9                                   | nova     | enabled | down  | 2015-05-29T20:08:37.000000 | -               |20:50
svgand so are all the computes20:50
*** sdake has joined #openstack-ansible20:50
svgAny particular logs I should look at?20:50
ApsuDid you restart the conductor service?20:50
ApsuIt has its own logs too20:50
svgansible restarted all teh nova services when adding the debug20:51
svgconductor seems to be overwhelmed with20:51
svg2015-05-29 22:50:57.902 3656 DEBUG nova.openstack.common.loopingcall [req-a275ac1a-0521-4cc8-a331-4682c9647006 - - - - -] Dynamic looping call <bound method Service.periodic_tasks of <nova.service.Service object at 0x7fa7a1d67f50>> sleeping for 60.00 seconds _inner /usr/local/lib/python2.7/dist-packages/nova/openstack/common/loopingcall.py:13220:51
ApsuAnd you're seeing nothing in nova-compute's log? Is it even running?20:52
Apsupgrep -fa nova-compute20:52
svgyup20:52
svgnothing except it starting up of course20:52
ApsuThat's particularly weird. Is it still running?20:54
*** sdake_ has quit IRC20:54
svgconductor? yes, with a bunch of subprocesses20:55
ApsuNo, compute20:55
Apsupgrep -fa nova-compute20:56
ApsuMy guess is it's dying not long after starting, probably due to a config error, and that's why it's not spitting out a ton of log message20:56
ApsuOr segfaulting early due to some other issue20:57
svgit is running20:57
ApsuHrm....check the nova.conf and make sure it says "debug = True" under [DEFAULT]20:57
svglast log entry sya\\ays20:57
svg2015-05-29 22:47:52.144 22828 INFO nova.compute.resource_tracker [req-8c3fe8e5-b421-4d66-8116-fed4778f2a9d - - - - -] Auditing locally available compute resources for node dc1-rk2-ch1-bl5.cumuli.be20:57
*** Mudpuppy_ has joined #openstack-ansible20:58
svgfull compute log: /var/log/nova/nova-compute.log20:58
svghttp://sprunge.us/WURd20:58
*** Mudpuppy_ has quit IRC20:59
ApsuSo it IS outputting a Ton of debug content. Ok, that's a good sign to start :P20:59
*** openstackgerrit has quit IRC20:59
*** Mudpuppy_ has joined #openstack-ansible20:59
*** openstackgerrit has joined #openstack-ansible20:59
svgah, sorry, I meant, on error relevant logs :)21:00
svgno21:00
Apsusvg: Any new logs after that point?21:00
svgthat was the full file catted21:00
ApsuUnderstood, I'm asking about right this moment, since it's been a few minutes.21:01
svglast entry 2015-05-29 22:47:52.14421:01
ApsuSo nothing new in the log. hrm.21:01
*** Mudpuppy has quit IRC21:01
ApsuI've got to take off for an appointment, but that's strange. Seems like it's not trying to talk to anything... have you made any custom changes to your nova-related user variables or config templates?21:02
ApsuMight be worth doing a git diff against your OSAD configs21:02
svgnot really, except for my ceph patch21:02
*** fawadkhaliq has quit IRC21:05
*** jwagner is now known as jwagner_away21:11
*** sigmavirus24_awa is now known as sigmavirus2421:14
svgApsu: tcpdumping during a nova compute restart shows it connects to rabbitmq21:14
matttsvg: so question21:20
matttactually n/m21:21
svgI was all ears :)21:21
*** sdake is now known as steakache21:23
*** steakache is now known as sdake21:24
*** openstack has joined #openstack-ansible21:33
*** stevemar has quit IRC21:53
*** Mudpuppy_ has quit IRC21:59
*** fawadkhaliq has joined #openstack-ansible22:05
*** fawadkhaliq has quit IRC22:11
*** jmccrory has quit IRC22:20
*** sdake_ has joined #openstack-ansible22:39
*** sdake has quit IRC22:43
*** sdake has joined #openstack-ansible22:49
*** sdake has quit IRC22:49
*** sdake has joined #openstack-ansible22:49
*** sdake_ has quit IRC22:52
*** radek__ has quit IRC22:54
*** fawadkhaliq has joined #openstack-ansible23:52
*** sdake_ has joined #openstack-ansible23:56
*** fawadkhaliq has quit IRC23:56

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