Thanks! I'll take a look at it and test it in other distros.
On Thu, Apr 24, 2014 at 8:00 AM, Michael Kutzner
<michael.kutz...@virtion.de> wrote:
> Hi Javier,
>
>
> Am 23.04.2014 um 21:18 schrieb Javier Fontan <jfon...@opennebula.org>:
>
>> Network restart is not supported in ubuntu. There is new code to
>> overcome this issue but we are still testing the packages. A package
>> with the latest code is attached if you want to try. You can install
>> it over the previous version.
>
> I run into the same problem today and tried to figure out
> what could be a way also to included fixed interfaces configured
> in /etc/network/interfaces.d.
>
> So, I slightly changed at the end of 00-network (from configure_network on)
> == snip ==
> configure_network()
> {
> gen_network_configuration > /etc/network/interfaces
> echo "source /etc/network/interfaces.d/*.cfg" >> /etc/network/interfaces
> }
>
> deactivate_network()
> {
> . /etc/os-release
> if [ $ID = "ubuntu" ]; then
> IFACES=`/sbin/ifquery -la`
>
> for i in $IFACES; do
> DEV=`get_dev $i`
> /sbin/ifdown $i
> done
> else
> service networking stop
> fi
> }
>
> activate_network()
> {
> . /etc/os-release
> if [ $ID = "ubuntu" ]; then
> IFACES=`/sbin/ifquery -la`
>
> for i in $IFACES; do
> DEV=`get_dev $i`
> /sbin/ifup $i
> done
> else
> service networking stop
> sleep 1
> service networking start
> fi
>
> sleep 2
> }
>
> deactivate_network
> configure_network
> activate_network
> == snip ==
>
> That works fine for me - especially in a mixed setup where I want to
> use the context on the one hand, but have the need to configure alias
> interfaces on the other hand (which is only handy on a VM with a
> fixed configuration).
>
> What I did not check yet if that influences somehow any other kind of
> package (relying on existing interfaces)
>
> Best, Michael
>
>
>
>>
>>
>>
>> On Wed, Apr 23, 2014 at 8:26 PM, ML mail <mlnos...@yahoo.com> wrote:
>>> Hello,
>>>
>>> I just generated a KVM qcow2 image for the new Ubuntu Server 14.04 LTS
>>> release. I usually prepare my images by simply installing the the ONE
>>> context package
>>> (http://dev.opennebula.org/attachments/download/768/one-context_4.5.0.deb)
>>> which I also did for this image.
>>>
>>>
>>> Now when I deploy a VM using this image on the very first boot the network
>>> is not working, although the /etc/network/interafaces gets correctly setup
>>> by the ONE context package an "ifconfig eth0" shows no IP addresses
>>> assigned to the interface. Also a "service networking restart" does not
>>> work. The only workaround I found for now is to reboot the VM, then
>>> networking works correctly.
>>>
>>> Is it possible that this is an issue related to the ONE context package? or
>>> simply some new networking code that Ubuntu 14.04 might have added or
>>> modified?
>>>
>>>
>>> Regards
>>> ML
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users@lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>>
>> --
>> Javier Fontán Muiños
>> Developer
>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>> <one-context_4.5.85.deb>_______________________________________________
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
--
Javier Fontán Muiños
Developer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | @OpenNebula | github.com/jfontan
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
