| Time |
Nick |
Message |
| 08:37 |
|
kworstell-isl joined #evergreen |
| 09:01 |
|
dguarrac joined #evergreen |
| 11:00 |
|
jihpringle joined #evergreen |
| 11:03 |
|
Christineb joined #evergreen |
| 11:16 |
|
kworstell_isl joined #evergreen |
| 11:47 |
csharp_ |
@band add Discovery Layer |
| 11:47 |
pinesol |
csharp_: Band 'Discovery Layer' added to list |
| 11:59 |
|
kworstell-isl joined #evergreen |
| 11:59 |
|
kworstell_isl joined #evergreen |
| 12:00 |
|
kworstell_isl_ joined #evergreen |
| 12:10 |
JBoyer |
Don't forget their thrash metal cousins, Discovery Slayer. 🤘 |
| 12:11 |
csharp_ |
YES |
| 12:46 |
|
jihpringle92 joined #evergreen |
| 14:06 |
csharp_ |
berick: Bmagic: in ansible installer, have either of you considered using an XPath module for all the XML replacement stuff? |
| 14:07 |
csharp_ |
currently perusing https://docs.ansible.com/ansible/latest/collections/community/general/xml_module.html |
| 14:08 |
csharp_ |
use case leading me here: I have a database that I need to connect to but the evergreen-ansible-installer only assumes the DB to be installed on localhost |
| 14:08 |
csharp_ |
so I was going to use the same DB variables that eg_db_config.pl would be using |
| 14:11 |
berick |
csharp_: for similar stuff, ansible has a handy builtin temlpating engine. e.g. the websocketd-osrf.service.j2 file in my ansible installer |
| 14:11 |
csharp_ |
I'll take a look |
| 14:11 |
berick |
opensrf_core.xml is a little more complicated becasue we have to modify it after EG has installed it. |
| 14:12 |
berick |
specifically to pick up the autogenerated passwords |
| 14:12 |
berick |
which will be a non-issue once redis is the default |
| 14:15 |
berick |
in the meantime, might be worth having a templated opensrf_core.xml in the ansible installer and just use 'password' for the passwords (as w/ ejabberd). |
| 14:15 |
berick |
would simplify some things |
| 14:16 |
csharp_ |
yeah, that makes sense |
| 14:16 |
csharp_ |
I'll tinker |
| 14:17 |
berick |
modifying database connection settings would mean doing the same w/ opensrf.xml or, as you say, maybe an xml/xpath module |
| 14:18 |
berick |
to answer your actual question, no, i have not used those before |
| 14:20 |
* csharp_ |
mumbles something about using XPath means you now have 2 problems... |
| 14:21 |
jeffdavis |
Our current approach is to specify the Redis passwords in Ansible and use j2 templates for both opensrf_core.xml and redis-accounts.txt, rather than using the autogenerated passwords. |
| 14:22 |
csharp_ |
jeffdavis: interesting |
| 14:24 |
berick |
jeffdavis: cool, i'm thinking the same w/ a default |
| 14:26 |
csharp_ |
cat /proc/sys/kernel/random/uuid - I didn't realize that's where those are coming from |
| 14:27 |
csharp_ |
I guess you could also generate them via a playbook? |
| 14:27 |
berick |
yeah. ansible has uuid, random, etc. generators |
| 14:28 |
csharp_ |
ah ansible.builtin.password |
| 14:33 |
csharp_ |
@decide believe weather app that says it's snowing or believe my own eyes |
| 14:33 |
pinesol |
csharp_: go with believe my own eyes |
| 14:39 |
berick |
jeffdavis: are you using Redis in production? any issues? |
| 14:39 |
jeffdavis |
No, not in production yet - we're planning to go live with it when we upgrade in April. |
| 14:39 |
csharp_ |
jeffdavis++ |
| 14:39 |
csharp_ |
our plans are for next month |
| 14:57 |
|
sandbergja joined #evergreen |
| 15:54 |
csharp_ |
Khruangbin++ |
| 15:54 |
csharp_ |
also, the snow is real, y'all |
| 16:06 |
|
sandbergja joined #evergreen |
| 18:34 |
|
eglogbot joined #evergreen |
| 18:34 |
|
Topic for #evergreen is now Welcome to #evergreen (https://evergreen-ils.org). This channel is publicly logged. Logs for today: http://irc.evergreen-ils.org/evergreen/today |
