New OpenStack instance - status

Kevin Fenzi kevin at scrye.com
Mon Mar 9 13:54:43 UTC 2015


On Mon, 09 Mar 2015 14:39:52 +0100
Miroslav Suchý <msuchy at redhat.com> wrote:

> 
> So it would be:
>   # 172.16.0.1/16 -- 172.21.0.1/20- Free to take
>   # 172.23.0.1/16 - free (but used by old cloud)
>   # 172.24.0.1/24 - RESERVED it is used internally for OS
>   # 172.25.0.1/20  - Cloudintern (172.25.0.1 - 172.25.15.254)
>   # 172.25.16.1/20 - infrastructure (172.25.16.1 - 172.25.31.254)
>   # 172.25.32.1/20 - persistent (172.25.32.1 - 172.25.47.254)
>   # 172.25.48.1/20 - transient (172.25.48.1 - 172.25.63.254)
>   # 172.25.64.1/20 - scratch (172.25.64.1 - 172.25.79.254)
>   # 172.25.80.1/20 - copr (172.25.80.1 - 172.25.95.254)
>   # 172.25.96.1/20 -- 172.25.240.1/20 - free
>   # 172.26.0.1/16 -- 172.31.0.1/16 - free
> 
> 
> Comments?

Sounds good to me. 

When we migrate from old->new we are going to have to deal with the
floating ips. I guess we could make the new openstack have the entire
range, then move those instances that expect to be at specific ips (and
they can claim them), then move the rest and give them just 'next ip'
in the external. 

Also, I'd like to reserve some externals for the other cloud. ie, once
we move to this new cloud, I want to keep say fed-cloud01/02 out and
redo them with juno or kilo or whatever so we can more quickly move to
a new cloud version if needed. 

I guess that should be something like: 

209.132.184:

.1 to .25 reserved for hardware nodes
26 to 30 reserved for 'test openstack' 
31-250 reserved for 'production openstack'

(and of course some instances may have specific ips in the production
range).

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150309/4d739208/attachment-0001.sig>


More information about the infrastructure mailing list