Feature #2965

OneFlow Service Names and Hooks

Added by James Horner over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:06/06/2014
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:duplicate Pull request:

Description

Hi There

It would be really useful if we could give services individual names, as per Templates and VMs.
The use case would be having a template LoadBalanced-WebApplication and being able to instantiate it as WebApp1 and WebApp2.

As an extension to this it would be useful to be able to pass the names and roles of VMs started to a hook script.
The use case would be that the hook would be able to update chef with this info.

Thanks


Related issues

Related to Backlog #2378: Hooks for OneFlow Services Pending 10/10/2013
Related to Feature #2123: Port features of templates and VMs to appflow Closed 06/13/2013

History

#1 Updated by Daniel Molina over 5 years ago

#2 Updated by Carlos Martín over 5 years ago

  • Related to Feature #2123: Port features of templates and VMs to appflow added

#3 Updated by Daniel Molina over 5 years ago

  • Tracker changed from Request to Feature
  • Status changed from Pending to Closed
  • Priority changed from Normal to High
  • Resolution set to duplicate

Hi James,

The first part of you request (service names) will be included in opennebula 4.8. Users will be able to provide a name for the new service and custom variables (i.e: mysql_password) that will be included in the CONTEXT section. These variables will be defined in the VM template and the user will have to provide them in the instantiate form.

We are also including a way to provide the network configuration for a given service. The admin will define how many network interfaces need the service and how each role is connected to them. The user will define what network is assigned for each interface in the instantiate form.

Hooks for OneFlow Services has been requested before, and we will try to consider it for future release.
As a workaround you can use VM Hooks and retrieve the service_id and role_name from the VM template. Also you can define the name that the new VMs will receive in the oneflow-server.conf
http://docs.opennebula.org/4.6/advanced_administration/application_flow_and_auto-scaling/appflow_configure.html#configuration

We are also extending the OneGate features for opennebula-4.8. Now a vm will be able to retrieve information of itself and the service it belongs to through OneGate.

Hope this helps

Also available in: Atom PDF