...
- 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
- Should we resize master? No one is using big masters.
- 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 - Will likely need to create another volume or change /var/lib/docker to mount /var/ to cover all cases.
- David's recommendation: 1 volume per node with bind mounts.
- 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. Stacks require catalog migration too.
- Node sizing:
- What is the correct size for the nodes? Do we need to resize LMA, master?
- LMA:
- Should map correct data volumes
- 4-8 cores; 32-64GB RAM