Live data from Hacker News

Azure Container Service is now generally available

azure.microsoft.com

31–38 of 38 posts

Re: Azure Container Service is now generally available

#31
post #5
post #3

is Microsoft paying for up votes?

They sure are and it's much worse on Reddit. With Microsoft's shrinking relevance to modern computing it's a given. They have billions in the bank so they might as well spend a few million on fake upvotes to give their products an illusion of popularity. When your own former CEO calls Microsoft's current cloud numbers "bullshit", they probably are.

Maybe they actually decided to start responding to the whining and demanding of developers on sites like HN because, you know, they exist to sell shit to users and developers? Maybe they are trying to give you guys exactly what you want in the way of services and products because your way won?

Or you could be a dick about it.

Re: Azure Container Service is now generally available

#32
post #28
post #7

Look for golang support in VS Code to continue improving.

It's honestly already pretty freaking good. If you allow for the fact that Go is a less rich language (syntactically) than Java, I'd even suggest that VSC for Go is on par with IDEA products for their respective languages. There's definitely stuff to improve yet, but the day-to-day stuff is smooth as silk.

Of course I use VS for my Stepford wife work, but always used LiteIDE for my golang stuff. I'll have to check out VSC.

Re: Azure Container Service is now generally available

#33

This is interesting when compared to Amazon Elastic Container Service because of Azure Container Service's support for native Docker clustering tools. If I am developing user docker-compose, I want to deploy that way, too - at least until I reach scale, at which point I want scheduling and orchestration tools, e.g. Swarm. For easier disaster recovery, it's very convenient if these scheduling/orchestration tools let y…

One of our primary goals with ACS is to make sure we offered versatility with the platform. We wanted to support both a choice of orchestrators (DCOS and Swarm) and wanted to expose these open source solutions directly, enabling cross-cloud mobility. Disclosure: I work for Microsoft on Azure.

Does this mean you and the Azure team convinced Mesosphere to open source DCOS?

Re: Azure Container Service is now generally available

#34
post #9

Earlier quoted context omitted.

I'm a little curious. What part of Microsoft having container availability in it's cloud offering is not interesting (particularly given that it can run both linux and windows containers)? In other words, what makes you assume that the upvotes are 'paid' vs people being interested in the technology?

Do you have a technical link to how to run Windows Containers in this new offering? I tried to look and this is the most specific I could find: " At this time the service supports Linux containers only. Microsoft has committed to providing Windows Server Containers using Docker and Apache Mesos is being ported to Windows. This work will allow us to add Windows Server Container support to Azure Container Service in th…

Sorry, I was looking at this:

https://msdn.microsoft.com/en-us/virtualization/windowsconta...

Which specifically mentions:

Windows Server Containers:

A Windows Container Host running Windows Server 2016 (Full or Core), either on-prem or in Azure.

Which I mistakenly thought was part of this offering.

Re: Azure Container Service is now generally available

#35
post #33

Earlier quoted context omitted.

One of our primary goals with ACS is to make sure we offered versatility with the platform. We wanted to support both a choice of orchestrators (DCOS and Swarm) and wanted to expose these open source solutions directly, enabling cross-cloud mobility. Disclosure: I work for Microsoft on Azure.

Does this mean you and the Azure team convinced Mesosphere to open source DCOS?

We (MS) are one of over 60 partners that Mesosphere worked with to open source DC/OS. No convincing required :-)

Re: Azure Container Service is now generally available

#36

This is interesting when compared to Amazon Elastic Container Service because of Azure Container Service's support for native Docker clustering tools. If I am developing user docker-compose, I want to deploy that way, too - at least until I reach scale, at which point I want scheduling and orchestration tools, e.g. Swarm. For easier disaster recovery, it's very convenient if these scheduling/orchestration tools let y…

One of our primary goals with ACS is to make sure we offered versatility with the platform. We wanted to support both a choice of orchestrators (DCOS and Swarm) and wanted to expose these open source solutions directly, enabling cross-cloud mobility. Disclosure: I work for Microsoft on Azure.

Will Kubernetes be supported in the future? This is much more interesting to me than Swarm

Re: Azure Container Service is now generally available

#37
post #23

Earlier quoted context omitted.

How can you say this with a straight face when day in and day out Google and Amazon are top stories on Hacker News? Azure is the second largest cloud platform, it's pretty relevant.

The post had 42 up votes before a single comment. Don't you find that ODD?

It's not that odd, and you're breaking the rules by throwing around accusations of astroturfing without evidence. Please stop.

If you suspect abuse, the thing to do is email hn@ycombinator.com so we can look at the data and investigate. Bringing it up in the threads will only provoke a tedious and off-topic flamewar, and if there isn't abuse going on, then you've unfairly maligned your fellow users.

Re: Azure Container Service is now generally available

#38
post #16

Earlier quoted context omitted.

Are there any well known YC companies using Azure? All the ones I know that have published their technology stacks are using AWS, which is why I expect AWS features to be more popular on HN since they're more relevant and useful.

I'm not a YC company but will share one man's opinion about Azure. We started using it because we have one piece of software in our stack that only runs on Windows, so we have a Windows VM and a couple Linux VM's running everything else. We're early in the life of the company so we're pretty much just using it for basics, but as a platform it's been fine. My dev ops guy seems to have few complaints on a day to day ba…

I'm reasonably seasoned in Azure, though far, far from an expert. But it sounds like you need to set up a Reserved IP in Azure, that should solve your problem. You'll need PowerShell to do this. (tut: https://azure.microsoft.com/en-us/blog/reserved-ip-addresses...)

I think you can do this from the Azure CP now, I am not 100% sure.

Your IP should not flush on reboot though, that should theoretically only occur if you're doing cold boots/shutdowns; but that's a no-no in any cloud environment unless you have a reserved IP; which is why you are encouraged to use cnames instead for domain management, etc.

As far as the region problem, this can happen if you're using something like a scale set or load balancers. That could throw off a trace route. Also making sure your storage account, etc are all in the same region is fairly important.

Post reply on HN