| *** Arsenick has joined #ara | 01:52 | |
| dmsimard | Work in progress to bootstrap an Ansible role for installing ara-server: https://github.com/dmsimard/ansible-role-ara-server | 03:01 |
|---|---|---|
| Arsenick | dmsimard: That's a good news! What's different than the one in the openstack repo ? | 03:41 |
| dmsimard | Arsenick: the one in the openstack repo is targetted at 0.x | 03:41 |
| dmsimard | I looked at what it would look like if I ported it to 1.0 and it didn't suit very well | 03:41 |
| dmsimard | Robert De Bock has a great Ansible role for ARA too: https://github.com/robertdebock/ansible-role-ara | 03:42 |
| Arsenick | ok, I'm lookinf forward to test the new one then, we are using ara since your presentation at the rhug Quebec city ;) | 03:43 |
| dmsimard | Arsenick: we have live demos at https://api.demo.recordsansible.org/api/v1/ and https://web.demo.recordsansible.org/ | 03:44 |
| dmsimard | it doesn't look like much but most of the hard work is done | 03:44 |
| dmsimard | :) | 03:44 |
| dmsimard | this new ara-server role is actually part of re-deploying api.demo from scratch after every commit | 03:45 |
| Arsenick | nice I didn't knew ara was on track for 1.0 soon, I might have missed the news! | 03:46 |
| dmsimard | we'll be consumer of the role in a lot of ways so hopefully this will be a strong feedback loop | 03:46 |
| dmsimard | Arsenick: part one https://ara.recordsansible.org/blog/2019/01/16/introducing-new-projects-for-the-upcoming-1.0-release/ | 03:47 |
| Arsenick | It's like a new world coming here, I've never found that blog nor getara.org in the topic lol.. I've always landed in the documentation or in the openstack github while searching for ara | 03:49 |
| Arsenick | Thanks for the link | 03:49 |
| dmsimard | oh, getara.org is the old domain | 03:49 |
| dmsimard | but it's still on the stickers so I'll just keep it and it's redirected | 03:50 |
| dmsimard | just noticed it's not redirected right though | 03:50 |
| Arsenick | Hehe yup! | 03:50 |
| *** ChanServ sets mode: +o dmsimard | 03:50 | |
| *** dmsimard changes topic to "ARA Records Ansible: Making playbook runs easier to visualize, understand and troubleshoot | https://ara.recordsansible.org | Git: https://github.com/openstack/ara | Changelog: https://github.com/openstack/ara/releases | This channel is logged: http://eavesdrop.openstack.org/irclogs/%23ara/"" | 03:51 | |
| *** dmsimard sets mode: -o dmsimard | 03:52 | |
| Arsenick | btw, I have a question for you. I'd like to know if it's possible to easily modify the way the playbook name is displayed Ex. smoke.yml in the web demo ? Here's a bit of context, ARA is installed on VSTS agents where our pipeline deploy the infra in azure and then run playbooks to configure them, but the agents are used by differents person and different pipeline, so the playbook smoke.yaml could be called by 3 different person/pipeline and it's a bit hard | 03:56 |
| Arsenick | to differentiate which one is mine. For now I'm using ara_record to set few value but it would be awesome if there was a way to display this in the name or anywhere else.. I don't know if my explanation is clear enough.. ;) I can say it in french that would probably be easier to understand! hah | 03:56 |
| Arsenick | or a global searchbox or a filter something along those line | 03:56 |
| dmsimard | Arsenick: so there's going to be a few things that will be able to help for that in 1.0 | 03:56 |
| Arsenick | sweet | 03:57 |
| dmsimard | you can give playbook names at runtime with an ansible variable (ara_playbook_name) | 03:58 |
| dmsimard | in the web client, the file path would probably be displayed if the playbook was not given a name | 03:59 |
| Arsenick | oh, I'll try with ara_playbook_name that could do the trick for now | 03:59 |
| dmsimard | the other feature that might help is labels | 03:59 |
| dmsimard | but I'm still thinking about the client side implementation | 04:00 |
| dmsimard | the general idea is that you can tag playbooks with labels -- any label | 04:00 |
| dmsimard | so then it makes those labels searchable in the API (and web client) | 04:00 |
| dmsimard | this is what it might look like: https://gist.github.com/dmsimard/de4a1dc51136e73054fb5f3515ac754b | 04:01 |
| Arsenick | I think that would be perfect for our usecase, that way I could tag with the username who launched the release, the name of the pipeline etc.. and if they are searchable we got everything! | 04:02 |
| dmsimard | Arsenick: yes. | 04:02 |
| dmsimard | \o/ | 04:02 |
| Arsenick | hehe | 04:02 |
| dmsimard | there will be something similar for hosts | 04:02 |
| dmsimard | letting you search results for a specific host across multiple playbook runs | 04:03 |
| dmsimard | I need to write moar docs | 04:03 |
| Arsenick | yeah we all know that feeling | 04:04 |
| Arsenick | ;) | 04:04 |
| Arsenick | anyway congrats for the project it's really usefull and well made! Keep up the good work | 04:07 |
| Arsenick | I'll try to stay here and help testing new releases, I'm really not a good dev so can't help on the code but I'll be happy to help whenever I can | 04:07 |
| dmsimard | I'm trying to make it easy to try out in different ways both for small and *larger* deployments | 04:08 |
| dmsimard | We still have a few features to land but I've shifted a lot of focus to better integration testing and the other things around that, the roles, etc. | 04:09 |
| dmsimard | But by doing that, I'm also writing tools that people can use to get started | 04:10 |
| Arsenick | Great, I hope you'll come back show that to us at the RHUG once it's ready | 04:12 |
| dmsimard | yes, in fact I'm working with Michael to start organizing the next meetups | 04:12 |
| Arsenick | Good news! I can't remember you were from mtl or qc ? | 04:12 |
| dmsimard | I've done both, haha | 04:12 |
| dmsimard | I've presented at the Ansible meetup at the Microsoft office from Quebec | 04:13 |
| dmsimard | and I've presented at several meetups in Montreal :p | 04:13 |
| Arsenick | yeah that's where I was, but I just can't recall if you are living in qc or mtl | 04:13 |
| dmsimard | Montreal :) | 04:14 |
| dmsimard | I drove to QC for the meetup haha | 04:14 |
| Arsenick | it's always great to find people working on foss in qc | 04:14 |
| Arsenick | ok nice, it was great, you "sold" it to us ;) | 04:14 |
| dmsimard | selling free software \o/ | 04:18 |
| Arsenick | haha | 04:18 |
| dmsimard | it's actually a common misconception that red hat sells free software | 04:18 |
| Arsenick | Yeah a lot of people need to read more about redhat and think about what it has done/give to the human race since the beginning.. | 04:21 |
| Arsenick | Enough for tonight, see ya. Thanks again for the work you are doing! gnight | 04:22 |
| dmsimard | ++ | 04:23 |
| *** etienne has joined #ara | 05:05 | |
| *** herald85 has joined #ara | 07:58 | |
| *** gvincent has quit IRC | 08:49 | |
| *** gvincent has joined #ara | 09:22 | |
| *** ssbarnea|bkp2 has joined #ara | 09:38 | |
| *** ssbarnea|rover has quit IRC | 09:39 | |
| *** gnupyx has joined #ara | 09:40 | |
| *** ssbarnea|bkp2 has quit IRC | 09:59 | |
| *** ssbarnea|rover has joined #ara | 10:00 | |
| *** ssbarnea|rover has quit IRC | 10:01 | |
| *** ssbarnea has joined #ara | 10:02 | |
| *** ssbarnea|bkp2 has joined #ara | 10:06 | |
| *** ssbarnea has quit IRC | 10:07 | |
| dmsimard | apollo13, gvincent: In the context of updating api.demo automatically, I'm working on bootstrapping an Ansible role for ara-server: https://github.com/dmsimard/ansible-role-ara-server | 14:36 |
| dmsimard | has a narrow set of supported deployment options (i.e, gunicorn and nginx) but we can add support for other things like uwsgi, mod_wsgi, etc. later on | 14:37 |
| dmsimard | I eventually want to use the role for integration testing as well :D | 14:37 |
| gvincent | httpd + mod_wsgi or gunicorn IMO | 14:38 |
| dmsimard | gvincent: yes, the general idea is to support the most popular deployment configurations in the role so we can use the role to test these deployment configurations | 14:47 |
| dmsimard | We need to test mysql and postgre too | 14:47 |
| gvincent | hum | 14:47 |
| gvincent | I disagree but ok :D | 14:48 |
| Jmainguy | needs more oracle database | 14:51 |
| Jmainguy | look how popular they are | 14:51 |
| dmsimard | gvincent: what are you disagreeing on ? | 15:05 |
| gvincent | to support multiple storage backend | 15:06 |
| dmsimard | gvincent: it's supported out of the box by django, why not ? | 15:06 |
| dmsimard | also, sqlite works well but has real limitations -- especially with concurrent writes | 15:06 |
| gvincent | why not? because it will introduce some extra work | 15:07 |
| gvincent | I prefer to choose one (postgresql) and test correctly with this backend | 15:07 |
| dmsimard | 0.x supports mysql and postgre through sqlalchemy | 15:08 |
| dmsimard | but isn't well tested | 15:08 |
| gvincent | but as I said I'm ok with this, I just prefer one well tested instead of 2/3 backends not tested | 15:08 |
| dmsimard | gvincent: the cost of testing mysql is writing a job that sets up mysql and ara to use mysql | 15:08 |
| dmsimard | 0.x has a hook for testing postgre -- it's designed to use the postgresql docker container | 15:09 |
| gvincent | and in the future some feature only avaialble on postgresql could not be used | 15:09 |
| gvincent | but if you are motivated to support mysql and postgres ;D | 15:10 |
| gvincent | let's go | 15:10 |
| Jmainguy | sqlite is awesome | 15:12 |
| dmsimard | Jmainguy: ++ | 15:13 |
| gvincent | yeah until you want to do 2 writes in the same time | 15:13 |
| dmsimard | we've scaled ara to >1 000 000 playbooks a month with sqlite in the openstack ci infrastructure :p | 15:13 |
| Jmainguy | I had some problems writing an app to do that with sqlite, but eventually got past it | 15:15 |
| Jmainguy | https://github.com/Jmainguy/survey_hail a texting survey app thing I wrote, which stored texts in sqlite | 15:16 |
| Jmainguy | just got to configure your app to not try writing 2x things at once =) | 15:17 |
| Jmainguy | wait for sqlite to be writable and try then | 15:18 |
| Jmainguy | dmsimard: gvincent what do you believe is the target market / expected architecture for most consumers of ARA? | 15:18 |
| Jmainguy | vms, containers, old reliable centos, or brand new fedora, full cluster of mysql / postgres, or sqlite | 15:19 |
| gvincent | Jmainguy, dmsimard can answer this one, I don't know | 15:20 |
| dmsimard | Jmainguy: right now we're testing against f29 and ubuntu bionic mostly because it brings us enough coverage without dragging our velocity down into attempting to support too many things out of the gate | 15:20 |
| dmsimard | we're targetting python >=3.6 | 15:21 |
| dmsimard | so it does exclude a lot of things (CentOS 7/RHEL 7 doesn't ship python3, for example) | 15:21 |
| dmsimard | I suspect that we will have a client and callback implementation that is supported on py2 but only when using a remote API server -- py2 wouldn't work with the offline client. | 15:22 |
| Jmainguy | seems reasonable | 15:23 |
| dmsimard | In terms of architecture, the "default" deployment is very similar to ara 0.x | 15:23 |
| dmsimard | You don't need to start an API server -- you pip install ara-server and ara-plugins, set the callback in Ansible and you're ready to start recording things locally on a sqlite database | 15:24 |
| Jmainguy | nice | 15:27 |
| dmsimard | If users need more than that, either because they're aggregating data from multiple locations or they need more performance/throughput, then we can start talking about a proper gunicorn/nginx setup or a apache/mod_wsgi setup.. maybe a mysql, maybe a postgre, etc | 15:27 |
| Jmainguy | for my personal use case, where I would be hosting it in openshift, and having clients connect to it from laptops and vms | 15:27 |
| Jmainguy | I would use gunicorn and mysql if needed, but if sqlite and gunicorn worked I would use that | 15:28 |
| Jmainguy | since those seem easier to containerize for my use case | 15:28 |
| dmsimard | Before releasing, I want to run some benchmarks | 15:28 |
| dmsimard | to compare 0.x against 1.0 | 15:28 |
| dmsimard | but also to benchmark different deployment scenarios in 1.0 | 15:28 |
| *** etienne has quit IRC | 15:29 | |
| dmsimard | Jmainguy: when using a remote API (or database) server, the main concern I have is the impact of latency on playbook perforamnce | 15:29 |
| dmsimard | which is also why I tend to recommend using sqlite for as long as possible (to avoid the roundtrip to a remote database server) | 15:30 |
| Jmainguy | makes sense | 15:30 |
| Jmainguy | yeah i dont have a need for a full cluster of databases for ARA, if the remote api worked great with sqlite, I would definitly just use that mdoel | 15:31 |
| Jmainguy | would be much easier for me to deploy that way as well | 15:31 |
| dmsimard | the one thing that is admittedly different in 1.0 is that the web interface doesn't come built-in | 15:32 |
| dmsimard | I mean, when you do "pip install ara" to install 0.x, it's a single package with everything in it (backend, frontend, callback, plugins, etc) | 15:32 |
| dmsimard | The web interface isn't hard to run locally, it's like npm install/npm start but since it is stateless, it does requires an API server to connect to | 15:33 |
| dmsimard | for example, https://web.demo.recordsansible.org/ is actually pulling real data from https://api.demo.recordsansible.org/ | 15:34 |
| *** TimNZ has quit IRC | 15:34 | |
| *** TimNZ has joined #ara | 15:35 | |
| dmsimard | I think ara-server and ara-web are good candidates for putting in containers, there's going to be ansible roles for them too so hopefully it should be ok | 15:35 |
| Jmainguy | nice | 15:35 |
| Jmainguy | yall are doing a great job, keep it up | 15:36 |
| dmsimard | trying hard, thanks :D | 15:37 |
| dmsimard | apollo13: added comments on https://review.openstack.org/#/c/631287/ which otherwise looks good to me | 15:43 |
| openstackgerrit | Florian Apolloner proposed openstack/ara-server master: Added support for external auth via REMOTE_USER provided by webservers. https://review.openstack.org/631287 | 16:01 |
| openstackgerrit | Merged openstack/ara-server master: Added very basic read/write authentication. https://review.openstack.org/631285 | 16:10 |
| openstackgerrit | Merged openstack/ara-server master: First iteration of authentication and security docs https://review.openstack.org/632181 | 16:10 |
| apollo13 | dmsimard: arg what did you just do :D | 16:10 |
| dmsimard | apollo13: ? | 16:10 |
| apollo13 | https://review.openstack.org/#/c/632181/ zuul just said "change is closed" :D | 16:10 |
| dmsimard | apollo13: did you have comments for it ? I can address in a follow up | 16:11 |
| apollo13 | I can no longer post comments there, so here is a screenshot: https://screenshots.firefox.com/1jBoogbKoDszHO3j/review.openstack.org | 16:11 |
| apollo13 | btw, I think (didn't test it) that dynaconf allows us to use lower-cased names in settings files | 16:12 |
| apollo13 | which might or might not be something to consider | 16:12 |
| apollo13 | I personally find it hard to read uppercase settings, but ymmv (ie as in I do not care) :D | 16:12 |
| dmsimard | yeah I don't have a strong opinion either | 16:13 |
| dmsimard | apollo13: I'm not sure I follow your concern about "default" | 16:13 |
| dmsimard | default is the default env | 16:13 |
| apollo13 | no it is not | 16:13 |
| dmsimard | is it not ? | 16:13 |
| apollo13 | the default env is development | 16:13 |
| dmsimard | ok but we're calling it default :p | 16:14 |
| dmsimard | I mean | 16:14 |
| apollo13 | no we are not | 16:14 |
| apollo13 | we just didn't notice :D | 16:14 |
| apollo13 | see https://dynaconf.readthedocs.io/en/latest/guides/configuration.html | 16:14 |
| apollo13 | ENV there says "development" is default | 16:14 |
| dmsimard | apollo13: yes, but we call the default env default | 16:14 |
| dmsimard | or wait | 16:14 |
| dmsimard | maybe we don't | 16:15 |
| apollo13 | did we somewhere tell dynaconf so? | 16:15 |
| dmsimard | hmmmm | 16:15 |
| apollo13 | because otherwise, in https://dpaste.de/wqjp host=123 will win | 16:15 |
| apollo13 | no matter what you put in default | 16:15 |
| dmsimard | apollo13: ah, this is where it comes from https://github.com/openstack/ara-server/blob/master/ara/server/settings.py#L216 | 16:15 |
| apollo13 | yes | 16:15 |
| apollo13 | which is nice in the sense that [default] serves as fallback for __all__ env | 16:16 |
| apollo13 | but technically the default env is development | 16:16 |
| dmsimard | ok, I understand what you mean now | 16:16 |
| dmsimard | yes, I can clarify that | 16:16 |
| dmsimard | apollo13: the "provided by" part is an attempt at linking to other docs where relevant | 16:17 |
| dmsimard | i.e, I don't want to copy/paste django/drf/dynaconf docs in ara's docs | 16:17 |
| dmsimard | so it's kind of like a "read more" for users that might care | 16:17 |
| apollo13 | yeah, I figured | 16:18 |
| dmsimard | apollo13: "privileges" might be a frenchism | 16:18 |
| dmsimard | I realize how it can be confusing, and now I'm not even sure it's a thing in english | 16:19 |
| apollo13 | :D | 16:19 |
| dmsimard | yeah from a quick google it's not a thing | 16:19 |
| dmsimard | in french there is a word that looks like that and it means that is values something more than something else | 16:19 |
| dmsimard | sort of like a preference | 16:19 |
| apollo13 | hurray, I could contribute something useful to docs^^ | 16:20 |
| apollo13 | https://github.com/openstack/ara-server/blob/master/.zuul.d/jobs.yaml#L15 anything stopping us from just getting rid of them? | 16:20 |
| dmsimard | soon | 16:20 |
| dmsimard | in hindsight, it's a bit trickier than I had expected and I'm not positive how to properly do it | 16:20 |
| dmsimard | (yet) | 16:21 |
| apollo13 | ok, what is the issue? | 16:21 |
| dmsimard | in ara-server, tox-linters actually shells out to a bash script which runs black, pep8, bandit, etc | 16:21 |
| dmsimard | it's a way to get feedback from all the linters in one shot instead of failing at the first occurrence and not running the ones after that | 16:22 |
| apollo13 | yes | 16:22 |
| dmsimard | the plan was to run this job against the other repos too | 16:22 |
| dmsimard | but then it means we need that shell script in the other repos too ? | 16:22 |
| apollo13 | ah | 16:22 |
| dmsimard | and then each project might have their own exceptions or w/e | 16:22 |
| apollo13 | yikes | 16:23 |
| apollo13 | I see, but we do not have a format env at all anymore in ara-server, so what does that offer? | 16:23 |
| dmsimard | in zuul, the configuration is shared across projects | 16:23 |
| dmsimard | ara-clients and ara-plugins are still using that tox-format job | 16:23 |
| apollo13 | ah okay, the comment could have said that ;) | 16:24 |
| dmsimard | If zuul even lets us remove it (it might spit out an error because the job is still used elsewhere), it would break the other things | 16:24 |
| dmsimard | well, I didn't expect that job to stick around that long | 16:24 |
| apollo13 | yeah | 16:24 |
| *** herald85 has quit IRC | 16:25 | |
| apollo13 | https://ara-server.readthedocs.io/en/latest/ look what I found :þ | 16:25 |
| dmsimard | yes it's actually not up to date | 16:25 |
| dmsimard | because the readthedocs webhook is broken | 16:25 |
| dmsimard | I need to trigger them manually for now | 16:25 |
| apollo13 | ah | 16:26 |
| dmsimard | just triggered it | 16:26 |
| dmsimard | so, what might happen with the linters job | 16:26 |
| dmsimard | is we could relocate it to ara-infra (where the other integration tests live) and have the linters job run the tests from ara-infra | 16:27 |
| dmsimard | pseudo-code: git clone https://github.com/openstack/ara-infra; ansible-playbook playbooks/linters.yaml | 16:27 |
| Jmainguy | is precedence the english version of the french "privleges"? | 16:27 |
| Jmainguy | means one thing is more important than the other | 16:27 |
| dmsimard | Jmainguy: precedence is a word in french too :) | 16:27 |
| Jmainguy | womp | 16:27 |
| dmsimard | Jmainguy: dictionary proposes things like "focus on", "emphasize" or "prioritize" https://www.linguee.fr/francais-anglais/traduction/privil%C3%A9gier.html | 16:28 |
| dmsimard | there's several words both in french and english that do not have a direct translation and it confuses my brain sometimes :p | 16:29 |
| dmsimard | apollo13: up to date (needed a ctrl+f5 for me tho): https://ara-server.readthedocs.io/en/latest/ | 16:29 |
| apollo13 | nice | 16:31 |
| apollo13 | https://etherpad.openstack.org/p/ara-todo-1.0 looks rather nice | 16:34 |
| dmsimard | apollo13: the last big chunk is probably the CLI | 16:36 |
| dmsimard | the equivalent to "ara playbook list" from 0.x, for example | 16:36 |
| apollo13 | I've never used ara, so… :D | 16:36 |
| dmsimard | T_T | 16:36 |
| * Jmainguy cries | 16:36 | |
| dmsimard | apollo13: https://ara.readthedocs.io/en/stable/usage.html#querying-the-database-with-the-cli | 16:37 |
| dmsimard | apollo13: 0.x uses cliff as the CLI framework -- it has some nice features like different output formats (pretty tables, json, yaml, etc.), filtering of columns | 16:39 |
| dmsimard | I am not terribly attached to it | 16:40 |
| apollo13 | I only know click, dunno, use whatever works for you :) | 16:41 |
| apollo13 | generating nice tables seems like something nice though | 16:41 |
| dmsimard | I've tried click once (for the ara-slack bridge, infact) | 16:42 |
| apollo13 | or just https://pypi.org/project/tabulate/#description | 16:42 |
| dmsimard | pretty tables aren't great for everything, though | 16:42 |
| apollo13 | for the tables that is | 16:42 |
| apollo13 | right | 16:42 |
| dmsimard | apollo13: attempting to display host facts through pretty tables is ugly: http://logs.openstack.org/22/631822/2/check/ara-integration-debian-py27-2.6.12/b5541b5/job-output.txt.gz#_2019-01-21_14_57_31_523489 | 16:43 |
| apollo13 | haha | 16:44 |
| dmsimard | apollo13: https://github.com/donnemartin/saws uses click and https://github.com/prompt-toolkit/python-prompt-toolkit | 16:51 |
| apollo13 | oh, that looks nice | 16:52 |
| dmsimard | lol, aws has a lot of commands https://github.com/donnemartin/saws/blob/master/saws/data/SOURCES.txt | 16:54 |
| apollo13 | well now you can probably imagine why security polcies in amazon are a nightmare | 17:12 |
| dmsimard | apollo13: do we care about MEDIA_ROOT and MEDIA_URL ? | 17:24 |
| dmsimard | I don't think we use them | 17:25 |
| apollo13 | no, not as long as we allow uploads of files to the filesystem | 17:25 |
| apollo13 | as we do not allow * | 17:25 |
| dmsimard | would it break anything if we removed them from settings.py ? | 17:26 |
| dmsimard | I guess I could try | 17:26 |
| apollo13 | nope, shouldn't change a thing | 17:26 |
| apollo13 | we can probably even get rid of STATIC_ROOT/FILES if we use whitenoise to serve them | 17:27 |
| dmsimard | whitenoise ? | 17:27 |
| apollo13 | https://pypi.org/project/whitenoise/ | 17:27 |
| apollo13 | performance is obviously lower than letting apache/nginx do it, but I doubt we'd care | 17:27 |
| dmsimard | well, the only thing we're serving is the DRF web interface, right | 17:27 |
| apollo13 | admin interface too | 17:28 |
| dmsimard | and the admin panel, I guess | 17:28 |
| dmsimard | yeah | 17:28 |
| dmsimard | good to know that it exists, we can consider it later | 17:28 |
| openstackgerrit | David Moreau Simard proposed openstack/ara-server master: Misc updates to security and configuration documentation https://review.openstack.org/633248 | 17:30 |
| openstackgerrit | David Moreau Simard proposed openstack/ara-server master: Add pip-wheel-metadata to gitignore https://review.openstack.org/633249 | 17:33 |
| openstackgerrit | David Moreau Simard proposed openstack/ara-clients master: Fix pep8 issues https://review.openstack.org/633251 | 17:35 |
| *** mgariepy has joined #ara | 19:43 | |
| *** etienne has joined #ara | 20:07 | |
| *** mgariepy has quit IRC | 20:25 | |
| *** med_ has quit IRC | 20:30 | |
| dmsimard | apollo13, gvincent: once the last outstanding patches land, I'll tag alpha2 and upload to pypi | 21:08 |
| openstackgerrit | Merged openstack/ara-clients master: Fix pep8 issues https://review.openstack.org/633251 | 21:16 |
| openstackgerrit | Merged openstack/ara-server master: Added support for external auth via REMOTE_USER provided by webservers. https://review.openstack.org/631287 | 21:28 |
| openstackgerrit | Merged openstack/ara-server master: Misc updates to security and configuration documentation https://review.openstack.org/633248 | 21:28 |
| dmsimard | 1.0.0a2 tagged for ara-server, ara-plugins, ara-clients and ara-web -- everything but ara-web has been updated on pypi | 23:11 |
| dmsimard | - ara-server: https://github.com/openstack/ara-server/releases/tag/1.0.0a2 | 23:11 |
| dmsimard | - ara-clients: https://github.com/openstack/ara-clients/releases/tag/1.0.0a2 | 23:12 |
| dmsimard | - ara-plugins: https://github.com/openstack/ara-plugins/releases/tag/1.0.0a2 | 23:12 |
| dmsimard | - ara-web: https://github.com/openstack/ara-web/releases/tag/1.0.0a2 | 23:12 |
| dmsimard | Live demos have been updated as well, signing off for now, have a nice weekend everyone o/ | 23:27 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!