Right now you can use one of these two methods: 1) Add several address ranges with different gateways. For example:
$ onevnet addar net --ip 10.0.0.100 --size 10 $ onevnet addar net --ip 10.0.1.100 --size 10 To change the gateways you can use updatear: $ onevnet updatear net 0 GATEWAY=10.0.0.1 $ onevnet updatear net 1 GATEWAY=10.0.1.1 Depending on the IP it the VM gets will use one gateway or the other. 2) Disable gateway configuration. To do this you can use GATEWAY_IFACE parameter. This tells the nic that is going to be used as default gateway. Setting it to a non existing interface will disable its configuration. For example: CONTEXT=[ NETWORK="YES", GATEWAY_IFACE=99 ] Cheers On Mon, Dec 29, 2014 at 8:19 PM, Laurent Grawet <openneb...@grawet.be> wrote: > Hi, > > The following is related to Request #3382 - Context: Overriding network > variables in context section - http://dev.opennebula.org/issues/3382 > > We are trying to define/redefine some network variables inside the VM > template. This is necessary for us because we are running different > load-balancers in the same network. So the default gateway may vary from one > VM to another. > > Is there any way to manage this use case with one+cloud-init ? Until now we > are forced to deactivate network contextualization after first boot to > customize network setup inside the VM. > > Many thanks, > > Laurent Grawet > > _______________________________________________ > Dev mailing list > Dev@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/dev-opennebula.org > -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan _______________________________________________ Dev mailing list Dev@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/dev-opennebula.org
