Wednesday, 2015-11-11

*** jimchou has quit IRC00:04
stevelleI'm sure you can cleanly specify the host vars for the shared-infra_hosts, only but I'm not coming up with it00:04
jaybeersstevelle: yeah, I think creating the directory is a better solution than the symlink00:07
jaybeersbut I'm going for the brass ring here :)00:07
jaybeersbut...in the grand scheme of things, not a catastrophe and it is 6:0000:07
stevellefair enough, I'll watch someone else come up with something that isn't ... inelegant. everything I am coming up with is rather ugly00:08
jaybeersalso, Fallout 4 released today00:08
jaybeersso...WTF am I doing here again?  :D00:09
jaybeersthanks for giving it a think, stevelle.  I'll let you know if I hear anything back from odyssey4me_ on the Galera...grouping?  zoning?00:10
stevelleyeah. that is close enough jaybeers00:10
*** jaybeers has quit IRC00:12
*** alkari has quit IRC00:14
*** KLevenstein_ has quit IRC00:20
*** jmckind has joined #openstack-ansible00:22
*** CheKoLyN has quit IRC00:30
*** subscope has quit IRC00:35
*** eil397 has quit IRC01:07
*** abitha has quit IRC01:25
*** eil397 has joined #openstack-ansible01:34
*** woodard has quit IRC01:37
*** harlowja has quit IRC01:38
*** harlowja_ has joined #openstack-ansible01:38
*** eil397 has quit IRC01:43
*** elgertam has joined #openstack-ansible01:57
openstackgerritXiaBing Yao proposed openstack/openstack-ansible: Choose virt type automatically  https://review.openstack.org/24309801:58
*** jmckind has quit IRC02:10
*** gouthamr has joined #openstack-ansible02:44
*** gouthamr has quit IRC02:48
*** rebase has quit IRC02:48
*** BjoernT has quit IRC02:53
*** sacharya has joined #openstack-ansible02:59
*** woodard has joined #openstack-ansible03:09
*** woodard has quit IRC03:13
*** agireud has joined #openstack-ansible03:34
*** tlian has quit IRC03:35
*** fawadkhaliq has joined #openstack-ansible03:39
*** agireud has quit IRC03:39
*** agireud has joined #openstack-ansible03:41
openstackgerritByron McCollum proposed openstack/openstack-ansible: Fix race condition for /openstack directories  https://review.openstack.org/24391603:57
*** fawadkhaliq has quit IRC04:17
*** sdake has joined #openstack-ansible04:47
*** fawadkhaliq has joined #openstack-ansible05:02
*** sdake has quit IRC05:10
*** sdake has joined #openstack-ansible05:15
*** sdake has quit IRC05:24
*** sacharya has quit IRC05:32
*** subscope has joined #openstack-ansible05:45
*** fawadkhaliq has quit IRC06:01
*** fawadkhaliq has joined #openstack-ansible06:02
*** fawadk has joined #openstack-ansible06:03
*** fawadkhaliq has quit IRC06:04
*** subscope has quit IRC06:32
*** phiche has joined #openstack-ansible06:33
*** javeriak has joined #openstack-ansible06:47
*** javeriak has quit IRC06:51
*** javeriak has joined #openstack-ansible06:54
*** sdake has joined #openstack-ansible06:58
*** sdake has quit IRC06:59
*** mss has quit IRC07:05
*** phiche has quit IRC07:15
*** phiche has joined #openstack-ansible07:24
*** jhesketh has quit IRC07:31
*** jhesketh has joined #openstack-ansible07:31
*** logan2 has quit IRC07:40
*** pabelanger has quit IRC07:40
*** logan2 has joined #openstack-ansible07:40
*** pabelanger has joined #openstack-ansible07:41
*** neillc is now known as neillc_away07:49
*** fawadk has quit IRC07:57
*** fawadkhaliq has joined #openstack-ansible07:58
*** javeriak has quit IRC07:59
*** mss has joined #openstack-ansible08:03
*** subscope has joined #openstack-ansible08:07
*** mss has quit IRC08:08
*** fawadkhaliq has quit IRC08:13
*** mpavone has joined #openstack-ansible08:14
*** mpavone has quit IRC08:15
*** egonzalez has joined #openstack-ansible08:22
*** subscope has quit IRC08:52
*** karimb has joined #openstack-ansible08:58
*** subscope has joined #openstack-ansible09:08
*** fawadkhaliq has joined #openstack-ansible09:12
*** egonzalez has quit IRC09:13
*** slotti has joined #openstack-ansible09:15
*** gparaskevas has joined #openstack-ansible09:17
*** karimb has quit IRC09:18
*** fawadkhaliq has quit IRC09:23
*** egonzalez has joined #openstack-ansible09:28
*** javeriak has joined #openstack-ansible09:32
*** odyssey4me_ is now known as odyssey4me09:33
*** javeriak_ has joined #openstack-ansible09:35
*** javeriak has quit IRC09:37
*** mss has joined #openstack-ansible09:43
*** fawadkhaliq has joined #openstack-ansible09:44
*** egonzalez has quit IRC09:46
*** subscope has quit IRC09:46
*** ntt has joined #openstack-ansible09:47
*** mss has quit IRC09:48
*** javeriak_ has quit IRC09:48
*** javeriak has joined #openstack-ansible09:50
*** subscope has joined #openstack-ansible09:58
*** javeriak has quit IRC10:00
*** javeriak has joined #openstack-ansible10:00
*** phiche1 has joined #openstack-ansible10:09
*** phiche has quit IRC10:12
*** javeriak_ has joined #openstack-ansible10:29
*** javeriak has quit IRC10:33
odyssey4mejaybeers stevelle cloudnull FYI the Galera segmentation work was done around six months ago, so the method is a bit dated - but I've put together https://gist.github.com/odyssey4me/548fe9a76a3540125d17 to describe the general mechanism and give a pointer to start with10:34
*** sacharya has joined #openstack-ansible10:35
*** markvoelker has quit IRC10:37
*** sacharya has quit IRC10:40
*** subscope has quit IRC10:53
*** subscope has joined #openstack-ansible10:53
*** karimb has joined #openstack-ansible10:57
*** karimb has quit IRC11:05
*** subscope has quit IRC11:14
*** javeriak has joined #openstack-ansible11:22
*** javeriak_ has quit IRC11:22
*** fawadkhaliq has quit IRC11:26
*** javeriak has quit IRC11:26
*** fawadkhaliq has joined #openstack-ansible11:34
*** javeriak has joined #openstack-ansible11:34
*** fawadkhaliq has quit IRC11:35
*** fawadkhaliq has joined #openstack-ansible11:36
*** karimb has joined #openstack-ansible11:36
*** markvoelker has joined #openstack-ansible11:37
*** markvoelker has quit IRC11:42
*** mss has joined #openstack-ansible11:44
*** mss has quit IRC11:48
*** fawadkhaliq has quit IRC12:02
*** javeriak has quit IRC12:03
*** subscope has joined #openstack-ansible12:04
*** neillc_away is now known as neillc12:05
*** javeriak has joined #openstack-ansible12:07
*** javeriak_ has joined #openstack-ansible12:13
*** javeriak has quit IRC12:16
*** javeriak has joined #openstack-ansible12:22
*** javeriak_ has quit IRC12:24
*** openstackgerrit has quit IRC12:31
*** openstackgerrit has joined #openstack-ansible12:32
*** karimb has quit IRC12:35
*** javeriak_ has joined #openstack-ansible12:45
*** javeriak has quit IRC12:47
gparaskevaswent to download fedora 23 and saw the face of mhayden...wasnt disapointed12:47
gparaskevas:P12:47
gparaskevashttps://getfedora.org/en/cloud/12:47
*** markvoelker has joined #openstack-ansible12:53
*** markvoelker has quit IRC12:58
*** jhesketh has quit IRC12:58
*** fawadkhaliq has joined #openstack-ansible12:59
*** jhesketh has joined #openstack-ansible13:00
*** sacharya has joined #openstack-ansible13:03
*** sacharya has quit IRC13:08
*** javeriak_ has quit IRC13:24
*** javeriak has joined #openstack-ansible13:25
*** tlian has joined #openstack-ansible13:32
*** fawadkhaliq has quit IRC13:32
logan2is it possible to unset something that is set in the default config templates that are deployed using config overrides13:32
*** fawadkhaliq has joined #openstack-ansible13:32
*** KLevenstein has joined #openstack-ansible13:34
*** mss has joined #openstack-ansible13:44
*** mss has quit IRC13:49
cloudnullmorning13:51
cloudnulllogan2: yes, kinda, you can change the value to the default effectively unsettling it however it will not remove the item.13:52
*** subscope has quit IRC13:54
*** markvoelker has joined #openstack-ansible13:54
*** woodard has joined #openstack-ansible13:55
*** woodard has quit IRC13:55
*** woodard has joined #openstack-ansible13:56
*** markvoelker has quit IRC13:58
*** javeriak has quit IRC14:00
*** mgoddard_ has joined #openstack-ansible14:01
*** mgoddard has quit IRC14:05
*** mss has joined #openstack-ansible14:05
logan2gotcha, ok thanks14:06
*** fawadkhaliq has quit IRC14:07
*** agireud has quit IRC14:08
*** git-harry has quit IRC14:08
*** mss has quit IRC14:10
*** subscope has joined #openstack-ansible14:13
*** agireud has joined #openstack-ansible14:15
*** git-harry has joined #openstack-ansible14:15
*** markvoelker has joined #openstack-ansible14:15
*** sdake has joined #openstack-ansible14:24
*** sdake has quit IRC14:30
*** rebase has joined #openstack-ansible14:30
*** egonzalez has joined #openstack-ansible14:34
*** woodard has quit IRC14:36
*** woodard has joined #openstack-ansible14:37
*** woodard has quit IRC14:37
*** woodard has joined #openstack-ansible14:38
*** mss has joined #openstack-ansible14:41
*** mss has quit IRC14:47
*** sdake has joined #openstack-ansible14:50
logan2one more question about config overrides.. is it possible to set overrides for a group of containers. trying to disable all file logging on compute nodes and leave the logging in place on the controller side containers. easy to do if i modify the templates but I was looking at doing all of this with config overrides14:52
*** cloudtrainme has joined #openstack-ansible14:55
*** fawadkhaliq has joined #openstack-ansible15:01
logan2bummer, looks like im going to be modifying templates regardless http://paste.gentoolinux.info/zagawomozi.coffee15:03
*** spotz_zzz is now known as spotz15:05
*** jwagner_away is now known as jwagner15:07
*** mgoddard has joined #openstack-ansible15:11
*** mgoddard_ has quit IRC15:11
*** Mudpuppy has joined #openstack-ansible15:11
*** sdake has quit IRC15:16
*** jimchou has joined #openstack-ansible15:19
cloudnulllogan2:  you can set the overrides within the https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio#L111 which would set specific overrides on given node15:21
cloudnullcontianer_vars set host variables that are local to all items within that host15:22
cloudnullalso i think you can unset that value by leaving it an empty sting15:23
cloudnullhttp://cdn.pasteraw.com/ijstk978v1kopswyc129edc4467pon315:23
logan2ok i will give that a try with the empty string. I am still split on whether I want to use container_vars for anything since it doesn't seem like I can set them on a group of containers, just per-container basis, so a lot of duplicated config and clutter15:27
*** sigmavirus24_awa is now known as sigmavirus2415:27
logan2if I could set container_vars on the nova_compute group or something that would really be helpful. i am skipping container_vars for cinder_backends right now due to that. i have 60 lines or so of backends to configure and it would just be a mess having to duplicate that for every single cinder_volume host15:31
cloudnullyou could add a group_var to https://github.com/openstack/openstack-ansible/tree/master/playbooks/inventory/group_vars which would be a file with the same name as the group15:32
cloudnullwhich would localize that15:32
logan2ok great i will do that15:32
cloudnullbut it would be nice to expose something like that through inv15:32
cloudnullodyssey4me: palendae15:32
logan2thanks for the help15:33
cloudnullyea sorry its not better / more concise15:35
*** rady has joined #openstack-ansible15:38
palendaeSorry, I'm missing something - expose container_vars? or group vars?15:43
*** sdake has joined #openstack-ansible15:50
cloudnullpalendae: more along the lines of adding an interface to add group_vars15:54
*** mss has joined #openstack-ansible15:55
*** k_stev has joined #openstack-ansible15:56
*** phiche1 has quit IRC15:56
*** openstackgerrit has quit IRC16:02
*** openstackgerrit has joined #openstack-ansible16:02
*** gparaskevas has quit IRC16:03
cloudnullright now contianer_vars , should really be renamed to host_vars but if there was a method to add specific group_vars through the use of the openstack_user_config, some group.d/ dir, etc we could enable deployers to make group specific changes without adding a specific group variable file.16:03
cloudnullto the main repo16:04
palendaeHm16:04
palendaeYeah16:04
palendaeThat would work for current inventory, though get hairy if we wanted inventory to come from a different source16:04
*** cloudtrainme has quit IRC16:09
*** alkari has joined #openstack-ansible16:12
*** britthou_ has joined #openstack-ansible16:12
*** subscope has quit IRC16:14
*** subscope has joined #openstack-ansible16:15
*** andyhky` has joined #openstack-ansible16:15
*** kore_ has joined #openstack-ansible16:16
*** subscope has quit IRC16:16
*** spy has joined #openstack-ansible16:16
*** cloudtrainme has joined #openstack-ansible16:16
*** subscope has joined #openstack-ansible16:17
*** andyhky has quit IRC16:17
*** antonym has quit IRC16:17
*** kore has quit IRC16:17
*** britthouser has quit IRC16:17
*** kore_ is now known as kore16:17
*** britthou_ is now known as britthouser16:17
*** britthouser has quit IRC16:18
*** britthouser has joined #openstack-ansible16:18
*** phiche has joined #openstack-ansible16:19
*** javeriak has joined #openstack-ansible16:19
cloudnullmattt:  were you ever able to reproduce the upgrade issues i was mentioning in https://review.openstack.org/#/c/240560/ ?16:19
*** javeriak has quit IRC16:19
*** javeriak has joined #openstack-ansible16:20
cloudnullalso anyone around to do reviews on https://review.openstack.org/#/c/241483/16:20
cloudnullwould be great to get that nailed down as https://review.openstack.org/#/c/243952/ is immanent16:21
*** britthouser has quit IRC16:21
*** britthouser has joined #openstack-ansible16:21
*** britthouser has quit IRC16:21
*** britthouser has joined #openstack-ansible16:22
*** javeriak_ has joined #openstack-ansible16:24
logan2I can't really test the py_pkgs one as I am on kilo.. tried backporting last week and failed16:24
cloudnulli've starred a few items that I'd like to see if cores are available to review https://review.openstack.org/#/q/starredby:cloudnull+status:open,n,z16:24
*** javeriak has quit IRC16:24
cloudnulllogan2: ah...16:24
cloudnullhum.. so i can backport the repo-build process to kilo which would then give you access to the multi-source bits or I can port the code for the py-pkg change to kilo. idk which one would be more acceptable ?16:25
*** sacharya has joined #openstack-ansible16:26
cloudnullandymccr, hughsaunders, odyssey4me, mattt, d34dh0r53, stevelle ?16:27
logan2I patched repo-build a while back without changing py_pkgs and it just broke everything. py_pkgs was stacking repos on top of each other and duping the builds16:27
*** subscope has quit IRC16:27
*** subscope has joined #openstack-ansible16:29
logan2main goal for me is overriding openstack_services.yml repos16:29
matttcloudnull: i did test the upgrade but tbh i didn't hit the issue you mentioned16:29
mattti hit some other issue but once i fixed it the neutron-db-manage ran :)16:30
*** jimchou_ has joined #openstack-ansible16:30
*** subscope has quit IRC16:30
*** sacharya has quit IRC16:31
*** alkari has quit IRC16:31
*** jimchou has quit IRC16:32
*** sacharya has joined #openstack-ansible16:33
*** subscope has joined #openstack-ansible16:33
*** sacharya_ has joined #openstack-ansible16:34
*** _hanhart has joined #openstack-ansible16:36
*** phiche1 has joined #openstack-ansible16:37
*** sacharya has quit IRC16:37
*** phiche has quit IRC16:39
d34dh0r53cloudnull: hmm, not sure16:39
*** _hanhart has quit IRC16:46
KLevensteinis there somewhere that y’all keep an agenda for the weekly community meetings?16:50
*** daneyon has joined #openstack-ansible16:52
cloudnullKLevenstein:  https://wiki.openstack.org/wiki/Meetings/openstack-ansible16:53
KLevensteincloudnull: thanks16:54
cloudnullnp anytime16:54
matttcloudnull: the thing i don't like about https://review.openstack.org/#/c/240560/16:54
*** daneyon__ has quit IRC16:54
matttcloudnull: actually https://review.openstack.org/#/c/241176/, the liberty bp16:55
matttcloudnull: is that i change some default vars and also the dict that the fact returns16:56
matttcloudnull: which kinda sucks since this isn't master :(16:56
matttcloudnull: but i figured the module was kind of a private api, so it hopefully doesn't matter -- however i'd appreciate if anyone comments if they disagree with me :)16:56
*** wtie has quit IRC16:58
openstackgerritKevin Carter proposed openstack/openstack-ansible: Functional backport for the new repo-build process  https://review.openstack.org/24421516:59
*** mgoddard has quit IRC16:59
*** mgoddard_ has joined #openstack-ansible16:59
cloudnulllogan2: https://review.openstack.org/#/c/244215/ not that it'll get merged at this time however that is a backport of the repo-build bits from liberty into kilo17:00
cloudnullI figured I'd do it and see if it gets accepted17:00
cloudnullwith that change we can backport the multi source py-pkg changes into kilo which will enable the use case you were looking for17:01
*** wtie has joined #openstack-ansible17:01
logan2cool I will give it a try17:02
logan2curious if the new build process allows me to use authenticated https git repos too, because yaprt didn't :)17:03
logan2we'll see17:03
*** spy is now known as antonym17:03
cloudnullhum, well it may. its using the git module within ansible now17:04
cloudnullwe're not passing creds into that17:04
cloudnullbut we could17:04
logan2interesting the module supports a key file. i could add the deployment host key to the github repo and do it that way. but it looks like you would just do authenticated https via the url, so maybe no code changes needed to support that17:07
*** slotti has quit IRC17:11
cloudnullthat would be awesome !17:11
*** subscope has quit IRC17:13
palendaeThrowing it out there, but we don't really use ansible-vault right now17:16
palendaeSo that might fit in, too17:16
*** k_stev has quit IRC17:18
*** daneyon_ has joined #openstack-ansible17:19
*** jimchou has joined #openstack-ansible17:21
*** egonzalez has quit IRC17:22
*** daneyon has quit IRC17:22
*** wtie has quit IRC17:23
*** jimchou_ has quit IRC17:23
*** tiagogomes_ has quit IRC17:24
*** jaybeers has joined #openstack-ansible17:30
jaybeersthe node names in openstack_user_config.yml are purely cosmetic, right?  In other words, I can change the names, then remove them from the inventory, re-run the playbooks, and it'll just pick up the new values?  Specifically, our "shared-infra_hosts" entries are all like 'db1', 'db2' and they need to be 'region1-db1' etc. 'cause we're adding the second region :)17:32
*** subscope has joined #openstack-ansible17:33
palendaejaybeers: It'll create completely new containers with those names17:33
cloudnulljaybeers:  if you change them, do so in the inventory and then the user-config17:34
cloudnullso what palendae said doesnt happen17:34
*** cloudtrainme has quit IRC17:34
*** jwagner is now known as jwagner_lunch17:34
jaybeersoh, right on, put the new names in the inventory directly.  of course17:34
palendaeYeah, the inventory.json file is what you'd want to change first to avoid completely new stuff17:35
*** subscope has quit IRC17:35
jaybeerscloudnull: odyssey4me gave me a kickstart in segmenting, so I'm setting that up too :)17:35
cloudnullthen in the user-config file so that on a subsequent run it doesnt thing to build new containers because the old host names are not found :)17:35
*** markvoelker has quit IRC17:35
cloudnulljaybeers:  nice !17:35
jaybeersI can't wait to benchmark the performance difference once we bring in all the DCs and we're saving like 6 transatlantic round trips17:36
*** sdake_ has joined #openstack-ansible17:36
*** cloudtrainme has joined #openstack-ansible17:36
cloudnullyea that'd be an awesome metric to know.17:37
jaybeersyeah, easy to test too...just deploy them all with gmcast.segment=0 and load test, then add all the appropriate values and test again17:37
*** sdake has quit IRC17:38
*** andyhky` is now known as andyhky17:42
*** cloudtrainme has quit IRC17:54
*** sdake_ is now known as sdake18:05
*** harlowja_ has quit IRC18:08
*** eil397 has joined #openstack-ansible18:16
*** eil397 has quit IRC18:16
*** eil397 has joined #openstack-ansible18:17
*** sacharya_ has quit IRC18:18
*** sacharya has joined #openstack-ansible18:22
*** jaypipes has quit IRC18:22
*** abitha has joined #openstack-ansible18:27
*** abitha has quit IRC18:27
*** abitha has joined #openstack-ansible18:28
*** markvoelker has joined #openstack-ansible18:31
*** alkari has joined #openstack-ansible18:36
*** eil397 has quit IRC18:42
*** harlowja has joined #openstack-ansible18:42
*** jaypipes has joined #openstack-ansible18:42
*** woodard_ has joined #openstack-ansible18:42
*** harlowja_ has joined #openstack-ansible18:44
*** harlowja has quit IRC18:44
*** woodard has quit IRC18:45
*** fawadkhaliq has quit IRC18:45
*** Jezogwza has joined #openstack-ansible18:57
*** phiche1 has quit IRC19:07
*** phiche has joined #openstack-ansible19:07
*** tlian has quit IRC19:08
*** rebase has quit IRC19:11
*** sacharya has quit IRC19:20
*** jwagner_lunch is now known as jwagner19:21
*** cloudtrainme has joined #openstack-ansible19:25
*** sdake_ has joined #openstack-ansible19:29
*** sdake has quit IRC19:30
*** abitha has quit IRC19:33
*** sdake has joined #openstack-ansible19:35
*** sdake_ has quit IRC19:35
*** rebase has joined #openstack-ansible19:36
*** sacharya has joined #openstack-ansible19:40
*** sacharya_ has joined #openstack-ansible19:41
*** sacharya has quit IRC19:44
*** tlian has joined #openstack-ansible19:49
*** spotz is now known as spotz_zzz20:00
*** spotz_zzz is now known as spotz20:01
*** Bjoern_ has joined #openstack-ansible20:03
Bjoern_Do we have some ceph documentation anywhere at https://github.com/openstack/openstack-ansible/tree/master/doc/source/install-guide?20:03
*** Bjoern_ is now known as BjoernT20:04
logan2i wasn't able to find anything when i set it up. the only documentation about the ceph settings i found was in user_variables.yml.example20:17
*** jaypipes has quit IRC20:17
palendaeBjoernT: From what I understand, OSA only includes client-side parts for Ceph, not server20:17
logan2right it expects to connect to an existing cluster with pools already built etc20:18
*** woodard_ has quit IRC20:20
*** woodard has joined #openstack-ansible20:21
logan2my deploy is basically porting a manual deployment to osa... so the ceph part was pretty straight forward to configure after seeing the example setup. the only major gotcha is the osa ceph role expects to be able to ssh to your ceph mon server(s) and collect keys from them to import into libvirt. i think long term it would be nice to provide these manually via user_secrets or something20:21
logan2so osa doesn't need to connect to my ceph mons20:21
*** woodard has quit IRC20:21
*** woodard has joined #openstack-ansible20:22
*** woodard_ has joined #openstack-ansible20:23
*** woodard_ has quit IRC20:24
*** woodard has quit IRC20:24
*** woodard has joined #openstack-ansible20:25
*** woodard has quit IRC20:25
*** woodard has joined #openstack-ansible20:26
BjoernTwell I was more asking from a AIO perspective with all the configuration options20:29
palendaeAh, I don't know. Honestly haven't done anything with the Ceph stuff20:33
*** tlian has quit IRC20:37
*** scarlisle has joined #openstack-ansible20:40
cloudnullmattt:  did some work on ceph and i think he did some bits on AIO testing w/ ceph20:41
*** woodard_ has joined #openstack-ansible20:46
*** woodard has quit IRC20:49
*** karimb has joined #openstack-ansible20:55
*** karimb has quit IRC20:55
*** karimb has joined #openstack-ansible20:56
matttBjoernT: not really, since we use upstream roles to deploy ceph itself20:59
matttand there are a boat load of options21:00
matttBjoernT: you did see how to deploy a ceph AIO w/ rpc-openstack right ?21:03
*** sigmavirus24 is now known as sigmavirus24_awa21:03
BjoernTno I'm looking into documentation fragments etc..21:03
matttBjoernT: https://gist.github.com/mattt416/2cacd4fe73ff76beb7e421:04
matttBjoernT: that should get you an AIO w/ 3 mon containers and 3 osd containers, and all the openstack bits plugged in21:05
openstackgerritKevin Carter proposed openstack/openstack-ansible: Functional backport for the new repo-build process  https://review.openstack.org/24421521:09
*** tlian has joined #openstack-ansible21:18
*** sacharya_ has quit IRC21:18
*** alkari has quit IRC21:23
*** sacharya has joined #openstack-ansible21:23
openstackgerritKevin Carter proposed openstack/openstack-ansible: Functional backport for the new repo-build process  https://review.openstack.org/24421521:23
openstackgerritKevin Carter proposed openstack/openstack-ansible: Functional backport for the new repo-build process  https://review.openstack.org/24421521:49
*** subscope has joined #openstack-ansible21:57
*** woodard has joined #openstack-ansible22:02
*** subscope has quit IRC22:02
*** woodard_ has quit IRC22:05
*** phiche has quit IRC22:06
*** woodard has quit IRC22:06
*** sdake has quit IRC22:07
*** javeriak_ has quit IRC22:16
*** Mudpuppy has quit IRC22:21
*** sdake has joined #openstack-ansible22:21
*** BjoernT is now known as Bjoern_zZzZzZzZ22:32
*** sacharya has quit IRC22:39
*** sacharya has joined #openstack-ansible22:40
*** daneyon_ has quit IRC22:47
*** sacharya_ has joined #openstack-ansible22:50
*** jwagner is now known as jwagner_away22:51
*** sacharya has quit IRC22:53
*** KLevenstein has quit IRC23:00
*** Jezogwza has quit IRC23:06
*** sacharya_ has quit IRC23:09
*** rebase has quit IRC23:10
*** sdake has quit IRC23:19
*** sdake has joined #openstack-ansible23:20
*** Bjoern_zZzZzZzZ is now known as BjoernT23:23
*** scarlisle has quit IRC23:25
*** shanecc has joined #openstack-ansible23:27
shanecchey all, anyone seen this error on adding compute/cinder nodes to a kilo env? One or more undefined variables: 'dict object' has no attribute 'nova_pubkey'23:28
shaneccall compute nodes error on that, even ones that were already running in the env23:29
*** jimchou has quit IRC23:37
*** tlian has quit IRC23:37
*** cloudtrainme has quit IRC23:39
*** rebase has joined #openstack-ansible23:39
*** spotz is now known as spotz_zzz23:41
*** sdake_ has joined #openstack-ansible23:41
*** sdake has quit IRC23:43
*** sdake_ has quit IRC23:56

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