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?
The bottom line is that any large-ish company who has a consumer-oriented product is paying for positive social media coverage. Even small ones try, as part of someone's job. The big guys just outsource it.
I expect one-third to one-half of anything positive I read about anything on the internet is bought-and-paid-for. I guess I should assume a portion of anything negative is also bought-and-paid-for by competing interests.
We invented the first, truly open and flat, egalitarian communication medium in the history of mankind, and then destroyed it within 20 years. Twenty billion web sites, and nothing exists except Amazon, Ebay, Google, YouTube, Facebook, and Twitter. Good job, corporations of America. I miss the web of '94.
EDIT: Also, I have no problem whatsoever believing that Reddit is a veritable playground for companies to exercise their "reputation management." It's pretty clear that their moves in recent years were precisely to allow deep pockets to game their systems to their benefit. I think Reddit and most of their top-posters are being completely hypocritical in claiming that the system isn't stacked in favor of whoever is paying them.
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 the future.
"
Right now, the Azure Container Service is a Linux only offering. We are working to enable Windows Server Container support using the Windows Server 2016 preview. Stay tuned for future announcements on this.
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.
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.
Are you assuming that only YC company employees use Hacker News as a news source? Google gets just as much airtime as Microsoft and Amazon here, and Google is vastly smaller (as of right now) in their cloud business.
No I'm assuming a lot of the Startup and YC community here are overwhelming using AWS which is why I expect AWS stories would be more relevant. I just see a lot of manufactured hype around Azure and not many well-known Startups using it.
The world is a lot bigger than the view around startups. They are great and all, but the audience of this site has grown a lot and includes a large number of corporate IT people now.
Weren't there several AWS stories on the front page anyway today? Has "cloud provider" become as tribal as "phone manufacturer" or "os vendor/not-vendor"? That whole part of technology culture is just wearing me out. Research shows that some things in tech trip the same emotional centers in the brain as religion. It just makes me tired. Even if MS was directly paying for stuff like this, wouldn't that be in-line with PG's libertarian whatchamacallit?
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 basis.
The one area we've consistently had real issues is with static IP persistence and VM location. At times, between our portal and an RDP session I've seen up to 3 different IP's for the same VM. Our VM's invariably lose their static IP's during reboots, which is a real nightmare because some of our vendors require IP white listing. We also can't seem to confirm that our servers are geographically where they're supposed to be. If we try to geolocate a server in US-West, we variously see it in other parts of the country, or even the world.
There's actually some very well thought out features related to what he's having a problem with. Don't just go with the "one endpoint per vm" that the default comes with in the older portal. Create a virtual network. Specify a custom DNS server or two for that subnet. Set static IP's on the NIC object in the new portal. Create a public IP address and bind it to that resource.
There are lots of options for fixing this problem. I'm really not trying to be all "read the eff manual" or anything. It really has changed a lot. Look at how some of the Azure Resource Manager templates fix this problem. They are all on github. The can show you what's possible even if you don't go with the declarative model for your environment.
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.
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.
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.
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 you deploy in the same way cross-cloud-provider. Swarm can run on AWS/Azure/GCE/bare metal, whereas ECS (which doesn't support Swarm and has its own scheduling/orchestration toolset) can only run on ECS.
+1 to MS for thinking about native tooling up-front.
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.
37 comments
[ 5.8 ms ] story [ 71.1 ms ] threadWith 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.
Or you could be a dick about it.
Very compelling.
http://techcrunch.com/2012/05/22/henry-blodget-linkbait-slid...
https://www.microsoft.com/en-us/security/online-privacy/repu...
I expect one-third to one-half of anything positive I read about anything on the internet is bought-and-paid-for. I guess I should assume a portion of anything negative is also bought-and-paid-for by competing interests.
We invented the first, truly open and flat, egalitarian communication medium in the history of mankind, and then destroyed it within 20 years. Twenty billion web sites, and nothing exists except Amazon, Ebay, Google, YouTube, Facebook, and Twitter. Good job, corporations of America. I miss the web of '94.
EDIT: Also, I have no problem whatsoever believing that Reddit is a veritable playground for companies to exercise their "reputation management." It's pretty clear that their moves in recent years were precisely to allow deep pockets to game their systems to their benefit. I think Reddit and most of their top-posters are being completely hypocritical in claiming that the system isn't stacked in favor of whoever is paying them.
In other words, what makes you assume that the upvotes are 'paid' vs people being interested in the technology?
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 the future. "
https://azure.microsoft.com/en-us/blog/azure-container-servi...
However that documentation is old as you can see. I cant find any new documentation.
I did find a post on how to setup a virtual machine of Windows Server 2016 preview and use it as a container
Windows Server Containers have existed since the release of Windows Server 2016 TP4 and you can try that out on Azure if you want to experiment with early code. See https://msdn.microsoft.com/en-us/virtualization/windowsconta...
DISCLAIMER: I work for MS as the PM on the Azure Container Service
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.
Weren't there several AWS stories on the front page anyway today? Has "cloud provider" become as tribal as "phone manufacturer" or "os vendor/not-vendor"? That whole part of technology culture is just wearing me out. Research shows that some things in tech trip the same emotional centers in the brain as religion. It just makes me tired. Even if MS was directly paying for stuff like this, wouldn't that be in-line with PG's libertarian whatchamacallit?
The one area we've consistently had real issues is with static IP persistence and VM location. At times, between our portal and an RDP session I've seen up to 3 different IP's for the same VM. Our VM's invariably lose their static IP's during reboots, which is a real nightmare because some of our vendors require IP white listing. We also can't seem to confirm that our servers are geographically where they're supposed to be. If we try to geolocate a server in US-West, we variously see it in other parts of the country, or even the world.
There are lots of options for fixing this problem. I'm really not trying to be all "read the eff manual" or anything. It really has changed a lot. Look at how some of the Azure Resource Manager templates fix this problem. They are all on github. The can show you what's possible even if you don't go with the declarative model for your environment.
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.
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.
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 you deploy in the same way cross-cloud-provider. Swarm can run on AWS/Azure/GCE/bare metal, whereas ECS (which doesn't support Swarm and has its own scheduling/orchestration toolset) can only run on ECS.
+1 to MS for thinking about native tooling up-front.
Disclosure: I work for Microsoft on Azure.