Monday, 2019-05-13

*** altlogbot_1 has quit IRC00:50
*** altlogbot_1 has joined #ara00:52
*** altlogbot_1 has quit IRC00:54
*** altlogbot_2 has joined #ara00:54
*** herald85 has joined #ara06:54
*** gvincent has joined #ara07:21
*** herald85 has quit IRC11:07
*** mgariepy has quit IRC12:27
*** mgariepy has joined #ara12:31
*** stdedos has joined #ara12:31
stdedosHello there! Would "ara" be a quick drop-in replacement for archiving runs in "stdout_callback=debug" verbosity?12:40
stdedosI discovered Ara after "fixing" my playbook, so I am more like a tl;dr response from people with experience in debugging playbook12:41
dmsimardstdedos: ara isn't a stdout callback so you could use both stdout_callback=debug and ara if you wanted to, although you may find the debug callback noisy13:44
dmsimardit's pretty "drop-in", but it's no replacement13:47
dmsimardin the sense that you install it, tell ansible to use it and it starts recording things.13:47
*** gvincent has quit IRC13:48
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: Properly (re-)load database and logging settings with dynaconf  https://review.opendev.org/65818413:58
*** ara-slack has joined #ara13:59
*** ChanServ sets mode: +v ara-slack13:59
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: WIP: Add tests for postgresql  https://review.opendev.org/65702314:03
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: WIP: Add tests for postgresql  https://review.opendev.org/65702314:04
*** gvincent has joined #ara14:06
*** e-tienne has joined #ara14:25
stdedosthank you dmsimard. I have added some functionality in the meantime, and I saw "how" it works.14:28
stdedosI think, it is exactly how you framed it: 'it's pretty "drop-in", but it's no replacement'14:29
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: WIP: Add tests for postgresql  https://review.opendev.org/65702314:34
dmsimardnew version of django-cors-headers is a bit more demanding, CI is failing right now :(14:38
dmsimard?: (corsheaders.E013) Origin '127.0.0.1:8000' in CORS_ORIGIN_WHITELIST is missing scheme or netloc14:38
dmsimardI'll send a fix but it's otherwise broken14:38
dmsimardhttps://github.com/ottoyiu/django-cors-headers/blob/master/HISTORY.rst#300-2019-05-1014:39
*** stdedos has quit IRC14:41
dmsimardpeople have already reported it as https://github.com/ottoyiu/django-cors-headers/issues/40314:41
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: Properly (re-)load database and logging settings with dynaconf  https://review.opendev.org/65818415:00
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: WIP: Add tests for postgresql  https://review.opendev.org/65702315:00
openstackgerritDavid Moreau Simard proposed recordsansible/ara feature/1.0: Include the http scheme for CORS_ORIGIN_WHITELIST  https://review.opendev.org/65884215:00
*** med_ has joined #ara17:17
ara-slackabcde0: The ansible testcases we're trying to execute come with this note "v2.0.0.2 is the currently tested Ansible version. Other versions may not work correctly." sure enough when ansible got upgraded to 2.7.2 upon installing ARA, the testcases failed left and right. My understanding is ARA doesn't support ansible version below 2.4. Is there anyway to make ARA work w/o having to update the testcases? Thanks!17:42
apollo13dmsimard: hi there, how is it going?17:43
*** spiette_ has quit IRC18:21
*** spiette has joined #ara18:23
dmsimardapollo13: o/ doing alright but I need a haircut :p18:32
apollo13dmsimard: I can also help with that, but not sure you will like the result18:33
dmsimard@abcde0 2.0 is an ancient version of Ansible and I would highly recommend against using it18:33
dmsimardthere could be unpatched CVEs and things like that18:33
dmsimard2.0 is EOL since 2016: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html18:34
*** gvincent has quit IRC18:35
ara-slackabcde0: @dmsimard yeah, i'm with you but it's a git repo contributed by virtually anyone. we don't really have a say. it's a bummer. i was really hoping we could take advantage of the slick reports ARA offers. :disappointed:18:36
dmsimard@abcde0 maybe there's an equally as ancient version of ara that would work but there be dragons, you're on your own :p18:37
dmsimardapollo13: I'll stick to django then :D18:39
dmsimardwhat's up ?18:39
ara-slackabcde0: @dmsimard argh, not the answer i was hoping for :disappointed: well, but thank you for your help all these time. i'm sure i'll find other opportunities to use ARA18:40
apollo13dmsimard: not much, family & work mostly. Not to much in the mood to code after work and deadlines coming up18:40
apollo13also I already dislike the new redhat logo18:41
apollo13although I do understand their rationale and like the documents they published about why and how18:41
apollo13but if I go to https://www.redhat.com/en my browser hates me and renders an ugly pixely version of the log18:42
apollo13even though it is an svg *mhm*18:42
apollo13I probably need a laptop with more pixels^^18:42
apollo13also downloading rhel 818:42
apollo13what's missing for ara 1.0 release?18:43
dmsimardapollo13: all my swag is legacy with the new logo now :(18:43
apollo13mhm the todos look rather empty https://github.com/ansible-community/ara/projects/1 -- that is great18:44
apollo13btw if one logs from multiple playbook runs to ara, is there any way to differentiate them? like different projects or environments…18:45
dmsimardin 1.0 there are playbook names as well as labels18:45
apollo13ah, issue 1518:46
dmsimardand 2518:46
apollo13yeah that was me fat fingering18:46
apollo13dmsimard: any thoughts on allowing labels in ansible.cfg?18:47
apollo13because I generally distinguish project by git repo and each has their own ansible.cfg18:48
dmsimardhow about an ansible var ?18:48
dmsimardthat's how playbook names are set up currently18:48
dmsimardhttps://github.com/ansible-community/ara/blob/bb4e5040c633d67c9edcf010da589b49e7bb5d3f/ara/plugins/callback/ara_default.py#L183-L18518:49
apollo13oh for consistency that would certainly be nice18:49
dmsimardI'm not convinced about an approach with a module18:50
dmsimardwe can retrieve things from ansible.cfg but a label doesn't feel like config18:50
dmsimardapollo13: regarding release of 1.018:51
apollo13well I'd like to "namespace" certain runs so to say18:51
apollo13if that means I have to put https://ara_server/<namespace>/api as config I'd be fine with that too18:52
dmsimardmain problem is lack of parity between 0.x and 1.018:52
apollo13you are going to hate me, but: ¯\_(ツ)_/¯ :D18:53
apollo13I haven't used 0.x because it didn't do what I needed ;)18:53
dmsimardI don't hate you, <318:53
dmsimardI've been conflicted myself18:54
apollo13but rationally, what do you expect? migration wise?18:54
apollo13or rather what would you like to see18:54
dmsimardpeople actually trying it out ahead of the release and providing feedback would be awesome18:55
dmsimardbut I don't think it's nothing that would be unfixable in a 1.1 or whatever18:56
apollo13well I'd see 1.0 as "you are comfortable with the feature set"18:56
apollo13nothing is set into stone afterwards aside from probably caring about backwards compat18:57
dmsimardright19:00
dmsimardapollo13: replied to your comment about databases19:06
apollo13"I haven't dug thoroughly to figure out why but at least in my testing with postgresql, it would only work if I exported the individual variables in my shell."19:08
apollo13I'll check, because that shouldn't happen19:08
apollo13or rather reading DATABASES via settings.get shouldn't result in a diff19:09
apollo13hrmpf, why does manage.py again miss the executable bit?19:11
dmsimardIt's a symlink ?19:11
dmsimardI forget, need to brb19:11
apollo13no it's not19:12
apollo13ah the reason is we are generating DATABASES19:12
openstackgerritMerged recordsansible/ara feature/1.0: Include the http scheme for CORS_ORIGIN_WHITELIST  https://review.opendev.org/65884219:13
openstackgerritFlorian Apolloner proposed recordsansible/ara feature/1.0: Properly (re-)load database and logging settings with dynaconf  https://review.opendev.org/65818419:20
apollo13dmsimard: ^ apply that, remove your ara settings.yml and let it recreate it19:20
apollo13dmsimard: we did read DATABASE_NAME  but did put the whole DATABASES into settings19:21
apollo13same for LOGGING19:21
apollo13for simplicity I'd go with one logging flag for now19:21
openstackgerritFlorian Apolloner proposed recordsansible/ara feature/1.0: Write only supported configuration params to the settings file.  https://review.opendev.org/65818419:22
openstackgerritFlorian Apolloner proposed recordsansible/ara feature/1.0: Write only supported configuration params to the settings file.  https://review.opendev.org/65818419:23
openstackgerritFlorian Apolloner proposed recordsansible/ara feature/1.0: Updated black dependency.  https://review.opendev.org/65890019:33
openstackgerritFlorian Apolloner proposed recordsansible/ara feature/1.0: Also ignore .venv directories.  https://review.opendev.org/65890219:35
apollo13dmsimard: btw django is going to blackify it's codebase19:37
*** Jmainguy has joined #ara20:45
*** Jmainguy has joined #ara20:49
*** openstackgerrit has quit IRC21:09

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