-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block Storage Improvements #9
Conversation
Updating readme
…vider-vultr into attach_fix
@Oogy - with this fix, if both the block storage and vultr server are managed by terraform, if I |
@badgerwithagun Yes that is correct. |
Fantastic. This is a bit concerning:
Is it possible that this will end up being unstable in practice? |
@badgerwithagun This is necessary since it is not possible to live attach block storage. Without this the reboot during the attachment process will interrupt the server bootstrap scripts leaving the server in a non-working state. So with the sleep stability is improved. |
@badgerwithagun as @Oogy stated this due to a constraint as to how we handle deployment and attaching of block storage to instances. This shouldn't cause any instability issues. @Oogy Tested and verified that everything is working with the ability to taint servers and have the block storage get reattached. The acceptance tests also pass locally with no issues! |
attached_id
parameter set. Previously it would have required a secondterraform apply
run.resourceVultrBlockStorageRead()
to useGet()
(returns the specified subscription) vs.List()
(returns list of all subscriptions, requires searching).attached_id
) having been destroyed inresourceVultrBlockStorageUpdate()
.