DO's TOR1 region is going on maintenance on December 7th and it might affect FaaStRuby's network performance.
Here is the official notification by DigitalOcean:
Subject: TOR1 Network Maintenance 2018-12-07 03:00 UTC Start: 2018-12-07 03:00 UTC End: 2018-12-07 09:00 UTC Hello, During the above window, the networking team will be making changes to our core networking equipment to improve performance for our TOR1 location Expected Impact: There may be a few minutes of increased latency as well as small amounts of packet loss while we shift traffic to redundant devices. We will endeavor to keep this to a minimum for the duration of the change. If you have any questions or concerns, please reach out to us by replying to this email or opening up a ticket on your account. Thank you, DigitalOcean Networking Team
This version addresses a bug that was preventing some function deployments in SFO2, plus a few enhancements.
- Change Ruby minimum version to 2.5.0.
- Disable timeout on HTTP requests.
- CTRL+C now quits gracefully.
- Add '--region' to help.
This update brings support for multiple Digital Ocean regions, starting with 'sfo2'. All regions are completely isolated, so you have to create a workspace and deploy your functions.
To manage different regions, use the '--region' flag on the command line. For example, to create a workspace:
$ faastruby --region sfo2 create-workspace my-workspace
The 2 regions supported so far are 'tor1' and 'sfo2'. The default is 'tor1', so if you run 'faastruby' without '--region', 'tor1' will be used.
It is also worth mentioning that each region has its own credentials file. The default path is '~/.faastruby.REGION'. For example, 'sfo2' credentials will be stored at '~/.faastruby.sfo2'. You can still use different files by setting the environment variable FAASTRUBY_CREDENTIALS.
To maintain backwards compatibility, if the region in use is 'tor1' and the file '~/.faastruby' already exists, the CLI will use that file instead of '~/.faastruby.tor1'.
Although the platform is meant to run on top of Digital Ocean droplets, they don't have a datacenter in Japan. Because the demand from Japan is really high, there are plans to add a Tokyo region through another provider. Friends from Japan, hang on tight!
That's all for now!
Oh, I got one more thing. Stay tuned for the next feature release: persistent storage!
I am excited to announce that now you can deploy your functions to the 'sfo2' Digital Ocean's datacenter! A new version of the gem is coming out shortly adding support for multiple regions. Stay tuned!
The migration is done! Stay tuned for more updates soon...
I am excited to announce that the platform is moving to a different infrastructure - still at Digital Ocean. This is the first step towards the goal of enabling multiple regions!
The end goal is to allow users to deploy functions to all regions supported by Digital Ocean. This should solve some of the latency complaints.
The maintenance should last for about 3 hours, and users could experience elevated error rates during this time. Please hang on tight!
If you have any questions, please join the chat!