Re: [one-users] reg oneflow - service template
Hi,
On Fri, Dec 13, 2013 at 2:53 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
Thanks for your mail. Still my doubt is
*(QUERY 1) How to know about that the counter has been reset, is there any
log files which makes entry? *
*We can see only the log stating how many times the the statement is true,
as seen below*
*ADJUST EXPRESSION EVALS
PERIOD COOL*
*+ 1 CPU[0.0] 60
13 / 3s 60s*
We don't log when the expression evaluates to false, but the code is in
ruby so you can easily add any log you need.
*(QUERY 2) Can you specify the time format used for scheduled policy -
start time?*
It's flexible, but to be safe you can use ISO 8601, -MM-DD.
Regards.
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmar...@opennebula.org |
@OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org
On Fri, Dec 13, 2013 at 2:53 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
Thanks for your mail. Still my doubt is
On Tue, Dec 10, 2013 at 2:15 AM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Wed, Dec 4, 2013 at 2:40 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
Thanks for the mail. Here are my queries,
On Tue, Dec 3, 2013 at 7:52 PM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K k.rajen...@gmail.com
wrote:
Hi Carlos,
I have updated the files [oneflow-templates and
service] as per your instructions. Hereby specify the output of oneflow
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is
being employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
],
scheduled_policies: [
]
}
kindly provide detail on how auto-scaling is happened in the above
sample, with relates to period_number , period and cooldown
The period_number, period and cooldown attributes are explained in
detail in the documentation [1].
In your example, the expression CPU 60 must be true 30 times, each 3
seconds.
*So the scaling should be triggered after 1.30 minutes (30 * 3 seconds)
(90 seconds) is it right?*
*The log shows that scaling is triggered after 16 minutes,*
LOG MESSAGES
12/02/13 10:06 [I] New state: DEPLOYING
*12/02/13 10:07 [I] New state: RUNNING*
*12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes*
12/02/13 10:22 [I] New state: SCALING
12/02/13 10:23 [I] New state: COOLDOWN
12/02/13 10:23 [I] New state: RUNNING
*12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes*
12/02/13 10:38 [I] New state: SCALING
12/02/13 10:39 [I] New state: COOLDOWN
12/02/13 10:39 [I] New state: RUNNING
The role will scale up *if the expression is true* those 90 seconds.
When the expression is false, the counter is reset.
*(QUERY 1) How to know about that the counter has been reset, is there any
log files which makes entry? *
*We can see only the log stating how many times the the statement is true,
as seen below*
*ADJUST EXPRESSION EVALS
PERIOD COOL*
*+ 1 CPU[0.0] 60
13 / 3s 60s*
*(QUERY 2) Can you specify the time format used for scheduled policy -
start time?*
After the scaling, your service will be in the cooldown period for 30
seconds before returning to running. The only defined policy is overriding
the default cooldown of 60 that you set.
if my understanding is correct, if we didn't specify any cooldown for
each role , it takes the default policy as 60 using that parameter?
That's right, if you set a default cooldown for the service you can leave
it unset for the roles.
Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org
| @OpenNebula http://twitter.com/opennebula
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] reg oneflow - service template
Hi,
On Wed, Dec 4, 2013 at 2:40 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
Thanks for the mail. Here are my queries,
On Tue, Dec 3, 2013 at 7:52 PM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
I have updated the files [oneflow-templates and
service] as per your instructions. Hereby specify the output of oneflow
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is
being employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
],
scheduled_policies: [
]
}
kindly provide detail on how auto-scaling is happened in the above
sample, with relates to period_number , period and cooldown
The period_number, period and cooldown attributes are explained in detail
in the documentation [1].
In your example, the expression CPU 60 must be true 30 times, each 3
seconds.
*So the scaling should be triggered after 1.30 minutes (30 * 3 seconds)
(90 seconds) is it right?*
*The log shows that scaling is triggered after 16 minutes,*
LOG MESSAGES
12/02/13 10:06 [I] New state: DEPLOYING
*12/02/13 10:07 [I] New state: RUNNING*
*12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes*
12/02/13 10:22 [I] New state: SCALING
12/02/13 10:23 [I] New state: COOLDOWN
12/02/13 10:23 [I] New state: RUNNING
*12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes*
12/02/13 10:38 [I] New state: SCALING
12/02/13 10:39 [I] New state: COOLDOWN
12/02/13 10:39 [I] New state: RUNNING
The role will scale up *if the expression is true* those 90 seconds. When
the expression is false, the counter is reset.
After the scaling, your service will be in the cooldown period for 30
seconds before returning to running. The only defined policy is overriding
the default cooldown of 60 that you set.
if my understanding is correct, if we didn't specify any cooldown for each
role , it takes the default policy as 60 using that parameter?
That's right, if you set a default cooldown for the service you can leave
it unset for the roles.
Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org |
@OpenNebula http://twitter.com/opennebula
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] reg oneflow - service template
Hi,
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
I have updated the files [oneflow-templates and service]
as per your instructions. Hereby specify the output of oneflow
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is being
employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
],
scheduled_policies: [
]
}
kindly provide detail on how auto-scaling is happened in the above sample,
with relates to period_number , period and cooldown
The period_number, period and cooldown attributes are explained in detail
in the documentation [1].
In your example, the expression CPU 60 must be true 30 times, each 3
seconds.
After the scaling, your service will be in the cooldown period for 30
seconds before returning to running. The only defined policy is overriding
the default cooldown of 60 that you set.
In a previous email you mentioned:
On Fri, Nov 29, 2013 at 5:19 AM, Rajendar K k.rajen...@gmail.com wrote:
(ii) Scheduled policies
- For my trial i have specified
start time - 2013-11-29 10:30:30
is my time format is correct? unable to scale up/down
using this time format.
But the output you provided does not have any scheduled_policies. Was that
another different template?
Regards.
[1] http://opennebula.org/documentation:rel4.4:appflow_elasticity
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org |
@OpenNebula http://twitter.com/opennebula cmar...@opennebula.org
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
I have updated the files [oneflow-templates and service]
as per your instructions. Hereby specify the output of oneflow
root@:/srv/cloud/one# oneflow show 179
SERVICE 179
INFORMATION
ID : 179
NAME: Sampletest
USER: root
GROUP : oneadmin
STRATEGY: straight
SERVICE STATE : RUNNING
SHUTDOWN: shutdown
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
ROLE role1
ROLE STATE : RUNNING
VM TEMPLATE : 590
CARNIDALITY : 3
MIN VMS : 1
MAX VMS : 3
COOLDOWN: 60s
SHUTDOWN: shutdown
NODES INFORMATION
VM_ID NAMESTAT UCPUUMEM
HOST TIME
568 role1_0_(service_179) runn0 1024M 10.1.26.32 0d
01h24
569 role1_1_(service_179) runn0 1024M 10.1.26.31 0d
01h07
570 role1_2_(service_179) runn0 1024M 10.1.26.32 0d
00h51
ELASTICITY RULES
ADJUST EXPRESSION EVALS
PERIOD COOL
+ 1 CPU[0.0] 6030 /
3s 30s
LOG
MESSAGES
12/02/13 10:06 [I] New state: DEPLOYING
12/02/13 10:07 [I] New state: RUNNING
12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes
12/02/13 10:22 [I] New state: SCALING
12/02/13 10:23 [I] New state: COOLDOWN
12/02/13 10:23 [I] New state: RUNNING
12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes
12/02/13 10:38 [I] New state: SCALING
12/02/13 10:39 [I] New state: COOLDOWN
12/02/13 10:39 [I] New state: RUNNING
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is being
employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
],
scheduled_policies: [
]
}
kindly provide detail on how auto-scaling is happened in the above sample,
with relates to period_number , period and cooldown
with regards
Raj
Raj,
Believe Yourself...
On Sat, Nov 30, 2013 at 2:19 AM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Fri, Nov 29, 2013 at 5:19 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi All,
I am using opennebula 4.2, i have the following
queries related to auto scaling features
(i) Even when conditions met, scaling up takes long time to trigger.
For my trial, I have used #periods 5 #period 30 cooldown
30
- i can able to c the values 5/5 in the log, and then it
crosses 16/5 in course of time
- Unable to trace down when it trigger actually.
hope it should trigger when it reaches 5/5 ?
This is a known bug, the period and period
Re: [one-users] reg oneflow - service template
Hi Carlos,
Thanks for the mail. Here are my queries,
On Tue, Dec 3, 2013 at 7:52 PM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
I have updated the files [oneflow-templates and
service] as per your instructions. Hereby specify the output of oneflow
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is
being employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
],
scheduled_policies: [
]
}
kindly provide detail on how auto-scaling is happened in the above
sample, with relates to period_number , period and cooldown
The period_number, period and cooldown attributes are explained in detail
in the documentation [1].
In your example, the expression CPU 60 must be true 30 times, each 3
seconds.
*So the scaling should be triggered after 1.30 minutes (30 * 3 seconds) (90
seconds) is it right?*
*The log shows that scaling is triggered after 16 minutes,*
LOG MESSAGES
12/02/13 10:06 [I] New state: DEPLOYING
*12/02/13 10:07 [I] New state: RUNNING*
*12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes*
12/02/13 10:22 [I] New state: SCALING
12/02/13 10:23 [I] New state: COOLDOWN
12/02/13 10:23 [I] New state: RUNNING
*12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes*
12/02/13 10:38 [I] New state: SCALING
12/02/13 10:39 [I] New state: COOLDOWN
12/02/13 10:39 [I] New state: RUNNING
After the scaling, your service will be in the cooldown period for 30
seconds before returning to running. The only defined policy is overriding
the default cooldown of 60 that you set.
if my understanding is correct, if we didn't specify any cooldown for each
role , it takes the default policy as 60 using that parameter?
In a previous email you mentioned:
On Fri, Nov 29, 2013 at 5:19 AM, Rajendar K k.rajen...@gmail.com wrote:
(ii) Scheduled policies
- For my trial i have specified
start time - 2013-11-29 10:30:30
is my time format is correct? unable to scale up/down
using this time format.
But the output you provided does not have any scheduled_policies. Was that
another different template?
Yes, its a different template
Regards.
[1] http://opennebula.org/documentation:rel4.4:appflow_elasticity
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org
| @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi Carlos,
I have updated the files [oneflow-templates and
service] as per your instructions. Hereby specify the output of oneflow
root@:/srv/cloud/one# oneflow show 179
SERVICE 179
INFORMATION
ID : 179
NAME: Sampletest
USER: root
GROUP : oneadmin
STRATEGY: straight
SERVICE STATE : RUNNING
SHUTDOWN: shutdown
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
ROLE role1
ROLE STATE : RUNNING
VM TEMPLATE : 590
CARNIDALITY : 3
MIN VMS : 1
MAX VMS : 3
COOLDOWN: 60s
SHUTDOWN: shutdown
NODES INFORMATION
VM_ID NAMESTAT UCPUUMEM
HOST TIME
568 role1_0_(service_179) runn0 1024M 10.1.26.32
0d 01h24
569 role1_1_(service_179) runn0 1024M 10.1.26.31
0d 01h07
570 role1_2_(service_179) runn0 1024M 10.1.26.32
0d 00h51
ELASTICITY RULES
ADJUST EXPRESSION EVALS
PERIOD COOL
+ 1 CPU[0.0] 6030 /
3s 30s
LOG
MESSAGES
12/02/13 10:06 [I] New state: DEPLOYING
12/02/13 10:07 [I] New state: RUNNING
12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes
12/02/13 10:22 [I] New state: SCALING
12/02/13 10:23 [I] New state: COOLDOWN
12/02/13 10:23 [I] New state: RUNNING
12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes
12/02/13 10:38 [I] New state: SCALING
12/02/13 10:39 [I] New state: COOLDOWN
12/02/13 10:39 [I] New state: RUNNING
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is
being employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
Re: [one-users] reg oneflow - service template
Hi Carlos,
I have updated the files [oneflow-templates and service]
as per your instructions. Hereby specify the output of oneflow
root@:/srv/cloud/one# oneflow show 179
SERVICE 179
INFORMATION
ID : 179
NAME: Sampletest
USER: root
GROUP : oneadmin
STRATEGY: straight
SERVICE STATE : RUNNING
SHUTDOWN: shutdown
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
ROLE role1
ROLE STATE : RUNNING
VM TEMPLATE : 590
CARNIDALITY : 3
MIN VMS : 1
MAX VMS : 3
COOLDOWN: 60s
SHUTDOWN: shutdown
NODES INFORMATION
VM_ID NAMESTAT UCPUUMEM HOST
TIME
568 role1_0_(service_179) runn0 1024M 10.1.26.32 0d
01h24
569 role1_1_(service_179) runn0 1024M 10.1.26.31 0d
01h07
570 role1_2_(service_179) runn0 1024M 10.1.26.32 0d
00h51
ELASTICITY RULES
ADJUST EXPRESSION EVALS PERIOD
COOL
+ 1 CPU[0.0] 6030 /
3s 30s
LOG
MESSAGES
12/02/13 10:06 [I] New state: DEPLOYING
12/02/13 10:07 [I] New state: RUNNING
12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes
12/02/13 10:22 [I] New state: SCALING
12/02/13 10:23 [I] New state: COOLDOWN
12/02/13 10:23 [I] New state: RUNNING
12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes
12/02/13 10:38 [I] New state: SCALING
12/02/13 10:39 [I] New state: COOLDOWN
12/02/13 10:39 [I] New state: RUNNING
= Elasticty conditions
min_vms: 1,
max_vms: 3,
* cooldown: 60, = At what period , this parameter is being
employed? *
elasticity_policies: [
{
type: CHANGE,
adjust: 1,
expression: CPU 60,
period: 3,
period_number: 30,
cooldown: 30
}
],
scheduled_policies: [
]
}
kindly provide detail on how auto-scaling is happened in the above sample,
with relates to period_number , period and cooldown
with regards
Raj
Raj,
Believe Yourself...
On Sat, Nov 30, 2013 at 2:19 AM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Fri, Nov 29, 2013 at 5:19 AM, Rajendar K k.rajen...@gmail.com wrote:
Hi All,
I am using opennebula 4.2, i have the following queries
related to auto scaling features
(i) Even when conditions met, scaling up takes long time to trigger.
For my trial, I have used #periods 5 #period 30 cooldown 30
- i can able to c the values 5/5 in the log, and then it
crosses 16/5 in course of time
- Unable to trace down when it trigger actually.
hope it should trigger when it reaches 5/5 ?
This is a known bug, the period and period number inputs in sunstone are
inverted [1].
To solve it, execute:
$ sudo wget
http://dev.opennebula.org/projects/opennebula/repository/revisions/5c7b370f6be5f4f9167d508bdd31b580f05dafd4/raw/src/sunstone/public/js/plugins/oneflow-templates.js-O
/usr/lib/one/sunstone/public/js/plugins/oneflow-templates.js
$ sudo wget
http://dev.opennebula.org/projects/opennebula/repository/revisions/970c34464a1d5a71f3a9dfdd3d77d62883400857/raw/src/sunstone/public/js/plugins/oneflow-services.js-O
/usr/lib/one/sunstone/public/js/plugins/oneflow-services.js
Or wait a few days and upgrade to OpenNebula 4.4 :)
(ii) Scheduled policies
- For my trial i have specified
start time - 2013-11-29 10:30:30
is my time format is correct? unable to scale up/down
using this time format.
Could you paste the output of oneflow show -j ?
(ii) is it like AND conditions, if i specify both (i) and (ii)?. I have
tried separately (i) and (ii) but still in-vain.
No, they do not interfere with each other. Each condition (time, metrics
expression) is evaluated independently.
Regards
[1] http://opennebula.org/documentation:rel4.2:known_issues
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org |
@OpenNebula http://twitter.com/opennebula
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] reg oneflow - service template
Hi All, I am using opennebula 4.2, i have the following queries related to auto scaling features (i) Even when conditions met, scaling up takes long time to trigger. For my trial, I have used #periods 5 #period 30 cooldown 30 - i can able to c the values 5/5 in the log, and then it crosses 16/5 in course of time - Unable to trace down when it trigger actually. hope it should trigger when it reaches 5/5 ? (ii) Scheduled policies - For my trial i have specified start time - 2013-11-29 10:30:30 is my time format is correct? unable to scale up/down using this time format. (ii) is it like AND conditions, if i specify both (i) and (ii)?. I have tried separately (i) and (ii) but still in-vain. Kindly help to have a clarification on this. with regards Raj Raj, Believe Yourself... On Fri, Oct 25, 2013 at 5:51 PM, Rajendar K k.rajen...@gmail.com wrote: Dear All, I am using opennebula 4. 2 and oneapps 3.9 . I would like to know how oneflow templates are stored and retrieved? Whether the oneflow template values are stored on database? Kindly provide me suggestions... with regards Raj, ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] reg oneflow - service template
Hi, On Mon, Oct 28, 2013 at 2:37 AM, Rajendar K k.rajen...@gmail.com wrote: Hi Carlos, Thanks for the mail. Yes, to explore functionality of both appstage and oneflow. with regards Raj Right. Then make sure you are using oneflow 4.2, the one included in OpenNebula, not in the oneapps package. Also bear in mind that appstage was discontinued, and it may not be 100% compatible with a 4.2 installation. May I ask why do you need to access the flow templates database? Is there some functionality missing in the API? Best regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org On Mon, Oct 28, 2013 at 2:37 AM, Rajendar K k.rajen...@gmail.com wrote: Hi Carlos, Thanks for the mail. Yes, to explore functionality of both appstage and oneflow. with regards Raj On Fri, Oct 25, 2013 at 6:57 PM, Carlos Martín Sánchez cmar...@opennebula.org wrote: Hi, On Fri, Oct 25, 2013 at 11:51 AM, Rajendar K k.rajen...@gmail.com wrote: Dear All, I am using opennebula 4. 2 and oneapps 3.9 . I would like to know how oneflow templates are stored and retrieved? Whether the oneflow template values are stored on database? Kindly provide me suggestions... with regards Raj, The oneflow templates are stored in the OpenNebula DB as generic Documents [1]. But oneapps was discontinued. OneFlow was merged to the main OpenNebula distribution, and AppMarket was released as a separate component. Perhaps you installed it because of Appstage? [1] http://opennebula.org/documentation:rel4.2:api#actions_for_document_management -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] reg oneflow - service template
Hi Carlos, Thanks for the mail. Yes, to explore functionality of both appstage and oneflow. with regards Raj On Fri, Oct 25, 2013 at 6:57 PM, Carlos Martín Sánchez cmar...@opennebula.org wrote: Hi, On Fri, Oct 25, 2013 at 11:51 AM, Rajendar K k.rajen...@gmail.com wrote: Dear All, I am using opennebula 4. 2 and oneapps 3.9 . I would like to know how oneflow templates are stored and retrieved? Whether the oneflow template values are stored on database? Kindly provide me suggestions... with regards Raj, The oneflow templates are stored in the OpenNebula DB as generic Documents [1]. But oneapps was discontinued. OneFlow was merged to the main OpenNebula distribution, and AppMarket was released as a separate component. Perhaps you installed it because of Appstage? [1] http://opennebula.org/documentation:rel4.2:api#actions_for_document_management -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] reg oneflow - service template
Dear All, I am using opennebula 4. 2 and oneapps 3.9 . I would like to know how oneflow templates are stored and retrieved? Whether the oneflow template values are stored on database? Kindly provide me suggestions... with regards Raj, ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] reg oneflow - service template
Hi, On Fri, Oct 25, 2013 at 11:51 AM, Rajendar K k.rajen...@gmail.com wrote: Dear All, I am using opennebula 4. 2 and oneapps 3.9 . I would like to know how oneflow templates are stored and retrieved? Whether the oneflow template values are stored on database? Kindly provide me suggestions... with regards Raj, The oneflow templates are stored in the OpenNebula DB as generic Documents [1]. But oneapps was discontinued. OneFlow was merged to the main OpenNebula distribution, and AppMarket was released as a separate component. Perhaps you installed it because of Appstage? [1] http://opennebula.org/documentation:rel4.2:api#actions_for_document_management -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
