I am struggling to find a solution given the following:
- A cluster of two or more servers - Each server has a storage volume attached - If a server goes down (disappears) it should attach to the same (identical content) volume when it is re-created - Minimal manual intervention for all life-cycle use cases - Fully managed vi Heat If it would be possible to define the following logic, it would be great, but I have not found any way to do this: - For each server, pre-declare the name of the volume to attach - When server is created and a volume with the pre-declared name exists, that volume is attached - When a server is created and a volume with the pre-declared name does not exist, such a volume is automatically created - When a server is deleted, its attached volume is deattached but not deleted (could do this using “deletion_policy: ‘Retain’” ) I would be happy to receive feedback on any idea that will take me closer to a solution. I have tried to use “external_id:” in conjunction with OS::Cinder::Volume in order to get a pre-declared name for each volume, but that did not work as I expected it to. I ma currently on “Newton”. Thanks
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
