summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Moreau Simard <dmsimard@redhat.com>2019-03-11 17:31:32 -0400
committerDavid Moreau Simard <dmsimard@redhat.com>2019-03-11 17:44:57 -0400
commit5c226dbea265853c300cfa644eb9e99a4a083653 (patch)
tree93122a93c67dc16fbfe8edd7fbea267204a23757
parenta797094b61d3dd5f7ccb25849499489ed40cafea (diff)
Add blog post for alpha3 milestone
Notes
Notes (review): Code-Review+2: David Moreau Simard <dmsimard@redhat.com> Workflow+1: David Moreau Simard <dmsimard@redhat.com> Verified+2: Zuul Submitted-by: Zuul Submitted-at: Tue, 12 Mar 2019 00:54:40 +0000 Reviewed-on: https://review.openstack.org/642579 Project: openstack/ara-infra Branch: refs/heads/master
-rw-r--r--website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/changelog.pngbin0 -> 69213 bytes
-rw-r--r--website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/index.md94
2 files changed, 94 insertions, 0 deletions
diff --git a/website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/changelog.png b/website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/changelog.png
new file mode 100644
index 0000000..8c44ec1
--- /dev/null
+++ b/website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/changelog.png
Binary files differ
diff --git a/website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/index.md b/website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/index.md
new file mode 100644
index 0000000..027e847
--- /dev/null
+++ b/website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/index.md
@@ -0,0 +1,94 @@
1---
2author: "David Moreau Simard"
3categories:
4 - development
5tags:
6 - ansible
7date: 2019-03-11
8title: "ARA 1.0 alpha3: back to basics"
9slug: ara-1.0-alpha3-back-to-basics
10type: post
11---
12
13The release of ARA 1.0 draws closer with a third alpha milestone !
14
15![changelog](changelog.png)
16
17If there was a theme for this milestone it would be "back to basics".
18
19In the previous [blog post](https://ara.recordsansible.org/blog/2019/01/16/introducing-new-projects-for-the-upcoming-1.0-release/),
20I explained that ARA 1.0 was composed of several projects such as ``ara-server``,
21``ara-plugins``, ``ara-clients``, ``ara-web`` and ``ara-infra``.
22
23As a user, developer and maintainer of these projects myself, I realized that
24the added complexity of keeping the projects separated did not provide enough
25value to be worth it.
26
27Things had to be simple because simplicity is a feature in ARA and failing to
28be simple meant that we were not staying true to the project's [core values](https://ara.readthedocs.io/en/stable/manifesto.html).
29
30## One repository instead of three
31
32The ``ara-server``, ``ara-plugins`` and ``ara-clients`` projects have been
33merged into a single repository and you'll be able to find them in the
34[feature/1.0 branch](https://github.com/openstack/ara/tree/feature/1.0) of the
35main ARA repository.
36
37This means less burden for contributors and maintainers, for example:
38
39- We're managing a single repository instead of three
40- We no longer need to manage dependencies between the three projects
41- We have one project to test, tag, release and contribute to
42- Tests and CI no longer need to account for the projects being separated
43
44By removing this overhead, the project becomes simpler to maintain which
45frees up time to do other things.
46
47For users, this means that there's only a single package with everything
48included on PyPi instead of three and 1.0 is already lightweight in terms of
49dependencies when compared to 0.x.
50
51[ara-web](https://github.com/openstack/ara-web) will remain a standalone project
52that provides a javascript web client to the API.
53
54[ara-infra](https://github.com/openstack/ara-infra) will also remain since it's
55for managing the infrastructure for the project -- including this blog post and
56the Ansible playbooks to deploy it !
57
58## Two built-in Ansible roles
59
60ARA 1.0 will ship with two built-in Ansible roles:
61
62- [ansible-role-ara-api](https://ara.readthedocs.io/en/feature-1.0/ansible-role-ara-api.html)
63- [ansible-role-ara-web](https://ara.readthedocs.io/en/feature-1.0/ansible-role-ara-web.html)
64
65These roles work are already in use to deploy
66[api.demo.recordsansible.org](https://api.demo.recordsansible.org) as
67well as [web.demo.recordsansible.org](https://web.demo.recordsansible.org) from
68playbooks in [ara-infra](https://github.com/openstack/ara-infra/commit/a797094b61d3dd5f7ccb25849499489ed40cafea).
69
70These roles are rough around the edges right now but they will evolve over
71time to provide a framework for integration testing different ways of deploying
72the new ARA API server as well as the web client interface.
73
74# Beta ?
75
76There's still some work to do before moving forward with what we'd call a beta.
77
78For example, we need to iterate on [ara-web](https://github.com/openstack/ara-web)
79and make sure the API is able to give it the information it needs.
80
81Also, while the API and the API clients are nearing completion, we currently do
82not yet have a CLI client which would allow users to query the API easily from
83the command line (ex: ``ara playbook list``).
84
85There's other things but I think those are definitely the ones that stand out
86the most right now.
87
88## In the meantime...
89
90If you would like to contribute code, feedback, documentation or help test the
91alpha milestones with us, please reach out !
92
93Find us on [#ara](http://webchat.freenode.net/?channels=%23ara) on the freenode IRC
94network and on [Slack](https://join.slack.com/t/arecordsansible/shared_invite/enQtMjMxNzI4ODAxMDQxLWU4MmZhZTI4ZjRjOTUwZTM2MzM3MzcwNDU1YzFmNzRlMzI0NTUzNDY1MWJlNThhM2I4ZTViZjUwZTRkNTBiM2I).