This will allow developers to iterate on the web interface without
needing to spin up an API server.
Change-Id: I3838dbe3fea45e7139c4a50ab2e402038322acfc
The API demo redirected / to /api/v1 for convenience but we no longer
need to do it since there's a new index now.
Change-Id: Ice4755a82ef4a3abb6b82aad94d812bdd4339677
The demo API should be read only for the time being.
Depends-On: https://review.openstack.org/642511
Change-Id: Ia550f30cd720437cfc86d373e9c6de7cffe6e753
This deploys api.demo.recordsansible.org as well as
web.demo.recordsansible.org using the Ansible roles from ara.
The only part not yet automated is the letsencrypt certificate
generation.
Change-Id: I6b436d3be32105fdf9d661d042bfb3d40e5e39a6
Depends-On: https://review.openstack.org/#/c/641859/
Now that ara-{clients,server,plugins} have been merged back into
ara, it's easier to keep everything in the same repository.
The roles and integration tests have already been moved to the ara
repository so we can remove this now.
Change-Id: I8baf5701abb4bd030c5f0b321790482e0f9c229b
This commits imports two bootstrapped Ansible roles:
- ara_server for installing and configuring ara-server
- ara_frontend_nginx for setting up vhosts with nginx
The roles are integration tested by new Zuul jobs on Fedora
and Ubuntu.
Change-Id: I06c7a2e9fb3f61fa451053543971de89d438fef4
These are largely imported from the existing ARA 0.x integration
tests. Ideally, both 0.x and 1.0 would be using the same tests and
jobs to test themselves.
This effectively adds three jobs:
- ara-integration-fedora-2.7
- ara-integration-fedora-devel
- ara-integration-ubuntu-2.6
These jobs install Ansible from source and then installs ara-server,
ara-clients and ara-plugins in a virtualenv. It then runs the
integration-tests.yaml playbook.
Change-Id: Id0e78259a2bc69f66bc68a9c528613e4d5b7c2a4
This adds a role which:
- Sets up user/group/logging for Hugo
- Retrieves and installs the hugo from upstream release
- Sets up a systemd unit file to keep the hugo server running
- Installs and configure nginx as a reverse proxy to the hugo server
to serve ara.recordsansible.org
I'm not sure yet if keeping the hugo server running is the way to
go or if we should regenerate the static files every time.
It sort of goes against the point of hugo to use the server but
the fact that it reloads automatically when the source changes could
come in handy for automated updates.
Change-Id: I40e833a27117f9ec5003007bb08a677e16734e55