configurable IP addresses
I would love to see it posible to configure/administrate IP address, such that the IP address can be reused on upgraded (virtual) servers. A feature similar to AWS "Elastic IP address" (http://aws.amazon.com/ec2/#features) is what I am looking for.
I'd like to have the option of having a number of IP addresses allocated to me that I can assign to or move from one cloud server to another.
Something comparable to EC2's Elastic IP Addresses:
"Elastic IP Addresses – Elastic IP addresses are static IP addresses designed for dynamic cloud computing. An Elastic IP address is associated with your account not a particular instance, and you control that address until you choose to explicitly release it. Unlike traditional static IP addresses, however, Elastic IP addresses allow you to mask instance or Availability Zone failures by programmatically remapping your public IP addresses to any instance in your account. Rather than waiting on a data technician to reconfigure or replace your host, or waiting for DNS to propagate to all of your customers, Amazon EC2 enables you to engineer around problems with your instance or software by quickly remapping your Elastic IP address to a replacement instance. In addition, you can optionally configure the reverse DNS record of any of your Elastic IP addresses by filling out this form."
This is planned as part of the Network Services product based on NOVA.
This would be wonderful for those cases when one is upgrading a server, no need to have a heart attack when diddling with DNS.
Any progress on this?
I would love to see this. I believe this can be done with cloud load balancers, but I don't need a load balancer. I would love to be able to just have an IP I assign to a specific server and can move to a new server when I upgrade.
Greg Knaddison commented
I see this is "planned" based on NOVA. What does that actually "mean"?
Emanuel Lundman commented
Zack Gold commented
Francisco Reyes commented
Ping.. Has been planned for over a year. Any ETA yet?
Mike Christensen commented
The thing I really want to be able to do is launch a new web server, test out all my code on that, and then when it's working, swap IPs with the old production web server. Right now, I have to take down my site to do an upgrade, which is a huge hassle! Basically, if I could swap IPs between any instance, I'd be set..
Talik Eichinger commented
I noticed this feature is planned. Is there any rough timeline for release of it? This feature is pretty important to me, as I need to register our IP addresses with services that we connect to. Without this feature, growing and shrinking my cluster based on load is a bit trickier as I have to register my IPs every time I add an instance.
Has this been figured out or added?
Justin Wilson commented
I hope Rackspace does do this as it would be VERY helpful and useful for my business. Rackspace, acgann made a good point so if you want, you could setup some kind of limit like.. automatically releases in say 30 days if not used. :)
Kevin Veroneau commented
I agree with acgann, being able to deploy a server without a public IP address which is only on servicenet. As long as you have one server with a public IP address, you can easily access the other servicenet-only servers via SSH/PowerShell/RDP.
Jarl Friis commented
Seems like a duplicate of this one:
You know, we have 20+ servers and they are all behind the firewall. Most don't actually need public IPs. Now if Rackspace wanted to increase flexibility, they'd let us spin up servers that are "servicenet only" that ONLY have a private IP. And then they could let us use the ones we would've gotten anyway in the pool.
Considering the crunch of IPv4, this probably won't come soon. No way are they going to let people hold on to IPs they aren't actively using.
They may be able to do it for IPv6 though.
Moving an IP to a different image or load balancer would be awesome. We're gonna need this one soon! Not to mention the peace of mind that you are have control over an IP since we have so many things pointing to it.
Another great feature that AWS has on top of RS
Jeffrey Nichols commented
I require this feature in Cloud Sites so that not all of my sites have the same IP. However, it's my fault for not checking for this feature before I started moving all my sites there.
It surely would save a lot of hassles and DNS reconfiguration at the time of deploying a new production server based on an existing development server or image. Even a few hours IP reservation between server deletion and creation would do in most cases.