Notes from discussion of NDS-686. If When redeploying beta, what do we need to do?
- Related issues:
- Master crashing: NDS-660
- Upgrading Kubernetes: NDS-413, NDS-708
- Disk space issues: NDS-627
- Are we migrating data?
- No
- What is the correct size for the nodes
We suspect that some of our nodes (master, lma, possibly glfs?) are incorrectly sized for the Labs Workbench Beta cluster.
Some things to consider:
* Are we migrating data?
* What is the correct size for these nodes?
* Do other nodes need to change size?
...
:
- Rebuild Gluster FS:
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-693 - We'll need to redeploy Gluster with the new sharding config
- Master crashing:
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-660 - In the end, this is a bug in the NDSLabs API Server. Needs to be fixed, but doesn't directly impact redeploy
- Upgrading Kubernetes:
,Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-413 Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-708 - This is probably our biggest risk/issue at this point for re-deploy. We're not sure whether we can do it.
- Disk space issues:
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-627
- Import/export accounts:
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-690 - We will need to migrate at least the account information
- Currently, stacks and data will not be migrated.
- Node sizing:
- What is the correct size for the nodes? Do we need to resize LMA, master?