Assigned
Status Update
Comments
fl...@google.com <fl...@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
ba...@google.com <ba...@google.com>
ba...@google.com <ba...@google.com>
bo...@google.com <bo...@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?
bo...@google.com <bo...@google.com>
bo...@google.com <bo...@google.com>
pr...@google.com <pr...@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.
bo...@google.com <bo...@google.com> #5 Restricted
Restricted
Comment has been deleted.
bo...@google.com <bo...@google.com>
bo...@google.com <bo...@google.com>
ka...@google.com <ka...@google.com>
ka...@google.com <ka...@google.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
After my customer reserved an internal IP address in a shared VPC architecture inside the Service project with the command line below[1], my customer was able to use this IP address to create a VM instance with that reserved IP address.
After that, my customer expects the configuration inside the VM instance for the network-scripts for the current interface was created with the reserved IP address as static. [2]
[1]
[2]
What you expected to happen:
customer expect the interface configuration setting up with the Internal IP address reserved along with the
DNS
,GATEWAY
,SUBNET_MASK
andBOOTPROTO="static"
Steps to reproduce:
Run the command line above [1] in a shared VPC architecture inside the service project attached
create a GCE from scratch with a CENTOS7 image and for advance configuration open the network section and select the reserved IP as IP for the NIC0
After the GCE instance start, move to the path:
/etc/sysconfig/network-scripts
open the interface configuration in this reference
cat ifcfg-eth0
and you can see the values as reference [2], customer expect the IP reserved as IP, and all the required configuration on the configuration file as static
Other information (workarounds you have tried, documentation consulted, etc):
Customer requires this value
BOOTPROTO
asstatic
to run their application.