101–110 of 119 posts
Love how DigitalOcean allows you to specify droplets as sources, groups of droplets (tags) as sources, or CIDR ranges.
DigitalOcean is killing it against Linode - I just migrated my last services off Linode because you still cannot attach arbitrary sized disks to your instances, something they've been promising as arriving "soon" for months. Go DO!
So awesome. It made me giggy today to remove all droplet level iptables rules and convert them to network level Cloud Firewall rules. Love how DigitalOcean allows you to specify droplets as sources, groups of droplets (tags) as sources, or CIDR ranges.
Earlier quoted context omitted.
How many firewalls can a single user create, and how many rules can be in each firewall? How is the order of multiple firewalls applied to the same droplet determined? Where is there logging to show when a rule matched? Is there any future plan to support REJECTing packets rather than only DROPing? Will the user interface warn the user when they are about to block all traffic (including ssh) to a droplet?
(DO employee here) The intro article answers many of these questions (and more): https://www.digitalocean.com/community/tutorials/an-introduc... > How many firewalls can a single user create, and how many rules can be in each firewall? 100 firewalls, 50 rules per firewall > How is the order of multiple firewalls applied to the same droplet determined? The rules are all added together and applied at the same priority.…
> The rules are all added together and applied at the same priority. Order doesn't matter.
If I make several firewalls, and the order of the rules when mixed results in unexpected traffic flows compared to the firewalls being applied individually, I have a bug that is hard to see, only experience during traffic as "timeout" or "not a timeout", and because of a lack of logging, no way to troubleshoot other than rewriting all the firewalls to try to remove any possibility of conflict, or writing whole new firewalls.
If I understood correctly, it's basically unsafe to mix more than one firewall per droplet, and in general a pain to troubleshoot. This is in contrast to iptables, where you can have multiple tables and chains, they follow a prescribed order, and you can mix and match them with expected results. Not to mention you can add logging whenever you need it.
DigitalOcean is killing it against Linode - I just migrated my last services off Linode because you still cannot attach arbitrary sized disks to your instances, something they've been promising as arriving "soon" for months. Go DO!
As long as Linode's portal is written in CodeFusion I wouldn't trust it.
Earlier quoted context omitted.
We published the roll-out schedule for Block Storage a little while back. Both LON1 and AMS3 are planned for this year: https://blog.digitalocean.com/block-storage-comes-to-singapo...
sweet. Is it possible to enable backups on block storage?
Earlier quoted context omitted.
(DO employee here) The intro article answers many of these questions (and more): https://www.digitalocean.com/community/tutorials/an-introduc... > How many firewalls can a single user create, and how many rules can be in each firewall? 100 firewalls, 50 rules per firewall > How is the order of multiple firewalls applied to the same droplet determined? The rules are all added together and applied at the same priority.…
Just checking if I have this right... > The rules are all added together and applied at the same priority. Order doesn't matter. If I make several firewalls, and the order of the rules when mixed results in unexpected traffic flows compared to the firewalls being applied individually, I have a bug that is hard to see, only experience during traffic as "timeout" or "not a timeout", and because of a lack of logging, no…
Earlier quoted context omitted.
That makes me really happy to hear. Is there any good way to keep up on potential up-coming features you are working on? I feel like that would be good knowledge to have when making decisions.
We don't have a formal system for that but we do announce customer early request betas. Sometimes they are invite only, other times we open them more broadly. In those cases where it is more broad it's usually featured on our homepage and then it's on a first come, first serve basis in terms of getting access and limited by the number of invitations that we are accepting. It's a bit of a fluid process as it depends o…
Earlier quoted context omitted.
Hmm, how do you mean? Mount an EC2 volume on a Linode server? The latency would be horrible.
Or S3, or another DO box, I guess. You're right that you'd never get excellent latency, but it could be good for storage.