GCE has too many features and I'd like for an easier way to create and manage instances for small projects.

Add a NLG service - this service should allow for someone to type a natural language query that goes beyond static sql but allows for inference at the query plan and get back a context-specific result either in form of a table output or a report. Point here is to avoid having to use sql to query the database but instead to use english sentence as a means of query.

To make sure we purchase for another committed use discounts (renewal), would be great to have feature reminder every month or one month before the expiration date of committed use discount.
the salesperson would be happy, the customer would be more than happy! :)

Add a QA service - that allows for question/answer permutations and retrieval on search and query as thought vectors on data

At present the IP range for BGP peering in a partner interconnect is 169.254.x.x set by Google Cloud. This seems that cannot be customized.These has some problems:

• I need to do monitoring from the peering device to the VMs in the VPC. This monitoring cannot use the 169.254.x.x address range as source IP that the sockets will use by default.


• traceroute not working.


• maybe this list is not exhaustive.

AWS and Azure do support specify a custom IP range for BGP peering.

Add a Complex Networks and Social Analysis Service - so its is possible to visualize huge network graphs, support for partition queries, and to combine that with geometric deep learning, bayesian analysis, random forests, and markov models (MCMC)

Add a BDI/Multiagent Service - that could be used for gametheory/argumentation, fault tolerance as part of natural computation, reinforcement learning steps. Such services could be useful for advertising platforms, detecting faults, security, chatbots, etc.

LOING OUTDORDE

A user build its project by adding multiple VPC, subnets, compute resource, network services and other VMs across various regions. A dashboard which provides an intuitive pictorial representation of the complete project would be very helpful. It could be similar to representations you use across your documentation pages. For eg:
https://cloud.google.com/router/images/vpn-failover.svg

The topology may also include below items:

Ip addresses configured on each resources

Vpc peering,VPN tunnels, interconnect etc.

For larger projects, you may provide both minimal and expandable views.
Each vpc/subnet/region/resource on the topology should be a clickable item which would display further attributes associated with it.

Maybe it would be nice to connect google-maps to the alarm-clock.

If I can tell my alarm-clock where I need to be at what time it would be nice if the clock changes the wake up time if there are traffic jams on the route I need to drive.

Add a Summarization Service - that could produce summarizes in all different types:

extractive
abstractive
single document
multi-document
indicative
informative
keyword
headline
generic
query-focused
update
main point
key point
outline
descriptive

Tried to launch the Single Node File Server 2 times with the same results - "failed to deploy". I hoped this would be a "slam-dunk" ZFS file server launch. After reading through reams of log output - it looks like storage resources failed. I'm not positive, because I don't have time to read through 10K lines of logs to a product I'm not familiar with. Disappointing and a waste of time.

Can we have this feature where the same content is shown to multiple users based on whether they have subscription or not. We want to include expiration (5-10 mins) and the link then becomes unusable and cannot be shared with others. Similar functionality is available at Similar to https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-urls.html

The users need to request IAM permissions via ticketing system. It would be great if the users can request in the organization level ticketing system

Google Cloud Load Balancers are great but missing Internal Https Load Balancer. Please support Internal Load Balancer for https.