cci-moc / adjutant-moc Goto Github PK

Document our business requirements for account lifecycle:

• How/when are accounts created?
• How/when do accounts expire?
• How we we manage exceptions to standard workflow?
• Etc.

Partially performed actions can be rolled back via rolling back the performed operations. However if an action is completed, and the task moves on to the next action in the task, and that fails, when the task is rerun, the first action is going to be called again. Checks need to be in place so that the action knows how to handle this situation.

Ex. this currently fails for create project since the project create action doesn't expect the project to be there, even though it was the one who created it on the last run. Idempotency

#3 introduces a healthcheck endpoint. Integrate this into the Zabbix monitoring infrastructure that we have in place.

Currently, Adjutant already supports a dashboard and API for requesting quota changes. Enable the feature for Kaizen OpenStack.

• Wrap through adjutant-moc
• Write tests
• Enable dashboard
• Test
• Release
• Deploy

Adjutant should notify project requestor if project name already exists. It should also clarify that a. if they are trying to be added to an existing project to have that project owner follow these instructions .... https://support.massopen.cloud/kb/faq.php?id=22 b. if not they will need to rename the project.

Proxy error (attached) when approving ~ 8 users.

Related: CCI-MOC/ops-issues#280

redirect google forms openstack project requests form to directions on massopen.cloud to create new one using adjutant. output of old process is: https://docs.google.com/spreadsheets/d/1J32SU5HunV5fhff4deathB5IsAIPtCOTWRZuSQFqns0/edit#gid=1644329058 not sure of URL for the old forms but the page they should point at is: https://massopen.cloud/request-an-account/

Adjutant supports talking to a specific API to create projects and users. This work has been implemented for an OpenShift microservice implementing the API here.

• Test with OpenShift staging deployment
• After microservice has gone live on production deployment, redeploy and update configuration to enable

UPDATE: Second action item has been split out into CCI-MOC/ops-issues#90

We're currently testing integration with OpenStack via GitHub CI, but not with OpenShift.

• Have GitHub spin up a VM in our OpenStack environment and install OpenShift to it
• Run tests on installed OpenShift
• Tear down

eg. threading model of adjutant not updated yet.

Attendees: Whole team discussion time boxed at 2 hours. Kristi to do a sketch first. 2nd week of sprint. @knikolla please get on folks calendar soon. Also, mechanism to capture discussion so we don't lose thread over holidays.

The ssh connection to the mail server works from sso1 but not from sso2.