The file with data of the context CD (context.sh) is generated by
OpenNebula daemon itself, not by a script, so this change is trickier.
There is already a ticket about it:
http://dev.opennebula.org/issues/3150
On Tue, Sep 16, 2014 at 5:22 AM, Marcin Stolarek ms...@icm.edu.pl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
I've noticed that when a network interface is added to running VM,
this doesn't change VM context, so even if VM is restarted this
network interface isn't configured via contextualization mechanism.
Should it be considered a bug? Where should I look to patch this issue?
I believe that there is a shell script which executes appropriate
commands on my physical host to add a network interface to vm, maybe
it's possible to add context modification to this script?
It won't change context of running machine, but in case of restart the
context will be changed and NIC configured appropriately.
cheers,
marcin
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iQEcBAEBAgAGBQJUF6zWAAoJEEjNHARke2+evFkIAL9oUFVYETSWMzAzN1O9Su6u
kWluAw7pahkShuv0GPEJcpoS70IbVvhLAmWLfHFcBgIBx1zhVMx9Q1SpNVUJmvuE
P4DZkEhioAnqig9L7fMkJyzexbuQg0omIszHXSJpEZSD8yYyPkab+A4KHGoY7DfB
2JwyGsgLhWOERHflCrZBHAJHyvMMBMPpo3BUg14vqhxsmCKD8pStUk8k47SZIVz4
kR8uZ1FptDEOD2FB7Y5MnpMtIxdrKdmyMQyeLvvv8WxGRCAasGijRaq5eh8sywRu
9CG0feoku2iVU6Jsb0SocDzOGyPNtpk+/0/TzGDnPMEWbrQHA5kevdQXDYfym3M=
=NpUt
-END PGP SIGNATURE-
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Javier Fontán Muiños
Developer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | @OpenNebula | github.com/jfontan
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
