How can we improve Compute Engine?

renaming vm

make it as easy as EC2 :)

878 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Erik shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
planned  ·  AdminPaul Nash (Product Manager, GCE, Google) responded  · 

Hi folks, we know there is a ton of interest in this ability, and our engineering team is working on enabling it. We don’t have specific schedule updates right now, but I wanted to post an update acknowledging that we definitely agree this is an important ability and we will launch the functionality just as soon as we can!

54 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Bathinda commented  ·   ·  Flag as inappropriate

    I voted this feature up.
    But what's the meaning that I only have 20 chances of voting up?

  • AL commented  ·   ·  Flag as inappropriate

    Really? Can we please have this ASAP? Going through 4-5 steps (Snapshot, clone, settings...) to do this is ridiculous and error prone when working with multiple instances!

  • Fady Ibrahim commented  ·   ·  Flag as inappropriate

    We are in 2019 and still not supported. I think it is an important thing that should be done!!

  • Anonymous commented  ·   ·  Flag as inappropriate

    Wow 2019, and this feature still not avaiable. I mean what's the point of not being able to rename it.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I was going crazy and shamed due the fact what I had to google something so basic, as rename an instance. I thought I was loosing my basic skills to find something that was supose to be very simple, but then I found this page and I do not know if I get relaxed or surprised for the lack of this feature, for so long time...

  • Anonymous commented  ·   ·  Flag as inappropriate

    can't you just have each vm have an internal id that never changes, and the name would link back to it? that seems trivial

  • Jules Lefevre commented  ·   ·  Flag as inappropriate

    Paul, we appreciate the new update - to learn this is not an easy implementation is news, prior to this support had only agreed with us that "it does seem trivial" - leaving a lot to be wondered.

    Looking forward to further updates.

  • Jules Lefevre commented  ·   ·  Flag as inappropriate

    @Steve Larson, sadly mate snapshotting does not retain metadata etc. All of this information does have to be re-entered manually.

  • Jules Lefevre commented  ·   ·  Flag as inappropriate

    4 years onwards and... Seriously, nothing.

    I genuinely was astounted when I found there was not a way to rename VM's back in 2014. It's easy to say "Yes, you're right, it's trivial", but truly Paul, this is so far beyond "Trivial" that it's actually embarrassing to admit to my AWS supporter friends that "Yes you STILL can't rename VM's in GCP".

    I can't believe this has gone this long without it's due attention. It's the 4th highest requested feature currently on GCE, and let's be honest, an intern with a day's free time could have had this solved all too long ago.

    At the end of the day, if it takes 4 years to fix something "trivial" then perhaps the method in which issues are deemed worthy of fixing should be "fixed".

  • William Barath commented  ·   ·  Flag as inappropriate

    This is taking a bizarre amount of time. The compute instance has a numerical unique ID. Everything should index by that, and then changing the name is just a trivial change to metadata. It's not like the name is actually being used for anything intelligent like ... oh... updating the /etc/hosts in the cloud shell ... so what exactly is the holdup?

← Previous 1 3

Feedback and Knowledge Base