[one-users] reg oneflow - service template

[Carlos Martín Sánchez]

Hi,

On Fri, Dec 13, 2013 at 2:53 AM, Rajendar K <k.rajendar at 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, YYYY-MM-DD.

Regards.
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Fri, Dec 13, 2013 at 2:53 AM, Rajendar K <k.rajendar at 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 <
> cmartin at opennebula.org> wrote:
>
>> Hi,
>>
>> On Wed, Dec 4, 2013 at 2:40 AM, Rajendar K <k.rajendar at 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 <
>>> cmartin at opennebula.org> wrote:
>>>
>>>> Hi,
>>>>
>>>>  On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K <k.rajendar at 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/> | cmartin at opennebula.org
>>  | @OpenNebula <http://twitter.com/opennebula>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20131213/7dda38dd/attachment-0002.htm>