Thanks for sharing!,... I've filled a ticket to track and implement this<div><br></div><div><a href="http://dev.opennebula.org/issues/602" target="_blank">http://dev.opennebula.org/issues/602</a></div><div><br></div><div>
Cheers</div><div>
<br></div><div>Ruben<br><br><div class="gmail_quote">On Fri, Apr 29, 2011 at 10:36 PM, Lars Kellogg-Stedman <span dir="ltr"><<a href="mailto:lars@seas.harvard.edu" target="_blank">lars@seas.harvard.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>> To improve this, we can extend the parameters to define the ranged network,<br>
> e.g. with the starting ip address parameter. Or alternatively, define a<br>
> fixed net using single leases and/or continuous ranges of leases. Which one<br>
> is better?<br>
<br>
</div>I think that RANGED networks are ultimately easier to manage than a<br>
FIXED network. I would like, for example, to create several small<br>
"networks" out of a larger block of addresses...for example, taking<br>
<a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a> and dividing it up into:<br>
<br>
- 10.10.10.10 - 10.10.10.30<br>
- 10.10.10.31 - 10.10.10.100<br>
- etc...<br>
<br>
It's certainly possible to do this using FIXED networks and generated<br>
leases, but it's somewhat less convenient and doesn't really lend<br>
itself to management via the web interface.<br>
<br>
This would require the ability to specify a base address for each<br>
"network", as well as the the number of addresses to provision. So<br>
something like this:<br>
<br>
NAME=cloud<br>
TYPE=RANGED<br>
BRIDIGE=br619<br>
NETWORK_BASE=10.10.10.10<br>
NETWORK_SIZE=30<br>
<br>
Ideally, I would like to be able to specify the network using any of<br>
the following:<br>
<br>
- An address mask:<br>
NETWORK_ADDRESS=<a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a><br>
<br>
- An address and mask as octets:<br>
NETWORK_ADDRESS=<a href="http://10.10.10.0/255.255.255.0" target="_blank">10.10.10.0/255.255.255.0</a><br>
<br>
- A base and size:<br>
NETWORK_BASE=10.10.10.1<br>
NETWORK_SIZE=253<br>
<br>
(where the first address allocated is NETWORK_BASE, and the last<br>
address allocated is NETWORK_BASE+NETWORK_SIZE).<br>
<br>
It would also be nice to be able to "reserve" addresses on a ranged<br>
network. For example, we have a /24 dedicated to our OpenNebula<br>
cluster right now, except there are two legacy hosts sitting there<br>
from a previous virtualization experiment. It would be great if I<br>
could do this:<br>
<br>
NETWORK_ADDRESS=<a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a><br>
RESERVED=[10.10.10.1, 10.10.10.254, 10.10.10.253]<br>
<br>
...or something like that.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div>Lars Kellogg-Stedman <<a href="mailto:lars@seas.harvard.edu" target="_blank">lars@seas.harvard.edu</a>><br>
Senior Technologist<br>
Harvard University SEAS<br>
Academic and Research Computing (ARC)<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dr. Ruben Santiago Montero<br>Associate Professor (Profesor Titular), Complutense University of Madrid<br><br>URL: <a href="http://dsa-research.org/doku.php?id=people:ruben" target="_blank">http://dsa-research.org/doku.php?id=people:ruben</a><br>
Weblog: <a href="http://blog.dsa-research.org/?author=7" target="_blank">http://blog.dsa-research.org/?author=7</a><br>
</div>