| harlowja | dmsimard have u seen https://gist.github.com/harlowja/ba07b0839d984ccf9b8b20e3debc8db9 | 00:15 |
|---|---|---|
| harlowja | me thinking a retry might be needed | 00:15 |
| harlowja | (yes i should get off sqlite) | 00:16 |
| harlowja | but maybe u already added some retry abilities | 00:18 |
| harlowja | seems like when that happened, it lost some data | 00:18 |
| harlowja | also seems to be related to me refreshing the UI while a playbook is still running | 00:21 |
| harlowja | i prob should move to mysql when 1.0 ships, ha | 00:23 |
| dmsimard | harlowja: never really seen that, but I guess sqlite is not very friendly to concurrent read and writes iirc | 01:12 |
| dmsimard | Need better exception and retry logic in ara, yes | 01:12 |
| dmsimard | A bit hard to implement proper error handling right now since database access is scattered all over the place | 01:15 |
| dmsimard | Hoping that the API layer will be a good central place to implement that kind of stuff | 01:15 |
| *** sebiwi has joined #ara | 08:08 | |
| sebiwi | hi, I'm having an issue with Ara | 08:09 |
| sebiwi | I'm under the impression that playbook data is not saved when the playbooks fail | 08:09 |
| sebiwi | so I have a beautiful dashboard without any red in it | 08:09 |
| *** sgr has quit IRC | 09:30 | |
| *** sebiwi has quit IRC | 09:49 | |
| dmsimard | sebiwi has asked questions twice at 4AM for me and left without giving me the opportunity to answer... | 11:58 |
| *** resmo has joined #ara | 11:59 | |
| *** tbielawa has joined #ara | 13:46 | |
| *** dmsimard has quit IRC | 15:19 | |
| *** dmsimard has joined #ara | 15:19 | |
| *** tolkien.freenode.net sets mode: +o dmsimard | 15:19 | |
| *** resmo has quit IRC | 15:33 | |
| *** tbielawa has quit IRC | 15:43 | |
| *** tbielawa has joined #ara | 15:49 | |
| *** tbielawa is now known as tbielawa|lunch | 15:50 | |
| harlowja | :-P | 16:44 |
| harlowja | ya, i've seen that before, lol | 16:44 |
| harlowja | (people asking then leaving) | 16:44 |
| ara-slack | <nullah> don't take it personall @dmsimard ... if it makes you feel better I have a question | 16:45 |
| ara-slack | <nullah> :P | 16:45 |
| ara-slack | <nullah> So, in general, it's best to have ara run seperately from a control machine? (I presume you can link many control machines to 1 single ara instance and that's why) | 16:45 |
| ara-slack | <nullah> furthermore, is it ok to have db and web server running on ara instance? I know it's case by case but generally what's the best practice? | 16:46 |
| ara-slack | <dmsimard> @nullah The two main use cases I've seen are | 16:57 |
| ara-slack | <dmsimard> 1) Run ansible-playbook once, generate static HTML report, upload report to log/web server (This is very popular with CI such as Jenkins, or Zuul, it allows to easily associate the report with the job it ran) | 16:58 |
| ara-slack | <dmsimard> 2) Host ARA as a WSGI application and a MySQL database, doesn't matter if the database and the webserver are on different machines. And then run ansible-playbook from wherever you need (i.e, your laptop) with the appropriate database configuration. | 16:59 |
| ara-slack | <nullah> Ara fetches info from DB to produce the reports right? | 17:00 |
| ara-slack | <dmsimard> The web application connects to the database to allow you to browse the recorded playbooks in the database, yes | 17:00 |
| ara-slack | <nullah> ok. cool. thanks for the insight. | 17:01 |
| ara-slack | <dmsimard> The static HTML generation more or less starts the webapp and crawls and saves every pages | 17:01 |
| ara-slack | <nullah> in both cases, ara is running elsewhere than control machine | 17:01 |
| ara-slack | <nullah> right? | 17:01 |
| ara-slack | <nullah> i.e. decouples so to speak | 17:02 |
| ara-slack | <dmsimard> @nullah btw I was invited to an Ansible meetup in Quebec City to present ARA in October, there's also going to be a Ansible meetup in Montreal around the time same if you want to chat :slightly_smiling_face: | 17:02 |
| ara-slack | <nullah> I'll be there! ;) | 17:02 |
| ara-slack | <dmsimard> What do you mean by "ara is running" ? | 17:02 |
| ara-slack | <dmsimard> The web app ? | 17:02 |
| ara-slack | <nullah> hosted | 17:02 |
| ara-slack | <nullah> i mean uhm | 17:02 |
| ara-slack | <nullah> what do i mean wait | 17:03 |
| ara-slack | <nullah> haha | 17:03 |
| ara-slack | <nullah> "installed on" | 17:03 |
| ara-slack | <dmsimard> ARA needs to be installed wherever you'll be using Ansible from, and Ansible should be configured to use the ARA callback. | 17:03 |
| ara-slack | <nullah> oh so control machine + ara reside on same server | 17:03 |
| ara-slack | <dmsimard> The web application and the callback are two separate components | 17:04 |
| ara-slack | <dmsimard> The callback *writes* the data to the database, the web application reads from it | 17:04 |
| ara-slack | <dmsimard> You need the callback installed and used wherever you're running Ansible from | 17:04 |
| ara-slack | <dmsimard> It doesn't matter where the web application is hosted so long as it has access to that database | 17:04 |
| ara-slack | <nullah> gotcha. so no problem in having ansible+ara+webserver+mysql all on same node right? | 17:04 |
| ara-slack | <dmsimard> In theory, no, but like you've seen the other day, it tends to be needlessly confusing | 17:05 |
| ara-slack | <nullah> oh ok right. so to simplify that we would decouple the web server and db components from the ansible+ara node | 17:05 |
| ara-slack | <nullah> right? | 17:05 |
| *** tbielawa|lunch is now known as tbielawa|brb | 17:08 | |
| ara-slack | <nullah> i.e. best approach = ansible/ara node + webserver + db = 3 instances in total, is that correct? | 17:08 |
| ara-slack | <dmsimard> There is probably no best approach that covers all use cases, it depends on what you intend on doing with ara and how you plan on using it | 17:21 |
| ara-slack | <nullah> OK fair enough. But we've determined that having webserver+db on ansible/ara is needlessly confusing | 17:21 |
| ara-slack | <dmsimard> right | 17:22 |
| ara-slack | <nullah> OK | 17:22 |
| ara-slack | <dmsimard> splitting the database and web servers is probably overkill, unless you're running at a huge scale | 17:22 |
| ara-slack | <nullah> great! ok so ara/ansible + webserver/db is best approach for small to medium scale? | 17:23 |
| ara-slack | <nullah> or is it ara/ansible/webserver + db | 17:24 |
| *** harlowja has quit IRC | 17:30 | |
| ara-slack | <dmsimard> @nullah http://logs.bonnyci.org/ara/ runs a centralized setup on modest virtual machines afaik and they have 32k playbooks | 17:34 |
| *** tbielawa|brb is now known as tbielawa | 17:34 | |
| ara-slack | <dmsimard> I would say not to split the database and web server until your scale justifies it, which might never happen | 17:35 |
| ara-slack | <nullah> ok cool! | 17:35 |
| ara-slack | <dmsimard> or unless you want to implement some sort of HA setup with load balancers/clusters/etc | 17:35 |
| ara-slack | <nullah> probably not. looking for simplest setup at this point | 17:36 |
| *** tbielawa has quit IRC | 17:56 | |
| *** tbielawa has joined #ara | 17:56 | |
| *** tbielawa is now known as tbielawa|bbiab | 19:04 | |
| *** tbielawa|bbiab is now known as tbielawa | 20:07 | |
| *** tbielawa has quit IRC | 21:21 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!