Hey Jay! Sorry for my late response. We will look into this and get back to you.
On Wednesday, March 30, 2016 at 10:02:50 PM UTC+8, Jay Farschman wrote: > > This is still a problem, and I'll entertain, even crazy ideas on how to > solve it. Sadly, I do not understand enough about how a Scalr Agent's > "ResumeComplete" can be used on the Scalr Server. I only understand how to > make scripts run on the scalr agent instance. > > > On Wednesday, March 23, 2016 at 8:44:25 AM UTC-6, Jay Farschman wrote: >> >> I ran into a problem this morning where resuming a suspended VM does not >> refresh the DNS zone. >> >> I suspect I could use the "ResumeComplete" event trigger to kick DNS in >> some way, but I thought I should ask advice. >> >> Does anyone have a way to handle this? For us, I have told users to >> suspend their VMs at night and not to worry about the DNS. It's handled, >> but it seems like DNS just disappears for suspended instances. >> >> *REPLICATE IT* >> >> 1. Create a DNS Zone and point it at a Farm Role. >> 2. When you issue the suspend command DNS records are removed from >> the zone record even before the system is fully suspended. >> 3. Once the WebUI says the instance is suspended, it is not >> completely suspended, but in 20 seconds or so it reaches that state in >> AWS. >> 4. On resume Scalr will fire the "ResumeComplete", but this does not >> seem to refresh the DNS zone. >> >> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
