Spotinst Terraform Provider Rom Hirsh Updated April 16, 2018 22:00 Follow http://api.spotinst.com/integration-docs/terraform/ Comments 9 comments Sort by Date Votes Christopher Nielsen May 15, 2017 18:48 It is unclear how the following resources interact. hot_ebs_volume ebs_block_device persistence For instance, if I am constructing a Cassandra cluster, and on node failure, I would like replacements to use the same EBS volumes as the terminated node, which, if any of the following should I do? Define ebs_block_device resources, then set persistence attributes to true. Create ebs volumes for all nodes, then define hot_ebs_volume entries, for them, and set persistence attributes to true. 0 Permalink Rom Hirsh May 16, 2017 07:51 (Edited May 16, 2017 07:51) Hi Christopher, Thanks for bringing up these questions :) Perhaps checking out these articles will help to better understand the usage of the stateful feature As a quick clarification: * Hot EBS Volumes - works as a "Group" pool of volumes that will be attached to an instance and will support cross AZ migration of the volumes. * Persistence (stateful) - works by keeping each specific instances volume and root device to maintain a specific state, no need to supply a list of volumes. Specifically while using thePersistence (stateful) feature (option 1 as per your comment), if your Cassandra node is replaced we’ll clone the instance and bring it back. Your Cassandra cluster will behave as if the instance was down for some time. Bringing up a clone of the previous instance ensures that cluster IOPs are not wasted on bringing a new instance up. 0 Permalink Mike McMahon July 19, 2017 04:22 I am a little confused about the "roll_config" option, I am currently using terraform 0.9.11; however, it is complaining that this is not a valid configuration. Which version of terraform is required? 0 Permalink Rom Hirsh July 19, 2017 08:17 Hi Mike, Thanks for reaching out! Please make sure you are using the latest Spotinst Provider: https://s3.amazonaws.com/spotinst-terraform/v0.9.11/windows_amd64/terraform-provider-spotinst.exe https://s3.amazonaws.com/spotinst-terraform/v0.9.11/linux_amd64/terraform-provider-spotinst https://s3.amazonaws.com/spotinst-terraform/v0.9.11/darwin_amd64/terraform-provider-spotinst I hope this will resolve your issue 0 Permalink Mike McMahon July 19, 2017 17:15 Thanks Rom, I guess something I'd be more interested in knowing is if there are plans when the next version of TF is released that it will come pre-bundled? Having to manage multiple plugins across our developers isn't something we're too particularly interested in at this time. Though something we can definitely do, just trying to keep complexities on our end simplified (and avoid a situation where we accidentally lock ourselves into a specific version of a plugin) . 0 Permalink Rom Hirsh July 20, 2017 07:08 Hi Mike, We are working with Hasi Corp to include the latest releases into the main release of Terraform. Our release cycle is much faster and as such, there is a period where we will move ahead with version and sync as the Terraform version is released. As a general good practice, you should use the main release unless you have a missing feature or capability. 0 Permalink Yosef Tavin November 25, 2017 19:08 works great! One little hitch, the Windows download link for version 10.7 doesn't work. Ended up using Bash on Ubuntu on Windows, worked with Terraform v0.11.0 and the linux binary v0.10.7 0 Permalink Rom Hirsh November 27, 2017 18:50 Hi Yosef! Thanks for letting us know! the link is fixed now. Have a great day! 1 Permalink Isaac Graf January 21, 2018 10:39 (Edited January 21, 2018 11:28) Hi, I find that if I change capacity parameters in my spotinst_aws_group resource, terraform does not pick up the change. When I run terraform plan it says that Infrastructure is up to date, even though I changed the values of target, minumum, and maximum under capacity. Do you know what I could be doing wrong? 0 Permalink Please sign in to leave a comment.