5 ms·

well written. Things I would add to the Good side. - ability to commit to multi year cpu/ram without upfront costs - they can live migrate your vm to new phy

by pbrumm 8y ago

well written. Things I would add to the Good side. - ability to commit to multi year cpu/ram without upfront costs - they can live migrate your vm to new physical hardware, so no need to have random reboots of your instances - https load balancers allow traffic around the world to enter google network closest to user, this reduces handshakes and reduces comcast like outages to affect users. the above greatly decrease my stress.

ebikelaw 8y ago
I guess that closeness to user got eliminated from the “good” list since Google’s FELB is serving 502 to this author’s customers.
- dantiberian 8y ago
  They did eventually stop serving sporadic 502's, I've updated the post to make that a bit clearer.
  - ebikelaw 8y ago
    That’s good to hear. My intuition is random failure like that resulted from inability to find your instances, or a belief in their non-existence or ill health.
  - esseti 8y ago
    OP: for the 502 problems give a look at this https://github.com/kubernetes/ingress-nginx/issues/1396 https://github.com/kubernetes/ingress-nginx/issues/1396 https://github.com/kubernetes/ingress-gce/issues/34 https://github.com/kubernetes/ingress-gce/issues/34 I run into the same problem while ago. It may solve your problem as well.
- pbrumm 8y ago
  maybe. We haven't had any issues with it over last year. The comcast outage last week probably affected more customers.
stephengillie 8y ago
> they can live migrate your vm to new physical hardware, so no need to have random reboots of your instances Having supported VMWare at multiple locations, and having worked for a smaller cloud host, it shocks me that AWS don't support live migrations. VMWare can live-migrate VMs between datacenters in different geographic regions, while maintaining active sessions!
- wikibob 8y ago
  Technical debt. AWS had first mover advantage but now is saddled with the decisions they had to make to move fast at the time.

by pbrumm 8y ago

ebikelaw 8y ago

I guess that closeness to user got eliminated from the “good” list since Google’s FELB is serving 502 to this author’s customers.

dantiberian 8y ago
They did eventually stop serving sporadic 502's, I've updated the post to make that a bit clearer.
- ebikelaw 8y ago
  That’s good to hear. My intuition is random failure like that resulted from inability to find your instances, or a belief in their non-existence or ill health.
- esseti 8y ago
  OP: for the 502 problems give a look at this https://github.com/kubernetes/ingress-nginx/issues/1396 https://github.com/kubernetes/ingress-nginx/issues/1396 https://github.com/kubernetes/ingress-gce/issues/34 https://github.com/kubernetes/ingress-gce/issues/34 I run into the same problem while ago. It may solve your problem as well.
pbrumm 8y ago
maybe. We haven't had any issues with it over last year. The comcast outage last week probably affected more customers.

stephengillie 8y ago

> they can live migrate your vm to new physical hardware, so no need to have random reboots of your instances Having supported VMWare at multiple locations, and having worked for a smaller cloud host, it shocks me that AWS don't support live migrations. VMWare can live-migrate VMs between datacenters in different geographic regions, while maintaining active sessions!

wikibob 8y ago
Technical debt. AWS had first mover advantage but now is saddled with the decisions they had to make to move fast at the time.