Mentioned in SAL (#wikimedia-cloud) [2020-07-02T15:41:26Z] <arturo> sudo wmcs-openstack --os-compute-api-version 2.55 flavor create --private --vcpus 8 --disk 300 --ram 16384 --property aggregate_instance_extra_specs:ceph=true --description "for packaging envoy" bigdisk-ceph (T256983)

Mentioned in SAL (#wikimedia-cloud) [2020-07-02T15:56:12Z] <arturo> bump RAM quota to make room for new envoy builder VM (T256983)

Mentioned in SAL (#wikimedia-cloud) [2020-07-02T15:58:14Z] <arturo> created VM 'builder-envoy-02' (T256983) with ceph storage

Thanks for the update; I was going to check back in here soon. We've actually rearranged this build a bit, and in the end we won't need the expanded disk after all, so we'll be settling back into a regular m1.xlarge instance.

Please don't make any quota changes yet, as I think @hnowlan is still in the process of shuffling instances around, but we'll let you know as soon as we're closed out. (And Hugh please note the lossage @Andrew mentioned, in case it affected your work.)

Was the corrupted instance builder-envoy-02? I don't see it in Horizon any more so I assume it was. It looks like builder-envoy-03 is still healthy, which is now our preferred instance going forward.

In T256983#6348334, @hnowlan wrote:

Was the corrupted instance builder-envoy-02? I don't see it in Horizon any more so I assume it was. It looks like builder-envoy-03 is still healthy, which is now our preferred instance going forward.

Yes! I deleted -02 because it was a lost cause. If you're only using -03 these days then everything is probably good (other than reverting the quota change).

Yep, we're all set. Please revert the RAM quota at your convenience, and if there are any Ceph resources to reclaim, feel free to do that too -- we won't be needing it for the foreseeable. Thanks!