Skip to content

Commit

Permalink
GITBOOK-683: change request with no subject merged in GitBook
Browse files Browse the repository at this point in the history
  • Loading branch information
@galenatjpl @gitbook-bot
galenatjpl authored and gitbook-bot committed Jan 16, 2025
1 parent 98d7eff commit 4f35bdf
Showing 1 changed file with 11 additions and 14 deletions.
25 changes: 11 additions & 14 deletions developer-docs/common-services/docs/maintenance/updating-venue-deployment.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,10 @@ description: Procedure for updating a venue deployment
```
4. Destroy Management Console via bastion host. See [instructions here](https://unity-sds.gitbook.io/docs/developer-docs/common-services/docs/users-guide/deployment/deployment-concepts-and-infrastructure/detailed-breakdown-of-project-onboarding-steps). (run destroy.sh under step 11)
5. Deploy new Management Console via bastion host. See [instructions here](https://unity-sds.gitbook.io/docs/developer-docs/common-services/docs/users-guide/deployment/deployment-concepts-and-infrastructure/detailed-breakdown-of-project-onboarding-steps).
6. Manually update the shared services API Gateway Integration "Endpoint URL" to be the API Gateway URL from the venue deployment (see screeenshot below for example). <mark style="color:red;">NOTE: This may be needed until automation that does this, is fixed.</mark>\
![](<../../../../.gitbook/assets/Screenshot 2025-01-14 at 6.57.56 PM.png>)
6. Manually update the shared services API Gateway Integration "Endpoint URL" to be the API Gateway URL from the venue deployment (see screeenshot below for example). <mark style="color:red;">NOTE: This may be needed until automation that does this, is fixed.</mark>\


<figure><img src="../../../../.gitbook/assets/Screenshot 2025-01-14 at 6.57.56 PM.png" alt=""><figcaption></figcaption></figure>
7. SPS Team re-deploys SPS
8. Re-add U-DS module to terraform state:

Expand All @@ -27,23 +29,18 @@ description: Procedure for updating a venue deployment

### Steps to Verify a Successful Deployment:

1. Verify the Management Console is accessible through the shared services HTTPD:

`https://www.<SS_PREFIX>.mdps.mcp.nasa.gov:4443/${VENUE_PATH}/management/ui`
1. Verify the Management Console is accessible through the shared services HTTPD:\
`https://www.<SS_PREFIX>.mdps.mcp.nasa.gov:4443/${VENUE_PATH}/management/ui`

**Development**: [`https://www.dev.mdps.mcp.nasa.gov:4443/unity/dev/management/ui`](https://www.dev.mdps.mcp.nasa.gov:4443/unity/dev/management/ui)&#x20;
**Development**: [`https://www.dev.mdps.mcp.nasa.gov:4443/unity/dev/management/ui`](https://www.dev.mdps.mcp.nasa.gov:4443/unity/dev/management/ui)&#x20;

**Test**: [`https://www.test.mdps.mcp.nasa.gov:4443/unity/test/management/ui`](https://www.test.mdps.mcp.nasa.gov:4443/unity/test/management/ui)
**Test**: [`https://www.test.mdps.mcp.nasa.gov:4443/unity/test/management/ui`](https://www.test.mdps.mcp.nasa.gov:4443/unity/test/management/ui)

**Production**: [`https://www.mdps.mcp.nasa.gov:4443/unity/prod/management/ui`](https://www.mdps.mcp.nasa.gov:4443/unity/prod/management/ui)
**Production**: [`https://www.mdps.mcp.nasa.gov:4443/unity/prod/management/ui`](https://www.mdps.mcp.nasa.gov:4443/unity/prod/management/ui)\

1. Notes:
1. `SS_PREFIX` varies by environment (dev, test, or empty for production)
2. Configuration is automatically removed during venue destruction
3. No manual Apache configuration is required\
2. Verify you can access the UI Dashboard\

2. Verify you can access the UI Dashboard
3. Verify the UI Dashboard is able to access the HealthCheck API, and is displaying statuses for each application.
3. Verify the UI Dashboard is able to access the HealthCheck API, and is displaying statuses for each application.



0 comments on commit 4f35bdf

Please sign in to comment.