You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Piers <pi...@rowan.id.au> on 2014/09/06 13:13:20 UTC
Advanced Networking with limited IP Addresses
Hi there,
My problem is that I want to achieve a maximum use of our public IP
range for VM's. We only have a /27 at this stage and there are some
other servers in use already.
After using the CentOS set up guide a few times we could get things
going but that basically used up our range or caused other problems [1].
Ideally I would like to generate private ranges for the VM guests and
attach them to public IP's as required (something I am under the
impression that Cloudstack can do ).
Please bear in mind I have done the initial set up many, many times but
with slight differences in selections trying to achieve this but run
into road blocks. This time I have ignored the auto set up and created a
zone manually. This has given me a set up with:
cloud0 Link encap:Ethernet HWaddr
inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
cloudbr0 Link encap:Ethernet HWaddr 00:30:48:FC:6B:B4
inet addr: X.X.X.X Bcast:X.X.X.0 Mask:255.255.255.224
eth0 (is the bridged physical interface)
Does my cloudbr0 having a public IP mean that I have to do something
different to the install process?
Is cloud0 a remnant of previous set ups or can/should the local guest
network hang in this range?
I'm not looking for someone to spoon feed me the answers (because I need
to maintain this set up myself) but I feel like I have misunderstood
something crucial.
The install or set up pointers I am after is to achieve:
X.X.X.X is a public IP with a NFS server on it (single machine set up).
I want the management & storage networks to be virtual and private.
I want to be able to allocate X.X.X.17 -> VM (169.254.0.26).
[1] The CentOS how to points at every VM being on the same {public}
range as the host. When set up this way the SSVM's were reported to
contribute in a DNS DDoS.
Sorry for all the typing but I am keen to learn more.
Thanks
Piers
Re: Advanced Networking with limited IP Addresses
Posted by Piers <pi...@rowan.id.au>.
On 06/09/14 22:47, Geoff Higginbottom wrote:
> Piers,
>
> I'm guessing you've been creating a Basic Networking Zone as the default wizard sends you in that direction.
Yep - right up until the most recent set up.
> If you have limited public IPs, and also want to leverage the full power of CloudStack you should create an Advanced network zone. This will give you private guest networks with a Virtual Router. Guest VMs will have private IPs and the VR will have a Public IP.
This is what I treid to do - what name should I give to the virtual
networks? Do they have to exist already or will cloudstack create them?
> If you need some VMs to have a Public IP directly assigned you can also create a Shared Network and allocate it a Public IP Range.
That is the plan thanks.
> There are some great blog articles on http://www.shapeblue.com which will help you understand the options etc.
I have had a look but couldn't see a specific how-to but will note the
site for future reference.
Thank you
Piers
Re: Advanced Networking with limited IP Addresses
Posted by Geoff Higginbottom <ge...@shapeblue.com>.
Piers,
I'm guessing you've been creating a Basic Networking Zone as the default wizard sends you in that direction.
If you have limited public IPs, and also want to leverage the full power of CloudStack you should create an Advanced network zone. This will give you private guest networks with a Virtual Router. Guest VMs will have private IPs and the VR will have a Public IP.
If you need some VMs to have a Public IP directly assigned you can also create a Shared Network and allocate it a Public IP Range.
There are some great blog articles on http://www.shapeblue.com which will help you understand the options etc.
We also offer training sessions, again details are on the web site.
Regards
Geoff Higginbottom
CTO / Cloud Architect
D: +44 20 3603 0542<tel:+442036030542> | S: +44 20 3603 0540<tel:+442036030540> | M: +447968161581<tel:+447968161581>
geoff.higginbottom@shapeblue.com<ma...@shapeblue.com> | www.shapeblue.com<htp://www.shapeblue.com/> | Twitter:@cloudstackguru<https://twitter.com/#!/cloudstackguru>
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS<x-apple-data-detectors://5>
On 6 Sep 2014, at 12:13, "Piers" <pi...@rowan.id.au>> wrote:
Hi there,
My problem is that I want to achieve a maximum use of our public IP range for VM's. We only have a /27 at this stage and there are some other servers in use already.
After using the CentOS set up guide a few times we could get things going but that basically used up our range or caused other problems [1].
Ideally I would like to generate private ranges for the VM guests and attach them to public IP's as required (something I am under the impression that Cloudstack can do ).
Please bear in mind I have done the initial set up many, many times but with slight differences in selections trying to achieve this but run into road blocks. This time I have ignored the auto set up and created a zone manually. This has given me a set up with:
cloud0 Link encap:Ethernet HWaddr
inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
cloudbr0 Link encap:Ethernet HWaddr 00:30:48:FC:6B:B4
inet addr: X.X.X.X Bcast:X.X.X.0 Mask:255.255.255.224
eth0 (is the bridged physical interface)
Does my cloudbr0 having a public IP mean that I have to do something different to the install process?
Is cloud0 a remnant of previous set ups or can/should the local guest network hang in this range?
I'm not looking for someone to spoon feed me the answers (because I need to maintain this set up myself) but I feel like I have misunderstood something crucial.
The install or set up pointers I am after is to achieve:
X.X.X.X is a public IP with a NFS server on it (single machine set up).
I want the management & storage networks to be virtual and private.
I want to be able to allocate X.X.X.17 -> VM (169.254.0.26).
[1] The CentOS how to points at every VM being on the same {public} range as the host. When set up this way the SSVM's were reported to contribute in a DNS DDoS.
Sorry for all the typing but I am keen to learn more.
Thanks
Piers
Find out more about ShapeBlue and our range of CloudStack related services
IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge - rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.