Merge pull request #139 from mwestphall/pr/add-ospool-ep-rpm-docs

Add section on ospool-ep rpm to OSPool Backfill Containers

docs/resource-sharing/os-backfill-containers.md

@@ -92,6 +92,46 @@ Privileged mode (`--privileged`) requested in the above `docker run` allows the
 to mount [CVMFS using cvmfsexec](#cvmfsexec) and invoke `singularity` for user jobs.
 Singularity (now known as Apptainer) allows OSPool users to use their own container for their job (e.g., a common use case for GPU jobs).
 
+Running the Container via RPM
+---------------------------------
+
+On EL hosts, the pilot container can also be managed via a systemctl service provided by the `ospool-ep` rpm. To install this RPM:
+
+1. [Enable OSG yum repos](../common/yum.md).
+
+    !! note "Under active development"
+        The RPM is currently only available in the development repo.
+
+1. Install the service
+
+        :::console
+        root@host # yum install ospool-ep --enablerepo=osg-development
+
+1. Copy your OSPool Access Token to `/etc/osg/ospool-ep.tkn`
+
+    !! note "Token file ownership"
+        The EP is run under uid 1000.
+        Ensure this user has read access to the token file.
+
+        :::console
+        root@host # chown 1000:1000 /etc/osg/ospool-ep.tkn
+
+1. Configure the container service by editing `/etc/osg/ospool-ep.cfg`
+
+    - Set `GLIDEIN_Site` to your OSG Topology Site identifier
+    - Set `GLIDEIN_ResourceName` to your OSG Topology Resource Name identifier
+
+1. Start the OSPool EP container service:
+
+        :::console
+        root@host # systemctl start ospool-ep
+
+1. (Optional) monitor the systemctl service logs to see if the container starts successfully:
+
+        :::console
+        root@host # journalctl -f -u ospool-ep
+
+
 Optional Configuration
 ----------------------