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
wrote:
> Hi Dev
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
wrote:
> Hi
Hi Gayan,
On Thu, Apr 30, 2015 at 12:27 PM, Gayan Gunarathne 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
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 a
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://local
