initial ecp ci document commit

services_and_applications/ecp_ci/ci_details.rst

@@ -0,0 +1,3 @@
+**********************
+ECP CI Details at OLCF
+**********************

services_and_applications/ecp_ci/getting_started.rst

@@ -0,0 +1,70 @@
+***********************************
+Getting Started with ECP CI at OLCF
+***********************************
+
+It is important to note that ECP CI capabilities are currently limited to the :ref:`ascent-user-guide` system. The ability to enable this on Summit is a work in progress.
+
+Getting Your Project Setup for ECP CI at OLCF
+---------------------------------------------
+
+An important realization is that NCCS has two separate security enclaves, Open and Moderate, with different resources. The ECP CI capability is only enabled in the Open enclave at this time, running on the :ref:`ascent-user-guide` system, not the Moderate enclave (Summit).
+
+This is important because you may already have a project setup within NCCS, for accessing Summit. If so, this project needs to be mirrored to the Open enclave for working with ECP CI on Ascent (assuming that is the project code you want to setup to use the ECP CI framework).
+
+So, the first thing is to establish a project in the NCCS Open Enclave. There are two options for this:
+
+	- Mirror an existing project from Moderate to Open for ECP CI
+	- Request a new project to be created in the Open enclave for ECP CI
+
+For both of these options please email `[email protected] <[email protected]>`_ to initate the request.
+
+**What to include in the request(s):**
+
+	For mirroring:
+
+		- The project PI (they need to approave the mirror request)
+		- The Project ID
+		- Statement that this is for ECP CI
+
+	For new project request:
+
+		- Name of the project
+		- Project PI
+		- Initial users
+
+
+What Accounts Do I Need?
+------------------------
+
+Accessing Ascent and working in the NCCS Open enclave requires an ORNL Resource Account (i.e., XCAMS or UCAMS). Users can register for an account at this `User Portal <https://user.ornl.gov/>`_. 
+
+This is different from your NCCS Account/User ID (i.e., the one you use to log into Summit).
+
+**NOTE:** ORNL Staff do not need to create an account and can use their standard ORNL User ID (UCAMS).
+
+Applying For Project Access
+---------------------------
+
+To gain access to a project, fill out the `Account Request Form <https://www.olcf.ornl.gov/support/getting-started/olcf-account-application>`_.
+
+**Please be sure to have this necessary information:**
+
+	- Your ORNL Resource Account User ID
+	- The Project ID
+	- The Project PI
+
+Accessing the CI Infrastructure
+-------------------------------
+
+Currently, ECP CI at OLCF is limited to the `code.ornl.gov <https://code.ornl.gov/>`_ Gitlab Server. It is specifically limited to the "ecpcitest" `group <https://code.ornl.gov/ecpcitest>`_, within that Gitlab Server.
+
+Your NCCS Open project needs to have a Gitlab project setup, within the "ecpcitest" group, on `code.ornl.gov <https://code.ornl.gov/>`_.
+
+Once you have your NCCS Open Project setup, please submit a ticket to `[email protected] <[email protected]>`_ requesting the Gitlab project be setup.
+
+In the end, you should be able to log into these systems:
+
+	- `code.ornl.gov <https://code.ornl.gov/>`_
+	-  ssh <Your_UID>@login1.ascent.olcf.ornl.gov 
+
+**NOTE:** Both of these systems require you to use your ORNL Resource Account User ID. This is different than your NCCS User ID.

services_and_applications/ecp_ci/index.rst

@@ -0,0 +1,11 @@
+**************************
+ECP Continuous Integration
+**************************
+
+
+.. toctree::
+   :maxdepth: 2
+
+   overview
+   getting_started
+   ci_details

services_and_applications/ecp_ci/overview.rst

@@ -0,0 +1,11 @@
+***************
+ECP CI Overview
+***************
+
+The ECP Continuous Integration (CI) resources are based on `Gitlab's CI components <https://docs.gitlab.com/ee/ci/introduction/>`_, but enhanced for HPC centers. These `enhancements <https://ecp-ci.gitlab.io/docs/introduction.html#enhancements>`_ were identified as critical, to improve the ability of application and software technology projects to test across diverse HPC architectures and software environments.
+
+You can find the central ECP CI Documentation, for all participating HPC Centers, at the main `ECP CI documentation page <https://ecp-ci.gitlab.io/index.html>`_. 
+
+The documentation you are looking at now is specific to OLCF's site-local model, to enable initial testing of ECP CI integration at OLCF. An overview of the different ECP CI models can be found `here <https://ecp-ci.gitlab.io/docs/introduction.html#ci-use-models>`_. The `Federated Model <https://ecp-ci.gitlab.io/docs/introduction.html#federated-model>`_ being the model that integrates all participating HPC facilities.
+
+**The Federated Model is NOT enabled yet. Currently, the site-local model is the only accessible implementation at OLCF.**

services_and_applications/index.rst

@@ -7,4 +7,5 @@ Services and Applications
 .. toctree::
    :maxdepth: 2
 
-   slate/index.rst
+   slate/index.rst
+   ecp_ci/index.rst