Browse Source

Add blog post for alpha3 milestone

Change-Id: I784cd298dde55df9bb40158832a2351a2a03f406
changes/79/642579/1
David Moreau Simard 3 months ago
parent
commit
5c226dbea2
No account linked to committer's email address

BIN
website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/changelog.png View File


+ 94
- 0
website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/index.md View File

@@ -0,0 +1,94 @@
1
+---
2
+author: "David Moreau Simard"
3
+categories:
4
+  - development
5
+tags:
6
+  - ansible
7
+date: 2019-03-11
8
+title: "ARA 1.0 alpha3: back to basics"
9
+slug: ara-1.0-alpha3-back-to-basics
10
+type: post
11
+---
12
+
13
+The release of ARA 1.0 draws closer with a third alpha milestone !
14
+
15
+![changelog](changelog.png)
16
+
17
+If there was a theme for this milestone it would be "back to basics".
18
+
19
+In the previous [blog post](https://ara.recordsansible.org/blog/2019/01/16/introducing-new-projects-for-the-upcoming-1.0-release/),
20
+I 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
+
23
+As a user, developer and maintainer of these projects myself, I realized that
24
+the added complexity of keeping the projects separated did not provide enough
25
+value to be worth it.
26
+
27
+Things had to be simple because simplicity is a feature in ARA and failing to
28
+be 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
+
32
+The ``ara-server``, ``ara-plugins`` and ``ara-clients`` projects have been
33
+merged 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
35
+main ARA repository.
36
+
37
+This 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
+
44
+By removing this overhead, the project becomes simpler to maintain which
45
+frees up time to do other things.
46
+
47
+For users, this means that there's only a single package with everything
48
+included on PyPi instead of three and 1.0 is already lightweight in terms of
49
+dependencies when compared to 0.x.
50
+
51
+[ara-web](https://github.com/openstack/ara-web) will remain a standalone project
52
+that provides a javascript web client to the API.
53
+
54
+[ara-infra](https://github.com/openstack/ara-infra) will also remain since it's
55
+for managing the infrastructure for the project -- including this blog post and
56
+the Ansible playbooks to deploy it !
57
+
58
+## Two built-in Ansible roles
59
+
60
+ARA 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
+
65
+These roles work are already in use to deploy
66
+[api.demo.recordsansible.org](https://api.demo.recordsansible.org) as
67
+well as [web.demo.recordsansible.org](https://web.demo.recordsansible.org) from
68
+playbooks in [ara-infra](https://github.com/openstack/ara-infra/commit/a797094b61d3dd5f7ccb25849499489ed40cafea).
69
+
70
+These roles are rough around the edges right now but they will evolve over
71
+time to provide a framework for integration testing different ways of deploying
72
+the new ARA API server as well as the web client interface.
73
+
74
+# Beta ?
75
+
76
+There's still some work to do before moving forward with what we'd call a beta.
77
+
78
+For example, we need to iterate on [ara-web](https://github.com/openstack/ara-web)
79
+and make sure the API is able to give it the information it needs.
80
+
81
+Also, while the API and the API clients are nearing completion, we currently do
82
+not yet have a CLI client which would allow users to query the API easily from
83
+the command line (ex: ``ara playbook list``).
84
+
85
+There's other things but I think those are definitely the ones that stand out
86
+the most right now.
87
+
88
+## In the meantime...
89
+
90
+If you would like to contribute code, feedback, documentation or help test the
91
+alpha milestones with us, please reach out !
92
+
93
+Find us on [#ara](http://webchat.freenode.net/?channels=%23ara) on the freenode IRC
94
+network and on [Slack](https://join.slack.com/t/arecordsansible/shared_invite/enQtMjMxNzI4ODAxMDQxLWU4MmZhZTI4ZjRjOTUwZTM2MzM3MzcwNDU1YzFmNzRlMzI0NTUzNDY1MWJlNThhM2I4ZTViZjUwZTRkNTBiM2I).

Loading…
Cancel
Save