RRT Duty

Processing Support Requests from RRT

Follow these steps to efficiently process support requests:

Monitoring

• Continuously monitor the RRT Teams channel for DI and Inventory issues.

Initial Interaction

• When an issue is reported, ask for additional details:

  • Flower release of the environment and related module versions.

  • Steps to reproduce the problem.

  • Logs relating to the issue.

• For complex problems that require deeper investigation, arrange a call with the support team to troubleshoot together.

Reproduction and Preliminary Investigation

• Verify if the problem is replicable in the latest Bugfest and snapshot environments.

• In case it's a known issue, provide an existing Jira issue.

• If possible, address the issue immediately.

• If a data-related problem arises provide the appropriate corrective scripts.

• If resolution isn't feasible or immediate resolution takes more than an hour, create a Jira issue to track investigation and resolution efforts.

• Provide a workaround solution, if possible. Consult the Product Owner for a workaround if necessary.

Managing Multiple Requests

• If numerous requests or tickets are open, address them according to priority. Consult the PO or Team Lead to determine priority levels.

DoD for Investigation Task

• The issue has been fixed, if possible.

• A workaround has been provided, when applicable.

• A note has been added to the Jira ticket explaining the root cause.

• The library confirms that the thread can now be closed.

DevOps Duty

Environments Management

• At the start of each sprint, recreate the development environment using the latest snapshot versions.

• On request from the team or Product Owner, create or recreate any additional environments that may be needed for specific purposes such as Performance Testing or User Acceptance Testing.

Communication with Kitfox Team

• Communicate with the Kitfox team in the event of any issues with the development environment.

Recreate env instructions

1. Use the deleteNamespace pipeline to delete the existing environment (documentation for the pipeline):

   1. use specific to the env cluster and namespace values

      1. Values Spitfire dev environment: cluster - folio-dev , namespace - spitfire

   2. use the right values in infrastructure fields like PostgreSQL, Kafka, etc.. They should be the same as the current environment.

      1. Spitfire dev environment: all built-in

2. Use the createNamespaceFromBranch pipeline to create a new environment (documentation for the pipeline):

   1. use specific to the env cluster and namespace values

      1. Values Spitfire dev environment: cluster - folio-dev , namespace - spitfire

   2. set value in FOLIO_BRANCH

      1. Spitfire dev environment should have the latest snapshot versions, so set snapshot

   3. Config type should be specific to a purpose, if it’s a dev environment use development if performance testing or UAT environment use performance value.

   4. Select if reference and sample data should be loaded.

      1. Spitfire dev environment should load only reference data.

   5. Select if consortia should be enabled on the environment.

      1. Yes, for Spitfire dev environment.

   6. Select right infrastructure (discuss with TL):

      1. For Spitfire dev environment all values should be built-in

   7. use the right values in infrastructure fields like PostgreSQL, Kafka, etc.. They should be the same as the current environment.

      1. Spitfire dev environment: all built-in

   8. Set access for the environment

      1. Set in MEMBERS field: Spitfire