Monty Taylor 83ced7f6e6 Split inventory into multiple dirs and move hostvars

Make inventory/service for service-specific things, including the
groups.yaml group definitions, and inventory/base for hostvars
related to the base system, including the list of hosts.

Move the exisitng host_vars into inventory/service, since most of
them are likely service-specific. Move group_vars/all.yaml into
base/group_vars as almost all of it is related to base things,
with the execption of the gerrit public key.

A followup patch will move host-specific values into equivilent
files in inventory/base.

This should let us override hostvars in gate jobs. It should also
allow us to do better file matchers - and to be able to organize
our playbooks move if we want to.

Depends-On: https://review.opendev.org/731583
Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf

2020-06-04 07:44:36 -05:00

2.0 KiB

Raw Blame History

title: Etherpad

Etherpad

Etherpad (previously known as "etherpad-lite") is installed on etherpad.opendev.org to facilitate real-time collaboration on documents. It is used extensively during OpenStack Developer Summits.

At a Glance

Hosts

http://etherpad.openstack.org

Ansible

Projects

Bugs

Overview

Apache is configured as a reverse proxy and there is a MySQL database backend.

Manual Administrative Tasks

The following sections describe tasks that individuals with root access may need to perform on rare occasions.

Deleting a Pad

On occasion it may be necessary to delete a pad, so as to redact sensitive or illegal data posted to it (the revision history it keeps makes this harder than just clearing the current contents through a browser). This is fairly easily accomplished via the HTTP API, but you need the key which is saved in a file on the server so it's easiest if done when SSH'd into it locally:

/usr/local/bin/docker-compose -f /etc/etherpad-docker/docker-compose.yaml exec -T etherpad \
bash -c "wget -qO- 'http://localhost:9001/api/1/deletePad?apikey='$(cat \
/opt/etherpad-lite/APIKEY.txt)'&padID=XXXXXXXXXX'"

...where XXXXXXXXXX is the pad's name as it appears at the end of its URL. If all goes well, you should receive a response like:

{"code":0,"message":"ok","data":null}

Browse to the original pad's URL and you should now see the fresh welcome message boilerplate for a new pad. Check the pad's history and note that it has no authors and no prior revisions.

2.0 KiB Raw Blame History