Wednesday, 2015-06-03

*** javeriak has quit IRC00:00
stevelleconfirming nova all the plays passed with the latest patch of that too00:09
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Allow configuration of Keystone SQLAlchemy options  https://review.openstack.org/18778100:12
cloudnullcommit message updated, but the gate was succeeding and had gotten passed the keystone portions.00:12
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Allow configuration of Keystone SQLAlchemy options  https://review.openstack.org/18778100:13
cloudnulld34dh0r53: stevelle: ^00:14
stevellecloudnull: it still says " 3 nova.conf vars:" in the message but really00:16
cloudnulldoes it ?00:17
cloudnull:\00:17
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Allow configuration of Keystone SQLAlchemy options  https://review.openstack.org/18778100:17
stevelle:D00:17
cloudnullim a bad person00:17
cloudnullim also ocd00:18
stevellemy keystone with changeset 4 is passing smoketests, so we're good00:19
d34dh0r53Should I be a bad person and just merge that one?00:25
d34dh0r53apparently we don't have the reviewers tonight00:26
stevelleI am already looking the other way00:26
d34dh0r53lol00:27
d34dh0r53cloudnull: ^^^00:27
*** galstrom_zzz is now known as galstrom00:30
* cloudnull dont have scroll back d34dh0r5300:33
cloudnull:)00:33
d34dh0r53<d34dh0r53>Should I be a bad person and just merge that one?00:33
d34dh0r53[19:26:23]  <d34dh0r53>apparently we don't have the reviewers tonight00:33
d34dh0r53[19:26:52]  <stevelle>I am already looking the other way00:33
d34dh0r53[19:27:05]  <d34dh0r53>lol00:33
d34dh0r53or cloudnull should I be a bad person and just merge that one? :)00:34
*** fawadkhaliq has quit IRC00:48
*** dkalleg has quit IRC01:08
*** dnlmln has joined #openstack-ansible01:10
*** dnlmln has quit IRC01:10
*** mildan has joined #openstack-ansible01:14
*** galstrom is now known as galstrom_zzz01:24
*** bzhou has joined #openstack-ansible01:30
* bzhou hello01:31
openstackgerritMerged stackforge/os-ansible-deployment: Allow configuration of Keystone SQLAlchemy options  https://review.openstack.org/18778101:45
*** dkalleg has joined #openstack-ansible02:09
*** sdake has quit IRC02:11
*** dkalleg has quit IRC02:13
*** fangfenghua has joined #openstack-ansible02:56
*** mildan has quit IRC02:57
*** JRobinson__ is now known as JRobinson__afk03:27
*** JRobinson__afk is now known as JRobinson__03:27
*** markvoelker has quit IRC03:44
*** JRobinson__ is now known as JRobinson__afk03:52
*** JRobinson__afk is now known as JRobinson__04:13
*** markvoelker has joined #openstack-ansible04:45
*** javeriak has joined #openstack-ansible04:47
*** markvoelker has quit IRC04:50
*** stevemar has quit IRC04:58
*** fangfenghua has quit IRC05:03
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment: Modularizing Neutron playbooks  https://review.openstack.org/18466505:11
*** radek_ has joined #openstack-ansible06:07
*** markvoelker has joined #openstack-ansible06:34
*** markvoelker has quit IRC06:38
*** JRobinson__ has quit IRC06:48
*** radek_ has quit IRC07:02
*** radek_ has joined #openstack-ansible07:05
*** radek__ has joined #openstack-ansible07:18
*** radek_ has quit IRC07:20
*** radek_ has joined #openstack-ansible07:35
*** radek__ has quit IRC07:37
evrardjphello everyone07:49
matttevrardjp: howdy07:55
odyssey4memorning!07:55
*** markvoelker has joined #openstack-ansible08:22
vincent_vdkmorning08:23
*** markvoelker has quit IRC08:27
mancdazmorning osad people!08:46
*** bzhou has quit IRC09:01
*** javeriak has quit IRC09:22
*** blallau has joined #openstack-ansible09:26
blallauHi all, I would like to use OSAD to deploy openstack on baremetal. I know it's possible by setting "is_metal: true" flag  in env conf file.09:29
blallaubut what about the network configuration? Are bridges (br-mgmt, br-vxlan, br-vlan, ...) still deployed and needed?09:32
odyssey4meblallau yep, it's expected that the appropriate network configuration is already in place on the hosts.09:37
evrardjpwhat's the advantage of doing so?09:38
blallaubut all these bridges are not needed for a no container deployment, no?09:39
evrardjpthe overhead of containers is (normally) really low...09:39
blallauYes I know that but th09:39
blallaufor security reasons (wrong for my part) we can't use containers09:40
odyssey4meblallau the bridges are used to separate traffic types and for security, they have nothing to do with the containers09:41
blallauin case you have as many interfaces as you need, you don't need these bridges09:41
odyssey4meblallau then just set each bridge on to its own interfaces09:42
matttodyssey4me: the bridges are used for the containers largely no09:42
odyssey4methe bridges are also required for neutron's ability to attach instances to them09:42
odyssey4memattt the containers are attached to the bridges, but they're not solely for containers09:43
mattttrue09:44
blallauyes I kown that but neutron will create is own bridges (br-tun, br-ethX, ...)09:44
odyssey4meto be fair, though, I've never done a bare metal only setup with OSAD09:44
matttodyssey4me: me neither :(09:44
blallauok thanks ;)09:44
matttblallau: honestly the containers should improve security no?09:44
blallauyes09:44
matttwhat is the concern then?09:45
evrardjpyou could still run one container per host if you want to have the same security as bare metal ><09:45
blallaufor deployment simplicity and business09:45
evrardjpI don't think that will improve your security :p09:45
blallaureasons09:45
evrardjp:)09:45
evrardjpdid you also think of maintenance simplicity?09:46
evrardjp(just playing devils' advocate)09:46
blallauI think OSAD was not implemented with bare metal  in minds09:46
blallaubut add it after, for compute and cinder (open_iscsi issue)09:47
matttblallau: i think there is scope to scale services out onto bare metal09:47
matttbut i'm not sure about doubling up all services onto bare metal09:47
blallauso it's strongly base on a container deployment09:47
matttnot sure that has been tested09:47
matttblallau: would be great for you to test this and let us know how you get on :)09:48
blallauok i'll do it, when I have time09:49
blallauI just take a look at https://etherpad.openstack.org/p/osad-discussion09:50
blallauit was written "    - abstract to non-containerized deployments?      - os-a-d can do bare-metal only right now "09:50
blallauI will test it..09:50
blallauLast question: adding a Postgresql deployment option (role) to OSAD is possible?09:55
matttblallau: hmmmm09:59
matttblallau: it's possible, but it's require a fair bit of work and testing09:59
blallauis there a need?09:59
blallaufor postgresql?09:59
matttblallau: to be honest, if we did any work there it would be to remove the galera stuff and allow a deployer to plug into whatever database engine they want10:00
*** vdo has joined #openstack-ansible10:00
matttbut i've not heard of a desire to use postgresql yet, so it's not on our road map as far as i know10:00
blallauthank you :)10:01
matttblallau: you may want to investigate postgresql support upstream openstack, i'm not even sure if that's a first class citizen10:01
blallauwe already use postgresql for our openstack deployment10:02
blallauit works10:02
matttblallau: is it tested upstream tho?10:02
vdohi10:02
matttblallau: i would like to see os-ansible-deployment be more db agnostic though, allowing a deployer to just plug into an existing cluster10:03
matttvdo: hey there10:03
blallauit depends of Openstack component but it is already tested by the gate10:03
matttblallau: oh, that is good10:04
matttblallau: how is your openstack cluster deployed now, and why are you looking to change it?10:04
vdowe created an ansible openstack deployment team on GH, based on packages, distro agnostic https://github.com/openstack-ansible-galaxy10:04
blallauwe actually have our own deployment system but i would to use a CMS10:05
blallaulike ansible10:05
matttvdo: what packages do you use?10:06
vdothe purpose is to have galaxy roles for each OSt component, we are currently adding rh support10:06
vdoubuntu, rdo10:06
matttvdo: cool, will have to have a closer look10:07
vdoit's a WIP, I also had a look at os-ansible-deployment10:08
*** blallau has quit IRC10:09
matttvdo: was this started before os-a-d?10:09
vdoI'm not really sure, the original repos were from @dguerri, I'm just adding rh support10:10
evrardjpvdo: cool an openstack ansible galaxy!10:10
vdobut I'm planning to add heat, cinder and others10:10
*** markvoelker has joined #openstack-ansible10:11
vdothe main idea is to keep them as independent as we can (i.e. no mysql stuff in each node)10:11
evrardjpOSAD should be in the galaxy10:12
vdos/node/role/10:12
mancdazevrardjp there's definitely discussion about that10:12
evrardjpit would bring more visibility10:13
mancdazall of the os roles have been prepared to be galaxy compatible - it would just be a case of separating them out into their own repo for easier management and then pushing them up to galaxy10:13
mancdazrepos10:13
evrardjpyes, that a lot of work10:13
evrardjpbut an easier readability10:13
evrardjpand moreover, I first turned to dguerri roles, because that's what was logical for me at that time10:14
mancdazevrardjp because they were in galaxy?10:14
evrardjpI only turned to OSAD afterwards, because it seemed more supported (disclaimer: it is!)10:14
evrardjpyup10:14
mancdazevrardjp yeah and the community around osad is growing all the time :)10:15
evrardjpmancdaz: hopefully10:15
*** markvoelker has quit IRC10:15
vdoyes but it's pip oriented isn't it10:16
matttvdo: yeah we don't use distro packages10:17
vdowe need distro packages for our QA10:17
matttwhich gives us really cool flexibility, plus it's all vanilla openstack10:17
vdoand OSAD doensn't fit our needs10:17
mancdazvdo fair enough. We used packages in the past and actually found them a hindrance for various reasons10:18
mancdaz(not in osad)10:18
evrardjpmancdaz: could you explain more?10:20
vdomoreover we need to test on ubuntu, rdo, rhosp, etc10:20
matttvdo: yeah sounds like we're after different things, but i'm sure we can still collaborate on our roles10:21
vdoi remember there were some ELK roles in OSAD, why did you changed to rsyslog10:21
vdosure :)10:21
mancdazevrardjp we used to have a chef deployment setup, using distro packages. We supported both ubuntu and rhel, who package the same things differently10:21
mancdazthey add their own little hotfixes in, drop configs in different locations10:22
mancdazsometimes we found packages that just plain broke services10:22
evrardjpok, but that doesn't explain why leaving packages for pip10:22
mancdazwe also had to wait sometimes months for packages to be produced10:22
vdowe can wait.. we are doing iterations on same OS release10:24
vdodid you use ELK? or I was dreaming?10:25
mancdazvdo in kilo the ELK stuff was removed from osad10:29
mancdazit still exists, but is in a rackspace specific repo, since it wasn't considered core openstack10:29
mancdazjuno -> kilo removed all the old rackspace bits and made osad much moire generic10:30
vdoaha10:30
vdowhich repo is it?10:30
mancdazhttps://github.com/rcbops/rpc-extras10:31
vdonice thanks10:31
mancdazall the monitoring, logging and rackspace support related stuff was moved out of osad10:31
*** sdake has joined #openstack-ansible11:02
*** blallau has joined #openstack-ansible11:22
*** markvoelker has joined #openstack-ansible11:42
*** markvoelker has quit IRC11:46
*** markvoelker has joined #openstack-ansible12:01
*** avozza is now known as zz_avozza12:16
*** zz_avozza is now known as avozza12:17
*** KLevenstein has joined #openstack-ansible12:18
cloudnullMorning.12:25
*** avozza has left #openstack-ansible12:25
*** hrvojem has quit IRC12:36
*** hrvojem has joined #openstack-ansible12:50
*** mildan has joined #openstack-ansible12:51
*** mildan has quit IRC12:52
*** mildan has joined #openstack-ansible12:57
*** stevemar has joined #openstack-ansible13:17
cloudnullblallau: was just reading scroll back and you had some questions about running things on baremetal13:30
cloudnullthe one thing that I wanted to touch on is "I kown that but neutron will create is own bridges (br-tun, br-ethX, ...)" this is not true, those bridges would only be created when using OVS which we do not at present.13:31
cloudnullour stack is using the linuxbridge agent13:31
cloudnullso you'd still need to create the br-vlan, br-vxlan bridges on the host13:31
cloudnullas for moving kilo to metal without containers, simply make the change in the environment and you should be good to go. as odyssey4me said the host networking should be done prior to deploying OSAD which is true when using containers and not.13:32
cloudnullevrardjp: to touch on why we left packages, and are building from source. what mancdaz is true that various packagers would take an indeterminate amount of time to apply security/bug fixes to packages while also providing "value add" patching to packages which would inevitably break a deployment as the packagers would forget about their broken patches.13:37
cloudnullwe fought that battle at rax for several years and decided that it was better if we just used the upstream source.13:37
cloudnull I mean all of OpenStack is python so it lends itself nicely to simply using pip.13:37
cloudnullvdo is there a reason that you have use "distro packages for our QA"? wouldn't using the smaller source code locked to a particular version that would only change based on you changing it be better for QA?13:42
cloudnullmore curious that than anything else.13:42
evrardjpcloudnull: I had a small talk with mancdaz that explained that. It was longer than "simply using pip", so I think there is more to say :p13:42
evrardjpbut I get that13:42
cloudnullfor sure, i was late to the convo, was just catching up.13:43
vdocloudnull: we need to test what our customers/users use13:43
evrardjpcloudnull: nothing wrong with that, thanks for the catching up/opinion13:44
cloudnullvdo:  fair enough .13:44
vdopip installations may differ a lot even if you pin an specific version13:45
cloudnullthat could if you pin.13:45
cloudnullwe have a public index and lock on a release13:45
cloudnullhttp://rpc-repo.rackspace.com/os-releases/11.0.1/13:45
evrardjpI think that's what's interesting to build13:45
evrardjpI think that's what should be better documented13:46
vdoso you use pip in production envs?13:46
evrardjpdistro packages/sources are just a tool13:46
cloudnulli think we need public documentation in the repo. :)13:46
evrardjpgetting to results is what matters13:46
cloudnullbut we're working on that13:46
cloudnullvdo: yyes13:46
evrardjpI'd be happy to understand how I could help13:46
evrardjpthis way I may help13:46
cloudnullin master/kilo we're locating the mirror in your deployment, so itll even work in a walled garden13:47
evrardjpI can't ATM13:47
cloudnulli've been courting Sam-I-Am to get started on it. :)13:47
* cloudnull nudges Sam-I-Am13:47
vdowe don't know anyone using pip with midonet for instance13:47
evrardjpI'd be happy to read him13:47
evrardjp:)13:48
evrardjpvdo: if it's documented, that may move oter to doing the same13:48
cloudnulli know auro is using midonet curious if it can be done with pip. idk for sure.13:48
vdowe need to certificate against distros and what is documented in openstack docss13:48
cloudnullvdo: i also dont know if your with auro and already knew that :p13:48
vdonope13:49
cloudnullSam-I-Am: document osad in the openstack docs.13:49
cloudnull:D13:49
evrardjpcloudnull: do you know who wrote the documentation there: http://docs.rackspace.com/rpc/api/v10/bk-rpc-guide/content/networking-create.html13:50
cloudnullvdo it looks like its possible on just an uninformed look at the packages. https://pypi.python.org/pypi/networking-midonet13:50
evrardjpI don't understand why the 8.1 d) was even there :p13:50
cloudnullSam-I-Am: KLevenstein: rromans: and a few others13:51
cloudnullthe plugin itself looks simple enough all you'd need after that would be the installation of the miokura infra.13:51
evrardjpA few of them are connected on this channel, they could even answer me py PM!13:51
evrardjpby*13:51
cloudnullidk where they are at present. but i will bother them some more.13:52
evrardjpno, it's not something urgent... I'm just suprised... What's more useful is documenting the things like the repo-* playbooks13:53
cloudnullvdo:  you should hit up serverascode he's worked with midenet13:53
*** sigmavirus24_awa is now known as sigmavirus2413:54
vdodisclaimer: I work in Midokura13:56
vdoany work on ansible+midonet ?13:56
cloudnullnone yet.13:57
cloudnullwe've done linuxbridge agent, there's been talk of ovs, and plumgrid has a blueprint for integration presently.13:58
*** mildan has quit IRC13:59
*** mildan has joined #openstack-ansible13:59
cloudnullevrardjp: i think the docs team is working on that ,however those will be out in the rax kilo release.13:59
KLevensteinevrardjp: Sam-I-Am is your guy for this particular question, but I believe he’s commuting at the moment.13:59
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment: Implement Ceilometer[WIP]  https://review.openstack.org/17306714:00
cloudnullat present the juno release is tied to our upstream repo, where in master/kilo we decoupled all of that.14:01
KLevensteinevrardjp: feel free to leave a comment on the page14:01
*** triggerz is now known as tobasco14:14
Sam-I-Ammoo.14:25
cloudnullSam-I-Am: typie typie make the docs14:54
cloudnull:)14:54
Sam-I-Amcloudnull: ugh, you're telling me14:55
Sam-I-Amwait, you are14:55
cloudnullhahaha14:57
cloudnullcc evrardjp - Sam-I-Am is the man at fault :)14:57
*** daneyon has joined #openstack-ansible14:57
*** daneyon_ has joined #openstack-ansible15:01
*** galstrom_zzz is now known as galstrom15:02
sigmavirus24no docs? Must be Sam-I-Am's fault15:03
*** daneyon has quit IRC15:04
*** Mudpuppy has joined #openstack-ansible15:07
*** Mudpuppy has quit IRC15:09
*** Mudpuppy has joined #openstack-ansible15:10
Sam-I-Amevrardjp: yes?15:14
cloudnullre: its your fault15:14
cloudnull:p15:14
Sam-I-Amtell me something i dont know15:15
cloudnullSam-I-Am: A female ferret will die if it goes into heat and cannot find a mate. - yw15:17
*** vdo has quit IRC15:18
cloudnullSam-I-Am: here's another one "celery has negative calories. It takes more calories to eat a piece of celery than the celery has in it to begin with." - yw15:20
andymccrthis is why you are PTL cloudnull15:20
cloudnullikr !15:20
cloudnulldropping knowledge15:21
Sam-I-Amcloudnull: this sounds like a good way to exercise15:21
*** Mudpuppy_ has joined #openstack-ansible15:22
prometheanfiretea is calorie negative too iirc15:25
*** Mudpuppy has quit IRC15:25
sigmavirus24cloudnull: celery also helps you drop other things... like tasks15:26
sigmavirus24of course, I'm talking about Python's celery ;)15:26
cloudnulllol15:26
cloudnulltea != coffee15:26
cloudnullprometheanfire: ^15:26
cloudnull=)15:26
prometheanfiretea > coffee15:26
*** Mudpuppy_ has quit IRC15:28
*** Mudpuppy has joined #openstack-ansible15:29
cloudnullas in a > hassle to make because its not coffee :)15:29
*** mildan has quit IRC15:30
prometheanfirecloudnull: you seen my tea maker thing at home?15:30
cloudnulli have15:31
prometheanfirehttp://www.amazon.com/Breville-BTM800XL-One-Touch-Tea-Maker/dp/B003LNOPSG15:31
prometheanfireshould probably use it at work, drink more here15:31
andymccrone touch tea maker haha. like a kettle? :/15:33
prometheanfireone that steeps tea, ya15:34
andymccrwhy america, why.15:34
prometheanfirelazyness15:34
prometheanfirewhat's wrong with it?15:35
andymccryou still have to put the tea bags in the thing, and clean it out just like regular tea. it doesnt really seem to save you a great deal of anything.15:35
prometheanfirebags?15:36
andymccror loose tea whatever you prefer15:36
prometheanfireit's nice for slightly more laze15:36
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Add an extension section to the developer docs.  https://review.openstack.org/18806516:19
*** Mudpuppy has quit IRC16:27
*** galstrom is now known as galstrom_zzz16:32
*** Mudpuppy has joined #openstack-ansible16:32
*** mildan_ has joined #openstack-ansible16:33
*** javeriak has joined #openstack-ansible16:38
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Moved all of group_vars into a variable file  https://review.openstack.org/18807416:42
openstackgerritMerged stackforge/os-ansible-deployment: Add an extension section to the developer docs.  https://review.openstack.org/18806516:46
*** cbaesema has joined #openstack-ansible16:51
*** javeriak_ has joined #openstack-ansible16:55
*** javeriak has quit IRC16:55
*** mildan_ has quit IRC17:25
*** javeriak_ has quit IRC17:26
*** dkalleg has joined #openstack-ansible17:29
*** KLevenstein has quit IRC17:29
*** KLevenstein has joined #openstack-ansible17:47
*** javeriak has joined #openstack-ansible18:04
*** ctgriffiths has quit IRC18:14
*** mildan has joined #openstack-ansible18:21
*** ctgriffiths has joined #openstack-ansible18:27
*** mildan has quit IRC18:39
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814018:51
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814318:54
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814418:54
*** mordred has quit IRC18:55
*** mordred has joined #openstack-ansible18:55
*** Mudpuppy has quit IRC18:59
*** Mudpuppy_ has joined #openstack-ansible18:59
*** Mudpuppy_ is now known as Mudpuppy19:00
*** Mudpuppy_ has joined #openstack-ansible19:06
*** Mudpuppy has quit IRC19:08
*** cbaesema has quit IRC19:11
*** cbaesema has joined #openstack-ansible19:11
*** javeriak has quit IRC19:35
*** javeriak has joined #openstack-ansible19:37
*** javeriak has quit IRC19:52
*** javeriak has joined #openstack-ansible19:53
*** daneyon_ has quit IRC20:08
*** daneyon has joined #openstack-ansible20:08
*** daneyon_ has joined #openstack-ansible20:11
*** daneyon has quit IRC20:14
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Prep for 10.1.7 tag  https://review.openstack.org/18817320:30
*** javeriak_ has joined #openstack-ansible20:34
*** javeriak has quit IRC20:34
*** radek_ has quit IRC20:44
*** stevemar has quit IRC20:51
*** Mudpuppy_ has quit IRC21:02
d34dh0r53Going to merge https://review.openstack.org/#/c/184665/ if no objections21:13
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814021:14
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814321:15
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814421:16
cloudnullsigmavirus24:  for the horizon change in master/kilo can we set the timeout in the default vars instead of having the conditional in the template?21:17
cloudnullthat wouldnt be possible or should be done in Juno, but we've been doc'ing a lot of the options by using what is set in the roles defaults.21:18
sigmavirus24cloudnull: oh sure21:18
* sigmavirus24 was going by the other conditionals that were in there21:19
cloudnullif you can , feel free to tell me to f-off.21:19
cloudnull:)21:19
cloudnullits fine either way21:19
sigmavirus24Nah it's all good21:21
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814021:22
openstackgerritIan Cordasco proposed stackforge/os-ansible-deployment: Allow the Horizon SESSION_TIMEOUT to be configured  https://review.openstack.org/18814321:24
*** KLevenstein has quit IRC22:00
cloudnulltyvm sigmavirus24 !22:01
cloudnullim out. back online later.22:02
openstackgerritMerged stackforge/os-ansible-deployment: Modularizing Neutron playbooks  https://review.openstack.org/18466522:03
sigmavirus24later22:03
cloudnullOoohhh javeriak_ ^22:05
cloudnullLater sigmavirus24 have a good evening / rest of the day22:05
sigmavirus24You too22:06
javeriak_yay! My first contribution to the community22:06
matttjaveriak_: yay!22:07
sigmavirus24Good work javeriak_!22:07
javeriak_thanks guys, you all have been very helpful, may this bring many more :)22:08
*** JRobinson__ has joined #openstack-ansible22:16
*** sigmavirus24 is now known as sigmavirus24_awa22:30
javeriak_if someone's around, question: juno installs ansible 1.6.x and ansible galaxy support for a requirements file only works for 1.8+, am i missing something here or does the ansible version need to be updated on the rackspace juno mirror23:25
*** jvora has joined #openstack-ansible23:32
javeriak_no actually, the support for other remote repositories only comes in ansible1.8+, so i guess the roles we want to pull into juno will have to be on ansible galaxy, no direct gitHub pulls will work23:33
*** sdake has quit IRC23:35
*** vincent_vdk has quit IRC23:51
*** vincent_vdk has joined #openstack-ansible23:52

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