Feature #189

Template variables should allow cross reference like CONTEXT does

Added by Tino Vázquez almost 11 years ago. Updated about 10 years ago.

Status:ClosedStart date:01/27/2010
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

100%

Category:Core & System
Target version:Release 2.0
Resolution: Pull request:

Description

This will potentially enable a wider a richer use of OpenNebula. For example, marrying the VNC port with the VM ID.


Related issues

Related to Feature #197: Custom Network Context Attributes Closed 03/01/2010

Associated revisions

Revision 28e9d41a
Added by Ruben S. Montero over 10 years ago

feature #189: Moved attribute parsing to VirtualMachine class (get rid of cross references). Added Requirements parsing and initial vnc_port generation

Revision ec6b21ef
Added by Ruben S. Montero over 10 years ago

feature #189: Added VNC_BASE_PORT to the configuration file, and PORT generation

Revision 3366abdb
Added by Ruben S. Montero over 10 years ago

feature #189: Support to access NETWORK templates in VM CONTEXT (e.g. $NETWORK[DNS])

Revision 9311f27b
Added by Daniel Molina over 10 years ago

feature #189 Added info to CONTEXT and REQUIREMENTS template schema

History

#1 Updated by Ruben S. Montero almost 11 years ago

  • Target version set to Release 1.4.2

Hi,

Looking at the attributes we do not need to use this cross parsing for all the variables (e.g. OS, DISK). Right now we have this for CONTEXT and for the REQUIREMENTS in a development branch. (For example you can do something like REQUIREMENTS = $NIC[MAC] = MACS, if you have a custom probe that generates a MACS attribute for the hosts you can do short of a MAC pinning, so only VMs with a given MAC runs in a given host)

My proposal: default generation values for port and listen in GRAPHICS. So if you do not put a port, OpenNebula will automatically assign 5900+$VMID, and if you do not put a listen OpenNebula will automatically HOSTNAME of the host where the VM is placed.

Ruben

#2 Updated by Ruben S. Montero almost 11 years ago

  • Category set to Core & System

#3 Updated by Ruben S. Montero almost 11 years ago

  • Tracker changed from Bug to Feature

#4 Updated by Ruben S. Montero over 10 years ago

  • Assignee set to Ruben S. Montero
  • Target version changed from Release 1.4.2 to Release 2.0

#5 Updated by Ruben S. Montero over 10 years ago

This ticket will include the following variable parsing/generation functionality for OpenNebula templates:

  • Substitution of template variables in the REQUIREMENTS attribute
  • Automatic generation of PORT as VMID + VNC_BASE_PORT. This should be enough to generate different ports for VMs so they do not collide
  • Parsing of network attributes in CONTEXT. Network variables can be referenced as $NETWORK[...], see the mailing list for more info

Ruben

#6 Updated by Ruben S. Montero over 10 years ago

  • % Done changed from 0 to 80

This is now ready in the feature-189 branch. Needs more testing and the documentation has to be updated.

#7 Updated by Ruben S. Montero over 10 years ago

  • % Done changed from 80 to 90

This feature is now in master, the documentation has been updated and it is ready for the RC... moving to 90%

#8 Updated by Daniel Molina about 10 years ago

  • Status changed from New to Closed
  • % Done changed from 90 to 100

Also available in: Atom PDF