Hi,
This is now implemented in master and ready for the next release, in
case you need to grab this asap.
Also you can use now user data in context as described in
http://www.opennebula.org/documentation:rel3.2:cong#defining_context
This comes in handy to store and inject user specific data (e.g. ssh
keys) in the VM at boot time.
Cheers
Ruben
On Fri, Dec 9, 2011 at 5:27 PM, Ruben S. Montero
rsmont...@opennebula.org wrote:
Hi,
Yes you are right, but it seems that the changes were not reverted for
the context attribute It'll be included for 3.2
THANKS for the heads up
Ruben
On Fri, Dec 9, 2011 at 5:15 PM, Thomas Higdon thig...@akamai.com wrote:
On Fri, Dec 09, 2011 at 10:13:55AM -0600, Fabian Wenk wrote:
Hello Tomá?
On 09.12.2011 10:42, Tomá? Nechutný wrote:
possible to define network by name (instead of id)? I tried
NETWORK=local, NETWORK=\local\ and same with NAME instead of
NETWORK_ID=1, but it doesn't work.
As far as I know with OpenNebula 3.0 only IDs can be uses.
I can confirm for 3.0, but 3.1/3.2 has re-added the ability to specify
this by name.
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula
--
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
