Private Network

April 28, 2013 5.5k views
Hey so I saw a few threads on this and its been a few months. The latest thread was around Jan so figured I bring up the subject again since you said you hope to have it resolved in a few months. Whats the latest status on private networking, For HA and failover abilities private IP's or at least a second IP set with a floating public IP address is pretty important. Thanks
10 Answers
The first stage of the private network will be rolled out as separate from the public internet but much like other providers it will be visible to other droplets in your account and others so there will still be a need to secure it with iptables rules depending on the services that you are running.

We are looking into the logistics of providing customer segmented networks but usually that entails some sort of vlan configuration which requires further networking automation as well as some hard limits on the number of vlans that can be supported by gear which creates a few barriers that we run into.

We are also looking into opening up an engineering tab which will inform customers of all of our current development, future development, and also provide priorities and ETAs. Often times there are new tasks which get prioritized higher which take precedence over long running engineering issues which is why some ETAs begin to get dragged out.

Our hope is that by providing more visibility into our development customers can see what other issues and features we are working on and also get a live idea of how priorities may shift if something comes up that requires immediate attention.
Agreed. Don't know if this is related, but I can't use scp or ftp commands from the command line to send or get the files from one droplet to another for some reason, while it works fine with another server outside DO network.

Hi Raiyu,

Is there any update on this?

We have deployed an internal beta of private IPs and are hoping to having it released soon. :]
I read somewhere that NYC2 would likely get this feature when released. Will existing droplets get the functionality or will we have to redeploy?
You should be able to enable it on your existing droplet once it's released without recreating it.
I can't wait! The only major thing keeping me from recommending this strongly to one of my major clients is the lack of private-IP networking! I have a small cluster currently on NYC2, and will be looking forward to the private IP option as soon as you can roll it out!
Aren't you going to deploy it in NYC1 any sooner ?
We would like to know if you plan to deploy "private shared network" in AMS1.

NYC2 has support for private networking. No ETA for other regions, though.
Have another answer? Share your knowledge.