网络状况更新 - 2016年4月

评论 (12)

1. 
   Ryan May 2, 2016 at 10:34 pm

   I’m very pleased to see some progress on this. It’s been a rough several months, I know, and I’m happy to see follow-through at long last. Can’t wait to see what it’s like after this is all rolled out in full!

   Reply
2. 
   Linode Customer May 3, 2016 at 9:14 am

   When will you be detailing the recent changes to the DNS service? Anybody with half a networking brain (which is presumably all of your customers) can see what you did, but we’re waiting for you to tell us the how and why of it.

   Reply
3. 
   Rich May 5, 2016 at 10:17 am

   Most of the DNS-related changes have been gone over here:

   https://status.linode.com/incidents/smh59r6tyw7j

   Not sure there’s going to be a full blog post dedicated to the CloudFlare Nameserver switch.

   Reply
4. 
   KP May 5, 2016 at 4:36 pm

   I realise you can’t do everything at once but do you have any plans regarding block storage in the pipeline? I’ve been at my instance’s storage limit for some time and given the expansion options at Linode it’s very hard to ignore the new block options from your competitors.

   Reply
5. 
   Steve May 6, 2016 at 2:46 pm

   No doubt Linode’s infrastructure is always the best in VPS, but from software service aspect, it ‘s kind of outdated: the dashboard looks like Web 1.0, docker support – docker machine drive, elastic IP, etc. Please put more effort on your software service. Now, software industry is started transfer into container based microservice, even serverless, the infrastructure layer should be expose less and less to the developers.

   Reply
6. 
   Kenn May 10, 2016 at 2:07 pm

   I disagree with Docker support. It’s too early to bet on it IMO. I like VPS because it’s a bare-metal solution.

   Elastic IP would be nice in theory, but not in the way AWS does it, please. One of my apps needs to bind multiple IPs to a socket, which is simply impossible with AWS. I hated it when I had to learn their proprietary way of doing on everything.

   If you want an encapsulated infrastructure layer, go with PaaS like Heroku.

   Reply
7. 
   thwutype May 23, 2016 at 3:42 am

   If Web 1.0 dashboard is working fine and secure, I see no reason to change that; since anytime you could write your favorite fancy Web-UI with Linode API.

   Time-to-time DDoS packet-drop and Tokyo-sold-out(KVM announced for ~1 year) shall be resolved ASAP.

   Reply
8. 
   Matt Freeman May 30, 2016 at 8:28 am

   Nice! 🙂 I can’t believe I missed this announcement. Credit where due.

   Reply
9. 
   James May 31, 2016 at 11:00 pm

   Glad you’re beefing up your network capacity. But this doesn’t change a thing for us: customers of yours that get DDOSed will still be booted off your platform. That is pretty harsh. Yes, there are services such as Cloudflare which protects websites cheaply but what about FTP, SSH + other random ports applications use? You really should offer some kind of paid DDOS protection service with all that bandwidth you’re buying, which can be turned on with a flick of the switch. We’re running our external firewalls with a DDOS protected provider then routing traffic to your DC and considering just making a switch to have everything under one roof.

   Reply
10. 
    Soh June 9, 2016 at 4:33 pm

    I realise you can’t do everything at once but do you have any plans regarding block storage in the pipeline? I’ve been at my instance’s storage limit for some time and given the expansion options at Linode it’s very hard to ignore the new block options from your competitors.

    There isn’t anything in the line at the time, but it’s certainly something that is always considered! Linode has always been trying to provide more for the same price – cause they love you. Promise.

    No doubt Linode’s infrastructure is always the best in VPS, but from software service aspect, it ‘s kind of outdated: the dashboard looks like Web 1.0, docker support – docker machine drive, elastic IP, etc. Please put more effort on your software service. Now, software industry is started transfer into container based microservice, even serverless, the infrastructure layer should be expose less and less to the developers.

    Touching up the look and infrastructure is something always considered as well, and our engineers have been working on this, actually! You can find their progress on it (as well as a github to the project) here:

    https://engineering.linode.com/2016/06/03/Building-a-comfy-frontend-stack.html

    Reply
11. 
    Matthew August 26, 2016 at 1:02 pm

    “The provider estimated a late June install date…”.

    Should’ve gone with “the provider”. It’s almost September and you’re still single-homed in Atlanta.

    Reply
12. 
    Bruce September 13, 2016 at 6:26 pm

    Which data centers are complete on this now? Is there a schedule that we can see?

    Reply