Assigned
Status Update
Comments
ga...@google.com <ga...@google.com>
ka...@google.com <ka...@google.com>
ka...@google.com <ka...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
su...@google.com <su...@google.com> #3
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
ba...@google.com <ba...@google.com>
ba...@google.com <ba...@google.com> #4
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
tu...@google.com <tu...@google.com> #5
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
Description
Business Impact: Operational burden by not being able to manage VMs in a centralized way
Issue summary: What you would like to accomplish: The tools of VM Manager [1], are very useful for managing VMs, with features such as OS patch management, and OS inventory management, however these tools are currently only supported on a project scope.
At the moment, there isn’t a way to use VM Manager in a centralized way, that is, for an organization with many projects, VM Manager needs to be set up for each of the projects, creating an operational burden as it can’t be managed by a centralized entity.
This could be solved by having the tools of VM Manager working at the organization level.
[1]https://cloud.google.com/compute/docs/vm-manager
How this might work: By having the tools of VM Manager work at the organization level: Example: OS inventory management showing the data of VMs across all the projects of an organization
If applicable, reasons why alternative solutions are not sufficient: Currently the tools of VM Manager only work on a project scope, there is no centralized way of management at the organization level