stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nirmal Fernando <nirmal070...@gmail.com>
Subject Re: adding the groupId to a member event ... RE: [Discuss] Grouping of services (cartridges)
Date Thu, 05 Jun 2014 02:46:01 GMT
Awesome!


On Thu, Jun 5, 2014 at 8:01 AM, Martin Eppel (meppel) <meppel@cisco.com>
wrote:

>  It worked,
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
>
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Wednesday, June 04, 2014 4:03 PM
>
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
>
>
>
>
> On Thu, Jun 5, 2014 at 3:24 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Ok, I see – I think I  don’t understand the correct process to add a new
> interface to the CloudController.
>
>
>
> Is this the correct procedure to develop the SOAP API for the could
> controller : ?
>
>
>
> 1.       Implement the new API in CloudControllerServiceImpl
>
> 2.       Recompile cloud controller project and patch the server
>
> 3.       Retrieve the wsdl (Cloudcontroller.wsdl) and place it in my
> build environment
>
> 3.2 place it in the corresponding service stub and replace the existing
> wsdl under src/main/resurces  and build the project.
>
>  4.       Implement the API in CloudControllerServiceClient, recompile
> all projects and redeploy binaries
>
>  Correct.
>
>
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Wednesday, June 04, 2014 2:34 PM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Hi Martin,
>
> That is a risky thing to do :-) I suggest you to start the product with
> your patch and then access the auto-generated wsdl using
> https://<host>:<port>/services/CloudControllerService?wsdl
>
>
>
> On Thu, Jun 5, 2014 at 1:31 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> I edited my changes manually …
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Wednesday, June 04, 2014 12:16 PM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> How did you generate the WSDL, Martin?
>
>
>
> On Thu, Jun 5, 2014 at 12:35 AM, Isuru Haththotuwa <isuruh@apache.org>
> wrote:
>
> Hi Martin,
>
> Can you send the locally built Cloud Controller jar (with your changes),
> so that we can try to generate the WSDL.
>
>
>
> On Thu, Jun 5, 2014 at 12:24 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> I patched it but still see the same issue, what’s the best way to debug
> this ?
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Wednesday, June 04, 2014 11:20 AM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> I remember you faced a similar issue earlier. So, just to make sure :-)
>
>
>
> On Wed, Jun 4, 2014 at 11:41 PM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> I recompiled all jars, generated the zips and installed the system from
> the installer zip files, you think it is still necessary ?
>
> (but I’ll  try anyway - recompile service stub and patch)
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Wednesday, June 04, 2014 10:58 AM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Can you try to patch the CC service stub to the running product and check?
>
>
>
> On Wed, Jun 4, 2014 at 11:18 PM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Here we go, see attached files:
>
>
>
> ServiceUtils invokes the API
>
> CloudControllerClient, CloudControllerServiceImpl for implementation
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Wednesday, June 04, 2014 9:45 AM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
>
>
>
>
> On Wed, Jun 4, 2014 at 10:14 PM, Nirmal Fernando <nirmal070125@gmail.com>
> wrote:
>
> I am sorry Martin, but it'll easy for me, if you can attach the code diff
> of CC component.
>
> Thanks.
>
>
>
> On Wed, Jun 4, 2014 at 10:07 PM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Attached to the email,
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Tuesday, June 03, 2014 10:20 PM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Can you please send a diff over?
>
>
>
> On Wed, Jun 4, 2014 at 10:46 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> No, but I modeled / followed the deployCartridgeDefinition API which I
> think passes a bean as parameter ?
>
>
>
> Is it required to define a bean ? Where and how ?
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Tuesday, June 03, 2014 8:57 PM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Hi Martin,
>
> Did you introduce a new bean class?
>
>
>
> On Wed, Jun 4, 2014 at 9:19 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Actually,
>
>
>
> Below are all the changes I made to the wsdl for the new API, all I want
> at this point is to pass a string parameter in the API:
>
>
>
>         <wsdl:operation name="deployCompositeApplicationDefinition">
>
>             <soap:operation
> soapAction="urn:deployCompositeApplicationDefinition"
> style="document"></soap:operation>
>
>             <wsdl:input>
>
>                 <soap:body use="literal"></soap:body>
>
>             </wsdl:input>
>
>             <wsdl:fault
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException">
>
>                 <soap:fault use="literal"
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException"></soap:fault>
>
>             </wsdl:fault>
>
>             <wsdl:fault
> name="CloudControllerServiceInvalidIaasProviderException">
>
>                 <soap:fault use="literal"
> name="CloudControllerServiceInvalidIaasProviderException"></soap:fault>
>
>             </wsdl:fault>
>
>         </wsdl:operation>
>
>
>
> <wsdl:operation name="deployCompositeApplicationDefinition">
>
>             <soap12:operation
> soapAction="urn:deployCompositeApplicationDefinition"
> style="document"></soap12:operation>
>
>            <wsdl:input>
>
>                 <soap12:body use="literal"></soap12:body>
>
>             </wsdl:input>
>
>             <wsdl:fault
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException">
>
>                 <soap12:fault use="literal"
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException"></soap12:fault>
>
>             </wsdl:fault>
>
>             <wsdl:fault
> name="CloudControllerServiceInvalidIaasProviderException">
>
>                 <soap12:fault use="literal"
> name="CloudControllerServiceInvalidIaasProviderException"></soap12:fault>
>
>             </wsdl:fault>
>
>         </wsdl:operation>
>
>
>
>                                 <wsdl:operation
> name="deployCompositeApplicationDefinition">
>
>             <http:operation
> location="deployCompositeApplicationDefinition"></http:operation>
>
>             <wsdl:input>
>
>                 <mime:content type="text/xml"
> part="parameters"></mime:content>
>
>             </wsdl:input>
>
>         </wsdl:operation>
>
>
>
>
>
>                                 <xs:element
> name="deployCompositeApplicationDefinition">
>
>                 <xs:complexType>
>
>                     <xs:sequence>
>
>                         <xs:element minOccurs="0"
> name="compositeApplicationConfig" nillable="true"
> type="xs:string"></xs:element>
>
>                     </xs:sequence>
>
>                 </xs:complexType>
>
>             </xs:element>
>
>
>
>
>
>
>
>                                 <wsdl:message
> name="deployCompositeApplicationDefinitionRequest">
>
>         <wsdl:part name="parameters"
> element="ns:deployCompositeApplicationDefinition"></wsdl:part>
>
>     </wsdl:message>
>
>
>
>                 <wsdl:operation
> name="deployCompositeApplicationDefinition">
>
>             <wsdl:input
> message="ns:deployCompositeApplicationDefinitionRequest"
> wsaw:Action="urn:deployCompositeApplicationDefinition"></wsdl:input>
>
>             <wsdl:fault
> message="ns:CloudControllerServiceInvalidCompositeApplicationDefinitionException"
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException"
> wsaw:Action="urn:deployCompositeApplicationDefinitionCloudControllerServiceInvalidCompositeApplicationDefinitionException"></wsdl:fault>
>
>             <wsdl:fault
> message="ns:CloudControllerServiceInvalidIaasProviderException"
> name="CloudControllerServiceInvalidIaasProviderException"
> wsaw:Action="urn:deployCompositeApplicationDefinitionCloudControllerServiceInvalidIaasProviderException"></wsdl:fault>
>
>         </wsdl:operation>
>
>
>
>
>
>                                 <xs:element
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException">
>
>                 <xs:complexType>
>
>                     <xs:sequence>
>
>                         <xs:element minOccurs="0"
> name="InvalidCompositeApplicationDefinitionException" nillable="true"
> type="ax219:InvalidCompositeApplicationDefinitionException"></xs:element>
>
>                     </xs:sequence>
>
>                 </xs:complexType>
>
>             </xs:element>
>
>
>
>                                 <wsdl:message
> name="CloudControllerServiceInvalidCompositeApplicationDefinitionException">
>
>         <wsdl:part name="parameters"
> element="ns:CloudControllerServiceInvalidCompositeApplicationDefinitionException"></wsdl:part>
>
>     </wsdl:message>
>
>
>
> *From:* Martin Eppel (meppel)
> *Sent:* Tuesday, June 03, 2014 8:47 PM
> *To:* dev@stratos.apache.org
> *Cc:* dev@stratos.incubator.apache.org; Lakmal Warusawithana; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* RE: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Yes,
>
>
>
> I did add the new api in the cloudcontroller.wsdl and regenerated the stub
> (recompiled successfully all projects, including service-stub, etc …). The
> error happens during run time when I invoke the API, are there any debug
> traces I can turn on for axis which might help ?
>
>
>
>
>
>
>
> *From:* isuruh@wso2.com [mailto:isuruh@wso2.com] *On Behalf Of *Isuru
> Haththotuwa
> *Sent:* Tuesday, June 03, 2014 8:11 PM
> *To:* dev@stratos.apache.org
> *Cc:* dev@stratos.incubator.apache.org; Isuru Haththotuwa; Lakmal
> Warusawithana; Melan Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Hi Marin,
>
> If you have changed the CloudController interface, you will need to use
> the new cloud controller WSDL and re-generate the Cloud Controller service
> stub code. This error can be a result of this. Let me know if you have not
> done this so that I can give some guide lines.
>
>
>
> On Wed, Jun 4, 2014 at 8:21 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> When I invoke my soap API I get the following exception, what ‘s the best
> way to troublshoot / debug this ? What could be the issue ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> TID: [0] [STRATOS] [2014-06-04 02:30:40,030] ERROR
> {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -  Exception
> occurred while trying to invoke service method
> deployCompositeApplicationDefinition
> {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver}
>
> java.lang.ArrayIndexOutOfBoundsException: 1
>
>         at
> org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:639)
>
>         at
> org.apache.axis2.rpc.receivers.RPCUtil.processRequest(RPCUtil.java:153)
>
>         at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:206)
>
>         at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
>
>         at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>
>         at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>
>         at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>
>         at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>
>         at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>
>         at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>
>         at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>
>         at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>
>         at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>
>         at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>
>         at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>
>         at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>
>         at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>
>         at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>
>         at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>
>         at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>
>         at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>
>         at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>
>         at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>
>         at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>
>         at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>
>         at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>
>         at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>
>         at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>
>         at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>
>         at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>
>         at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>
>         at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>
>         at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>
>         at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>
>         at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>
>         at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>
>         at java.lang.Thread.run(Thread.java:745)
>
> TID: [0] [STRATOS] [2014-06-04 02:30:40,039] ERROR
> {org.apache.stratos.rest.endpoint.services.ServiceUtils} -  Exception
> occurred while trying to invoke service method
> deployCompositeApplicationDefinition
> {org.apache.stratos.rest.endpoint.services.ServiceUtils}
>
> org.apache.axis2.AxisFault: Exception occurred while trying to invoke
> service method deployCompositeApplicationDefinition
>
>         at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
>
>         at
> org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
>
>         at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
>
>         at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>
>         at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>
>         at
> org.apache.stratos.cloud.controller.stub.CloudControllerServiceStub.deployCompositeApplicationDefinition(CloudControllerServiceStub.java:389)
>
>         at
> org.apache.stratos.manager.client.CloudControllerServiceClient.deployCompositeApplicationDefinition(CloudControllerServiceClient.java:118)
>
>         at
> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployCompositeApplicationDefinition(ServiceUtils.java:227)
>
>         at
> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplication(ServiceUtils.java:198)
>
>         at
> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:120)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>
>
> *From:* Nirmal Fernando [mailto:nirmal070125@gmail.com]
> *Sent:* Tuesday, June 03, 2014 2:30 PM
> *To:* dev
> *Cc:* dev@stratos.incubator.apache.org; Isuru Haththotuwa; Lakmal
> Warusawithana; Melan Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: adding the groupId to a member event ... RE: [Discuss]
> Grouping of services (cartridges)
>
>
>
> Hi Martin,
>
> Who knows about this group id? Who's suppose to set it to the topology?
>
>
>
> On Wed, Jun 4, 2014 at 2:21 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Hi Isuru,
>
>
>
> As part of the grouping I need to add the groupId to a Member event (e.g.
> MemberStartedEvent, MemberActivatedEvent).
>
> Currently I added the composite application data  to the Topology by
> generating a event and respective event processor (similar to Service)
> which works fine for the autoscaler.
>
> However it seems that  the CloudController uses its own registry and the
> application info is missing when the topology is restored so it seems I
> have to push the application data also to the cloud controller.
>
> The only interface available seems to be the soap api
> (CloudControllerService.wsdl) which I would like to avoid (complicated and
> time intensive). Is there a better way to push the data, can I use a
> topology event, share the manager registry or do you have any other
> recommendations ?
>
> In case  the soap API is the only option, is there a better way to
> generate the CloudControllerService .wsdl or do I have to manually edit in
> my API changes ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Martin Eppel (meppel)
> *Sent:* Tuesday, May 20, 2014 9:15 AM
> *To:* Isuru Haththotuwa
> *Cc:* Lakmal Warusawithana; dev@stratos.incubator.apache.org; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* RE: [Discuss] Grouping of services (cartridges)
>
>
>
> Sounds good
>
>
>
> *From:* isuruh@wso2.com [mailto:isuruh@wso2.com] *On Behalf Of *Isuru
> Haththotuwa
> *Sent:* Tuesday, May 20, 2014 4:41 AM
> *To:* Martin Eppel (meppel)
> *Cc:* Lakmal Warusawithana; dev@stratos.incubator.apache.org; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: [Discuss] Grouping of services (cartridges)
>
>
>
> Hi Martin,
>
>
>
> On Tue, May 20, 2014 at 12:17 AM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Can you give me a quick json example to make sure I won’t misunderstand ?
>
> We would still be using the component JSON definitions as per your
> proposal, since if we put everything inline it would be one large JSON
> file. In the top level Composite Application Definition (which is the more
> appropriate name for subscription Plan, as suggested by Lakmal), you can
> refer the previously deployed groups by using the alias. So, the last
> example that you have given in the doc would be a valid JSON sample. Hope
> this is clear. Do let me know if its not.
>
>
>
>
>
>
>
> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
> *Sent:* Monday, May 19, 2014 11:33 AM
> *To:* Martin Eppel (meppel)
> *Cc:* dev@stratos.incubator.apache.org; Isuru Haththotuwa; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* Re: [Discuss] Grouping of services (cartridges)
>
>
>
>
>
>
>
> On Mon, May 19, 2014 at 11:55 PM, Martin Eppel (meppel) <meppel@cisco.com>
> wrote:
>
> Lakmal,
>
>
>
> A few clarifications:
>
>
>
> I think based on the last proposal we can consolidate the definition of
> components, dependencies in one definition and deploy all at once as
> subscription plan, correct (simplifies the deployment) ?
>
>
>
>
>
> Yes, but as the first step, will have separate deployers for groups,
> components and then composite application (which is you have mention
> subscription plan).
>
>
>
>  Also, Isuru pointed out that the term application might be  confusing so
> I suggested subscription plan (or something similar), do we still want to
> go with it ?
>
>
>
>
>
> What i suggest to call it composite application.
>
>
>
> And composite application can refer, previous deployed group, components.
> components can refer cartridge definitions. And dependancies (start order,
> kill order) should be defined in the top level, which is in composite
> application definition.
>
>
>
>
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Martin Eppel (meppel)
> *Sent:* Monday, May 19, 2014 10:58 AM
> *To:* Martin Eppel (meppel); Lakmal Warusawithana
> *Cc:* dev@stratos.incubator.apache.org; Isuru Haththotuwa; Melan
> Jayasingha; Shaheedur Haque (shahhaqu)
> *Subject:* RE: [Discuss] Grouping of services (cartridges)
>
>
>
> Sorry, hit the send button to soon:
>
>
>
> Ok, I’ll work on the deployment. I’ll send you guys the code as patch to
> checkin.
>
>
>
> Do we have already a planned date for 4.1 Milestone 1 ?
>
>
>
> Thanks
>
>
>
> ...
>
> [Message clipped]




-- 
Best Regards,
Nirmal

Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.

Blog: http://nirmalfdo.blogspot.com/

Mime
View raw message