Hi, unfortunately you are comparing apples and oranges. Windows licensing is a complex topic, controlled by the licensing rules Microsoft enforces. These rules are different for multi-tenant public cloud providers offering IaaS services than a vendor selling single tenant, dedicated hardware. That is a different business model, and different cost structure, and has very different rules from Microsoft.
At a high level, we have a strong partner relationship with Microsoft, and have made many suggestions on how they could improve the flexibility for customers to run Windows workloads in hyperscale clouds. We hope they’ll implement some of these soon, so we can offer the kinds of options you are looking for.
While we hear your feedback and share your wishes, the comparison for pricing of what you're getting is really to look at the cost of a Windows VM in any major public cloud provider, where you can walk up and pay for one for 10 minutes with no strings, no commitments. You'll likely find that GCE's VM options for Windows are very competitively priced for that type of product (which is the product that Microsoft's rules make it feasible to offer at this time).
Thanks for your feedback… please stay tuned!
Felicity, thank you very much for posting the detailed information on your workaround! I'm sharing this with the networking and support teams for their information, and I'm sure other users will find this helpful too until we can hopefully provide a service like this. Thank you for helping build our user community here on Uservoice!
Thanks, Felicity. I didn't see your comment, but moved it there anyway. I moved an older, less complete idea into this one. Stay tuned, we might have some news here soon, I know the product team has been exploring this due to customer demand.
Please provide more detail, see comments.
Hi - "allocate address" is an AWS command. I think I know what you mean though. Do you mean, "gcloud compute addresses create" and its equivalent API call? Are you asking that the command simply report back the IP address value that was created?
Based on a small number of customer requests, I am moving this from Declined to Under Review so we can accept further votes and feedback on whether some kind of “undelete” would be valuable.
We have received a few inquiries about this, but we do not offer any kind of "undelete" ability. Because some customers ask, I'm moving the state of this to "Under Review" instead of Declined, but we do not have immediate plans to offer this.
Thx, pls see comments for further info.
Typically, modern architectures use one of the many packages available that provides Service Discovery, which is a different thing than DNS. etcd, zookeeper, and consul are all examples you might investigate.
Thanks for the suggestion! This is one that we hear pretty infrequently, usually from users of EC2-Classic networking who have relied on this behavior as a form of service discovery (It is not supported in their newer VPC networking, to my knowledge). We hear this request about once every 6-12 months, and usually from one customer at a time, hence it has not been very high on our backlog. You're the first to mention it in the last 12 months that I'm aware of. :/
I'm not saying we won't consider this, as it has always been on our backlog, but other capabilities like private DNS tend to rank higher. So, if you have friends that want it, have them vote here. :)
Thanks, we’ll make sure this is on our radar.
We try to tackle improvements based on what gets the most votes and will provide the most positive impact for users, not a measure of time. As this item has been getting more positive votes recently and we have completed many other more popular requests, this item is under consideration as I mentioned a couple weeks ago.
Yup, still on there... sorry but no ETA yet. We have a number of usability improvements slated for the coming months, but I can't really speak to where this one lands on the timeline. :/
Announced today at Cloud Next ’17, PostGresQL Cloud SQL is now in Beta! Thanks to everyone for your enthusiasm and patience!
Response from the Cloud SQL PM team:
Thanks for your feedback! A GA date has not yet been set for Postgres support. Large features, such as replication and automatic failover (HA) will be added to the beta period later this year.
Thanks, glad you love it! I've shared your question with the PM for Cloud SQL.
Sorry Chuck, that just means that I changed the forum for this feature request within UserVoice (in case you were trying to figure out where it went). The CloudSQL product team is well aware of the market interest in this, thanks for adding your voice to the chorus! :)
Hang in there!!! The team is definitely aware of how many customers want this. :)
Thanks, I have shifted this request to the Cloud SQL area.
35 votesunder review · 3 comments · Google Cloud Platform » Feature Request · Flag idea as inappropriate… · Admin →
Good feedback, Mani. In this case, I'm inclined to keep them separate, because it's likely that the cron-like task queue piece could be available on a different schedule than the full slate of GAE-like services. I don't have dates to announce, but this is on our roadmap.
This is in Beta now.
Thanks, Mani. Sorry for the staleness - our UserVoice forums are a pilot project, and not all product teams are onboarded to actively moderate their forums yet. :)
We recently announced that Sao Paulo will be a region launching in 2017.
I'm sorry, but we can't generally make more specific predictions as the timing is subject to change for a variety of reasons. If you are a current customer with a sales/support relationship, you may be able to reach out to your representative for a more personalized conversation about your business needs.
Hi, we recently announced that Sao Paulo will be a GCP region launched in 2017. You can find more information on future planned regions here:
Thanks for your suggestion, this is definitely something we will consider adding in the future!
Thanks, Gary, we're considering this for a future enhancement.
Have you seen this one?
Interesting idea. This might be a bit beyond what would make sense for us to provide as a core platform capability, but it could definitely be done with something like a collectd agent (for example the version Stackdriver uses) and some downstream tech.
Yes, more or less. If you actually want to use it with Stackdriver, you can find out more about installing the agents here . The instructions are quite extensive, but there's a packaged version you can install . Most of the stuff there is about setting up verything to feed the data out to Stackdriver, from what I can tell. For your purposes though, you could probably use the collectd fork from Stackdriver, or just regular collectd and point it wherever you want, then read out that information. I'm not arguing that we or Stackdriver couldn't do this and offer it as a feature, by the way, just giving you some resources in case you want to have a DIY version. :)
Thanks for your feedback. We have both quick-start and tutorials available (see comments for links).
Hi, A quick-start including SSH is available here:
There are also step-by-step tutorials for doing many things. The "build a todo app" tutorial includes using SSH:
This feature is being tested in a private alpha program. If you would like to be invited to test this feature early, please fill out the form here:
This issue was imported from code.google.com, but it is a duplicate. Merging into the main suggestion.
Note, one possible workaround to this is to use a dynamic DNS service like dyndns. We recognize it would be better if instances got auto-generated DNS names, and we're looking at doing this in the future, but thought I'd mention this as it has worked for many people.
Currently we do not allow outbound traffic on port 25, but third party mail services like Sendgrid are available to use.
Hi, sorry but UserVoice is for product suggestions and feedback about what we can make better, but is not staffed for technical support responses. Please visit the gce-discussion Google Group, or post on a forum like StackOverflow or StackExchange where our support team can connect with you to help with any issues you may have. Thanks!
I definitely can appreciate your point of view, and we have heard this feedback from a number of customers (definitely more than the 6 votes this item has...). We're looking into a better approach for this that balances the concerns, but don't have anything to announce quite yet. I'll follow up with you directly to discuss the details of your situation a bit more and see if we can get you un-blocked somehow.
16 votesunder review · 5 comments · Compute Engine » Feature Request · Flag idea as inappropriate… · Admin →
Thanks for the feedback in these comments. I think at this point we understand what users are looking to do, and we're investigating changes that would allow this. The evolution of this limitation is due to what Scott described earlier - templates started as a requirement for MIGs, but they have since evolved into a more general "make a VM like this" function of the platform. I hope we can make improvements here in the near future.
Thanks, we’re looking at this.
I'm not sure this would work as you've described it, as a tag is not unique to a single instance. For example, you could label a handful of instances "staging". In that case, there couldn't be a DNS resource that uniquely identifies any single instance. Note, also, non-DNS entities like disks can be tagged.
While this may not be feasible, we are exploring making the instance name itself an automatic DNS entry.
Hello, thanks for your suggestion. Im’ sorry to say that we are only able to support this forum in English at this time, as most of the Product Management team that runs UserVoice is located in the US. please see comments for more details.
If you are able to post some additional comments on how you believe the proposed feature should work, we would be happy to consider this. We're not completely sure what you're proposing based on the title alone. Thanks!
Translated title to English via Google Translate.
We expect to allow finer grained controls in the future.
Thanks, we're definitely working on this.