-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update config files and fix errors found in testing new configs (#214)
Add --RESEnvironmentName to the installer Ease initial integration with Research and Engineering Studio (RES). Automatically add the correct submitter security groups and configure the /home directory. Automatically choose the subnets if not specified based on RES subnets. Resolves #207 ============================ Update template config files Added more comments to clarify that these are examples that should be copied and customized by users. Added comments for typical configuration options. Deleted obsolete configs that were from v1. Resolves #203 ============================= Set default head node instance type based on architecture. Resolves #206 ============================== Clean up ansible-lint errors and warnings. Arm architecture cluster was failing because of an incorrect condition in the ansible playbook that is flagged by lint. ============================== Use vdi controller instead of cluster manager for users and groups info Cluster manager stopped being domain joined for some reason. ============================== Paginate describe_instances when creating head node a record. Otherwise, may not find the cluster head node instance. ============================== Add default MungeKeySecret. This should be the default or you can't access multiple clusters from the same server. ============================== Increase timeout for ssm command that configures submitters Need the time to compile slurm. ============================== Force slurm to be rebuilt for submitters of all os distributions even if they match the os of the cluster. Otherwise get errors because can't find PluginDir in the same location as when it was compiled. ============================== Paginate describe_instances in UpdateHeadNode lambda ============================== Add check for min memory of 4 GB for slurm controller ============================== Update documentation. Remove Regions from InstanceConfig. This was left over from legacy cluster. ParallelCluster doesn't support multiple regions.
- Loading branch information
Showing
63 changed files
with
1,639 additions
and
1,534 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,45 +1,14 @@ | ||
| # Delete Cluster (legacy) | ||
| # Delete Cluster | ||
|
|
||
| Most of the resources can be deleted by simply deleting the cluster's CloudFormation stack. | ||
| However, there a couple of resources that must be manually deleted: | ||
| To delete the cluster all you need to do is delete the configuration CloudFormation stack. | ||
| This will delete the ParallelCluster cluster and all of the configuration resources. | ||
|
|
||
| * The Slurm RDS database | ||
| * The Slurm file system | ||
| If you specified RESEnvironmentName then it will also deconfigure the creation of `users_groups.json` and also deconfigure the VDI | ||
| instances so they are no longer using the cluster. | ||
|
|
||
| The deletion of the CloudFormation stack will fail because of these 2 resources and some resources that are used | ||
| by them will also fail to delete. | ||
| Manually delete the resources and then retry deleting the CloudFormation stack. | ||
| If you deployed the Slurm database stack then you can keep that and use it for other clusters. | ||
| If you don't need it anymore, then you can delete the stack. | ||
| You will also need to manually delete the RDS database. | ||
|
|
||
| ## Manually Delete RDS Database | ||
|
|
||
| If the database contains production data then it is highly recommended that you back up the data. | ||
| You could also keep the database and use it for creating new clusters. | ||
|
|
||
|
|
||
| Even after deleting the database CloudFormation may say that it failed to delete. | ||
| Confirm in the RDS console that it deleted and then ignore the resource when retrying the stack deletion. | ||
|
|
||
| * Go the the RDS console | ||
| * Select Databases on the left | ||
| * Remove deletion protection | ||
| * Select the cluster's database | ||
| * Click `Modify` | ||
| * Expand `Additional scaling configuration` | ||
| * Uncheck `Scale the capacity to 0 ACIs when cluster is idle` | ||
| * Uncheck `Enable deletion protection` | ||
| * Click `Continue` | ||
| * Select `Apply immediately` | ||
| * Click `Modify cluster` | ||
| * Delete the database | ||
| * Select the cluster's database | ||
| * Click `Actions` -> `Delete` | ||
| * Click `Delete DB cluster` | ||
|
|
||
| ## Manually delete the Slurm file system | ||
|
|
||
| ### FSx for OpenZfs | ||
|
|
||
| * Go to the FSx console | ||
| * Select the cluster's file system | ||
| * Click `Actions` -> `Delete file system` | ||
| * Click `Delete file system` | ||
| If you deployed the ParallelCluster UI then you can keep it and use it with other clusters. | ||
| If you don't need it anymore then you can delete the stack. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.