nerc-project / coldfront-nerc Goto Github PK

Currently, it only populates the username

https://github.com/ubccr/coldfront/blob/f667f56bc4377eab1a34b6b67c45ac5568b80957/coldfront/config/core.py#L78

Currently using django's built-in dev server (ie runserver command).

Number of gunicorn workers can be configured via WEB_CONCURRENCY environment variable:
https://docs.gunicorn.org/en/stable/settings.html#worker-processeshttps://docs.gunicorn.org/en/stable/settings.html#worker-processes

Throws a list doesn't support split error

The new plan is to keep using ColdFront staging for the early adopters of the OCP Prod cluster. This card tracks the task to move from Staging ColdFront to Production Coldfront once we are ready to rollout to all users.

-- Original Description --
After #69 is up, all that's left is running the create_openshift_resource through the pod terminal.

We should move to deploying releases rather than from the main branch.

Update the configuration to enable and set up OpenID Connect integration with Keycloak

Currently, the image is rebuilt and pushed every time that a commit is pushed, meaning doc changes and kubernetes manifest changes also trigger rebuilds.

The customized email templates used on NERC's ColdFront, located here has issue with project information. For example, for project allocations expiring soon is rendered like the following (Without the project infos):

Dear New England Research Cloud user,

Your access to New England Research Cloud's resources is expiring soon. Failure to renew the expiring allocation(s) on time will terminate access to the resource
for all users on the allocation. To renew, login to ColdFront and complete the short renewal process for each expiring allocation.  Below is a list of links to
your project(s) containing at least one expiring allocation:

The group owner responsible for this project is required to renew it on a yearly basis. If you have not done so in the
last year, you will be required to before renewing the allocation.
For more information about the yearly renewal, visit our knowledge base: https://nerc.mghpcc.org/user-guides/

Thank you,
New England Research Cloud (NERC)
https://nerc.mghpcc.org/
https://nerc-project.github.io/nerc-docs
https://nerc.instatus.com/

I transferred the repos but haven't updated the urls in the requirements and setup.cfg

Once OCP-on-NERC/nerc-ocp-config#143 is up and running we're all set to integrate NERC OCP Prod to ColdFront. To do that we need to provision the username and password as environment variables so that ColdFront has access to them.

1. The secret needs to be put in vault.
2. Create the external secret definition.

We're currently using coldfront-staging for managing the production OpenShift cluster.

When we're ready to roll out that OpenShift cluster more broadly to all users, we will need to start using the production ColdFront (#70).

• Do we want to provide a path for existing users to migrate their projects and resource allocations from the staging ColdFront to the production cluster?

If yes, the workflow needs to be defined and the feature implemented.

https://github.com/ubccr/coldfront/blob/941e87a6113d108286d8fe439dd4f8c2e619745a/coldfront/config/email.py#L17

An email needs to be sent to the ticketing system when a new request comes in.
An email needs to be sent out when the allocation has been approved.

Creating an issue so that this work can be tracked from CCI-MOC projects at https://github.com/orgs/CCI-MOC/projects

Currently the list of Fields of Science in ColdFront is more granular than we need.

• Get a mapping of current fields of science to new list, X -> Y. Here
• Write migration command to transition every project from X to Y.

https://github.com/cci-moc/coldfront-plugin-api introduces a REST API for querying Resource Allocations.

• Update requirements to install coldfront-plugin-api
• Update requirements to install forked ColdFront at cci-moc/coldfront

Currently this is loaded by rendering: https://github.com/ubccr/coldfront/tree/master/coldfront/templates/email