Browse Source

opendev: Remove content and leave an URL to the GitHub repository

Change-Id: Ic78075a42fc93684c21881d9388229a7085c8912
changes/68/777668/1
David Moreau Simard 9 months ago
parent
commit
da6fef5713
No known key found for this signature in database GPG Key ID: 7D4729EC4E64E8B7
  1. 1
      .gitignore
  2. 674
      LICENSE
  3. 43
      README.rst
  4. 10
      playbooks/ansible.cfg
  5. 1
      playbooks/hosts
  6. 26
      playbooks/live-demo.yaml
  7. 1
      playbooks/roles
  8. 46
      playbooks/templates/api.demo.recordsansible.org.conf.j2
  9. 46
      playbooks/templates/web.demo.recordsansible.org.conf.j2
  10. 7
      playbooks/website.yaml
  11. 22
      roles/website/defaults/main.yaml
  12. 52
      roles/website/files/ara.recordsansible.org.conf
  13. 23
      roles/website/handlers/main.yaml
  14. 81
      roles/website/tasks/hugo.yaml
  15. 42
      roles/website/tasks/main.yaml
  16. 43
      roles/website/tasks/nginx.yaml
  17. 16
      roles/website/templates/hugo.service.j2
  18. 42
      tests/website-post.yaml
  19. 53
      tests/website-pre.yaml
  20. 25
      website/README.rst
  21. 96
      website/config.toml
  22. 144
      website/content/_index.md
  23. 182
      website/content/blog/2016-05-21_an-idea-to-store-browse-and-troubleshoot-ansible-playbook-runs/index.md
  24. 103
      website/content/blog/2016-06-07_ara-one-month-and-200-commits-later/index.md
  25. 92
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/index.md
  26. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-1.png
  27. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-2.png
  28. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-failed.png
  29. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-file.png
  30. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-gate.png
  31. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-logs.png
  32. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-playbook.png
  33. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-task.png
  34. BIN
      website/content/blog/2016-11-09_visualizing-kolla-ansible-playbooks-with-ara/kolla-webapp.png
  35. 98
      website/content/blog/2016-12-01_0.10-the-biggest-release-yet-is-out/index.md
  36. BIN
      website/content/blog/2017-02-13_announcing-the-release-of-0.11/ara-with-icon.png
  37. BIN
      website/content/blog/2017-02-13_announcing-the-release-of-0.11/ara.png
  38. 113
      website/content/blog/2017-02-13_announcing-the-release-of-0.11/index.md
  39. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/facts.png
  40. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/file.png
  41. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/home.png
  42. 146
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/index.md
  43. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/reports.png
  44. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/result.png
  45. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/search.png
  46. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/sort.png
  47. BIN
      website/content/blog/2017-03-12_an-even-better-ansible-reporting-interface-with-ara-0-12/summary.png
  48. 148
      website/content/blog/2017-05-05_ara-0-13-is-out-and-its-awesome/index.md
  49. BIN
      website/content/blog/2017-05-05_ara-0-13-is-out-and-its-awesome/new-file-tab.png
  50. BIN
      website/content/blog/2017-05-05_ara-0-13-is-out-and-its-awesome/parameters.png
  51. BIN
      website/content/blog/2017-05-05_ara-0-13-is-out-and-its-awesome/permalinks.png
  52. BIN
      website/content/blog/2017-05-05_ara-0-13-is-out-and-its-awesome/tags.png
  53. BIN
      website/content/blog/2017-05-08_ara-is-one-year-old-a-look-back-at-the-past-year/ara-with-icon.png
  54. BIN
      website/content/blog/2017-05-08_ara-is-one-year-old-a-look-back-at-the-past-year/ara.png
  55. BIN
      website/content/blog/2017-05-08_ara-is-one-year-old-a-look-back-at-the-past-year/first-commit.png
  56. 255
      website/content/blog/2017-05-08_ara-is-one-year-old-a-look-back-at-the-past-year/index.md
  57. 240
      website/content/blog/2017-08-16_whats-coming-in-ara-1.0/index.md
  58. 63
      website/content/blog/2017-08-27_new-ways-of-reaching-the-ara-community/index.md
  59. BIN
      website/content/blog/2017-11-22_status-update-ara-1.0/1.0-diff.png
  60. BIN
      website/content/blog/2017-11-22_status-update-ara-1.0/1.0-files.png
  61. BIN
      website/content/blog/2017-11-22_status-update-ara-1.0/db-layout-0.x.png
  62. BIN
      website/content/blog/2017-11-22_status-update-ara-1.0/db-layout-1.x.png
  63. BIN
      website/content/blog/2017-11-22_status-update-ara-1.0/git-network.png
  64. 394
      website/content/blog/2017-11-22_status-update-ara-1.0/index.md
  65. BIN
      website/content/blog/2017-11-22_status-update-ara-1.0/slack-notification.png
  66. BIN
      website/content/blog/2018-02-23_rebranding-ansible-run-analysis-to-ara-records-ansible/ara-reports.png
  67. BIN
      website/content/blog/2018-02-23_rebranding-ansible-run-analysis-to-ara-records-ansible/gnu-is-not-unix.png
  68. 100
      website/content/blog/2018-02-23_rebranding-ansible-run-analysis-to-ara-records-ansible/index.md
  69. 118
      website/content/blog/2018-04-09_scaling-ara-to-a-million-ansible-playbooks-a-month/index.md
  70. BIN
      website/content/blog/2018-04-09_scaling-ara-to-a-million-ansible-playbooks-a-month/zuul-ci.png
  71. BIN
      website/content/blog/2018-04-09_scaling-ara-to-a-million-ansible-playbooks-a-month/zuul-pipelines.png
  72. 90
      website/content/blog/2018-05-03_ara-records-ansible-0.15-has-been-released/index.md
  73. BIN
      website/content/blog/2018-10-08_ansiblefest-2018-community-project-highlights/community-projects-ansiblefest.jpg
  74. 120
      website/content/blog/2018-10-08_ansiblefest-2018-community-project-highlights/index.md
  75. 86
      website/content/blog/2019-11-06_announcing-the-release-of-ara-1.2/index.md
  76. BIN
      website/content/blog/2019-11-06_announcing-the-release-of-ara-1.2/new-built-in.png
  77. BIN
      website/content/blog/2019-11-06_announcing-the-release-of-ara-1.2/search.png
  78. 51
      website/content/blog/2019-11-18_ara-0.16-maintenance-release-and-eventual-end-of-life/index.md
  79. 57
      website/content/blog/2019-11-22_ara-is-now-packaged-for-fedora/index.md
  80. 90
      website/content/blog/2019-12-03_announcing-the-release-of-ara-1.3/index.md
  81. BIN
      website/content/blog/2019-12-03_announcing-the-release-of-ara-1.3/playbook-search.png
  82. BIN
      website/content/blog/2019-12-31_2019-in-restrospective-for-ara-records-ansible/1.0-diff.png
  83. BIN
      website/content/blog/2019-12-31_2019-in-restrospective-for-ara-records-ansible/1.0-release.png
  84. BIN
      website/content/blog/2019-12-31_2019-in-restrospective-for-ara-records-ansible/1.1-release.png
  85. 174
      website/content/blog/2019-12-31_2019-in-restrospective-for-ara-records-ansible/index.md
  86. BIN
      website/content/blog/2019-12-31_2019-in-restrospective-for-ara-records-ansible/new-built-in.png
  87. BIN
      website/content/blog/2019-12-31_2019-in-restrospective-for-ara-records-ansible/playbook-search.png
  88. 235
      website/content/blog/2019_01_16_introducing-new-projects-for-the-upcoming-1.0-release/index.md
  89. BIN
      website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/changelog.png
  90. 94
      website/content/blog/2019_03_11_ara-1.0-alpha3-back-to-basics/index.md
  91. 149
      website/content/blog/2019_05_16_1.0-beta-help-wanted/index.md
  92. BIN
      website/content/blog/2019_05_16_1.0-beta-help-wanted/live-demo-playbook.png
  93. 89
      website/content/blog/2019_06_04-announcing-the-release-of-ara-1.0/index.md
  94. BIN
      website/content/blog/2019_06_04-announcing-the-release-of-ara-1.0/live-demo-playbook.png
  95. 45
      website/content/blog/2020-04-14-ara-0.16.7-and-end-of-life-for-0.x/index.md
  96. BIN
      website/content/blog/2020-04-15-announcing-the-upcoming-release-of-ara-1.4.0/host_search.png
  97. 189
      website/content/blog/2020-04-15-announcing-the-upcoming-release-of-ara-1.4.0/index.md
  98. BIN
      website/content/blog/2020-04-15-announcing-the-upcoming-release-of-ara-1.4.0/task_search.png
  99. BIN
      website/content/blog/2020-04-15-announcing-the-upcoming-release-of-ara-1.4.0/ui_index.png
  100. BIN
      website/content/blog/2020-09-23-announcing-the-release-of-ara-1.5.0/host_search.png

1
.gitignore

@ -1 +0,0 @@
*.retry

674
LICENSE

@ -1,674 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<http://www.gnu.org/philosophy/why-not-lgpl.html>.

43
README.rst

@ -1,41 +1,4 @@
ara-infra
=========
This project has been moved
---------------------------
``ara-infra`` is a collection of playbooks, roles, tests, scripts, tools and
documentation helpful in the context of managing the CI/CD of ARA itself.
It is meant to do things like:
- Deploy the infrastructure server, ``infra.recordsansible.org``
- Deploy the website `ara.recordsansible.org <https://ara.recordsansible.org>`_
- Deploy `teamchat <https://github.com/dmsimard/teamchat>`_ for bridging ARA's Slack and IRC communities
- Carry common integration tests between the different ARA projects
If you're looking to use ARA Records Ansible for reporting on your playbooks,
the ARA documentation is available on `ara.readthedocs.io <https://ara.readthedocs.io/>`_.
Contributors
============
See contributors on GitHub_.
.. _GitHub: https://github.com/ansible-community/ara-infra/graphs/contributors
Copyright
=========
::
Copyright (c) 2018 Red Hat, Inc.
ARA is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
ARA is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with ARA. If not, see <http://www.gnu.org/licenses/>.
This project's code and code review is now on GitHub: https://github.com/ansible-community/ara-infra

10
playbooks/ansible.cfg

@ -1,10 +0,0 @@
[defaults]
forks = 25
gathering = smart
fact_caching = jsonfile
fact_caching_connection = /tmp/
fact_caching_timeout = 3600
inventory = hosts
[ssh_connection]
pipelining = True

1
playbooks/hosts

@ -1 +0,0 @@
demo.recordsansible.org ansible_host=139.178.83.37 ansible_user=fedora ansible_python_interpreter=/usr/bin/python3

26
playbooks/live-demo.yaml

@ -1,26 +0,0 @@
- name: Provision demo.recordsansible.org
hosts: demo.recordsansible.org
gather_facts: yes
vars:
# ara_api
ara_api_write_login_required: true
ara_api_fqdn: api.demo.recordsansible.org
ara_api_frontend_server: nginx
ara_api_frontend_vhost: api.demo.recordsansible.org.conf.j2
ara_api_wsgi_server: gunicorn
ara_api_allowed_hosts:
- api.demo.recordsansible.org
# TODO: Figure out if it's possible to set ara-web to use demo from localhost:3000
ara_api_cors_origin_allow_all: true
ara_api_cors_origin_whitelist:
- https://web.demo.recordsansible.org
- http://logs.openstack.org
- http://localhost:3000
# ara_web
ara_web_fqdn: web.demo.recordsansible.org
ara_web_api_endpoint: "https://api.demo.recordsansible.org"
ara_web_frontend_server: nginx
ara_web_frontend_vhost: web.demo.recordsansible.org.conf.j2
roles:
- ara_api
- ara_web

1
playbooks/roles

@ -1 +0,0 @@
../roles

46
playbooks/templates/api.demo.recordsansible.org.conf.j2

@ -1,46 +0,0 @@
upstream ara_api {
# fail_timeout=0 means we always retry an upstream even if it failed
# to return a good HTTP response
server {{ ara_api_wsgi_bind }} fail_timeout=0;
}
server {
listen 80;
server_name {{ ara_api_fqdn }};
return 301 https://{{ ara_api_fqdn }}$request_uri;
}
server {
listen 443;
server_name {{ ara_api_fqdn }};
access_log /var/log/nginx/{{ ara_api_fqdn }}_access.log;
error_log /var/log/nginx/{{ ara_api_fqdn }}_error.log;
ssl on;
ssl_certificate /etc/letsencrypt/live/{{ ara_api_fqdn }}/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/{{ ara_api_fqdn }}/privkey.pem;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
location /static {
expires 7d;
add_header Cache-Control "public";
}
# Everything, including static files, is served by the backend
location ~ {
# checks if the file exists, if not found proxy to app
try_files $uri @proxy_to_app;
}
location @proxy_to_app {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass http://ara_api;
}
}

46
playbooks/templates/web.demo.recordsansible.org.conf.j2

@ -1,46 +0,0 @@
{% if ara_web_dev_server %}
upstream ara_web {
# fail_timeout=0 means we always retry an upstream even if it failed
# to return a good HTTP response
server {{ ara_web_dev_server_bind_address }}:{{ ara_web_dev_server_bind_port }} fail_timeout=0;
}
{% endif %}
server {
listen 80;
server_name {{ ara_web_fqdn }};
return 301 https://{{ ara_web_fqdn }}$request_uri;
}
server {
listen 443;
server_name {{ ara_web_fqdn }};
root {{ ara_web_static_dir }};
access_log /var/log/nginx/{{ ara_web_fqdn }}_access.log;
error_log /var/log/nginx/{{ ara_web_fqdn }}_error.log;
ssl on;
ssl_certificate /etc/letsencrypt/live/{{ ara_web_fqdn }}/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/{{ ara_web_fqdn }}/privkey.pem;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
{% if ara_web_dev_server %}
location ~ {
# checks for static file, if not found proxy to server
try_files $uri @proxy_to_app;
}
location @proxy_to_app {
# Redefine the header fields that NGINX sends to the upstream server
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# Define the location of the proxy server to send the request to
proxy_pass http://ara_web;
}
{% endif %}
}

7
playbooks/website.yaml

@ -1,7 +0,0 @@
- name: Set up the ara.recordsansible.org website
hosts: ara.recordsansible.org
gather_facts: yes
tasks:
- name: Include the website role
include_role:
name: website

22
roles/website/defaults/main.yaml

@ -1,22 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
hugo_release: https://github.com/gohugoio/hugo/releases/download/v0.51/hugo_0.51_Linux-64bit.tar.gz
hugo_directory: /opt/hugo
hugo_theme: https://github.com/jpescador/hugo-future-imperfect
hugo_theme_directory: "{{ hugo_directory }}/themes/hugo-future-imperfect"

52
roles/website/files/ara.recordsansible.org.conf

@ -1,52 +0,0 @@
upstream hugo {
server 127.0.0.1:1313;
}
server {
listen 80;
server_name www.getara.org getara.org www.recordsansible.org ara.recordsansible.org;
return 301 https://ara.recordsansible.org$request_uri;
}
server {
listen 443;
server_name ara.recordsansible.org;
ssl on;
ssl_certificate /etc/letsencrypt/live/ara.recordsansible.org/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/ara.recordsansible.org/privkey.pem;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
access_log /var/log/nginx/ara.recordsansible.org_access.log;
error_log /var/log/nginx/ara.recordsansible.org_error.log;
# Media: images, icons, video, audio, HTC
location ~* \.(?:jpg|jpeg|gif|png|ico|cur|gz|svg|mp4|ogg|ogv|webm|htc)$ {
access_log off;
add_header Cache-Control "max-age=2592000";
}
# CSS and Javascript
location ~* \.(?:css|js)$ {
add_header Cache-Control "max-age=2592000";
access_log off;
}
location ^~ {
# checks for static file, if not found proxy to server
try_files $uri @proxy_to_server;
}
location @proxy_to_server {
# Redefine the header fields that NGINX sends to the upstream server
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# Define the location of the proxy server to send the request to
proxy_pass http://hugo;
}
}

23
roles/website/handlers/main.yaml

@ -1,23 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
- name: Restart nginx
become: yes
service:
name: nginx
state: restarted

81
roles/website/tasks/hugo.yaml

@ -1,81 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
- become: yes
block:
- name: Install git
package:
name: git
state: present
- name: Create user for Hugo
become: true
user:
name: hugo
comment: User for Hugo
shell: /sbin/nologin
home: "{{ hugo_directory }}"
- name: Download Hugo release tarball
get_url:
url: "{{ hugo_release }}"
dest: "{{ hugo_directory }}"
register: hugo_download
- name: Extract Hugo release tarball
unarchive:
src: "{{ hugo_download.dest }}"
dest: "{{ hugo_directory }}"
remote_src: yes
when: hugo_download is changed
- name: Symlink Hugo in PATH
file:
src: "{{ hugo_directory }}/hugo"
dest: /usr/local/bin/hugo
owner: hugo
group: hugo
state: link
- name: Clone Hugo theme
become_user: hugo
git:
repo: "{{ hugo_theme }}"
dest: "{{ hugo_theme_directory }}"
force: yes
update: yes
- name: Configure Hugo server systemd service
template:
src: hugo.service.j2
dest: /etc/systemd/system/hugo.service
owner: root
group: root
mode: 0644
register: hugo_systemd
- when: hugo_systemd is changed
block:
- name: Reload systemctl
systemd:
daemon_reload: yes
- name: Restart Hugo
service:
name: hugo
state: restarted

42
roles/website/tasks/main.yaml

@ -1,42 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
# Zuul already prepares the src repository on the remote node and
# Zuul doesn't let you run pipe lookups on executors for security purposes
- name: Symlink ara-infra to persistent location with Zuul
become: yes
file:
src: "{{ ansible_user_dir }}/{{ zuul.project.src_dir }}"
dest: /opt/ara-infra
state: link
when: zuul is defined
# git rev-parse --show-toplevel returns the root git directory
- name: Copy ara-infra to persistent location
become: yes
synchronize:
src: "{{ lookup('pipe', 'git rev-parse --show-toplevel') }}"
dest: /opt/
delete: yes
when: zuul is not defined
- name: Set up Hugo
include_tasks: hugo.yaml
- name: Set up nginx
include_tasks: nginx.yaml

43
roles/website/tasks/nginx.yaml

@ -1,43 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
- become: yes
block:
- name: Install nginx
package:
name: nginx
state: present
- name: Set selinux boolean to allow nginx to reverse proxy
seboolean:
name: httpd_can_network_connect
state: yes
persistent: yes
- name: Set up nginx vhost
copy:
src: ara.recordsansible.org.conf
dest: /etc/nginx/conf.d/ara.recordsansible.org.conf
notify:
- Restart nginx
- name: Start and enable nginx
service:
name: nginx
state: started
enabled: yes

16
roles/website/templates/hugo.service.j2

@ -1,16 +0,0 @@
[Unit]
Description=Hugo internal server
After=network.target
[Service]
User=hugo
Group=hugo
Type=simple
ExecStart=/usr/local/bin/hugo server --source /opt/ara-infra/website --themesDir {{ hugo_directory }}/themes --baseURL "https://ara.recordsansible.org/" --appendPort=false
ProtectSystem=yes
ProtectHome=no
NoNewPrivileges=yes
PrivateTmp=yes
[Install]
WantedBy=multi-user.target

42
tests/website-post.yaml

@ -1,42 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
- name: Website post-run
hosts: ara.recordsansible.org
gather_facts: yes
tasks:
- name: Create artifact directories
file:
path: "{{ ansible_user_dir }}/workspace/logs/build"
state: directory
recurse: yes
- name: Generate static version of the website
become: yes
command: |
/usr/local/bin/hugo \
--source /opt/ara-infra/website \
--themesDir /opt/hugo/themes \
--destination {{ ansible_user_dir }}/workspace/logs/build
- name: Upload log artifacts
synchronize:
src: "{{ ansible_user_dir }}/workspace/logs"
dest: "{{ zuul.executor.log_root }}"
mode: pull
verify_host: true

53
tests/website-pre.yaml

@ -1,53 +0,0 @@
---
# Copyright (c) 2018 Red Hat, Inc.
#
# This file is part of ARA Records Ansible.
#
# ARA is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# ARA is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with ARA. If not, see <http://www.gnu.org/licenses/>.
- name: Website pre-run
hosts: ara.recordsansible.org
vars:
domain: ara.recordsansible.org
ansible_python_interpreter: /usr/bin/python3
tasks:
- become: true
block:
- name: Install python3-pyOpenSSL
package:
name: python3-pyOpenSSL
state: present
- name: Create expected letsencrypt directories
file:
path: "/etc/letsencrypt/live/{{ domain }}"
state: directory
recurse: yes
- name: Generate an OpenSSL private key
openssl_privatekey:
path: "/etc/letsencrypt/live/{{ domain }}/privkey.pem"
- name: Generate an OpenSSL CSR
openssl_csr:
path: /etc/letsencrypt/live/{{ domain }}/request.csr
privatekey_path: "/etc/letsencrypt/live/{{ domain }}/privkey.pem"
common_name: "{{ domain }}"
- name: Generate a self signed SSL certificate
openssl_certificate:
path: "/etc/letsencrypt/live/{{ domain }}/fullchain.pem"
privatekey_path: "/etc/letsencrypt/live/{{ domain }}/privkey.pem"
csr_path: /etc/letsencrypt/live/{{ domain }}/request.csr
provider: selfsigned

25
website/README.rst

@ -1,25 +0,0 @@
ARA's website
=============
Hosted at `ara.recordsansible.org <https://ara.recordsansible.org>`_, the
website is built with `Hugo <https://gohugo.io/>`_ and installed with the
``website`` role from this project's repository.
The website uses the Hugo theme called `future-imperfect <https://themes.gohugo.io/future-imperfect/>`_
and it must be checked out as part of building the site.
Development
-----------
Clone repositories::
# This repo
git clone https://git.openstack.org/openstack/ara-infra /opt/ara-infra
# The Hugo theme (future-imperfect)
git clone https://github.com/jpescador/hugo-future-imperfect /opt/hugo/themes/hugo-future-imperfect
Install Hugo following instructions from their `documentation <https://gohugo.io/getting-started/installing/>`_.
Run Hugo's standalone server::
hugo server --source /opt/ara-infra/website --themesDir /opt/hugo/themes

96
website/config.toml

@ -1,96 +0,0 @@
# https://gohugo.io/getting-started/configuration/
languageCode = "en-us"
title = "ARA Records Ansible | ara.recordsansible.org"
theme = "hugo-future-imperfect"
preserveTaxonomyNames = true
paginate = 10
pluralizeListTitles = false
enableRobotsTXT = true
enableGitInfo = true
relativeURLs = true
[params]
categoriesByCount = true
cssFiles = ["default"]
description = "ARA Records Ansible and makes it easier to understand and troubleshoot."
dynamicTitles = false
enableCDN = false
faviconVersion = ""
hideEmptyStats = false
highlightjsLang = ["bash", "python", "yaml"]
highlightjsTheme = "github"
highlightjs = true
imageStretch = ""
jsFiles = ["default"]
loadFavicon = true
navbarTitle = "ARA Records Ansible"
readingTime = true
removeBlur = false
rssAppearAtBottom = true
rssAppearAtTop = true
showSidebarCategories = true
socialShare = []
viewMorePostsLink = "/blog/"
[permalinks]
blog = "/blog/:year/:month/:day/:slug/"
[params.intro]
paragraph = "Records Ansible and makes it easier to understand and troubleshoot."
[params.intro.pic]
src = "static/logo.png"
circle = false
imperfect = false
width = ""
alt = "ara.recordsansible.org"
# https://discourse.gohugo.io/t/raw-html-getting-omitted-in-0-60-0/22032
[markup.goldmark.renderer]
unsafe = true
[params.postAmount]
# Sets the number of recent posts to show in the sidebar. The default value is 5.
sidebar = 8
# Sets the menu items in the navigation bar
# Identifier prepends a Font Awesome icon to the menu item
[[menu.main]]
name = "About"
url = "/"
identifier = "fa fa-question-circle"
weight = 1
[[menu.main]]
name = "Blog"
url = "/blog/"
identifier = "fa fa-newspaper-o"
weight = 2
[[menu.main]]
name = "Code"
url = "https://github.com/ansible-community/ara"
identifier = "fa fa-github"
weight = 3
[[menu.main]]
name = "Documentation"
url = "https://ara.readthedocs.io"
identifier = "fa fa-book"
weight = 4
[[menu.main]]
name = "Demo"
url = "https://demo.recordsansible.org"
identifier = "fa fa-external-link"
weight = 5
[[menu.main]]
name = "Community & Help"
url = "/community"
identifier = "fa fa-users"
weight = 6
[social]
github = "ansible-community/?q=ara"
twitter = "RecordsAnsible"

144
website/content/_index.md

@ -1,144 +0,0 @@
---
kind: home
---
ARA Records Ansible and makes it easier to understand and troubleshoot.
It's another recursive acronym.
![ara-full-logo](/static/ara-full-logo.png)
## What it does
Simple to install and get started, ara provides reporting by saving detailed and
granular results of ``ansible`` and ``ansible-playbook`` commands wherever you run them:
- by hand or from a script
- from a laptop, a desktop, a container or a server
- for development, CI or production
- from a linux distribution or even on OS X (as long as you have ``python >= 3.5``)
- from tools such as AWX or Tower, Jenkins, GitLab CI, Rundeck, Zuul, Molecule, ansible-pull, ansible-test or ansible-runner
By default, ara's Ansible callback plugin will record data to a local sqlite
database without requiring you to run a server or a service:
![quickstart-default](/static/ara-quickstart-default.gif)
ara can also provide a single pane of glass when recording data from multiple
locations by pointing the callback plugin to a running API server:
![quickstart-server](/static/ara-quickstart-server.gif)
The data is then made available for browsing, searching and querying over the
included reporting interface, a CLI client as well as a REST API.
## How it works
ARA Records Ansible execution results to sqlite, mysql or postgresql databases
by using an [Ansible callback plugin](https://docs.ansible.com/ansible/latest/plugins/callback.html).
This callback plugin leverages built-in python API clients to send data to a
REST API server:
![recording-workflow](/static/recording-workflow.png)
## What it looks like
### API browser
Included by the API server with django-rest-framework, the API browser allows
users to navigate the different API endpoints and query recorded data.
![ui-api-browser](/static/ui-api-browser.png)
### Reporting interface
A simple reporting interface built-in to the API server without any extra dependencies.
![ui-playbook-details](/static/ui-playbook-details.png)
### ara CLI
A built-in CLI client for querying and managing playbooks and their recorded data.
![cli-playbook-list](/static/cli-playbook-list.png)
The full list of commands, their arguments as well as examples can be found in
the [CLI documentation](https://ara.readthedocs.io/en/latest/cli.html#cli-ara-api-client).
## Getting started
### Requirements
- Any recent Linux distribution or Mac OS with python >=3.5 available
- The ara Ansible plugins must be installed for the same python interpreter as Ansible itself
For RHEL 7 and CentOS 7 it is recommended to run the API server in a container due to missing or outdated dependencies.
See this [issue](https://github.com/ansible-community/ara/issues/99) for more information.
### Recording playbooks without an API server
With defaults and using a local sqlite database:
```bash
# Install Ansible and ARA (with API server dependencies) for the current user
python3 -m pip install --user ansible "ara[server]"
# Configure Ansible to use the ARA callback plugin
export ANSIBLE_CALLBACK_PLUGINS="$(python3 -m ara.setup.callback_plugins)"
# Run an Ansible playbook
ansible-playbook playbook.yaml
# Use the CLI to see recorded playbooks
ara playbook list
# Start the built-in development server to browse recorded results
ara-manage runserver
```
### Recording playbooks with an API server
You can get an API server deployed using the [ara Ansible collection](https://github.com/ansible-community/ara-collection)
or get started quickly using the container images from [DockerHub](https://hub.docker.com/r/recordsansible/ara-api) and
[quay.io](https://quay.io/repository/recordsansible/ara-api):
```bash
# Create a directory for a volume to store settings and a sqlite database
mkdir -p ~/.ara/server
# Start an API server with podman from the image on DockerHub:
podman run --name api-server --detach --tty \
--volume ~/.ara/server:/opt/ara:z -p 8000:8000 \
docker.io/recordsansible/ara-api:latest
# or with docker from the image on quay.io:
docker run --name api-server --detach --tty \
--volume ~/.ara/server:/opt/ara:z -p 8000:8000 \
quay.io/recordsansible/ara-api:latest
```
Once the server is running, ara's Ansible callback plugin must be installed and configured to send data to it:
```bash
# Install Ansible and ARA (without API server dependencies) for the current user
python3 -m pip install --user ansible ara
# Configure Ansible to use the ARA callback plugin
export ANSIBLE_CALLBACK_PLUGINS="$(python3 -m ara.setup.callback_plugins)"
# Set up the ARA callback to know where the API server is located
export ARA_API_CLIENT="http"
export ARA_API_SERVER="http://127.0.0.1:8000"
# Run an Ansible playbook
ansible-playbook playbook.yaml
# Use the CLI to see recorded playbooks
ara playbook list
```
Data will be available on the API server in real time as the playbook progresses and completes.
You can read more about how container images are built and how to run them in the
[documentation](https://ara.readthedocs.io/en/latest/container-images.html).

182
website/content/blog/2016-05-21_an-idea-to-store-browse-and-troubleshoot-ansible-playbook-runs/index.md

@ -1,182 +0,0 @@
---
author: "David Moreau Simard"
categories:
- development
tags:
- ansible
- openstack
date: 2016-05-21
title: "ARA: An idea to store, browse and troubleshoot Ansible Playbook runs"
slug: an-idea-to-store-browse-and-troubleshoot-ansible-playbook-runs
type: post
---
# The context
[Ansible](https://www.ansible.com/) can be used for a lot of things and it's
grown pretty popular for managing servers and their configuration.
In the [RDO](https://www.rdoproject.org/) and
[OpenStack](https://www.openstack.org/) communities, Ansible is heavily used to
deploy or test OpenStack through Continuous Integration (CI). Projects like
[TripleO-Quickstart](https://github.com/openstack/tripleo-quickstart),
[WeIRDO](https://github.com/redhat-openstack/weirdo),
[OpenStack-Ansible](https://github.com/openstack/openstack-ansible) or
[Zuul v3](https://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html#ansible)
are completely driven by Ansible.
In the world of automated continuous integration, it's not uncommon to have
hundreds, if not thousands of jobs running every day for testing, building,
compiling, deploying and so on.
Keeping up with a large amount of Ansible runs and their outcome, not
just in the context of CI, is challenging.
# The idea
[ARA](https://github.com/dmsimard/ara) is an idea I came up with to try
and make Ansible runs easier to visualize, understand and troubleshoot.
ARA is three things:
1. An [Ansible callback plugin](https://ara.readthedocs.io/en/latest/configuration.html#ansible) to record playbook runs into a local or remote database
2. A [CLI client](https://ara.readthedocs.io/en/latest/usage.html#querying-the-database-with-the-cli) to query the database
3. A [web interface](https://ara.readthedocs.io/en/latest/faq.html#what-does-the-web-interface-look-like) to visualize the database
ARA organizes recorded playbook data in a way to make it intuitive for you to
search and find what you're interested for as fast and as easily as possible.
It provides summaries of task results per host or per playbook.
It allows you to filter task results by playbook, play, host, task or by the
status of the task.
With ARA, you're able to easily drill down from the summary view for the results
you're interested in, whether it's a particular host or a specific task.
Beyond browsing a single ansible-playbook run, ARA supports recording and
viewing multiple runs in the same database.
This allows you to, for example, recognize patterns (ex: this particular host
is always failing this particular task) since you have access to data from
multiple runs.
ARA is an open source project available on [Github](https://github.com/dmsimard/ara) under the Apache v2 license.
[Documentation](https://ara.readthedocs.io/en/latest/) and
[frequently asked questions](https://ara.readthedocs.io/en/latest/faq.html) are available on readthedocs.io.
# Why ?
As I mentioned before, the vast majority of the RDO CI is powered by Ansible.
When a job build fails, I have to look at one of these Jenkins
[console logs](https://dmsimard.com/files/ansible-jenkins.txt) that's >8000
lines long. If it doesn't crash my browser, I get to dig across the large
amount of output to try and figure out what went wrong in the job build.
When you're testing OpenStack trunk, you're going to be troubleshooting a *lot*
of those large failed jobs and it's painful.
Over time, I've (*unfortunately*) gotten used to it and got pretty good, actually.
However, it still takes me a non negligible amount of time just to find where
Ansible failed to know where to start searching for in the logs.
It's also definitely a nightmare when someone else wants to look at the jobs
to try and understand what happened.
ARA solves that painpoint - and many others - by making it easier to
browse the results of a playbook.
### Other attempts
To try and help us before ARA was born, we leveraged two callbacks to
try and help us parse the Ansible Playbook output.
The first is [human_log.py](https://gist.github.com/cliffano/9868180) which
helps pretty-printing output from tasks like "command" or "yum".
We also have [profile_tasks](https://github.com/jlafon/ansible-profile/blob/master/callback_plugins/profile_tasks.py)
that is built-in and helps by showing how much time each task took.
These callbacks are definitely helpful for small playbooks or playbooks that
contain small or short-running tasks.
On long-running playbooks with a large amount of output, they almost make matters
worse by adding even more output into the task results.
# How do I get started with ARA ?
I've tried to do simple, yet effective documentation on how to get started
with ARA.
### 1) Install ARA
Documentation: [https://ara.readthedocs.io/en/latest/installation.html](https://ara.readthedocs.io/en/latest/installation.html)
First, you'll need to install some packaged dependencies and then you
can install ARA from source or from pip.
For example on a CentOS server:
yum -y install gcc python-devel libffi-devel openssl-devel
pip install ara
### 2) Configure the callback
Documentation: [https://ara.readthedocs.io/en/latest/configuration.html#ansible](https://ara.readthedocs.io/en/latest/configuration.html#ansible)
([What's an Ansible Callback ?](https://ara.readthedocs.io/en/latest/faq.html#what-s-an-ansible-callback))
The configuration of the callback is simple and seemless. You want to
add the following to your ansible.cfg file:
[defaults]
callback_plugins = /usr/lib/python2.7/site-packages/ara/callback
# Or, if using a virtual environment, for example
[defaults]
callback_plugins = $VIRTUAL_ENV/lib/python2.7/site-packages/ara/callback
### 3) Run a playbook with ansible-playbook
Run your favorite playbook !
### 4.1) Browse your data through the CLI
Documentation: [https://ara.readthedocs.io/en/latest/usage.html#querying-the-database-with-the-cli](https://ara.readthedocs.io/en/latest/usage.html#querying-the-database-with-the-cli)
$ ara result list
+--------------------------------------+-------------+----------------+--------+---------------+----------------------------+----------------------------+
| ID | Host | Task | Status | Ignore Errors | Time Start | Time End |
+--------------------------------------+-------------+----------------+--------+---------------+----------------------------+----------------------------+
| a73efa33-0d1e-4a7d-8e28-a76fa93b9377 | localhost | Debug thing | ok | False | 2016-05-21 14:42:24.794070 | 2016-05-21 14:42:24.837268 |
+--------------------------------------+-------------+----------------+--------+---------------+----------------------------+----------------------------+
$ ara result show a73efa33-0d1e-4a7d-8e28-a76fa93b9377
+---------------+----------------------------------------------------+
| Field | Value |
+---------------+----------------------------------------------------+
| ID | a73efa33-0d1e-4a7d-8e28-a76fa93b9377 |
| Host | localhost |
| Task | Debug thing (d04a5828-d32f-4349-89f1-39d7400b328f) |
| Status | ok |
| Ignore Errors | False |
| Time Start | 2016-05-21 14:42:24.794070 |
| Time End | 2016-05-21 14:42:24.837268 |
+---------------+----------------------------------------------------+
### 4.2) Browse your data through the web interface
Documentation: [https://ara.readthedocs.io/en/latest/usage.html#browsing-the-web-interface](https://ara.readthedocs.io/en/latest/usage.html#browsing-the-web-interface)
([What does the web UI look like ?](https://ara.readthedocs.io/en/latest/faq.html#what-does-the-web-interface-look-like))
Fire off the bundled webserver:
$ ara-manage runserver
* Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
And use your favorite browser.
# There's no step five !
We're all done here. That's the gist of it.
A lot of effort was made towards making ARA as simple to install,
configure and use as possible. It is meant to be able to run from start
to finish locally but it is also powerful enough if you'd like to
aggregate runs into a central server.
### Discussing or contributing to ARA
If you'd like to use ARA or contribute to the project, definitely feel
free ! Feedback, comments, ideas and suggestions are quite welcomed as
well.
I hang out in the **#ara** channel on freenode IRC if you want to come chat about ARA !
Special thanks to [Lars Kellogg-Stedman](http://blog.oddbit.com/) for the early feedback on the project, ideas and code contributions.
He was very helpful in fleshing and maturing the idea into something better.

103
website/content/blog/2016-06-07_ara-one-month-and-200-commits-later/index.md

@ -1,103 +0,0 @@
---
author: "David Moreau Simard"
categories:
- development
- changelog
tags:
- ansible
- openstack
date: 2016-06-07
title: "One month and 200 commits later"
slug: one-month-and-200-commits-later
type: post
---
On May 21st, I wrote a blog post about [ARA, an idea to store, browse and troubleshoot Ansible playbook runs](https://dmsimard.com/2016/05/21/ara-an-idea-to-store-browse-and-troubleshoot-ansible-playbook-runs/).
Let's rewind a bit further back in time.
On May 6th, I got tired of trying to make our [human_log](https://github.com/rdo-infra/weirdo/blob/master/playbooks/library/human_log.py) callback write user friendly HTML files.
I simply wasn't happy with my [attempts](https://review.gerrithub.io/#/q/topic:human_log_html)...
I'm a big fan of the UNIX philosophy: Do one thing and do it well.
Trying to hack HTML writing into human_log didn't feel like that at all.
I got frustrated and took a completely different direction.
What if, instead of writing and appending to a html file throughout a playbook run, I'd write to a database and make a dynamic, database-driven interface.
This would allow to organize playbook run data and also provide supported for aggregated run visualization.