Monday, 2015-08-10

*** shoutm has quit IRC00:17
*** shoutm has joined #openstack-ansible00:20
*** shoutm has quit IRC00:44
*** shoutm has joined #openstack-ansible01:02
*** shoutm has quit IRC01:16
*** shoutm has joined #openstack-ansible01:19
*** daneyon_ has quit IRC01:24
*** shoutm has quit IRC01:28
*** shoutm has joined #openstack-ansible01:30
*** markvoelker has joined #openstack-ansible01:39
*** markvoelker has quit IRC01:44
*** alejandrito has joined #openstack-ansible02:08
*** Mudpuppy has joined #openstack-ansible02:17
*** alejandrito has quit IRC02:37
*** JRobinson__ is now known as JRobinson__afk03:40
*** markvoelker has joined #openstack-ansible03:40
*** markvoelker has quit IRC03:45
*** JRobinson__afk is now known as JRobinson__04:25
*** sdake has quit IRC05:01
*** Mudpuppy has quit IRC05:18
*** jasondotstar has joined #openstack-ansible05:21
*** jasondotstar has quit IRC05:26
*** markvoelker has joined #openstack-ansible05:41
*** markvoelker has quit IRC05:46
*** Mudpuppy has joined #openstack-ansible05:48
*** Mudpuppy has quit IRC05:53
*** marekd has quit IRC06:09
*** marekd has joined #openstack-ansible06:12
*** odyssey4me has quit IRC06:50
*** odyssey4me has joined #openstack-ansible06:50
*** shoutm has quit IRC07:27
*** shoutm has joined #openstack-ansible07:30
*** markvoelker has joined #openstack-ansible07:42
*** JRobinson__ has quit IRC07:42
*** markvoelker has quit IRC07:46
*** jasondotstar has joined #openstack-ansible07:48
*** jasondotstar has quit IRC07:52
*** vdo_ has joined #openstack-ansible08:03
*** odyssey4me has quit IRC08:26
*** odyssey4me has joined #openstack-ansible08:27
*** shoutm has quit IRC08:34
*** shausy has joined #openstack-ansible08:57
*** shausy has quit IRC09:05
*** shausy has joined #openstack-ansible09:05
*** shoutm has joined #openstack-ansible09:09
*** javeriak has joined #openstack-ansible09:14
*** javeriak has quit IRC09:25
*** javeriak has joined #openstack-ansible09:25
evrardjpgood morning everyone09:25
svgway too early evrardjp09:35
evrardjp;)09:35
svgI'm still post processing my morning coffee09:36
evrardjp:D09:37
evrardjpyou're on holiday, so it's normal ;)09:41
*** odyssey4me has quit IRC09:43
*** markvoelker has joined #openstack-ansible09:43
*** odyssey4me has joined #openstack-ansible09:43
matttsvg: holiday harder09:44
*** markvoelker has quit IRC09:49
*** vdo_ has quit IRC09:50
*** shoutm has quit IRC09:58
javeriakhey guys, if theres anyone not on holiday, ive got some question with a kilo install10:01
javeriak:)10:01
evrardjpI'm not, but I'm not sure I can help10:01
javeriakhmm now worries, lets give it a try, my infra playbook is erroring out on a command from the galera_install.yml playbook, it cant find the /etc/mysql/debian.cnf file,10:02
javeriakthe file however is only installed in a playbook later galera_post_install.yml, so it makes sense the former error out10:03
javeriakis there something im mising out in the workflow here?10:03
*** odyssey4me has quit IRC10:04
*** odyssey4me has joined #openstack-ansible10:04
evrardjpIIRC galera is installed during the setup-infrastructure.yml10:06
*** javeriak has quit IRC10:07
evrardjpwhere does it fail ?10:10
*** javeriak has joined #openstack-ansible10:12
evrardjpafk sorry10:12
javeriakhey, sorry evrardjp, i got dc, the only message i got from you is "IIRC galera is installed during the setup-infrastructure.yml", not sure if u said anything esle10:13
javeriakyes its during the setup-infrastructure.yml galera portion that this hits, seems to be something with the order of things, as in a file is attempted to be used before it is installed10:14
matttjaveriak: well that is a default debian file10:15
matttso it should exist after the mariadb packages getting installed10:15
odyssey4megit-harry for your side project ;) https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration10:18
git-harryodyssey4me: ta10:20
matttjaveriak: just double-checked, the mariadb-galera-server postinst does stuff with debian.cnf, so that file should exist assuming the package is installed10:28
*** jasondotstar has joined #openstack-ansible10:29
javeriakmattt: yes seems like the installation must have failed, let me check it out, wouldn't the playbooks notify of such a failure though?10:34
matttjaveriak: it should have failed the run, as we're not ignoring those errors10:35
*** jaypipes has joined #openstack-ansible10:53
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Replace ADFS example DNS name with something appropriate  https://review.openstack.org/21110210:56
*** fawadkhaliq has joined #openstack-ansible11:11
*** jasondotstar has quit IRC11:18
openstackgerritMerged stackforge/os-ansible-deployment: Keystone Federation Service Provider Configuration  https://review.openstack.org/21062811:21
*** sdake has joined #openstack-ansible11:28
*** jmckind has joined #openstack-ansible11:29
*** markvoelker has joined #openstack-ansible11:29
*** shoutm has joined #openstack-ansible11:30
*** jmckind has quit IRC11:30
*** sdake_ has joined #openstack-ansible11:32
*** jmckind has joined #openstack-ansible11:32
evrardjpodyssey4me: for the tunables, isn't it better to use lineinfile module from ansible, instead of doing such difficult things?11:34
*** markvoelker has quit IRC11:34
evrardjpmoreover, you can use validate to check integrity and you don't have anything fancy to do...11:35
odyssey4meevrardjp the blueprint is an idea, and I tried a method which was abandoned... git-harry has an alternative idea11:35
evrardjpoh11:35
evrardjpI was looking at that11:35
evrardjphttps://review.openstack.org/#/c/168976/1/specs/kilo/tunable-openstack-configuration.rst11:35
*** sdake has quit IRC11:36
evrardjpI thought it could be better to give my opinion, to help things11:36
odyssey4meessentially the hope is that a deployer could easily define any extra options for openstack conf files that they want without having to go through the dev cycle of adding a new variable, putting the template in, test, merge, etc11:36
*** jmckind has quit IRC11:36
odyssey4meevrardjp it wasn't accepted and was abandoned - if you have an alternative idea then you're welcome to figure it out and submit a spec :)11:37
*** jmckind has joined #openstack-ansible11:38
evrardjpcinder_use_custom_file: True and then copy module, voila!11:39
evrardjpyeah not perfect.11:39
odyssey4melol, the idea is to allow the use of one or two extra vars that get added to the appropriate sections and still take advantage of the templating and defaults in place... not wholesale replace the file11:40
evrardjpI know, I was joking ;p11:40
odyssey4meif you're prepping your config files by hand, you're doing it wrong :p11:41
evrardjpthe lineinfile approach is not that bad11:42
evrardjpthat's what I'm using in other playbooks (not related to openstack)11:42
odyssey4meso the trouble is that as we're compiling from source, there is no file there - we have to place it there11:45
odyssey4meso we have to template anyway11:45
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Update the documented ceph user variables  https://review.openstack.org/20913011:47
evrardjpwhat I don't like with lineinfile is: if you are templating and then editing with lineinfile, it gives idempotency issues (lineinfile rewrites the generated file from template, so re-running makes the task "changed")11:48
odyssey4meyup, that's not great11:48
svgAvoid using lineinfile as much as possible11:49
*** sdake has joined #openstack-ansible11:49
odyssey4mesvg shouldn't you be holidaying?11:49
odyssey4me;)11:49
svgI am !11:49
svgeach time I go inside to take a drink I wander past my laptop though :)11:49
svglineinfile is a hack to edit an existing file that is not managed fully by ansible - which by oitself breaks a bit the point of doing CM11:50
*** Mudpuppy has joined #openstack-ansible11:51
*** sdake_ has quit IRC11:52
svghttps://review.openstack.org/#/c/168976/1/specs/kilo/tunable-openstack-configuration.rst sounds nice though11:52
svgthis is a technique lots of projects could benefit from11:53
svgodyssey4me: what exactly was abondoned?11:53
odyssey4mesvg my spec for doing tunable config files11:53
odyssey4mesvg: https://review.openstack.org/#/c/168976/11:54
odyssey4meI haven't had the time to figure out alternative ways of doing somethign which achieves the desired goal11:54
svgah the spec itself; is that a case of ENOTIME?11:55
odyssey4meit may be worth resurrecting it11:55
odyssey4methere were almost no reviews, but that said that was back in the days when spec were a new thing (and they still are)11:55
odyssey4mewe're a bit better now at reviewing specs11:56
*** Mudpuppy has quit IRC11:56
odyssey4mebut yeah, that method wasn't great and I haven't had a time to figure out an alternative method that I think is good11:56
svgWhy wasn't it great?11:57
svgBasically boils down to a technique to finegrained merging of dicts, overriding sub dicts, etc.11:58
svgWhich would be a great feature in ansible11:58
odyssey4meyep, which I thought would be a pretty useful feature to have in our deployments11:58
git-harryhash_behaviour11:58
odyssey4meand yeah, it'd be great to have something similar in ansible - something a little more fine-grained than the global hash merging11:59
svgdefining hash_behavour as an general ansible.cfg is a bad idea imho; that should be a setting that happens wwithin the inventory, per project etc12:00
evrardjp+112:00
svgthat's one of the things that is a second citizin in ansible land, and few are those that use it12:01
evrardjpsvg: with the ansible.cfg file being in the playbooks folder, it overwrites any other ansible.cfg before, so it's like it's using a "per-project" (osad) config12:03
evrardjpit's not perfect, but it's still something12:03
svgwell, yes, as long as ansible.cfg is in $PWD12:03
svgwhich is the technique I use everywhere12:03
svgGuys, I'll let you ponder these things. My pool is calling.12:05
*** markvoelker has joined #openstack-ansible12:08
evrardjp:)12:10
odyssey4meideally I'd like to be selective in a playbook regarding when the hash behavior is applied... so I could turn it on or off for a specified set of variables per play12:13
evrardjpyes, that would be the best12:15
evrardjplike before giving the variables, you can just put a hash_behaviour: merge12:15
odyssey4meor perhaps even as a filter?12:16
evrardjpno the best would be to chose per variable/hash12:16
odyssey4mewith_items: "{{ my_dict | hash_merge }}"12:16
evrardjpdreaming of "{{my_dict | hash_merge(merged_dict) }}" ?12:18
*** javeriak has quit IRC12:18
*** jmckind has quit IRC12:19
evrardjpthere is something like {{ list1 | union(list2) }} already12:19
odyssey4meyep, but as I recall it doesn't do what I was hoping to do12:20
odyssey4meI can't recall exactly why12:20
evrardjpyeah:12:21
evrardjphttps://github.com/ansible/ansible/issues/749512:21
evrardjpunion is a ansible jinja2 filter, it was never meant to work with dictionaries, it works with lists/sets.12:21
odyssey4mehmm, v2 has this: https://github.com/ansible/ansible/pull/753412:24
odyssey4mewell, devel has it - will have to see whether it merged into anything before v212:25
*** tlian has joined #openstack-ansible12:26
*** tlian has quit IRC12:26
*** tlian has joined #openstack-ansible12:32
*** bapalm has joined #openstack-ansible12:36
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Remove hardcoded config drive enforcement  https://review.openstack.org/19540312:45
*** woodard has joined #openstack-ansible12:47
*** woodard has quit IRC12:47
*** javeriak has joined #openstack-ansible12:47
*** woodard has joined #openstack-ansible12:48
*** yaya has joined #openstack-ansible12:56
*** woodard has quit IRC12:58
*** bapalm_ has joined #openstack-ansible12:58
*** bapalm has quit IRC13:02
*** woodard has joined #openstack-ansible13:03
*** yaya has quit IRC13:14
*** prad_ has joined #openstack-ansible13:18
openstackgerritHugh Saunders proposed stackforge/os-ansible-deployment: Add Ceph/RBD support to playbooks  https://review.openstack.org/21115113:23
*** jasondotstar has joined #openstack-ansible13:29
*** jasondotstar has quit IRC13:34
*** prad_ is now known as pradk13:36
*** shoutm has quit IRC13:44
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Remove hardcoded config drive enforcement  https://review.openstack.org/19540313:45
*** richoid has joined #openstack-ansible13:47
*** Mudpuppy has joined #openstack-ansible13:49
*** jasondotstar has joined #openstack-ansible13:49
openstackgerritMatthew Kassawara proposed stackforge/os-ansible-deployment: Reduce neutron configuration  https://review.openstack.org/21117113:58
*** jasondotstar has quit IRC13:59
*** jasondotstar has joined #openstack-ansible14:00
*** KLevenstein has joined #openstack-ansible14:03
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Reduce neutron configuration  https://review.openstack.org/21117114:11
*** yaya has joined #openstack-ansible14:12
svgodyssey4me: evrardjp the merging happens when parsing the inventory, which basically happens at ansible initialisation, so the different 'instance values' are not available any more at run time14:14
odyssey4mesvg yep14:14
odyssey4meit would be nice if they were accessible somehow14:14
*** richoid has quit IRC14:15
odyssey4methen a simple filter or module could be used to specify a hash merge for a specific variable14:15
*** richoid has joined #openstack-ansible14:15
odyssey4memorning palendae14:17
palendaeMonring14:17
odyssey4mewould you mind glancing through https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment,n,z paying special attention to the backports14:18
openstackgerritYoshitaka Tahara proposed stackforge/os-ansible-deployment: Fix Invalid link "deployment-os.html" in  Install Guide  https://review.openstack.org/21118614:18
odyssey4mepalendae andymccr hughsaunders mattt backports for your attention please: https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment,n,z14:23
*** sdake_ has joined #openstack-ansible14:23
Sam-I-Amodyssey4me: was my backport done wrong?14:25
*** sdake has quit IRC14:27
odyssey4meSam-I-Am nope, I just rebased to improve its chances of success14:29
Sam-I-Amok. should i do a rebase normally?14:29
Sam-I-Amwhich i guess would be review -X ## then rebase, fix whatever, then commit?14:29
Sam-I-Amthe docs workflow doesnt include rebasing14:30
odyssey4meSam-I-Am typically before you cherry-pick -x you should pull the latest origin branch14:30
Sam-I-Amok, that works too14:30
odyssey4meif something's committed and the cherry pick is clean, just use the gerrit UI to cherry-pick to the branch and it'll do it on the latest branch anyway14:31
*** sdake has joined #openstack-ansible14:34
Sam-I-Amodyssey4me: i've never done that14:34
*** wmlynch has joined #openstack-ansible14:34
*** yaya has quit IRC14:36
*** javeriak has quit IRC14:36
*** sdake_ has quit IRC14:37
*** spotz_zzz is now known as spotz14:45
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: [WIP] Add swift standalone gate script  https://review.openstack.org/21120914:46
*** yaya has joined #openstack-ansible14:46
evrardjpif I want to edit my cinder quotas, it's best that I create a variable in user_variables as it will be brought to execution with openstack-ansible OR should I edit role default variable (and create another branch...)?14:47
evrardjp(only locally)14:47
palendaeevrardjp: I would say the first14:47
palendaeUsing user_variables or user_extra_variables14:47
palendaeIf you use openstack-ansible, it'll source any user_* files for you14:48
evrardjpI know :)14:48
odyssey4meevrardjp yeah, you should avoid editing anything in-tree14:48
evrardjpthat's what I thought14:49
evrardjpI'll use user_cinder_overrides.yml or something like that14:49
odyssey4meand if the tree doesn't have the right bits in the templates/defaults, then rather submit a review once you have a patch prepped so that we can include it ina future release14:49
palendaeSince I'm kind of on standby today waiting for our QA people, i think I'm gonna take a stab at documenting that way environment, user_config, and dynamic_inventory.py all play together14:49
odyssey4meevrardjp typically we (at this stage) recommend doing all your overrides in user_variables.yml14:50
evrardjpok14:50
palendaeodyssey4me: Oh, I'd recommend not shoving anything in there, personally14:50
palendaeThough I seem to be in the minority14:50
evrardjpthat was kinda a hidden question14:50
evrardjpI'd think like palendae at first14:50
odyssey4mepalendae until we have a better mechanism, that's the process at this stage14:51
evrardjpkeep the user_variables so close to standard as possible14:51
evrardjpand have another user_* something for override14:51
palendaeevrardjp: I know a few cases on our project that wraps OSAD, I had stuff separated into their own files, then later patches put them back in...so /shrug14:51
odyssey4meevrardjp user_variables should not contain anything to start with - so there's no such thing as a 'standard' user_variables14:51
odyssey4mepalendae yeah, it'd be more ideal to be able to put them into conf.d or something like that14:52
odyssey4meperhaps it'd be more ansible-like to use group vars properly though14:52
evrardjpit does: *_ceilometer_enabled: False, ceilometer_db_*14:52
evrardjpssl_*14:52
palendaeodyssey4me: conf.d is for inventory config, nothing to do with Ansible14:53
odyssey4meevrardjp those are some bad habits :/14:53
palendaeWhich is why I intend to write those docs today :p14:53
palendaeconf.d is configuration for our inventory, and it happens to be YAML, but it has little to do with Ansibel vars14:53
odyssey4mepalendae sure, you you could review the backports to kilo first that'd be swell14:53
palendaeExcept when it does14:53
evrardjpI'll not create a new user_* file if this is gonna change in the future, thanks for notifying :)14:53
palendaePlan to14:53
palendaeevrardjp: Any changes in the future are undefined at the moment14:54
palendaeAs far as I know, we don't have an alternative proposed yet14:54
palendaevars.d? :p14:54
odyssey4meevrardjp if it does change then you'll know - but it's not high on the priority list right now14:54
evrardjpthat's also what I thought :)14:54
evrardjpanyway14:54
palendaeodyssey4me: Yeah, going through backports now14:55
*** javeriak has joined #openstack-ansible14:56
odyssey4mepalendae thanks - I'd like to release 11.1.0 and get some sleep tonight :p14:56
palendaeI'd like you to get some sleep too14:56
Sam-I-Ampffft sleep14:57
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Remove hardcoded config drive enforcement  https://review.openstack.org/19540314:57
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Remove hardcoded config drive enforcement  https://review.openstack.org/19540314:57
*** woodard has quit IRC14:59
openstackgerritMerged stackforge/os-ansible-deployment: Wrapper script to perform K2K federated login  https://review.openstack.org/21075114:59
odyssey4methanks palendae15:02
palendaeWelcome15:03
*** Verilium has quit IRC15:04
*** daneyon has joined #openstack-ansible15:05
*** daneyon has quit IRC15:05
odyssey4meFYI - in my testing it appears that https://review.openstack.org/209047 quite solidly resolves a lot of the master-related build failures in the gate15:06
*** daneyon has joined #openstack-ansible15:06
palendaeCool15:06
palendaeSo this is Liberty versions of Keystone only?15:06
odyssey4methe new config resolves import race conditions in Keystone wsgi, and therefore results in a more reliable Keystone service15:06
*** fawadkhaliq has quit IRC15:06
palendaeSeems so, since it's upstream as of Aug15:06
odyssey4mepalendae I suspect that this should be backported15:06
odyssey4methis config should work both ways, and while kilo doesn't require it - it's a better config than we have right now15:07
palendaeGotcha15:07
*** woodard has joined #openstack-ansible15:07
*** jmckind has joined #openstack-ansible15:11
odyssey4meprometheanfire FYI https://review.openstack.org/211209 implements a complete standalone swift gate check build - next step is to get the tempest role to deploy properly on it, and test properly15:11
palendaeodyssey4me: Are you thinking about having that be within the normal gate check, or a separate job?15:18
*** galstrom_zzz is now known as galstrom15:18
odyssey4mepalendae standalone swift?15:18
palendaeyaeh15:18
odyssey4meI'm thinking of having several use-cases checked on each commit. One would be standalone swift.15:18
palendaeRight, I'm asking in terms of how that's actually implemented in gerrit15:19
palendaeOne big job, or several jobs, like linting vs. gate-check-commit15:19
stevellenot qw qn inline check15:19
stevellewow15:19
stevellefingers on wrong keys15:19
odyssey4meIt'll show as another job, so you'd have: gate-osad-lint, gate-osad-commit, gate-osad-swift15:19
*** phalmos has joined #openstack-ansible15:20
palendaeGotcha15:20
odyssey4meand I'd like to add a compute with nfs (not swift) check too15:20
palendaeThat's how I'd like it :)15:20
odyssey4meas compute with nfs is a use-case that covers the usage of things like netapp, but without the netapp15:21
odyssey4mebut before diving into that, I'd like to get a multinode gate check right15:22
palendaeYeah15:23
openstackgerritMerged stackforge/os-ansible-deployment: Adjust key distribution mechanism for Swift  https://review.openstack.org/21063015:25
*** alop has joined #openstack-ansible15:28
*** woodard_ has joined #openstack-ansible15:28
*** woodard__ has joined #openstack-ansible15:30
*** javeriak has quit IRC15:30
*** woodard_ has quit IRC15:30
*** woodard has quit IRC15:32
*** daneyon has quit IRC15:32
*** daneyon has joined #openstack-ansible15:32
*** alop has quit IRC15:37
*** alop has joined #openstack-ansible15:37
*** jmckind has quit IRC15:40
prometheanfireodyssey4me: ah, nice :D15:42
Sam-I-Amso, that means standalone swift is a thing?15:43
prometheanfireSam-I-Am: why not15:43
Sam-I-Amwe dont document it15:43
prometheanfireSam-I-Am: ah, well, don't think we 'support' it officially yet15:44
palendaeSam-I-Am: Not yet, but it's coming15:48
Sam-I-Amosad support, or also rpc?15:49
Sam-I-Amthey're two different beastises15:49
prometheanfireosad15:51
* prometheanfire heard nothing of rpc15:51
prometheanfireI just wanted it to make it easier to test multiregion swift15:51
prometheanfirealso, seemed like a good idea at the time15:51
palendaeSam-I-Am: rpc-openstack will have MaaS monitoring15:52
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Update the documented ceph user variables  https://review.openstack.org/20913015:52
*** woodard__ has quit IRC15:52
Sam-I-Amoutside of gating, i would prefer that official support for swift-only doesnt merge without doc updates15:53
Sam-I-Amparticularly the install guide, but i'm sure theres other stuff15:53
prometheanfireI asked that it was at least made docimpact15:53
*** CheKoLyN has joined #openstack-ansible15:54
openstackgerritMerged stackforge/os-ansible-deployment: Adjust swift_rings.py to work on specified regions  https://review.openstack.org/21063115:55
*** woodard_ has joined #openstack-ansible15:55
openstackgerritMerged stackforge/os-ansible-deployment: Adjust the network rings are syncd on  https://review.openstack.org/21063215:56
*** darrenc has quit IRC15:57
*** darrenc has joined #openstack-ansible15:58
openstackgerritMerged stackforge/os-ansible-deployment: Add md5sum check for swift rings after ring-sync  https://review.openstack.org/21063316:01
*** woodard_ has quit IRC16:04
*** woodard has joined #openstack-ansible16:04
openstackgerritMerged stackforge/os-ansible-deployment: Add swift-sync role and environment  https://review.openstack.org/21063416:09
openstackgerritMerged stackforge/os-ansible-deployment: Add sample Keystone Federation SP configuration for ADFS  https://review.openstack.org/21080416:10
stevelleSam-I-Am: confirming those docs could use freshening but they are not too far off now16:12
Sam-I-Amstevelle: which docs?16:14
stevelleSam-I-Am: swift-only.  catching up from 25 min ago16:14
Sam-I-Amstevelle: i think only rpc has docs for it, maybe just for juno?16:14
stevelleSam-I-Am: I think there was a kilo draft but it was a touch stale.  Might be mistaken.16:15
stevelleand yes rpc but I trust the experts can do a needful16:15
Sam-I-Am'experts'16:20
Sam-I-Amwhere be those16:20
*** javeriak has joined #openstack-ansible16:22
*** shausy has quit IRC16:25
*** yaya has quit IRC16:28
*** yaya has joined #openstack-ansible16:31
*** fawadkhaliq has joined #openstack-ansible16:34
*** bapalm has joined #openstack-ansible16:43
*** metral is now known as metral_zzz16:47
*** metral_zzz is now known as metral16:48
*** fawadkhaliq has quit IRC17:01
*** britthou_ has joined #openstack-ansible17:04
*** sdake_ has joined #openstack-ansible17:04
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Update kilo for new dev work - 10 Aug 2015  https://review.openstack.org/21126517:06
*** britthouser has quit IRC17:07
*** sdake has quit IRC17:07
*** javeriak has quit IRC17:08
*** britthou_ has quit IRC17:10
*** sdake_ is now known as sdake17:14
*** bapalm has quit IRC17:16
*** bapalm has joined #openstack-ansible17:16
*** bapalm has quit IRC17:21
*** yaya has quit IRC17:26
*** javeriak has joined #openstack-ansible17:31
*** sdake_ has joined #openstack-ansible17:32
mgariepyis it possible to create some extra container with specified ips/hostname with osad ?17:33
palendaemgariepy: You can add a container to the environment with http://osad.readthedocs.org/en/latest/extending.html#env-d17:34
*** yaya has joined #openstack-ansible17:35
palendaeThere are some examples here https://github.com/rcbops/rpc-openstack/tree/master/rpcd/etc/openstack_deploy17:35
*** sdake has quit IRC17:35
*** CheKoLyN has quit IRC17:38
*** britthouser has joined #openstack-ansible17:45
mgariepypalendae, and for the ip ? can it be specified ?17:47
palendaemgariepy: You'd have to add an entry in user_config.yml then17:48
palendaeThe environment defines a skeleton, the user config fits hosts into that skeleton17:48
mgariepyok17:48
*** britthouser has quit IRC17:50
*** britthouser has joined #openstack-ansible17:50
stevelledo I recall that we have had some sort of discussion about osad's docs and where docs bugs will live possibly changing?17:50
palendaeOSAD's? For now assign to rpcdocs team17:51
palendaeI think that's right, KLevenstein would have to confirm17:51
palendaeAs in, the Launchpad team17:51
KLevensteinyeah, if there’s an OSAD docs bug, create it and assign it to the rpcdocs team17:51
*** Bjoern_ has joined #openstack-ansible17:52
KLevensteinI’m very unhappy right now with all the different streams for docs bug tracking that exist, but I can’t see a way around it just yet.17:52
KLevensteinbut that being said, if it’s an OSAD docs bug and not an RPC docs bug, it belongs in the OSAD launchpad system, assigned to the rpcdocs group17:53
stevellepretty sure this is going to be an osad docs bug: https://review.openstack.org/#/c/21118617:56
stevellealso, community17:57
Bjoern_Howdy. do you guys know off hand if osad support logo customizations inside horizon ? I can't find any17:59
*** Bjoern_ is now known as BjoernT17:59
stevelleBjoernT: I believe that is possible using CSS overrides, see https://github.com/rcbops/horizon-extensions18:04
BjoernTthat is ostack version agnostic ?18:05
BjoernToh i see multiple branches18:05
stevelleIt should work in kilo+18:06
stevelleI believe juno should still work as well18:06
stevellethe technique for changing horizon templates is the same18:07
*** bapalm has joined #openstack-ansible18:07
*** bapalm has quit IRC18:07
*** bapalm has joined #openstack-ansible18:08
BjoernTand its not colliding with osad18:08
BjoernTa playbook run would not revert css changes?18:08
*** britthou_ has joined #openstack-ansible18:09
*** britthou_ has quit IRC18:12
*** britthouser has quit IRC18:12
stevelleI'm working from fuzzy memory when I answer but I believe the answer is that the base.html file dropped might be overwritten when "Collect and compress static files" runs in the horizon_post_install task. Perhaps miguelgrinberg can remember.18:13
*** rrrobbb has joined #openstack-ansible18:13
miguelgrinbergBjoernT: osad does not have any settings to rebrand horizon18:14
miguelgrinbergyou can do it manually on the horizon container18:15
BjoernTthanks, I kinda expected that already18:15
miguelgrinbergthere is a documented rebranding for horizon (in upstream docs), that's what the horizon-extension plays does18:15
stevellemiguelgrinberg: would the playbooks clobber any rebranding vis css?18:15
*** britthouser has joined #openstack-ansible18:16
miguelgrinbergstevelle: maybe. If the horizon package gets reinstalled, then the graphics will revert back to the upstream versions18:16
stevelleok, so we don't know BjoernT18:16
BjoernTlol, we'll test it18:17
stevelleyes18:17
miguelgrinbergwhat's the question we don't know?18:17
BjoernTif the osad horizion playbooks will remove css changes made by the horizion-extension18:18
miguelgrinberghorizon extensions does not change CSS, it overwrites three image files from the horizon upstream package18:19
miguelgrinbergif you reinstall upstream horizon then you'll lose the customizations18:19
miguelgrinbergrunning the horizon play in osad may or may not screw up the rebranding, depending on whether it reinstalls horizon or not18:20
*** britthouser has quit IRC18:21
stevellemiguelgrinberg: perhaps I'm confused by https://github.com/rcbops/horizon-extensions/blob/master/rackspace/templates/rackspace/base.html18:22
*** toddnni has quit IRC18:23
*** toddnni has joined #openstack-ansible18:23
*** toddnni has quit IRC18:23
miguelgrinbergthat's not the rebranding, that's the solutions tab18:24
miguelgrinbergthat will survive a horizon reinstall18:24
miguelgrinbergthis is a horizon plugin that is installed separately from horizon18:25
miguelgrinbergI thought BjoernT asked specifically about rebranding? Maybe I missunderstood18:26
BjoernTkind, primarily about the logo but i general it goes into rebranding18:27
*** bapalm__ has joined #openstack-ansible18:27
stevelleIt looked to me at a glance that rackspace/static/rackspace/login.css is linked through the base.html and that is where /static/rackspace/img/logo-rackspace-large.png is attached to the wireframe18:27
stevelleoverly simplistic sleuthing maybe18:28
miguelgrinbergno, the logos are images that come with horizon that we overwrite, no css trickery involved18:29
*** toddnni has joined #openstack-ansible18:29
miguelgrinbergstevelle: here: https://github.com/rcbops/rpc-openstack/blob/master/rpcd/playbooks/roles/horizon_extensions/tasks/main.yml#L16-L2618:30
*** bapalm has quit IRC18:30
stevelleok so I would suspect that logo files will get clobbered on upgrade18:31
stevellemaybe more often18:32
*** yaya has quit IRC18:32
*** rromans has quit IRC18:35
*** sdake_ is now known as sdake18:35
*** yaya has joined #openstack-ansible18:40
*** yaya_ has joined #openstack-ansible18:43
*** rrrobbb has quit IRC18:43
*** javeriak_ has joined #openstack-ansible18:43
*** javeriak has quit IRC18:44
*** yaya has quit IRC18:44
*** yaya_ is now known as yaya18:44
*** rrrobbb has joined #openstack-ansible18:47
*** andyhky has quit IRC18:49
*** andyhky has joined #openstack-ansible18:49
*** javeriak has joined #openstack-ansible19:01
*** britthouser has joined #openstack-ansible19:02
*** javeriak_ has quit IRC19:05
*** bapalm_ has quit IRC19:08
*** fawadkhaliq has joined #openstack-ansible19:18
*** britthouser has quit IRC19:26
*** britthouser has joined #openstack-ansible19:26
*** sdake_ has joined #openstack-ansible19:29
*** sdake has quit IRC19:33
*** sdake has joined #openstack-ansible19:35
*** britthouser has quit IRC19:36
*** sdake_ has quit IRC19:38
*** britthouser has joined #openstack-ansible19:40
*** bapalm__ has quit IRC19:44
*** bapalm has joined #openstack-ansible19:45
*** bapalm has quit IRC19:46
*** javeriak has quit IRC19:46
*** bapalm has joined #openstack-ansible19:46
*** yaya has quit IRC19:56
*** yaya has joined #openstack-ansible20:02
*** yaya has quit IRC20:04
*** yaya has joined #openstack-ansible20:08
*** bapalm has quit IRC20:09
*** bapalm has joined #openstack-ansible20:09
*** bapalm has quit IRC20:12
*** bapalm has joined #openstack-ansible20:12
*** rrrobbb has quit IRC20:27
*** fawadkhaliq has quit IRC20:29
*** rrrobbb has joined #openstack-ansible20:31
*** bapalm has quit IRC20:44
*** bapalm has joined #openstack-ansible20:45
*** bapalm_ has joined #openstack-ansible20:46
*** woodard has quit IRC20:47
*** bapalm has quit IRC20:49
*** bapalm_ has quit IRC20:50
*** yaya has quit IRC21:00
*** pradk has quit IRC21:14
*** tlian2 has joined #openstack-ansible21:17
*** CheKoLyN has joined #openstack-ansible21:19
*** tlian has quit IRC21:21
*** Mudpuppy_ has joined #openstack-ansible21:30
*** Mudpuppy has quit IRC21:34
*** Mudpuppy_ has quit IRC21:35
*** cfarquhar has joined #openstack-ansible21:41
*** yaya has joined #openstack-ansible21:43
*** bapalm has joined #openstack-ansible21:56
*** yaya has quit IRC22:00
*** sdake has quit IRC22:01
*** bapalm has quit IRC22:02
*** bapalm has joined #openstack-ansible22:03
*** bapalm has quit IRC22:07
*** bapalm has joined #openstack-ansible22:18
*** rrrobbb has quit IRC22:23
*** rrrobbb has joined #openstack-ansible22:27
*** rrrobbb has quit IRC22:28
*** galstrom is now known as galstrom_zzz22:28
*** rromans has joined #openstack-ansible22:28
*** bapalm has quit IRC22:29
*** spotz is now known as spotz_zzz22:40
*** yaya has joined #openstack-ansible23:00
*** KLevenstein has quit IRC23:06
*** yaya has quit IRC23:07
*** CheKoLyN has quit IRC23:10
*** tlian2 has quit IRC23:13
*** JRobinson__ has joined #openstack-ansible23:18
*** sdake has joined #openstack-ansible23:31
*** jaypipes has quit IRC23:42
*** BjoernT has quit IRC23:43
*** daneyon has quit IRC23:44
*** daneyon has joined #openstack-ansible23:44
*** Mudpuppy has joined #openstack-ansible23:47
*** phalmos has quit IRC23:52
*** sdake has quit IRC23:53
*** sdake has joined #openstack-ansible23:56
*** tlian has joined #openstack-ansible23:57

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