Single public IP setup?

You could do

nova-manage floating create `hostname` my.single.public.ip/32

The important part is the /32. That's what will create the one and only one
IP specified by my.single.public.ip

Note the back ticks around hostname to get the hostname of the machine
you're running this command on.

Everett

On Sun, May 8, 2011 at 11:05 AM, Michael G. <
<email address hidden>> wrote:

> New question #156597 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/156597
>
> Is there a possible setup for nova to only use one public ip?
>
> Is there any documentation about that, I'm not sure how to accomplish this.
>
> Thanks michael
>
> --
> You received this question notification because you are an answer
> contact for OpenStack Compute (nova).
>

Which network configuration should I use? how would it be possible then to ssh into instances? via vlan and vpn?

thanks for your help.

Could it be an issue just having one public ip? for example with using rightscale (ssh in)

Public IPs will work with any of the network modes. FlatDHCP is a good one
to get started with.

You should be able to ssh directly to the public IP once you've associated
it with a VM (euca-associate-address).

I can't really speak to any potential problems with RightScale as I haven't
used it.

Everett

On Sun, May 8, 2011 at 1:01 PM, Michael G. <
<email address hidden>> wrote:

> Question #156597 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156597
>
> Status: Answered => Open
>
> Michael G. is still having a problem:
> Which network configuration should I use? how would it be possible then
> to ssh into instances? via vlan and vpn?
>
> thanks for your help.
>
> Could it be an issue just having one public ip? for example with using
> rightscale (ssh in)
>
> --
> You received this question notification because you are an answer
> contact for OpenStack Compute (nova).
>

I'm not sure, but I think you got the wrong impression of my question.
I asked for just one public ip for the whole cloud, not per vm. So I'm not sure yet how to ssh in to a vm and if there could be problems not ssh in via public ip.

And how I could use only one single ip.

Thanks for your help.

You're right, I got the wrong impression.

Two questions:

1. Do you want your cloud to be accessible to the outside world or just
within your own network?
2. Do you want your VMs to be accessible to the outside world or just within
your own network?

Maybe this will answer your question...you don't actually any public IPs at
all to run OpenStack within your own network. You can get along just fine
using private IPs only.

Everett

On Tue, May 10, 2011 at 2:15 AM, Michael G. <
<email address hidden>> wrote:

> Question #156597 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156597
>
> Status: Answered => Open
>
> Michael G. is still having a problem:
> I'm not sure, but I think you got the wrong impression of my question.
> I asked for just one public ip for the whole cloud, not per vm. So I'm not
> sure yet how to ssh in to a vm and if there could be problems not ssh in via
> public ip.
>
> And how I could use only one single ip.
>
> Thanks for your help.
>
> --
> You received this question notification because you are an answer
> contact for OpenStack Compute (nova).
>

On May 11, 2011, at 8:15 AM, Everett Toews wrote:

>
> Maybe this will answer your question...you don't actually any public IPs at
> all to run OpenStack within your own network. You can get along just fine
> using private IPs only.
>

You can also set up a route on external computers to get to the private ips by specifying the ip of the host running nova-network as a gateway. If nova network is running on 99.99.99.1 and you are using 10.x range for your vms, a command like the following would allow you to route to them:

route add -net 10.0.0.0/8 gw 99.99.99.1

Vish