On Wednesday, February 18, 2015, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> Please find a question inline.
>
> On Wed, Feb 11, 2015 at 7:27 PM, Imesh Gunaratne > wrote:
>
>> Hi Devs,
>>
>> Today we had a call on this topic and please find the summary of the
>> discussion below:
>>
>> - In Strato
Hi Imesh,
Please find a question inline.
On Wed, Feb 11, 2015 at 7:27 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> Today we had a call on this topic and please find the summary of the
> discussion below:
>
> - In Stratos 4.0.0 the deployment policy was defined in the global context
> and it was re
Great work Sajith! Thanks for the update!
On Wed, Feb 18, 2015 at 1:33 AM, Sajith Kariyawasam wrote:
> Hi Imesh,
>
> I have done following,
> * Update deployApplication operation in Autoscaler service to have
> application policy as an argument, instead of deployment policy. WSDLs ,
> stubs and
Hi Imesh,
I have done following,
* Update deployApplication operation in Autoscaler service to have
application policy as an argument, instead of deployment policy. WSDLs ,
stubs and Rest API is also updated
* Removed activeByDefault from NetworkPartitionBean and updating utility
methods used for
Great work Raj! Thanks for the update!
FYI: When you are doing changes please try to avoid any code clean ups in
this branch beacause it would be difficult for us to merge back to master
branch.
Thanks
On Tue, Feb 17, 2015 at 9:38 PM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> I have done the
Hi Imesh,
I have done the followings as part of the effort in this modification.
- implemented network partition management logic in CC and updated
relevant rest APIs and Service Clients
- implemented proper deployment policy validation
- fixed authorization action in some rest APIs
Hi Raj/Sajith,
Appreciate if you can provide an update on the progress we have made so far
with this modification.
Thanks
On Sun, Feb 15, 2015 at 10:40 PM, Imesh Gunaratne wrote:
> Hi Shaheed,
>
> Please find comments inline:
>
> On Sun, Feb 15, 2015 at 8:03 PM, Shaheedur Haque (shahhaqu) <
>
Hi Shaheed,
Please find comments inline:
On Sun, Feb 15, 2015 at 8:03 PM, Shaheedur Haque (shahhaqu) <
shahh...@cisco.com> wrote:
> OK, I think we are close. In the following reply, I am only concerned
> with the users view, not any Stratos internal concepts or names.
>
>
>
> I define an “appli
...@apache.org]
Sent: 15 February 2015 03:52
To: Shaheedur Haque (shahhaqu); dev
Subject: Re: 4.1 deployment policy questions
Hi Shaheed,
On Sun, Feb 15, 2015 at 12:09 AM, Shaheedur Haque (shahhaqu)
mailto:shahh...@cisco.com>> wrote:
Imesh, Gayan,
I look forward to the updated JSON samples; they w
Hi Shaheed,
On Sun, Feb 15, 2015 at 12:09 AM, Shaheedur Haque (shahhaqu) <
shahh...@cisco.com> wrote:
> Imesh, Gayan,
>
>
>
> I look forward to the updated JSON samples; they will no doubt help reduce
> confusion.
>
>
>
Yes we will send this ASAP.
> Just to comment briefly on the replies you
take advantage of D. (That seems a more
likely use case to me).
Now what is the sequence of steps?
Thanks, Shaheed
From: Imesh Gunaratne [mailto:im...@apache.org]
Sent: 13 February 2015 11:39
To: dev; Shaheedur Haque (shahhaqu)
Subject: Re: 4.1 deployment policy questions
Hi Shaheed,
Please
>
> *From:* Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* 13 February 2015 09:28
> *To:* dev; Shaheedur Haque (shahhaqu)
> *Subject:* Re: 4.1 deployment policy questions
>
>
>
> [Adding Shaheed]
>
>
>
> On Fri, Feb 13, 2015 at 8:31 AM, Imesh Gunaratne w
plementation.
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* 13 February 2015 09:28
> *To:* dev; Shaheedur Haque (shahhaqu)
> *Subject:* Re: 4.1 deployment policy questions
>
>
>
> [Adding Shaheed]
>
>
>
> On Fri, Feb 13, 2015 at 8:31 AM,
Thanks, I must have missed this thread before. CIL…but remember that I am
talking conceptually only as I don’t know the implementation.
From: Imesh Gunaratne [mailto:im...@apache.org]
Sent: 13 February 2015 09:28
To: dev; Shaheedur Haque (shahhaqu)
Subject: Re: 4.1 deployment policy questions
[Adding Shaheed]
On Fri, Feb 13, 2015 at 8:31 AM, Imesh Gunaratne wrote:
> I agree with Udara. We could take the following approach to improve the
> efficiency:
>
> 1. Implement deployment policy management logic and service methods in CC
> without affecting any other modules
> 2. Implement dpel
I agree with Udara. We could take the following approach to improve the
efficiency:
1. Implement deployment policy management logic and service methods in CC
without affecting any other modules
2. Implement dpeloyment policy management REST API methods, still this
would not affect any other module
Hi,
I started working on new branch. However it has lot of compilation
failures. I started fixing few, but there are many. It is true that we are
changing/adding some functionality which it is OK to functions not to work
properly. But we can avoid compilation issues IMO. We can change back end
fir
Hi Devs,
Following is a task breakdown for this mofication:
*Deploymenet Policy Management:*
- Introduce deployment policy management service methods in Cloud
Controller (CC). I believe deployment policies should reside in CC because
they contain IaaS related information.
- Introduce REST API me
Hi Devs,
Today we had a call on this topic and please find the summary of the
discussion below:
- In Stratos 4.0.0 the deployment policy was defined in the global context
and it was reusable.
- Now deployment policy is in application context and contains deployment
pattens of multiple cartridges.
+1 for the idea Lakmal! Yes I think it is better to have a call and discuss
this before doing any changes.
Thanks
On Wed, Feb 11, 2015 at 8:05 AM, Lakmal Warusawithana
wrote:
> Hi Shaheed,
>
> Will try to explain further but simple and here some workaround solution.
>
> Previous release we only
Shaheed, shall we go for a call and get this clear.
On Wed, Feb 11, 2015 at 8:05 AM, Lakmal Warusawithana
wrote:
> Hi Shaheed,
>
> Will try to explain further but simple and here some workaround solution.
>
> Previous release we only subscribe to a single cartridge with given
> deployment policy
Hi Shaheed,
Will try to explain further but simple and here some workaround solution.
Previous release we only subscribe to a single cartridge with given
deployment policy. We have re used defined deployment policy. The main
reason that we cloud do, single cartridge has single deployment patten f
Yes, I agree with your concerns Shaheed! Please find my comments below:
On Wed, Feb 11, 2015 at 4:13 AM, Shaheed Haque wrote:
>
>
> OK, I get that argument. But consider that multiple subscriptions all
> using a single deployment spec was the previous model, and now we have
> inverted that cardi
Hi Shadeed,
A good question!
On Tue, Feb 10, 2015 at 11:45 PM, Shaheedur Haque (shahhaqu) <
shahh...@cisco.com> wrote:
> Hi,
>
> This is surely backwards. Why do deployment policies name the
> application? Why can’t a single deployment policy be referenced by multiple
> applications (just like
OK, I get that argument. But consider that multiple subscriptions all using a
single
deployment spec was the previous model, and now we have inverted that
cardinality
completely.
To my knowledge, in addition to the generic automation of single cartridge
subscriptions we provided our Stratos
An application definition defines cartridges and dependencies among the
cartridges, and few other stuff such as autoscaling etc. Deployment policy
defines how to deploy an application. Ideally application is defined once,
but it should be able to deploy differently by using different deployment
pol
Hi,
I am just looking at the new group/application mode, for 4.1, and I noticed
that the subscribablesInfo no longer contains a deploymentPolicy. For example,
from [1]:
"applicationId: "single_group_v1",
...
"subscribableInfo": {
"alias": "tom2group6",
"autoscalingPo
27 matches
Mail list logo
