You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Reka Thirunavukkarasu <re...@wso2.com> on 2015/04/30 07:44:09 UTC
Application update for cartridgeMin/cartridgeMax and groupInstanceMin/groupInstanceMax
Hi Devs,
$subject[1] has been implemented for beta2. You can modify the existing
application with any of the above parameters change and update it to
stratos using the below REST API command.
curl -X PUT -H "Content-Type: application/json" -d "@application.json" -k
-v -u admin:admin https://localhost:9443/api/applications
Only the instances count will get updated with the existing application.
The application structure and aliases should be same as the existing
application. Otherwise it will get validated in the update. We simply
ignore any other update that has been done in the application.
With this improvement, you can increase/decrease any of those values. That
will get picked up by the monitors in the immediate next iteration.
Please update the documentation accordingly...
[1] https://issues.apache.org/jira/browse/STRATOS-1340
Thanks,
Reka
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Application update for cartridgeMin/cartridgeMax and groupInstanceMin/groupInstanceMax
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi Vanson/Shaheed,
Please let me know, how the testing goes with this feature in your setup
with more real world use cases. So that we can fix, if there is any issue
as early as possible and include it for GA.
Thanks,
Reka
On Thu, Apr 30, 2015 at 11:14 AM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi Devs,
>
> $subject[1] has been implemented for beta2. You can modify the existing
> application with any of the above parameters change and update it to
> stratos using the below REST API command.
>
> curl -X PUT -H "Content-Type: application/json" -d "@application.json" -k
> -v -u admin:admin https://localhost:9443/api/applications
>
> Only the instances count will get updated with the existing application.
> The application structure and aliases should be same as the existing
> application. Otherwise it will get validated in the update. We simply
> ignore any other update that has been done in the application.
>
> With this improvement, you can increase/decrease any of those values. That
> will get picked up by the monitors in the immediate next iteration.
>
> Please update the documentation accordingly...
>
> [1] https://issues.apache.org/jira/browse/STRATOS-1340
>
> Thanks,
> Reka
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Application update for cartridgeMin/cartridgeMax and groupInstanceMin/groupInstanceMax
Posted by Gayan Gunarathne <ga...@wso2.com>.
Hi Reka,
Thank you for the clarifications.Yeah we can introduce validation with the
MAX values to secure the existing cluster over the update as mention below.
I think it will provide more stability in the existing deployment.
On Thu, Apr 30, 2015 at 12:52 PM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi Gayan,
>
> On Thu, Apr 30, 2015 at 12:27 PM, Gayan Gunarathne <ga...@wso2.com>
> wrote:
>
>> Hi Reka,
>>
>> This is a good improvement to the current set up. I have a small question.
>>
>> How are we validating the min/max in the case of update?
>>
>> Think if I have deployment of with 5 cartridges.(My min and max is 2 and
>> 5) This means it is fully scale up.
>>
>> Now I am changing to min and max to 2 and 3 and still we are getting
>> health stat , to increase the instance count. Then are we still allow this
>> min/max update or are we blocking this?
>>
>
> This is a good point. I believe that it is actually up to the application
> updater to handle it. If you decrease the max, then excess members will
> gracefully be shutting down. During that time, if the health stats is still
> high, then that particular cluster instance will be exhausted. In that
> case, it will notify the parent. So, if the parent has room or updated with
> more GroupInstances or Application has bursting support, then it will get
> group scale up or application bursting.
>
> Also, before updating the cartridge, they can go through the existing
> topology or instance count and come up with a good count to be updated. If
> the cluster is getting used at its max, then it is better to increase it
> rather than decreasing it..
>
>>
>> Are we validating any of these stuff?
>>
>
> Nope..We are not validating this currently. We can implement a validation
> as it will provide protection to the existing cluster. In that case, we can
> check the activeMembers count and let anyone update with the max as greater
> value than activeMembers. WDYT?
>
+1. IMO also that validation will provide more stability in the deployment.
> Thanks,
> Reka
>
>>
>> Thanks,
>> Gayan
>>
>>
>>
>> On Thu, Apr 30, 2015 at 11:14 AM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> $subject[1] has been implemented for beta2. You can modify the existing
>>> application with any of the above parameters change and update it to
>>> stratos using the below REST API command.
>>>
>>> curl -X PUT -H "Content-Type: application/json" -d "@application.json"
>>> -k -v -u admin:admin https://localhost:9443/api/applications
>>>
>>> Only the instances count will get updated with the existing application.
>>> The application structure and aliases should be same as the existing
>>> application. Otherwise it will get validated in the update. We simply
>>> ignore any other update that has been done in the application.
>>>
>>> With this improvement, you can increase/decrease any of those values.
>>> That will get picked up by the monitors in the immediate next iteration.
>>>
>>> Please update the documentation accordingly...
>>>
>>> [1] https://issues.apache.org/jira/browse/STRATOS-1340
>>>
>>> Thanks,
>>> Reka
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead
>> WSO2 Inc. (http://wso2.com)
>> email : gayang@wso2.com | mobile : +94 766819985
>>
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: Application update for cartridgeMin/cartridgeMax and groupInstanceMin/groupInstanceMax
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi Gayan,
On Thu, Apr 30, 2015 at 12:27 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
> Hi Reka,
>
> This is a good improvement to the current set up. I have a small question.
>
> How are we validating the min/max in the case of update?
>
> Think if I have deployment of with 5 cartridges.(My min and max is 2 and
> 5) This means it is fully scale up.
>
> Now I am changing to min and max to 2 and 3 and still we are getting
> health stat , to increase the instance count. Then are we still allow this
> min/max update or are we blocking this?
>
This is a good point. I believe that it is actually up to the application
updater to handle it. If you decrease the max, then excess members will
gracefully be shutting down. During that time, if the health stats is still
high, then that particular cluster instance will be exhausted. In that
case, it will notify the parent. So, if the parent has room or updated with
more GroupInstances or Application has bursting support, then it will get
group scale up or application bursting.
Also, before updating the cartridge, they can go through the existing
topology or instance count and come up with a good count to be updated. If
the cluster is getting used at its max, then it is better to increase it
rather than decreasing it..
>
> Are we validating any of these stuff?
>
Nope..We are not validating this currently. We can implement a validation
as it will provide protection to the existing cluster. In that case, we can
check the activeMembers count and let anyone update with the max as greater
value than activeMembers. WDYT?
Thanks,
Reka
>
> Thanks,
> Gayan
>
>
>
> On Thu, Apr 30, 2015 at 11:14 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> $subject[1] has been implemented for beta2. You can modify the existing
>> application with any of the above parameters change and update it to
>> stratos using the below REST API command.
>>
>> curl -X PUT -H "Content-Type: application/json" -d "@application.json" -k
>> -v -u admin:admin https://localhost:9443/api/applications
>>
>> Only the instances count will get updated with the existing application.
>> The application structure and aliases should be same as the existing
>> application. Otherwise it will get validated in the update. We simply
>> ignore any other update that has been done in the application.
>>
>> With this improvement, you can increase/decrease any of those values.
>> That will get picked up by the monitors in the immediate next iteration.
>>
>> Please update the documentation accordingly...
>>
>> [1] https://issues.apache.org/jira/browse/STRATOS-1340
>>
>> Thanks,
>> Reka
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Application update for cartridgeMin/cartridgeMax and groupInstanceMin/groupInstanceMax
Posted by Gayan Gunarathne <ga...@wso2.com>.
Hi Reka,
This is a good improvement to the current set up. I have a small question.
How are we validating the min/max in the case of update?
Think if I have deployment of with 5 cartridges.(My min and max is 2 and 5)
This means it is fully scale up.
Now I am changing to min and max to 2 and 3 and still we are getting health
stat , to increase the instance count. Then are we still allow this min/max
update or are we blocking this?
Are we validating any of these stuff?
Thanks,
Gayan
On Thu, Apr 30, 2015 at 11:14 AM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi Devs,
>
> $subject[1] has been implemented for beta2. You can modify the existing
> application with any of the above parameters change and update it to
> stratos using the below REST API command.
>
> curl -X PUT -H "Content-Type: application/json" -d "@application.json" -k
> -v -u admin:admin https://localhost:9443/api/applications
>
> Only the instances count will get updated with the existing application.
> The application structure and aliases should be same as the existing
> application. Otherwise it will get validated in the update. We simply
> ignore any other update that has been done in the application.
>
> With this improvement, you can increase/decrease any of those values. That
> will get picked up by the monitors in the immediate next iteration.
>
> Please update the documentation accordingly...
>
> [1] https://issues.apache.org/jira/browse/STRATOS-1340
>
> Thanks,
> Reka
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985