GUI: Add ACL editor (fate#310170)

Signed-off-by: Tim Serong <tserong@suse.com>
GUI: explorer: Add ability to upload hb_reports (fate#313354)

Signed-off-by: Tim Serong <tserong@suse.com>
Build: Set xgettext options (ensures POT file keeps comments)

Signed-off-by: Tim Serong <tserong@suse.com>
Build: Touch POT file back to ancient date (ensures correct generation)

It's possible to end up with the POT file having a newer mtime than the
various source files we need to search for translations (say, if you've
been checking out different versions of it).  If the POT file mtime is
too new, text strings from "older" source won't be pulled in, hence the
`touch` invocation.

Signed-off-by: Tim Serong <tserong@suse.com>
Build: Regenerate POT file

Signed-off-by: Tim Serong <tserong@suse.com>
GUI: dashboard: Add display of Geo cluster sites (fate#316119)

Signed-off-by: Tim Serong <tserong@suse.com>
GUI: Add ability to grant/revoke tickets via booth (fate#316119)

Signed-off-by: Tim Serong <tserong@suse.com>
Build: Regenerate POT file

Signed-off-by: Tim Serong <tserong@suse.com>
GUI: wizard: Prevent access if CIB not writable by user (fate#316465)

Signed-off-by: Tim Serong <tserong@suse.com>
GUI: wizard: Remove O2CB from OCFS2 templates (bnc#862757)

Signed-off-by: Tim Serong <tserong@suse.com>
Build: Regenerate POT file

Signed-off-by: Tim Serong <tserong@suse.com>
High: wizard: crmsh script for NFS server
add comments on service
Prototype for NFS server wizard
Update NFS server template
A variant that should work without added features
Low: wizard: Updated nfsserver crm script
Medium: wizard: A mostly broken sketch for how cluster scripts might be used from the wizard controller
Medium: wizard: Check output of cluster script
In-progress wizard work

Calling the cluster script seems to work, but there a lot of things
missing: Right now, there is no deeper interaction between the wizard
and the cluster script.

TODO:

1. appropriate parameters to the cluster script (matching the parameters
   to the wizard)
2. hawk updating the statefile with configured values before Validate
3. calling the cluster script as root (and requesting root privileges)
4. allowing multiple exportfs elements in the wizard.

My initial idea for 4) was to add something like

In the exportfs template, an attribute that says that this step can be
done multiple times (no good idea for an attribute name here)

In the <crm_script> section, use

<for template="exportfs">
...
</for>
which should expand to all the instances of the exportfs template in
sequence.