Change Details

Now that cloudcumin hosts are available, we should remove the `wmcs-admin` group from `hieradata/role/common/cluster/management.yaml`. Before we want to make sure the members of that group can use cloudcumin to perform the same tasks: {T347977}.

Now that cloudcumin hosts are available, we should remove the `wmcs-admin` group from `hieradata/role/common/cluster/management.yaml`. Before we want to make sure the members of that group can use cloudcumins to run the same commands they can now run from production cumin hosts: {T347977}. Another reason why members of `wmcs-admin` might need to SSH to production cumin hosts is to downtime alerts through the alertmanager API. So we should also complete {T347490} before this task can be started.

Now that cloudcumin hosts are available, we should remove the `wmcs-admin` group from `hieradata/role/common/cluster/management.yaml`. Before we want to make sure the members of that group can use cloudcumin to perform the same tasks: {T347977}s to run the same commands they can now run from production cumin hosts: {T347977}. Another reason why members of `wmcs-admin` might need to SSH to production cumin hosts is to downtime alerts through the alertmanager API. So we should also complete {T347490} before this task can be started.