You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Pradeep Fernando <pr...@gmail.com> on 2014/03/12 18:31:47 UTC
Running stratos in one JVM
Hi Guys,
I started on the $subject. This thread is to track the progress..
thanks,
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
This is because, in service stub side, the databinding goes as,
public class InvalidPartitionException
implements org.apache.axis2.databinding.ADBBean{
and not extending/implementing throwable
On Fri, Mar 14, 2014 at 2:29 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Now i have a pack that has
>
> as/sm/cc
>
> and im getting below error. This is because client stubs and services are
> both reside in the same runtime and share the package structure.
>
> http://stackoverflow.com/questions/3438404/java-lang-verifyerror
>
>
>
> [2014-03-14 14:01:31,256] ERROR
> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> adding services from bundle :
> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> java.lang.VerifyError: (class:
> org/apache/stratos/cloud/controller/impl/CloudControllerServiceImpl,
> method: validatePartition signature:
> (Lorg/apache/stratos/cloud/controller/deployment/partition/Partition;)Z)
> catch_type not a subclass of Throwable
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> at
> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>
>
> On Thu, Mar 13, 2014 at 8:23 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> I was able to put together as/cc and sm.
>>
>> I'm encoutering following issue,
>>
>> even though there carbon kernel supports profiles, it does not support
>> config files per profiles.
>>
>> for an example SM host a webapp and thus has carbonWebappClassLoader in
>> catalina server.xml. Hence i have to install webapp mgt feature to other
>> profiles as well..
>>
>> thanks,
>> --Pradee
>>
>>
>>
>> On Thu, Mar 13, 2014 at 2:03 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> for the moment i'm ignoring caramel and jaggery features and moved
>>> forward. Provisioned initial profiles. (default and sm)
>>>
>>> next task,
>>>
>>> cc profile
>>> as profile
>>>
>>> full profile
>>>
>>>
>>> we have to fix caramel and jaggery features later
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:54 PM, Sameera Jayasoma <
>>> sameera.madushan@gmail.com> wrote:
>>>
>>>> How about using the "copy" action instead of the "mkdir" action? This
>>>> requires a change in the jaggery features though.
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Mar 13, 2014 at 12:50 PM, Pradeep Fernando <pradeepfn@gmail.com
>>>> > wrote:
>>>>
>>>>> its the modules directory created by jaggery/caramel features. its a
>>>>> top level directory. Ideally, the touchpoint should have a semantic to
>>>>> express, create if not exist.
>>>>> But for the moment i can call ant task and delete the directory after
>>>>> first round of provisioning...
>>>>>
>>>>> thanks,
>>>>> --Pradeep
>>>>>
>>>>>
>>>>> On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
>>>>> sameera.madushan@gmail.com> wrote:
>>>>>
>>>>>> Hi Pradeep,
>>>>>>
>>>>>> Can you provide a little more context to this problem? I.e. which
>>>>>> feature, which directory.. Trying to understand whether we can avoid
>>>>>> creating the directory?
>>>>>>
>>>>>> Thanks,
>>>>>> Sameera.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <
>>>>>> pradeepfn@gmail.com> wrote:
>>>>>>
>>>>>>> Encounter the first issue, :)
>>>>>>>
>>>>>>> Provisioning semantics fails to create a dir, when it already
>>>>>>> exists. Im taking about mkdir touchpoint found in eclipse.
>>>>>>> and there is not param to skip if exists it seems.
>>>>>>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>>>>>> Hopfully i can workaround it.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <
>>>>>>> pradeepfn@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Guys,
>>>>>>>>
>>>>>>>> I started on the $subject. This thread is to track the progress..
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Pradeep Fernando.
>>>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Pradeep Fernando.
>>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sameera Jayasoma
>>>>>>
>>>>>> blog: http://sameera.adahas.org
>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Pradeep Fernando.
>>>>> http://pradeepfernando.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sameera Jayasoma
>>>>
>>>> blog: http://sameera.adahas.org
>>>> twitter: https://twitter.com/sameerajayasoma
>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Sameera Jayasoma <sa...@gmail.com>.
This is wrong design IMO. To overcome this we may have to refactor this
code bit in Stratos.
Thanks,
Sameera.
On Fri, Mar 14, 2014 at 2:29 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Now i have a pack that has
>
> as/sm/cc
>
> and im getting below error. This is because client stubs and services are
> both reside in the same runtime and share the package structure.
>
> http://stackoverflow.com/questions/3438404/java-lang-verifyerror
>
>
>
> [2014-03-14 14:01:31,256] ERROR
> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> adding services from bundle :
> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> java.lang.VerifyError: (class:
> org/apache/stratos/cloud/controller/impl/CloudControllerServiceImpl,
> method: validatePartition signature:
> (Lorg/apache/stratos/cloud/controller/deployment/partition/Partition;)Z)
> catch_type not a subclass of Throwable
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> at
> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>
>
> On Thu, Mar 13, 2014 at 8:23 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> I was able to put together as/cc and sm.
>>
>> I'm encoutering following issue,
>>
>> even though there carbon kernel supports profiles, it does not support
>> config files per profiles.
>>
>> for an example SM host a webapp and thus has carbonWebappClassLoader in
>> catalina server.xml. Hence i have to install webapp mgt feature to other
>> profiles as well..
>>
>> thanks,
>> --Pradee
>>
>>
>>
>> On Thu, Mar 13, 2014 at 2:03 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> for the moment i'm ignoring caramel and jaggery features and moved
>>> forward. Provisioned initial profiles. (default and sm)
>>>
>>> next task,
>>>
>>> cc profile
>>> as profile
>>>
>>> full profile
>>>
>>>
>>> we have to fix caramel and jaggery features later
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:54 PM, Sameera Jayasoma <
>>> sameera.madushan@gmail.com> wrote:
>>>
>>>> How about using the "copy" action instead of the "mkdir" action? This
>>>> requires a change in the jaggery features though.
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Mar 13, 2014 at 12:50 PM, Pradeep Fernando <pradeepfn@gmail.com
>>>> > wrote:
>>>>
>>>>> its the modules directory created by jaggery/caramel features. its a
>>>>> top level directory. Ideally, the touchpoint should have a semantic to
>>>>> express, create if not exist.
>>>>> But for the moment i can call ant task and delete the directory after
>>>>> first round of provisioning...
>>>>>
>>>>> thanks,
>>>>> --Pradeep
>>>>>
>>>>>
>>>>> On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
>>>>> sameera.madushan@gmail.com> wrote:
>>>>>
>>>>>> Hi Pradeep,
>>>>>>
>>>>>> Can you provide a little more context to this problem? I.e. which
>>>>>> feature, which directory.. Trying to understand whether we can avoid
>>>>>> creating the directory?
>>>>>>
>>>>>> Thanks,
>>>>>> Sameera.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <
>>>>>> pradeepfn@gmail.com> wrote:
>>>>>>
>>>>>>> Encounter the first issue, :)
>>>>>>>
>>>>>>> Provisioning semantics fails to create a dir, when it already
>>>>>>> exists. Im taking about mkdir touchpoint found in eclipse.
>>>>>>> and there is not param to skip if exists it seems.
>>>>>>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>>>>>> Hopfully i can workaround it.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <
>>>>>>> pradeepfn@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Guys,
>>>>>>>>
>>>>>>>> I started on the $subject. This thread is to track the progress..
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Pradeep Fernando.
>>>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Pradeep Fernando.
>>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sameera Jayasoma
>>>>>>
>>>>>> blog: http://sameera.adahas.org
>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Pradeep Fernando.
>>>>> http://pradeepfernando.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sameera Jayasoma
>>>>
>>>> blog: http://sameera.adahas.org
>>>> twitter: https://twitter.com/sameerajayasoma
>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Sameera Jayasoma
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
Now i have a pack that has
as/sm/cc
and im getting below error. This is because client stubs and services are
both reside in the same runtime and share the package structure.
http://stackoverflow.com/questions/3438404/java-lang-verifyerror
[2014-03-14 14:01:31,256] ERROR
{org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
adding services from bundle :
org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
java.lang.VerifyError: (class:
org/apache/stratos/cloud/controller/impl/CloudControllerServiceImpl,
method: validatePartition signature:
(Lorg/apache/stratos/cloud/controller/deployment/partition/Partition;)Z)
catch_type not a subclass of Throwable
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
at
org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
On Thu, Mar 13, 2014 at 8:23 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> I was able to put together as/cc and sm.
>
> I'm encoutering following issue,
>
> even though there carbon kernel supports profiles, it does not support
> config files per profiles.
>
> for an example SM host a webapp and thus has carbonWebappClassLoader in
> catalina server.xml. Hence i have to install webapp mgt feature to other
> profiles as well..
>
> thanks,
> --Pradee
>
>
>
> On Thu, Mar 13, 2014 at 2:03 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> for the moment i'm ignoring caramel and jaggery features and moved
>> forward. Provisioned initial profiles. (default and sm)
>>
>> next task,
>>
>> cc profile
>> as profile
>>
>> full profile
>>
>>
>> we have to fix caramel and jaggery features later
>>
>>
>>
>> On Thu, Mar 13, 2014 at 12:54 PM, Sameera Jayasoma <
>> sameera.madushan@gmail.com> wrote:
>>
>>> How about using the "copy" action instead of the "mkdir" action? This
>>> requires a change in the jaggery features though.
>>>
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:50 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>>
>>>> its the modules directory created by jaggery/caramel features. its a
>>>> top level directory. Ideally, the touchpoint should have a semantic to
>>>> express, create if not exist.
>>>> But for the moment i can call ant task and delete the directory after
>>>> first round of provisioning...
>>>>
>>>> thanks,
>>>> --Pradeep
>>>>
>>>>
>>>> On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
>>>> sameera.madushan@gmail.com> wrote:
>>>>
>>>>> Hi Pradeep,
>>>>>
>>>>> Can you provide a little more context to this problem? I.e. which
>>>>> feature, which directory.. Trying to understand whether we can avoid
>>>>> creating the directory?
>>>>>
>>>>> Thanks,
>>>>> Sameera.
>>>>>
>>>>>
>>>>> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com> wrote:
>>>>>
>>>>>> Encounter the first issue, :)
>>>>>>
>>>>>> Provisioning semantics fails to create a dir, when it already exists.
>>>>>> Im taking about mkdir touchpoint found in eclipse.
>>>>>> and there is not param to skip if exists it seems.
>>>>>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>>>>> Hopfully i can workaround it.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <
>>>>>> pradeepfn@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Guys,
>>>>>>>
>>>>>>> I started on the $subject. This thread is to track the progress..
>>>>>>>
>>>>>>> thanks,
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Pradeep Fernando.
>>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Pradeep Fernando.
>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Jayasoma
>>>>>
>>>>> blog: http://sameera.adahas.org
>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Pradeep Fernando.
>>>> http://pradeepfernando.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma
>>>
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
I was able to put together as/cc and sm.
I'm encoutering following issue,
even though there carbon kernel supports profiles, it does not support
config files per profiles.
for an example SM host a webapp and thus has carbonWebappClassLoader in
catalina server.xml. Hence i have to install webapp mgt feature to other
profiles as well..
thanks,
--Pradee
On Thu, Mar 13, 2014 at 2:03 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> for the moment i'm ignoring caramel and jaggery features and moved
> forward. Provisioned initial profiles. (default and sm)
>
> next task,
>
> cc profile
> as profile
>
> full profile
>
>
> we have to fix caramel and jaggery features later
>
>
>
> On Thu, Mar 13, 2014 at 12:54 PM, Sameera Jayasoma <
> sameera.madushan@gmail.com> wrote:
>
>> How about using the "copy" action instead of the "mkdir" action? This
>> requires a change in the jaggery features though.
>>
>>
>>
>>
>> On Thu, Mar 13, 2014 at 12:50 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> its the modules directory created by jaggery/caramel features. its a top
>>> level directory. Ideally, the touchpoint should have a semantic to express,
>>> create if not exist.
>>> But for the moment i can call ant task and delete the directory after
>>> first round of provisioning...
>>>
>>> thanks,
>>> --Pradeep
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
>>> sameera.madushan@gmail.com> wrote:
>>>
>>>> Hi Pradeep,
>>>>
>>>> Can you provide a little more context to this problem? I.e. which
>>>> feature, which directory.. Trying to understand whether we can avoid
>>>> creating the directory?
>>>>
>>>> Thanks,
>>>> Sameera.
>>>>
>>>>
>>>> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <pradeepfn@gmail.com
>>>> > wrote:
>>>>
>>>>> Encounter the first issue, :)
>>>>>
>>>>> Provisioning semantics fails to create a dir, when it already exists.
>>>>> Im taking about mkdir touchpoint found in eclipse.
>>>>> and there is not param to skip if exists it seems.
>>>>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>>>> Hopfully i can workaround it.
>>>>>
>>>>>
>>>>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com> wrote:
>>>>>
>>>>>> Hi Guys,
>>>>>>
>>>>>> I started on the $subject. This thread is to track the progress..
>>>>>>
>>>>>> thanks,
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Pradeep Fernando.
>>>>>> http://pradeepfernando.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Pradeep Fernando.
>>>>> http://pradeepfernando.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sameera Jayasoma
>>>>
>>>> blog: http://sameera.adahas.org
>>>> twitter: https://twitter.com/sameerajayasoma
>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>>
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
for the moment i'm ignoring caramel and jaggery features and moved forward.
Provisioned initial profiles. (default and sm)
next task,
cc profile
as profile
full profile
we have to fix caramel and jaggery features later
On Thu, Mar 13, 2014 at 12:54 PM, Sameera Jayasoma <
sameera.madushan@gmail.com> wrote:
> How about using the "copy" action instead of the "mkdir" action? This
> requires a change in the jaggery features though.
>
>
>
>
> On Thu, Mar 13, 2014 at 12:50 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> its the modules directory created by jaggery/caramel features. its a top
>> level directory. Ideally, the touchpoint should have a semantic to express,
>> create if not exist.
>> But for the moment i can call ant task and delete the directory after
>> first round of provisioning...
>>
>> thanks,
>> --Pradeep
>>
>>
>> On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
>> sameera.madushan@gmail.com> wrote:
>>
>>> Hi Pradeep,
>>>
>>> Can you provide a little more context to this problem? I.e. which
>>> feature, which directory.. Trying to understand whether we can avoid
>>> creating the directory?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>>
>>>> Encounter the first issue, :)
>>>>
>>>> Provisioning semantics fails to create a dir, when it already exists.
>>>> Im taking about mkdir touchpoint found in eclipse.
>>>> and there is not param to skip if exists it seems.
>>>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>>> Hopfully i can workaround it.
>>>>
>>>>
>>>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <pradeepfn@gmail.com
>>>> > wrote:
>>>>
>>>>> Hi Guys,
>>>>>
>>>>> I started on the $subject. This thread is to track the progress..
>>>>>
>>>>> thanks,
>>>>>
>>>>>
>>>>> --
>>>>> Pradeep Fernando.
>>>>> http://pradeepfernando.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Pradeep Fernando.
>>>> http://pradeepfernando.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma
>>>
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Sameera Jayasoma
>
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Sameera Jayasoma <sa...@gmail.com>.
How about using the "copy" action instead of the "mkdir" action? This
requires a change in the jaggery features though.
On Thu, Mar 13, 2014 at 12:50 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> its the modules directory created by jaggery/caramel features. its a top
> level directory. Ideally, the touchpoint should have a semantic to express,
> create if not exist.
> But for the moment i can call ant task and delete the directory after
> first round of provisioning...
>
> thanks,
> --Pradeep
>
>
> On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
> sameera.madushan@gmail.com> wrote:
>
>> Hi Pradeep,
>>
>> Can you provide a little more context to this problem? I.e. which
>> feature, which directory.. Trying to understand whether we can avoid
>> creating the directory?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> Encounter the first issue, :)
>>>
>>> Provisioning semantics fails to create a dir, when it already exists. Im
>>> taking about mkdir touchpoint found in eclipse.
>>> and there is not param to skip if exists it seems.
>>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>> Hopfully i can workaround it.
>>>
>>>
>>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>>
>>>> Hi Guys,
>>>>
>>>> I started on the $subject. This thread is to track the progress..
>>>>
>>>> thanks,
>>>>
>>>>
>>>> --
>>>> Pradeep Fernando.
>>>> http://pradeepfernando.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>>
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Sameera Jayasoma
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
its the modules directory created by jaggery/caramel features. its a top
level directory. Ideally, the touchpoint should have a semantic to express,
create if not exist.
But for the moment i can call ant task and delete the directory after first
round of provisioning...
thanks,
--Pradeep
On Thu, Mar 13, 2014 at 12:47 PM, Sameera Jayasoma <
sameera.madushan@gmail.com> wrote:
> Hi Pradeep,
>
> Can you provide a little more context to this problem? I.e. which feature,
> which directory.. Trying to understand whether we can avoid creating the
> directory?
>
> Thanks,
> Sameera.
>
>
> On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Encounter the first issue, :)
>>
>> Provisioning semantics fails to create a dir, when it already exists. Im
>> taking about mkdir touchpoint found in eclipse.
>> and there is not param to skip if exists it seems.
>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>> Hopfully i can workaround it.
>>
>>
>> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> Hi Guys,
>>>
>>> I started on the $subject. This thread is to track the progress..
>>>
>>> thanks,
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Sameera Jayasoma
>
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Sameera Jayasoma <sa...@gmail.com>.
Hi Pradeep,
Can you provide a little more context to this problem? I.e. which feature,
which directory.. Trying to understand whether we can avoid creating the
directory?
Thanks,
Sameera.
On Wed, Mar 12, 2014 at 11:04 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Encounter the first issue, :)
>
> Provisioning semantics fails to create a dir, when it already exists. Im
> taking about mkdir touchpoint found in eclipse.
> and there is not param to skip if exists it seems.
> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
> Hopfully i can workaround it.
>
>
> On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Hi Guys,
>>
>> I started on the $subject. This thread is to track the progress..
>>
>> thanks,
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Sameera Jayasoma
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
Encounter the first issue, :)
Provisioning semantics fails to create a dir, when it already exists. Im
taking about mkdir touchpoint found in eclipse.
and there is not param to skip if exists it seems.
http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
Hopfully i can workaround it.
On Wed, Mar 12, 2014 at 11:01 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Hi Guys,
>
> I started on the $subject. This thread is to track the progress..
>
> thanks,
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Isuru Perera <is...@wso2.com>.
On Wed, Mar 19, 2014 at 12:57 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time being
> without much research, I'm going to use ActiveMQ.
>
+1. Let's use ActiveMQ for now.
>
>
> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com> wrote:
>
>> Awesome - thanks Nirmal!
>>
>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>> > I'll continue on this.
>> >
>> >
>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>> wrote:
>> >>
>> >> Can this patch be reviewed and committed? I'm worried that unless it
>> >> gets applied soon it will become out of date and difficult to commit
>> >> later on.
>> >>
>> >>
>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <pradeepfn@gmail.com
>> >
>> >> wrote:
>> >> > apply the patch and add the jclouds dependency to reolve the jclouds
>> >> > CNF.
>> >> > After that, build the product named stratos. It contains all the
>> >> > components
>> >> > except MB.
>> >> >
>> >> > we can start a test round with an external MB
>> >> >
>> >> > hope this helps.. :)
>> >> >
>> >> > thanks.
>> >> >
>> >> >
>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>> >> > <sa...@gmail.com> wrote:
>> >> >>
>> >> >> Hi Pradeep,
>> >> >>
>> >> >> This patch contains so many code changes. Can you please provide an
>> >> >> update
>> >> >> on where we are on this? What are the remaining items?
>> >> >>
>> >> >> Thanks,
>> >> >> Sameera.
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>> >> >> <pr...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Please someone takeover from here. Unfortunately i have to attend
>> some
>> >> >>> other work.
>> >> >>>
>> >> >>> I have created a JIRA and updated it. Patch attached.
>> >> >>>
>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>> >> >>>
>> >> >>> thanks.
>> >> >>> --Pradeep
>> >> >>>
>> >> >>>
>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>> >> >>> <pr...@gmail.com>
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> Hi Guys,
>> >> >>>>
>> >> >>>> Now the server starts fine with as + cc + sm + cep
>> >> >>>>
>> >> >>>> I managed to workaround the classloading issue, by renaming stub
>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>> >> >>>> unavailability. Its a pretty straightforward fix.
>> >> >>>>
>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>> >> >>>> while
>> >> >>>> adding services from bundle :
>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>> >> >>>> java.lang.NoClassDefFoundError:
>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>> >> >>>>
>> >> >>>> at java.lang.Class.forName0(Native Method)
>> >> >>>> at java.lang.Class.forName(Class.java:247)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> >> >>>> at
>> >> >>>>
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>> >> >>>> at
>> >> >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> >> >>>> ... 49 more
>> >> >>>> [2014-03-17 18:29:20,726] INFO
>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>> Deploying
>> >> >>>> Axis2
>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>> >> >>>> [2014-03-17 18:29:21,465] INFO
>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
>> :
>> >> >>>>
>> >> >>>>
>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>> >> >>>> [2014-03-17 18:29:21,748] INFO
>> >> >>>>
>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>> >> >>>> Permission cache updated for tenant -1234
>> >> >>>> [2014-03-17 18:29:21,904] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >> >>>> Thrift Server started at 10.100.1.80
>> >> >>>> [2014-03-17 18:29:21,923] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >> >>>> Thrift SSL port : 7711
>> >> >>>> [2014-03-17 18:29:21,925] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >> >>>> Thrift port : 7611
>> >> >>>> [2014-03-17 18:29:21,958] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the input WSEventLocal adaptor service
>> >> >>>> [2014-03-17 18:29:21,962] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output WSEventLocal adaptor service
>> >> >>>> [2014-03-17 18:29:21,976] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the input email event service
>> >> >>>> [2014-03-17 18:29:21,983] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>> >> >>>> [2014-03-17 18:29:21,993] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output Email event adaptor service
>> >> >>>> [2014-03-17 18:29:22,002] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output SMS event adaptor service
>> >> >>>> [2014-03-17 18:29:22,011] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>> >> >>>> [2014-03-17 18:29:22,026] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>> >> >>>> A SSO Service Provider is registered for : console
>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>> >> >>>> configuration
>> >> >>>> element 'TenantRegistrationPage' not found in
>> >> >>>>
>> >> >>>>
>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>> >> >>>> [2014-03-17 18:29:22,133] INFO
>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>> >> >>>> HTTPS port
>> >> >>>> : 9443
>> >> >>>> [2014-03-17 18:29:22,133] INFO
>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -
>> HTTP
>> >> >>>> port
>> >> >>>> : 9763
>> >> >>>> [2014-03-17 18:29:22,138] INFO
>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>> >> >>>> selector for
>> >> >>>> servlet write/read
>> >> >>>> [2014-03-17 18:29:22,154] INFO
>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>> >> >>>> selector for
>> >> >>>> servlet write/read
>> >> >>>> [2014-03-17 18:29:22,193] INFO
>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>> >> >>>> service
>> >> >>>> starting in STANDALONE mode...
>> >> >>>> [2014-03-17 18:29:22,202] INFO
>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>> >> >>>> Setting
>> >> >>>> config properties into System properties
>> >> >>>> [2014-03-17 18:29:22,225] INFO
>> >> >>>>
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> >> >>>> Topology receiver thread started
>> >> >>>> [2014-03-17 18:29:22,226] INFO
>> >> >>>>
>> >> >>>>
>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>> >> >>>> - Stratos Manager topology receiver thread started
>> >> >>>> [2014-03-17 18:29:22,231] INFO
>> >> >>>>
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> >> >>>> ADC
>> >> >>>> management server component is activated
>> >> >>>> [2014-03-17 18:29:22,255] INFO
>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>> >> >>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>> >> >>>> [2014-03-17 18:29:22,275] INFO
>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -
>> Task
>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>> >> >>>> [2014-03-17 18:29:22,275] INFO
>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> >> >>>> Server
>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>> >> >>>> [2014-03-17 18:29:22,275] INFO
>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> >> >>>> WSO2
>> >> >>>> Carbon started in 55 sec
>> >> >>>> [2014-03-17 18:29:22,430] INFO
>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>> Console
>> >> >>>> URL :
>> >> >>>> https://10.100.1.80:9443/carbon/
>> >> >>>> [2014-03-17 18:29:22,521] INFO
>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>> Additional
>> >> >>>> SASL
>> >> >>>> providers successfully registered.
>> >> >>>> [2014-03-17 18:29:22,522] INFO
>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>> Callback
>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
>> >> >>>> AMQPLAIN
>> >> >>>> PLAIN
>> >> >>>> [2014-03-17 18:29:22,535] WARN
>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>> >> >>>> Unable to find resource qpidversion.properties from classloader
>> >> >>>>
>> >> >>>>
>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>> shahhaqu@cisco.com>
>> >> >>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Pradeep,
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> I *think* I am interested in this topic and am new to this
>> domain,
>> >> >>>>> but
>> >> >>>>> from the archives, I'm not 100% of the original goals of this
>> work.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage
>> of
>> >> >>>>> your work: do we still use the same CLIs to start the processes
>> or
>> >> >>>>> what? I
>> >> >>>>> see some mention of profiles and pre-built VMs, but am unclear
>> how
>> >> >>>>> they
>> >> >>>>> relate to this.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this feature I
>> can
>> >> >>>>> read?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Thanks, Shaheed
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>> >> >>>>>
>> >> >>>>> Interesting ... it would be cool to combine these with something
>> >> >>>>> like
>> >> >>>>> rPath to build a minimal Linux image with just the exact bits in
>> it.
>> >> >>>>> Looks
>> >> >>>>> like rPath is gone - what's the way people build custom images
>> now?
>> >> >>>>> Or is
>> >> >>>>> that gone with just more memory and more disk being normal??
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>> chsnow123@gmail.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Sanjiva,
>> >> >>>>>
>> >> >>>>> Vagrant works on top of an existing image (box). There are
>> plenty of
>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
>> >> >>>>> although
>> >> >>>>> the disk size is a little small to be useful. Opscode also
>> >> >>>>> provide some
>> >> >>>>> pretty good boxes [2]. If these still don't meet your needs, you
>> can
>> >> >>>>> copy
>> >> >>>>> the packer definitions from opscode and modify them to build your
>> >> >>>>> own box
>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>> >> >>>>>
>> >> >>>>> Many thanks,
>> >> >>>>>
>> >> >>>>> Chris
>> >> >>>>>
>> >> >>>>> ---
>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>> >> >>>>> [2] https://github.com/opscode/bento
>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>> >> >>>>> [4] http://packer.io
>> >> >>>>>
>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>> scripts
>> >> >>>>> as
>> >> >>>>> well!
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does it
>> build
>> >> >>>>> a
>> >> >>>>> VM image or does it set up the environment to run the image?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Sanjiva.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <chsnow123@gmail.com
>> >
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Sanjiva,
>> >> >>>>>
>> >> >>>>> For VM images, vagrant makes life very easy for users; setting up
>> >> >>>>> disks, setting up network cards, setting up memory, configuring
>> >> >>>>> guest proxy
>> >> >>>>> settings, running provisioning scripts, etc.
>> >> >>>>>
>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
>> project
>> >> >>>>> is
>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making good
>> >> >>>>> progress.
>> >> >>>>> Although my scripts are buggy, with a few commands I can
>> checkout,
>> >> >>>>> build and
>> >> >>>>> provision a cloudstack developer environment. I am now working
>> on
>> >> >>>>> the
>> >> >>>>> scripts to do the same for Stratos.
>> >> >>>>>
>> >> >>>>> Initially, the memory requirements will be high on my
>> environment,
>> >> >>>>> but
>> >> >>>>> for me the first goal is automation, the next goal will be
>> >> >>>>> efficiency.
>> >> >>>>>
>> >> >>>>> Many thanks,
>> >> >>>>> Chris
>> >> >>>>>
>> >> >>>>> ---
>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>> >> >>>>>
>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> I think right now we need to focus on getting a single trivial
>> >> >>>>> server
>> >> >>>>> mechanism to be able to run Stratos without too much of stuff
>> having
>> >> >>>>> to be
>> >> >>>>> set up. I'd love to see two developer distros:
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> - a VM image that has everything in it and runs in under 4GB with
>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>> Carbon
>> >> >>>>> server to
>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>> (Carbon
>> >> >>>>> stuff
>> >> >>>>> HAS to run in one server - else its a bug in those products .. so
>> >> >>>>> the
>> >> >>>>> decision should not be based on ability to run in one JVM but
>> rather
>> >> >>>>> just
>> >> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0
>> - I
>> >> >>>>> think
>> >> >>>>> we're nearly there for it.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
>> >> >>>>> plugin
>> >> >>>>> to jClouds that spins up Docker images as processes and there's
>> one
>> >> >>>>> JVM that
>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
>> plus
>> >> >>>>> a URL
>> >> >>>>> to a Docker image registry from which the images are booted up
>> and
>> >> >>>>> run
>> >> >>>>> (obviously a local registry will do better). We don't have this
>> >> >>>>> no-IaaS-IaaS
>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that
>> hard
>> >> >>>>> to make
>> >> >>>>> it work).
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> For production deployments obviously this one server stuff is
>> >> >>>>> nonsense
>> >> >>>>> .. so we need to have full decoupled distributed execution. For
>> that
>> >> >>>>> we
>> >> >>>>> should ship puppet scripts to get them up and running plus maybe
>> >> >>>>> Boto
>> >> >>>>> scripts for someone to get it all up on EC2 with one command.
>> Again
>> >> >>>>> its
>> >> >>>>> totally fine to use whatever broker here and whatever other
>> >> >>>>> pluggable
>> >> >>>>> components people want to use (and we need to make sure all the
>> >> >>>>> parts are
>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>> etc.)).
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Makes sense?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Sanjiva.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>> >> >>>>> <pr...@gmail.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Chris,
>> >> >>>>>
>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>> >> >>>>>
>> >> >>>>> Thanks
>> >> >>>>>
>> >> >>>>> --Pradeep
>> >> >>>>> sent from my phone
>> >> >>>>>
>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work to
>> have
>> >> >>>>> a
>> >> >>>>> view on that :(
>> >> >>>>>
>> >> >>>>> One thing I'm wondering though is how much memory will be saved
>> if
>> >> >>>>> we
>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>> >> >>>>>
>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>> >> >>>>> <pr...@gmail.com> wrote:
>> >> >>>>> > btw,
>> >> >>>>> >
>> >> >>>>> > Now im working on MB and CEP bits.
>> >> >>>>> >
>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>> >> >>>>> > However,
>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>> profile
>> >> >>>>> > (the
>> >> >>>>> > profile that has all) makes sense.
>> >> >>>>> >
>> >> >>>>> > WDYT?
>> >> >>>>> >
>> >> >>>>> > Are we all on same page..
>> >> >>>>> >
>> >> >>>>> > thanks
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>> chsnow123@gmail.com>
>> >> >>>>> > wrote:
>> >> >>>>> >>
>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> >> >>>>> >> findings!
>> >> >>>>> >>
>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>> >> >>>>> >> <pr...@gmail.com>
>> >> >>>>> >> wrote:
>> >> >>>>> >> > Hi Guys,
>> >> >>>>> >> >
>> >> >>>>> >> > I started on the $subject. This thread is to track the
>> >> >>>>> >> > progress..
>> >> >>>>> >> >
>> >> >>>>> >> > thanks,
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > --
>> >> >>>>> >> > Pradeep Fernando.
>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>> >> >>>>> >>
>> >> >>>>> >>
>> >> >>>>> >>
>> >> >>>>> >> --
>> >> >>>>> >> Check out my professional profile and connect with me on
>> >> >>>>> >> LinkedIn.
>> >> >>>>> >> http://lnkd.in/cw5k69
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > --
>> >> >>>>> > Pradeep Fernando.
>> >> >>>>> > http://pradeepfernando.blogspot.com/
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>> Check out my professional profile and connect with me on
>> LinkedIn.
>> >> >>>>> http://lnkd.in/cw5k69
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> 5345)
>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >> >>>>> 8311
>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >> >>>>> Lean . Enterprise . Middleware
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> 5345)
>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >> >>>>> 8311
>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >> >>>>> Lean . Enterprise . Middleware
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> 5345)
>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >> >>>>> 8311
>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >> >>>>> Lean . Enterprise . Middleware
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> Pradeep Fernando.
>> >> >>>> http://pradeepfernando.blogspot.com/
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Pradeep Fernando.
>> >> >>> http://pradeepfernando.blogspot.com/
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Sameera Jayasoma
>> >> >>
>> >> >> blog: http://sameera.adahas.org
>> >> >> twitter: https://twitter.com/sameerajayasoma
>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Pradeep Fernando.
>> >> > http://pradeepfernando.blogspot.com/
>> >>
>> >>
>> >>
>> >> --
>> >> Check out my professional profile and connect with me on LinkedIn.
>> >> http://lnkd.in/cw5k69
>> >
>> >
>> >
>> >
>> > --
>> > Best Regards,
>> > Nirmal
>> >
>> > Nirmal Fernando.
>> > PPMC Member & Committer of Apache Stratos,
>> > Senior Software Engineer, WSO2 Inc.
>> >
>> > Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Thats awesome news Nirmal!
On Thu, Mar 20, 2014 at 10:54 AM, Nirmal Fernando
<ni...@gmail.com> wrote:
> Good news! Now the single JVM runs fine with ActiveMQ and I have tested up
> to subscription.
>
> Next steps would be to test a full cycle (subscription -> activation ->
> access) with a puppet master.
>
> I suggest we use this only in developer environments at least in 4.0. Wdyt?
>
>
> On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <ni...@gmail.com>
> wrote:
>>
>> Update: fixed few other issues including one class loading issue.
>>
>> SingleJVM now can communicate with ActiveMQ.
>>
>> Now copying relevant configs to the product and doing a test round.
>>
>>
>> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>>>
>>> With Sameera's help, we managed to fix it. Cloud-controller has a
>>> customized launch.ini file and that has this missing package. So, we gonna
>>> have a customized launch.ini file in the single JVM case too.
>>>
>>> Thanks Sameera.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <ni...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Sameera,
>>>>
>>>> Actually I sent that info earlier, let me paste again.
>>>>
>>>>
>>>> osgi> diag 79
>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>> Direct constraints which are unresolved:
>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>> osgi>
>>>>
>>>> osgi> p javax.lang.model.type
>>>> No exported packages
>>>> osgi>
>>>>
>>>> In Cloud controller product:
>>>>
>>>> osgi> p javax.lang.model.type
>>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>>> osgi_3.8.1.v20120830-144521 [0]>
>>>> jclouds-core_1.7.1 [65] imports
>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>> imports
>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>
>>>>
>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>> package is not exported in the single jvm case.
>>>>
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma
>>>> <sa...@gmail.com> wrote:
>>>>>
>>>>> Hi Nirmal,
>>>>>
>>>>> Can you check who is exporting the javax.lang.model.type package in a
>>>>> working package? Check whether this package is exported from the JDK via the
>>>>> equinox system bundle?
>>>>>
>>>>> Thanks,
>>>>> Sameera.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando
>>>>> <ni...@gmail.com> wrote:
>>>>>>
>>>>>> Hi Sameera,
>>>>>>
>>>>>> Thanks for the reply.
>>>>>>
>>>>>> Here's the full stack-trace:
>>>>>>
>>>>>>
>>>>>> java.lang.NoClassDefFoundError:
>>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>> at java.lang.Class.forName(Class.java:247)
>>>>>> at
>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>> at
>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>> at
>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>> at
>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>> at
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>> at
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>> at
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>> at
>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>> at
>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>> at
>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>> at
>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>> at
>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>> at
>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>> at
>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>>> at
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>
>>>>>>
>>>>>>
>>>>>> osgi> ss jcloud
>>>>>> "Framework is launched."
>>>>>>
>>>>>>
>>>>>> id State Bundle
>>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>>> osgi>
>>>>>> osgi>
>>>>>> osgi> diag 79
>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>> Direct constraints which are unresolved:
>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>> osgi>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma
>>>>>> <sa...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi Nirmal,
>>>>>>>
>>>>>>> Can you post the full stacktrace?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sameera.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando
>>>>>>> <ni...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> osgi> diag 79
>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>> Direct constraints which are unresolved:
>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>> osgi>
>>>>>>>>
>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>> No exported packages
>>>>>>>> osgi>
>>>>>>>>
>>>>>>>> In Cloud controller product:
>>>>>>>>
>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>> javax.lang.model.type;
>>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>>> imports
>>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>>>> package is not exported in the single jvm case.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando
>>>>>>>> <ni...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Sounds good, though at some point in the future should we remove
>>>>>>>>>> the dependency on using jndi? It seems a bit ironic that we are using a
>>>>>>>>>> cross platform protocol AMPQ, but are connecting to it with a Java specific
>>>>>>>>>> mechanism.
>>>>>>>>>>
>>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the
>>>>>>>>>>> time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow
>>>>>>>>>>> <ch...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando
>>>>>>>>>>>> <ni...@gmail.com> wrote:
>>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow
>>>>>>>>>>>> > <ch...@gmail.com> wrote:
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>>>>>> >> unless it
>>>>>>>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>>>>>>>> >> commit
>>>>>>>>>>>> >> later on.
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando
>>>>>>>>>>>> >> <pr...@gmail.com>
>>>>>>>>>>>> >> wrote:
>>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve
>>>>>>>>>>>> >> > the jclouds
>>>>>>>>>>>> >> > CNF.
>>>>>>>>>>>> >> > After that, build the product named stratos. It contains
>>>>>>>>>>>> >> > all the
>>>>>>>>>>>> >> > components
>>>>>>>>>>>> >> > except MB.
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > thanks.
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>>>>>> >> >> provide an
>>>>>>>>>>>> >> >> update
>>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have
>>>>>>>>>>>> >> >>> to attend some
>>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>>> >> >>>> renaming stub
>>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud
>>>>>>>>>>>> >> >>>> class
>>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry}
>>>>>>>>>>>> >> >>>> - Error
>>>>>>>>>>>> >> >>>> while
>>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor}
>>>>>>>>>>>> >> >>>> - Deploying
>>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>>> >> >>>> {super-tenant}
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>>> >> >>>> Repository :
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>>> >> >>>> port
>>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>>>> >> >>>> shared
>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>>>> >> >>>> shared
>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>>> >> >>>> Service URL :
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>>> >> >>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -
>>>>>>>>>>>> >> >>>> Mgt Console
>>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>>>>>>> >> >>>> Additional
>>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry}
>>>>>>>>>>>> >> >>>> - Callback
>>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>>> >> >>>> CRAM-MD5-HASHED
>>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>>> >> >>>> classloader
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque
>>>>>>>>>>>> >> >>>> <sh...@cisco.com>
>>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to
>>>>>>>>>>>> >> >>>>> this domain,
>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals
>>>>>>>>>>>> >> >>>>> of this work.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>>>>>>> >> >>>>> advantage of
>>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>>>>>> >> >>>>> processes or
>>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>>>>>>> >> >>>>> unclear how
>>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>>>>>> >> >>>>> feature I can
>>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>>>>>>> >> >>>>> something
>>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>>> >> >>>>> exact bits in it.
>>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>>>>>>>> >> >>>>> images now?
>>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>>> >> >>>>> normal??
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow
>>>>>>>>>>>> >> >>>>> <ch...@gmail.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There
>>>>>>>>>>>> >> >>>>> are plenty of
>>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>>>>>>> >> >>>>> boxes [1],
>>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode
>>>>>>>>>>>> >> >>>>> also
>>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>>>>>> >> >>>>> needs, you can
>>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>>>>>>> >> >>>>> build your
>>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look
>>>>>>>>>>>> >> >>>>> too.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana"
>>>>>>>>>>>> >> >>>>> <sa...@wso2.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>>> >> >>>>> vagrant scripts
>>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out.
>>>>>>>>>>>> >> >>>>> Does it build
>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>>>>>> >> >>>>> image?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow
>>>>>>>>>>>> >> >>>>> <ch...@gmail.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>>>>>>> >> >>>>> setting up
>>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>>> >> >>>>> configuring
>>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>>> >> >>>>> Stratos. My project
>>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>>>>>> >> >>>>> making good
>>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I
>>>>>>>>>>>> >> >>>>> can checkout,
>>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>>>>>>>> >> >>>>> working on
>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>>>>>> >> >>>>> environment,
>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal will
>>>>>>>>>>>> >> >>>>> be
>>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana"
>>>>>>>>>>>> >> >>>>> <sa...@wso2.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>>>>>>> >> >>>>> trivial
>>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>>>>>>>> >> >>>>> stuff having
>>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>>> >> >>>>> under 4GB with
>>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses
>>>>>>>>>>>> >> >>>>> one Carbon
>>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>>> >> >>>>> broker. (Carbon
>>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>>> >> >>>>> products .. so
>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in one
>>>>>>>>>>>> >> >>>>> JVM but rather
>>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be
>>>>>>>>>>>> >> >>>>> in 4.0.0 - I
>>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write
>>>>>>>>>>>> >> >>>>> a direct
>>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>>>>>>>> >> >>>>> there's one
>>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes
>>>>>>>>>>>> >> >>>>> one JVM plus
>>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>>>>> >> >>>>> booted up and
>>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't
>>>>>>>>>>>> >> >>>>> have this
>>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its
>>>>>>>>>>>> >> >>>>> not that hard
>>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>>>>> >> >>>>> stuff is
>>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>>> >> >>>>> execution. For that
>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running
>>>>>>>>>>>> >> >>>>> plus maybe
>>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>>>>> >> >>>>> command. Again
>>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever
>>>>>>>>>>>> >> >>>>> other
>>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>>> >> >>>>> components people want to use (and we need to make sure
>>>>>>>>>>>> >> >>>>> all the
>>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>>> >> >>>>> engine, etc.)).
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same
>>>>>>>>>>>> >> >>>>> suggestion.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow"
>>>>>>>>>>>> >> >>>>> <ch...@gmail.com> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles
>>>>>>>>>>>> >> >>>>> work to have
>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will
>>>>>>>>>>>> >> >>>>> be saved if
>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles
>>>>>>>>>>>> >> >>>>> > in stratos.
>>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>>> >> >>>>> > default profile
>>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow
>>>>>>>>>>>> >> >>>>> > <ch...@gmail.com>
>>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>>> >> >>>>> >> forward to your
>>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track
>>>>>>>>>>>> >> >>>>> >> > the
>>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect with
>>>>>>>>>>>> >> >>>>> >> me on
>>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with me
>>>>>>>>>>>> >> >>>>> on LinkedIn.
>>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>> >> >>>>> 11 214 5345)
>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>>> >> >>>>> +1 650 265
>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>> >> >>>>> @sanjiva
>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>> >> >>>>> 11 214 5345)
>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>>> >> >>>>> +1 650 265
>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>> >> >>>>> @sanjiva
>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>> >> >>>>> 11 214 5345)
>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>>> >> >>>>> +1 650 265
>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>> >> >>>>> @sanjiva
>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> --
>>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> --
>>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> --
>>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > --
>>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> --
>>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>>> >> LinkedIn.
>>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> > --
>>>>>>>>>>>> > Best Regards,
>>>>>>>>>>>> > Nirmal
>>>>>>>>>>>> >
>>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>> >
>>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> Nirmal
>>>>>>>>>>>
>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Nirmal
>>>>>>>>>
>>>>>>>>> Nirmal Fernando.
>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Nirmal
>>>>>>>>
>>>>>>>> Nirmal Fernando.
>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>
>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sameera Jayasoma
>>>>>>>
>>>>>>> blog: http://sameera.adahas.org
>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Jayasoma
>>>>>
>>>>> blog: http://sameera.adahas.org
>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by Afkham Azeez <af...@gmail.com>.
Rather than releasing in a hurry, I would prefer to do the proper thing.
Azeez
On Fri, Mar 21, 2014 at 9:42 AM, Afkham Azeez <af...@gmail.com> wrote:
>
>
>
> On Fri, Mar 21, 2014 at 9:36 AM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi Azeez,
>>
>>
>> On Fri, Mar 21, 2014 at 12:20 AM, Afkham Azeez <af...@gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Thu, Mar 20, 2014 at 4:24 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> Good news! Now the single JVM runs fine with ActiveMQ and I have tested
>>>> up to subscription.
>>>>
>>>
>>> Nice work Nirmal!
>>>
>>>>
>>>> Next steps would be to test a full cycle (subscription -> activation ->
>>>> access) with a puppet master.
>>>>
>>>> I suggest we use this only in developer environments at least in 4.0.
>>>> Wdyt?
>>>>
>>>
>>> In production, we can run multiple instances of this binary with the
>>> relevant profiles. Have you tested starting up with different profiles?
>>>
>>
>> No, given the time constraints, shall we stick only to the default
>> profile at least for 4.0? Anyway, I'll try it once, but if we face some
>> issues at the time of provisioning, we might not be able to fix those
>> quickly.
>>
>
> I was under the impression that Pradeep created the profiles. One of the
> main ideas was to have the profiles so that you can run the same pack with
> different profiles. Having one pack to play around, and another for
> production deployments is not good IMOP.
>
>>
>> Let me know your thoughts.
>>
>>>
>>>
>>>>
>>>>
>>>> On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> Update: fixed few other issues including one class loading issue.
>>>>>
>>>>> SingleJVM now can communicate with ActiveMQ.
>>>>>
>>>>> Now copying relevant configs to the product and doing a test round.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> With Sameera's help, we managed to fix it. Cloud-controller has a
>>>>>> customized launch.ini file and that has this missing package. So, we gonna
>>>>>> have a customized launch.ini file in the single JVM case too.
>>>>>>
>>>>>> Thanks Sameera.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Sameera,
>>>>>>>
>>>>>>> Actually I sent that info earlier, let me paste again.
>>>>>>>
>>>>>>>
>>>>>>> osgi> diag 79
>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>> Direct constraints which are unresolved:
>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>> osgi>
>>>>>>>
>>>>>>> osgi> p javax.lang.model.type
>>>>>>> No exported packages
>>>>>>> osgi>
>>>>>>>
>>>>>>> In Cloud controller product:
>>>>>>>
>>>>>>> osgi> p javax.lang.model.type
>>>>>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>>>>>> osgi_3.8.1.v20120830-144521 [0]>
>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>> imports
>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>>> package is not exported in the single jvm case.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Nirmal,
>>>>>>>>
>>>>>>>> Can you check who is exporting the javax.lang.model.type package
>>>>>>>> in a working package? Check whether this package is exported from
>>>>>>>> the JDK via the equinox system bundle?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sameera.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <
>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Sameera,
>>>>>>>>>
>>>>>>>>> Thanks for the reply.
>>>>>>>>>
>>>>>>>>> Here's the full stack-trace:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> java.lang.NoClassDefFoundError:
>>>>>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>> at
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>> at
>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> osgi> ss jcloud
>>>>>>>>> "Framework is launched."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> id State Bundle
>>>>>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>>>>>> osgi>
>>>>>>>>> osgi>
>>>>>>>>> osgi> diag 79
>>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>>> Direct constraints which are unresolved:
>>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>>> osgi>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Nirmal,
>>>>>>>>>>
>>>>>>>>>> Can you post the full stacktrace?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Sameera.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> osgi> diag 79
>>>>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>>>>> Direct constraints which are unresolved:
>>>>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>>>>> osgi>
>>>>>>>>>>>
>>>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>>>> No exported packages
>>>>>>>>>>> osgi>
>>>>>>>>>>>
>>>>>>>>>>> In Cloud controller product:
>>>>>>>>>>>
>>>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>>>> javax.lang.model.type;
>>>>>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96]
>>>>>>>>>>> imports
>>>>>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510
>>>>>>>>>>> [124] imports
>>>>>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but
>>>>>>>>>>> this package is not exported in the single jvm case.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Sounds good, though at some point in the future should we
>>>>>>>>>>>>> remove the dependency on using jndi? It seems a bit ironic that we are
>>>>>>>>>>>>> using a cross platform protocol AMPQ, but are connecting to it with a Java
>>>>>>>>>>>>> specific mechanism.
>>>>>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <
>>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for
>>>>>>>>>>>>>> the time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <
>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried
>>>>>>>>>>>>>>> that unless it
>>>>>>>>>>>>>>> >> gets applied soon it will become out of date and
>>>>>>>>>>>>>>> difficult to commit
>>>>>>>>>>>>>>> >> later on.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>>>>>>> >> wrote:
>>>>>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to
>>>>>>>>>>>>>>> reolve the jclouds
>>>>>>>>>>>>>>> >> > CNF.
>>>>>>>>>>>>>>> >> > After that, build the product named stratos. It
>>>>>>>>>>>>>>> contains all the
>>>>>>>>>>>>>>> >> > components
>>>>>>>>>>>>>>> >> > except MB.
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > thanks.
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> This patch contains so many code changes. Can you
>>>>>>>>>>>>>>> please provide an
>>>>>>>>>>>>>>> >> >> update
>>>>>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i
>>>>>>>>>>>>>>> have to attend some
>>>>>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>>>>>> renaming stub
>>>>>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to
>>>>>>>>>>>>>>> jcloud class
>>>>>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>>>>>>>>>>>>>>> >> >>>> while
>>>>>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
>>>>>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>>>>>> {super-tenant}
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>>>>>> Repository :
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input email event
>>>>>>>>>>>>>>> service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>>>>>> service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>>>>>> service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} -
>>>>>>>>>>>>>>> The
>>>>>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>>>>>> >> >>>> port
>>>>>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} -
>>>>>>>>>>>>>>> Using a shared
>>>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} -
>>>>>>>>>>>>>>> Using a shared
>>>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>>>>>> Service URL :
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
>>>>>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
>>>>>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>>>>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>>>>>> classloader
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new
>>>>>>>>>>>>>>> to this domain,
>>>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original
>>>>>>>>>>>>>>> goals of this work.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we
>>>>>>>>>>>>>>> take advantage of
>>>>>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start
>>>>>>>>>>>>>>> the processes or
>>>>>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but
>>>>>>>>>>>>>>> am unclear how
>>>>>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for
>>>>>>>>>>>>>>> this feature I can
>>>>>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva
>>>>>>>>>>>>>>> Weerawarana wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these
>>>>>>>>>>>>>>> with something
>>>>>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>>>>>> exact bits in it.
>>>>>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build
>>>>>>>>>>>>>>> custom images now?
>>>>>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>>>>>> normal??
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box).
>>>>>>>>>>>>>>> There are plenty of
>>>>>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides
>>>>>>>>>>>>>>> vagrant boxes [1],
>>>>>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful.
>>>>>>>>>>>>>>> Opscode also
>>>>>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet
>>>>>>>>>>>>>>> your needs, you can
>>>>>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them
>>>>>>>>>>>>>>> to build your
>>>>>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look
>>>>>>>>>>>>>>> too.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>>>>>> >> >>>>> [3]
>>>>>>>>>>>>>>> https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>>>>>> vagrant scripts
>>>>>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it
>>>>>>>>>>>>>>> out. Does it build
>>>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run
>>>>>>>>>>>>>>> the image?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for
>>>>>>>>>>>>>>> users; setting up
>>>>>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>>>>>> configuring
>>>>>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>>>>>> Stratos. My project
>>>>>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but
>>>>>>>>>>>>>>> I'm making good
>>>>>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands
>>>>>>>>>>>>>>> I can checkout,
>>>>>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am
>>>>>>>>>>>>>>> now working on
>>>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on
>>>>>>>>>>>>>>> my environment,
>>>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal
>>>>>>>>>>>>>>> will be
>>>>>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a
>>>>>>>>>>>>>>> single trivial
>>>>>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too
>>>>>>>>>>>>>>> much of stuff having
>>>>>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>>>>>> under 4GB with
>>>>>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this
>>>>>>>>>>>>>>> uses one Carbon
>>>>>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>>>>>> broker. (Carbon
>>>>>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>>>>>> products .. so
>>>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in
>>>>>>>>>>>>>>> one JVM but rather
>>>>>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to
>>>>>>>>>>>>>>> be in 4.0.0 - I
>>>>>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we
>>>>>>>>>>>>>>> write a direct
>>>>>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes
>>>>>>>>>>>>>>> and there's one
>>>>>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download
>>>>>>>>>>>>>>> becomes one JVM plus
>>>>>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images
>>>>>>>>>>>>>>> are booted up and
>>>>>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We
>>>>>>>>>>>>>>> don't have this
>>>>>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever
>>>>>>>>>>>>>>> (its not that hard
>>>>>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> For production deployments obviously this one
>>>>>>>>>>>>>>> server stuff is
>>>>>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>>>>>> execution. For that
>>>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and
>>>>>>>>>>>>>>> running plus maybe
>>>>>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with
>>>>>>>>>>>>>>> one command. Again
>>>>>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and
>>>>>>>>>>>>>>> whatever other
>>>>>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>>>>>> >> >>>>> components people want to use (and we need to make
>>>>>>>>>>>>>>> sure all the
>>>>>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>>>>>> engine, etc.)).
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same
>>>>>>>>>>>>>>> suggestion.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the
>>>>>>>>>>>>>>> profiles work to have
>>>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory
>>>>>>>>>>>>>>> will be saved if
>>>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only
>>>>>>>>>>>>>>> profiles in stratos.
>>>>>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>>>>>> default profile
>>>>>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>>>>>> forward to your
>>>>>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to
>>>>>>>>>>>>>>> track the
>>>>>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect
>>>>>>>>>>>>>>> with me on
>>>>>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with
>>>>>>>>>>>>>>> me on LinkedIn.
>>>>>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499| +94
>>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499| +94
>>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499| +94
>>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> --
>>>>>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> --
>>>>>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> --
>>>>>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > --
>>>>>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> --
>>>>>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > --
>>>>>>>>>>>>>>> > Best Regards,
>>>>>>>>>>>>>>> > Nirmal
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Best Regards,
>>>>>>>>>>>>>> Nirmal
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Best Regards,
>>>>>>>>>>>> Nirmal
>>>>>>>>>>>>
>>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>
>>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> Nirmal
>>>>>>>>>>>
>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sameera Jayasoma
>>>>>>>>>>
>>>>>>>>>> blog: http://sameera.adahas.org
>>>>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Nirmal
>>>>>>>>>
>>>>>>>>> Nirmal Fernando.
>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sameera Jayasoma
>>>>>>>>
>>>>>>>> blog: http://sameera.adahas.org
>>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com,
>>> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
>>>
>>> *email: **azeez@wso2.com* <az...@wso2.com>
>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com,
> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
>
> *email: **azeez@wso2.com* <az...@wso2.com>
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* <http://blog.afkham.org>
> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> <http://lk.linkedin.com/in/afkhamazeez>*
>
> *Lean . Enterprise . Middleware*
>
>
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com,
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*email: **azeez@wso2.com* <az...@wso2.com>
* cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org>
*twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
<http://lk.linkedin.com/in/afkhamazeez>*
*Lean . Enterprise . Middleware*
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
I will test and see whether there're any road blocks.
On Fri, Mar 21, 2014 at 9:42 AM, Afkham Azeez <af...@gmail.com> wrote:
>
>
>
> On Fri, Mar 21, 2014 at 9:36 AM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi Azeez,
>>
>>
>> On Fri, Mar 21, 2014 at 12:20 AM, Afkham Azeez <af...@gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Thu, Mar 20, 2014 at 4:24 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> Good news! Now the single JVM runs fine with ActiveMQ and I have tested
>>>> up to subscription.
>>>>
>>>
>>> Nice work Nirmal!
>>>
>>>>
>>>> Next steps would be to test a full cycle (subscription -> activation ->
>>>> access) with a puppet master.
>>>>
>>>> I suggest we use this only in developer environments at least in 4.0.
>>>> Wdyt?
>>>>
>>>
>>> In production, we can run multiple instances of this binary with the
>>> relevant profiles. Have you tested starting up with different profiles?
>>>
>>
>> No, given the time constraints, shall we stick only to the default
>> profile at least for 4.0? Anyway, I'll try it once, but if we face some
>> issues at the time of provisioning, we might not be able to fix those
>> quickly.
>>
>
> I was under the impression that Pradeep created the profiles. One of the
> main ideas was to have the profiles so that you can run the same pack with
> different profiles. Having one pack to play around, and another for
> production deployments is not good IMOP.
>
>>
>> Let me know your thoughts.
>>
>>>
>>>
>>>>
>>>>
>>>> On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> Update: fixed few other issues including one class loading issue.
>>>>>
>>>>> SingleJVM now can communicate with ActiveMQ.
>>>>>
>>>>> Now copying relevant configs to the product and doing a test round.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> With Sameera's help, we managed to fix it. Cloud-controller has a
>>>>>> customized launch.ini file and that has this missing package. So, we gonna
>>>>>> have a customized launch.ini file in the single JVM case too.
>>>>>>
>>>>>> Thanks Sameera.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Sameera,
>>>>>>>
>>>>>>> Actually I sent that info earlier, let me paste again.
>>>>>>>
>>>>>>>
>>>>>>> osgi> diag 79
>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>> Direct constraints which are unresolved:
>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>> osgi>
>>>>>>>
>>>>>>> osgi> p javax.lang.model.type
>>>>>>> No exported packages
>>>>>>> osgi>
>>>>>>>
>>>>>>> In Cloud controller product:
>>>>>>>
>>>>>>> osgi> p javax.lang.model.type
>>>>>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>>>>>> osgi_3.8.1.v20120830-144521 [0]>
>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>> imports
>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>>> package is not exported in the single jvm case.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Nirmal,
>>>>>>>>
>>>>>>>> Can you check who is exporting the javax.lang.model.type package
>>>>>>>> in a working package? Check whether this package is exported from
>>>>>>>> the JDK via the equinox system bundle?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sameera.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <
>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Sameera,
>>>>>>>>>
>>>>>>>>> Thanks for the reply.
>>>>>>>>>
>>>>>>>>> Here's the full stack-trace:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> java.lang.NoClassDefFoundError:
>>>>>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>> at
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>> at
>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>> at
>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> osgi> ss jcloud
>>>>>>>>> "Framework is launched."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> id State Bundle
>>>>>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>>>>>> osgi>
>>>>>>>>> osgi>
>>>>>>>>> osgi> diag 79
>>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>>> Direct constraints which are unresolved:
>>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>>> osgi>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Nirmal,
>>>>>>>>>>
>>>>>>>>>> Can you post the full stacktrace?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Sameera.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> osgi> diag 79
>>>>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>>>>> Direct constraints which are unresolved:
>>>>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>>>>> osgi>
>>>>>>>>>>>
>>>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>>>> No exported packages
>>>>>>>>>>> osgi>
>>>>>>>>>>>
>>>>>>>>>>> In Cloud controller product:
>>>>>>>>>>>
>>>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>>>> javax.lang.model.type;
>>>>>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96]
>>>>>>>>>>> imports
>>>>>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510
>>>>>>>>>>> [124] imports
>>>>>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but
>>>>>>>>>>> this package is not exported in the single jvm case.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Sounds good, though at some point in the future should we
>>>>>>>>>>>>> remove the dependency on using jndi? It seems a bit ironic that we are
>>>>>>>>>>>>> using a cross platform protocol AMPQ, but are connecting to it with a Java
>>>>>>>>>>>>> specific mechanism.
>>>>>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <
>>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for
>>>>>>>>>>>>>> the time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <
>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried
>>>>>>>>>>>>>>> that unless it
>>>>>>>>>>>>>>> >> gets applied soon it will become out of date and
>>>>>>>>>>>>>>> difficult to commit
>>>>>>>>>>>>>>> >> later on.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>>>>>>> >> wrote:
>>>>>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to
>>>>>>>>>>>>>>> reolve the jclouds
>>>>>>>>>>>>>>> >> > CNF.
>>>>>>>>>>>>>>> >> > After that, build the product named stratos. It
>>>>>>>>>>>>>>> contains all the
>>>>>>>>>>>>>>> >> > components
>>>>>>>>>>>>>>> >> > except MB.
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > thanks.
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> This patch contains so many code changes. Can you
>>>>>>>>>>>>>>> please provide an
>>>>>>>>>>>>>>> >> >> update
>>>>>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i
>>>>>>>>>>>>>>> have to attend some
>>>>>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>>>>>> renaming stub
>>>>>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to
>>>>>>>>>>>>>>> jcloud class
>>>>>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>>>>>>>>>>>>>>> >> >>>> while
>>>>>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
>>>>>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>>>>>> {super-tenant}
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>>>>>> Repository :
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input email event
>>>>>>>>>>>>>>> service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>>>>>> service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event
>>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>>>>>> service
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} -
>>>>>>>>>>>>>>> The
>>>>>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>>>>>> >> >>>> port
>>>>>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} -
>>>>>>>>>>>>>>> Using a shared
>>>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} -
>>>>>>>>>>>>>>> Using a shared
>>>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>>>>>> Service URL :
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
>>>>>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
>>>>>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>>>>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>>>>>> classloader
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new
>>>>>>>>>>>>>>> to this domain,
>>>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original
>>>>>>>>>>>>>>> goals of this work.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we
>>>>>>>>>>>>>>> take advantage of
>>>>>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start
>>>>>>>>>>>>>>> the processes or
>>>>>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but
>>>>>>>>>>>>>>> am unclear how
>>>>>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for
>>>>>>>>>>>>>>> this feature I can
>>>>>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva
>>>>>>>>>>>>>>> Weerawarana wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these
>>>>>>>>>>>>>>> with something
>>>>>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>>>>>> exact bits in it.
>>>>>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build
>>>>>>>>>>>>>>> custom images now?
>>>>>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>>>>>> normal??
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box).
>>>>>>>>>>>>>>> There are plenty of
>>>>>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides
>>>>>>>>>>>>>>> vagrant boxes [1],
>>>>>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful.
>>>>>>>>>>>>>>> Opscode also
>>>>>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet
>>>>>>>>>>>>>>> your needs, you can
>>>>>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them
>>>>>>>>>>>>>>> to build your
>>>>>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look
>>>>>>>>>>>>>>> too.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>>>>>> >> >>>>> [3]
>>>>>>>>>>>>>>> https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>>>>>> vagrant scripts
>>>>>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it
>>>>>>>>>>>>>>> out. Does it build
>>>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run
>>>>>>>>>>>>>>> the image?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for
>>>>>>>>>>>>>>> users; setting up
>>>>>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>>>>>> configuring
>>>>>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>>>>>> Stratos. My project
>>>>>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but
>>>>>>>>>>>>>>> I'm making good
>>>>>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands
>>>>>>>>>>>>>>> I can checkout,
>>>>>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am
>>>>>>>>>>>>>>> now working on
>>>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on
>>>>>>>>>>>>>>> my environment,
>>>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal
>>>>>>>>>>>>>>> will be
>>>>>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a
>>>>>>>>>>>>>>> single trivial
>>>>>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too
>>>>>>>>>>>>>>> much of stuff having
>>>>>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>>>>>> under 4GB with
>>>>>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this
>>>>>>>>>>>>>>> uses one Carbon
>>>>>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>>>>>> broker. (Carbon
>>>>>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>>>>>> products .. so
>>>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in
>>>>>>>>>>>>>>> one JVM but rather
>>>>>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to
>>>>>>>>>>>>>>> be in 4.0.0 - I
>>>>>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we
>>>>>>>>>>>>>>> write a direct
>>>>>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes
>>>>>>>>>>>>>>> and there's one
>>>>>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download
>>>>>>>>>>>>>>> becomes one JVM plus
>>>>>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images
>>>>>>>>>>>>>>> are booted up and
>>>>>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We
>>>>>>>>>>>>>>> don't have this
>>>>>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever
>>>>>>>>>>>>>>> (its not that hard
>>>>>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> For production deployments obviously this one
>>>>>>>>>>>>>>> server stuff is
>>>>>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>>>>>> execution. For that
>>>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and
>>>>>>>>>>>>>>> running plus maybe
>>>>>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with
>>>>>>>>>>>>>>> one command. Again
>>>>>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and
>>>>>>>>>>>>>>> whatever other
>>>>>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>>>>>> >> >>>>> components people want to use (and we need to make
>>>>>>>>>>>>>>> sure all the
>>>>>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>>>>>> engine, etc.)).
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same
>>>>>>>>>>>>>>> suggestion.
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the
>>>>>>>>>>>>>>> profiles work to have
>>>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory
>>>>>>>>>>>>>>> will be saved if
>>>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only
>>>>>>>>>>>>>>> profiles in stratos.
>>>>>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>>>>>> default profile
>>>>>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>>>>>> forward to your
>>>>>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to
>>>>>>>>>>>>>>> track the
>>>>>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect
>>>>>>>>>>>>>>> with me on
>>>>>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with
>>>>>>>>>>>>>>> me on LinkedIn.
>>>>>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499| +94
>>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499| +94
>>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499| +94
>>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>>> >> >>>> --
>>>>>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>>> >> >>> --
>>>>>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> --
>>>>>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>>> >> > --
>>>>>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> --
>>>>>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > --
>>>>>>>>>>>>>>> > Best Regards,
>>>>>>>>>>>>>>> > Nirmal
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Best Regards,
>>>>>>>>>>>>>> Nirmal
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Best Regards,
>>>>>>>>>>>> Nirmal
>>>>>>>>>>>>
>>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>
>>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> Nirmal
>>>>>>>>>>>
>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sameera Jayasoma
>>>>>>>>>>
>>>>>>>>>> blog: http://sameera.adahas.org
>>>>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Nirmal
>>>>>>>>>
>>>>>>>>> Nirmal Fernando.
>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sameera Jayasoma
>>>>>>>>
>>>>>>>> blog: http://sameera.adahas.org
>>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com,
>>> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
>>>
>>> *email: **azeez@wso2.com* <az...@wso2.com>
>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com,
> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
>
> *email: **azeez@wso2.com* <az...@wso2.com>
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* <http://blog.afkham.org>
> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> <http://lk.linkedin.com/in/afkhamazeez>*
>
> *Lean . Enterprise . Middleware*
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Afkham Azeez <af...@gmail.com>.
On Fri, Mar 21, 2014 at 9:36 AM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi Azeez,
>
>
> On Fri, Mar 21, 2014 at 12:20 AM, Afkham Azeez <af...@gmail.com> wrote:
>
>>
>>
>>
>> On Thu, Mar 20, 2014 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> Good news! Now the single JVM runs fine with ActiveMQ and I have tested
>>> up to subscription.
>>>
>>
>> Nice work Nirmal!
>>
>>>
>>> Next steps would be to test a full cycle (subscription -> activation ->
>>> access) with a puppet master.
>>>
>>> I suggest we use this only in developer environments at least in 4.0.
>>> Wdyt?
>>>
>>
>> In production, we can run multiple instances of this binary with the
>> relevant profiles. Have you tested starting up with different profiles?
>>
>
> No, given the time constraints, shall we stick only to the default profile
> at least for 4.0? Anyway, I'll try it once, but if we face some issues at
> the time of provisioning, we might not be able to fix those quickly.
>
I was under the impression that Pradeep created the profiles. One of the
main ideas was to have the profiles so that you can run the same pack with
different profiles. Having one pack to play around, and another for
production deployments is not good IMOP.
>
> Let me know your thoughts.
>
>>
>>
>>>
>>>
>>> On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <
>>> nirmal070125@gmail.com> wrote:
>>>
>>>> Update: fixed few other issues including one class loading issue.
>>>>
>>>> SingleJVM now can communicate with ActiveMQ.
>>>>
>>>> Now copying relevant configs to the product and doing a test round.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> With Sameera's help, we managed to fix it. Cloud-controller has a
>>>>> customized launch.ini file and that has this missing package. So, we gonna
>>>>> have a customized launch.ini file in the single JVM case too.
>>>>>
>>>>> Thanks Sameera.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> Hi Sameera,
>>>>>>
>>>>>> Actually I sent that info earlier, let me paste again.
>>>>>>
>>>>>>
>>>>>> osgi> diag 79
>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>> Direct constraints which are unresolved:
>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>> osgi>
>>>>>>
>>>>>> osgi> p javax.lang.model.type
>>>>>> No exported packages
>>>>>> osgi>
>>>>>>
>>>>>> In Cloud controller product:
>>>>>>
>>>>>> osgi> p javax.lang.model.type
>>>>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>>>>> osgi_3.8.1.v20120830-144521 [0]>
>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>> imports
>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>> package is not exported in the single jvm case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Nirmal,
>>>>>>>
>>>>>>> Can you check who is exporting the javax.lang.model.type package in
>>>>>>> a working package? Check whether this package is exported from the
>>>>>>> JDK via the equinox system bundle?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sameera.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <
>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Sameera,
>>>>>>>>
>>>>>>>> Thanks for the reply.
>>>>>>>>
>>>>>>>> Here's the full stack-trace:
>>>>>>>>
>>>>>>>>
>>>>>>>> java.lang.NoClassDefFoundError:
>>>>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>> at
>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>> at
>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>> at
>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>> at
>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>> at
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>> at
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>> at
>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>> at
>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>> at
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>> at
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>> at
>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> osgi> ss jcloud
>>>>>>>> "Framework is launched."
>>>>>>>>
>>>>>>>>
>>>>>>>> id State Bundle
>>>>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>>>>> osgi>
>>>>>>>> osgi>
>>>>>>>> osgi> diag 79
>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>> Direct constraints which are unresolved:
>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>> osgi>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Nirmal,
>>>>>>>>>
>>>>>>>>> Can you post the full stacktrace?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sameera.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> osgi> diag 79
>>>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>>>> Direct constraints which are unresolved:
>>>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>>>> osgi>
>>>>>>>>>>
>>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>>> No exported packages
>>>>>>>>>> osgi>
>>>>>>>>>>
>>>>>>>>>> In Cloud controller product:
>>>>>>>>>>
>>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>>> javax.lang.model.type;
>>>>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96]
>>>>>>>>>> imports
>>>>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>>>>> imports
>>>>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but
>>>>>>>>>> this package is not exported in the single jvm case.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <chsnow123@gmail.com
>>>>>>>>>>> > wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Sounds good, though at some point in the future should we
>>>>>>>>>>>> remove the dependency on using jndi? It seems a bit ironic that we are
>>>>>>>>>>>> using a cross platform protocol AMPQ, but are connecting to it with a Java
>>>>>>>>>>>> specific mechanism.
>>>>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <
>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the
>>>>>>>>>>>>> time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <
>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried
>>>>>>>>>>>>>> that unless it
>>>>>>>>>>>>>> >> gets applied soon it will become out of date and difficult
>>>>>>>>>>>>>> to commit
>>>>>>>>>>>>>> >> later on.
>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>>>>>> >> wrote:
>>>>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve
>>>>>>>>>>>>>> the jclouds
>>>>>>>>>>>>>> >> > CNF.
>>>>>>>>>>>>>> >> > After that, build the product named stratos. It contains
>>>>>>>>>>>>>> all the
>>>>>>>>>>>>>> >> > components
>>>>>>>>>>>>>> >> > except MB.
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> > thanks.
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >> This patch contains so many code changes. Can you
>>>>>>>>>>>>>> please provide an
>>>>>>>>>>>>>> >> >> update
>>>>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i
>>>>>>>>>>>>>> have to attend some
>>>>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>>>>> renaming stub
>>>>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to
>>>>>>>>>>>>>> jcloud class
>>>>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>>>>>>>>>>>>>> >> >>>> while
>>>>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
>>>>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>>>>> {super-tenant}
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>>>>> Repository :
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal
>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal
>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>>>>> service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event
>>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>>>>>>> service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>>>>> service
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} -
>>>>>>>>>>>>>> The
>>>>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>>>>> >> >>>> port
>>>>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using
>>>>>>>>>>>>>> a shared
>>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using
>>>>>>>>>>>>>> a shared
>>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>>>>> Service URL :
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
>>>>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar}
>>>>>>>>>>>>>> - Additional
>>>>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>>>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>>>>> classloader
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new
>>>>>>>>>>>>>> to this domain,
>>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original
>>>>>>>>>>>>>> goals of this work.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we
>>>>>>>>>>>>>> take advantage of
>>>>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start
>>>>>>>>>>>>>> the processes or
>>>>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but
>>>>>>>>>>>>>> am unclear how
>>>>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for
>>>>>>>>>>>>>> this feature I can
>>>>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these
>>>>>>>>>>>>>> with something
>>>>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>>>>> exact bits in it.
>>>>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build
>>>>>>>>>>>>>> custom images now?
>>>>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>>>>> normal??
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box).
>>>>>>>>>>>>>> There are plenty of
>>>>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides
>>>>>>>>>>>>>> vagrant boxes [1],
>>>>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful.
>>>>>>>>>>>>>> Opscode also
>>>>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet
>>>>>>>>>>>>>> your needs, you can
>>>>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them
>>>>>>>>>>>>>> to build your
>>>>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look
>>>>>>>>>>>>>> too.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>>>>> >> >>>>> [3]
>>>>>>>>>>>>>> https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>>>>> vagrant scripts
>>>>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it
>>>>>>>>>>>>>> out. Does it build
>>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run
>>>>>>>>>>>>>> the image?
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for
>>>>>>>>>>>>>> users; setting up
>>>>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>>>>> configuring
>>>>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>>>>> Stratos. My project
>>>>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but
>>>>>>>>>>>>>> I'm making good
>>>>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I
>>>>>>>>>>>>>> can checkout,
>>>>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am
>>>>>>>>>>>>>> now working on
>>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on
>>>>>>>>>>>>>> my environment,
>>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal
>>>>>>>>>>>>>> will be
>>>>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a
>>>>>>>>>>>>>> single trivial
>>>>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much
>>>>>>>>>>>>>> of stuff having
>>>>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>>>>> under 4GB with
>>>>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this
>>>>>>>>>>>>>> uses one Carbon
>>>>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>>>>> broker. (Carbon
>>>>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>>>>> products .. so
>>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in
>>>>>>>>>>>>>> one JVM but rather
>>>>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to
>>>>>>>>>>>>>> be in 4.0.0 - I
>>>>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we
>>>>>>>>>>>>>> write a direct
>>>>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes
>>>>>>>>>>>>>> and there's one
>>>>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download
>>>>>>>>>>>>>> becomes one JVM plus
>>>>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>>>>>>> booted up and
>>>>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We
>>>>>>>>>>>>>> don't have this
>>>>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its
>>>>>>>>>>>>>> not that hard
>>>>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>>>>>>> stuff is
>>>>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>>>>> execution. For that
>>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and
>>>>>>>>>>>>>> running plus maybe
>>>>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>>>>>>> command. Again
>>>>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and
>>>>>>>>>>>>>> whatever other
>>>>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>>>>> >> >>>>> components people want to use (and we need to make
>>>>>>>>>>>>>> sure all the
>>>>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>>>>> engine, etc.)).
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same
>>>>>>>>>>>>>> suggestion.
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the
>>>>>>>>>>>>>> profiles work to have
>>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory
>>>>>>>>>>>>>> will be saved if
>>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only
>>>>>>>>>>>>>> profiles in stratos.
>>>>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>>>>> default profile
>>>>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>>>>> forward to your
>>>>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to
>>>>>>>>>>>>>> track the
>>>>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect
>>>>>>>>>>>>>> with me on
>>>>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with
>>>>>>>>>>>>>> me on LinkedIn.
>>>>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>>> >> >>>> --
>>>>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>>> >> >>> --
>>>>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >> --
>>>>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> >
>>>>>>>>>>>>>> >> > --
>>>>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>> >> --
>>>>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> > --
>>>>>>>>>>>>>> > Best Regards,
>>>>>>>>>>>>>> > Nirmal
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Best Regards,
>>>>>>>>>>>>> Nirmal
>>>>>>>>>>>>>
>>>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> Nirmal
>>>>>>>>>>>
>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Best Regards,
>>>>>>>>>> Nirmal
>>>>>>>>>>
>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sameera Jayasoma
>>>>>>>>>
>>>>>>>>> blog: http://sameera.adahas.org
>>>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Nirmal
>>>>>>>>
>>>>>>>> Nirmal Fernando.
>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>
>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sameera Jayasoma
>>>>>>>
>>>>>>> blog: http://sameera.adahas.org
>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com,
>> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
>>
>> *email: **azeez@wso2.com* <az...@wso2.com>
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* <http://blog.afkham.org>
>> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> <http://lk.linkedin.com/in/afkhamazeez>*
>>
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com,
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*email: **azeez@wso2.com* <az...@wso2.com>
* cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org>
*twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
<http://lk.linkedin.com/in/afkhamazeez>*
*Lean . Enterprise . Middleware*
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Azeez,
On Fri, Mar 21, 2014 at 12:20 AM, Afkham Azeez <af...@gmail.com> wrote:
>
>
>
> On Thu, Mar 20, 2014 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Good news! Now the single JVM runs fine with ActiveMQ and I have tested
>> up to subscription.
>>
>
> Nice work Nirmal!
>
>>
>> Next steps would be to test a full cycle (subscription -> activation ->
>> access) with a puppet master.
>>
>> I suggest we use this only in developer environments at least in 4.0.
>> Wdyt?
>>
>
> In production, we can run multiple instances of this binary with the
> relevant profiles. Have you tested starting up with different profiles?
>
No, given the time constraints, shall we stick only to the default profile
at least for 4.0? Anyway, I'll try it once, but if we face some issues at
the time of provisioning, we might not be able to fix those quickly.
Let me know your thoughts.
>
>
>>
>>
>> On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <nirmal070125@gmail.com
>> > wrote:
>>
>>> Update: fixed few other issues including one class loading issue.
>>>
>>> SingleJVM now can communicate with ActiveMQ.
>>>
>>> Now copying relevant configs to the product and doing a test round.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> With Sameera's help, we managed to fix it. Cloud-controller has a
>>>> customized launch.ini file and that has this missing package. So, we gonna
>>>> have a customized launch.ini file in the single JVM case too.
>>>>
>>>> Thanks Sameera.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> Hi Sameera,
>>>>>
>>>>> Actually I sent that info earlier, let me paste again.
>>>>>
>>>>>
>>>>> osgi> diag 79
>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>> Direct constraints which are unresolved:
>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>> osgi>
>>>>>
>>>>> osgi> p javax.lang.model.type
>>>>> No exported packages
>>>>> osgi>
>>>>>
>>>>> In Cloud controller product:
>>>>>
>>>>> osgi> p javax.lang.model.type
>>>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>>>> osgi_3.8.1.v20120830-144521 [0]>
>>>>> jclouds-core_1.7.1 [65] imports
>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>> imports
>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>
>>>>>
>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>> package is not exported in the single jvm case.
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>>>>> sameera.madushan@gmail.com> wrote:
>>>>>
>>>>>> Hi Nirmal,
>>>>>>
>>>>>> Can you check who is exporting the javax.lang.model.type package in
>>>>>> a working package? Check whether this package is exported from the
>>>>>> JDK via the equinox system bundle?
>>>>>>
>>>>>> Thanks,
>>>>>> Sameera.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Sameera,
>>>>>>>
>>>>>>> Thanks for the reply.
>>>>>>>
>>>>>>> Here's the full stack-trace:
>>>>>>>
>>>>>>>
>>>>>>> java.lang.NoClassDefFoundError:
>>>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>>> at java.lang.Class.forName(Class.java:247)
>>>>>>> at
>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>> at
>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>> at
>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>> at
>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>> at
>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>> at
>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>> at
>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>> at
>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>> at
>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>> at
>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>> at
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>> at
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>> at
>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>> at
>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>> at
>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>> at
>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>> at
>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>> at
>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>> at
>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>> at
>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>> at
>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>> at
>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>> at
>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>> at
>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>> at
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>> at
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>> at
>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> osgi> ss jcloud
>>>>>>> "Framework is launched."
>>>>>>>
>>>>>>>
>>>>>>> id State Bundle
>>>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>>>> osgi>
>>>>>>> osgi>
>>>>>>> osgi> diag 79
>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>> Direct constraints which are unresolved:
>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>> osgi>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Nirmal,
>>>>>>>>
>>>>>>>> Can you post the full stacktrace?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sameera.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> osgi> diag 79
>>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>>> Direct constraints which are unresolved:
>>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>>> osgi>
>>>>>>>>>
>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>> No exported packages
>>>>>>>>> osgi>
>>>>>>>>>
>>>>>>>>> In Cloud controller product:
>>>>>>>>>
>>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>>> javax.lang.model.type;
>>>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96]
>>>>>>>>> imports
>>>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>>>> imports
>>>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>>>>> package is not exported in the single jvm case.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>>>>>>>
>>>>>>>>>>> Sounds good, though at some point in the future should we
>>>>>>>>>>> remove the dependency on using jndi? It seems a bit ironic that we are
>>>>>>>>>>> using a cross platform protocol AMPQ, but are connecting to it with a Java
>>>>>>>>>>> specific mechanism.
>>>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the
>>>>>>>>>>>> time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>>>>>>> unless it
>>>>>>>>>>>>> >> gets applied soon it will become out of date and difficult
>>>>>>>>>>>>> to commit
>>>>>>>>>>>>> >> later on.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>>>>> >> wrote:
>>>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve
>>>>>>>>>>>>> the jclouds
>>>>>>>>>>>>> >> > CNF.
>>>>>>>>>>>>> >> > After that, build the product named stratos. It contains
>>>>>>>>>>>>> all the
>>>>>>>>>>>>> >> > components
>>>>>>>>>>>>> >> > except MB.
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > thanks.
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>>>>>>> provide an
>>>>>>>>>>>>> >> >> update
>>>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have
>>>>>>>>>>>>> to attend some
>>>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>>>> renaming stub
>>>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to
>>>>>>>>>>>>> jcloud class
>>>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>>>>>>>>>>>>> >> >>>> while
>>>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
>>>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>>>> {super-tenant}
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>>>> Repository :
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal
>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal
>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>>>> service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event
>>>>>>>>>>>>> adaptor service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>>>>>> service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>>>> service
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} -
>>>>>>>>>>>>> The
>>>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>>>> >> >>>> port
>>>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using
>>>>>>>>>>>>> a shared
>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using
>>>>>>>>>>>>> a shared
>>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>>>> Service URL :
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>>>>>>>>>>>> - Mgt Console
>>>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar}
>>>>>>>>>>>>> - Additional
>>>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>>>> classloader
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to
>>>>>>>>>>>>> this domain,
>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals
>>>>>>>>>>>>> of this work.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we
>>>>>>>>>>>>> take advantage of
>>>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>>>>>>> processes or
>>>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but
>>>>>>>>>>>>> am unclear how
>>>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>>>>>>> feature I can
>>>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these
>>>>>>>>>>>>> with something
>>>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>>>> exact bits in it.
>>>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build
>>>>>>>>>>>>> custom images now?
>>>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>>>> normal??
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box).
>>>>>>>>>>>>> There are plenty of
>>>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides
>>>>>>>>>>>>> vagrant boxes [1],
>>>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful.
>>>>>>>>>>>>> Opscode also
>>>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>>>>>>> needs, you can
>>>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them
>>>>>>>>>>>>> to build your
>>>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look
>>>>>>>>>>>>> too.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>>>> >> >>>>> [3]
>>>>>>>>>>>>> https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>>>> vagrant scripts
>>>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out.
>>>>>>>>>>>>> Does it build
>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>>>>>>> image?
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for
>>>>>>>>>>>>> users; setting up
>>>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>>>> configuring
>>>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>>>> Stratos. My project
>>>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>>>>>>> making good
>>>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I
>>>>>>>>>>>>> can checkout,
>>>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am
>>>>>>>>>>>>> now working on
>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>>>>>>> environment,
>>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal
>>>>>>>>>>>>> will be
>>>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a
>>>>>>>>>>>>> single trivial
>>>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much
>>>>>>>>>>>>> of stuff having
>>>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>>>> under 4GB with
>>>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this
>>>>>>>>>>>>> uses one Carbon
>>>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>>>> broker. (Carbon
>>>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>>>> products .. so
>>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in one
>>>>>>>>>>>>> JVM but rather
>>>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to
>>>>>>>>>>>>> be in 4.0.0 - I
>>>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we
>>>>>>>>>>>>> write a direct
>>>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes
>>>>>>>>>>>>> and there's one
>>>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download
>>>>>>>>>>>>> becomes one JVM plus
>>>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>>>>>> booted up and
>>>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't
>>>>>>>>>>>>> have this
>>>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its
>>>>>>>>>>>>> not that hard
>>>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>>>>>> stuff is
>>>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>>>> execution. For that
>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running
>>>>>>>>>>>>> plus maybe
>>>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>>>>>> command. Again
>>>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever
>>>>>>>>>>>>> other
>>>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>>>> >> >>>>> components people want to use (and we need to make
>>>>>>>>>>>>> sure all the
>>>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>>>> engine, etc.)).
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same
>>>>>>>>>>>>> suggestion.
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the
>>>>>>>>>>>>> profiles work to have
>>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory
>>>>>>>>>>>>> will be saved if
>>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles
>>>>>>>>>>>>> in stratos.
>>>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>>>> default profile
>>>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>>>> forward to your
>>>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to
>>>>>>>>>>>>> track the
>>>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect with
>>>>>>>>>>>>> me on
>>>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with me
>>>>>>>>>>>>> on LinkedIn.
>>>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.;
>>>>>>>>>>>>> http://wso2.com/
>>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099;
>>>>>>>>>>>>> voip: +1 650 265
>>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>>> >> >>>> --
>>>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>>
>>>>>>>>>>>>> >> >>> --
>>>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> --
>>>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > --
>>>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> --
>>>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > --
>>>>>>>>>>>>> > Best Regards,
>>>>>>>>>>>>> > Nirmal
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Best Regards,
>>>>>>>>>>>> Nirmal
>>>>>>>>>>>>
>>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>>
>>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Best Regards,
>>>>>>>>>> Nirmal
>>>>>>>>>>
>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Nirmal
>>>>>>>>>
>>>>>>>>> Nirmal Fernando.
>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sameera Jayasoma
>>>>>>>>
>>>>>>>> blog: http://sameera.adahas.org
>>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sameera Jayasoma
>>>>>>
>>>>>> blog: http://sameera.adahas.org
>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com,
> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
>
> *email: **azeez@wso2.com* <az...@wso2.com>
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* <http://blog.afkham.org>
> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> <http://lk.linkedin.com/in/afkhamazeez>*
>
>
> *Lean . Enterprise . Middleware*
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Afkham Azeez <af...@gmail.com>.
On Thu, Mar 20, 2014 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Good news! Now the single JVM runs fine with ActiveMQ and I have tested up
> to subscription.
>
Nice work Nirmal!
>
> Next steps would be to test a full cycle (subscription -> activation ->
> access) with a puppet master.
>
> I suggest we use this only in developer environments at least in 4.0. Wdyt?
>
In production, we can run multiple instances of this binary with the
relevant profiles. Have you tested starting up with different profiles?
>
>
> On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Update: fixed few other issues including one class loading issue.
>>
>> SingleJVM now can communicate with ActiveMQ.
>>
>> Now copying relevant configs to the product and doing a test round.
>>
>>
>> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> With Sameera's help, we managed to fix it. Cloud-controller has a
>>> customized launch.ini file and that has this missing package. So, we gonna
>>> have a customized launch.ini file in the single JVM case too.
>>>
>>> Thanks Sameera.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> Hi Sameera,
>>>>
>>>> Actually I sent that info earlier, let me paste again.
>>>>
>>>>
>>>> osgi> diag 79
>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>> Direct constraints which are unresolved:
>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>> osgi>
>>>>
>>>> osgi> p javax.lang.model.type
>>>> No exported packages
>>>> osgi>
>>>>
>>>> In Cloud controller product:
>>>>
>>>> osgi> p javax.lang.model.type
>>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>>> osgi_3.8.1.v20120830-144521 [0]>
>>>> jclouds-core_1.7.1 [65] imports
>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>> imports
>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>
>>>>
>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>> package is not exported in the single jvm case.
>>>>
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>>>> sameera.madushan@gmail.com> wrote:
>>>>
>>>>> Hi Nirmal,
>>>>>
>>>>> Can you check who is exporting the javax.lang.model.type package in a
>>>>> working package? Check whether this package is exported from the JDK
>>>>> via the equinox system bundle?
>>>>>
>>>>> Thanks,
>>>>> Sameera.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> Hi Sameera,
>>>>>>
>>>>>> Thanks for the reply.
>>>>>>
>>>>>> Here's the full stack-trace:
>>>>>>
>>>>>>
>>>>>> java.lang.NoClassDefFoundError:
>>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>> at java.lang.Class.forName(Class.java:247)
>>>>>> at
>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>> at
>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>> at
>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>> at
>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>> at
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>> at
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>> at
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>> at
>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>> at
>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>> at
>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>> at
>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>> at
>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>> at
>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>> at
>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>> at
>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>>> at
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>> at
>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>
>>>>>>
>>>>>>
>>>>>> osgi> ss jcloud
>>>>>> "Framework is launched."
>>>>>>
>>>>>>
>>>>>> id State Bundle
>>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>>> osgi>
>>>>>> osgi>
>>>>>> osgi> diag 79
>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>> Direct constraints which are unresolved:
>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>> osgi>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>>>> sameera.madushan@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Nirmal,
>>>>>>>
>>>>>>> Can you post the full stacktrace?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sameera.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>
>>>>>>>> osgi> diag 79
>>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>>> Direct constraints which are unresolved:
>>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>>> osgi>
>>>>>>>>
>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>> No exported packages
>>>>>>>> osgi>
>>>>>>>>
>>>>>>>> In Cloud controller product:
>>>>>>>>
>>>>>>>> osgi> p javax.lang.model.type
>>>>>>>> javax.lang.model.type;
>>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>>> imports
>>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>>>> package is not exported in the single jvm case.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>>>>>>
>>>>>>>>>> Sounds good, though at some point in the future should we remove
>>>>>>>>>> the dependency on using jndi? It seems a bit ironic that we are using a
>>>>>>>>>> cross platform protocol AMPQ, but are connecting to it with a Java specific
>>>>>>>>>> mechanism.
>>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the
>>>>>>>>>>> time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <
>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>>>>>> unless it
>>>>>>>>>>>> >> gets applied soon it will become out of date and difficult
>>>>>>>>>>>> to commit
>>>>>>>>>>>> >> later on.
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>>>> >> wrote:
>>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve
>>>>>>>>>>>> the jclouds
>>>>>>>>>>>> >> > CNF.
>>>>>>>>>>>> >> > After that, build the product named stratos. It contains
>>>>>>>>>>>> all the
>>>>>>>>>>>> >> > components
>>>>>>>>>>>> >> > except MB.
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > thanks.
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>>>>>> provide an
>>>>>>>>>>>> >> >> update
>>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have
>>>>>>>>>>>> to attend some
>>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>>> renaming stub
>>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud
>>>>>>>>>>>> class
>>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry}
>>>>>>>>>>>> - Error
>>>>>>>>>>>> >> >>>> while
>>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>>> >> >>>> at
>>>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor}
>>>>>>>>>>>> - Deploying
>>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>>> {super-tenant}
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>>> Repository :
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>>>>>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal
>>>>>>>>>>>> adaptor service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>>>>>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>>>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>>> service
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>>> >> >>>> port
>>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>>>> shared
>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>>>> shared
>>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>>> >> >>>> service
>>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>>> Service URL :
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>>>>>>>>>>> - Mgt Console
>>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>>>>>>> Additional
>>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>>> classloader
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to
>>>>>>>>>>>> this domain,
>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals
>>>>>>>>>>>> of this work.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>>>>>>> advantage of
>>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>>>>>> processes or
>>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>>>>>>> unclear how
>>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>>>>>> feature I can
>>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>>>>>>> something
>>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>>> exact bits in it.
>>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build
>>>>>>>>>>>> custom images now?
>>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>>> normal??
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There
>>>>>>>>>>>> are plenty of
>>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>>>>>>> boxes [1],
>>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful.
>>>>>>>>>>>> Opscode also
>>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>>>>>> needs, you can
>>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>>>>>>> build your
>>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look
>>>>>>>>>>>> too.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>>> >> >>>>> [3]
>>>>>>>>>>>> https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>>> vagrant scripts
>>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out.
>>>>>>>>>>>> Does it build
>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>>>>>> image?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>>>>>>> setting up
>>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>>> configuring
>>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>>> Stratos. My project
>>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>>>>>> making good
>>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I
>>>>>>>>>>>> can checkout,
>>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am
>>>>>>>>>>>> now working on
>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>>>>>> environment,
>>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal
>>>>>>>>>>>> will be
>>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>>>>>>> trivial
>>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much
>>>>>>>>>>>> of stuff having
>>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>>> under 4GB with
>>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this
>>>>>>>>>>>> uses one Carbon
>>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>>> broker. (Carbon
>>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>>> products .. so
>>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in one
>>>>>>>>>>>> JVM but rather
>>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be
>>>>>>>>>>>> in 4.0.0 - I
>>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we
>>>>>>>>>>>> write a direct
>>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes
>>>>>>>>>>>> and there's one
>>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download
>>>>>>>>>>>> becomes one JVM plus
>>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>>>>> booted up and
>>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't
>>>>>>>>>>>> have this
>>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its
>>>>>>>>>>>> not that hard
>>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>>>>> stuff is
>>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>>> execution. For that
>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running
>>>>>>>>>>>> plus maybe
>>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>>>>> command. Again
>>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever
>>>>>>>>>>>> other
>>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>>> >> >>>>> components people want to use (and we need to make
>>>>>>>>>>>> sure all the
>>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>>> engine, etc.)).
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same
>>>>>>>>>>>> suggestion.
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the
>>>>>>>>>>>> profiles work to have
>>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will
>>>>>>>>>>>> be saved if
>>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles
>>>>>>>>>>>> in stratos.
>>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>>> default profile
>>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>>> forward to your
>>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to
>>>>>>>>>>>> track the
>>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect with
>>>>>>>>>>>> me on
>>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with me
>>>>>>>>>>>> on LinkedIn.
>>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>>> +1 650 265
>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>>> +1 650 265
>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>>> +1 650 265
>>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>>> @sanjiva
>>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>>
>>>>>>>>>>>> >> >>>> --
>>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>>
>>>>>>>>>>>> >> >>> --
>>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> --
>>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > --
>>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> --
>>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> > --
>>>>>>>>>>>> > Best Regards,
>>>>>>>>>>>> > Nirmal
>>>>>>>>>>>> >
>>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>> >
>>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>>> LinkedIn.
>>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> Nirmal
>>>>>>>>>>>
>>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Nirmal
>>>>>>>>>
>>>>>>>>> Nirmal Fernando.
>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Nirmal
>>>>>>>>
>>>>>>>> Nirmal Fernando.
>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>
>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sameera Jayasoma
>>>>>>>
>>>>>>> blog: http://sameera.adahas.org
>>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Jayasoma
>>>>>
>>>>> blog: http://sameera.adahas.org
>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com,
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*email: **azeez@wso2.com* <az...@wso2.com>
* cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org>
*twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
<http://lk.linkedin.com/in/afkhamazeez>*
*Lean . Enterprise . Middleware*
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Good news! Now the single JVM runs fine with ActiveMQ and I have tested up
to subscription.
Next steps would be to test a full cycle (subscription -> activation ->
access) with a puppet master.
I suggest we use this only in developer environments at least in 4.0. Wdyt?
On Thu, Mar 20, 2014 at 11:23 AM, Nirmal Fernando <ni...@gmail.com>wrote:
> Update: fixed few other issues including one class loading issue.
>
> SingleJVM now can communicate with ActiveMQ.
>
> Now copying relevant configs to the product and doing a test round.
>
>
> On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> With Sameera's help, we managed to fix it. Cloud-controller has a
>> customized launch.ini file and that has this missing package. So, we gonna
>> have a customized launch.ini file in the single JVM case too.
>>
>> Thanks Sameera.
>>
>>
>> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> Hi Sameera,
>>>
>>> Actually I sent that info earlier, let me paste again.
>>>
>>>
>>> osgi> diag 79
>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>> Direct constraints which are unresolved:
>>> Missing imported package javax.lang.model.type_0.0.0.
>>> osgi>
>>>
>>> osgi> p javax.lang.model.type
>>> No exported packages
>>> osgi>
>>>
>>> In Cloud controller product:
>>>
>>> osgi> p javax.lang.model.type
>>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>>> osgi_3.8.1.v20120830-144521 [0]>
>>> jclouds-core_1.7.1 [65] imports
>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>
>>>
>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>> package is not exported in the single jvm case.
>>>
>>>
>>>
>>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>>> sameera.madushan@gmail.com> wrote:
>>>
>>>> Hi Nirmal,
>>>>
>>>> Can you check who is exporting the javax.lang.model.type package in a
>>>> working package? Check whether this package is exported from the JDK
>>>> via the equinox system bundle?
>>>>
>>>> Thanks,
>>>> Sameera.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> Hi Sameera,
>>>>>
>>>>> Thanks for the reply.
>>>>>
>>>>> Here's the full stack-trace:
>>>>>
>>>>>
>>>>> java.lang.NoClassDefFoundError:
>>>>> org/jclouds/rest/ResourceNotFoundException
>>>>> at java.lang.Class.forName0(Native Method)
>>>>> at java.lang.Class.forName(Class.java:247)
>>>>> at
>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>> at
>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>> at
>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>> at
>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>> at
>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>> at
>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>> at
>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>> at
>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>> at
>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>> at
>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>> at
>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>> at
>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>> at
>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>> at
>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>> at
>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>> at
>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>> at
>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>> at
>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>> at
>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>> at
>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>> at
>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>> Caused by: java.lang.ClassNotFoundException:
>>>>> org.jclouds.rest.ResourceNotFoundException
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>> at
>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>
>>>>>
>>>>>
>>>>> osgi> ss jcloud
>>>>> "Framework is launched."
>>>>>
>>>>>
>>>>> id State Bundle
>>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>>> 79 INSTALLED jclouds-core_1.7.1
>>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>>> osgi>
>>>>> osgi>
>>>>> osgi> diag 79
>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>> Direct constraints which are unresolved:
>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>> osgi>
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>>> sameera.madushan@gmail.com> wrote:
>>>>>
>>>>>> Hi Nirmal,
>>>>>>
>>>>>> Can you post the full stacktrace?
>>>>>>
>>>>>> Thanks,
>>>>>> Sameera.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> osgi> diag 79
>>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>>> Direct constraints which are unresolved:
>>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>>> osgi>
>>>>>>>
>>>>>>> osgi> p javax.lang.model.type
>>>>>>> No exported packages
>>>>>>> osgi>
>>>>>>>
>>>>>>> In Cloud controller product:
>>>>>>>
>>>>>>> osgi> p javax.lang.model.type
>>>>>>> javax.lang.model.type;
>>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>>> imports
>>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>>> package is not exported in the single jvm case.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>
>>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>>>>>
>>>>>>>>> Sounds good, though at some point in the future should we remove
>>>>>>>>> the dependency on using jndi? It seems a bit ironic that we are using a
>>>>>>>>> cross platform protocol AMPQ, but are connecting to it with a Java specific
>>>>>>>>> mechanism.
>>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the
>>>>>>>>>> time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <chsnow123@gmail.com
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>>> > I'll continue on this.
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>> >>
>>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>>>>> unless it
>>>>>>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>>>>>>> commit
>>>>>>>>>>> >> later on.
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>>> >> wrote:
>>>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve
>>>>>>>>>>> the jclouds
>>>>>>>>>>> >> > CNF.
>>>>>>>>>>> >> > After that, build the product named stratos. It contains
>>>>>>>>>>> all the
>>>>>>>>>>> >> > components
>>>>>>>>>>> >> > except MB.
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > thanks.
>>>>>>>>>>> >> >
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>>>>> provide an
>>>>>>>>>>> >> >> update
>>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> Thanks,
>>>>>>>>>>> >> >> Sameera.
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have
>>>>>>>>>>> to attend some
>>>>>>>>>>> >> >>> other work.
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>> thanks.
>>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>>> >> >>> wrote:
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>>> renaming stub
>>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud
>>>>>>>>>>> class
>>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry}
>>>>>>>>>>> - Error
>>>>>>>>>>> >> >>>> while
>>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>>> >> >>>> at
>>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor}
>>>>>>>>>>> - Deploying
>>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService
>>>>>>>>>>> {super-tenant}
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>>> Repository :
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>>>>>> service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>>>>>>> service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor
>>>>>>>>>>> service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>>>>>> service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>>>> service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>>> service
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>>>>>> >> >>>> configuration
>>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>>> >> >>>> port
>>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>>> shared
>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>>> shared
>>>>>>>>>>> >> >>>> selector for
>>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>>>>>>>>>> >> >>>> service
>>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>>> >> >>>> Setting
>>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>>> >> >>>> ADC
>>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>>> Service URL :
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>> >> >>>> Server
>>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -
>>>>>>>>>>> Mgt Console
>>>>>>>>>>> >> >>>> URL :
>>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>>>>>> Additional
>>>>>>>>>>> >> >>>> SASL
>>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry}
>>>>>>>>>>> - Callback
>>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>>> classloader
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to
>>>>>>>>>>> this domain,
>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals
>>>>>>>>>>> of this work.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>>>>>> advantage of
>>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>>>>> processes or
>>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>>>>>> unclear how
>>>>>>>>>>> >> >>>>> they
>>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>>>>> feature I can
>>>>>>>>>>> >> >>>>> read?
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>>>>>> something
>>>>>>>>>>> >> >>>>> like
>>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the
>>>>>>>>>>> exact bits in it.
>>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>>>>>>> images now?
>>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>>> normal??
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There
>>>>>>>>>>> are plenty of
>>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>>>>>> boxes [1],
>>>>>>>>>>> >> >>>>> although
>>>>>>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode
>>>>>>>>>>> also
>>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>>>>> needs, you can
>>>>>>>>>>> >> >>>>> copy
>>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>>>>>> build your
>>>>>>>>>>> >> >>>>> own box
>>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>>> vagrant scripts
>>>>>>>>>>> >> >>>>> as
>>>>>>>>>>> >> >>>>> well!
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out.
>>>>>>>>>>> Does it build
>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>>>>> image?
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>>>>>> setting up
>>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>>> configuring
>>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack +
>>>>>>>>>>> Stratos. My project
>>>>>>>>>>> >> >>>>> is
>>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>>>>> making good
>>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I
>>>>>>>>>>> can checkout,
>>>>>>>>>>> >> >>>>> build and
>>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>>>>>>> working on
>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>>>>> environment,
>>>>>>>>>>> >> >>>>> but
>>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal will
>>>>>>>>>>> be
>>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> ---
>>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>>>>>> trivial
>>>>>>>>>>> >> >>>>> server
>>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>>>>>>> stuff having
>>>>>>>>>>> >> >>>>> to be
>>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in
>>>>>>>>>>> under 4GB with
>>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses
>>>>>>>>>>> one Carbon
>>>>>>>>>>> >> >>>>> server to
>>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>>> broker. (Carbon
>>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>>> products .. so
>>>>>>>>>>> >> >>>>> the
>>>>>>>>>>> >> >>>>> decision should not be based on ability to run in one
>>>>>>>>>>> JVM but rather
>>>>>>>>>>> >> >>>>> just
>>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be
>>>>>>>>>>> in 4.0.0 - I
>>>>>>>>>>> >> >>>>> think
>>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write
>>>>>>>>>>> a direct
>>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>>>>>>> there's one
>>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes
>>>>>>>>>>> one JVM plus
>>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>>>> booted up and
>>>>>>>>>>> >> >>>>> run
>>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't
>>>>>>>>>>> have this
>>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its
>>>>>>>>>>> not that hard
>>>>>>>>>>> >> >>>>> to make
>>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>>>> stuff is
>>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>>> execution. For that
>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running
>>>>>>>>>>> plus maybe
>>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>>>> command. Again
>>>>>>>>>>> >> >>>>> its
>>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever
>>>>>>>>>>> other
>>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>>> >> >>>>> components people want to use (and we need to make sure
>>>>>>>>>>> all the
>>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>>> engine, etc.)).
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles
>>>>>>>>>>> work to have
>>>>>>>>>>> >> >>>>> a
>>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will
>>>>>>>>>>> be saved if
>>>>>>>>>>> >> >>>>> we
>>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles
>>>>>>>>>>> in stratos.
>>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>>> default profile
>>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>>> forward to your
>>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track
>>>>>>>>>>> the
>>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>> >> >>>>> >>
>>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect with
>>>>>>>>>>> me on
>>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> >
>>>>>>>>>>> >> >>>>> > --
>>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>> >> >>>>> Check out my professional profile and connect with me
>>>>>>>>>>> on LinkedIn.
>>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>> +1 650 265
>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>> @sanjiva
>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>> +1 650 265
>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>> @sanjiva
>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> --
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>>> 11 214 5345)
>>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>>> +1 650 265
>>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter:
>>>>>>>>>>> @sanjiva
>>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>>
>>>>>>>>>>> >> >>>> --
>>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>>
>>>>>>>>>>> >> >>> --
>>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> --
>>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>>> >> >
>>>>>>>>>>> >> >
>>>>>>>>>>> >> >
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > --
>>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >> --
>>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>>> LinkedIn.
>>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > --
>>>>>>>>>>> > Best Regards,
>>>>>>>>>>> > Nirmal
>>>>>>>>>>> >
>>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>> >
>>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Check out my professional profile and connect with me on
>>>>>>>>>>> LinkedIn.
>>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Best Regards,
>>>>>>>>>> Nirmal
>>>>>>>>>>
>>>>>>>>>> Nirmal Fernando.
>>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Nirmal
>>>>>>>>
>>>>>>>> Nirmal Fernando.
>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>
>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sameera Jayasoma
>>>>>>
>>>>>> blog: http://sameera.adahas.org
>>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sameera Jayasoma
>>>>
>>>> blog: http://sameera.adahas.org
>>>> twitter: https://twitter.com/sameerajayasoma
>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Update: fixed few other issues including one class loading issue.
SingleJVM now can communicate with ActiveMQ.
Now copying relevant configs to the product and doing a test round.
On Wed, Mar 19, 2014 at 4:42 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> With Sameera's help, we managed to fix it. Cloud-controller has a
> customized launch.ini file and that has this missing package. So, we gonna
> have a customized launch.ini file in the single JVM case too.
>
> Thanks Sameera.
>
>
> On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi Sameera,
>>
>> Actually I sent that info earlier, let me paste again.
>>
>>
>> osgi> diag 79
>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>> Direct constraints which are unresolved:
>> Missing imported package javax.lang.model.type_0.0.0.
>> osgi>
>>
>> osgi> p javax.lang.model.type
>> No exported packages
>> osgi>
>>
>> In Cloud controller product:
>>
>> osgi> p javax.lang.model.type
>> javax.lang.model.type; version="0.0.0"<org.eclipse.
>> osgi_3.8.1.v20120830-144521 [0]>
>> jclouds-core_1.7.1 [65] imports
>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>
>>
>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>> package is not exported in the single jvm case.
>>
>>
>>
>> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
>> sameera.madushan@gmail.com> wrote:
>>
>>> Hi Nirmal,
>>>
>>> Can you check who is exporting the javax.lang.model.type package in a
>>> working package? Check whether this package is exported from the JDK
>>> via the equinox system bundle?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> Hi Sameera,
>>>>
>>>> Thanks for the reply.
>>>>
>>>> Here's the full stack-trace:
>>>>
>>>>
>>>> java.lang.NoClassDefFoundError:
>>>> org/jclouds/rest/ResourceNotFoundException
>>>> at java.lang.Class.forName0(Native Method)
>>>> at java.lang.Class.forName(Class.java:247)
>>>> at
>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>> at
>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>> at
>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>> at
>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>> at
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>> at
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>> at
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>> at
>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>> at
>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>> at
>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>> at
>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>> at
>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>> at
>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>> at
>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>> at
>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>> at
>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>> at
>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>> at
>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>> Caused by: java.lang.ClassNotFoundException:
>>>> org.jclouds.rest.ResourceNotFoundException
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>> at
>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>
>>>>
>>>>
>>>> osgi> ss jcloud
>>>> "Framework is launched."
>>>>
>>>>
>>>> id State Bundle
>>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>>> 78 INSTALLED jclouds-compute_1.7.1
>>>> 79 INSTALLED jclouds-core_1.7.1
>>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>>> 81 INSTALLED jclouds-joda_1.7.1
>>>> 82 INSTALLED jclouds-netty_1.7.1
>>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>>> 85 INSTALLED jclouds-sshj_1.7.1
>>>> osgi>
>>>> osgi>
>>>> osgi> diag 79
>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>> Direct constraints which are unresolved:
>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>> osgi>
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>>> sameera.madushan@gmail.com> wrote:
>>>>
>>>>> Hi Nirmal,
>>>>>
>>>>> Can you post the full stacktrace?
>>>>>
>>>>> Thanks,
>>>>> Sameera.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> osgi> diag 79
>>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>>> Direct constraints which are unresolved:
>>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>>> osgi>
>>>>>>
>>>>>> osgi> p javax.lang.model.type
>>>>>> No exported packages
>>>>>> osgi>
>>>>>>
>>>>>> In Cloud controller product:
>>>>>>
>>>>>> osgi> p javax.lang.model.type
>>>>>> javax.lang.model.type;
>>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>>> jclouds-core_1.7.1 [65] imports
>>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>>> imports
>>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>>> package is not exported in the single jvm case.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>>> dependency issue. I'm looking into it now.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>>>>
>>>>>>>> Sounds good, though at some point in the future should we remove
>>>>>>>> the dependency on using jndi? It seems a bit ironic that we are using a
>>>>>>>> cross platform protocol AMPQ, but are connecting to it with a Java specific
>>>>>>>> mechanism.
>>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the
>>>>>>>>> time being without much research, I'm going to use ActiveMQ.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>>>>>>>
>>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>>> > I'll continue on this.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <
>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>> >>
>>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>>>> unless it
>>>>>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>>>>>> commit
>>>>>>>>>> >> later on.
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>>> >> wrote:
>>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>>>>>>>> jclouds
>>>>>>>>>> >> > CNF.
>>>>>>>>>> >> > After that, build the product named stratos. It contains all
>>>>>>>>>> the
>>>>>>>>>> >> > components
>>>>>>>>>> >> > except MB.
>>>>>>>>>> >> >
>>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>>> >> >
>>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>>> >> >
>>>>>>>>>> >> > thanks.
>>>>>>>>>> >> >
>>>>>>>>>> >> >
>>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>>>> provide an
>>>>>>>>>> >> >> update
>>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> Thanks,
>>>>>>>>>> >> >> Sameera.
>>>>>>>>>> >> >>
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>>> >> >> wrote:
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>>>>>>>> attend some
>>>>>>>>>> >> >>> other work.
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>> thanks.
>>>>>>>>>> >> >>> --Pradeep
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>>> >> >>> wrote:
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>>> renaming stub
>>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud
>>>>>>>>>> class
>>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -
>>>>>>>>>> Error
>>>>>>>>>> >> >>>> while
>>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>>> >> >>>> at
>>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>>>>>>>> Deploying
>>>>>>>>>> >> >>>> Axis2
>>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>>> Repository :
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>>>>> service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>>>>>> service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>>>>> service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>>> service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor
>>>>>>>>>> service
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>>>>> >> >>>> configuration
>>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>>> >> >>>> : 9443
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>>> >> >>>> port
>>>>>>>>>> >> >>>> : 9763
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>> shared
>>>>>>>>>> >> >>>> selector for
>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>>> shared
>>>>>>>>>> >> >>>> selector for
>>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl}
>>>>>>>>>> - Task
>>>>>>>>>> >> >>>> service
>>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>>> >> >>>> Setting
>>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>>> >> >>>> ADC
>>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>>> Service URL :
>>>>>>>>>> >> >>>>
>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>>> >> >>>> scheduled:
>>>>>>>>>> [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>> >> >>>> Server
>>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>>> >> >>>>
>>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>>> >> >>>> WSO2
>>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -
>>>>>>>>>> Mgt Console
>>>>>>>>>> >> >>>> URL :
>>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>>>>> Additional
>>>>>>>>>> >> >>>> SASL
>>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry}
>>>>>>>>>> - Callback
>>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>>> >> >>>> PLAIN
>>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>>> classloader
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>>> >> >>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to
>>>>>>>>>> this domain,
>>>>>>>>>> >> >>>>> but
>>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals of
>>>>>>>>>> this work.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>>>>> advantage of
>>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>>>> processes or
>>>>>>>>>> >> >>>>> what? I
>>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>>>>> unclear how
>>>>>>>>>> >> >>>>> they
>>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>>>> feature I can
>>>>>>>>>> >> >>>>> read?
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>>>>> something
>>>>>>>>>> >> >>>>> like
>>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the exact
>>>>>>>>>> bits in it.
>>>>>>>>>> >> >>>>> Looks
>>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>>>>>> images now?
>>>>>>>>>> >> >>>>> Or is
>>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>>> normal??
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There
>>>>>>>>>> are plenty of
>>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>>>>> boxes [1],
>>>>>>>>>> >> >>>>> although
>>>>>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode
>>>>>>>>>> also
>>>>>>>>>> >> >>>>> provide some
>>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>>>> needs, you can
>>>>>>>>>> >> >>>>> copy
>>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>>>>> build your
>>>>>>>>>> >> >>>>> own box
>>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> ---
>>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>>> vagrant scripts
>>>>>>>>>> >> >>>>> as
>>>>>>>>>> >> >>>>> well!
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out.
>>>>>>>>>> Does it build
>>>>>>>>>> >> >>>>> a
>>>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>>>> image?
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>>>>> setting up
>>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>>> configuring
>>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos.
>>>>>>>>>> My project
>>>>>>>>>> >> >>>>> is
>>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>>>> making good
>>>>>>>>>> >> >>>>> progress.
>>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>>>>>>>> checkout,
>>>>>>>>>> >> >>>>> build and
>>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>>>>>> working on
>>>>>>>>>> >> >>>>> the
>>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>>>> environment,
>>>>>>>>>> >> >>>>> but
>>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal will
>>>>>>>>>> be
>>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>>> >> >>>>> Chris
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> ---
>>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>>>>> trivial
>>>>>>>>>> >> >>>>> server
>>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>>>>>> stuff having
>>>>>>>>>> >> >>>>> to be
>>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in under
>>>>>>>>>> 4GB with
>>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses
>>>>>>>>>> one Carbon
>>>>>>>>>> >> >>>>> server to
>>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>>> broker. (Carbon
>>>>>>>>>> >> >>>>> stuff
>>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>>> products .. so
>>>>>>>>>> >> >>>>> the
>>>>>>>>>> >> >>>>> decision should not be based on ability to run in one
>>>>>>>>>> JVM but rather
>>>>>>>>>> >> >>>>> just
>>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be
>>>>>>>>>> in 4.0.0 - I
>>>>>>>>>> >> >>>>> think
>>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write
>>>>>>>>>> a direct
>>>>>>>>>> >> >>>>> plugin
>>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>>>>>> there's one
>>>>>>>>>> >> >>>>> JVM that
>>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes
>>>>>>>>>> one JVM plus
>>>>>>>>>> >> >>>>> a URL
>>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>>> booted up and
>>>>>>>>>> >> >>>>> run
>>>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't
>>>>>>>>>> have this
>>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not
>>>>>>>>>> that hard
>>>>>>>>>> >> >>>>> to make
>>>>>>>>>> >> >>>>> it work).
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>>> stuff is
>>>>>>>>>> >> >>>>> nonsense
>>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>>> execution. For that
>>>>>>>>>> >> >>>>> we
>>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running
>>>>>>>>>> plus maybe
>>>>>>>>>> >> >>>>> Boto
>>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>>> command. Again
>>>>>>>>>> >> >>>>> its
>>>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever
>>>>>>>>>> other
>>>>>>>>>> >> >>>>> pluggable
>>>>>>>>>> >> >>>>> components people want to use (and we need to make sure
>>>>>>>>>> all the
>>>>>>>>>> >> >>>>> parts are
>>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>>> engine, etc.)).
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>>> >> >>>>> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Thanks
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles
>>>>>>>>>> work to have
>>>>>>>>>> >> >>>>> a
>>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will
>>>>>>>>>> be saved if
>>>>>>>>>> >> >>>>> we
>>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>>> >> >>>>> > btw,
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>>>>>>>> stratos.
>>>>>>>>>> >> >>>>> > However,
>>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>>> default profile
>>>>>>>>>> >> >>>>> > (the
>>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > thanks
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>>> >> >>>>> >>
>>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking
>>>>>>>>>> forward to your
>>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>>> >> >>>>> >>
>>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track
>>>>>>>>>> the
>>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>> >> >>>>> >> >
>>>>>>>>>> >> >>>>> >> > --
>>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>> >> >>>>> >>
>>>>>>>>>> >> >>>>> >>
>>>>>>>>>> >> >>>>> >>
>>>>>>>>>> >> >>>>> >> --
>>>>>>>>>> >> >>>>> >> Check out my professional profile and connect with me
>>>>>>>>>> on
>>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> >
>>>>>>>>>> >> >>>>> > --
>>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> --
>>>>>>>>>> >> >>>>> Check out my professional profile and connect with me on
>>>>>>>>>> LinkedIn.
>>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> --
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>> 11 214 5345)
>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>> +1 650 265
>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> --
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>> 11 214 5345)
>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>> +1 650 265
>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> --
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>>> 11 214 5345)
>>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip:
>>>>>>>>>> +1 650 265
>>>>>>>>>> >> >>>>> 8311
>>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>>
>>>>>>>>>> >> >>>> --
>>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>>
>>>>>>>>>> >> >>> --
>>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>>> >> >>
>>>>>>>>>> >> >>
>>>>>>>>>> >> >>
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> --
>>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>>> >> >
>>>>>>>>>> >> >
>>>>>>>>>> >> >
>>>>>>>>>> >> >
>>>>>>>>>> >> > --
>>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> --
>>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>>> LinkedIn.
>>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > --
>>>>>>>>>> > Best Regards,
>>>>>>>>>> > Nirmal
>>>>>>>>>> >
>>>>>>>>>> > Nirmal Fernando.
>>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>>> >
>>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Nirmal
>>>>>>>>>
>>>>>>>>> Nirmal Fernando.
>>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Jayasoma
>>>>>
>>>>> blog: http://sameera.adahas.org
>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma
>>>
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
With Sameera's help, we managed to fix it. Cloud-controller has a
customized launch.ini file and that has this missing package. So, we gonna
have a customized launch.ini file in the single JVM case too.
Thanks Sameera.
On Wed, Mar 19, 2014 at 4:29 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi Sameera,
>
> Actually I sent that info earlier, let me paste again.
>
>
> osgi> diag 79
> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
> Direct constraints which are unresolved:
> Missing imported package javax.lang.model.type_0.0.0.
> osgi>
>
> osgi> p javax.lang.model.type
> No exported packages
> osgi>
>
> In Cloud controller product:
>
> osgi> p javax.lang.model.type
> javax.lang.model.type; version="0.0.0"<org.eclipse.
> osgi_3.8.1.v20120830-144521 [0]>
> jclouds-core_1.7.1 [65] imports
> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>
>
> org.eclipse.osgi_3.8.1* is activated in both the servers, but this package
> is not exported in the single jvm case.
>
>
>
> On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
> sameera.madushan@gmail.com> wrote:
>
>> Hi Nirmal,
>>
>> Can you check who is exporting the javax.lang.model.type package in a
>> working package? Check whether this package is exported from the JDK via
>> the equinox system bundle?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> Hi Sameera,
>>>
>>> Thanks for the reply.
>>>
>>> Here's the full stack-trace:
>>>
>>>
>>> java.lang.NoClassDefFoundError:
>>> org/jclouds/rest/ResourceNotFoundException
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:247)
>>> at
>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>> at
>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>> at
>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>> at
>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>> at
>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>> at
>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>> at
>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>> at
>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> at
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>> at
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:662)
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.jclouds.rest.ResourceNotFoundException
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>
>>>
>>>
>>> osgi> ss jcloud
>>> "Framework is launched."
>>>
>>>
>>> id State Bundle
>>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>>> 78 INSTALLED jclouds-compute_1.7.1
>>> 79 INSTALLED jclouds-core_1.7.1
>>> 80 INSTALLED jclouds-enterprise_1.7.1
>>> 81 INSTALLED jclouds-joda_1.7.1
>>> 82 INSTALLED jclouds-netty_1.7.1
>>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>>> 84 INSTALLED jclouds-slf4j_1.7.1
>>> 85 INSTALLED jclouds-sshj_1.7.1
>>> osgi>
>>> osgi>
>>> osgi> diag 79
>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>> Direct constraints which are unresolved:
>>> Missing imported package javax.lang.model.type_0.0.0.
>>> osgi>
>>>
>>>
>>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>>> sameera.madushan@gmail.com> wrote:
>>>
>>>> Hi Nirmal,
>>>>
>>>> Can you post the full stacktrace?
>>>>
>>>> Thanks,
>>>> Sameera.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> osgi> diag 79
>>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>>> Direct constraints which are unresolved:
>>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>>> osgi>
>>>>>
>>>>> osgi> p javax.lang.model.type
>>>>> No exported packages
>>>>> osgi>
>>>>>
>>>>> In Cloud controller product:
>>>>>
>>>>> osgi> p javax.lang.model.type
>>>>> javax.lang.model.type;
>>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>>> jclouds-core_1.7.1 [65] imports
>>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>>> imports
>>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>>
>>>>>
>>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>>> package is not exported in the single jvm case.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>>> dependency issue. I'm looking into it now.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>>>
>>>>>>> Sounds good, though at some point in the future should we remove
>>>>>>> the dependency on using jndi? It seems a bit ironic that we are using a
>>>>>>> cross platform protocol AMPQ, but are connecting to it with a Java specific
>>>>>>> mechanism.
>>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time
>>>>>>>> being without much research, I'm going to use ActiveMQ.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>>>>>>
>>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>>> > I'll continue on this.
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> >>
>>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>>> unless it
>>>>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>>>>> commit
>>>>>>>>> >> later on.
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>>> pradeepfn@gmail.com>
>>>>>>>>> >> wrote:
>>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>>>>>>> jclouds
>>>>>>>>> >> > CNF.
>>>>>>>>> >> > After that, build the product named stratos. It contains all
>>>>>>>>> the
>>>>>>>>> >> > components
>>>>>>>>> >> > except MB.
>>>>>>>>> >> >
>>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>>> >> >
>>>>>>>>> >> > hope this helps.. :)
>>>>>>>>> >> >
>>>>>>>>> >> > thanks.
>>>>>>>>> >> >
>>>>>>>>> >> >
>>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>>> >> >>
>>>>>>>>> >> >> Hi Pradeep,
>>>>>>>>> >> >>
>>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>>> provide an
>>>>>>>>> >> >> update
>>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>>> >> >>
>>>>>>>>> >> >> Thanks,
>>>>>>>>> >> >> Sameera.
>>>>>>>>> >> >>
>>>>>>>>> >> >>
>>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>>> >> >> wrote:
>>>>>>>>> >> >>>
>>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>>>>>>> attend some
>>>>>>>>> >> >>> other work.
>>>>>>>>> >> >>>
>>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>>> >> >>>
>>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>>> >> >>>
>>>>>>>>> >> >>> thanks.
>>>>>>>>> >> >>> --Pradeep
>>>>>>>>> >> >>>
>>>>>>>>> >> >>>
>>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>>> >> >>> wrote:
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> Hi Guys,
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> I managed to workaround the classloading issue, by
>>>>>>>>> renaming stub
>>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud
>>>>>>>>> class
>>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -
>>>>>>>>> Error
>>>>>>>>> >> >>>> while
>>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>> Method)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>>> >> >>>> at
>>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>>> >> >>>> at
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>>> >> >>>> at
>>>>>>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>>> >> >>>> ... 49 more
>>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>>>>>>> Deploying
>>>>>>>>> >> >>>> Axis2
>>>>>>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>>> Repository :
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>>>> service
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>>>>> service
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>>>> service
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>>> service
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>>>> >> >>>> configuration
>>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>>> >> >>>> HTTPS port
>>>>>>>>> >> >>>> : 9443
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>>> >> >>>> port
>>>>>>>>> >> >>>> : 9763
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>> shared
>>>>>>>>> >> >>>> selector for
>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>>> shared
>>>>>>>>> >> >>>> selector for
>>>>>>>>> >> >>>> servlet write/read
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl}
>>>>>>>>> - Task
>>>>>>>>> >> >>>> service
>>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>>> >> >>>> Setting
>>>>>>>>> >> >>>> config properties into System properties
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>>> >> >>>> ADC
>>>>>>>>> >> >>>> management server component is activated
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX
>>>>>>>>> Service URL :
>>>>>>>>> >> >>>>
>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>>>>>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>> >> >>>> Server
>>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>>> >> >>>>
>>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>>> >> >>>> WSO2
>>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -
>>>>>>>>> Mgt Console
>>>>>>>>> >> >>>> URL :
>>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>>>> Additional
>>>>>>>>> >> >>>> SASL
>>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>>>>>>>> Callback
>>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>>> CRAM-MD5-HASHED
>>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>>> >> >>>> PLAIN
>>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>>> classloader
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>>> shahhaqu@cisco.com>
>>>>>>>>> >> >>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to
>>>>>>>>> this domain,
>>>>>>>>> >> >>>>> but
>>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals of
>>>>>>>>> this work.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>>>> advantage of
>>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>>> processes or
>>>>>>>>> >> >>>>> what? I
>>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>>>> unclear how
>>>>>>>>> >> >>>>> they
>>>>>>>>> >> >>>>> relate to this.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>>> feature I can
>>>>>>>>> >> >>>>> read?
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana
>>>>>>>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>>>> something
>>>>>>>>> >> >>>>> like
>>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the exact
>>>>>>>>> bits in it.
>>>>>>>>> >> >>>>> Looks
>>>>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>>>>> images now?
>>>>>>>>> >> >>>>> Or is
>>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>>> normal??
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>> >> >>>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There
>>>>>>>>> are plenty of
>>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>>>> boxes [1],
>>>>>>>>> >> >>>>> although
>>>>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode
>>>>>>>>> also
>>>>>>>>> >> >>>>> provide some
>>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>>> needs, you can
>>>>>>>>> >> >>>>> copy
>>>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>>>> build your
>>>>>>>>> >> >>>>> own box
>>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Chris
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> ---
>>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>> >> >>>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>>> vagrant scripts
>>>>>>>>> >> >>>>> as
>>>>>>>>> >> >>>>> well!
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out.
>>>>>>>>> Does it build
>>>>>>>>> >> >>>>> a
>>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>>> image?
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>> >> >>>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>>>> setting up
>>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>>> configuring
>>>>>>>>> >> >>>>> guest proxy
>>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos.
>>>>>>>>> My project
>>>>>>>>> >> >>>>> is
>>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>>> making good
>>>>>>>>> >> >>>>> progress.
>>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>>>>>>> checkout,
>>>>>>>>> >> >>>>> build and
>>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>>>>> working on
>>>>>>>>> >> >>>>> the
>>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>>> environment,
>>>>>>>>> >> >>>>> but
>>>>>>>>> >> >>>>> for me the first goal is automation, the next goal will be
>>>>>>>>> >> >>>>> efficiency.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Many thanks,
>>>>>>>>> >> >>>>> Chris
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> ---
>>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>>> sanjiva@wso2.com>
>>>>>>>>> >> >>>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>>>> trivial
>>>>>>>>> >> >>>>> server
>>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>>>>> stuff having
>>>>>>>>> >> >>>>> to be
>>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in under
>>>>>>>>> 4GB with
>>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses
>>>>>>>>> one Carbon
>>>>>>>>> >> >>>>> server to
>>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>>> broker. (Carbon
>>>>>>>>> >> >>>>> stuff
>>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>>> products .. so
>>>>>>>>> >> >>>>> the
>>>>>>>>> >> >>>>> decision should not be based on ability to run in one JVM
>>>>>>>>> but rather
>>>>>>>>> >> >>>>> just
>>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be in
>>>>>>>>> 4.0.0 - I
>>>>>>>>> >> >>>>> think
>>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a
>>>>>>>>> direct
>>>>>>>>> >> >>>>> plugin
>>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>>>>> there's one
>>>>>>>>> >> >>>>> JVM that
>>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes
>>>>>>>>> one JVM plus
>>>>>>>>> >> >>>>> a URL
>>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>>> booted up and
>>>>>>>>> >> >>>>> run
>>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't
>>>>>>>>> have this
>>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not
>>>>>>>>> that hard
>>>>>>>>> >> >>>>> to make
>>>>>>>>> >> >>>>> it work).
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> For production deployments obviously this one server
>>>>>>>>> stuff is
>>>>>>>>> >> >>>>> nonsense
>>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>>> execution. For that
>>>>>>>>> >> >>>>> we
>>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running
>>>>>>>>> plus maybe
>>>>>>>>> >> >>>>> Boto
>>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>>> command. Again
>>>>>>>>> >> >>>>> its
>>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever
>>>>>>>>> other
>>>>>>>>> >> >>>>> pluggable
>>>>>>>>> >> >>>>> components people want to use (and we need to make sure
>>>>>>>>> all the
>>>>>>>>> >> >>>>> parts are
>>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP
>>>>>>>>> engine, etc.)).
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Makes sense?
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>>> >> >>>>> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Thanks
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> --Pradeep
>>>>>>>>> >> >>>>> sent from my phone
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <
>>>>>>>>> chsnow123@gmail.com> wrote:
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles
>>>>>>>>> work to have
>>>>>>>>> >> >>>>> a
>>>>>>>>> >> >>>>> view on that :(
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will be
>>>>>>>>> saved if
>>>>>>>>> >> >>>>> we
>>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>>> >> >>>>> > btw,
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>>>>>>> stratos.
>>>>>>>>> >> >>>>> > However,
>>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to
>>>>>>>>> default profile
>>>>>>>>> >> >>>>> > (the
>>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > WDYT?
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > thanks
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>>> chsnow123@gmail.com>
>>>>>>>>> >> >>>>> > wrote:
>>>>>>>>> >> >>>>> >>
>>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward
>>>>>>>>> to your
>>>>>>>>> >> >>>>> >> findings!
>>>>>>>>> >> >>>>> >>
>>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>>> >> >>>>> >> wrote:
>>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>>> >> >>>>> >> >
>>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track
>>>>>>>>> the
>>>>>>>>> >> >>>>> >> > progress..
>>>>>>>>> >> >>>>> >> >
>>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>>> >> >>>>> >> >
>>>>>>>>> >> >>>>> >> >
>>>>>>>>> >> >>>>> >> > --
>>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>> >> >>>>> >>
>>>>>>>>> >> >>>>> >>
>>>>>>>>> >> >>>>> >>
>>>>>>>>> >> >>>>> >> --
>>>>>>>>> >> >>>>> >> Check out my professional profile and connect with me
>>>>>>>>> on
>>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> >
>>>>>>>>> >> >>>>> > --
>>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> --
>>>>>>>>> >> >>>>> Check out my professional profile and connect with me on
>>>>>>>>> LinkedIn.
>>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> --
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>> 11 214 5345)
>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>>>> 650 265
>>>>>>>>> >> >>>>> 8311
>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> --
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>> 11 214 5345)
>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>>>> 650 265
>>>>>>>>> >> >>>>> 8311
>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> --
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>>> 11 214 5345)
>>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>>>> 650 265
>>>>>>>>> >> >>>>> 8311
>>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>>
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>>
>>>>>>>>> >> >>>> --
>>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>>> >> >>>
>>>>>>>>> >> >>>
>>>>>>>>> >> >>>
>>>>>>>>> >> >>>
>>>>>>>>> >> >>> --
>>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>>> >> >>
>>>>>>>>> >> >>
>>>>>>>>> >> >>
>>>>>>>>> >> >>
>>>>>>>>> >> >> --
>>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>>> >> >>
>>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>>> >> >
>>>>>>>>> >> >
>>>>>>>>> >> >
>>>>>>>>> >> >
>>>>>>>>> >> > --
>>>>>>>>> >> > Pradeep Fernando.
>>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> --
>>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>>> LinkedIn.
>>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > --
>>>>>>>>> > Best Regards,
>>>>>>>>> > Nirmal
>>>>>>>>> >
>>>>>>>>> > Nirmal Fernando.
>>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>>> >
>>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Nirmal
>>>>>>>>
>>>>>>>> Nirmal Fernando.
>>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>>
>>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sameera Jayasoma
>>>>
>>>> blog: http://sameera.adahas.org
>>>> twitter: https://twitter.com/sameerajayasoma
>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>>
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Sameera,
Actually I sent that info earlier, let me paste again.
osgi> diag 79
reference:file:../plugins/jclouds-core_1.7.1.jar [79]
Direct constraints which are unresolved:
Missing imported package javax.lang.model.type_0.0.0.
osgi>
osgi> p javax.lang.model.type
No exported packages
osgi>
In Cloud controller product:
osgi> p javax.lang.model.type
javax.lang.model.type; version="0.0.0"<org.eclipse.
osgi_3.8.1.v20120830-144521 [0]>
jclouds-core_1.7.1 [65] imports
org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
org.eclipse.osgi_3.8.1* is activated in both the servers, but this package
is not exported in the single jvm case.
On Wed, Mar 19, 2014 at 4:25 PM, Sameera Jayasoma <
sameera.madushan@gmail.com> wrote:
> Hi Nirmal,
>
> Can you check who is exporting the javax.lang.model.type package in a
> working package? Check whether this package is exported from the JDK via
> the equinox system bundle?
>
> Thanks,
> Sameera.
>
>
> On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi Sameera,
>>
>> Thanks for the reply.
>>
>> Here's the full stack-trace:
>>
>>
>> java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:247)
>> at
>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>> at
>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>> at
>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>> at
>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>> at
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>> at
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>> Caused by: java.lang.ClassNotFoundException:
>> org.jclouds.rest.ResourceNotFoundException
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>
>>
>>
>> osgi> ss jcloud
>> "Framework is launched."
>>
>>
>> id State Bundle
>> 77 INSTALLED jclouds-bouncycastle_1.7.1
>> 78 INSTALLED jclouds-compute_1.7.1
>> 79 INSTALLED jclouds-core_1.7.1
>> 80 INSTALLED jclouds-enterprise_1.7.1
>> 81 INSTALLED jclouds-joda_1.7.1
>> 82 INSTALLED jclouds-netty_1.7.1
>> 83 INSTALLED jclouds-scriptbuilder_1.7.1
>> 84 INSTALLED jclouds-slf4j_1.7.1
>> 85 INSTALLED jclouds-sshj_1.7.1
>> osgi>
>> osgi>
>> osgi> diag 79
>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>> Direct constraints which are unresolved:
>> Missing imported package javax.lang.model.type_0.0.0.
>> osgi>
>>
>>
>> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
>> sameera.madushan@gmail.com> wrote:
>>
>>> Hi Nirmal,
>>>
>>> Can you post the full stacktrace?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> osgi> diag 79
>>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>>> Direct constraints which are unresolved:
>>>> Missing imported package javax.lang.model.type_0.0.0.
>>>> osgi>
>>>>
>>>> osgi> p javax.lang.model.type
>>>> No exported packages
>>>> osgi>
>>>>
>>>> In Cloud controller product:
>>>>
>>>> osgi> p javax.lang.model.type
>>>> javax.lang.model.type;
>>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>>> jclouds-core_1.7.1 [65] imports
>>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124]
>>>> imports
>>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>>
>>>>
>>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>>> package is not exported in the single jvm case.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>>> dependency issue. I'm looking into it now.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>>
>>>>>> Sounds good, though at some point in the future should we remove the
>>>>>> dependency on using jndi? It seems a bit ironic that we are using a cross
>>>>>> platform protocol AMPQ, but are connecting to it with a Java specific
>>>>>> mechanism.
>>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time
>>>>>>> being without much research, I'm going to use ActiveMQ.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>>>>>
>>>>>>>> Awesome - thanks Nirmal!
>>>>>>>>
>>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>>> > I'll continue on this.
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> >>
>>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>>> unless it
>>>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>>>> commit
>>>>>>>> >> later on.
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>>> pradeepfn@gmail.com>
>>>>>>>> >> wrote:
>>>>>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>>>>>> jclouds
>>>>>>>> >> > CNF.
>>>>>>>> >> > After that, build the product named stratos. It contains all
>>>>>>>> the
>>>>>>>> >> > components
>>>>>>>> >> > except MB.
>>>>>>>> >> >
>>>>>>>> >> > we can start a test round with an external MB
>>>>>>>> >> >
>>>>>>>> >> > hope this helps.. :)
>>>>>>>> >> >
>>>>>>>> >> > thanks.
>>>>>>>> >> >
>>>>>>>> >> >
>>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>>> >> >>
>>>>>>>> >> >> Hi Pradeep,
>>>>>>>> >> >>
>>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>>> provide an
>>>>>>>> >> >> update
>>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>>> >> >>
>>>>>>>> >> >> Thanks,
>>>>>>>> >> >> Sameera.
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>>> >> >> <pr...@gmail.com>
>>>>>>>> >> >> wrote:
>>>>>>>> >> >>>
>>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>>>>>> attend some
>>>>>>>> >> >>> other work.
>>>>>>>> >> >>>
>>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>>> >> >>>
>>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>>> >> >>>
>>>>>>>> >> >>> thanks.
>>>>>>>> >> >>> --Pradeep
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>>> >> >>> wrote:
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> Hi Guys,
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> I managed to workaround the classloading issue, by renaming
>>>>>>>> stub
>>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud
>>>>>>>> class
>>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -
>>>>>>>> Error
>>>>>>>> >> >>>> while
>>>>>>>> >> >>>> adding services from bundle :
>>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>> Method)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>>> >> >>>> at
>>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>>> >> >>>> at
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>>> >> >>>> ... 49 more
>>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>>>>>> Deploying
>>>>>>>> >> >>>> Axis2
>>>>>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>>> Repository :
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>>> >> >>>> Thrift port : 7611
>>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>>> service
>>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>>>> service
>>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>>> service
>>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor
>>>>>>>> service
>>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>>> >> >>>> configuration
>>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>>> >> >>>> HTTPS port
>>>>>>>> >> >>>> : 9443
>>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>>>>>>> >> >>>> port
>>>>>>>> >> >>>> : 9763
>>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>> shared
>>>>>>>> >> >>>> selector for
>>>>>>>> >> >>>> servlet write/read
>>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>>> shared
>>>>>>>> >> >>>> selector for
>>>>>>>> >> >>>> servlet write/read
>>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -
>>>>>>>> Task
>>>>>>>> >> >>>> service
>>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>>>> >> >>>> Setting
>>>>>>>> >> >>>> config properties into System properties
>>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>> >> >>>> Topology receiver thread started
>>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>>> >> >>>> ADC
>>>>>>>> >> >>>> management server component is activated
>>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service
>>>>>>>> URL :
>>>>>>>> >> >>>>
>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}
>>>>>>>> - Task
>>>>>>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>> >> >>>> Server
>>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>>> >> >>>>
>>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>>> >> >>>> WSO2
>>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -
>>>>>>>> Mgt Console
>>>>>>>> >> >>>> URL :
>>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>>> Additional
>>>>>>>> >> >>>> SASL
>>>>>>>> >> >>>> providers successfully registered.
>>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>>>>>>> Callback
>>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>>> CRAM-MD5-HASHED
>>>>>>>> >> >>>> AMQPLAIN
>>>>>>>> >> >>>> PLAIN
>>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>>> classloader
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>>> shahhaqu@cisco.com>
>>>>>>>> >> >>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to this
>>>>>>>> domain,
>>>>>>>> >> >>>>> but
>>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals of
>>>>>>>> this work.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>>> advantage of
>>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>>> processes or
>>>>>>>> >> >>>>> what? I
>>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>>> unclear how
>>>>>>>> >> >>>>> they
>>>>>>>> >> >>>>> relate to this.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>>> feature I can
>>>>>>>> >> >>>>> read?
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>>> something
>>>>>>>> >> >>>>> like
>>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the exact
>>>>>>>> bits in it.
>>>>>>>> >> >>>>> Looks
>>>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>>>> images now?
>>>>>>>> >> >>>>> Or is
>>>>>>>> >> >>>>> that gone with just more memory and more disk being
>>>>>>>> normal??
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>>> chsnow123@gmail.com>
>>>>>>>> >> >>>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There are
>>>>>>>> plenty of
>>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>>> boxes [1],
>>>>>>>> >> >>>>> although
>>>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode
>>>>>>>> also
>>>>>>>> >> >>>>> provide some
>>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>>> needs, you can
>>>>>>>> >> >>>>> copy
>>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>>> build your
>>>>>>>> >> >>>>> own box
>>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Many thanks,
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Chris
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> ---
>>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>>> sanjiva@wso2.com>
>>>>>>>> >> >>>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having
>>>>>>>> vagrant scripts
>>>>>>>> >> >>>>> as
>>>>>>>> >> >>>>> well!
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does
>>>>>>>> it build
>>>>>>>> >> >>>>> a
>>>>>>>> >> >>>>> VM image or does it set up the environment to run the
>>>>>>>> image?
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>>> chsnow123@gmail.com>
>>>>>>>> >> >>>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>>> setting up
>>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>>> configuring
>>>>>>>> >> >>>>> guest proxy
>>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos.
>>>>>>>> My project
>>>>>>>> >> >>>>> is
>>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>>> making good
>>>>>>>> >> >>>>> progress.
>>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>>>>>> checkout,
>>>>>>>> >> >>>>> build and
>>>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>>>> working on
>>>>>>>> >> >>>>> the
>>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>>> environment,
>>>>>>>> >> >>>>> but
>>>>>>>> >> >>>>> for me the first goal is automation, the next goal will be
>>>>>>>> >> >>>>> efficiency.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Many thanks,
>>>>>>>> >> >>>>> Chris
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> ---
>>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>>> sanjiva@wso2.com>
>>>>>>>> >> >>>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>>> trivial
>>>>>>>> >> >>>>> server
>>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>>>> stuff having
>>>>>>>> >> >>>>> to be
>>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> - a VM image that has everything in it and runs in under
>>>>>>>> 4GB with
>>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses
>>>>>>>> one Carbon
>>>>>>>> >> >>>>> server to
>>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP
>>>>>>>> broker. (Carbon
>>>>>>>> >> >>>>> stuff
>>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those
>>>>>>>> products .. so
>>>>>>>> >> >>>>> the
>>>>>>>> >> >>>>> decision should not be based on ability to run in one JVM
>>>>>>>> but rather
>>>>>>>> >> >>>>> just
>>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be in
>>>>>>>> 4.0.0 - I
>>>>>>>> >> >>>>> think
>>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a
>>>>>>>> direct
>>>>>>>> >> >>>>> plugin
>>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>>>> there's one
>>>>>>>> >> >>>>> JVM that
>>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes
>>>>>>>> one JVM plus
>>>>>>>> >> >>>>> a URL
>>>>>>>> >> >>>>> to a Docker image registry from which the images are
>>>>>>>> booted up and
>>>>>>>> >> >>>>> run
>>>>>>>> >> >>>>> (obviously a local registry will do better). We don't have
>>>>>>>> this
>>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not
>>>>>>>> that hard
>>>>>>>> >> >>>>> to make
>>>>>>>> >> >>>>> it work).
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> For production deployments obviously this one server stuff
>>>>>>>> is
>>>>>>>> >> >>>>> nonsense
>>>>>>>> >> >>>>> .. so we need to have full decoupled distributed
>>>>>>>> execution. For that
>>>>>>>> >> >>>>> we
>>>>>>>> >> >>>>> should ship puppet scripts to get them up and running plus
>>>>>>>> maybe
>>>>>>>> >> >>>>> Boto
>>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>>> command. Again
>>>>>>>> >> >>>>> its
>>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever other
>>>>>>>> >> >>>>> pluggable
>>>>>>>> >> >>>>> components people want to use (and we need to make sure
>>>>>>>> all the
>>>>>>>> >> >>>>> parts are
>>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>>>>>>>> etc.)).
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Makes sense?
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Sanjiva.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>>> >> >>>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Hi Chris,
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Thanks
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> --Pradeep
>>>>>>>> >> >>>>> sent from my phone
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles
>>>>>>>> work to have
>>>>>>>> >> >>>>> a
>>>>>>>> >> >>>>> view on that :(
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will be
>>>>>>>> saved if
>>>>>>>> >> >>>>> we
>>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>>> >> >>>>> > btw,
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>>>>>> stratos.
>>>>>>>> >> >>>>> > However,
>>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>>>>>>>> profile
>>>>>>>> >> >>>>> > (the
>>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > WDYT?
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > thanks
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>>> chsnow123@gmail.com>
>>>>>>>> >> >>>>> > wrote:
>>>>>>>> >> >>>>> >>
>>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward
>>>>>>>> to your
>>>>>>>> >> >>>>> >> findings!
>>>>>>>> >> >>>>> >>
>>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>>> >> >>>>> >> wrote:
>>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>>> >> >>>>> >> >
>>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track the
>>>>>>>> >> >>>>> >> > progress..
>>>>>>>> >> >>>>> >> >
>>>>>>>> >> >>>>> >> > thanks,
>>>>>>>> >> >>>>> >> >
>>>>>>>> >> >>>>> >> >
>>>>>>>> >> >>>>> >> > --
>>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>> >> >>>>> >>
>>>>>>>> >> >>>>> >>
>>>>>>>> >> >>>>> >>
>>>>>>>> >> >>>>> >> --
>>>>>>>> >> >>>>> >> Check out my professional profile and connect with me on
>>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> >
>>>>>>>> >> >>>>> > --
>>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> --
>>>>>>>> >> >>>>> Check out my professional profile and connect with me on
>>>>>>>> LinkedIn.
>>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> --
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>> 11 214 5345)
>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>>> 650 265
>>>>>>>> >> >>>>> 8311
>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> --
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>> 11 214 5345)
>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>>> 650 265
>>>>>>>> >> >>>>> 8311
>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> --
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94
>>>>>>>> 11 214 5345)
>>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>>> 650 265
>>>>>>>> >> >>>>> 8311
>>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>>
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> >> >>>>
>>>>>>>> >> >>>> --
>>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>> --
>>>>>>>> >> >>> Pradeep Fernando.
>>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >> --
>>>>>>>> >> >> Sameera Jayasoma
>>>>>>>> >> >>
>>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>>> >> >
>>>>>>>> >> >
>>>>>>>> >> >
>>>>>>>> >> >
>>>>>>>> >> > --
>>>>>>>> >> > Pradeep Fernando.
>>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> --
>>>>>>>> >> Check out my professional profile and connect with me on
>>>>>>>> LinkedIn.
>>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > --
>>>>>>>> > Best Regards,
>>>>>>>> > Nirmal
>>>>>>>> >
>>>>>>>> > Nirmal Fernando.
>>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>>> >
>>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>>>> http://lnkd.in/cw5k69
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma
>>>
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Sameera Jayasoma
>
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Sameera Jayasoma <sa...@gmail.com>.
Hi Nirmal,
Can you check who is exporting the javax.lang.model.type package in a
working package? Check whether this package is exported from the JDK via
the equinox system bundle?
Thanks,
Sameera.
On Wed, Mar 19, 2014 at 4:13 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi Sameera,
>
> Thanks for the reply.
>
> Here's the full stack-trace:
>
>
> java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> at
> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException:
> org.jclouds.rest.ResourceNotFoundException
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>
>
>
> osgi> ss jcloud
> "Framework is launched."
>
>
> id State Bundle
> 77 INSTALLED jclouds-bouncycastle_1.7.1
> 78 INSTALLED jclouds-compute_1.7.1
> 79 INSTALLED jclouds-core_1.7.1
> 80 INSTALLED jclouds-enterprise_1.7.1
> 81 INSTALLED jclouds-joda_1.7.1
> 82 INSTALLED jclouds-netty_1.7.1
> 83 INSTALLED jclouds-scriptbuilder_1.7.1
> 84 INSTALLED jclouds-slf4j_1.7.1
> 85 INSTALLED jclouds-sshj_1.7.1
> osgi>
> osgi>
> osgi> diag 79
> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
> Direct constraints which are unresolved:
> Missing imported package javax.lang.model.type_0.0.0.
> osgi>
>
>
> On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
> sameera.madushan@gmail.com> wrote:
>
>> Hi Nirmal,
>>
>> Can you post the full stacktrace?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> osgi> diag 79
>>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>>> Direct constraints which are unresolved:
>>> Missing imported package javax.lang.model.type_0.0.0.
>>> osgi>
>>>
>>> osgi> p javax.lang.model.type
>>> No exported packages
>>> osgi>
>>>
>>> In Cloud controller product:
>>>
>>> osgi> p javax.lang.model.type
>>> javax.lang.model.type;
>>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>>> jclouds-core_1.7.1 [65] imports
>>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
>>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>>
>>>
>>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>>> package is not exported in the single jvm case.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> The jclouds CNF is a class loading issue, not a simple missing
>>>> dependency issue. I'm looking into it now.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com>wrote:
>>>>
>>>>> Sounds good, though at some point in the future should we remove the
>>>>> dependency on using jndi? It seems a bit ironic that we are using a cross
>>>>> platform protocol AMPQ, but are connecting to it with a Java specific
>>>>> mechanism.
>>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time
>>>>>> being without much research, I'm going to use ActiveMQ.
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>>>>
>>>>>>> Awesome - thanks Nirmal!
>>>>>>>
>>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>> > I'll continue on this.
>>>>>>> >
>>>>>>> >
>>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>
>>>>>>> >> Can this patch be reviewed and committed? I'm worried that
>>>>>>> unless it
>>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>>> commit
>>>>>>> >> later on.
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>>> pradeepfn@gmail.com>
>>>>>>> >> wrote:
>>>>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>>>>> jclouds
>>>>>>> >> > CNF.
>>>>>>> >> > After that, build the product named stratos. It contains all the
>>>>>>> >> > components
>>>>>>> >> > except MB.
>>>>>>> >> >
>>>>>>> >> > we can start a test round with an external MB
>>>>>>> >> >
>>>>>>> >> > hope this helps.. :)
>>>>>>> >> >
>>>>>>> >> > thanks.
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>>> >> >>
>>>>>>> >> >> Hi Pradeep,
>>>>>>> >> >>
>>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>>> provide an
>>>>>>> >> >> update
>>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>>> >> >>
>>>>>>> >> >> Thanks,
>>>>>>> >> >> Sameera.
>>>>>>> >> >>
>>>>>>> >> >>
>>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>>> >> >> <pr...@gmail.com>
>>>>>>> >> >> wrote:
>>>>>>> >> >>>
>>>>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>>>>> attend some
>>>>>>> >> >>> other work.
>>>>>>> >> >>>
>>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>>> >> >>>
>>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>>> >> >>>
>>>>>>> >> >>> thanks.
>>>>>>> >> >>> --Pradeep
>>>>>>> >> >>>
>>>>>>> >> >>>
>>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>>> >> >>> <pr...@gmail.com>
>>>>>>> >> >>> wrote:
>>>>>>> >> >>>>
>>>>>>> >> >>>> Hi Guys,
>>>>>>> >> >>>>
>>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>>> >> >>>>
>>>>>>> >> >>>> I managed to workaround the classloading issue, by renaming
>>>>>>> stub
>>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>>> >> >>>>
>>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -
>>>>>>> Error
>>>>>>> >> >>>> while
>>>>>>> >> >>>> adding services from bundle :
>>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>>> >> >>>>
>>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>> Method)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>>> >> >>>> at
>>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>>> >> >>>> at
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>>> >> >>>> ... 49 more
>>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>>>>> Deploying
>>>>>>> >> >>>> Axis2
>>>>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>>>> Repository :
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>>> >> >>>> Thrift port : 7611
>>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>>> service
>>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>>> service
>>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>>> service
>>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor service
>>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>>> >> >>>> configuration
>>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>>>> >> >>>> HTTPS port
>>>>>>> >> >>>> : 9443
>>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener}
>>>>>>> - HTTP
>>>>>>> >> >>>> port
>>>>>>> >> >>>> : 9763
>>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>> shared
>>>>>>> >> >>>> selector for
>>>>>>> >> >>>> servlet write/read
>>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a
>>>>>>> shared
>>>>>>> >> >>>> selector for
>>>>>>> >> >>>> servlet write/read
>>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -
>>>>>>> Task
>>>>>>> >> >>>> service
>>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader}
>>>>>>> -
>>>>>>> >> >>>> Setting
>>>>>>> >> >>>> config properties into System properties
>>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>>> >> >>>>
>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>> >> >>>> Topology receiver thread started
>>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>>> >> >>>>
>>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>>> >> >>>> ADC
>>>>>>> >> >>>> management server component is activated
>>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service
>>>>>>> URL :
>>>>>>> >> >>>>
>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}
>>>>>>> - Task
>>>>>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>> >> >>>> Server
>>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>>> >> >>>>
>>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>>> >> >>>> WSO2
>>>>>>> >> >>>> Carbon started in 55 sec
>>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -
>>>>>>> Mgt Console
>>>>>>> >> >>>> URL :
>>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>>> Additional
>>>>>>> >> >>>> SASL
>>>>>>> >> >>>> providers successfully registered.
>>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>>>>>> Callback
>>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>>> CRAM-MD5-HASHED
>>>>>>> >> >>>> AMQPLAIN
>>>>>>> >> >>>> PLAIN
>>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>>> classloader
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>>> shahhaqu@cisco.com>
>>>>>>> >> >>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Hi Pradeep,
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> I *think* I am interested in this topic and am new to this
>>>>>>> domain,
>>>>>>> >> >>>>> but
>>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals of
>>>>>>> this work.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>>> advantage of
>>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>>> processes or
>>>>>>> >> >>>>> what? I
>>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>>> unclear how
>>>>>>> >> >>>>> they
>>>>>>> >> >>>>> relate to this.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>>> feature I can
>>>>>>> >> >>>>> read?
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Thanks, Shaheed
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>>> something
>>>>>>> >> >>>>> like
>>>>>>> >> >>>>> rPath to build a minimal Linux image with just the exact
>>>>>>> bits in it.
>>>>>>> >> >>>>> Looks
>>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>>> images now?
>>>>>>> >> >>>>> Or is
>>>>>>> >> >>>>> that gone with just more memory and more disk being normal??
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>>> chsnow123@gmail.com>
>>>>>>> >> >>>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There are
>>>>>>> plenty of
>>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant
>>>>>>> boxes [1],
>>>>>>> >> >>>>> although
>>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode also
>>>>>>> >> >>>>> provide some
>>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your
>>>>>>> needs, you can
>>>>>>> >> >>>>> copy
>>>>>>> >> >>>>> the packer definitions from opscode and modify them to
>>>>>>> build your
>>>>>>> >> >>>>> own box
>>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Many thanks,
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Chris
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> ---
>>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>>> >> >>>>> [4] http://packer.io
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>>> sanjiva@wso2.com>
>>>>>>> >> >>>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>>>>>>> scripts
>>>>>>> >> >>>>> as
>>>>>>> >> >>>>> well!
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does
>>>>>>> it build
>>>>>>> >> >>>>> a
>>>>>>> >> >>>>> VM image or does it set up the environment to run the image?
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Sanjiva.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>>> chsnow123@gmail.com>
>>>>>>> >> >>>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Hi Sanjiva,
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>>> setting up
>>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>>> configuring
>>>>>>> >> >>>>> guest proxy
>>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos.
>>>>>>> My project
>>>>>>> >> >>>>> is
>>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm
>>>>>>> making good
>>>>>>> >> >>>>> progress.
>>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>>>>> checkout,
>>>>>>> >> >>>>> build and
>>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>>> working on
>>>>>>> >> >>>>> the
>>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>>> environment,
>>>>>>> >> >>>>> but
>>>>>>> >> >>>>> for me the first goal is automation, the next goal will be
>>>>>>> >> >>>>> efficiency.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Many thanks,
>>>>>>> >> >>>>> Chris
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> ---
>>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>>> sanjiva@wso2.com>
>>>>>>> >> >>>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>>> trivial
>>>>>>> >> >>>>> server
>>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>>> stuff having
>>>>>>> >> >>>>> to be
>>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> - a VM image that has everything in it and runs in under
>>>>>>> 4GB with
>>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>>>>>>> Carbon
>>>>>>> >> >>>>> server to
>>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>>>>>>> (Carbon
>>>>>>> >> >>>>> stuff
>>>>>>> >> >>>>> HAS to run in one server - else its a bug in those products
>>>>>>> .. so
>>>>>>> >> >>>>> the
>>>>>>> >> >>>>> decision should not be based on ability to run in one JVM
>>>>>>> but rather
>>>>>>> >> >>>>> just
>>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be in
>>>>>>> 4.0.0 - I
>>>>>>> >> >>>>> think
>>>>>>> >> >>>>> we're nearly there for it.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a
>>>>>>> direct
>>>>>>> >> >>>>> plugin
>>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>>> there's one
>>>>>>> >> >>>>> JVM that
>>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one
>>>>>>> JVM plus
>>>>>>> >> >>>>> a URL
>>>>>>> >> >>>>> to a Docker image registry from which the images are booted
>>>>>>> up and
>>>>>>> >> >>>>> run
>>>>>>> >> >>>>> (obviously a local registry will do better). We don't have
>>>>>>> this
>>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not
>>>>>>> that hard
>>>>>>> >> >>>>> to make
>>>>>>> >> >>>>> it work).
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> For production deployments obviously this one server stuff
>>>>>>> is
>>>>>>> >> >>>>> nonsense
>>>>>>> >> >>>>> .. so we need to have full decoupled distributed execution.
>>>>>>> For that
>>>>>>> >> >>>>> we
>>>>>>> >> >>>>> should ship puppet scripts to get them up and running plus
>>>>>>> maybe
>>>>>>> >> >>>>> Boto
>>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>>> command. Again
>>>>>>> >> >>>>> its
>>>>>>> >> >>>>> totally fine to use whatever broker here and whatever other
>>>>>>> >> >>>>> pluggable
>>>>>>> >> >>>>> components people want to use (and we need to make sure all
>>>>>>> the
>>>>>>> >> >>>>> parts are
>>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>>>>>>> etc.)).
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Makes sense?
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Sanjiva.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>>> >> >>>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Hi Chris,
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Thanks
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> --Pradeep
>>>>>>> >> >>>>> sent from my phone
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>>>>>>> wrote:
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles
>>>>>>> work to have
>>>>>>> >> >>>>> a
>>>>>>> >> >>>>> view on that :(
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> One thing I'm wondering though is how much memory will be
>>>>>>> saved if
>>>>>>> >> >>>>> we
>>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>>> >> >>>>> > btw,
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>>>>> stratos.
>>>>>>> >> >>>>> > However,
>>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>>>>>>> profile
>>>>>>> >> >>>>> > (the
>>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > WDYT?
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > Are we all on same page..
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > thanks
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>>> chsnow123@gmail.com>
>>>>>>> >> >>>>> > wrote:
>>>>>>> >> >>>>> >>
>>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward
>>>>>>> to your
>>>>>>> >> >>>>> >> findings!
>>>>>>> >> >>>>> >>
>>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>>> >> >>>>> >> wrote:
>>>>>>> >> >>>>> >> > Hi Guys,
>>>>>>> >> >>>>> >> >
>>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track the
>>>>>>> >> >>>>> >> > progress..
>>>>>>> >> >>>>> >> >
>>>>>>> >> >>>>> >> > thanks,
>>>>>>> >> >>>>> >> >
>>>>>>> >> >>>>> >> >
>>>>>>> >> >>>>> >> > --
>>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>> >> >>>>> >>
>>>>>>> >> >>>>> >>
>>>>>>> >> >>>>> >>
>>>>>>> >> >>>>> >> --
>>>>>>> >> >>>>> >> Check out my professional profile and connect with me on
>>>>>>> >> >>>>> >> LinkedIn.
>>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> >
>>>>>>> >> >>>>> > --
>>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> --
>>>>>>> >> >>>>> Check out my professional profile and connect with me on
>>>>>>> LinkedIn.
>>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> --
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>>>> 214 5345)
>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>> 650 265
>>>>>>> >> >>>>> 8311
>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> --
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>>>> 214 5345)
>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>> 650 265
>>>>>>> >> >>>>> 8311
>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> --
>>>>>>> >> >>>>>
>>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>>>> 214 5345)
>>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>>> 650 265
>>>>>>> >> >>>>> 8311
>>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>>
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> >> >>>>
>>>>>>> >> >>>> --
>>>>>>> >> >>>> Pradeep Fernando.
>>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>>> >> >>>
>>>>>>> >> >>>
>>>>>>> >> >>>
>>>>>>> >> >>>
>>>>>>> >> >>> --
>>>>>>> >> >>> Pradeep Fernando.
>>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>>> >> >>
>>>>>>> >> >>
>>>>>>> >> >>
>>>>>>> >> >>
>>>>>>> >> >> --
>>>>>>> >> >> Sameera Jayasoma
>>>>>>> >> >>
>>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> > --
>>>>>>> >> > Pradeep Fernando.
>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> --
>>>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > Best Regards,
>>>>>>> > Nirmal
>>>>>>> >
>>>>>>> > Nirmal Fernando.
>>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>>> >
>>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>>> http://lnkd.in/cw5k69
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>>
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Sameera Jayasoma
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Sameera,
Thanks for the reply.
Here's the full stack-trace:
java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
at
org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
at
org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException:
org.jclouds.rest.ResourceNotFoundException
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
osgi> ss jcloud
"Framework is launched."
id State Bundle
77 INSTALLED jclouds-bouncycastle_1.7.1
78 INSTALLED jclouds-compute_1.7.1
79 INSTALLED jclouds-core_1.7.1
80 INSTALLED jclouds-enterprise_1.7.1
81 INSTALLED jclouds-joda_1.7.1
82 INSTALLED jclouds-netty_1.7.1
83 INSTALLED jclouds-scriptbuilder_1.7.1
84 INSTALLED jclouds-slf4j_1.7.1
85 INSTALLED jclouds-sshj_1.7.1
osgi>
osgi>
osgi> diag 79
reference:file:../plugins/jclouds-core_1.7.1.jar [79]
Direct constraints which are unresolved:
Missing imported package javax.lang.model.type_0.0.0.
osgi>
On Wed, Mar 19, 2014 at 4:08 PM, Sameera Jayasoma <
sameera.madushan@gmail.com> wrote:
> Hi Nirmal,
>
> Can you post the full stacktrace?
>
> Thanks,
> Sameera.
>
>
> On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> osgi> diag 79
>> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
>> Direct constraints which are unresolved:
>> Missing imported package javax.lang.model.type_0.0.0.
>> osgi>
>>
>> osgi> p javax.lang.model.type
>> No exported packages
>> osgi>
>>
>> In Cloud controller product:
>>
>> osgi> p javax.lang.model.type
>> javax.lang.model.type;
>> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
>> jclouds-core_1.7.1 [65] imports
>> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
>> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
>> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
>> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>>
>>
>> org.eclipse.osgi_3.8.1* is activated in both the servers, but this
>> package is not exported in the single jvm case.
>>
>>
>> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> The jclouds CNF is a class loading issue, not a simple missing
>>> dependency issue. I'm looking into it now.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>>
>>>> Sounds good, though at some point in the future should we remove the
>>>> dependency on using jndi? It seems a bit ironic that we are using a cross
>>>> platform protocol AMPQ, but are connecting to it with a Java specific
>>>> mechanism.
>>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com>
>>>> wrote:
>>>>
>>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time
>>>>> being without much research, I'm going to use ActiveMQ.
>>>>>
>>>>>
>>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>>>
>>>>>> Awesome - thanks Nirmal!
>>>>>>
>>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>> > I'll continue on this.
>>>>>> >
>>>>>> >
>>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> Can this patch be reviewed and committed? I'm worried that unless
>>>>>> it
>>>>>> >> gets applied soon it will become out of date and difficult to
>>>>>> commit
>>>>>> >> later on.
>>>>>> >>
>>>>>> >>
>>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>>> pradeepfn@gmail.com>
>>>>>> >> wrote:
>>>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>>>> jclouds
>>>>>> >> > CNF.
>>>>>> >> > After that, build the product named stratos. It contains all the
>>>>>> >> > components
>>>>>> >> > except MB.
>>>>>> >> >
>>>>>> >> > we can start a test round with an external MB
>>>>>> >> >
>>>>>> >> > hope this helps.. :)
>>>>>> >> >
>>>>>> >> > thanks.
>>>>>> >> >
>>>>>> >> >
>>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>>> >> > <sa...@gmail.com> wrote:
>>>>>> >> >>
>>>>>> >> >> Hi Pradeep,
>>>>>> >> >>
>>>>>> >> >> This patch contains so many code changes. Can you please
>>>>>> provide an
>>>>>> >> >> update
>>>>>> >> >> on where we are on this? What are the remaining items?
>>>>>> >> >>
>>>>>> >> >> Thanks,
>>>>>> >> >> Sameera.
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>>> >> >> <pr...@gmail.com>
>>>>>> >> >> wrote:
>>>>>> >> >>>
>>>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>>>> attend some
>>>>>> >> >>> other work.
>>>>>> >> >>>
>>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>>> >> >>>
>>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>>> >> >>>
>>>>>> >> >>> thanks.
>>>>>> >> >>> --Pradeep
>>>>>> >> >>>
>>>>>> >> >>>
>>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>>> >> >>> <pr...@gmail.com>
>>>>>> >> >>> wrote:
>>>>>> >> >>>>
>>>>>> >> >>>> Hi Guys,
>>>>>> >> >>>>
>>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>>> >> >>>>
>>>>>> >> >>>> I managed to workaround the classloading issue, by renaming
>>>>>> stub
>>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>>> >> >>>>
>>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -
>>>>>> Error
>>>>>> >> >>>> while
>>>>>> >> >>>> adding services from bundle :
>>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>>> >> >>>>
>>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>> Method)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>> >> >>>> at
>>>>>> java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>>> >> >>>> at
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>>> >> >>>> ... 49 more
>>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>>>> Deploying
>>>>>> >> >>>> Axis2
>>>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
>>>>>> :
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>> >> >>>> Thrift SSL port : 7711
>>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>>> >> >>>> Thrift port : 7611
>>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor
>>>>>> service
>>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>>> service
>>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the input email event service
>>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the output Email event adaptor
>>>>>> service
>>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the output SMS event adaptor service
>>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>>> >> >>>> configuration
>>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener}
>>>>>> -
>>>>>> >> >>>> HTTPS port
>>>>>> >> >>>> : 9443
>>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener}
>>>>>> - HTTP
>>>>>> >> >>>> port
>>>>>> >> >>>> : 9763
>>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>>>> >> >>>> selector for
>>>>>> >> >>>> servlet write/read
>>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>>>> >> >>>> selector for
>>>>>> >> >>>> servlet write/read
>>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -
>>>>>> Task
>>>>>> >> >>>> service
>>>>>> >> >>>> starting in STANDALONE mode...
>>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>>> >> >>>> Setting
>>>>>> >> >>>> config properties into System properties
>>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>>> >> >>>>
>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>> >> >>>> Topology receiver thread started
>>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>>> >> >>>>
>>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>>> >> >>>> ADC
>>>>>> >> >>>> management server component is activated
>>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service
>>>>>> URL :
>>>>>> >> >>>>
>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -
>>>>>> Task
>>>>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>> >> >>>> Server
>>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>>> >> >>>>
>>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>>> >> >>>> WSO2
>>>>>> >> >>>> Carbon started in 55 sec
>>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>>>>>> Console
>>>>>> >> >>>> URL :
>>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>>> Additional
>>>>>> >> >>>> SASL
>>>>>> >> >>>> providers successfully registered.
>>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>>>>> Callback
>>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>>> CRAM-MD5-HASHED
>>>>>> >> >>>> AMQPLAIN
>>>>>> >> >>>> PLAIN
>>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>>> >> >>>> Unable to find resource qpidversion.properties from
>>>>>> classloader
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>>> shahhaqu@cisco.com>
>>>>>> >> >>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Hi Pradeep,
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> I *think* I am interested in this topic and am new to this
>>>>>> domain,
>>>>>> >> >>>>> but
>>>>>> >> >>>>> from the archives, I'm not 100% of the original goals of
>>>>>> this work.
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>>> advantage of
>>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>>> processes or
>>>>>> >> >>>>> what? I
>>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>>> unclear how
>>>>>> >> >>>>> they
>>>>>> >> >>>>> relate to this.
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this
>>>>>> feature I can
>>>>>> >> >>>>> read?
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> Thanks, Shaheed
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>>> something
>>>>>> >> >>>>> like
>>>>>> >> >>>>> rPath to build a minimal Linux image with just the exact
>>>>>> bits in it.
>>>>>> >> >>>>> Looks
>>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>>> images now?
>>>>>> >> >>>>> Or is
>>>>>> >> >>>>> that gone with just more memory and more disk being normal??
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>>> chsnow123@gmail.com>
>>>>>> >> >>>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Hi Sanjiva,
>>>>>> >> >>>>>
>>>>>> >> >>>>> Vagrant works on top of an existing image (box). There are
>>>>>> plenty of
>>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes
>>>>>> [1],
>>>>>> >> >>>>> although
>>>>>> >> >>>>> the disk size is a little small to be useful. Opscode also
>>>>>> >> >>>>> provide some
>>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your needs,
>>>>>> you can
>>>>>> >> >>>>> copy
>>>>>> >> >>>>> the packer definitions from opscode and modify them to build
>>>>>> your
>>>>>> >> >>>>> own box
>>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>> >> >>>>>
>>>>>> >> >>>>> Many thanks,
>>>>>> >> >>>>>
>>>>>> >> >>>>> Chris
>>>>>> >> >>>>>
>>>>>> >> >>>>> ---
>>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>>> >> >>>>> [4] http://packer.io
>>>>>> >> >>>>>
>>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <
>>>>>> sanjiva@wso2.com>
>>>>>> >> >>>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>>>>>> scripts
>>>>>> >> >>>>> as
>>>>>> >> >>>>> well!
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does
>>>>>> it build
>>>>>> >> >>>>> a
>>>>>> >> >>>>> VM image or does it set up the environment to run the image?
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> Sanjiva.
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>>> chsnow123@gmail.com>
>>>>>> >> >>>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Hi Sanjiva,
>>>>>> >> >>>>>
>>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>>> setting up
>>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>>> configuring
>>>>>> >> >>>>> guest proxy
>>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>>> >> >>>>>
>>>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
>>>>>> project
>>>>>> >> >>>>> is
>>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making
>>>>>> good
>>>>>> >> >>>>> progress.
>>>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>>>> checkout,
>>>>>> >> >>>>> build and
>>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>>> working on
>>>>>> >> >>>>> the
>>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>>> >> >>>>>
>>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>>> environment,
>>>>>> >> >>>>> but
>>>>>> >> >>>>> for me the first goal is automation, the next goal will be
>>>>>> >> >>>>> efficiency.
>>>>>> >> >>>>>
>>>>>> >> >>>>> Many thanks,
>>>>>> >> >>>>> Chris
>>>>>> >> >>>>>
>>>>>> >> >>>>> ---
>>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>>> >> >>>>>
>>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <
>>>>>> sanjiva@wso2.com>
>>>>>> >> >>>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> I think right now we need to focus on getting a single
>>>>>> trivial
>>>>>> >> >>>>> server
>>>>>> >> >>>>> mechanism to be able to run Stratos without too much of
>>>>>> stuff having
>>>>>> >> >>>>> to be
>>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> - a VM image that has everything in it and runs in under 4GB
>>>>>> with
>>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>>>>>> Carbon
>>>>>> >> >>>>> server to
>>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>>>>>> (Carbon
>>>>>> >> >>>>> stuff
>>>>>> >> >>>>> HAS to run in one server - else its a bug in those products
>>>>>> .. so
>>>>>> >> >>>>> the
>>>>>> >> >>>>> decision should not be based on ability to run in one JVM
>>>>>> but rather
>>>>>> >> >>>>> just
>>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be in
>>>>>> 4.0.0 - I
>>>>>> >> >>>>> think
>>>>>> >> >>>>> we're nearly there for it.
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a
>>>>>> direct
>>>>>> >> >>>>> plugin
>>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>>> there's one
>>>>>> >> >>>>> JVM that
>>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one
>>>>>> JVM plus
>>>>>> >> >>>>> a URL
>>>>>> >> >>>>> to a Docker image registry from which the images are booted
>>>>>> up and
>>>>>> >> >>>>> run
>>>>>> >> >>>>> (obviously a local registry will do better). We don't have
>>>>>> this
>>>>>> >> >>>>> no-IaaS-IaaS
>>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not
>>>>>> that hard
>>>>>> >> >>>>> to make
>>>>>> >> >>>>> it work).
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> For production deployments obviously this one server stuff is
>>>>>> >> >>>>> nonsense
>>>>>> >> >>>>> .. so we need to have full decoupled distributed execution.
>>>>>> For that
>>>>>> >> >>>>> we
>>>>>> >> >>>>> should ship puppet scripts to get them up and running plus
>>>>>> maybe
>>>>>> >> >>>>> Boto
>>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one
>>>>>> command. Again
>>>>>> >> >>>>> its
>>>>>> >> >>>>> totally fine to use whatever broker here and whatever other
>>>>>> >> >>>>> pluggable
>>>>>> >> >>>>> components people want to use (and we need to make sure all
>>>>>> the
>>>>>> >> >>>>> parts are
>>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>>>>>> etc.)).
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> Makes sense?
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> Sanjiva.
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>>> >> >>>>> <pr...@gmail.com>
>>>>>> >> >>>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Hi Chris,
>>>>>> >> >>>>>
>>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>> >> >>>>>
>>>>>> >> >>>>> Thanks
>>>>>> >> >>>>>
>>>>>> >> >>>>> --Pradeep
>>>>>> >> >>>>> sent from my phone
>>>>>> >> >>>>>
>>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>>>>>> wrote:
>>>>>> >> >>>>>
>>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work
>>>>>> to have
>>>>>> >> >>>>> a
>>>>>> >> >>>>> view on that :(
>>>>>> >> >>>>>
>>>>>> >> >>>>> One thing I'm wondering though is how much memory will be
>>>>>> saved if
>>>>>> >> >>>>> we
>>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>> >> >>>>>
>>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>>> >> >>>>> > btw,
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>>>> stratos.
>>>>>> >> >>>>> > However,
>>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>>>>>> profile
>>>>>> >> >>>>> > (the
>>>>>> >> >>>>> > profile that has all) makes sense.
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > WDYT?
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > Are we all on same page..
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > thanks
>>>>>> >> >>>>> >
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>>> chsnow123@gmail.com>
>>>>>> >> >>>>> > wrote:
>>>>>> >> >>>>> >>
>>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to
>>>>>> your
>>>>>> >> >>>>> >> findings!
>>>>>> >> >>>>> >>
>>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>>> >> >>>>> >> wrote:
>>>>>> >> >>>>> >> > Hi Guys,
>>>>>> >> >>>>> >> >
>>>>>> >> >>>>> >> > I started on the $subject. This thread is to track the
>>>>>> >> >>>>> >> > progress..
>>>>>> >> >>>>> >> >
>>>>>> >> >>>>> >> > thanks,
>>>>>> >> >>>>> >> >
>>>>>> >> >>>>> >> >
>>>>>> >> >>>>> >> > --
>>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>> >> >>>>> >>
>>>>>> >> >>>>> >>
>>>>>> >> >>>>> >>
>>>>>> >> >>>>> >> --
>>>>>> >> >>>>> >> Check out my professional profile and connect with me on
>>>>>> >> >>>>> >> LinkedIn.
>>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>>> >> >>>>> >
>>>>>> >> >>>>> >
>>>>>> >> >>>>> >
>>>>>> >> >>>>> >
>>>>>> >> >>>>> > --
>>>>>> >> >>>>> > Pradeep Fernando.
>>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> --
>>>>>> >> >>>>> Check out my professional profile and connect with me on
>>>>>> LinkedIn.
>>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> --
>>>>>> >> >>>>>
>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>>> 214 5345)
>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>> 650 265
>>>>>> >> >>>>> 8311
>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> --
>>>>>> >> >>>>>
>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>>> 214 5345)
>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>> 650 265
>>>>>> >> >>>>> 8311
>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>> --
>>>>>> >> >>>>>
>>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>>> 214 5345)
>>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
>>>>>> 650 265
>>>>>> >> >>>>> 8311
>>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>>
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> >> >>>>
>>>>>> >> >>>> --
>>>>>> >> >>>> Pradeep Fernando.
>>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>>> >> >>>
>>>>>> >> >>>
>>>>>> >> >>>
>>>>>> >> >>>
>>>>>> >> >>> --
>>>>>> >> >>> Pradeep Fernando.
>>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >> --
>>>>>> >> >> Sameera Jayasoma
>>>>>> >> >>
>>>>>> >> >> blog: http://sameera.adahas.org
>>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>>> >> >
>>>>>> >> >
>>>>>> >> >
>>>>>> >> >
>>>>>> >> > --
>>>>>> >> > Pradeep Fernando.
>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> --
>>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>>> >> http://lnkd.in/cw5k69
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > Best Regards,
>>>>>> > Nirmal
>>>>>> >
>>>>>> > Nirmal Fernando.
>>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>>> >
>>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>> http://lnkd.in/cw5k69
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Sameera Jayasoma
>
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Sameera Jayasoma <sa...@gmail.com>.
Hi Nirmal,
Can you post the full stacktrace?
Thanks,
Sameera.
On Wed, Mar 19, 2014 at 3:47 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> osgi> diag 79
> reference:file:../plugins/jclouds-core_1.7.1.jar [79]
> Direct constraints which are unresolved:
> Missing imported package javax.lang.model.type_0.0.0.
> osgi>
>
> osgi> p javax.lang.model.type
> No exported packages
> osgi>
>
> In Cloud controller product:
>
> osgi> p javax.lang.model.type
> javax.lang.model.type;
> version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
> jclouds-core_1.7.1 [65] imports
> org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
> org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
> org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
> org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
>
>
> org.eclipse.osgi_3.8.1* is activated in both the servers, but this package
> is not exported in the single jvm case.
>
>
> On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> The jclouds CNF is a class loading issue, not a simple missing dependency
>> issue. I'm looking into it now.
>>
>>
>> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>
>>> Sounds good, though at some point in the future should we remove the
>>> dependency on using jndi? It seems a bit ironic that we are using a cross
>>> platform protocol AMPQ, but are connecting to it with a Java specific
>>> mechanism.
>>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com> wrote:
>>>
>>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time
>>>> being without much research, I'm going to use ActiveMQ.
>>>>
>>>>
>>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>>
>>>>> Awesome - thanks Nirmal!
>>>>>
>>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>> > I'll continue on this.
>>>>> >
>>>>> >
>>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Can this patch be reviewed and committed? I'm worried that unless
>>>>> it
>>>>> >> gets applied soon it will become out of date and difficult to commit
>>>>> >> later on.
>>>>> >>
>>>>> >>
>>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com>
>>>>> >> wrote:
>>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>>> jclouds
>>>>> >> > CNF.
>>>>> >> > After that, build the product named stratos. It contains all the
>>>>> >> > components
>>>>> >> > except MB.
>>>>> >> >
>>>>> >> > we can start a test round with an external MB
>>>>> >> >
>>>>> >> > hope this helps.. :)
>>>>> >> >
>>>>> >> > thanks.
>>>>> >> >
>>>>> >> >
>>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>>> >> > <sa...@gmail.com> wrote:
>>>>> >> >>
>>>>> >> >> Hi Pradeep,
>>>>> >> >>
>>>>> >> >> This patch contains so many code changes. Can you please provide
>>>>> an
>>>>> >> >> update
>>>>> >> >> on where we are on this? What are the remaining items?
>>>>> >> >>
>>>>> >> >> Thanks,
>>>>> >> >> Sameera.
>>>>> >> >>
>>>>> >> >>
>>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>>> >> >> <pr...@gmail.com>
>>>>> >> >> wrote:
>>>>> >> >>>
>>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>>> attend some
>>>>> >> >>> other work.
>>>>> >> >>>
>>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>>> >> >>>
>>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>>> >> >>>
>>>>> >> >>> thanks.
>>>>> >> >>> --Pradeep
>>>>> >> >>>
>>>>> >> >>>
>>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>>> >> >>> <pr...@gmail.com>
>>>>> >> >>> wrote:
>>>>> >> >>>>
>>>>> >> >>>> Hi Guys,
>>>>> >> >>>>
>>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>>> >> >>>>
>>>>> >> >>>> I managed to workaround the classloading issue, by renaming
>>>>> stub
>>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>>> >> >>>>
>>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -
>>>>> Error
>>>>> >> >>>> while
>>>>> >> >>>> adding services from bundle :
>>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>>> >> >>>>
>>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>> Method)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>> >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>>> >> >>>> at
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>> >> >>>> ... 49 more
>>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>>> Deploying
>>>>> >> >>>> Axis2
>>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
>>>>> :
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>>> >> >>>>
>>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>>> >> >>>> Permission cache updated for tenant -1234
>>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>> >> >>>> Thrift SSL port : 7711
>>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>>> >> >>>> Thrift port : 7611
>>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor service
>>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor
>>>>> service
>>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the input email event service
>>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the output Email event adaptor service
>>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the output SMS event adaptor service
>>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>>> >> >>>> A SSO Service Provider is registered for : console
>>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>>> >> >>>> configuration
>>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>>> >> >>>> HTTPS port
>>>>> >> >>>> : 9443
>>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -
>>>>> HTTP
>>>>> >> >>>> port
>>>>> >> >>>> : 9763
>>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>>> >> >>>> selector for
>>>>> >> >>>> servlet write/read
>>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>>> >> >>>> selector for
>>>>> >> >>>> servlet write/read
>>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -
>>>>> Task
>>>>> >> >>>> service
>>>>> >> >>>> starting in STANDALONE mode...
>>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>>> >> >>>> Setting
>>>>> >> >>>> config properties into System properties
>>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>>> >> >>>>
>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>> >> >>>> Topology receiver thread started
>>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>>> >> >>>>
>>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>>> >> >>>> ADC
>>>>> >> >>>> management server component is activated
>>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service
>>>>> URL :
>>>>> >> >>>>
>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -
>>>>> Task
>>>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>> >> >>>>
>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>> >> >>>> Server
>>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>>> >> >>>>
>>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>>> >> >>>> WSO2
>>>>> >> >>>> Carbon started in 55 sec
>>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>>>>> Console
>>>>> >> >>>> URL :
>>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>>> Additional
>>>>> >> >>>> SASL
>>>>> >> >>>> providers successfully registered.
>>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>>>> Callback
>>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5
>>>>> CRAM-MD5-HASHED
>>>>> >> >>>> AMQPLAIN
>>>>> >> >>>> PLAIN
>>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>>> >> >>>> Unable to find resource qpidversion.properties from classloader
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>>> shahhaqu@cisco.com>
>>>>> >> >>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Hi Pradeep,
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> I *think* I am interested in this topic and am new to this
>>>>> domain,
>>>>> >> >>>>> but
>>>>> >> >>>>> from the archives, I'm not 100% of the original goals of this
>>>>> work.
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>>> advantage of
>>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>>> processes or
>>>>> >> >>>>> what? I
>>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am
>>>>> unclear how
>>>>> >> >>>>> they
>>>>> >> >>>>> relate to this.
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this feature
>>>>> I can
>>>>> >> >>>>> read?
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> Thanks, Shaheed
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>>> something
>>>>> >> >>>>> like
>>>>> >> >>>>> rPath to build a minimal Linux image with just the exact bits
>>>>> in it.
>>>>> >> >>>>> Looks
>>>>> >> >>>>> like rPath is gone - what's the way people build custom
>>>>> images now?
>>>>> >> >>>>> Or is
>>>>> >> >>>>> that gone with just more memory and more disk being normal??
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>>> chsnow123@gmail.com>
>>>>> >> >>>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Hi Sanjiva,
>>>>> >> >>>>>
>>>>> >> >>>>> Vagrant works on top of an existing image (box). There are
>>>>> plenty of
>>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes
>>>>> [1],
>>>>> >> >>>>> although
>>>>> >> >>>>> the disk size is a little small to be useful. Opscode also
>>>>> >> >>>>> provide some
>>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your needs,
>>>>> you can
>>>>> >> >>>>> copy
>>>>> >> >>>>> the packer definitions from opscode and modify them to build
>>>>> your
>>>>> >> >>>>> own box
>>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>> >> >>>>>
>>>>> >> >>>>> Many thanks,
>>>>> >> >>>>>
>>>>> >> >>>>> Chris
>>>>> >> >>>>>
>>>>> >> >>>>> ---
>>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>> >> >>>>> [4] http://packer.io
>>>>> >> >>>>>
>>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sanjiva@wso2.com
>>>>> >
>>>>> >> >>>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>>>>> scripts
>>>>> >> >>>>> as
>>>>> >> >>>>> well!
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does it
>>>>> build
>>>>> >> >>>>> a
>>>>> >> >>>>> VM image or does it set up the environment to run the image?
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> Sanjiva.
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>>> chsnow123@gmail.com>
>>>>> >> >>>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Hi Sanjiva,
>>>>> >> >>>>>
>>>>> >> >>>>> For VM images, vagrant makes life very easy for users;
>>>>> setting up
>>>>> >> >>>>> disks, setting up network cards, setting up memory,
>>>>> configuring
>>>>> >> >>>>> guest proxy
>>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>>> >> >>>>>
>>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
>>>>> project
>>>>> >> >>>>> is
>>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making
>>>>> good
>>>>> >> >>>>> progress.
>>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>>> checkout,
>>>>> >> >>>>> build and
>>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>>> working on
>>>>> >> >>>>> the
>>>>> >> >>>>> scripts to do the same for Stratos.
>>>>> >> >>>>>
>>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>>> environment,
>>>>> >> >>>>> but
>>>>> >> >>>>> for me the first goal is automation, the next goal will be
>>>>> >> >>>>> efficiency.
>>>>> >> >>>>>
>>>>> >> >>>>> Many thanks,
>>>>> >> >>>>> Chris
>>>>> >> >>>>>
>>>>> >> >>>>> ---
>>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>>> >> >>>>>
>>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sanjiva@wso2.com
>>>>> >
>>>>> >> >>>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> I think right now we need to focus on getting a single trivial
>>>>> >> >>>>> server
>>>>> >> >>>>> mechanism to be able to run Stratos without too much of stuff
>>>>> having
>>>>> >> >>>>> to be
>>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> - a VM image that has everything in it and runs in under 4GB
>>>>> with
>>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>>>>> Carbon
>>>>> >> >>>>> server to
>>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>>>>> (Carbon
>>>>> >> >>>>> stuff
>>>>> >> >>>>> HAS to run in one server - else its a bug in those products
>>>>> .. so
>>>>> >> >>>>> the
>>>>> >> >>>>> decision should not be based on ability to run in one JVM but
>>>>> rather
>>>>> >> >>>>> just
>>>>> >> >>>>> making it dirt simple to use.) This distro needs to be in
>>>>> 4.0.0 - I
>>>>> >> >>>>> think
>>>>> >> >>>>> we're nearly there for it.
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a
>>>>> direct
>>>>> >> >>>>> plugin
>>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>>> there's one
>>>>> >> >>>>> JVM that
>>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one
>>>>> JVM plus
>>>>> >> >>>>> a URL
>>>>> >> >>>>> to a Docker image registry from which the images are booted
>>>>> up and
>>>>> >> >>>>> run
>>>>> >> >>>>> (obviously a local registry will do better). We don't have
>>>>> this
>>>>> >> >>>>> no-IaaS-IaaS
>>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that
>>>>> hard
>>>>> >> >>>>> to make
>>>>> >> >>>>> it work).
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> For production deployments obviously this one server stuff is
>>>>> >> >>>>> nonsense
>>>>> >> >>>>> .. so we need to have full decoupled distributed execution.
>>>>> For that
>>>>> >> >>>>> we
>>>>> >> >>>>> should ship puppet scripts to get them up and running plus
>>>>> maybe
>>>>> >> >>>>> Boto
>>>>> >> >>>>> scripts for someone to get it all up on EC2 with one command.
>>>>> Again
>>>>> >> >>>>> its
>>>>> >> >>>>> totally fine to use whatever broker here and whatever other
>>>>> >> >>>>> pluggable
>>>>> >> >>>>> components people want to use (and we need to make sure all
>>>>> the
>>>>> >> >>>>> parts are
>>>>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>>>>> etc.)).
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> Makes sense?
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> Sanjiva.
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>>> >> >>>>> <pr...@gmail.com>
>>>>> >> >>>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Hi Chris,
>>>>> >> >>>>>
>>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>> >> >>>>>
>>>>> >> >>>>> Thanks
>>>>> >> >>>>>
>>>>> >> >>>>> --Pradeep
>>>>> >> >>>>> sent from my phone
>>>>> >> >>>>>
>>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>>>>> wrote:
>>>>> >> >>>>>
>>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work
>>>>> to have
>>>>> >> >>>>> a
>>>>> >> >>>>> view on that :(
>>>>> >> >>>>>
>>>>> >> >>>>> One thing I'm wondering though is how much memory will be
>>>>> saved if
>>>>> >> >>>>> we
>>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>> >> >>>>>
>>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>>> >> >>>>> > btw,
>>>>> >> >>>>> >
>>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>>> >> >>>>> >
>>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>>> stratos.
>>>>> >> >>>>> > However,
>>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>>>>> profile
>>>>> >> >>>>> > (the
>>>>> >> >>>>> > profile that has all) makes sense.
>>>>> >> >>>>> >
>>>>> >> >>>>> > WDYT?
>>>>> >> >>>>> >
>>>>> >> >>>>> > Are we all on same page..
>>>>> >> >>>>> >
>>>>> >> >>>>> > thanks
>>>>> >> >>>>> >
>>>>> >> >>>>> >
>>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>>> chsnow123@gmail.com>
>>>>> >> >>>>> > wrote:
>>>>> >> >>>>> >>
>>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to
>>>>> your
>>>>> >> >>>>> >> findings!
>>>>> >> >>>>> >>
>>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>> >> >>>>> >> <pr...@gmail.com>
>>>>> >> >>>>> >> wrote:
>>>>> >> >>>>> >> > Hi Guys,
>>>>> >> >>>>> >> >
>>>>> >> >>>>> >> > I started on the $subject. This thread is to track the
>>>>> >> >>>>> >> > progress..
>>>>> >> >>>>> >> >
>>>>> >> >>>>> >> > thanks,
>>>>> >> >>>>> >> >
>>>>> >> >>>>> >> >
>>>>> >> >>>>> >> > --
>>>>> >> >>>>> >> > Pradeep Fernando.
>>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>>> >> >>>>> >>
>>>>> >> >>>>> >>
>>>>> >> >>>>> >>
>>>>> >> >>>>> >> --
>>>>> >> >>>>> >> Check out my professional profile and connect with me on
>>>>> >> >>>>> >> LinkedIn.
>>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>>> >> >>>>> >
>>>>> >> >>>>> >
>>>>> >> >>>>> >
>>>>> >> >>>>> >
>>>>> >> >>>>> > --
>>>>> >> >>>>> > Pradeep Fernando.
>>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> --
>>>>> >> >>>>> Check out my professional profile and connect with me on
>>>>> LinkedIn.
>>>>> >> >>>>> http://lnkd.in/cw5k69
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> --
>>>>> >> >>>>>
>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>> 214 5345)
>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>>>> 265
>>>>> >> >>>>> 8311
>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> --
>>>>> >> >>>>>
>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>> 214 5345)
>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>>>> 265
>>>>> >> >>>>> 8311
>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>> --
>>>>> >> >>>>>
>>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>>> 214 5345)
>>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>>>> 265
>>>>> >> >>>>> 8311
>>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> >> >>>>> Lean . Enterprise . Middleware
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>>
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> >> >>>>
>>>>> >> >>>> --
>>>>> >> >>>> Pradeep Fernando.
>>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>>> >> >>>
>>>>> >> >>>
>>>>> >> >>>
>>>>> >> >>>
>>>>> >> >>> --
>>>>> >> >>> Pradeep Fernando.
>>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>>> >> >>
>>>>> >> >>
>>>>> >> >>
>>>>> >> >>
>>>>> >> >> --
>>>>> >> >> Sameera Jayasoma
>>>>> >> >>
>>>>> >> >> blog: http://sameera.adahas.org
>>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>>> >> >
>>>>> >> >
>>>>> >> >
>>>>> >> >
>>>>> >> > --
>>>>> >> > Pradeep Fernando.
>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>> >> http://lnkd.in/cw5k69
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Best Regards,
>>>>> > Nirmal
>>>>> >
>>>>> > Nirmal Fernando.
>>>>> > PPMC Member & Committer of Apache Stratos,
>>>>> > Senior Software Engineer, WSO2 Inc.
>>>>> >
>>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>> http://lnkd.in/cw5k69
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Sameera Jayasoma
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
osgi> diag 79
reference:file:../plugins/jclouds-core_1.7.1.jar [79]
Direct constraints which are unresolved:
Missing imported package javax.lang.model.type_0.0.0.
osgi>
osgi> p javax.lang.model.type
No exported packages
osgi>
In Cloud controller product:
osgi> p javax.lang.model.type
javax.lang.model.type;
version="0.0.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
jclouds-core_1.7.1 [65] imports
org.eclipse.core.expressions_3.4.401.v20120627-124442 [96] imports
org.eclipse.core.runtime_3.8.0.v20120521-2346 [98] imports
org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [124] imports
org.wso2.carbon.p2.touchpoint_4.2.0 [204] imports
org.eclipse.osgi_3.8.1* is activated in both the servers, but this package
is not exported in the single jvm case.
On Wed, Mar 19, 2014 at 3:11 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> The jclouds CNF is a class loading issue, not a simple missing dependency
> issue. I'm looking into it now.
>
>
> On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>
>> Sounds good, though at some point in the future should we remove the
>> dependency on using jndi? It seems a bit ironic that we are using a cross
>> platform protocol AMPQ, but are connecting to it with a Java specific
>> mechanism.
>> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com> wrote:
>>
>>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time
>>> being without much research, I'm going to use ActiveMQ.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com>wrote:
>>>
>>>> Awesome - thanks Nirmal!
>>>>
>>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>> > I'll continue on this.
>>>> >
>>>> >
>>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Can this patch be reviewed and committed? I'm worried that unless it
>>>> >> gets applied soon it will become out of date and difficult to commit
>>>> >> later on.
>>>> >>
>>>> >>
>>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>>> pradeepfn@gmail.com>
>>>> >> wrote:
>>>> >> > apply the patch and add the jclouds dependency to reolve the
>>>> jclouds
>>>> >> > CNF.
>>>> >> > After that, build the product named stratos. It contains all the
>>>> >> > components
>>>> >> > except MB.
>>>> >> >
>>>> >> > we can start a test round with an external MB
>>>> >> >
>>>> >> > hope this helps.. :)
>>>> >> >
>>>> >> > thanks.
>>>> >> >
>>>> >> >
>>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>>> >> > <sa...@gmail.com> wrote:
>>>> >> >>
>>>> >> >> Hi Pradeep,
>>>> >> >>
>>>> >> >> This patch contains so many code changes. Can you please provide
>>>> an
>>>> >> >> update
>>>> >> >> on where we are on this? What are the remaining items?
>>>> >> >>
>>>> >> >> Thanks,
>>>> >> >> Sameera.
>>>> >> >>
>>>> >> >>
>>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>>> >> >> <pr...@gmail.com>
>>>> >> >> wrote:
>>>> >> >>>
>>>> >> >>> Please someone takeover from here. Unfortunately i have to
>>>> attend some
>>>> >> >>> other work.
>>>> >> >>>
>>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>>> >> >>>
>>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>>> >> >>>
>>>> >> >>> thanks.
>>>> >> >>> --Pradeep
>>>> >> >>>
>>>> >> >>>
>>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>>> >> >>> <pr...@gmail.com>
>>>> >> >>> wrote:
>>>> >> >>>>
>>>> >> >>>> Hi Guys,
>>>> >> >>>>
>>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>>> >> >>>>
>>>> >> >>>> I managed to workaround the classloading issue, by renaming stub
>>>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>>> >> >>>>
>>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>>>> >> >>>> while
>>>> >> >>>> adding services from bundle :
>>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>> >> >>>> java.lang.NoClassDefFoundError:
>>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>>> >> >>>>
>>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>> Method)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>> >> >>>> at
>>>> >> >>>>
>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>> >> >>>> at
>>>> >> >>>>
>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>> >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>> >> >>>> at
>>>> >> >>>>
>>>> >> >>>>
>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>> >> >>>> ... 49 more
>>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>>> Deploying
>>>> >> >>>> Axis2
>>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
>>>> :
>>>> >> >>>>
>>>> >> >>>>
>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>>> >> >>>>
>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>> >> >>>> Permission cache updated for tenant -1234
>>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>> >> >>>> Thrift Server started at 10.100.1.80
>>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>> >> >>>> Thrift SSL port : 7711
>>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>> >> >>>> Thrift port : 7611
>>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor service
>>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor service
>>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the input email event service
>>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the output Email event adaptor service
>>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the output SMS event adaptor service
>>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>> >> >>>> A SSO Service Provider is registered for : console
>>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>>> >> >>>> configuration
>>>> >> >>>> element 'TenantRegistrationPage' not found in
>>>> >> >>>>
>>>> >> >>>>
>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>>> >> >>>> HTTPS port
>>>> >> >>>> : 9443
>>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -
>>>> HTTP
>>>> >> >>>> port
>>>> >> >>>> : 9763
>>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>> >> >>>> selector for
>>>> >> >>>> servlet write/read
>>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>> >> >>>> selector for
>>>> >> >>>> servlet write/read
>>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -
>>>> Task
>>>> >> >>>> service
>>>> >> >>>> starting in STANDALONE mode...
>>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>>> >> >>>> Setting
>>>> >> >>>> config properties into System properties
>>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>>> >> >>>>
>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>> >> >>>> Topology receiver thread started
>>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>>> >> >>>>
>>>> >> >>>>
>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>> >> >>>> - Stratos Manager topology receiver thread started
>>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>>> >> >>>>
>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>> >> >>>> ADC
>>>> >> >>>> management server component is activated
>>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL
>>>> :
>>>> >> >>>>
>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -
>>>> Task
>>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>> >> >>>>
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>> >> >>>> Server
>>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>>> >> >>>>
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>>> >> >>>> WSO2
>>>> >> >>>> Carbon started in 55 sec
>>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>>>> Console
>>>> >> >>>> URL :
>>>> >> >>>> https://10.100.1.80:9443/carbon/
>>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>>> Additional
>>>> >> >>>> SASL
>>>> >> >>>> providers successfully registered.
>>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>>> Callback
>>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
>>>> >> >>>> AMQPLAIN
>>>> >> >>>> PLAIN
>>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>>> >> >>>> Unable to find resource qpidversion.properties from classloader
>>>> >> >>>>
>>>> >> >>>>
>>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>>> shahhaqu@cisco.com>
>>>> >> >>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> Hi Pradeep,
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> I *think* I am interested in this topic and am new to this
>>>> domain,
>>>> >> >>>>> but
>>>> >> >>>>> from the archives, I'm not 100% of the original goals of this
>>>> work.
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>>> advantage of
>>>> >> >>>>> your work: do we still use the same CLIs to start the
>>>> processes or
>>>> >> >>>>> what? I
>>>> >> >>>>> see some mention of profiles and pre-built VMs, but am unclear
>>>> how
>>>> >> >>>>> they
>>>> >> >>>>> relate to this.
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this feature
>>>> I can
>>>> >> >>>>> read?
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> Thanks, Shaheed
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>> >> >>>>>
>>>> >> >>>>> Interesting ... it would be cool to combine these with
>>>> something
>>>> >> >>>>> like
>>>> >> >>>>> rPath to build a minimal Linux image with just the exact bits
>>>> in it.
>>>> >> >>>>> Looks
>>>> >> >>>>> like rPath is gone - what's the way people build custom images
>>>> now?
>>>> >> >>>>> Or is
>>>> >> >>>>> that gone with just more memory and more disk being normal??
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>>> chsnow123@gmail.com>
>>>> >> >>>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> Hi Sanjiva,
>>>> >> >>>>>
>>>> >> >>>>> Vagrant works on top of an existing image (box). There are
>>>> plenty of
>>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes
>>>> [1],
>>>> >> >>>>> although
>>>> >> >>>>> the disk size is a little small to be useful. Opscode also
>>>> >> >>>>> provide some
>>>> >> >>>>> pretty good boxes [2]. If these still don't meet your needs,
>>>> you can
>>>> >> >>>>> copy
>>>> >> >>>>> the packer definitions from opscode and modify them to build
>>>> your
>>>> >> >>>>> own box
>>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>>> >> >>>>>
>>>> >> >>>>> Many thanks,
>>>> >> >>>>>
>>>> >> >>>>> Chris
>>>> >> >>>>>
>>>> >> >>>>> ---
>>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>> >> >>>>> [2] https://github.com/opscode/bento
>>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>> >> >>>>> [4] http://packer.io
>>>> >> >>>>>
>>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
>>>> >> >>>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>>>> scripts
>>>> >> >>>>> as
>>>> >> >>>>> well!
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does it
>>>> build
>>>> >> >>>>> a
>>>> >> >>>>> VM image or does it set up the environment to run the image?
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> Sanjiva.
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>>> chsnow123@gmail.com>
>>>> >> >>>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> Hi Sanjiva,
>>>> >> >>>>>
>>>> >> >>>>> For VM images, vagrant makes life very easy for users; setting
>>>> up
>>>> >> >>>>> disks, setting up network cards, setting up memory, configuring
>>>> >> >>>>> guest proxy
>>>> >> >>>>> settings, running provisioning scripts, etc.
>>>> >> >>>>>
>>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
>>>> project
>>>> >> >>>>> is
>>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making
>>>> good
>>>> >> >>>>> progress.
>>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>>> checkout,
>>>> >> >>>>> build and
>>>> >> >>>>> provision a cloudstack developer environment. I am now
>>>> working on
>>>> >> >>>>> the
>>>> >> >>>>> scripts to do the same for Stratos.
>>>> >> >>>>>
>>>> >> >>>>> Initially, the memory requirements will be high on my
>>>> environment,
>>>> >> >>>>> but
>>>> >> >>>>> for me the first goal is automation, the next goal will be
>>>> >> >>>>> efficiency.
>>>> >> >>>>>
>>>> >> >>>>> Many thanks,
>>>> >> >>>>> Chris
>>>> >> >>>>>
>>>> >> >>>>> ---
>>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>>> >> >>>>>
>>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
>>>> >> >>>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> I think right now we need to focus on getting a single trivial
>>>> >> >>>>> server
>>>> >> >>>>> mechanism to be able to run Stratos without too much of stuff
>>>> having
>>>> >> >>>>> to be
>>>> >> >>>>> set up. I'd love to see two developer distros:
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> - a VM image that has everything in it and runs in under 4GB
>>>> with
>>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>>>> Carbon
>>>> >> >>>>> server to
>>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>>>> (Carbon
>>>> >> >>>>> stuff
>>>> >> >>>>> HAS to run in one server - else its a bug in those products ..
>>>> so
>>>> >> >>>>> the
>>>> >> >>>>> decision should not be based on ability to run in one JVM but
>>>> rather
>>>> >> >>>>> just
>>>> >> >>>>> making it dirt simple to use.) This distro needs to be in
>>>> 4.0.0 - I
>>>> >> >>>>> think
>>>> >> >>>>> we're nearly there for it.
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a
>>>> direct
>>>> >> >>>>> plugin
>>>> >> >>>>> to jClouds that spins up Docker images as processes and
>>>> there's one
>>>> >> >>>>> JVM that
>>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one
>>>> JVM plus
>>>> >> >>>>> a URL
>>>> >> >>>>> to a Docker image registry from which the images are booted up
>>>> and
>>>> >> >>>>> run
>>>> >> >>>>> (obviously a local registry will do better). We don't have this
>>>> >> >>>>> no-IaaS-IaaS
>>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that
>>>> hard
>>>> >> >>>>> to make
>>>> >> >>>>> it work).
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> For production deployments obviously this one server stuff is
>>>> >> >>>>> nonsense
>>>> >> >>>>> .. so we need to have full decoupled distributed execution.
>>>> For that
>>>> >> >>>>> we
>>>> >> >>>>> should ship puppet scripts to get them up and running plus
>>>> maybe
>>>> >> >>>>> Boto
>>>> >> >>>>> scripts for someone to get it all up on EC2 with one command.
>>>> Again
>>>> >> >>>>> its
>>>> >> >>>>> totally fine to use whatever broker here and whatever other
>>>> >> >>>>> pluggable
>>>> >> >>>>> components people want to use (and we need to make sure all the
>>>> >> >>>>> parts are
>>>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>>>> etc.)).
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> Makes sense?
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> Sanjiva.
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>>> >> >>>>> <pr...@gmail.com>
>>>> >> >>>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> Hi Chris,
>>>> >> >>>>>
>>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>>> >> >>>>>
>>>> >> >>>>> Thanks
>>>> >> >>>>>
>>>> >> >>>>> --Pradeep
>>>> >> >>>>> sent from my phone
>>>> >> >>>>>
>>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>>>> wrote:
>>>> >> >>>>>
>>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work
>>>> to have
>>>> >> >>>>> a
>>>> >> >>>>> view on that :(
>>>> >> >>>>>
>>>> >> >>>>> One thing I'm wondering though is how much memory will be
>>>> saved if
>>>> >> >>>>> we
>>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>>> >> >>>>>
>>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>> >> >>>>> <pr...@gmail.com> wrote:
>>>> >> >>>>> > btw,
>>>> >> >>>>> >
>>>> >> >>>>> > Now im working on MB and CEP bits.
>>>> >> >>>>> >
>>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>>> stratos.
>>>> >> >>>>> > However,
>>>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>>>> profile
>>>> >> >>>>> > (the
>>>> >> >>>>> > profile that has all) makes sense.
>>>> >> >>>>> >
>>>> >> >>>>> > WDYT?
>>>> >> >>>>> >
>>>> >> >>>>> > Are we all on same page..
>>>> >> >>>>> >
>>>> >> >>>>> > thanks
>>>> >> >>>>> >
>>>> >> >>>>> >
>>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>>> chsnow123@gmail.com>
>>>> >> >>>>> > wrote:
>>>> >> >>>>> >>
>>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to
>>>> your
>>>> >> >>>>> >> findings!
>>>> >> >>>>> >>
>>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>> >> >>>>> >> <pr...@gmail.com>
>>>> >> >>>>> >> wrote:
>>>> >> >>>>> >> > Hi Guys,
>>>> >> >>>>> >> >
>>>> >> >>>>> >> > I started on the $subject. This thread is to track the
>>>> >> >>>>> >> > progress..
>>>> >> >>>>> >> >
>>>> >> >>>>> >> > thanks,
>>>> >> >>>>> >> >
>>>> >> >>>>> >> >
>>>> >> >>>>> >> > --
>>>> >> >>>>> >> > Pradeep Fernando.
>>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>>> >> >>>>> >>
>>>> >> >>>>> >>
>>>> >> >>>>> >>
>>>> >> >>>>> >> --
>>>> >> >>>>> >> Check out my professional profile and connect with me on
>>>> >> >>>>> >> LinkedIn.
>>>> >> >>>>> >> http://lnkd.in/cw5k69
>>>> >> >>>>> >
>>>> >> >>>>> >
>>>> >> >>>>> >
>>>> >> >>>>> >
>>>> >> >>>>> > --
>>>> >> >>>>> > Pradeep Fernando.
>>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> --
>>>> >> >>>>> Check out my professional profile and connect with me on
>>>> LinkedIn.
>>>> >> >>>>> http://lnkd.in/cw5k69
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> --
>>>> >> >>>>>
>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>> 214 5345)
>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>>> 265
>>>> >> >>>>> 8311
>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> >> >>>>> Lean . Enterprise . Middleware
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> --
>>>> >> >>>>>
>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>> 214 5345)
>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>>> 265
>>>> >> >>>>> 8311
>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> >> >>>>> Lean . Enterprise . Middleware
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>> --
>>>> >> >>>>>
>>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11
>>>> 214 5345)
>>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>>> 265
>>>> >> >>>>> 8311
>>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> >> >>>>> Lean . Enterprise . Middleware
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>>
>>>> >> >>>>
>>>> >> >>>>
>>>> >> >>>>
>>>> >> >>>> --
>>>> >> >>>> Pradeep Fernando.
>>>> >> >>>> http://pradeepfernando.blogspot.com/
>>>> >> >>>
>>>> >> >>>
>>>> >> >>>
>>>> >> >>>
>>>> >> >>> --
>>>> >> >>> Pradeep Fernando.
>>>> >> >>> http://pradeepfernando.blogspot.com/
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> --
>>>> >> >> Sameera Jayasoma
>>>> >> >>
>>>> >> >> blog: http://sameera.adahas.org
>>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Pradeep Fernando.
>>>> >> > http://pradeepfernando.blogspot.com/
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>> >> http://lnkd.in/cw5k69
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Best Regards,
>>>> > Nirmal
>>>> >
>>>> > Nirmal Fernando.
>>>> > PPMC Member & Committer of Apache Stratos,
>>>> > Senior Software Engineer, WSO2 Inc.
>>>> >
>>>> > Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>>
>>>>
>>>> --
>>>> Check out my professional profile and connect with me on LinkedIn.
>>>> http://lnkd.in/cw5k69
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
The jclouds CNF is a class loading issue, not a simple missing dependency
issue. I'm looking into it now.
On Wed, Mar 19, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
> Sounds good, though at some point in the future should we remove the
> dependency on using jndi? It seems a bit ironic that we are using a cross
> platform protocol AMPQ, but are connecting to it with a Java specific
> mechanism.
> On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com> wrote:
>
>> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time being
>> without much research, I'm going to use ActiveMQ.
>>
>>
>> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com> wrote:
>>
>>> Awesome - thanks Nirmal!
>>>
>>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <ni...@gmail.com>
>>> wrote:
>>> > I'll continue on this.
>>> >
>>> >
>>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>> >>
>>> >> Can this patch be reviewed and committed? I'm worried that unless it
>>> >> gets applied soon it will become out of date and difficult to commit
>>> >> later on.
>>> >>
>>> >>
>>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <
>>> pradeepfn@gmail.com>
>>> >> wrote:
>>> >> > apply the patch and add the jclouds dependency to reolve the jclouds
>>> >> > CNF.
>>> >> > After that, build the product named stratos. It contains all the
>>> >> > components
>>> >> > except MB.
>>> >> >
>>> >> > we can start a test round with an external MB
>>> >> >
>>> >> > hope this helps.. :)
>>> >> >
>>> >> > thanks.
>>> >> >
>>> >> >
>>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>>> >> > <sa...@gmail.com> wrote:
>>> >> >>
>>> >> >> Hi Pradeep,
>>> >> >>
>>> >> >> This patch contains so many code changes. Can you please provide an
>>> >> >> update
>>> >> >> on where we are on this? What are the remaining items?
>>> >> >>
>>> >> >> Thanks,
>>> >> >> Sameera.
>>> >> >>
>>> >> >>
>>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>>> >> >> <pr...@gmail.com>
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> Please someone takeover from here. Unfortunately i have to attend
>>> some
>>> >> >>> other work.
>>> >> >>>
>>> >> >>> I have created a JIRA and updated it. Patch attached.
>>> >> >>>
>>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>>> >> >>>
>>> >> >>> thanks.
>>> >> >>> --Pradeep
>>> >> >>>
>>> >> >>>
>>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>>> >> >>> <pr...@gmail.com>
>>> >> >>> wrote:
>>> >> >>>>
>>> >> >>>> Hi Guys,
>>> >> >>>>
>>> >> >>>> Now the server starts fine with as + cc + sm + cep
>>> >> >>>>
>>> >> >>>> I managed to workaround the classloading issue, by renaming stub
>>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>>> >> >>>> unavailability. Its a pretty straightforward fix.
>>> >> >>>>
>>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>>> >> >>>> while
>>> >> >>>> adding services from bundle :
>>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>> >> >>>> java.lang.NoClassDefFoundError:
>>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>>> >> >>>>
>>> >> >>>> at java.lang.Class.forName0(Native Method)
>>> >> >>>> at java.lang.Class.forName(Class.java:247)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>> >> >>>> at
>>> >> >>>>
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>> >> >>>> at
>>> >> >>>>
>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>> >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>>
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>> >> >>>> ... 49 more
>>> >> >>>> [2014-03-17 18:29:20,726] INFO
>>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>>> Deploying
>>> >> >>>> Axis2
>>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>>> >> >>>> [2014-03-17 18:29:21,465] INFO
>>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
>>> :
>>> >> >>>>
>>> >> >>>>
>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>> >> >>>> [2014-03-17 18:29:21,748] INFO
>>> >> >>>>
>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>> >> >>>> Permission cache updated for tenant -1234
>>> >> >>>> [2014-03-17 18:29:21,904] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> >> >>>> Thrift Server started at 10.100.1.80
>>> >> >>>> [2014-03-17 18:29:21,923] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> >> >>>> Thrift SSL port : 7711
>>> >> >>>> [2014-03-17 18:29:21,925] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> >> >>>> Thrift port : 7611
>>> >> >>>> [2014-03-17 18:29:21,958] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the input WSEventLocal adaptor service
>>> >> >>>> [2014-03-17 18:29:21,962] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the output WSEventLocal adaptor service
>>> >> >>>> [2014-03-17 18:29:21,976] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the input email event service
>>> >> >>>> [2014-03-17 18:29:21,983] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>>> >> >>>> [2014-03-17 18:29:21,993] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the output Email event adaptor service
>>> >> >>>> [2014-03-17 18:29:22,002] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the output SMS event adaptor service
>>> >> >>>> [2014-03-17 18:29:22,011] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>>> >> >>>> [2014-03-17 18:29:22,026] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>> >> >>>> A SSO Service Provider is registered for : console
>>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>>> >> >>>> configuration
>>> >> >>>> element 'TenantRegistrationPage' not found in
>>> >> >>>>
>>> >> >>>>
>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>>> >> >>>> HTTPS port
>>> >> >>>> : 9443
>>> >> >>>> [2014-03-17 18:29:22,133] INFO
>>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -
>>> HTTP
>>> >> >>>> port
>>> >> >>>> : 9763
>>> >> >>>> [2014-03-17 18:29:22,138] INFO
>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>> >> >>>> selector for
>>> >> >>>> servlet write/read
>>> >> >>>> [2014-03-17 18:29:22,154] INFO
>>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>> >> >>>> selector for
>>> >> >>>> servlet write/read
>>> >> >>>> [2014-03-17 18:29:22,193] INFO
>>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>>> >> >>>> service
>>> >> >>>> starting in STANDALONE mode...
>>> >> >>>> [2014-03-17 18:29:22,202] INFO
>>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>>> >> >>>> Setting
>>> >> >>>> config properties into System properties
>>> >> >>>> [2014-03-17 18:29:22,225] INFO
>>> >> >>>>
>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>> >> >>>> Topology receiver thread started
>>> >> >>>> [2014-03-17 18:29:22,226] INFO
>>> >> >>>>
>>> >> >>>>
>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>> >> >>>> - Stratos Manager topology receiver thread started
>>> >> >>>> [2014-03-17 18:29:22,231] INFO
>>> >> >>>>
>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>> >> >>>> ADC
>>> >> >>>> management server component is activated
>>> >> >>>> [2014-03-17 18:29:22,255] INFO
>>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL
>>> :
>>> >> >>>>
>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -
>>> Task
>>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent}
>>> -
>>> >> >>>> Server
>>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>> >> >>>> [2014-03-17 18:29:22,275] INFO
>>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent}
>>> -
>>> >> >>>> WSO2
>>> >> >>>> Carbon started in 55 sec
>>> >> >>>> [2014-03-17 18:29:22,430] INFO
>>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>>> Console
>>> >> >>>> URL :
>>> >> >>>> https://10.100.1.80:9443/carbon/
>>> >> >>>> [2014-03-17 18:29:22,521] INFO
>>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>>> Additional
>>> >> >>>> SASL
>>> >> >>>> providers successfully registered.
>>> >> >>>> [2014-03-17 18:29:22,522] INFO
>>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>>> Callback
>>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
>>> >> >>>> AMQPLAIN
>>> >> >>>> PLAIN
>>> >> >>>> [2014-03-17 18:29:22,535] WARN
>>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>>> >> >>>> Unable to find resource qpidversion.properties from classloader
>>> >> >>>>
>>> >> >>>>
>>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>>> shahhaqu@cisco.com>
>>> >> >>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Hi Pradeep,
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> I *think* I am interested in this topic and am new to this
>>> domain,
>>> >> >>>>> but
>>> >> >>>>> from the archives, I'm not 100% of the original goals of this
>>> work.
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take
>>> advantage of
>>> >> >>>>> your work: do we still use the same CLIs to start the processes
>>> or
>>> >> >>>>> what? I
>>> >> >>>>> see some mention of profiles and pre-built VMs, but am unclear
>>> how
>>> >> >>>>> they
>>> >> >>>>> relate to this.
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this feature I
>>> can
>>> >> >>>>> read?
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> Thanks, Shaheed
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>> >> >>>>>
>>> >> >>>>> Interesting ... it would be cool to combine these with something
>>> >> >>>>> like
>>> >> >>>>> rPath to build a minimal Linux image with just the exact bits
>>> in it.
>>> >> >>>>> Looks
>>> >> >>>>> like rPath is gone - what's the way people build custom images
>>> now?
>>> >> >>>>> Or is
>>> >> >>>>> that gone with just more memory and more disk being normal??
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>>> chsnow123@gmail.com>
>>> >> >>>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Hi Sanjiva,
>>> >> >>>>>
>>> >> >>>>> Vagrant works on top of an existing image (box). There are
>>> plenty of
>>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes
>>> [1],
>>> >> >>>>> although
>>> >> >>>>> the disk size is a little small to be useful. Opscode also
>>> >> >>>>> provide some
>>> >> >>>>> pretty good boxes [2]. If these still don't meet your needs,
>>> you can
>>> >> >>>>> copy
>>> >> >>>>> the packer definitions from opscode and modify them to build
>>> your
>>> >> >>>>> own box
>>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>>> >> >>>>>
>>> >> >>>>> Many thanks,
>>> >> >>>>>
>>> >> >>>>> Chris
>>> >> >>>>>
>>> >> >>>>> ---
>>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>> >> >>>>> [2] https://github.com/opscode/bento
>>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>> >> >>>>> [4] http://packer.io
>>> >> >>>>>
>>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
>>> >> >>>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>>> scripts
>>> >> >>>>> as
>>> >> >>>>> well!
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does it
>>> build
>>> >> >>>>> a
>>> >> >>>>> VM image or does it set up the environment to run the image?
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> Sanjiva.
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <
>>> chsnow123@gmail.com>
>>> >> >>>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Hi Sanjiva,
>>> >> >>>>>
>>> >> >>>>> For VM images, vagrant makes life very easy for users; setting
>>> up
>>> >> >>>>> disks, setting up network cards, setting up memory, configuring
>>> >> >>>>> guest proxy
>>> >> >>>>> settings, running provisioning scripts, etc.
>>> >> >>>>>
>>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
>>> project
>>> >> >>>>> is
>>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making
>>> good
>>> >> >>>>> progress.
>>> >> >>>>> Although my scripts are buggy, with a few commands I can
>>> checkout,
>>> >> >>>>> build and
>>> >> >>>>> provision a cloudstack developer environment. I am now working
>>> on
>>> >> >>>>> the
>>> >> >>>>> scripts to do the same for Stratos.
>>> >> >>>>>
>>> >> >>>>> Initially, the memory requirements will be high on my
>>> environment,
>>> >> >>>>> but
>>> >> >>>>> for me the first goal is automation, the next goal will be
>>> >> >>>>> efficiency.
>>> >> >>>>>
>>> >> >>>>> Many thanks,
>>> >> >>>>> Chris
>>> >> >>>>>
>>> >> >>>>> ---
>>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>>> >> >>>>>
>>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
>>> >> >>>>> wrote:
>>> >> >>>>>
>>> >> >>>>> I think right now we need to focus on getting a single trivial
>>> >> >>>>> server
>>> >> >>>>> mechanism to be able to run Stratos without too much of stuff
>>> having
>>> >> >>>>> to be
>>> >> >>>>> set up. I'd love to see two developer distros:
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> - a VM image that has everything in it and runs in under 4GB
>>> with
>>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>>> Carbon
>>> >> >>>>> server to
>>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>>> (Carbon
>>> >> >>>>> stuff
>>> >> >>>>> HAS to run in one server - else its a bug in those products ..
>>> so
>>> >> >>>>> the
>>> >> >>>>> decision should not be based on ability to run in one JVM but
>>> rather
>>> >> >>>>> just
>>> >> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0
>>> - I
>>> >> >>>>> think
>>> >> >>>>> we're nearly there for it.
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
>>> >> >>>>> plugin
>>> >> >>>>> to jClouds that spins up Docker images as processes and there's
>>> one
>>> >> >>>>> JVM that
>>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
>>> plus
>>> >> >>>>> a URL
>>> >> >>>>> to a Docker image registry from which the images are booted up
>>> and
>>> >> >>>>> run
>>> >> >>>>> (obviously a local registry will do better). We don't have this
>>> >> >>>>> no-IaaS-IaaS
>>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that
>>> hard
>>> >> >>>>> to make
>>> >> >>>>> it work).
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> For production deployments obviously this one server stuff is
>>> >> >>>>> nonsense
>>> >> >>>>> .. so we need to have full decoupled distributed execution. For
>>> that
>>> >> >>>>> we
>>> >> >>>>> should ship puppet scripts to get them up and running plus maybe
>>> >> >>>>> Boto
>>> >> >>>>> scripts for someone to get it all up on EC2 with one command.
>>> Again
>>> >> >>>>> its
>>> >> >>>>> totally fine to use whatever broker here and whatever other
>>> >> >>>>> pluggable
>>> >> >>>>> components people want to use (and we need to make sure all the
>>> >> >>>>> parts are
>>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>>> etc.)).
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> Makes sense?
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> Sanjiva.
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>>> >> >>>>> <pr...@gmail.com>
>>> >> >>>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Hi Chris,
>>> >> >>>>>
>>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>>> >> >>>>>
>>> >> >>>>> Thanks
>>> >> >>>>>
>>> >> >>>>> --Pradeep
>>> >> >>>>> sent from my phone
>>> >> >>>>>
>>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work to
>>> have
>>> >> >>>>> a
>>> >> >>>>> view on that :(
>>> >> >>>>>
>>> >> >>>>> One thing I'm wondering though is how much memory will be saved
>>> if
>>> >> >>>>> we
>>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>>> >> >>>>>
>>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>> >> >>>>> <pr...@gmail.com> wrote:
>>> >> >>>>> > btw,
>>> >> >>>>> >
>>> >> >>>>> > Now im working on MB and CEP bits.
>>> >> >>>>> >
>>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in
>>> stratos.
>>> >> >>>>> > However,
>>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>>> profile
>>> >> >>>>> > (the
>>> >> >>>>> > profile that has all) makes sense.
>>> >> >>>>> >
>>> >> >>>>> > WDYT?
>>> >> >>>>> >
>>> >> >>>>> > Are we all on same page..
>>> >> >>>>> >
>>> >> >>>>> > thanks
>>> >> >>>>> >
>>> >> >>>>> >
>>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>>> chsnow123@gmail.com>
>>> >> >>>>> > wrote:
>>> >> >>>>> >>
>>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to
>>> your
>>> >> >>>>> >> findings!
>>> >> >>>>> >>
>>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>> >> >>>>> >> <pr...@gmail.com>
>>> >> >>>>> >> wrote:
>>> >> >>>>> >> > Hi Guys,
>>> >> >>>>> >> >
>>> >> >>>>> >> > I started on the $subject. This thread is to track the
>>> >> >>>>> >> > progress..
>>> >> >>>>> >> >
>>> >> >>>>> >> > thanks,
>>> >> >>>>> >> >
>>> >> >>>>> >> >
>>> >> >>>>> >> > --
>>> >> >>>>> >> > Pradeep Fernando.
>>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>>> >> >>>>> >>
>>> >> >>>>> >>
>>> >> >>>>> >>
>>> >> >>>>> >> --
>>> >> >>>>> >> Check out my professional profile and connect with me on
>>> >> >>>>> >> LinkedIn.
>>> >> >>>>> >> http://lnkd.in/cw5k69
>>> >> >>>>> >
>>> >> >>>>> >
>>> >> >>>>> >
>>> >> >>>>> >
>>> >> >>>>> > --
>>> >> >>>>> > Pradeep Fernando.
>>> >> >>>>> > http://pradeepfernando.blogspot.com/
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> --
>>> >> >>>>> Check out my professional profile and connect with me on
>>> LinkedIn.
>>> >> >>>>> http://lnkd.in/cw5k69
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> --
>>> >> >>>>>
>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>>> 5345)
>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>> 265
>>> >> >>>>> 8311
>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> >> >>>>> Lean . Enterprise . Middleware
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> --
>>> >> >>>>>
>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>>> 5345)
>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>> 265
>>> >> >>>>> 8311
>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> >> >>>>> Lean . Enterprise . Middleware
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> --
>>> >> >>>>>
>>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>>> 5345)
>>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650
>>> 265
>>> >> >>>>> 8311
>>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> >> >>>>> Lean . Enterprise . Middleware
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>
>>> >> >>>>
>>> >> >>>>
>>> >> >>>> --
>>> >> >>>> Pradeep Fernando.
>>> >> >>>> http://pradeepfernando.blogspot.com/
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>> --
>>> >> >>> Pradeep Fernando.
>>> >> >>> http://pradeepfernando.blogspot.com/
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> Sameera Jayasoma
>>> >> >>
>>> >> >> blog: http://sameera.adahas.org
>>> >> >> twitter: https://twitter.com/sameerajayasoma
>>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Pradeep Fernando.
>>> >> > http://pradeepfernando.blogspot.com/
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Check out my professional profile and connect with me on LinkedIn.
>>> >> http://lnkd.in/cw5k69
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Best Regards,
>>> > Nirmal
>>> >
>>> > Nirmal Fernando.
>>> > PPMC Member & Committer of Apache Stratos,
>>> > Senior Software Engineer, WSO2 Inc.
>>> >
>>> > Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Sounds good, though at some point in the future should we remove the
dependency on using jndi? It seems a bit ironic that we are using a cross
platform protocol AMPQ, but are connecting to it with a Java specific
mechanism.
On 19 Mar 2014 07:27, "Nirmal Fernando" <ni...@gmail.com> wrote:
> Seems like RabbitMQ doesn't have JNDI support yet. So, for the time being
> without much research, I'm going to use ActiveMQ.
>
>
> On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com> wrote:
>
>> Awesome - thanks Nirmal!
>>
>> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>> > I'll continue on this.
>> >
>> >
>> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com>
>> wrote:
>> >>
>> >> Can this patch be reviewed and committed? I'm worried that unless it
>> >> gets applied soon it will become out of date and difficult to commit
>> >> later on.
>> >>
>> >>
>> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <pradeepfn@gmail.com
>> >
>> >> wrote:
>> >> > apply the patch and add the jclouds dependency to reolve the jclouds
>> >> > CNF.
>> >> > After that, build the product named stratos. It contains all the
>> >> > components
>> >> > except MB.
>> >> >
>> >> > we can start a test round with an external MB
>> >> >
>> >> > hope this helps.. :)
>> >> >
>> >> > thanks.
>> >> >
>> >> >
>> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>> >> > <sa...@gmail.com> wrote:
>> >> >>
>> >> >> Hi Pradeep,
>> >> >>
>> >> >> This patch contains so many code changes. Can you please provide an
>> >> >> update
>> >> >> on where we are on this? What are the remaining items?
>> >> >>
>> >> >> Thanks,
>> >> >> Sameera.
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>> >> >> <pr...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Please someone takeover from here. Unfortunately i have to attend
>> some
>> >> >>> other work.
>> >> >>>
>> >> >>> I have created a JIRA and updated it. Patch attached.
>> >> >>>
>> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
>> >> >>>
>> >> >>> thanks.
>> >> >>> --Pradeep
>> >> >>>
>> >> >>>
>> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>> >> >>> <pr...@gmail.com>
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> Hi Guys,
>> >> >>>>
>> >> >>>> Now the server starts fine with as + cc + sm + cep
>> >> >>>>
>> >> >>>> I managed to workaround the classloading issue, by renaming stub
>> >> >>>> packages. Right now im encountering a CNF due to jcloud class
>> >> >>>> unavailability. Its a pretty straightforward fix.
>> >> >>>>
>> >> >>>> [2014-03-17 18:29:20,715] ERROR
>> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>> >> >>>> while
>> >> >>>> adding services from bundle :
>> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>> >> >>>> java.lang.NoClassDefFoundError:
>> >> >>>> org/jclouds/rest/ResourceNotFoundException
>> >> >>>>
>> >> >>>> at java.lang.Class.forName0(Native Method)
>> >> >>>> at java.lang.Class.forName(Class.java:247)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> >> >>>> at
>> >> >>>>
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>> >> >>>> at
>> >> >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> >> >>>> at java.lang.Thread.run(Thread.java:662)
>> >> >>>> Caused by: java.lang.ClassNotFoundException:
>> >> >>>> org.jclouds.rest.ResourceNotFoundException
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> >> >>>> at
>> >> >>>>
>> >> >>>>
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> >> >>>> ... 49 more
>> >> >>>> [2014-03-17 18:29:20,726] INFO
>> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
>> Deploying
>> >> >>>> Axis2
>> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
>> >> >>>> [2014-03-17 18:29:21,465] INFO
>> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
>> :
>> >> >>>>
>> >> >>>>
>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>> >> >>>> [2014-03-17 18:29:21,748] INFO
>> >> >>>>
>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>> >> >>>> Permission cache updated for tenant -1234
>> >> >>>> [2014-03-17 18:29:21,904] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >> >>>> Thrift Server started at 10.100.1.80
>> >> >>>> [2014-03-17 18:29:21,923] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >> >>>> Thrift SSL port : 7711
>> >> >>>> [2014-03-17 18:29:21,925] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >> >>>> Thrift port : 7611
>> >> >>>> [2014-03-17 18:29:21,958] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the input WSEventLocal adaptor service
>> >> >>>> [2014-03-17 18:29:21,962] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output WSEventLocal adaptor service
>> >> >>>> [2014-03-17 18:29:21,976] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the input email event service
>> >> >>>> [2014-03-17 18:29:21,983] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the input WSEvent adaptor service
>> >> >>>> [2014-03-17 18:29:21,993] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output Email event adaptor service
>> >> >>>> [2014-03-17 18:29:22,002] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output SMS event adaptor service
>> >> >>>> [2014-03-17 18:29:22,011] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> >> >>>> - Successfully deployed the output WSEvent adaptor service
>> >> >>>> [2014-03-17 18:29:22,026] INFO
>> >> >>>>
>> >> >>>>
>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>> >> >>>> A SSO Service Provider is registered for : console
>> >> >>>> [2014-03-17 18:29:22,060] ERROR
>> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>> >> >>>> configuration
>> >> >>>> element 'TenantRegistrationPage' not found in
>> >> >>>>
>> >> >>>>
>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>> >> >>>> [2014-03-17 18:29:22,133] INFO
>> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>> >> >>>> HTTPS port
>> >> >>>> : 9443
>> >> >>>> [2014-03-17 18:29:22,133] INFO
>> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -
>> HTTP
>> >> >>>> port
>> >> >>>> : 9763
>> >> >>>> [2014-03-17 18:29:22,138] INFO
>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>> >> >>>> selector for
>> >> >>>> servlet write/read
>> >> >>>> [2014-03-17 18:29:22,154] INFO
>> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>> >> >>>> selector for
>> >> >>>> servlet write/read
>> >> >>>> [2014-03-17 18:29:22,193] INFO
>> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>> >> >>>> service
>> >> >>>> starting in STANDALONE mode...
>> >> >>>> [2014-03-17 18:29:22,202] INFO
>> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>> >> >>>> Setting
>> >> >>>> config properties into System properties
>> >> >>>> [2014-03-17 18:29:22,225] INFO
>> >> >>>>
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> >> >>>> Topology receiver thread started
>> >> >>>> [2014-03-17 18:29:22,226] INFO
>> >> >>>>
>> >> >>>>
>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>> >> >>>> - Stratos Manager topology receiver thread started
>> >> >>>> [2014-03-17 18:29:22,231] INFO
>> >> >>>>
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> >> >>>> ADC
>> >> >>>> management server component is activated
>> >> >>>> [2014-03-17 18:29:22,255] INFO
>> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>> >> >>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>> >> >>>> [2014-03-17 18:29:22,275] INFO
>> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -
>> Task
>> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>> >> >>>> [2014-03-17 18:29:22,275] INFO
>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> >> >>>> Server
>> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>> >> >>>> [2014-03-17 18:29:22,275] INFO
>> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> >> >>>> WSO2
>> >> >>>> Carbon started in 55 sec
>> >> >>>> [2014-03-17 18:29:22,430] INFO
>> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>> Console
>> >> >>>> URL :
>> >> >>>> https://10.100.1.80:9443/carbon/
>> >> >>>> [2014-03-17 18:29:22,521] INFO
>> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} -
>> Additional
>> >> >>>> SASL
>> >> >>>> providers successfully registered.
>> >> >>>> [2014-03-17 18:29:22,522] INFO
>> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
>> Callback
>> >> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
>> >> >>>> AMQPLAIN
>> >> >>>> PLAIN
>> >> >>>> [2014-03-17 18:29:22,535] WARN
>> >> >>>> {org.wso2.andes.common.QpidProperties} -
>> >> >>>> Unable to find resource qpidversion.properties from classloader
>> >> >>>>
>> >> >>>>
>> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <
>> shahhaqu@cisco.com>
>> >> >>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Pradeep,
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> I *think* I am interested in this topic and am new to this
>> domain,
>> >> >>>>> but
>> >> >>>>> from the archives, I'm not 100% of the original goals of this
>> work.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage
>> of
>> >> >>>>> your work: do we still use the same CLIs to start the processes
>> or
>> >> >>>>> what? I
>> >> >>>>> see some mention of profiles and pre-built VMs, but am unclear
>> how
>> >> >>>>> they
>> >> >>>>> relate to this.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Can you clarify please? Is there a JIRA/spec for this feature I
>> can
>> >> >>>>> read?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Thanks, Shaheed
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>> >> >>>>>
>> >> >>>>> Interesting ... it would be cool to combine these with something
>> >> >>>>> like
>> >> >>>>> rPath to build a minimal Linux image with just the exact bits in
>> it.
>> >> >>>>> Looks
>> >> >>>>> like rPath is gone - what's the way people build custom images
>> now?
>> >> >>>>> Or is
>> >> >>>>> that gone with just more memory and more disk being normal??
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <
>> chsnow123@gmail.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Sanjiva,
>> >> >>>>>
>> >> >>>>> Vagrant works on top of an existing image (box). There are
>> plenty of
>> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
>> >> >>>>> although
>> >> >>>>> the disk size is a little small to be useful. Opscode also
>> >> >>>>> provide some
>> >> >>>>> pretty good boxes [2]. If these still don't meet your needs, you
>> can
>> >> >>>>> copy
>> >> >>>>> the packer definitions from opscode and modify them to build your
>> >> >>>>> own box
>> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
>> >> >>>>>
>> >> >>>>> Many thanks,
>> >> >>>>>
>> >> >>>>> Chris
>> >> >>>>>
>> >> >>>>> ---
>> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>> >> >>>>> [2] https://github.com/opscode/bento
>> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>> >> >>>>> [4] http://packer.io
>> >> >>>>>
>> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
>> scripts
>> >> >>>>> as
>> >> >>>>> well!
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> I'm not familiar with vagrant - just checking it out. Does it
>> build
>> >> >>>>> a
>> >> >>>>> VM image or does it set up the environment to run the image?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Sanjiva.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <chsnow123@gmail.com
>> >
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Sanjiva,
>> >> >>>>>
>> >> >>>>> For VM images, vagrant makes life very easy for users; setting up
>> >> >>>>> disks, setting up network cards, setting up memory, configuring
>> >> >>>>> guest proxy
>> >> >>>>> settings, running provisioning scripts, etc.
>> >> >>>>>
>> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
>> project
>> >> >>>>> is
>> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making good
>> >> >>>>> progress.
>> >> >>>>> Although my scripts are buggy, with a few commands I can
>> checkout,
>> >> >>>>> build and
>> >> >>>>> provision a cloudstack developer environment. I am now working
>> on
>> >> >>>>> the
>> >> >>>>> scripts to do the same for Stratos.
>> >> >>>>>
>> >> >>>>> Initially, the memory requirements will be high on my
>> environment,
>> >> >>>>> but
>> >> >>>>> for me the first goal is automation, the next goal will be
>> >> >>>>> efficiency.
>> >> >>>>>
>> >> >>>>> Many thanks,
>> >> >>>>> Chris
>> >> >>>>>
>> >> >>>>> ---
>> >> >>>>> [1] https://github.com/snowch/devcloud-script
>> >> >>>>>
>> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> I think right now we need to focus on getting a single trivial
>> >> >>>>> server
>> >> >>>>> mechanism to be able to run Stratos without too much of stuff
>> having
>> >> >>>>> to be
>> >> >>>>> set up. I'd love to see two developer distros:
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> - a VM image that has everything in it and runs in under 4GB with
>> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
>> Carbon
>> >> >>>>> server to
>> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
>> (Carbon
>> >> >>>>> stuff
>> >> >>>>> HAS to run in one server - else its a bug in those products .. so
>> >> >>>>> the
>> >> >>>>> decision should not be based on ability to run in one JVM but
>> rather
>> >> >>>>> just
>> >> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0
>> - I
>> >> >>>>> think
>> >> >>>>> we're nearly there for it.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
>> >> >>>>> plugin
>> >> >>>>> to jClouds that spins up Docker images as processes and there's
>> one
>> >> >>>>> JVM that
>> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
>> plus
>> >> >>>>> a URL
>> >> >>>>> to a Docker image registry from which the images are booted up
>> and
>> >> >>>>> run
>> >> >>>>> (obviously a local registry will do better). We don't have this
>> >> >>>>> no-IaaS-IaaS
>> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that
>> hard
>> >> >>>>> to make
>> >> >>>>> it work).
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> For production deployments obviously this one server stuff is
>> >> >>>>> nonsense
>> >> >>>>> .. so we need to have full decoupled distributed execution. For
>> that
>> >> >>>>> we
>> >> >>>>> should ship puppet scripts to get them up and running plus maybe
>> >> >>>>> Boto
>> >> >>>>> scripts for someone to get it all up on EC2 with one command.
>> Again
>> >> >>>>> its
>> >> >>>>> totally fine to use whatever broker here and whatever other
>> >> >>>>> pluggable
>> >> >>>>> components people want to use (and we need to make sure all the
>> >> >>>>> parts are
>> >> >>>>> pluggable: load balancers, message broker, the CEP engine,
>> etc.)).
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Makes sense?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Sanjiva.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>> >> >>>>> <pr...@gmail.com>
>> >> >>>>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Chris,
>> >> >>>>>
>> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
>> >> >>>>>
>> >> >>>>> Thanks
>> >> >>>>>
>> >> >>>>> --Pradeep
>> >> >>>>> sent from my phone
>> >> >>>>>
>> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
>> wrote:
>> >> >>>>>
>> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work to
>> have
>> >> >>>>> a
>> >> >>>>> view on that :(
>> >> >>>>>
>> >> >>>>> One thing I'm wondering though is how much memory will be saved
>> if
>> >> >>>>> we
>> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
>> >> >>>>>
>> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>> >> >>>>> <pr...@gmail.com> wrote:
>> >> >>>>> > btw,
>> >> >>>>> >
>> >> >>>>> > Now im working on MB and CEP bits.
>> >> >>>>> >
>> >> >>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>> >> >>>>> > However,
>> >> >>>>> > adding MB/CEP features (the ones that we use) to default
>> profile
>> >> >>>>> > (the
>> >> >>>>> > profile that has all) makes sense.
>> >> >>>>> >
>> >> >>>>> > WDYT?
>> >> >>>>> >
>> >> >>>>> > Are we all on same page..
>> >> >>>>> >
>> >> >>>>> > thanks
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
>> chsnow123@gmail.com>
>> >> >>>>> > wrote:
>> >> >>>>> >>
>> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> >> >>>>> >> findings!
>> >> >>>>> >>
>> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>> >> >>>>> >> <pr...@gmail.com>
>> >> >>>>> >> wrote:
>> >> >>>>> >> > Hi Guys,
>> >> >>>>> >> >
>> >> >>>>> >> > I started on the $subject. This thread is to track the
>> >> >>>>> >> > progress..
>> >> >>>>> >> >
>> >> >>>>> >> > thanks,
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > --
>> >> >>>>> >> > Pradeep Fernando.
>> >> >>>>> >> > http://pradeepfernando.blogspot.com/
>> >> >>>>> >>
>> >> >>>>> >>
>> >> >>>>> >>
>> >> >>>>> >> --
>> >> >>>>> >> Check out my professional profile and connect with me on
>> >> >>>>> >> LinkedIn.
>> >> >>>>> >> http://lnkd.in/cw5k69
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > --
>> >> >>>>> > Pradeep Fernando.
>> >> >>>>> > http://pradeepfernando.blogspot.com/
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>> Check out my professional profile and connect with me on
>> LinkedIn.
>> >> >>>>> http://lnkd.in/cw5k69
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> 5345)
>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >> >>>>> 8311
>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >> >>>>> Lean . Enterprise . Middleware
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> 5345)
>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >> >>>>> 8311
>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >> >>>>> Lean . Enterprise . Middleware
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>> Sanjiva Weerawarana, Ph.D.
>> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> 5345)
>> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >> >>>>> 8311
>> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >> >>>>> Lean . Enterprise . Middleware
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> Pradeep Fernando.
>> >> >>>> http://pradeepfernando.blogspot.com/
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Pradeep Fernando.
>> >> >>> http://pradeepfernando.blogspot.com/
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Sameera Jayasoma
>> >> >>
>> >> >> blog: http://sameera.adahas.org
>> >> >> twitter: https://twitter.com/sameerajayasoma
>> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Pradeep Fernando.
>> >> > http://pradeepfernando.blogspot.com/
>> >>
>> >>
>> >>
>> >> --
>> >> Check out my professional profile and connect with me on LinkedIn.
>> >> http://lnkd.in/cw5k69
>> >
>> >
>> >
>> >
>> > --
>> > Best Regards,
>> > Nirmal
>> >
>> > Nirmal Fernando.
>> > PPMC Member & Committer of Apache Stratos,
>> > Senior Software Engineer, WSO2 Inc.
>> >
>> > Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Seems like RabbitMQ doesn't have JNDI support yet. So, for the time being
without much research, I'm going to use ActiveMQ.
On Wed, Mar 19, 2014 at 10:32 AM, chris snow <ch...@gmail.com> wrote:
> Awesome - thanks Nirmal!
>
> On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <ni...@gmail.com>
> wrote:
> > I'll continue on this.
> >
> >
> > On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com> wrote:
> >>
> >> Can this patch be reviewed and committed? I'm worried that unless it
> >> gets applied soon it will become out of date and difficult to commit
> >> later on.
> >>
> >>
> >> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <pr...@gmail.com>
> >> wrote:
> >> > apply the patch and add the jclouds dependency to reolve the jclouds
> >> > CNF.
> >> > After that, build the product named stratos. It contains all the
> >> > components
> >> > except MB.
> >> >
> >> > we can start a test round with an external MB
> >> >
> >> > hope this helps.. :)
> >> >
> >> > thanks.
> >> >
> >> >
> >> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
> >> > <sa...@gmail.com> wrote:
> >> >>
> >> >> Hi Pradeep,
> >> >>
> >> >> This patch contains so many code changes. Can you please provide an
> >> >> update
> >> >> on where we are on this? What are the remaining items?
> >> >>
> >> >> Thanks,
> >> >> Sameera.
> >> >>
> >> >>
> >> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
> >> >> <pr...@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Please someone takeover from here. Unfortunately i have to attend
> some
> >> >>> other work.
> >> >>>
> >> >>> I have created a JIRA and updated it. Patch attached.
> >> >>>
> >> >>> https://issues.apache.org/jira/browse/STRATOS-523
> >> >>>
> >> >>> thanks.
> >> >>> --Pradeep
> >> >>>
> >> >>>
> >> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
> >> >>> <pr...@gmail.com>
> >> >>> wrote:
> >> >>>>
> >> >>>> Hi Guys,
> >> >>>>
> >> >>>> Now the server starts fine with as + cc + sm + cep
> >> >>>>
> >> >>>> I managed to workaround the classloading issue, by renaming stub
> >> >>>> packages. Right now im encountering a CNF due to jcloud class
> >> >>>> unavailability. Its a pretty straightforward fix.
> >> >>>>
> >> >>>> [2014-03-17 18:29:20,715] ERROR
> >> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
> >> >>>> while
> >> >>>> adding services from bundle :
> >> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> >> >>>> java.lang.NoClassDefFoundError:
> >> >>>> org/jclouds/rest/ResourceNotFoundException
> >> >>>>
> >> >>>> at java.lang.Class.forName0(Native Method)
> >> >>>> at java.lang.Class.forName(Class.java:247)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> >>>> at
> >> >>>>
> >> >>>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >> >>>> at
> >> >>>>
> >> >>>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> >> >>>> at
> >> >>>>
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> >> >>>> at
> >> >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >> >>>> at
> >> >>>>
> >> >>>>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >> >>>> at
> >> >>>>
> >> >>>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >> >>>> at java.lang.Thread.run(Thread.java:662)
> >> >>>> Caused by: java.lang.ClassNotFoundException:
> >> >>>> org.jclouds.rest.ResourceNotFoundException
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> >> >>>> at
> >> >>>>
> >> >>>>
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> >> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> >> >>>> ... 49 more
> >> >>>> [2014-03-17 18:29:20,726] INFO
> >> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -
> Deploying
> >> >>>> Axis2
> >> >>>> service: InstanceCleanupNotificationService {super-tenant}
> >> >>>> [2014-03-17 18:29:21,465] INFO
> >> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository
> :
> >> >>>>
> >> >>>>
> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
> >> >>>> [2014-03-17 18:29:21,748] INFO
> >> >>>>
> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> >> >>>> Permission cache updated for tenant -1234
> >> >>>> [2014-03-17 18:29:21,904] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >> >>>> Thrift Server started at 10.100.1.80
> >> >>>> [2014-03-17 18:29:21,923] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >> >>>> Thrift SSL port : 7711
> >> >>>> [2014-03-17 18:29:21,925] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >> >>>> Thrift port : 7611
> >> >>>> [2014-03-17 18:29:21,958] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the input WSEventLocal adaptor service
> >> >>>> [2014-03-17 18:29:21,962] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the output WSEventLocal adaptor service
> >> >>>> [2014-03-17 18:29:21,976] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the input email event service
> >> >>>> [2014-03-17 18:29:21,983] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the input WSEvent adaptor service
> >> >>>> [2014-03-17 18:29:21,993] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the output Email event adaptor service
> >> >>>> [2014-03-17 18:29:22,002] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the output SMS event adaptor service
> >> >>>> [2014-03-17 18:29:22,011] INFO
> >> >>>>
> >> >>>>
> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >> >>>> - Successfully deployed the output WSEvent adaptor service
> >> >>>> [2014-03-17 18:29:22,026] INFO
> >> >>>>
> >> >>>>
> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
> >> >>>> A SSO Service Provider is registered for : console
> >> >>>> [2014-03-17 18:29:22,060] ERROR
> >> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
> >> >>>> configuration
> >> >>>> element 'TenantRegistrationPage' not found in
> >> >>>>
> >> >>>>
> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
> >> >>>> [2014-03-17 18:29:22,133] INFO
> >> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
> >> >>>> HTTPS port
> >> >>>> : 9443
> >> >>>> [2014-03-17 18:29:22,133] INFO
> >> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -
> HTTP
> >> >>>> port
> >> >>>> : 9763
> >> >>>> [2014-03-17 18:29:22,138] INFO
> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> >> >>>> selector for
> >> >>>> servlet write/read
> >> >>>> [2014-03-17 18:29:22,154] INFO
> >> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> >> >>>> selector for
> >> >>>> servlet write/read
> >> >>>> [2014-03-17 18:29:22,193] INFO
> >> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
> >> >>>> service
> >> >>>> starting in STANDALONE mode...
> >> >>>> [2014-03-17 18:29:22,202] INFO
> >> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
> >> >>>> Setting
> >> >>>> config properties into System properties
> >> >>>> [2014-03-17 18:29:22,225] INFO
> >> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent}
> -
> >> >>>> Topology receiver thread started
> >> >>>> [2014-03-17 18:29:22,226] INFO
> >> >>>>
> >> >>>>
> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
> >> >>>> - Stratos Manager topology receiver thread started
> >> >>>> [2014-03-17 18:29:22,231] INFO
> >> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent}
> -
> >> >>>> ADC
> >> >>>> management server component is activated
> >> >>>> [2014-03-17 18:29:22,255] INFO
> >> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
> >> >>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
> >> >>>> [2014-03-17 18:29:22,275] INFO
> >> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
> >> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
> >> >>>> [2014-03-17 18:29:22,275] INFO
> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> >> >>>> Server
> >> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
> >> >>>> [2014-03-17 18:29:22,275] INFO
> >> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> >> >>>> WSO2
> >> >>>> Carbon started in 55 sec
> >> >>>> [2014-03-17 18:29:22,430] INFO
> >> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
> Console
> >> >>>> URL :
> >> >>>> https://10.100.1.80:9443/carbon/
> >> >>>> [2014-03-17 18:29:22,521] INFO
> >> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
> >> >>>> SASL
> >> >>>> providers successfully registered.
> >> >>>> [2014-03-17 18:29:22,522] INFO
> >> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} -
> Callback
> >> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
> >> >>>> AMQPLAIN
> >> >>>> PLAIN
> >> >>>> [2014-03-17 18:29:22,535] WARN
> >> >>>> {org.wso2.andes.common.QpidProperties} -
> >> >>>> Unable to find resource qpidversion.properties from classloader
> >> >>>>
> >> >>>>
> >> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <shahhaqu@cisco.com
> >
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> Hi Pradeep,
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> I *think* I am interested in this topic and am new to this domain,
> >> >>>>> but
> >> >>>>> from the archives, I'm not 100% of the original goals of this
> work.
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage
> of
> >> >>>>> your work: do we still use the same CLIs to start the processes or
> >> >>>>> what? I
> >> >>>>> see some mention of profiles and pre-built VMs, but am unclear how
> >> >>>>> they
> >> >>>>> relate to this.
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Can you clarify please? Is there a JIRA/spec for this feature I
> can
> >> >>>>> read?
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Thanks, Shaheed
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
> >> >>>>>
> >> >>>>> Interesting ... it would be cool to combine these with something
> >> >>>>> like
> >> >>>>> rPath to build a minimal Linux image with just the exact bits in
> it.
> >> >>>>> Looks
> >> >>>>> like rPath is gone - what's the way people build custom images
> now?
> >> >>>>> Or is
> >> >>>>> that gone with just more memory and more disk being normal??
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <chsnow123@gmail.com
> >
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>> Hi Sanjiva,
> >> >>>>>
> >> >>>>> Vagrant works on top of an existing image (box). There are plenty
> of
> >> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
> >> >>>>> although
> >> >>>>> the disk size is a little small to be useful. Opscode also
> >> >>>>> provide some
> >> >>>>> pretty good boxes [2]. If these still don't meet your needs, you
> can
> >> >>>>> copy
> >> >>>>> the packer definitions from opscode and modify them to build your
> >> >>>>> own box
> >> >>>>> from scratch [3]. Packer is definitely worth a look too.
> >> >>>>>
> >> >>>>> Many thanks,
> >> >>>>>
> >> >>>>> Chris
> >> >>>>>
> >> >>>>> ---
> >> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
> >> >>>>> [2] https://github.com/opscode/bento
> >> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
> >> >>>>> [4] http://packer.io
> >> >>>>>
> >> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant
> scripts
> >> >>>>> as
> >> >>>>> well!
> >> >>>>>
> >> >>>>>
> >> >>>>> I'm not familiar with vagrant - just checking it out. Does it
> build
> >> >>>>> a
> >> >>>>> VM image or does it set up the environment to run the image?
> >> >>>>>
> >> >>>>>
> >> >>>>> Sanjiva.
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>> Hi Sanjiva,
> >> >>>>>
> >> >>>>> For VM images, vagrant makes life very easy for users; setting up
> >> >>>>> disks, setting up network cards, setting up memory, configuring
> >> >>>>> guest proxy
> >> >>>>> settings, running provisioning scripts, etc.
> >> >>>>>
> >> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My
> project
> >> >>>>> is
> >> >>>>> here [1]. It isn't ready for general use yet, but I'm making good
> >> >>>>> progress.
> >> >>>>> Although my scripts are buggy, with a few commands I can checkout,
> >> >>>>> build and
> >> >>>>> provision a cloudstack developer environment. I am now working on
> >> >>>>> the
> >> >>>>> scripts to do the same for Stratos.
> >> >>>>>
> >> >>>>> Initially, the memory requirements will be high on my environment,
> >> >>>>> but
> >> >>>>> for me the first goal is automation, the next goal will be
> >> >>>>> efficiency.
> >> >>>>>
> >> >>>>> Many thanks,
> >> >>>>> Chris
> >> >>>>>
> >> >>>>> ---
> >> >>>>> [1] https://github.com/snowch/devcloud-script
> >> >>>>>
> >> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>> I think right now we need to focus on getting a single trivial
> >> >>>>> server
> >> >>>>> mechanism to be able to run Stratos without too much of stuff
> having
> >> >>>>> to be
> >> >>>>> set up. I'd love to see two developer distros:
> >> >>>>>
> >> >>>>>
> >> >>>>> - a VM image that has everything in it and runs in under 4GB with
> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon
> >> >>>>> server to
> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
> (Carbon
> >> >>>>> stuff
> >> >>>>> HAS to run in one server - else its a bug in those products .. so
> >> >>>>> the
> >> >>>>> decision should not be based on ability to run in one JVM but
> rather
> >> >>>>> just
> >> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 -
> I
> >> >>>>> think
> >> >>>>> we're nearly there for it.
> >> >>>>>
> >> >>>>>
> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
> >> >>>>> plugin
> >> >>>>> to jClouds that spins up Docker images as processes and there's
> one
> >> >>>>> JVM that
> >> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
> plus
> >> >>>>> a URL
> >> >>>>> to a Docker image registry from which the images are booted up and
> >> >>>>> run
> >> >>>>> (obviously a local registry will do better). We don't have this
> >> >>>>> no-IaaS-IaaS
> >> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard
> >> >>>>> to make
> >> >>>>> it work).
> >> >>>>>
> >> >>>>>
> >> >>>>> For production deployments obviously this one server stuff is
> >> >>>>> nonsense
> >> >>>>> .. so we need to have full decoupled distributed execution. For
> that
> >> >>>>> we
> >> >>>>> should ship puppet scripts to get them up and running plus maybe
> >> >>>>> Boto
> >> >>>>> scripts for someone to get it all up on EC2 with one command.
> Again
> >> >>>>> its
> >> >>>>> totally fine to use whatever broker here and whatever other
> >> >>>>> pluggable
> >> >>>>> components people want to use (and we need to make sure all the
> >> >>>>> parts are
> >> >>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
> >> >>>>>
> >> >>>>>
> >> >>>>> Makes sense?
> >> >>>>>
> >> >>>>>
> >> >>>>> Sanjiva.
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
> >> >>>>> <pr...@gmail.com>
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>> Hi Chris,
> >> >>>>>
> >> >>>>> Yes good point. Other day Azeez did the same suggestion.
> >> >>>>>
> >> >>>>> Thanks
> >> >>>>>
> >> >>>>> --Pradeep
> >> >>>>> sent from my phone
> >> >>>>>
> >> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
> wrote:
> >> >>>>>
> >> >>>>> Hi Pradeep - I don't know enough about how the profiles work to
> have
> >> >>>>> a
> >> >>>>> view on that :(
> >> >>>>>
> >> >>>>> One thing I'm wondering though is how much memory will be saved if
> >> >>>>> we
> >> >>>>> use RabbitMQ (or another MQ) instead of MB?
> >> >>>>>
> >> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
> >> >>>>> <pr...@gmail.com> wrote:
> >> >>>>> > btw,
> >> >>>>> >
> >> >>>>> > Now im working on MB and CEP bits.
> >> >>>>> >
> >> >>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
> >> >>>>> > However,
> >> >>>>> > adding MB/CEP features (the ones that we use) to default profile
> >> >>>>> > (the
> >> >>>>> > profile that has all) makes sense.
> >> >>>>> >
> >> >>>>> > WDYT?
> >> >>>>> >
> >> >>>>> > Are we all on same page..
> >> >>>>> >
> >> >>>>> > thanks
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <
> chsnow123@gmail.com>
> >> >>>>> > wrote:
> >> >>>>> >>
> >> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
> >> >>>>> >> findings!
> >> >>>>> >>
> >> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
> >> >>>>> >> <pr...@gmail.com>
> >> >>>>> >> wrote:
> >> >>>>> >> > Hi Guys,
> >> >>>>> >> >
> >> >>>>> >> > I started on the $subject. This thread is to track the
> >> >>>>> >> > progress..
> >> >>>>> >> >
> >> >>>>> >> > thanks,
> >> >>>>> >> >
> >> >>>>> >> >
> >> >>>>> >> > --
> >> >>>>> >> > Pradeep Fernando.
> >> >>>>> >> > http://pradeepfernando.blogspot.com/
> >> >>>>> >>
> >> >>>>> >>
> >> >>>>> >>
> >> >>>>> >> --
> >> >>>>> >> Check out my professional profile and connect with me on
> >> >>>>> >> LinkedIn.
> >> >>>>> >> http://lnkd.in/cw5k69
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > --
> >> >>>>> > Pradeep Fernando.
> >> >>>>> > http://pradeepfernando.blogspot.com/
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>> Check out my professional profile and connect with me on LinkedIn.
> >> >>>>> http://lnkd.in/cw5k69
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>>
> >> >>>>> Sanjiva Weerawarana, Ph.D.
> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
> 5345)
> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> >> >>>>> 8311
> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >> >>>>> Lean . Enterprise . Middleware
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>>
> >> >>>>> Sanjiva Weerawarana, Ph.D.
> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
> 5345)
> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> >> >>>>> 8311
> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >> >>>>> Lean . Enterprise . Middleware
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>>
> >> >>>>> Sanjiva Weerawarana, Ph.D.
> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
> 5345)
> >> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> >> >>>>> 8311
> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >> >>>>> Lean . Enterprise . Middleware
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Pradeep Fernando.
> >> >>>> http://pradeepfernando.blogspot.com/
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Pradeep Fernando.
> >> >>> http://pradeepfernando.blogspot.com/
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Sameera Jayasoma
> >> >>
> >> >> blog: http://sameera.adahas.org
> >> >> twitter: https://twitter.com/sameerajayasoma
> >> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Pradeep Fernando.
> >> > http://pradeepfernando.blogspot.com/
> >>
> >>
> >>
> >> --
> >> Check out my professional profile and connect with me on LinkedIn.
> >> http://lnkd.in/cw5k69
> >
> >
> >
> >
> > --
> > Best Regards,
> > Nirmal
> >
> > Nirmal Fernando.
> > PPMC Member & Committer of Apache Stratos,
> > Senior Software Engineer, WSO2 Inc.
> >
> > Blog: http://nirmalfdo.blogspot.com/
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Awesome - thanks Nirmal!
On Wed, Mar 19, 2014 at 4:01 AM, Nirmal Fernando <ni...@gmail.com> wrote:
> I'll continue on this.
>
>
> On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Can this patch be reviewed and committed? I'm worried that unless it
>> gets applied soon it will become out of date and difficult to commit
>> later on.
>>
>>
>> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > apply the patch and add the jclouds dependency to reolve the jclouds
>> > CNF.
>> > After that, build the product named stratos. It contains all the
>> > components
>> > except MB.
>> >
>> > we can start a test round with an external MB
>> >
>> > hope this helps.. :)
>> >
>> > thanks.
>> >
>> >
>> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
>> > <sa...@gmail.com> wrote:
>> >>
>> >> Hi Pradeep,
>> >>
>> >> This patch contains so many code changes. Can you please provide an
>> >> update
>> >> on where we are on this? What are the remaining items?
>> >>
>> >> Thanks,
>> >> Sameera.
>> >>
>> >>
>> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando
>> >> <pr...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Please someone takeover from here. Unfortunately i have to attend some
>> >>> other work.
>> >>>
>> >>> I have created a JIRA and updated it. Patch attached.
>> >>>
>> >>> https://issues.apache.org/jira/browse/STRATOS-523
>> >>>
>> >>> thanks.
>> >>> --Pradeep
>> >>>
>> >>>
>> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando
>> >>> <pr...@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi Guys,
>> >>>>
>> >>>> Now the server starts fine with as + cc + sm + cep
>> >>>>
>> >>>> I managed to workaround the classloading issue, by renaming stub
>> >>>> packages. Right now im encountering a CNF due to jcloud class
>> >>>> unavailability. Its a pretty straightforward fix.
>> >>>>
>> >>>> [2014-03-17 18:29:20,715] ERROR
>> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error
>> >>>> while
>> >>>> adding services from bundle :
>> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>> >>>> java.lang.NoClassDefFoundError:
>> >>>> org/jclouds/rest/ResourceNotFoundException
>> >>>>
>> >>>> at java.lang.Class.forName0(Native Method)
>> >>>> at java.lang.Class.forName(Class.java:247)
>> >>>> at
>> >>>>
>> >>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>> >>>> at
>> >>>>
>> >>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>> >>>> at
>> >>>>
>> >>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>> >>>> at
>> >>>>
>> >>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >>>> at
>> >>>>
>> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >>>> at
>> >>>>
>> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> >>>> at
>> >>>>
>> >>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> >>>> at
>> >>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>> >>>> at
>> >>>>
>> >>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>> >>>> at
>> >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> >>>> at
>> >>>>
>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> >>>> at
>> >>>>
>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> >>>> at java.lang.Thread.run(Thread.java:662)
>> >>>> Caused by: java.lang.ClassNotFoundException:
>> >>>> org.jclouds.rest.ResourceNotFoundException
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> >>>> at
>> >>>>
>> >>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> >>>> ... 49 more
>> >>>> [2014-03-17 18:29:20,726] INFO
>> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
>> >>>> Axis2
>> >>>> service: InstanceCleanupNotificationService {super-tenant}
>> >>>> [2014-03-17 18:29:21,465] INFO
>> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
>> >>>>
>> >>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>> >>>> [2014-03-17 18:29:21,748] INFO
>> >>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>> >>>> Permission cache updated for tenant -1234
>> >>>> [2014-03-17 18:29:21,904] INFO
>> >>>>
>> >>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >>>> Thrift Server started at 10.100.1.80
>> >>>> [2014-03-17 18:29:21,923] INFO
>> >>>>
>> >>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >>>> Thrift SSL port : 7711
>> >>>> [2014-03-17 18:29:21,925] INFO
>> >>>>
>> >>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> >>>> Thrift port : 7611
>> >>>> [2014-03-17 18:29:21,958] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> >>>> - Successfully deployed the input WSEventLocal adaptor service
>> >>>> [2014-03-17 18:29:21,962] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> >>>> - Successfully deployed the output WSEventLocal adaptor service
>> >>>> [2014-03-17 18:29:21,976] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> >>>> - Successfully deployed the input email event service
>> >>>> [2014-03-17 18:29:21,983] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> >>>> - Successfully deployed the input WSEvent adaptor service
>> >>>> [2014-03-17 18:29:21,993] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> >>>> - Successfully deployed the output Email event adaptor service
>> >>>> [2014-03-17 18:29:22,002] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>> >>>> - Successfully deployed the output SMS event adaptor service
>> >>>> [2014-03-17 18:29:22,011] INFO
>> >>>>
>> >>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> >>>> - Successfully deployed the output WSEvent adaptor service
>> >>>> [2014-03-17 18:29:22,026] INFO
>> >>>>
>> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>> >>>> A SSO Service Provider is registered for : console
>> >>>> [2014-03-17 18:29:22,060] ERROR
>> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The
>> >>>> configuration
>> >>>> element 'TenantRegistrationPage' not found in
>> >>>>
>> >>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>> >>>> [2014-03-17 18:29:22,133] INFO
>> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
>> >>>> HTTPS port
>> >>>> : 9443
>> >>>> [2014-03-17 18:29:22,133] INFO
>> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>> >>>> port
>> >>>> : 9763
>> >>>> [2014-03-17 18:29:22,138] INFO
>> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>> >>>> selector for
>> >>>> servlet write/read
>> >>>> [2014-03-17 18:29:22,154] INFO
>> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>> >>>> selector for
>> >>>> servlet write/read
>> >>>> [2014-03-17 18:29:22,193] INFO
>> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
>> >>>> service
>> >>>> starting in STANDALONE mode...
>> >>>> [2014-03-17 18:29:22,202] INFO
>> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
>> >>>> Setting
>> >>>> config properties into System properties
>> >>>> [2014-03-17 18:29:22,225] INFO
>> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> >>>> Topology receiver thread started
>> >>>> [2014-03-17 18:29:22,226] INFO
>> >>>>
>> >>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>> >>>> - Stratos Manager topology receiver thread started
>> >>>> [2014-03-17 18:29:22,231] INFO
>> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> >>>> ADC
>> >>>> management server component is activated
>> >>>> [2014-03-17 18:29:22,255] INFO
>> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>> >>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>> >>>> [2014-03-17 18:29:22,275] INFO
>> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>> >>>> [2014-03-17 18:29:22,275] INFO
>> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> >>>> Server
>> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>> >>>> [2014-03-17 18:29:22,275] INFO
>> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> >>>> WSO2
>> >>>> Carbon started in 55 sec
>> >>>> [2014-03-17 18:29:22,430] INFO
>> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
>> >>>> URL :
>> >>>> https://10.100.1.80:9443/carbon/
>> >>>> [2014-03-17 18:29:22,521] INFO
>> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
>> >>>> SASL
>> >>>> providers successfully registered.
>> >>>> [2014-03-17 18:29:22,522] INFO
>> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
>> >>>> AMQPLAIN
>> >>>> PLAIN
>> >>>> [2014-03-17 18:29:22,535] WARN
>> >>>> {org.wso2.andes.common.QpidProperties} -
>> >>>> Unable to find resource qpidversion.properties from classloader
>> >>>>
>> >>>>
>> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> Hi Pradeep,
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> I *think* I am interested in this topic and am new to this domain,
>> >>>>> but
>> >>>>> from the archives, I'm not 100% of the original goals of this work.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of
>> >>>>> your work: do we still use the same CLIs to start the processes or
>> >>>>> what? I
>> >>>>> see some mention of profiles and pre-built VMs, but am unclear how
>> >>>>> they
>> >>>>> relate to this.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Can you clarify please? Is there a JIRA/spec for this feature I can
>> >>>>> read?
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Thanks, Shaheed
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>> >>>>>
>> >>>>> Interesting ... it would be cool to combine these with something
>> >>>>> like
>> >>>>> rPath to build a minimal Linux image with just the exact bits in it.
>> >>>>> Looks
>> >>>>> like rPath is gone - what's the way people build custom images now?
>> >>>>> Or is
>> >>>>> that gone with just more memory and more disk being normal??
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>> Hi Sanjiva,
>> >>>>>
>> >>>>> Vagrant works on top of an existing image (box). There are plenty of
>> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
>> >>>>> although
>> >>>>> the disk size is a little small to be useful. Opscode also
>> >>>>> provide some
>> >>>>> pretty good boxes [2]. If these still don't meet your needs, you can
>> >>>>> copy
>> >>>>> the packer definitions from opscode and modify them to build your
>> >>>>> own box
>> >>>>> from scratch [3]. Packer is definitely worth a look too.
>> >>>>>
>> >>>>> Many thanks,
>> >>>>>
>> >>>>> Chris
>> >>>>>
>> >>>>> ---
>> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>> >>>>> [2] https://github.com/opscode/bento
>> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
>> >>>>> [4] http://packer.io
>> >>>>>
>> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts
>> >>>>> as
>> >>>>> well!
>> >>>>>
>> >>>>>
>> >>>>> I'm not familiar with vagrant - just checking it out. Does it build
>> >>>>> a
>> >>>>> VM image or does it set up the environment to run the image?
>> >>>>>
>> >>>>>
>> >>>>> Sanjiva.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>> Hi Sanjiva,
>> >>>>>
>> >>>>> For VM images, vagrant makes life very easy for users; setting up
>> >>>>> disks, setting up network cards, setting up memory, configuring
>> >>>>> guest proxy
>> >>>>> settings, running provisioning scripts, etc.
>> >>>>>
>> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My project
>> >>>>> is
>> >>>>> here [1]. It isn't ready for general use yet, but I'm making good
>> >>>>> progress.
>> >>>>> Although my scripts are buggy, with a few commands I can checkout,
>> >>>>> build and
>> >>>>> provision a cloudstack developer environment. I am now working on
>> >>>>> the
>> >>>>> scripts to do the same for Stratos.
>> >>>>>
>> >>>>> Initially, the memory requirements will be high on my environment,
>> >>>>> but
>> >>>>> for me the first goal is automation, the next goal will be
>> >>>>> efficiency.
>> >>>>>
>> >>>>> Many thanks,
>> >>>>> Chris
>> >>>>>
>> >>>>> ---
>> >>>>> [1] https://github.com/snowch/devcloud-script
>> >>>>>
>> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>> I think right now we need to focus on getting a single trivial
>> >>>>> server
>> >>>>> mechanism to be able to run Stratos without too much of stuff having
>> >>>>> to be
>> >>>>> set up. I'd love to see two developer distros:
>> >>>>>
>> >>>>>
>> >>>>> - a VM image that has everything in it and runs in under 4GB with
>> >>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon
>> >>>>> server to
>> >>>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>> >>>>> stuff
>> >>>>> HAS to run in one server - else its a bug in those products .. so
>> >>>>> the
>> >>>>> decision should not be based on ability to run in one JVM but rather
>> >>>>> just
>> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I
>> >>>>> think
>> >>>>> we're nearly there for it.
>> >>>>>
>> >>>>>
>> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
>> >>>>> plugin
>> >>>>> to jClouds that spins up Docker images as processes and there's one
>> >>>>> JVM that
>> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus
>> >>>>> a URL
>> >>>>> to a Docker image registry from which the images are booted up and
>> >>>>> run
>> >>>>> (obviously a local registry will do better). We don't have this
>> >>>>> no-IaaS-IaaS
>> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard
>> >>>>> to make
>> >>>>> it work).
>> >>>>>
>> >>>>>
>> >>>>> For production deployments obviously this one server stuff is
>> >>>>> nonsense
>> >>>>> .. so we need to have full decoupled distributed execution. For that
>> >>>>> we
>> >>>>> should ship puppet scripts to get them up and running plus maybe
>> >>>>> Boto
>> >>>>> scripts for someone to get it all up on EC2 with one command. Again
>> >>>>> its
>> >>>>> totally fine to use whatever broker here and whatever other
>> >>>>> pluggable
>> >>>>> components people want to use (and we need to make sure all the
>> >>>>> parts are
>> >>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>> >>>>>
>> >>>>>
>> >>>>> Makes sense?
>> >>>>>
>> >>>>>
>> >>>>> Sanjiva.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>> >>>>> <pr...@gmail.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>> Hi Chris,
>> >>>>>
>> >>>>> Yes good point. Other day Azeez did the same suggestion.
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> --Pradeep
>> >>>>> sent from my phone
>> >>>>>
>> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>> >>>>>
>> >>>>> Hi Pradeep - I don't know enough about how the profiles work to have
>> >>>>> a
>> >>>>> view on that :(
>> >>>>>
>> >>>>> One thing I'm wondering though is how much memory will be saved if
>> >>>>> we
>> >>>>> use RabbitMQ (or another MQ) instead of MB?
>> >>>>>
>> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>> >>>>> <pr...@gmail.com> wrote:
>> >>>>> > btw,
>> >>>>> >
>> >>>>> > Now im working on MB and CEP bits.
>> >>>>> >
>> >>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>> >>>>> > However,
>> >>>>> > adding MB/CEP features (the ones that we use) to default profile
>> >>>>> > (the
>> >>>>> > profile that has all) makes sense.
>> >>>>> >
>> >>>>> > WDYT?
>> >>>>> >
>> >>>>> > Are we all on same page..
>> >>>>> >
>> >>>>> > thanks
>> >>>>> >
>> >>>>> >
>> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>> >>>>> > wrote:
>> >>>>> >>
>> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> >>>>> >> findings!
>> >>>>> >>
>> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>> >>>>> >> <pr...@gmail.com>
>> >>>>> >> wrote:
>> >>>>> >> > Hi Guys,
>> >>>>> >> >
>> >>>>> >> > I started on the $subject. This thread is to track the
>> >>>>> >> > progress..
>> >>>>> >> >
>> >>>>> >> > thanks,
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > --
>> >>>>> >> > Pradeep Fernando.
>> >>>>> >> > http://pradeepfernando.blogspot.com/
>> >>>>> >>
>> >>>>> >>
>> >>>>> >>
>> >>>>> >> --
>> >>>>> >> Check out my professional profile and connect with me on
>> >>>>> >> LinkedIn.
>> >>>>> >> http://lnkd.in/cw5k69
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> > --
>> >>>>> > Pradeep Fernando.
>> >>>>> > http://pradeepfernando.blogspot.com/
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Check out my professional profile and connect with me on LinkedIn.
>> >>>>> http://lnkd.in/cw5k69
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>> Sanjiva Weerawarana, Ph.D.
>> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >>>>> 8311
>> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >>>>> Lean . Enterprise . Middleware
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>> Sanjiva Weerawarana, Ph.D.
>> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >>>>> 8311
>> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >>>>> Lean . Enterprise . Middleware
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>> Sanjiva Weerawarana, Ph.D.
>> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
>> >>>>> 8311
>> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >>>>> Lean . Enterprise . Middleware
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Pradeep Fernando.
>> >>>> http://pradeepfernando.blogspot.com/
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Pradeep Fernando.
>> >>> http://pradeepfernando.blogspot.com/
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Sameera Jayasoma
>> >>
>> >> blog: http://sameera.adahas.org
>> >> twitter: https://twitter.com/sameerajayasoma
>> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>> >
>> >
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
I'll continue on this.
On Tue, Mar 18, 2014 at 1:15 PM, chris snow <ch...@gmail.com> wrote:
> Can this patch be reviewed and committed? I'm worried that unless it
> gets applied soon it will become out of date and difficult to commit
> later on.
>
>
> On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <pr...@gmail.com>
> wrote:
> > apply the patch and add the jclouds dependency to reolve the jclouds CNF.
> > After that, build the product named stratos. It contains all the
> components
> > except MB.
> >
> > we can start a test round with an external MB
> >
> > hope this helps.. :)
> >
> > thanks.
> >
> >
> > On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
> > <sa...@gmail.com> wrote:
> >>
> >> Hi Pradeep,
> >>
> >> This patch contains so many code changes. Can you please provide an
> update
> >> on where we are on this? What are the remaining items?
> >>
> >> Thanks,
> >> Sameera.
> >>
> >>
> >> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando <pradeepfn@gmail.com
> >
> >> wrote:
> >>>
> >>> Please someone takeover from here. Unfortunately i have to attend some
> >>> other work.
> >>>
> >>> I have created a JIRA and updated it. Patch attached.
> >>>
> >>> https://issues.apache.org/jira/browse/STRATOS-523
> >>>
> >>> thanks.
> >>> --Pradeep
> >>>
> >>>
> >>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pradeepfn@gmail.com
> >
> >>> wrote:
> >>>>
> >>>> Hi Guys,
> >>>>
> >>>> Now the server starts fine with as + cc + sm + cep
> >>>>
> >>>> I managed to workaround the classloading issue, by renaming stub
> >>>> packages. Right now im encountering a CNF due to jcloud class
> >>>> unavailability. Its a pretty straightforward fix.
> >>>>
> >>>> [2014-03-17 18:29:20,715] ERROR
> >>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> >>>> adding services from bundle :
> >>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> >>>> java.lang.NoClassDefFoundError:
> >>>> org/jclouds/rest/ResourceNotFoundException
> >>>>
> >>>> at java.lang.Class.forName0(Native Method)
> >>>> at java.lang.Class.forName(Class.java:247)
> >>>> at
> >>>>
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> >>>> at
> >>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> >>>> at
> >>>>
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> >>>> at
> >>>>
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> >>>> at
> >>>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> >>>> at
> >>>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> >>>> at
> >>>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> >>>> at
> >>>>
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> >>>> at
> >>>>
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> >>>> at
> >>>>
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>> at
> >>>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>>> at
> >>>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> >>>> at
> >>>>
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> >>>> at
> >>>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> >>>> at
> >>>>
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> >>>> at
> >>>>
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> >>>> at
> >>>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> >>>> at
> >>>>
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> >>>> at
> >>>>
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> >>>> at
> >>>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> >>>> at
> >>>>
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> >>>> at
> >>>>
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> >>>> at
> >>>>
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> >>>> at
> >>>>
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> >>>> at
> >>>>
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> >>>> at
> >>>>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> >>>> at
> >>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> >>>> at
> >>>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> >>>> at
> >>>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> >>>> at
> >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >>>> at
> >>>>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >>>> at
> >>>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >>>> at java.lang.Thread.run(Thread.java:662)
> >>>> Caused by: java.lang.ClassNotFoundException:
> >>>> org.jclouds.rest.ResourceNotFoundException
> >>>> at
> >>>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> >>>> at
> >>>>
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> >>>> ... 49 more
> >>>> [2014-03-17 18:29:20,726] INFO
> >>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
> Axis2
> >>>> service: InstanceCleanupNotificationService {super-tenant}
> >>>> [2014-03-17 18:29:21,465] INFO
> >>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
> >>>>
> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
> >>>> [2014-03-17 18:29:21,748] INFO
> >>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> >>>> Permission cache updated for tenant -1234
> >>>> [2014-03-17 18:29:21,904] INFO
> >>>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>>> Thrift Server started at 10.100.1.80
> >>>> [2014-03-17 18:29:21,923] INFO
> >>>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>>> Thrift SSL port : 7711
> >>>> [2014-03-17 18:29:21,925] INFO
> >>>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>>> Thrift port : 7611
> >>>> [2014-03-17 18:29:21,958] INFO
> >>>>
> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >>>> - Successfully deployed the input WSEventLocal adaptor service
> >>>> [2014-03-17 18:29:21,962] INFO
> >>>>
> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >>>> - Successfully deployed the output WSEventLocal adaptor service
> >>>> [2014-03-17 18:29:21,976] INFO
> >>>>
> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >>>> - Successfully deployed the input email event service
> >>>> [2014-03-17 18:29:21,983] INFO
> >>>>
> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >>>> - Successfully deployed the input WSEvent adaptor service
> >>>> [2014-03-17 18:29:21,993] INFO
> >>>>
> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >>>> - Successfully deployed the output Email event adaptor service
> >>>> [2014-03-17 18:29:22,002] INFO
> >>>>
> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
> >>>> - Successfully deployed the output SMS event adaptor service
> >>>> [2014-03-17 18:29:22,011] INFO
> >>>>
> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >>>> - Successfully deployed the output WSEvent adaptor service
> >>>> [2014-03-17 18:29:22,026] INFO
> >>>>
> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
> >>>> A SSO Service Provider is registered for : console
> >>>> [2014-03-17 18:29:22,060] ERROR
> >>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
> >>>> element 'TenantRegistrationPage' not found in
> >>>>
> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
> >>>> [2014-03-17 18:29:22,133] INFO
> >>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -
> HTTPS port
> >>>> : 9443
> >>>> [2014-03-17 18:29:22,133] INFO
> >>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
> port
> >>>> : 9763
> >>>> [2014-03-17 18:29:22,138] INFO
> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> selector for
> >>>> servlet write/read
> >>>> [2014-03-17 18:29:22,154] INFO
> >>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> selector for
> >>>> servlet write/read
> >>>> [2014-03-17 18:29:22,193] INFO
> >>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
> service
> >>>> starting in STANDALONE mode...
> >>>> [2014-03-17 18:29:22,202] INFO
> >>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} -
> Setting
> >>>> config properties into System properties
> >>>> [2014-03-17 18:29:22,225] INFO
> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> >>>> Topology receiver thread started
> >>>> [2014-03-17 18:29:22,226] INFO
> >>>>
> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
> >>>> - Stratos Manager topology receiver thread started
> >>>> [2014-03-17 18:29:22,231] INFO
> >>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> ADC
> >>>> management server component is activated
> >>>> [2014-03-17 18:29:22,255] INFO
> >>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
> >>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
> >>>> [2014-03-17 18:29:22,275] INFO
> >>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
> >>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
> >>>> [2014-03-17 18:29:22,275] INFO
> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> Server
> >>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
> >>>> [2014-03-17 18:29:22,275] INFO
> >>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> WSO2
> >>>> Carbon started in 55 sec
> >>>> [2014-03-17 18:29:22,430] INFO
> >>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
> URL :
> >>>> https://10.100.1.80:9443/carbon/
> >>>> [2014-03-17 18:29:22,521] INFO
> >>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
> SASL
> >>>> providers successfully registered.
> >>>> [2014-03-17 18:29:22,522] INFO
> >>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
> >>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
> AMQPLAIN
> >>>> PLAIN
> >>>> [2014-03-17 18:29:22,535] WARN
> {org.wso2.andes.common.QpidProperties} -
> >>>> Unable to find resource qpidversion.properties from classloader
> >>>>
> >>>>
> >>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>
> >>>> wrote:
> >>>>>
> >>>>> Hi Pradeep,
> >>>>>
> >>>>>
> >>>>>
> >>>>> I *think* I am interested in this topic and am new to this domain,
> but
> >>>>> from the archives, I'm not 100% of the original goals of this work.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of
> >>>>> your work: do we still use the same CLIs to start the processes or
> what? I
> >>>>> see some mention of profiles and pre-built VMs, but am unclear how
> they
> >>>>> relate to this.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Can you clarify please? Is there a JIRA/spec for this feature I can
> >>>>> read?
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks, Shaheed
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
> >>>>>
> >>>>> Interesting ... it would be cool to combine these with something like
> >>>>> rPath to build a minimal Linux image with just the exact bits in it.
> Looks
> >>>>> like rPath is gone - what's the way people build custom images now?
> Or is
> >>>>> that gone with just more memory and more disk being normal??
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>> Hi Sanjiva,
> >>>>>
> >>>>> Vagrant works on top of an existing image (box). There are plenty of
> >>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
> although
> >>>>> the disk size is a little small to be useful. Opscode also
> provide some
> >>>>> pretty good boxes [2]. If these still don't meet your needs, you can
> copy
> >>>>> the packer definitions from opscode and modify them to build your
> own box
> >>>>> from scratch [3]. Packer is definitely worth a look too.
> >>>>>
> >>>>> Many thanks,
> >>>>>
> >>>>> Chris
> >>>>>
> >>>>> ---
> >>>>> [1] http://cloud-images.ubuntu.com/vagrant/
> >>>>> [2] https://github.com/opscode/bento
> >>>>> [3] https://github.com/opscode/bento/tree/master/packer
> >>>>> [4] http://packer.io
> >>>>>
> >>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
> wrote:
> >>>>>
> >>>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts
> as
> >>>>> well!
> >>>>>
> >>>>>
> >>>>> I'm not familiar with vagrant - just checking it out. Does it build a
> >>>>> VM image or does it set up the environment to run the image?
> >>>>>
> >>>>>
> >>>>> Sanjiva.
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>> Hi Sanjiva,
> >>>>>
> >>>>> For VM images, vagrant makes life very easy for users; setting up
> >>>>> disks, setting up network cards, setting up memory, configuring
> guest proxy
> >>>>> settings, running provisioning scripts, etc.
> >>>>>
> >>>>> I am working on a vagrant setup of cloudstack + Stratos. My project
> is
> >>>>> here [1]. It isn't ready for general use yet, but I'm making good
> progress.
> >>>>> Although my scripts are buggy, with a few commands I can checkout,
> build and
> >>>>> provision a cloudstack developer environment. I am now working on
> the
> >>>>> scripts to do the same for Stratos.
> >>>>>
> >>>>> Initially, the memory requirements will be high on my environment,
> but
> >>>>> for me the first goal is automation, the next goal will be
> efficiency.
> >>>>>
> >>>>> Many thanks,
> >>>>> Chris
> >>>>>
> >>>>> ---
> >>>>> [1] https://github.com/snowch/devcloud-script
> >>>>>
> >>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
> wrote:
> >>>>>
> >>>>> I think right now we need to focus on getting a single trivial server
> >>>>> mechanism to be able to run Stratos without too much of stuff having
> to be
> >>>>> set up. I'd love to see two developer distros:
> >>>>>
> >>>>>
> >>>>> - a VM image that has everything in it and runs in under 4GB with
> >>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon
> server to
> >>>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff
> >>>>> HAS to run in one server - else its a bug in those products .. so the
> >>>>> decision should not be based on ability to run in one JVM but rather
> just
> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I
> think
> >>>>> we're nearly there for it.
> >>>>>
> >>>>>
> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
> plugin
> >>>>> to jClouds that spins up Docker images as processes and there's one
> JVM that
> >>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus
> a URL
> >>>>> to a Docker image registry from which the images are booted up and
> run
> >>>>> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS
> >>>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard
> to make
> >>>>> it work).
> >>>>>
> >>>>>
> >>>>> For production deployments obviously this one server stuff is
> nonsense
> >>>>> .. so we need to have full decoupled distributed execution. For that
> we
> >>>>> should ship puppet scripts to get them up and running plus maybe Boto
> >>>>> scripts for someone to get it all up on EC2 with one command. Again
> its
> >>>>> totally fine to use whatever broker here and whatever other pluggable
> >>>>> components people want to use (and we need to make sure all the
> parts are
> >>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
> >>>>>
> >>>>>
> >>>>> Makes sense?
> >>>>>
> >>>>>
> >>>>> Sanjiva.
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <
> pradeepfn@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>> Hi Chris,
> >>>>>
> >>>>> Yes good point. Other day Azeez did the same suggestion.
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> --Pradeep
> >>>>> sent from my phone
> >>>>>
> >>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
> >>>>>
> >>>>> Hi Pradeep - I don't know enough about how the profiles work to have
> a
> >>>>> view on that :(
> >>>>>
> >>>>> One thing I'm wondering though is how much memory will be saved if we
> >>>>> use RabbitMQ (or another MQ) instead of MB?
> >>>>>
> >>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
> >>>>> <pr...@gmail.com> wrote:
> >>>>> > btw,
> >>>>> >
> >>>>> > Now im working on MB and CEP bits.
> >>>>> >
> >>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
> >>>>> > However,
> >>>>> > adding MB/CEP features (the ones that we use) to default profile
> (the
> >>>>> > profile that has all) makes sense.
> >>>>> >
> >>>>> > WDYT?
> >>>>> >
> >>>>> > Are we all on same page..
> >>>>> >
> >>>>> > thanks
> >>>>> >
> >>>>> >
> >>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
> >>>>> > wrote:
> >>>>> >>
> >>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
> >>>>> >> findings!
> >>>>> >>
> >>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
> >>>>> >> <pr...@gmail.com>
> >>>>> >> wrote:
> >>>>> >> > Hi Guys,
> >>>>> >> >
> >>>>> >> > I started on the $subject. This thread is to track the
> progress..
> >>>>> >> >
> >>>>> >> > thanks,
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > --
> >>>>> >> > Pradeep Fernando.
> >>>>> >> > http://pradeepfernando.blogspot.com/
> >>>>> >>
> >>>>> >>
> >>>>> >>
> >>>>> >> --
> >>>>> >> Check out my professional profile and connect with me on LinkedIn.
> >>>>> >> http://lnkd.in/cw5k69
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > Pradeep Fernando.
> >>>>> > http://pradeepfernando.blogspot.com/
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Check out my professional profile and connect with me on LinkedIn.
> >>>>> http://lnkd.in/cw5k69
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Sanjiva Weerawarana, Ph.D.
> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> 8311
> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>>> Lean . Enterprise . Middleware
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Sanjiva Weerawarana, Ph.D.
> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> 8311
> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>>> Lean . Enterprise . Middleware
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Sanjiva Weerawarana, Ph.D.
> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>>> Lean . Enterprise . Middleware
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Pradeep Fernando.
> >>>> http://pradeepfernando.blogspot.com/
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Pradeep Fernando.
> >>> http://pradeepfernando.blogspot.com/
> >>
> >>
> >>
> >>
> >> --
> >> Sameera Jayasoma
> >>
> >> blog: http://sameera.adahas.org
> >> twitter: https://twitter.com/sameerajayasoma
> >> flickr: http://www.flickr.com/photos/sameera-jayasoma/
> >
> >
> >
> >
> > --
> > Pradeep Fernando.
> > http://pradeepfernando.blogspot.com/
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Can this patch be reviewed and committed? I'm worried that unless it
gets applied soon it will become out of date and difficult to commit
later on.
On Tue, Mar 18, 2014 at 2:29 PM, Pradeep Fernando <pr...@gmail.com> wrote:
> apply the patch and add the jclouds dependency to reolve the jclouds CNF.
> After that, build the product named stratos. It contains all the components
> except MB.
>
> we can start a test round with an external MB
>
> hope this helps.. :)
>
> thanks.
>
>
> On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma
> <sa...@gmail.com> wrote:
>>
>> Hi Pradeep,
>>
>> This patch contains so many code changes. Can you please provide an update
>> on where we are on this? What are the remaining items?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>>>
>>> Please someone takeover from here. Unfortunately i have to attend some
>>> other work.
>>>
>>> I have created a JIRA and updated it. Patch attached.
>>>
>>> https://issues.apache.org/jira/browse/STRATOS-523
>>>
>>> thanks.
>>> --Pradeep
>>>
>>>
>>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> Now the server starts fine with as + cc + sm + cep
>>>>
>>>> I managed to workaround the classloading issue, by renaming stub
>>>> packages. Right now im encountering a CNF due to jcloud class
>>>> unavailability. Its a pretty straightforward fix.
>>>>
>>>> [2014-03-17 18:29:20,715] ERROR
>>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
>>>> adding services from bundle :
>>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>>> java.lang.NoClassDefFoundError:
>>>> org/jclouds/rest/ResourceNotFoundException
>>>>
>>>> at java.lang.Class.forName0(Native Method)
>>>> at java.lang.Class.forName(Class.java:247)
>>>> at
>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>>> at
>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>>> at
>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>>> at
>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>>> at
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>>> at
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>> at
>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>>> at
>>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>> at
>>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>>> at
>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>> at
>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>> at
>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>>> at
>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>>> at
>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>>> at
>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>> at
>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>>> at
>>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>>> at
>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>> Caused by: java.lang.ClassNotFoundException:
>>>> org.jclouds.rest.ResourceNotFoundException
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>> at
>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>> ... 49 more
>>>> [2014-03-17 18:29:20,726] INFO
>>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
>>>> service: InstanceCleanupNotificationService {super-tenant}
>>>> [2014-03-17 18:29:21,465] INFO
>>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
>>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>>> [2014-03-17 18:29:21,748] INFO
>>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>>> Permission cache updated for tenant -1234
>>>> [2014-03-17 18:29:21,904] INFO
>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>> Thrift Server started at 10.100.1.80
>>>> [2014-03-17 18:29:21,923] INFO
>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>> Thrift SSL port : 7711
>>>> [2014-03-17 18:29:21,925] INFO
>>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>>> Thrift port : 7611
>>>> [2014-03-17 18:29:21,958] INFO
>>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>> - Successfully deployed the input WSEventLocal adaptor service
>>>> [2014-03-17 18:29:21,962] INFO
>>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>>> - Successfully deployed the output WSEventLocal adaptor service
>>>> [2014-03-17 18:29:21,976] INFO
>>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>> - Successfully deployed the input email event service
>>>> [2014-03-17 18:29:21,983] INFO
>>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>> - Successfully deployed the input WSEvent adaptor service
>>>> [2014-03-17 18:29:21,993] INFO
>>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>>> - Successfully deployed the output Email event adaptor service
>>>> [2014-03-17 18:29:22,002] INFO
>>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>>> - Successfully deployed the output SMS event adaptor service
>>>> [2014-03-17 18:29:22,011] INFO
>>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>>> - Successfully deployed the output WSEvent adaptor service
>>>> [2014-03-17 18:29:22,026] INFO
>>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>>> A SSO Service Provider is registered for : console
>>>> [2014-03-17 18:29:22,060] ERROR
>>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
>>>> element 'TenantRegistrationPage' not found in
>>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>>> [2014-03-17 18:29:22,133] INFO
>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
>>>> : 9443
>>>> [2014-03-17 18:29:22,133] INFO
>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
>>>> : 9763
>>>> [2014-03-17 18:29:22,138] INFO
>>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>>>> servlet write/read
>>>> [2014-03-17 18:29:22,154] INFO
>>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>>>> servlet write/read
>>>> [2014-03-17 18:29:22,193] INFO
>>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
>>>> starting in STANDALONE mode...
>>>> [2014-03-17 18:29:22,202] INFO
>>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
>>>> config properties into System properties
>>>> [2014-03-17 18:29:22,225] INFO
>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>>> Topology receiver thread started
>>>> [2014-03-17 18:29:22,226] INFO
>>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>>> - Stratos Manager topology receiver thread started
>>>> [2014-03-17 18:29:22,231] INFO
>>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
>>>> management server component is activated
>>>> [2014-03-17 18:29:22,255] INFO
>>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>> [2014-03-17 18:29:22,275] INFO
>>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>>> [2014-03-17 18:29:22,275] INFO
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
>>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>>> [2014-03-17 18:29:22,275] INFO
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>>>> Carbon started in 55 sec
>>>> [2014-03-17 18:29:22,430] INFO
>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL :
>>>> https://10.100.1.80:9443/carbon/
>>>> [2014-03-17 18:29:22,521] INFO
>>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
>>>> providers successfully registered.
>>>> [2014-03-17 18:29:22,522] INFO
>>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
>>>> PLAIN
>>>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
>>>> Unable to find resource qpidversion.properties from classloader
>>>>
>>>>
>>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>
>>>> wrote:
>>>>>
>>>>> Hi Pradeep,
>>>>>
>>>>>
>>>>>
>>>>> I *think* I am interested in this topic and am new to this domain, but
>>>>> from the archives, I'm not 100% of the original goals of this work.
>>>>>
>>>>>
>>>>>
>>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of
>>>>> your work: do we still use the same CLIs to start the processes or what? I
>>>>> see some mention of profiles and pre-built VMs, but am unclear how they
>>>>> relate to this.
>>>>>
>>>>>
>>>>>
>>>>> Can you clarify please? Is there a JIRA/spec for this feature I can
>>>>> read?
>>>>>
>>>>>
>>>>>
>>>>> Thanks, Shaheed
>>>>>
>>>>>
>>>>>
>>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>>
>>>>> Interesting ... it would be cool to combine these with something like
>>>>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>>>>> like rPath is gone - what's the way people build custom images now? Or is
>>>>> that gone with just more memory and more disk being normal??
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Sanjiva,
>>>>>
>>>>> Vagrant works on top of an existing image (box). There are plenty of
>>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>>>>> the disk size is a little small to be useful. Opscode also provide some
>>>>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>>>>> the packer definitions from opscode and modify them to build your own box
>>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>>
>>>>> Many thanks,
>>>>>
>>>>> Chris
>>>>>
>>>>> ---
>>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>>> [2] https://github.com/opscode/bento
>>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>>> [4] http://packer.io
>>>>>
>>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>>
>>>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>>>>> well!
>>>>>
>>>>>
>>>>> I'm not familiar with vagrant - just checking it out. Does it build a
>>>>> VM image or does it set up the environment to run the image?
>>>>>
>>>>>
>>>>> Sanjiva.
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Sanjiva,
>>>>>
>>>>> For VM images, vagrant makes life very easy for users; setting up
>>>>> disks, setting up network cards, setting up memory, configuring guest proxy
>>>>> settings, running provisioning scripts, etc.
>>>>>
>>>>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>>>>> here [1]. It isn't ready for general use yet, but I'm making good progress.
>>>>> Although my scripts are buggy, with a few commands I can checkout, build and
>>>>> provision a cloudstack developer environment. I am now working on the
>>>>> scripts to do the same for Stratos.
>>>>>
>>>>> Initially, the memory requirements will be high on my environment, but
>>>>> for me the first goal is automation, the next goal will be efficiency.
>>>>>
>>>>> Many thanks,
>>>>> Chris
>>>>>
>>>>> ---
>>>>> [1] https://github.com/snowch/devcloud-script
>>>>>
>>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>>
>>>>> I think right now we need to focus on getting a single trivial server
>>>>> mechanism to be able to run Stratos without too much of stuff having to be
>>>>> set up. I'd love to see two developer distros:
>>>>>
>>>>>
>>>>> - a VM image that has everything in it and runs in under 4GB with
>>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server to
>>>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon stuff
>>>>> HAS to run in one server - else its a bug in those products .. so the
>>>>> decision should not be based on ability to run in one JVM but rather just
>>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>>>> we're nearly there for it.
>>>>>
>>>>>
>>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>>>> to jClouds that spins up Docker images as processes and there's one JVM that
>>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
>>>>> to a Docker image registry from which the images are booted up and run
>>>>> (obviously a local registry will do better). We don't have this no-IaaS-IaaS
>>>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard to make
>>>>> it work).
>>>>>
>>>>>
>>>>> For production deployments obviously this one server stuff is nonsense
>>>>> .. so we need to have full decoupled distributed execution. For that we
>>>>> should ship puppet scripts to get them up and running plus maybe Boto
>>>>> scripts for someone to get it all up on EC2 with one command. Again its
>>>>> totally fine to use whatever broker here and whatever other pluggable
>>>>> components people want to use (and we need to make sure all the parts are
>>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>>>
>>>>>
>>>>> Makes sense?
>>>>>
>>>>>
>>>>> Sanjiva.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Chris,
>>>>>
>>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>
>>>>> Thanks
>>>>>
>>>>> --Pradeep
>>>>> sent from my phone
>>>>>
>>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>>
>>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>>> view on that :(
>>>>>
>>>>> One thing I'm wondering though is how much memory will be saved if we
>>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>
>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>> <pr...@gmail.com> wrote:
>>>>> > btw,
>>>>> >
>>>>> > Now im working on MB and CEP bits.
>>>>> >
>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>>> > However,
>>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>>> > profile that has all) makes sense.
>>>>> >
>>>>> > WDYT?
>>>>> >
>>>>> > Are we all on same page..
>>>>> >
>>>>> > thanks
>>>>> >
>>>>> >
>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>>> > wrote:
>>>>> >>
>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>>> >> findings!
>>>>> >>
>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>> >> <pr...@gmail.com>
>>>>> >> wrote:
>>>>> >> > Hi Guys,
>>>>> >> >
>>>>> >> > I started on the $subject. This thread is to track the progress..
>>>>> >> >
>>>>> >> > thanks,
>>>>> >> >
>>>>> >> >
>>>>> >> > --
>>>>> >> > Pradeep Fernando.
>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>> >> http://lnkd.in/cw5k69
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Pradeep Fernando.
>>>>> > http://pradeepfernando.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>> http://lnkd.in/cw5k69
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Sanjiva Weerawarana, Ph.D.
>>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Sanjiva Weerawarana, Ph.D.
>>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Sanjiva Weerawarana, Ph.D.
>>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Pradeep Fernando.
>>>> http://pradeepfernando.blogspot.com/
>>>
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>>
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
apply the patch and add the jclouds dependency to reolve the jclouds CNF.
After that, build the product named stratos. It contains all the components
except MB.
we can start a test round with an external MB
hope this helps.. :)
thanks.
On Tue, Mar 18, 2014 at 5:32 PM, Sameera Jayasoma <
sameera.madushan@gmail.com> wrote:
> Hi Pradeep,
>
> This patch contains so many code changes. Can you please provide an update
> on where we are on this? What are the remaining items?
>
> Thanks,
> Sameera.
>
>
> On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Please someone takeover from here. Unfortunately i have to attend some
>> other work.
>>
>> I have created a JIRA and updated it. Patch attached.
>>
>> https://issues.apache.org/jira/browse/STRATOS-523
>>
>> thanks.
>> --Pradeep
>>
>>
>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> Hi Guys,
>>>
>>> Now the server starts fine with as + cc + sm + cep
>>>
>>> I managed to workaround the classloading issue, by renaming stub
>>> packages. Right now im encountering a CNF due to jcloud class
>>> unavailability. Its a pretty straightforward fix.
>>>
>>> [2014-03-17 18:29:20,715] ERROR
>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
>>> adding services from bundle :
>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>> java.lang.NoClassDefFoundError:
>>> org/jclouds/rest/ResourceNotFoundException
>>>
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:247)
>>> at
>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>> at
>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>> at
>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>> at
>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>> at
>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>> at
>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>> at
>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>> at
>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> at
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>> at
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:662)
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.jclouds.rest.ResourceNotFoundException
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>> ... 49 more
>>> [2014-03-17 18:29:20,726] INFO
>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
>>> service: InstanceCleanupNotificationService {super-tenant}
>>> [2014-03-17 18:29:21,465] INFO
>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>> [2014-03-17 18:29:21,748] INFO
>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>> Permission cache updated for tenant -1234
>>> [2014-03-17 18:29:21,904] INFO
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> Thrift Server started at 10.100.1.80
>>> [2014-03-17 18:29:21,923] INFO
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> Thrift SSL port : 7711
>>> [2014-03-17 18:29:21,925] INFO
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> Thrift port : 7611
>>> [2014-03-17 18:29:21,958] INFO
>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>> - Successfully deployed the input WSEventLocal adaptor service
>>> [2014-03-17 18:29:21,962] INFO
>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>> - Successfully deployed the output WSEventLocal adaptor service
>>> [2014-03-17 18:29:21,976] INFO
>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>> - Successfully deployed the input email event service
>>> [2014-03-17 18:29:21,983] INFO
>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>> - Successfully deployed the input WSEvent adaptor service
>>> [2014-03-17 18:29:21,993] INFO
>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>> - Successfully deployed the output Email event adaptor service
>>> [2014-03-17 18:29:22,002] INFO
>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>> - Successfully deployed the output SMS event adaptor service
>>> [2014-03-17 18:29:22,011] INFO
>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>> - Successfully deployed the output WSEvent adaptor service
>>> [2014-03-17 18:29:22,026] INFO
>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager}
>>> - A SSO Service Provider is registered for : console
>>> [2014-03-17 18:29:22,060] ERROR
>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
>>> element 'TenantRegistrationPage' not found in
>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>> [2014-03-17 18:29:22,133] INFO
>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
>>> port : 9443
>>> [2014-03-17 18:29:22,133] INFO
>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>> port : 9763
>>> [2014-03-17 18:29:22,138] INFO
>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>>> servlet write/read
>>> [2014-03-17 18:29:22,154] INFO
>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>>> servlet write/read
>>> [2014-03-17 18:29:22,193] INFO
>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
>>> starting in STANDALONE mode...
>>> [2014-03-17 18:29:22,202] INFO
>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
>>> config properties into System properties
>>> [2014-03-17 18:29:22,225] INFO
>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>> Topology receiver thread started
>>> [2014-03-17 18:29:22,226] INFO
>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>> - Stratos Manager topology receiver thread started
>>> [2014-03-17 18:29:22,231] INFO
>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
>>> management server component is activated
>>> [2014-03-17 18:29:22,255] INFO
>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>> [2014-03-17 18:29:22,275] INFO
>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>> [2014-03-17 18:29:22,275] INFO
>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>> Server : Apache Stratos Controller-4.0.0-SNAPSHOT
>>> [2014-03-17 18:29:22,275] INFO
>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>>> Carbon started in 55 sec
>>> [2014-03-17 18:29:22,430] INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
>>> : https://10.100.1.80:9443/carbon/
>>> [2014-03-17 18:29:22,521] INFO
>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
>>> providers successfully registered.
>>> [2014-03-17 18:29:22,522] INFO
>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
>>> PLAIN
>>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties}
>>> - Unable to find resource qpidversion.properties from classloader
>>>
>>>
>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>wrote:
>>>
>>>> Hi Pradeep,
>>>>
>>>>
>>>>
>>>> I *think* I am interested in this topic and am new to this domain, but
>>>> from the archives, I'm not 100% of the original goals of this work.
>>>>
>>>>
>>>>
>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of
>>>> your work: do we still use the same CLIs to start the processes or what? I
>>>> see some mention of profiles and pre-built VMs, but am unclear how they
>>>> relate to this.
>>>>
>>>>
>>>>
>>>> Can you clarify please? Is there a JIRA/spec for this feature I can
>>>> read?
>>>>
>>>>
>>>>
>>>> Thanks, Shaheed
>>>>
>>>>
>>>>
>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>
>>>> Interesting ... it would be cool to combine these with something like
>>>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>>>> like rPath is gone - what's the way people build custom images now? Or is
>>>> that gone with just more memory and more disk being normal??
>>>>
>>>>
>>>>
>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Sanjiva,
>>>>
>>>> Vagrant works on top of an existing image (box). There are plenty of
>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>>>> the disk size is a little small to be useful. Opscode also provide some
>>>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>>>> the packer definitions from opscode and modify them to build your own box
>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>
>>>> Many thanks,
>>>>
>>>> Chris
>>>>
>>>> ---
>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>> [2] https://github.com/opscode/bento
>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>> [4] http://packer.io
>>>>
>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>
>>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>>>> well!
>>>>
>>>>
>>>> I'm not familiar with vagrant - just checking it out. Does it build a
>>>> VM image or does it set up the environment to run the image?
>>>>
>>>>
>>>> Sanjiva.
>>>>
>>>>
>>>>
>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Sanjiva,
>>>>
>>>> For VM images, vagrant makes life very easy for users; setting up
>>>> disks, setting up network cards, setting up memory, configuring guest proxy
>>>> settings, running provisioning scripts, etc.
>>>>
>>>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>>>> here [1]. It isn't ready for general use yet, but I'm making good
>>>> progress. Although my scripts are buggy, with a few commands I can
>>>> checkout, build and provision a cloudstack developer environment. I am now
>>>> working on the scripts to do the same for Stratos.
>>>>
>>>> Initially, the memory requirements will be high on my environment, but
>>>> for me the first goal is automation, the next goal will be efficiency.
>>>>
>>>> Many thanks,
>>>> Chris
>>>>
>>>> ---
>>>> [1] https://github.com/snowch/devcloud-script
>>>>
>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>
>>>> I think right now we need to focus on getting a single trivial server
>>>> mechanism to be able to run Stratos without too much of stuff having to be
>>>> set up. I'd love to see two developer distros:
>>>>
>>>>
>>>> - a VM image that has everything in it and runs in under 4GB with
>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>>>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>>>> stuff HAS to run in one server - else its a bug in those products .. so the
>>>> decision should not be based on ability to run in one JVM but rather just
>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>>> we're nearly there for it.
>>>>
>>>>
>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>>> to jClouds that spins up Docker images as processes and there's one JVM
>>>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>>>> URL to a Docker image registry from which the images are booted up and run
>>>> (obviously a local registry will do better). We don't have this
>>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>>>> hard to make it work).
>>>>
>>>>
>>>> For production deployments obviously this one server stuff is nonsense
>>>> .. so we need to have full decoupled distributed execution. For that we
>>>> should ship puppet scripts to get them up and running plus maybe Boto
>>>> scripts for someone to get it all up on EC2 with one command. Again its
>>>> totally fine to use whatever broker here and whatever other pluggable
>>>> components people want to use (and we need to make sure all the parts are
>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>>
>>>>
>>>> Makes sense?
>>>>
>>>>
>>>> Sanjiva.
>>>>
>>>>
>>>>
>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Chris,
>>>>
>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>
>>>> Thanks
>>>>
>>>> --Pradeep
>>>> sent from my phone
>>>>
>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>
>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>> view on that :(
>>>>
>>>> One thing I'm wondering though is how much memory will be saved if we
>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>
>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>>> wrote:
>>>> > btw,
>>>> >
>>>> > Now im working on MB and CEP bits.
>>>> >
>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>> However,
>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>> > profile that has all) makes sense.
>>>> >
>>>> > WDYT?
>>>> >
>>>> > Are we all on same page..
>>>> >
>>>> > thanks
>>>> >
>>>> >
>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>> findings!
>>>> >>
>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>>> pradeepfn@gmail.com>
>>>> >> wrote:
>>>> >> > Hi Guys,
>>>> >> >
>>>> >> > I started on the $subject. This thread is to track the progress..
>>>> >> >
>>>> >> > thanks,
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Pradeep Fernando.
>>>> >> > http://pradeepfernando.blogspot.com/
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>> >> http://lnkd.in/cw5k69
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Pradeep Fernando.
>>>> > http://pradeepfernando.blogspot.com/
>>>>
>>>>
>>>>
>>>> --
>>>> Check out my professional profile and connect with me on LinkedIn.
>>>> http://lnkd.in/cw5k69
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Sameera Jayasoma
>
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Sameera Jayasoma <sa...@gmail.com>.
Hi Pradeep,
This patch contains so many code changes. Can you please provide an update
on where we are on this? What are the remaining items?
Thanks,
Sameera.
On Mon, Mar 17, 2014 at 11:47 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Please someone takeover from here. Unfortunately i have to attend some
> other work.
>
> I have created a JIRA and updated it. Patch attached.
>
> https://issues.apache.org/jira/browse/STRATOS-523
>
> thanks.
> --Pradeep
>
>
> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Hi Guys,
>>
>> Now the server starts fine with as + cc + sm + cep
>>
>> I managed to workaround the classloading issue, by renaming stub
>> packages. Right now im encountering a CNF due to jcloud class
>> unavailability. Its a pretty straightforward fix.
>>
>> [2014-03-17 18:29:20,715] ERROR
>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
>> adding services from bundle :
>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>> java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
>>
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:247)
>> at
>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>> at
>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>> at
>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>> at
>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>> at
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>> at
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>> Caused by: java.lang.ClassNotFoundException:
>> org.jclouds.rest.ResourceNotFoundException
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> ... 49 more
>> [2014-03-17 18:29:20,726] INFO
>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
>> service: InstanceCleanupNotificationService {super-tenant}
>> [2014-03-17 18:29:21,465] INFO
>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>> [2014-03-17 18:29:21,748] INFO
>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>> Permission cache updated for tenant -1234
>> [2014-03-17 18:29:21,904] INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> Thrift Server started at 10.100.1.80
>> [2014-03-17 18:29:21,923] INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> Thrift SSL port : 7711
>> [2014-03-17 18:29:21,925] INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> Thrift port : 7611
>> [2014-03-17 18:29:21,958] INFO
>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> - Successfully deployed the input WSEventLocal adaptor service
>> [2014-03-17 18:29:21,962] INFO
>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> - Successfully deployed the output WSEventLocal adaptor service
>> [2014-03-17 18:29:21,976] INFO
>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> - Successfully deployed the input email event service
>> [2014-03-17 18:29:21,983] INFO
>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> - Successfully deployed the input WSEvent adaptor service
>> [2014-03-17 18:29:21,993] INFO
>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> - Successfully deployed the output Email event adaptor service
>> [2014-03-17 18:29:22,002] INFO
>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>> - Successfully deployed the output SMS event adaptor service
>> [2014-03-17 18:29:22,011] INFO
>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> - Successfully deployed the output WSEvent adaptor service
>> [2014-03-17 18:29:22,026] INFO
>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager}
>> - A SSO Service Provider is registered for : console
>> [2014-03-17 18:29:22,060] ERROR
>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
>> element 'TenantRegistrationPage' not found in
>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>> [2014-03-17 18:29:22,133] INFO
>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
>> port : 9443
>> [2014-03-17 18:29:22,133] INFO
>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>> port : 9763
>> [2014-03-17 18:29:22,138] INFO
>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>> servlet write/read
>> [2014-03-17 18:29:22,154] INFO
>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>> servlet write/read
>> [2014-03-17 18:29:22,193] INFO
>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
>> starting in STANDALONE mode...
>> [2014-03-17 18:29:22,202] INFO
>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
>> config properties into System properties
>> [2014-03-17 18:29:22,225] INFO
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> Topology receiver thread started
>> [2014-03-17 18:29:22,226] INFO
>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>> - Stratos Manager topology receiver thread started
>> [2014-03-17 18:29:22,231] INFO
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
>> management server component is activated
>> [2014-03-17 18:29:22,255] INFO
>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>> [2014-03-17 18:29:22,275] INFO
>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>> [2014-03-17 18:29:22,275] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> Server : Apache Stratos Controller-4.0.0-SNAPSHOT
>> [2014-03-17 18:29:22,275] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>> Carbon started in 55 sec
>> [2014-03-17 18:29:22,430] INFO
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
>> : https://10.100.1.80:9443/carbon/
>> [2014-03-17 18:29:22,521] INFO
>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
>> providers successfully registered.
>> [2014-03-17 18:29:22,522] INFO
>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
>> PLAIN
>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
>> Unable to find resource qpidversion.properties from classloader
>>
>>
>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>wrote:
>>
>>> Hi Pradeep,
>>>
>>>
>>>
>>> I *think* I am interested in this topic and am new to this domain, but
>>> from the archives, I'm not 100% of the original goals of this work.
>>>
>>>
>>>
>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of your
>>> work: do we still use the same CLIs to start the processes or what? I see
>>> some mention of profiles and pre-built VMs, but am unclear how they relate
>>> to this.
>>>
>>>
>>>
>>> Can you clarify please? Is there a JIRA/spec for this feature I can read?
>>>
>>>
>>>
>>> Thanks, Shaheed
>>>
>>>
>>>
>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>
>>> Interesting ... it would be cool to combine these with something like
>>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>>> like rPath is gone - what's the way people build custom images now? Or is
>>> that gone with just more memory and more disk being normal??
>>>
>>>
>>>
>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>>
>>> Hi Sanjiva,
>>>
>>> Vagrant works on top of an existing image (box). There are plenty of
>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>>> the disk size is a little small to be useful. Opscode also provide some
>>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>>> the packer definitions from opscode and modify them to build your own box
>>> from scratch [3]. Packer is definitely worth a look too.
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>> ---
>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>> [2] https://github.com/opscode/bento
>>> [3] https://github.com/opscode/bento/tree/master/packer
>>> [4] http://packer.io
>>>
>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>>> well!
>>>
>>>
>>> I'm not familiar with vagrant - just checking it out. Does it build a VM
>>> image or does it set up the environment to run the image?
>>>
>>>
>>> Sanjiva.
>>>
>>>
>>>
>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>>
>>> Hi Sanjiva,
>>>
>>> For VM images, vagrant makes life very easy for users; setting up disks,
>>> setting up network cards, setting up memory, configuring guest proxy
>>> settings, running provisioning scripts, etc.
>>>
>>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>>> here [1]. It isn't ready for general use yet, but I'm making good
>>> progress. Although my scripts are buggy, with a few commands I can
>>> checkout, build and provision a cloudstack developer environment. I am now
>>> working on the scripts to do the same for Stratos.
>>>
>>> Initially, the memory requirements will be high on my environment, but
>>> for me the first goal is automation, the next goal will be efficiency.
>>>
>>> Many thanks,
>>> Chris
>>>
>>> ---
>>> [1] https://github.com/snowch/devcloud-script
>>>
>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>> I think right now we need to focus on getting a single trivial server
>>> mechanism to be able to run Stratos without too much of stuff having to be
>>> set up. I'd love to see two developer distros:
>>>
>>>
>>> - a VM image that has everything in it and runs in under 4GB with
>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>>> stuff HAS to run in one server - else its a bug in those products .. so the
>>> decision should not be based on ability to run in one JVM but rather just
>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>> we're nearly there for it.
>>>
>>>
>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>> to jClouds that spins up Docker images as processes and there's one JVM
>>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>>> URL to a Docker image registry from which the images are booted up and run
>>> (obviously a local registry will do better). We don't have this
>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>>> hard to make it work).
>>>
>>>
>>> For production deployments obviously this one server stuff is nonsense
>>> .. so we need to have full decoupled distributed execution. For that we
>>> should ship puppet scripts to get them up and running plus maybe Boto
>>> scripts for someone to get it all up on EC2 with one command. Again its
>>> totally fine to use whatever broker here and whatever other pluggable
>>> components people want to use (and we need to make sure all the parts are
>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>
>>>
>>> Makes sense?
>>>
>>>
>>> Sanjiva.
>>>
>>>
>>>
>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>>
>>> Hi Chris,
>>>
>>> Yes good point. Other day Azeez did the same suggestion.
>>>
>>> Thanks
>>>
>>> --Pradeep
>>> sent from my phone
>>>
>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>
>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>> view on that :(
>>>
>>> One thing I'm wondering though is how much memory will be saved if we
>>> use RabbitMQ (or another MQ) instead of MB?
>>>
>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>> > btw,
>>> >
>>> > Now im working on MB and CEP bits.
>>> >
>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>> However,
>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>> > profile that has all) makes sense.
>>> >
>>> > WDYT?
>>> >
>>> > Are we all on same page..
>>> >
>>> > thanks
>>> >
>>> >
>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>> >>
>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>> findings!
>>> >>
>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>> pradeepfn@gmail.com>
>>> >> wrote:
>>> >> > Hi Guys,
>>> >> >
>>> >> > I started on the $subject. This thread is to track the progress..
>>> >> >
>>> >> > thanks,
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Pradeep Fernando.
>>> >> > http://pradeepfernando.blogspot.com/
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Check out my professional profile and connect with me on LinkedIn.
>>> >> http://lnkd.in/cw5k69
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Pradeep Fernando.
>>> > http://pradeepfernando.blogspot.com/
>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Sameera Jayasoma
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
Please someone takeover from here. Unfortunately i have to attend some
other work.
I have created a JIRA and updated it. Patch attached.
https://issues.apache.org/jira/browse/STRATOS-523
thanks.
--Pradeep
On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Hi Guys,
>
> Now the server starts fine with as + cc + sm + cep
>
> I managed to workaround the classloading issue, by renaming stub packages.
> Right now im encountering a CNF due to jcloud class unavailability. Its a
> pretty straightforward fix.
>
> [2014-03-17 18:29:20,715] ERROR
> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> adding services from bundle :
> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
>
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> at
> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException:
> org.jclouds.rest.ResourceNotFoundException
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 49 more
> [2014-03-17 18:29:20,726] INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
> service: InstanceCleanupNotificationService {super-tenant}
> [2014-03-17 18:29:21,465] INFO
> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
> [2014-03-17 18:29:21,748] INFO
> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> Permission cache updated for tenant -1234
> [2014-03-17 18:29:21,904] INFO
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> Thrift Server started at 10.100.1.80
> [2014-03-17 18:29:21,923] INFO
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> Thrift SSL port : 7711
> [2014-03-17 18:29:21,925] INFO
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> Thrift port : 7611
> [2014-03-17 18:29:21,958] INFO
> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> - Successfully deployed the input WSEventLocal adaptor service
> [2014-03-17 18:29:21,962] INFO
> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> - Successfully deployed the output WSEventLocal adaptor service
> [2014-03-17 18:29:21,976] INFO
> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> - Successfully deployed the input email event service
> [2014-03-17 18:29:21,983] INFO
> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> - Successfully deployed the input WSEvent adaptor service
> [2014-03-17 18:29:21,993] INFO
> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> - Successfully deployed the output Email event adaptor service
> [2014-03-17 18:29:22,002] INFO
> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
> - Successfully deployed the output SMS event adaptor service
> [2014-03-17 18:29:22,011] INFO
> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> - Successfully deployed the output WSEvent adaptor service
> [2014-03-17 18:29:22,026] INFO
> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager}
> - A SSO Service Provider is registered for : console
> [2014-03-17 18:29:22,060] ERROR
> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
> element 'TenantRegistrationPage' not found in
> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
> [2014-03-17 18:29:22,133] INFO
> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
> port : 9443
> [2014-03-17 18:29:22,133] INFO
> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
> port : 9763
> [2014-03-17 18:29:22,138] INFO
> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
> servlet write/read
> [2014-03-17 18:29:22,154] INFO
> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
> servlet write/read
> [2014-03-17 18:29:22,193] INFO
> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
> starting in STANDALONE mode...
> [2014-03-17 18:29:22,202] INFO
> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
> config properties into System properties
> [2014-03-17 18:29:22,225] INFO
> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> Topology receiver thread started
> [2014-03-17 18:29:22,226] INFO
> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
> - Stratos Manager topology receiver thread started
> [2014-03-17 18:29:22,231] INFO
> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
> management server component is activated
> [2014-03-17 18:29:22,255] INFO
> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
> [2014-03-17 18:29:22,275] INFO
> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
> [2014-03-17 18:29:22,275] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> Server : Apache Stratos Controller-4.0.0-SNAPSHOT
> [2014-03-17 18:29:22,275] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
> Carbon started in 55 sec
> [2014-03-17 18:29:22,430] INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
> : https://10.100.1.80:9443/carbon/
> [2014-03-17 18:29:22,521] INFO
> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
> providers successfully registered.
> [2014-03-17 18:29:22,522] INFO
> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
> PLAIN
> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
> Unable to find resource qpidversion.properties from classloader
>
>
> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com> wrote:
>
>> Hi Pradeep,
>>
>>
>>
>> I *think* I am interested in this topic and am new to this domain, but
>> from the archives, I'm not 100% of the original goals of this work.
>>
>>
>>
>> Also, if the idea is to ship in 4.0.0, how can we take advantage of your
>> work: do we still use the same CLIs to start the processes or what? I see
>> some mention of profiles and pre-built VMs, but am unclear how they relate
>> to this.
>>
>>
>>
>> Can you clarify please? Is there a JIRA/spec for this feature I can read?
>>
>>
>>
>> Thanks, Shaheed
>>
>>
>>
>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>
>> Interesting ... it would be cool to combine these with something like
>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>> like rPath is gone - what's the way people build custom images now? Or is
>> that gone with just more memory and more disk being normal??
>>
>>
>>
>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> Vagrant works on top of an existing image (box). There are plenty of
>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>> the disk size is a little small to be useful. Opscode also provide some
>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>> the packer definitions from opscode and modify them to build your own box
>> from scratch [3]. Packer is definitely worth a look too.
>>
>> Many thanks,
>>
>> Chris
>>
>> ---
>> [1] http://cloud-images.ubuntu.com/vagrant/
>> [2] https://github.com/opscode/bento
>> [3] https://github.com/opscode/bento/tree/master/packer
>> [4] http://packer.io
>>
>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>
>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>> well!
>>
>>
>> I'm not familiar with vagrant - just checking it out. Does it build a VM
>> image or does it set up the environment to run the image?
>>
>>
>> Sanjiva.
>>
>>
>>
>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> For VM images, vagrant makes life very easy for users; setting up disks,
>> setting up network cards, setting up memory, configuring guest proxy
>> settings, running provisioning scripts, etc.
>>
>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>> here [1]. It isn't ready for general use yet, but I'm making good
>> progress. Although my scripts are buggy, with a few commands I can
>> checkout, build and provision a cloudstack developer environment. I am now
>> working on the scripts to do the same for Stratos.
>>
>> Initially, the memory requirements will be high on my environment, but
>> for me the first goal is automation, the next goal will be efficiency.
>>
>> Many thanks,
>> Chris
>>
>> ---
>> [1] https://github.com/snowch/devcloud-script
>>
>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>
>> I think right now we need to focus on getting a single trivial server
>> mechanism to be able to run Stratos without too much of stuff having to be
>> set up. I'd love to see two developer distros:
>>
>>
>> - a VM image that has everything in it and runs in under 4GB with
>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>> stuff HAS to run in one server - else its a bug in those products .. so the
>> decision should not be based on ability to run in one JVM but rather just
>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>> we're nearly there for it.
>>
>>
>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>> to jClouds that spins up Docker images as processes and there's one JVM
>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>> URL to a Docker image registry from which the images are booted up and run
>> (obviously a local registry will do better). We don't have this
>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>> hard to make it work).
>>
>>
>> For production deployments obviously this one server stuff is nonsense ..
>> so we need to have full decoupled distributed execution. For that we should
>> ship puppet scripts to get them up and running plus maybe Boto scripts for
>> someone to get it all up on EC2 with one command. Again its totally fine to
>> use whatever broker here and whatever other pluggable components people
>> want to use (and we need to make sure all the parts are pluggable: load
>> balancers, message broker, the CEP engine, etc.)).
>>
>>
>> Makes sense?
>>
>>
>> Sanjiva.
>>
>>
>>
>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>>
>> Hi Chris,
>>
>> Yes good point. Other day Azeez did the same suggestion.
>>
>> Thanks
>>
>> --Pradeep
>> sent from my phone
>>
>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>
>> Hi Pradeep - I don't know enough about how the profiles work to have a
>> view on that :(
>>
>> One thing I'm wondering though is how much memory will be saved if we
>> use RabbitMQ (or another MQ) instead of MB?
>>
>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > btw,
>> >
>> > Now im working on MB and CEP bits.
>> >
>> > IMHO, we should not create MB and CEP only profiles in stratos. However,
>> > adding MB/CEP features (the ones that we use) to default profile (the
>> > profile that has all) makes sense.
>> >
>> > WDYT?
>> >
>> > Are we all on same page..
>> >
>> > thanks
>> >
>> >
>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>> wrote:
>> >>
>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> findings!
>> >>
>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pradeepfn@gmail.com
>> >
>> >> wrote:
>> >> > Hi Guys,
>> >> >
>> >> > I started on the $subject. This thread is to track the progress..
>> >> >
>> >> > thanks,
>> >> >
>> >> >
>> >> > --
>> >> > Pradeep Fernando.
>> >> > http://pradeepfernando.blogspot.com/
>> >>
>> >>
>> >>
>> >> --
>> >> Check out my professional profile and connect with me on LinkedIn.
>> >> http://lnkd.in/cw5k69
>> >
>> >
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>>
>>
>>
>> --
>>
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>> --
>>
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>> --
>>
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Isuru Perera <is...@wso2.com>.
Yes Chris! It's very simple to install RabbitMQ and use it.
Even for OpenStack installations on Ubuntu, installing RabbitMQ is a single
step. We should try testing Stratos on RabbitMQ.
On Mon, Mar 17, 2014 at 8:25 PM, chris snow <ch...@gmail.com> wrote:
> Is RabbbitMQ the simplest to setup? i.e. just install the OS package
> ("apt-get install rabbitmq-server") and then configure stratos to use
> it?
>
>
> On Mon, Mar 17, 2014 at 1:36 PM, Isuru Perera <is...@wso2.com> wrote:
> > I think running an ActiveMQ or a RabbitMQ along with Stratos single pack
> > would be okay.
> >
> > Integrating MB features to Stratos will bring unnecessary complications.
> > Having MB within CC was one of the limitations to upgrade jclouds
> libraries
> > when we were doing Stratos 3.0.0-incubating release.
> >
> > There is nothing much to configure in Message Broker. IMO we don't need
> to
> > integrate MB into Stratos for now.
> >
> > On Mon, Mar 17, 2014 at 6:35 PM, Pradeep Fernando <pr...@gmail.com>
> > wrote:
> >>
> >> So the remaining bit is MB.
> >>
> >> We need to integrate WSO2 MB or ActiveMQ.
> >>
> >> @Shaheed : will get back to you with answers. :) sorry im bit busy at
> the
> >> moment.
> >>
> >> thanks
> >>
> >>
> >> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>
> >> wrote:
> >>>
> >>> Hi Guys,
> >>>
> >>> Now the server starts fine with as + cc + sm + cep
> >>>
> >>> I managed to workaround the classloading issue, by renaming stub
> >>> packages. Right now im encountering a CNF due to jcloud class
> >>> unavailability. Its a pretty straightforward fix.
> >>>
> >>> [2014-03-17 18:29:20,715] ERROR
> >>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> >>> adding services from bundle :
> >>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> >>> java.lang.NoClassDefFoundError:
> >>> org/jclouds/rest/ResourceNotFoundException
> >>>
> >>> at java.lang.Class.forName0(Native Method)
> >>> at java.lang.Class.forName(Class.java:247)
> >>> at
> >>>
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> >>> at
> >>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> >>> at
> >>>
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> >>> at
> >>>
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> >>> at
> >>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> >>> at
> >>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> >>> at
> >>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> >>> at
> >>>
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> >>> at
> >>>
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> >>> at
> >>>
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>> at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>> at java.lang.reflect.Method.invoke(Method.java:597)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> >>> at
> >>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> >>> at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> >>> at
> >>>
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> >>> at
> >>>
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> >>> at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> >>> at
> >>>
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> >>> at
> >>>
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> >>> at
> >>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> >>> at
> >>>
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> >>> at
> >>>
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> >>> at
> >>>
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> >>> at
> >>>
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> >>> at
> >>>
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> >>> at
> >>>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> >>> at
> >>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> >>> at
> >>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> >>> at
> >>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> >>> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >>> at
> >>>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >>> at
> >>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >>> at java.lang.Thread.run(Thread.java:662)
> >>> Caused by: java.lang.ClassNotFoundException:
> >>> org.jclouds.rest.ResourceNotFoundException
> >>> at
> >>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> >>> at
> >>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> >>> at
> >>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> >>> at
> >>>
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> >>> ... 49 more
> >>> [2014-03-17 18:29:20,726] INFO
> >>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
> Axis2
> >>> service: InstanceCleanupNotificationService {super-tenant}
> >>> [2014-03-17 18:29:21,465] INFO
> >>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
> >>>
> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
> >>> [2014-03-17 18:29:21,748] INFO
> >>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> >>> Permission cache updated for tenant -1234
> >>> [2014-03-17 18:29:21,904] INFO
> >>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>> Thrift Server started at 10.100.1.80
> >>> [2014-03-17 18:29:21,923] INFO
> >>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>> Thrift SSL port : 7711
> >>> [2014-03-17 18:29:21,925] INFO
> >>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>> Thrift port : 7611
> >>> [2014-03-17 18:29:21,958] INFO
> >>>
> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >>> - Successfully deployed the input WSEventLocal adaptor service
> >>> [2014-03-17 18:29:21,962] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >>> - Successfully deployed the output WSEventLocal adaptor service
> >>> [2014-03-17 18:29:21,976] INFO
> >>>
> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >>> - Successfully deployed the input email event service
> >>> [2014-03-17 18:29:21,983] INFO
> >>>
> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >>> - Successfully deployed the input WSEvent adaptor service
> >>> [2014-03-17 18:29:21,993] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >>> - Successfully deployed the output Email event adaptor service
> >>> [2014-03-17 18:29:22,002] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
> >>> - Successfully deployed the output SMS event adaptor service
> >>> [2014-03-17 18:29:22,011] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >>> - Successfully deployed the output WSEvent adaptor service
> >>> [2014-03-17 18:29:22,026] INFO
> >>>
> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
> >>> A SSO Service Provider is registered for : console
> >>> [2014-03-17 18:29:22,060] ERROR
> >>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
> >>> element 'TenantRegistrationPage' not found in
> >>>
> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
> >>> [2014-03-17 18:29:22,133] INFO
> >>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
> port
> >>> : 9443
> >>> [2014-03-17 18:29:22,133] INFO
> >>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
> port
> >>> : 9763
> >>> [2014-03-17 18:29:22,138] INFO
> >>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> selector for
> >>> servlet write/read
> >>> [2014-03-17 18:29:22,154] INFO
> >>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> selector for
> >>> servlet write/read
> >>> [2014-03-17 18:29:22,193] INFO
> >>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
> service
> >>> starting in STANDALONE mode...
> >>> [2014-03-17 18:29:22,202] INFO
> >>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
> >>> config properties into System properties
> >>> [2014-03-17 18:29:22,225] INFO
> >>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> >>> Topology receiver thread started
> >>> [2014-03-17 18:29:22,226] INFO
> >>>
> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
> >>> - Stratos Manager topology receiver thread started
> >>> [2014-03-17 18:29:22,231] INFO
> >>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> ADC
> >>> management server component is activated
> >>> [2014-03-17 18:29:22,255] INFO
> >>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
> >>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
> >>> [2014-03-17 18:29:22,275] INFO
> >>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
> >>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
> >>> [2014-03-17 18:29:22,275] INFO
> >>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> Server
> >>> : Apache Stratos Controller-4.0.0-SNAPSHOT
> >>> [2014-03-17 18:29:22,275] INFO
> >>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> WSO2
> >>> Carbon started in 55 sec
> >>> [2014-03-17 18:29:22,430] INFO
> >>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
> URL :
> >>> https://10.100.1.80:9443/carbon/
> >>> [2014-03-17 18:29:22,521] INFO
> >>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
> SASL
> >>> providers successfully registered.
> >>> [2014-03-17 18:29:22,522] INFO
> >>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
> >>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
> AMQPLAIN
> >>> PLAIN
> >>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties}
> -
> >>> Unable to find resource qpidversion.properties from classloader
> >>>
> >>>
> >>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>
> >>> wrote:
> >>>>
> >>>> Hi Pradeep,
> >>>>
> >>>>
> >>>>
> >>>> I *think* I am interested in this topic and am new to this domain, but
> >>>> from the archives, I'm not 100% of the original goals of this work.
> >>>>
> >>>>
> >>>>
> >>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of
> your
> >>>> work: do we still use the same CLIs to start the processes or what? I
> see
> >>>> some mention of profiles and pre-built VMs, but am unclear how they
> relate
> >>>> to this.
> >>>>
> >>>>
> >>>>
> >>>> Can you clarify please? Is there a JIRA/spec for this feature I can
> >>>> read?
> >>>>
> >>>>
> >>>>
> >>>> Thanks, Shaheed
> >>>>
> >>>>
> >>>>
> >>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
> >>>>
> >>>> Interesting ... it would be cool to combine these with something like
> >>>> rPath to build a minimal Linux image with just the exact bits in it.
> Looks
> >>>> like rPath is gone - what's the way people build custom images now?
> Or is
> >>>> that gone with just more memory and more disk being normal??
> >>>>
> >>>>
> >>>>
> >>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi Sanjiva,
> >>>>
> >>>> Vagrant works on top of an existing image (box). There are plenty of
> >>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
> although
> >>>> the disk size is a little small to be useful. Opscode also provide
> some
> >>>> pretty good boxes [2]. If these still don't meet your needs, you can
> copy
> >>>> the packer definitions from opscode and modify them to build your own
> box
> >>>> from scratch [3]. Packer is definitely worth a look too.
> >>>>
> >>>> Many thanks,
> >>>>
> >>>> Chris
> >>>>
> >>>> ---
> >>>> [1] http://cloud-images.ubuntu.com/vagrant/
> >>>> [2] https://github.com/opscode/bento
> >>>> [3] https://github.com/opscode/bento/tree/master/packer
> >>>> [4] http://packer.io
> >>>>
> >>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >>>>
> >>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
> >>>> well!
> >>>>
> >>>>
> >>>> I'm not familiar with vagrant - just checking it out. Does it build a
> VM
> >>>> image or does it set up the environment to run the image?
> >>>>
> >>>>
> >>>> Sanjiva.
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
> wrote:
> >>>>
> >>>> Hi Sanjiva,
> >>>>
> >>>> For VM images, vagrant makes life very easy for users; setting up
> disks,
> >>>> setting up network cards, setting up memory, configuring guest proxy
> >>>> settings, running provisioning scripts, etc.
> >>>>
> >>>> I am working on a vagrant setup of cloudstack + Stratos. My project
> is
> >>>> here [1]. It isn't ready for general use yet, but I'm making good
> progress.
> >>>> Although my scripts are buggy, with a few commands I can checkout,
> build and
> >>>> provision a cloudstack developer environment. I am now working on the
> >>>> scripts to do the same for Stratos.
> >>>>
> >>>> Initially, the memory requirements will be high on my environment, but
> >>>> for me the first goal is automation, the next goal will be efficiency.
> >>>>
> >>>> Many thanks,
> >>>> Chris
> >>>>
> >>>> ---
> >>>> [1] https://github.com/snowch/devcloud-script
> >>>>
> >>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >>>>
> >>>> I think right now we need to focus on getting a single trivial server
> >>>> mechanism to be able to run Stratos without too much of stuff having
> to be
> >>>> set up. I'd love to see two developer distros:
> >>>>
> >>>>
> >>>> - a VM image that has everything in it and runs in under 4GB with
> >>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon
> server to
> >>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff
> >>>> HAS to run in one server - else its a bug in those products .. so the
> >>>> decision should not be based on ability to run in one JVM but rather
> just
> >>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I
> think
> >>>> we're nearly there for it.
> >>>>
> >>>>
> >>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
> plugin
> >>>> to jClouds that spins up Docker images as processes and there's one
> JVM that
> >>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus
> a URL
> >>>> to a Docker image registry from which the images are booted up and run
> >>>> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS
> >>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard to
> make
> >>>> it work).
> >>>>
> >>>>
> >>>> For production deployments obviously this one server stuff is nonsense
> >>>> .. so we need to have full decoupled distributed execution. For that
> we
> >>>> should ship puppet scripts to get them up and running plus maybe Boto
> >>>> scripts for someone to get it all up on EC2 with one command. Again
> its
> >>>> totally fine to use whatever broker here and whatever other pluggable
> >>>> components people want to use (and we need to make sure all the parts
> are
> >>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
> >>>>
> >>>>
> >>>> Makes sense?
> >>>>
> >>>>
> >>>> Sanjiva.
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <
> pradeepfn@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi Chris,
> >>>>
> >>>> Yes good point. Other day Azeez did the same suggestion.
> >>>>
> >>>> Thanks
> >>>>
> >>>> --Pradeep
> >>>> sent from my phone
> >>>>
> >>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
> >>>>
> >>>> Hi Pradeep - I don't know enough about how the profiles work to have a
> >>>> view on that :(
> >>>>
> >>>> One thing I'm wondering though is how much memory will be saved if we
> >>>> use RabbitMQ (or another MQ) instead of MB?
> >>>>
> >>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
> pradeepfn@gmail.com>
> >>>> wrote:
> >>>> > btw,
> >>>> >
> >>>> > Now im working on MB and CEP bits.
> >>>> >
> >>>> > IMHO, we should not create MB and CEP only profiles in stratos.
> >>>> > However,
> >>>> > adding MB/CEP features (the ones that we use) to default profile
> (the
> >>>> > profile that has all) makes sense.
> >>>> >
> >>>> > WDYT?
> >>>> >
> >>>> > Are we all on same page..
> >>>> >
> >>>> > thanks
> >>>> >
> >>>> >
> >>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
> >>>> > wrote:
> >>>> >>
> >>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
> >>>> >> findings!
> >>>> >>
> >>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
> >>>> >> <pr...@gmail.com>
> >>>> >> wrote:
> >>>> >> > Hi Guys,
> >>>> >> >
> >>>> >> > I started on the $subject. This thread is to track the progress..
> >>>> >> >
> >>>> >> > thanks,
> >>>> >> >
> >>>> >> >
> >>>> >> > --
> >>>> >> > Pradeep Fernando.
> >>>> >> > http://pradeepfernando.blogspot.com/
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >> --
> >>>> >> Check out my professional profile and connect with me on LinkedIn.
> >>>> >> http://lnkd.in/cw5k69
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Pradeep Fernando.
> >>>> > http://pradeepfernando.blogspot.com/
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Check out my professional profile and connect with me on LinkedIn.
> >>>> http://lnkd.in/cw5k69
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Sanjiva Weerawarana, Ph.D.
> >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>> Lean . Enterprise . Middleware
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Sanjiva Weerawarana, Ph.D.
> >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>> Lean . Enterprise . Middleware
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Sanjiva Weerawarana, Ph.D.
> >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>> Lean . Enterprise . Middleware
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Pradeep Fernando.
> >>> http://pradeepfernando.blogspot.com/
> >>
> >>
> >>
> >>
> >> --
> >> Pradeep Fernando.
> >> http://pradeepfernando.blogspot.com/
> >
> >
> >
> >
> > --
> > Isuru Perera
> > Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> >
> > Lean . Enterprise . Middleware
> >
> > about.me/chrishantha
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
+1 for RabbitMQ. Seems like it's non-Java and hopefully lightweight.
On Mon, Mar 17, 2014 at 10:55 AM, chris snow <ch...@gmail.com> wrote:
> Is RabbbitMQ the simplest to setup? i.e. just install the OS package
> ("apt-get install rabbitmq-server") and then configure stratos to use
> it?
>
>
> On Mon, Mar 17, 2014 at 1:36 PM, Isuru Perera <is...@wso2.com> wrote:
> > I think running an ActiveMQ or a RabbitMQ along with Stratos single pack
> > would be okay.
> >
> > Integrating MB features to Stratos will bring unnecessary complications.
> > Having MB within CC was one of the limitations to upgrade jclouds
> libraries
> > when we were doing Stratos 3.0.0-incubating release.
> >
> > There is nothing much to configure in Message Broker. IMO we don't need
> to
> > integrate MB into Stratos for now.
> >
> > On Mon, Mar 17, 2014 at 6:35 PM, Pradeep Fernando <pr...@gmail.com>
> > wrote:
> >>
> >> So the remaining bit is MB.
> >>
> >> We need to integrate WSO2 MB or ActiveMQ.
> >>
> >> @Shaheed : will get back to you with answers. :) sorry im bit busy at
> the
> >> moment.
> >>
> >> thanks
> >>
> >>
> >> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>
> >> wrote:
> >>>
> >>> Hi Guys,
> >>>
> >>> Now the server starts fine with as + cc + sm + cep
> >>>
> >>> I managed to workaround the classloading issue, by renaming stub
> >>> packages. Right now im encountering a CNF due to jcloud class
> >>> unavailability. Its a pretty straightforward fix.
> >>>
> >>> [2014-03-17 18:29:20,715] ERROR
> >>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> >>> adding services from bundle :
> >>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> >>> java.lang.NoClassDefFoundError:
> >>> org/jclouds/rest/ResourceNotFoundException
> >>>
> >>> at java.lang.Class.forName0(Native Method)
> >>> at java.lang.Class.forName(Class.java:247)
> >>> at
> >>>
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> >>> at
> >>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> >>> at
> >>>
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> >>> at
> >>>
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> >>> at
> >>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> >>> at
> >>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> >>> at
> >>>
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> >>> at
> >>>
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> >>> at
> >>>
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> >>> at
> >>>
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>> at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>> at java.lang.reflect.Method.invoke(Method.java:597)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> >>> at
> >>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> >>> at
> >>>
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> >>> at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> >>> at
> >>>
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> >>> at
> >>>
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> >>> at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> >>> at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> >>> at
> >>>
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> >>> at
> >>>
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> >>> at
> >>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> >>> at
> >>>
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> >>> at
> >>>
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> >>> at
> >>>
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> >>> at
> >>>
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> >>> at
> >>>
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> >>> at
> >>>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> >>> at
> >>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> >>> at
> >>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> >>> at
> >>>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> >>> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >>> at
> >>>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >>> at
> >>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >>> at java.lang.Thread.run(Thread.java:662)
> >>> Caused by: java.lang.ClassNotFoundException:
> >>> org.jclouds.rest.ResourceNotFoundException
> >>> at
> >>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> >>> at
> >>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> >>> at
> >>>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> >>> at
> >>>
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> >>> ... 49 more
> >>> [2014-03-17 18:29:20,726] INFO
> >>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying
> Axis2
> >>> service: InstanceCleanupNotificationService {super-tenant}
> >>> [2014-03-17 18:29:21,465] INFO
> >>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
> >>>
> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
> >>> [2014-03-17 18:29:21,748] INFO
> >>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> >>> Permission cache updated for tenant -1234
> >>> [2014-03-17 18:29:21,904] INFO
> >>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>> Thrift Server started at 10.100.1.80
> >>> [2014-03-17 18:29:21,923] INFO
> >>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>> Thrift SSL port : 7711
> >>> [2014-03-17 18:29:21,925] INFO
> >>>
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> >>> Thrift port : 7611
> >>> [2014-03-17 18:29:21,958] INFO
> >>>
> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >>> - Successfully deployed the input WSEventLocal adaptor service
> >>> [2014-03-17 18:29:21,962] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> >>> - Successfully deployed the output WSEventLocal adaptor service
> >>> [2014-03-17 18:29:21,976] INFO
> >>>
> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >>> - Successfully deployed the input email event service
> >>> [2014-03-17 18:29:21,983] INFO
> >>>
> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >>> - Successfully deployed the input WSEvent adaptor service
> >>> [2014-03-17 18:29:21,993] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> >>> - Successfully deployed the output Email event adaptor service
> >>> [2014-03-17 18:29:22,002] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
> >>> - Successfully deployed the output SMS event adaptor service
> >>> [2014-03-17 18:29:22,011] INFO
> >>>
> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> >>> - Successfully deployed the output WSEvent adaptor service
> >>> [2014-03-17 18:29:22,026] INFO
> >>>
> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
> >>> A SSO Service Provider is registered for : console
> >>> [2014-03-17 18:29:22,060] ERROR
> >>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
> >>> element 'TenantRegistrationPage' not found in
> >>>
> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
> >>> [2014-03-17 18:29:22,133] INFO
> >>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
> port
> >>> : 9443
> >>> [2014-03-17 18:29:22,133] INFO
> >>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
> port
> >>> : 9763
> >>> [2014-03-17 18:29:22,138] INFO
> >>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> selector for
> >>> servlet write/read
> >>> [2014-03-17 18:29:22,154] INFO
> >>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
> selector for
> >>> servlet write/read
> >>> [2014-03-17 18:29:22,193] INFO
> >>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task
> service
> >>> starting in STANDALONE mode...
> >>> [2014-03-17 18:29:22,202] INFO
> >>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
> >>> config properties into System properties
> >>> [2014-03-17 18:29:22,225] INFO
> >>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> >>> Topology receiver thread started
> >>> [2014-03-17 18:29:22,226] INFO
> >>>
> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
> >>> - Stratos Manager topology receiver thread started
> >>> [2014-03-17 18:29:22,231] INFO
> >>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> ADC
> >>> management server component is activated
> >>> [2014-03-17 18:29:22,255] INFO
> >>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
> >>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
> >>> [2014-03-17 18:29:22,275] INFO
> >>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
> >>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
> >>> [2014-03-17 18:29:22,275] INFO
> >>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> Server
> >>> : Apache Stratos Controller-4.0.0-SNAPSHOT
> >>> [2014-03-17 18:29:22,275] INFO
> >>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> WSO2
> >>> Carbon started in 55 sec
> >>> [2014-03-17 18:29:22,430] INFO
> >>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
> URL :
> >>> https://10.100.1.80:9443/carbon/
> >>> [2014-03-17 18:29:22,521] INFO
> >>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional
> SASL
> >>> providers successfully registered.
> >>> [2014-03-17 18:29:22,522] INFO
> >>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
> >>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED
> AMQPLAIN
> >>> PLAIN
> >>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties}
> -
> >>> Unable to find resource qpidversion.properties from classloader
> >>>
> >>>
> >>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>
> >>> wrote:
> >>>>
> >>>> Hi Pradeep,
> >>>>
> >>>>
> >>>>
> >>>> I *think* I am interested in this topic and am new to this domain, but
> >>>> from the archives, I'm not 100% of the original goals of this work.
> >>>>
> >>>>
> >>>>
> >>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of
> your
> >>>> work: do we still use the same CLIs to start the processes or what? I
> see
> >>>> some mention of profiles and pre-built VMs, but am unclear how they
> relate
> >>>> to this.
> >>>>
> >>>>
> >>>>
> >>>> Can you clarify please? Is there a JIRA/spec for this feature I can
> >>>> read?
> >>>>
> >>>>
> >>>>
> >>>> Thanks, Shaheed
> >>>>
> >>>>
> >>>>
> >>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
> >>>>
> >>>> Interesting ... it would be cool to combine these with something like
> >>>> rPath to build a minimal Linux image with just the exact bits in it.
> Looks
> >>>> like rPath is gone - what's the way people build custom images now?
> Or is
> >>>> that gone with just more memory and more disk being normal??
> >>>>
> >>>>
> >>>>
> >>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi Sanjiva,
> >>>>
> >>>> Vagrant works on top of an existing image (box). There are plenty of
> >>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
> although
> >>>> the disk size is a little small to be useful. Opscode also provide
> some
> >>>> pretty good boxes [2]. If these still don't meet your needs, you can
> copy
> >>>> the packer definitions from opscode and modify them to build your own
> box
> >>>> from scratch [3]. Packer is definitely worth a look too.
> >>>>
> >>>> Many thanks,
> >>>>
> >>>> Chris
> >>>>
> >>>> ---
> >>>> [1] http://cloud-images.ubuntu.com/vagrant/
> >>>> [2] https://github.com/opscode/bento
> >>>> [3] https://github.com/opscode/bento/tree/master/packer
> >>>> [4] http://packer.io
> >>>>
> >>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >>>>
> >>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
> >>>> well!
> >>>>
> >>>>
> >>>> I'm not familiar with vagrant - just checking it out. Does it build a
> VM
> >>>> image or does it set up the environment to run the image?
> >>>>
> >>>>
> >>>> Sanjiva.
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
> wrote:
> >>>>
> >>>> Hi Sanjiva,
> >>>>
> >>>> For VM images, vagrant makes life very easy for users; setting up
> disks,
> >>>> setting up network cards, setting up memory, configuring guest proxy
> >>>> settings, running provisioning scripts, etc.
> >>>>
> >>>> I am working on a vagrant setup of cloudstack + Stratos. My project
> is
> >>>> here [1]. It isn't ready for general use yet, but I'm making good
> progress.
> >>>> Although my scripts are buggy, with a few commands I can checkout,
> build and
> >>>> provision a cloudstack developer environment. I am now working on the
> >>>> scripts to do the same for Stratos.
> >>>>
> >>>> Initially, the memory requirements will be high on my environment, but
> >>>> for me the first goal is automation, the next goal will be efficiency.
> >>>>
> >>>> Many thanks,
> >>>> Chris
> >>>>
> >>>> ---
> >>>> [1] https://github.com/snowch/devcloud-script
> >>>>
> >>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >>>>
> >>>> I think right now we need to focus on getting a single trivial server
> >>>> mechanism to be able to run Stratos without too much of stuff having
> to be
> >>>> set up. I'd love to see two developer distros:
> >>>>
> >>>>
> >>>> - a VM image that has everything in it and runs in under 4GB with
> >>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon
> server to
> >>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff
> >>>> HAS to run in one server - else its a bug in those products .. so the
> >>>> decision should not be based on ability to run in one JVM but rather
> just
> >>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I
> think
> >>>> we're nearly there for it.
> >>>>
> >>>>
> >>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
> plugin
> >>>> to jClouds that spins up Docker images as processes and there's one
> JVM that
> >>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus
> a URL
> >>>> to a Docker image registry from which the images are booted up and run
> >>>> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS
> >>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard to
> make
> >>>> it work).
> >>>>
> >>>>
> >>>> For production deployments obviously this one server stuff is nonsense
> >>>> .. so we need to have full decoupled distributed execution. For that
> we
> >>>> should ship puppet scripts to get them up and running plus maybe Boto
> >>>> scripts for someone to get it all up on EC2 with one command. Again
> its
> >>>> totally fine to use whatever broker here and whatever other pluggable
> >>>> components people want to use (and we need to make sure all the parts
> are
> >>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
> >>>>
> >>>>
> >>>> Makes sense?
> >>>>
> >>>>
> >>>> Sanjiva.
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <
> pradeepfn@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi Chris,
> >>>>
> >>>> Yes good point. Other day Azeez did the same suggestion.
> >>>>
> >>>> Thanks
> >>>>
> >>>> --Pradeep
> >>>> sent from my phone
> >>>>
> >>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
> >>>>
> >>>> Hi Pradeep - I don't know enough about how the profiles work to have a
> >>>> view on that :(
> >>>>
> >>>> One thing I'm wondering though is how much memory will be saved if we
> >>>> use RabbitMQ (or another MQ) instead of MB?
> >>>>
> >>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
> pradeepfn@gmail.com>
> >>>> wrote:
> >>>> > btw,
> >>>> >
> >>>> > Now im working on MB and CEP bits.
> >>>> >
> >>>> > IMHO, we should not create MB and CEP only profiles in stratos.
> >>>> > However,
> >>>> > adding MB/CEP features (the ones that we use) to default profile
> (the
> >>>> > profile that has all) makes sense.
> >>>> >
> >>>> > WDYT?
> >>>> >
> >>>> > Are we all on same page..
> >>>> >
> >>>> > thanks
> >>>> >
> >>>> >
> >>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
> >>>> > wrote:
> >>>> >>
> >>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
> >>>> >> findings!
> >>>> >>
> >>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
> >>>> >> <pr...@gmail.com>
> >>>> >> wrote:
> >>>> >> > Hi Guys,
> >>>> >> >
> >>>> >> > I started on the $subject. This thread is to track the progress..
> >>>> >> >
> >>>> >> > thanks,
> >>>> >> >
> >>>> >> >
> >>>> >> > --
> >>>> >> > Pradeep Fernando.
> >>>> >> > http://pradeepfernando.blogspot.com/
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >> --
> >>>> >> Check out my professional profile and connect with me on LinkedIn.
> >>>> >> http://lnkd.in/cw5k69
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Pradeep Fernando.
> >>>> > http://pradeepfernando.blogspot.com/
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Check out my professional profile and connect with me on LinkedIn.
> >>>> http://lnkd.in/cw5k69
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Sanjiva Weerawarana, Ph.D.
> >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>> Lean . Enterprise . Middleware
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Sanjiva Weerawarana, Ph.D.
> >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>> Lean . Enterprise . Middleware
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Sanjiva Weerawarana, Ph.D.
> >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>> Lean . Enterprise . Middleware
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Pradeep Fernando.
> >>> http://pradeepfernando.blogspot.com/
> >>
> >>
> >>
> >>
> >> --
> >> Pradeep Fernando.
> >> http://pradeepfernando.blogspot.com/
> >
> >
> >
> >
> > --
> > Isuru Perera
> > Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> >
> > Lean . Enterprise . Middleware
> >
> > about.me/chrishantha
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Is RabbbitMQ the simplest to setup? i.e. just install the OS package
("apt-get install rabbitmq-server") and then configure stratos to use
it?
On Mon, Mar 17, 2014 at 1:36 PM, Isuru Perera <is...@wso2.com> wrote:
> I think running an ActiveMQ or a RabbitMQ along with Stratos single pack
> would be okay.
>
> Integrating MB features to Stratos will bring unnecessary complications.
> Having MB within CC was one of the limitations to upgrade jclouds libraries
> when we were doing Stratos 3.0.0-incubating release.
>
> There is nothing much to configure in Message Broker. IMO we don't need to
> integrate MB into Stratos for now.
>
> On Mon, Mar 17, 2014 at 6:35 PM, Pradeep Fernando <pr...@gmail.com>
> wrote:
>>
>> So the remaining bit is MB.
>>
>> We need to integrate WSO2 MB or ActiveMQ.
>>
>> @Shaheed : will get back to you with answers. :) sorry im bit busy at the
>> moment.
>>
>> thanks
>>
>>
>> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>>>
>>> Hi Guys,
>>>
>>> Now the server starts fine with as + cc + sm + cep
>>>
>>> I managed to workaround the classloading issue, by renaming stub
>>> packages. Right now im encountering a CNF due to jcloud class
>>> unavailability. Its a pretty straightforward fix.
>>>
>>> [2014-03-17 18:29:20,715] ERROR
>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
>>> adding services from bundle :
>>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>>> java.lang.NoClassDefFoundError:
>>> org/jclouds/rest/ResourceNotFoundException
>>>
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:247)
>>> at
>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>>> at
>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>>> at
>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>>> at
>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>> at
>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>> at
>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>> at
>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>>> at
>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> at
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>>> at
>>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:662)
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.jclouds.rest.ResourceNotFoundException
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>> ... 49 more
>>> [2014-03-17 18:29:20,726] INFO
>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
>>> service: InstanceCleanupNotificationService {super-tenant}
>>> [2014-03-17 18:29:21,465] INFO
>>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
>>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>>> [2014-03-17 18:29:21,748] INFO
>>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>> Permission cache updated for tenant -1234
>>> [2014-03-17 18:29:21,904] INFO
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> Thrift Server started at 10.100.1.80
>>> [2014-03-17 18:29:21,923] INFO
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> Thrift SSL port : 7711
>>> [2014-03-17 18:29:21,925] INFO
>>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>> Thrift port : 7611
>>> [2014-03-17 18:29:21,958] INFO
>>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>> - Successfully deployed the input WSEventLocal adaptor service
>>> [2014-03-17 18:29:21,962] INFO
>>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>>> - Successfully deployed the output WSEventLocal adaptor service
>>> [2014-03-17 18:29:21,976] INFO
>>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>> - Successfully deployed the input email event service
>>> [2014-03-17 18:29:21,983] INFO
>>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>> - Successfully deployed the input WSEvent adaptor service
>>> [2014-03-17 18:29:21,993] INFO
>>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>>> - Successfully deployed the output Email event adaptor service
>>> [2014-03-17 18:29:22,002] INFO
>>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>>> - Successfully deployed the output SMS event adaptor service
>>> [2014-03-17 18:29:22,011] INFO
>>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>>> - Successfully deployed the output WSEvent adaptor service
>>> [2014-03-17 18:29:22,026] INFO
>>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager} -
>>> A SSO Service Provider is registered for : console
>>> [2014-03-17 18:29:22,060] ERROR
>>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
>>> element 'TenantRegistrationPage' not found in
>>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>>> [2014-03-17 18:29:22,133] INFO
>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
>>> : 9443
>>> [2014-03-17 18:29:22,133] INFO
>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
>>> : 9763
>>> [2014-03-17 18:29:22,138] INFO
>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>>> servlet write/read
>>> [2014-03-17 18:29:22,154] INFO
>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>>> servlet write/read
>>> [2014-03-17 18:29:22,193] INFO
>>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
>>> starting in STANDALONE mode...
>>> [2014-03-17 18:29:22,202] INFO
>>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
>>> config properties into System properties
>>> [2014-03-17 18:29:22,225] INFO
>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>>> Topology receiver thread started
>>> [2014-03-17 18:29:22,226] INFO
>>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>>> - Stratos Manager topology receiver thread started
>>> [2014-03-17 18:29:22,231] INFO
>>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
>>> management server component is activated
>>> [2014-03-17 18:29:22,255] INFO
>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>> [2014-03-17 18:29:22,275] INFO
>>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>>> [2014-03-17 18:29:22,275] INFO
>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
>>> : Apache Stratos Controller-4.0.0-SNAPSHOT
>>> [2014-03-17 18:29:22,275] INFO
>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>>> Carbon started in 55 sec
>>> [2014-03-17 18:29:22,430] INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL :
>>> https://10.100.1.80:9443/carbon/
>>> [2014-03-17 18:29:22,521] INFO
>>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
>>> providers successfully registered.
>>> [2014-03-17 18:29:22,522] INFO
>>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
>>> PLAIN
>>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
>>> Unable to find resource qpidversion.properties from classloader
>>>
>>>
>>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>
>>> wrote:
>>>>
>>>> Hi Pradeep,
>>>>
>>>>
>>>>
>>>> I *think* I am interested in this topic and am new to this domain, but
>>>> from the archives, I'm not 100% of the original goals of this work.
>>>>
>>>>
>>>>
>>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of your
>>>> work: do we still use the same CLIs to start the processes or what? I see
>>>> some mention of profiles and pre-built VMs, but am unclear how they relate
>>>> to this.
>>>>
>>>>
>>>>
>>>> Can you clarify please? Is there a JIRA/spec for this feature I can
>>>> read?
>>>>
>>>>
>>>>
>>>> Thanks, Shaheed
>>>>
>>>>
>>>>
>>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>>
>>>> Interesting ... it would be cool to combine these with something like
>>>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>>>> like rPath is gone - what's the way people build custom images now? Or is
>>>> that gone with just more memory and more disk being normal??
>>>>
>>>>
>>>>
>>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Sanjiva,
>>>>
>>>> Vagrant works on top of an existing image (box). There are plenty of
>>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>>>> the disk size is a little small to be useful. Opscode also provide some
>>>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>>>> the packer definitions from opscode and modify them to build your own box
>>>> from scratch [3]. Packer is definitely worth a look too.
>>>>
>>>> Many thanks,
>>>>
>>>> Chris
>>>>
>>>> ---
>>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>>> [2] https://github.com/opscode/bento
>>>> [3] https://github.com/opscode/bento/tree/master/packer
>>>> [4] http://packer.io
>>>>
>>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>
>>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>>>> well!
>>>>
>>>>
>>>> I'm not familiar with vagrant - just checking it out. Does it build a VM
>>>> image or does it set up the environment to run the image?
>>>>
>>>>
>>>> Sanjiva.
>>>>
>>>>
>>>>
>>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>>>
>>>> Hi Sanjiva,
>>>>
>>>> For VM images, vagrant makes life very easy for users; setting up disks,
>>>> setting up network cards, setting up memory, configuring guest proxy
>>>> settings, running provisioning scripts, etc.
>>>>
>>>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>>>> here [1]. It isn't ready for general use yet, but I'm making good progress.
>>>> Although my scripts are buggy, with a few commands I can checkout, build and
>>>> provision a cloudstack developer environment. I am now working on the
>>>> scripts to do the same for Stratos.
>>>>
>>>> Initially, the memory requirements will be high on my environment, but
>>>> for me the first goal is automation, the next goal will be efficiency.
>>>>
>>>> Many thanks,
>>>> Chris
>>>>
>>>> ---
>>>> [1] https://github.com/snowch/devcloud-script
>>>>
>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>
>>>> I think right now we need to focus on getting a single trivial server
>>>> mechanism to be able to run Stratos without too much of stuff having to be
>>>> set up. I'd love to see two developer distros:
>>>>
>>>>
>>>> - a VM image that has everything in it and runs in under 4GB with
>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server to
>>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon stuff
>>>> HAS to run in one server - else its a bug in those products .. so the
>>>> decision should not be based on ability to run in one JVM but rather just
>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>>> we're nearly there for it.
>>>>
>>>>
>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>>> to jClouds that spins up Docker images as processes and there's one JVM that
>>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
>>>> to a Docker image registry from which the images are booted up and run
>>>> (obviously a local registry will do better). We don't have this no-IaaS-IaaS
>>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard to make
>>>> it work).
>>>>
>>>>
>>>> For production deployments obviously this one server stuff is nonsense
>>>> .. so we need to have full decoupled distributed execution. For that we
>>>> should ship puppet scripts to get them up and running plus maybe Boto
>>>> scripts for someone to get it all up on EC2 with one command. Again its
>>>> totally fine to use whatever broker here and whatever other pluggable
>>>> components people want to use (and we need to make sure all the parts are
>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>>
>>>>
>>>> Makes sense?
>>>>
>>>>
>>>> Sanjiva.
>>>>
>>>>
>>>>
>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Chris,
>>>>
>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>
>>>> Thanks
>>>>
>>>> --Pradeep
>>>> sent from my phone
>>>>
>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>
>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>> view on that :(
>>>>
>>>> One thing I'm wondering though is how much memory will be saved if we
>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>
>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>>> wrote:
>>>> > btw,
>>>> >
>>>> > Now im working on MB and CEP bits.
>>>> >
>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>> > However,
>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>> > profile that has all) makes sense.
>>>> >
>>>> > WDYT?
>>>> >
>>>> > Are we all on same page..
>>>> >
>>>> > thanks
>>>> >
>>>> >
>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>> > wrote:
>>>> >>
>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>> >> findings!
>>>> >>
>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>> >> <pr...@gmail.com>
>>>> >> wrote:
>>>> >> > Hi Guys,
>>>> >> >
>>>> >> > I started on the $subject. This thread is to track the progress..
>>>> >> >
>>>> >> > thanks,
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Pradeep Fernando.
>>>> >> > http://pradeepfernando.blogspot.com/
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>> >> http://lnkd.in/cw5k69
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Pradeep Fernando.
>>>> > http://pradeepfernando.blogspot.com/
>>>>
>>>>
>>>>
>>>> --
>>>> Check out my professional profile and connect with me on LinkedIn.
>>>> http://lnkd.in/cw5k69
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando.
>>> http://pradeepfernando.blogspot.com/
>>
>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>
>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by Isuru Perera <is...@wso2.com>.
I think running an ActiveMQ or a RabbitMQ along with Stratos single pack
would be okay.
Integrating MB features to Stratos will bring unnecessary complications.
Having MB within CC was one of the limitations to upgrade jclouds libraries
when we were doing Stratos 3.0.0-incubating release.
There is nothing much to configure in Message Broker. IMO we don't need to
integrate MB into Stratos for now.
On Mon, Mar 17, 2014 at 6:35 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> So the remaining bit is MB.
>
> We need to integrate WSO2 MB or ActiveMQ.
>
> @Shaheed : will get back to you with answers. :) sorry im bit busy at the
> moment.
>
> thanks
>
>
> On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Hi Guys,
>>
>> Now the server starts fine with as + cc + sm + cep
>>
>> I managed to workaround the classloading issue, by renaming stub
>> packages. Right now im encountering a CNF due to jcloud class
>> unavailability. Its a pretty straightforward fix.
>>
>> [2014-03-17 18:29:20,715] ERROR
>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
>> adding services from bundle :
>> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
>> java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
>>
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:247)
>> at
>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
>> at
>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
>> at
>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
>> at
>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>> at
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>> at
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>> Caused by: java.lang.ClassNotFoundException:
>> org.jclouds.rest.ResourceNotFoundException
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> ... 49 more
>> [2014-03-17 18:29:20,726] INFO
>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
>> service: InstanceCleanupNotificationService {super-tenant}
>> [2014-03-17 18:29:21,465] INFO
>> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
>> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
>> [2014-03-17 18:29:21,748] INFO
>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>> Permission cache updated for tenant -1234
>> [2014-03-17 18:29:21,904] INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> Thrift Server started at 10.100.1.80
>> [2014-03-17 18:29:21,923] INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> Thrift SSL port : 7711
>> [2014-03-17 18:29:21,925] INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>> Thrift port : 7611
>> [2014-03-17 18:29:21,958] INFO
>> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> - Successfully deployed the input WSEventLocal adaptor service
>> [2014-03-17 18:29:21,962] INFO
>> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
>> - Successfully deployed the output WSEventLocal adaptor service
>> [2014-03-17 18:29:21,976] INFO
>> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> - Successfully deployed the input email event service
>> [2014-03-17 18:29:21,983] INFO
>> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> - Successfully deployed the input WSEvent adaptor service
>> [2014-03-17 18:29:21,993] INFO
>> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
>> - Successfully deployed the output Email event adaptor service
>> [2014-03-17 18:29:22,002] INFO
>> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
>> - Successfully deployed the output SMS event adaptor service
>> [2014-03-17 18:29:22,011] INFO
>> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
>> - Successfully deployed the output WSEvent adaptor service
>> [2014-03-17 18:29:22,026] INFO
>> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager}
>> - A SSO Service Provider is registered for : console
>> [2014-03-17 18:29:22,060] ERROR
>> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
>> element 'TenantRegistrationPage' not found in
>> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
>> [2014-03-17 18:29:22,133] INFO
>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
>> port : 9443
>> [2014-03-17 18:29:22,133] INFO
>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>> port : 9763
>> [2014-03-17 18:29:22,138] INFO
>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>> servlet write/read
>> [2014-03-17 18:29:22,154] INFO
>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
>> servlet write/read
>> [2014-03-17 18:29:22,193] INFO
>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
>> starting in STANDALONE mode...
>> [2014-03-17 18:29:22,202] INFO
>> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
>> config properties into System properties
>> [2014-03-17 18:29:22,225] INFO
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
>> Topology receiver thread started
>> [2014-03-17 18:29:22,226] INFO
>> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
>> - Stratos Manager topology receiver thread started
>> [2014-03-17 18:29:22,231] INFO
>> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
>> management server component is activated
>> [2014-03-17 18:29:22,255] INFO
>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>> [2014-03-17 18:29:22,275] INFO
>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
>> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
>> [2014-03-17 18:29:22,275] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>> Server : Apache Stratos Controller-4.0.0-SNAPSHOT
>> [2014-03-17 18:29:22,275] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>> Carbon started in 55 sec
>> [2014-03-17 18:29:22,430] INFO
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
>> : https://10.100.1.80:9443/carbon/
>> [2014-03-17 18:29:22,521] INFO
>> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
>> providers successfully registered.
>> [2014-03-17 18:29:22,522] INFO
>> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
>> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
>> PLAIN
>> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
>> Unable to find resource qpidversion.properties from classloader
>>
>>
>> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com>wrote:
>>
>>> Hi Pradeep,
>>>
>>>
>>>
>>> I *think* I am interested in this topic and am new to this domain, but
>>> from the archives, I'm not 100% of the original goals of this work.
>>>
>>>
>>>
>>> Also, if the idea is to ship in 4.0.0, how can we take advantage of your
>>> work: do we still use the same CLIs to start the processes or what? I see
>>> some mention of profiles and pre-built VMs, but am unclear how they relate
>>> to this.
>>>
>>>
>>>
>>> Can you clarify please? Is there a JIRA/spec for this feature I can read?
>>>
>>>
>>>
>>> Thanks, Shaheed
>>>
>>>
>>>
>>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>>
>>> Interesting ... it would be cool to combine these with something like
>>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>>> like rPath is gone - what's the way people build custom images now? Or is
>>> that gone with just more memory and more disk being normal??
>>>
>>>
>>>
>>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>>
>>> Hi Sanjiva,
>>>
>>> Vagrant works on top of an existing image (box). There are plenty of
>>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>>> the disk size is a little small to be useful. Opscode also provide some
>>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>>> the packer definitions from opscode and modify them to build your own box
>>> from scratch [3]. Packer is definitely worth a look too.
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>> ---
>>> [1] http://cloud-images.ubuntu.com/vagrant/
>>> [2] https://github.com/opscode/bento
>>> [3] https://github.com/opscode/bento/tree/master/packer
>>> [4] http://packer.io
>>>
>>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>>> well!
>>>
>>>
>>> I'm not familiar with vagrant - just checking it out. Does it build a VM
>>> image or does it set up the environment to run the image?
>>>
>>>
>>> Sanjiva.
>>>
>>>
>>>
>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>>
>>> Hi Sanjiva,
>>>
>>> For VM images, vagrant makes life very easy for users; setting up disks,
>>> setting up network cards, setting up memory, configuring guest proxy
>>> settings, running provisioning scripts, etc.
>>>
>>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>>> here [1]. It isn't ready for general use yet, but I'm making good
>>> progress. Although my scripts are buggy, with a few commands I can
>>> checkout, build and provision a cloudstack developer environment. I am now
>>> working on the scripts to do the same for Stratos.
>>>
>>> Initially, the memory requirements will be high on my environment, but
>>> for me the first goal is automation, the next goal will be efficiency.
>>>
>>> Many thanks,
>>> Chris
>>>
>>> ---
>>> [1] https://github.com/snowch/devcloud-script
>>>
>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>> I think right now we need to focus on getting a single trivial server
>>> mechanism to be able to run Stratos without too much of stuff having to be
>>> set up. I'd love to see two developer distros:
>>>
>>>
>>> - a VM image that has everything in it and runs in under 4GB with
>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>>> stuff HAS to run in one server - else its a bug in those products .. so the
>>> decision should not be based on ability to run in one JVM but rather just
>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>> we're nearly there for it.
>>>
>>>
>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>> to jClouds that spins up Docker images as processes and there's one JVM
>>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>>> URL to a Docker image registry from which the images are booted up and run
>>> (obviously a local registry will do better). We don't have this
>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>>> hard to make it work).
>>>
>>>
>>> For production deployments obviously this one server stuff is nonsense
>>> .. so we need to have full decoupled distributed execution. For that we
>>> should ship puppet scripts to get them up and running plus maybe Boto
>>> scripts for someone to get it all up on EC2 with one command. Again its
>>> totally fine to use whatever broker here and whatever other pluggable
>>> components people want to use (and we need to make sure all the parts are
>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>
>>>
>>> Makes sense?
>>>
>>>
>>> Sanjiva.
>>>
>>>
>>>
>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>>
>>> Hi Chris,
>>>
>>> Yes good point. Other day Azeez did the same suggestion.
>>>
>>> Thanks
>>>
>>> --Pradeep
>>> sent from my phone
>>>
>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>
>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>> view on that :(
>>>
>>> One thing I'm wondering though is how much memory will be saved if we
>>> use RabbitMQ (or another MQ) instead of MB?
>>>
>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>> > btw,
>>> >
>>> > Now im working on MB and CEP bits.
>>> >
>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>> However,
>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>> > profile that has all) makes sense.
>>> >
>>> > WDYT?
>>> >
>>> > Are we all on same page..
>>> >
>>> > thanks
>>> >
>>> >
>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>> >>
>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>> findings!
>>> >>
>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>> pradeepfn@gmail.com>
>>> >> wrote:
>>> >> > Hi Guys,
>>> >> >
>>> >> > I started on the $subject. This thread is to track the progress..
>>> >> >
>>> >> > thanks,
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Pradeep Fernando.
>>> >> > http://pradeepfernando.blogspot.com/
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Check out my professional profile and connect with me on LinkedIn.
>>> >> http://lnkd.in/cw5k69
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Pradeep Fernando.
>>> > http://pradeepfernando.blogspot.com/
>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
So the remaining bit is MB.
We need to integrate WSO2 MB or ActiveMQ.
@Shaheed : will get back to you with answers. :) sorry im bit busy at the
moment.
thanks
On Mon, Mar 17, 2014 at 6:33 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Hi Guys,
>
> Now the server starts fine with as + cc + sm + cep
>
> I managed to workaround the classloading issue, by renaming stub packages.
> Right now im encountering a CNF due to jcloud class unavailability. Its a
> pretty straightforward fix.
>
> [2014-03-17 18:29:20,715] ERROR
> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
> adding services from bundle :
> org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
> java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
>
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
> at
> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException:
> org.jclouds.rest.ResourceNotFoundException
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 49 more
> [2014-03-17 18:29:20,726] INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
> service: InstanceCleanupNotificationService {super-tenant}
> [2014-03-17 18:29:21,465] INFO
> {org.wso2.carbon.core.init.CarbonServerManager} - Repository :
> /home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
> [2014-03-17 18:29:21,748] INFO
> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> Permission cache updated for tenant -1234
> [2014-03-17 18:29:21,904] INFO
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> Thrift Server started at 10.100.1.80
> [2014-03-17 18:29:21,923] INFO
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> Thrift SSL port : 7711
> [2014-03-17 18:29:21,925] INFO
> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
> Thrift port : 7611
> [2014-03-17 18:29:21,958] INFO
> {org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> - Successfully deployed the input WSEventLocal adaptor service
> [2014-03-17 18:29:21,962] INFO
> {org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
> - Successfully deployed the output WSEventLocal adaptor service
> [2014-03-17 18:29:21,976] INFO
> {org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> - Successfully deployed the input email event service
> [2014-03-17 18:29:21,983] INFO
> {org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> - Successfully deployed the input WSEvent adaptor service
> [2014-03-17 18:29:21,993] INFO
> {org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
> - Successfully deployed the output Email event adaptor service
> [2014-03-17 18:29:22,002] INFO
> {org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
> - Successfully deployed the output SMS event adaptor service
> [2014-03-17 18:29:22,011] INFO
> {org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
> - Successfully deployed the output WSEvent adaptor service
> [2014-03-17 18:29:22,026] INFO
> {org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager}
> - A SSO Service Provider is registered for : console
> [2014-03-17 18:29:22,060] ERROR
> {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
> element 'TenantRegistrationPage' not found in
> '/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
> [2014-03-17 18:29:22,133] INFO
> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
> port : 9443
> [2014-03-17 18:29:22,133] INFO
> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
> port : 9763
> [2014-03-17 18:29:22,138] INFO
> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
> servlet write/read
> [2014-03-17 18:29:22,154] INFO
> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
> servlet write/read
> [2014-03-17 18:29:22,193] INFO
> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
> starting in STANDALONE mode...
> [2014-03-17 18:29:22,202] INFO
> {org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
> config properties into System properties
> [2014-03-17 18:29:22,225] INFO
> {org.apache.stratos.manager.internal.ADCManagementServerComponent} -
> Topology receiver thread started
> [2014-03-17 18:29:22,226] INFO
> {org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
> - Stratos Manager topology receiver thread started
> [2014-03-17 18:29:22,231] INFO
> {org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
> management server component is activated
> [2014-03-17 18:29:22,255] INFO
> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
> [2014-03-17 18:29:22,275] INFO
> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
> scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
> [2014-03-17 18:29:22,275] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> Server : Apache Stratos Controller-4.0.0-SNAPSHOT
> [2014-03-17 18:29:22,275] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
> Carbon started in 55 sec
> [2014-03-17 18:29:22,430] INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
> : https://10.100.1.80:9443/carbon/
> [2014-03-17 18:29:22,521] INFO
> {org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
> providers successfully registered.
> [2014-03-17 18:29:22,522] INFO
> {org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
> handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
> PLAIN
> [2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
> Unable to find resource qpidversion.properties from classloader
>
>
> On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com> wrote:
>
>> Hi Pradeep,
>>
>>
>>
>> I *think* I am interested in this topic and am new to this domain, but
>> from the archives, I'm not 100% of the original goals of this work.
>>
>>
>>
>> Also, if the idea is to ship in 4.0.0, how can we take advantage of your
>> work: do we still use the same CLIs to start the processes or what? I see
>> some mention of profiles and pre-built VMs, but am unclear how they relate
>> to this.
>>
>>
>>
>> Can you clarify please? Is there a JIRA/spec for this feature I can read?
>>
>>
>>
>> Thanks, Shaheed
>>
>>
>>
>> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>>
>> Interesting ... it would be cool to combine these with something like
>> rPath to build a minimal Linux image with just the exact bits in it. Looks
>> like rPath is gone - what's the way people build custom images now? Or is
>> that gone with just more memory and more disk being normal??
>>
>>
>>
>> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> Vagrant works on top of an existing image (box). There are plenty of
>> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>> the disk size is a little small to be useful. Opscode also provide some
>> pretty good boxes [2]. If these still don't meet your needs, you can copy
>> the packer definitions from opscode and modify them to build your own box
>> from scratch [3]. Packer is definitely worth a look too.
>>
>> Many thanks,
>>
>> Chris
>>
>> ---
>> [1] http://cloud-images.ubuntu.com/vagrant/
>> [2] https://github.com/opscode/bento
>> [3] https://github.com/opscode/bento/tree/master/packer
>> [4] http://packer.io
>>
>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>
>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>> well!
>>
>>
>> I'm not familiar with vagrant - just checking it out. Does it build a VM
>> image or does it set up the environment to run the image?
>>
>>
>> Sanjiva.
>>
>>
>>
>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> For VM images, vagrant makes life very easy for users; setting up disks,
>> setting up network cards, setting up memory, configuring guest proxy
>> settings, running provisioning scripts, etc.
>>
>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>> here [1]. It isn't ready for general use yet, but I'm making good
>> progress. Although my scripts are buggy, with a few commands I can
>> checkout, build and provision a cloudstack developer environment. I am now
>> working on the scripts to do the same for Stratos.
>>
>> Initially, the memory requirements will be high on my environment, but
>> for me the first goal is automation, the next goal will be efficiency.
>>
>> Many thanks,
>> Chris
>>
>> ---
>> [1] https://github.com/snowch/devcloud-script
>>
>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>
>> I think right now we need to focus on getting a single trivial server
>> mechanism to be able to run Stratos without too much of stuff having to be
>> set up. I'd love to see two developer distros:
>>
>>
>> - a VM image that has everything in it and runs in under 4GB with
>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>> stuff HAS to run in one server - else its a bug in those products .. so the
>> decision should not be based on ability to run in one JVM but rather just
>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>> we're nearly there for it.
>>
>>
>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>> to jClouds that spins up Docker images as processes and there's one JVM
>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>> URL to a Docker image registry from which the images are booted up and run
>> (obviously a local registry will do better). We don't have this
>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>> hard to make it work).
>>
>>
>> For production deployments obviously this one server stuff is nonsense ..
>> so we need to have full decoupled distributed execution. For that we should
>> ship puppet scripts to get them up and running plus maybe Boto scripts for
>> someone to get it all up on EC2 with one command. Again its totally fine to
>> use whatever broker here and whatever other pluggable components people
>> want to use (and we need to make sure all the parts are pluggable: load
>> balancers, message broker, the CEP engine, etc.)).
>>
>>
>> Makes sense?
>>
>>
>> Sanjiva.
>>
>>
>>
>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>>
>> Hi Chris,
>>
>> Yes good point. Other day Azeez did the same suggestion.
>>
>> Thanks
>>
>> --Pradeep
>> sent from my phone
>>
>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>
>> Hi Pradeep - I don't know enough about how the profiles work to have a
>> view on that :(
>>
>> One thing I'm wondering though is how much memory will be saved if we
>> use RabbitMQ (or another MQ) instead of MB?
>>
>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > btw,
>> >
>> > Now im working on MB and CEP bits.
>> >
>> > IMHO, we should not create MB and CEP only profiles in stratos. However,
>> > adding MB/CEP features (the ones that we use) to default profile (the
>> > profile that has all) makes sense.
>> >
>> > WDYT?
>> >
>> > Are we all on same page..
>> >
>> > thanks
>> >
>> >
>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>> wrote:
>> >>
>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> findings!
>> >>
>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pradeepfn@gmail.com
>> >
>> >> wrote:
>> >> > Hi Guys,
>> >> >
>> >> > I started on the $subject. This thread is to track the progress..
>> >> >
>> >> > thanks,
>> >> >
>> >> >
>> >> > --
>> >> > Pradeep Fernando.
>> >> > http://pradeepfernando.blogspot.com/
>> >>
>> >>
>> >>
>> >> --
>> >> Check out my professional profile and connect with me on LinkedIn.
>> >> http://lnkd.in/cw5k69
>> >
>> >
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>>
>>
>>
>> --
>>
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>> --
>>
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>> --
>>
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
Hi Guys,
Now the server starts fine with as + cc + sm + cep
I managed to workaround the classloading issue, by renaming stub packages.
Right now im encountering a CNF due to jcloud class unavailability. Its a
pretty straightforward fix.
[2014-03-17 18:29:20,715] ERROR
{org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
adding services from bundle :
org.apache.stratos.cloud.controller-4.0.0.SNAPSHOT
java.lang.NoClassDefFoundError: org/jclouds/rest/ResourceNotFoundException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:140)
at
org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
at
org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException:
org.jclouds.rest.ResourceNotFoundException
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 49 more
[2014-03-17 18:29:20,726] INFO
{org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
service: InstanceCleanupNotificationService {super-tenant}
[2014-03-17 18:29:21,465] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Repository :
/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/deployment/server/
[2014-03-17 18:29:21,748] INFO
{org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
Permission cache updated for tenant -1234
[2014-03-17 18:29:21,904] INFO
{org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
Thrift Server started at 10.100.1.80
[2014-03-17 18:29:21,923] INFO
{org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
Thrift SSL port : 7711
[2014-03-17 18:29:21,925] INFO
{org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
Thrift port : 7611
[2014-03-17 18:29:21,958] INFO
{org.wso2.carbon.event.input.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
- Successfully deployed the input WSEventLocal adaptor service
[2014-03-17 18:29:21,962] INFO
{org.wso2.carbon.event.output.adaptor.wsevent.local.internal.ds.WSEventLocalEventAdaptorServiceDS}
- Successfully deployed the output WSEventLocal adaptor service
[2014-03-17 18:29:21,976] INFO
{org.wso2.carbon.event.input.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
- Successfully deployed the input email event service
[2014-03-17 18:29:21,983] INFO
{org.wso2.carbon.event.input.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
- Successfully deployed the input WSEvent adaptor service
[2014-03-17 18:29:21,993] INFO
{org.wso2.carbon.event.output.adaptor.email.internal.ds.EmailEventAdaptorServiceDS}
- Successfully deployed the output Email event adaptor service
[2014-03-17 18:29:22,002] INFO
{org.wso2.carbon.event.output.adaptor.sms.internal.ds.SMSEventAdaptorServiceDS}
- Successfully deployed the output SMS event adaptor service
[2014-03-17 18:29:22,011] INFO
{org.wso2.carbon.event.output.adaptor.wsevent.internal.ds.WSEventAdaptorServiceDS}
- Successfully deployed the output WSEvent adaptor service
[2014-03-17 18:29:22,026] INFO
{org.wso2.stratos.identity.saml2.sso.mgt.SSOServiceProviderUpdateManager}
- A SSO Service Provider is registered for : console
[2014-03-17 18:29:22,060] ERROR
{org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration
element 'TenantRegistrationPage' not found in
'/home/pradeep/checkout/stratos-profile/products/stratos/modules/distribution/target/apache-stratos-4.0.0-SNAPSHOT/repository/conf/sso-idp-config.xml'
[2014-03-17 18:29:22,133] INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
port : 9443
[2014-03-17 18:29:22,133] INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
port : 9763
[2014-03-17 18:29:22,138] INFO
{org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
servlet write/read
[2014-03-17 18:29:22,154] INFO
{org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
servlet write/read
[2014-03-17 18:29:22,193] INFO
{org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service
starting in STANDALONE mode...
[2014-03-17 18:29:22,202] INFO
{org.apache.stratos.manager.utils.CartridgeConfigFileReader} - Setting
config properties into System properties
[2014-03-17 18:29:22,225] INFO
{org.apache.stratos.manager.internal.ADCManagementServerComponent} -
Topology receiver thread started
[2014-03-17 18:29:22,226] INFO
{org.apache.stratos.manager.topology.receiver.StratosManagerTopologyReceiver}
- Stratos Manager topology receiver thread started
[2014-03-17 18:29:22,231] INFO
{org.apache.stratos.manager.internal.ADCManagementServerComponent} - ADC
management server component is activated
[2014-03-17 18:29:22,255] INFO
{org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
[2014-03-17 18:29:22,275] INFO
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task
scheduled: [-1234][TENANT_SYNC_TASK_TYPE][TENANT_SYNC_TASK]
[2014-03-17 18:29:22,275] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
Server : Apache Stratos Controller-4.0.0-SNAPSHOT
[2014-03-17 18:29:22,275] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
Carbon started in 55 sec
[2014-03-17 18:29:22,430] INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
: https://10.100.1.80:9443/carbon/
[2014-03-17 18:29:22,521] INFO
{org.wso2.andes.client.security.DynamicSaslRegistrar} - Additional SASL
providers successfully registered.
[2014-03-17 18:29:22,522] INFO
{org.wso2.andes.client.security.CallbackHandlerRegistry} - Callback
handlers available for SASL mechanisms: CRAM-MD5 CRAM-MD5-HASHED AMQPLAIN
PLAIN
[2014-03-17 18:29:22,535] WARN {org.wso2.andes.common.QpidProperties} -
Unable to find resource qpidversion.properties from classloader
On Mon, Mar 17, 2014 at 4:15 PM, Shaheed Haque <sh...@cisco.com> wrote:
> Hi Pradeep,
>
>
>
> I *think* I am interested in this topic and am new to this domain, but
> from the archives, I'm not 100% of the original goals of this work.
>
>
>
> Also, if the idea is to ship in 4.0.0, how can we take advantage of your
> work: do we still use the same CLIs to start the processes or what? I see
> some mention of profiles and pre-built VMs, but am unclear how they relate
> to this.
>
>
>
> Can you clarify please? Is there a JIRA/spec for this feature I can read?
>
>
>
> Thanks, Shaheed
>
>
>
> On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
>
> Interesting ... it would be cool to combine these with something like
> rPath to build a minimal Linux image with just the exact bits in it. Looks
> like rPath is gone - what's the way people build custom images now? Or is
> that gone with just more memory and more disk being normal??
>
>
>
> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com> wrote:
>
> Hi Sanjiva,
>
> Vagrant works on top of an existing image (box). There are plenty of boxes
> for vagrant. Ubuntu for example provides vagrant boxes [1], although the
> disk size is a little small to be useful. Opscode also provide some
> pretty good boxes [2]. If these still don't meet your needs, you can copy
> the packer definitions from opscode and modify them to build your own box
> from scratch [3]. Packer is definitely worth a look too.
>
> Many thanks,
>
> Chris
>
> ---
> [1] http://cloud-images.ubuntu.com/vagrant/
> [2] https://github.com/opscode/bento
> [3] https://github.com/opscode/bento/tree/master/packer
> [4] http://packer.io
>
> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>
> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
> well!
>
>
> I'm not familiar with vagrant - just checking it out. Does it build a VM
> image or does it set up the environment to run the image?
>
>
> Sanjiva.
>
>
>
> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>
> Hi Sanjiva,
>
> For VM images, vagrant makes life very easy for users; setting up disks,
> setting up network cards, setting up memory, configuring guest proxy
> settings, running provisioning scripts, etc.
>
> I am working on a vagrant setup of cloudstack + Stratos. My project is
> here [1]. It isn't ready for general use yet, but I'm making good
> progress. Although my scripts are buggy, with a few commands I can
> checkout, build and provision a cloudstack developer environment. I am now
> working on the scripts to do the same for Stratos.
>
> Initially, the memory requirements will be high on my environment, but for
> me the first goal is automation, the next goal will be efficiency.
>
> Many thanks,
> Chris
>
> ---
> [1] https://github.com/snowch/devcloud-script
>
> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>
> I think right now we need to focus on getting a single trivial server
> mechanism to be able to run Stratos without too much of stuff having to be
> set up. I'd love to see two developer distros:
>
>
> - a VM image that has everything in it and runs in under 4GB with
> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff HAS to run in one server - else its a bug in those products .. so the
> decision should not be based on ability to run in one JVM but rather just
> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
> we're nearly there for it.
>
>
> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin to
> jClouds that spins up Docker images as processes and there's one JVM that
> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
> to a Docker image registry from which the images are booted up and run
> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
> hard to make it work).
>
>
> For production deployments obviously this one server stuff is nonsense ..
> so we need to have full decoupled distributed execution. For that we should
> ship puppet scripts to get them up and running plus maybe Boto scripts for
> someone to get it all up on EC2 with one command. Again its totally fine to
> use whatever broker here and whatever other pluggable components people
> want to use (and we need to make sure all the parts are pluggable: load
> balancers, message broker, the CEP engine, etc.)).
>
>
> Makes sense?
>
>
> Sanjiva.
>
>
>
> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
> wrote:
>
> Hi Chris,
>
> Yes good point. Other day Azeez did the same suggestion.
>
> Thanks
>
> --Pradeep
> sent from my phone
>
> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>
> Hi Pradeep - I don't know enough about how the profiles work to have a
> view on that :(
>
> One thing I'm wondering though is how much memory will be saved if we
> use RabbitMQ (or another MQ) instead of MB?
>
> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
> wrote:
> > btw,
> >
> > Now im working on MB and CEP bits.
> >
> > IMHO, we should not create MB and CEP only profiles in stratos. However,
> > adding MB/CEP features (the ones that we use) to default profile (the
> > profile that has all) makes sense.
> >
> > WDYT?
> >
> > Are we all on same page..
> >
> > thanks
> >
> >
> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com> wrote:
> >>
> >> Hey Pradeep - this is exciting stuff! Looking forward to your findings!
> >>
> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com>
> >> wrote:
> >> > Hi Guys,
> >> >
> >> > I started on the $subject. This thread is to track the progress..
> >> >
> >> > thanks,
> >> >
> >> >
> >> > --
> >> > Pradeep Fernando.
> >> > http://pradeepfernando.blogspot.com/
> >>
> >>
> >>
> >> --
> >> Check out my professional profile and connect with me on LinkedIn.
> >> http://lnkd.in/cw5k69
> >
> >
> >
> >
> > --
> > Pradeep Fernando.
> > http://pradeepfernando.blogspot.com/
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
>
>
>
> --
>
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
>
>
>
> --
>
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
>
>
>
> --
>
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
>
>
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by Shaheed Haque <sh...@cisco.com>.
Hi Pradeep,
I *think* I am interested in this topic and am new to this domain, but from
the archives, I'm not 100% of the original goals of this work.
Also, if the idea is to ship in 4.0.0, how can we take advantage of your work:
do we still use the same CLIs to start the processes or what? I see some
mention of profiles and pre-built VMs, but am unclear how they relate to this.
Can you clarify please? Is there a JIRA/spec for this feature I can read?
Thanks, Shaheed
On Monday 17 March 2014 06:17:01 Sanjiva Weerawarana wrote:
Interesting ... it would be cool to combine these with something like rPath to
build a minimal Linux image with just the exact bits in it. Looks like rPath
is gone - what's the way people build custom images now? Or is that gone with
just more memory and more disk being normal??
On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com> wrote:
Hi Sanjiva,
Vagrant works on top of an existing image (box). There are plenty of boxes for
vagrant. Ubuntu for example provides vagrant boxes [1], although the disk size
is a little small to be useful. Opscode also provide some pretty good boxes
[2]. If these still don't meet your needs, you can copy the packer definitions
from opscode and modify them to build your own box from scratch [3]. Packer is
definitely worth a look too.
Many thanks,
Chris
---
[1] http://cloud-images.ubuntu.com/vagrant/
[2] https://github.com/opscode/bento
[3] https://github.com/opscode/bento/tree/master/packer
[4] http://packer.io
On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
Hey Chris - that's awesome .. totally +1 for having vagrant scripts as well!
I'm not familiar with vagrant - just checking it out. Does it build a VM image
or does it set up the environment to run the image?
Sanjiva.
On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
Hi Sanjiva,
For VM images, vagrant makes life very easy for users; setting up disks,
setting up network cards, setting up memory, configuring guest proxy settings,
running provisioning scripts, etc.
I am working on a vagrant setup of cloudstack + Stratos. My project is here
[1]. It isn't ready for general use yet, but I'm making good progress.
Although my scripts are buggy, with a few commands I can checkout, build and
provision a cloudstack developer environment. I am now working on the scripts
to do the same for Stratos.
Initially, the memory requirements will be high on my environment, but for me
the first goal is automation, the next goal will be efficiency.
Many thanks,
Chris
---
[1] https://github.com/snowch/devcloud-script
On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
I think right now we need to focus on getting a single trivial server
mechanism to be able to run Stratos without too much of stuff having to be set
up. I'd love to see two developer distros:
- a VM image that has everything in it and runs in under 4GB with OpenStack +
Docker. It doesn't matter whether this uses one Carbon server to run it all or
whether we use RabbitMQ or other AMQP broker. (Carbon stuff HAS to run in one
server - else its a bug in those products .. so the decision should not be
based on ability to run in one JVM but rather just making it dirt simple to
use.) This distro needs to be in 4.0.0 - I think we're nearly there for it.
- next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin to
jClouds that spins up Docker images as processes and there's one JVM that
works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL to
a Docker image registry from which the images are booted up and run (obviously
a local registry will do better). We don't have this no-IaaS-IaaS yet so this
can come maybe as 4.1.0 or whatever (its not that hard to make it work).
For production deployments obviously this one server stuff is nonsense .. so
we need to have full decoupled distributed execution. For that we should ship
puppet scripts to get them up and running plus maybe Boto scripts for someone
to get it all up on EC2 with one command. Again its totally fine to use
whatever broker here and whatever other pluggable components people want to
use (and we need to make sure all the parts are pluggable: load balancers,
message broker, the CEP engine, etc.)).
Makes sense?
Sanjiva.
On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com> wrote:
Hi Chris,
Yes good point. Other day Azeez did the same suggestion.
Thanks
--Pradeep
sent from my phone
On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
Hi Pradeep - I don't know enough about how the profiles work to have a
view on that :(
One thing I'm wondering though is how much memory will be saved if we
use RabbitMQ (or another MQ) instead of MB?
On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
wrote:
> btw,
>
> Now im working on MB and CEP bits.
>
> IMHO, we should not create MB and CEP only profiles in stratos. However,
> adding MB/CEP features (the ones that we use) to default profile (the
> profile that has all) makes sense.
>
> WDYT?
>
> Are we all on same page..
>
> thanks
>
>
> On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hey Pradeep - this is exciting stuff! Looking forward to your findings!
>>
>> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > Hi Guys,
>> >
>> > I started on the $subject. This thread is to track the progress..
>> >
>> > thanks,
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700;
cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700;
cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700;
cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
Re: Running stratos in one JVM
Posted by damitha kumarage <da...@gmail.com>.
Thanks Chris for the pointers
Damitha
On Tue, Mar 18, 2014 at 12:25 PM, chris snow <ch...@gmail.com> wrote:
> Hi Damitha,
>
> If you haven't already, take a look at the Vagrant docs getting
> started [1] - this will give you the gist of vagrant
>
> Create a new directory for your vagrant project, and create a
> Vagrantfile. This is what I am using:
>
> Vagrant.configure("2") do |config|
>
> # opscode vagrant boxes have 40Gb disk size which should be enough
> for stratos
> config.vm.box = "opscode-ubuntu-12.04"
> config.vm.box_url =
> "
> http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-12.04_chef-provisionerless.box
> "
>
> # set the box hostname
> config.vm.hostname = "paas.stratos.org"
>
> # tweak the vm
> config.vm.provider "virtualbox" do |v|
> v.customize ["modifyvm", :id, "--memory", 5120]
> end
>
> # I have a bash script stratos_dev.sh in my vagrant project folder
> # at the moment I run that script manually from inside the guest,
> but when the script is finished, I will setup vagrant to automate it
> fully
> # see http://docs.vagrantup.com/v2/provisioning/shell.html for
> more information on vagrant shell scripting
>
> config.vm.provision "shell", inline: "ln -sf
> /vagrant/stratos_dev.sh /home/vagrant/stratos_dev.sh", privileged:
> false
> end
>
> My cloudstack+stratos project is here [2]. It may be easier for you
> to follow the instructions at that page for running the stratos box.
> Note that my stratos script is still a work-in-progress.
>
> Is your host machine sitting behind a proxy server? If it is, you
> will need a vagrant plugin to configure the guest to use the proxy.
>
> Any questions, please give me a shout.
>
> Many thanks,
>
> Chris
>
>
> ---
> [1] http://docs.vagrantup.com/v2/getting-started/
> [2] https://github.com/snowch/devcloud-script/
>
> On Tue, Mar 18, 2014 at 5:27 AM, damitha kumarage <da...@gmail.com>
> wrote:
> > Hi Chris,
> > In Vagrantdocs it says machines are provisioned on top of virtualbox. So,
> > can vagrant spin up a virtualbox instance which run Stratos, starting
> from a
> > vagrantfile? Since I have already created a virtualbox image which run
> > Stratos in 5G memory(not yet with single jvm in which case it should
> reduce
> > further.), could you please explain a bit how I can get this setup
> automate
> > using vagrant (using a vagrantfile?).
> >
> > Damitha
> >
> >
> > On Mon, Mar 17, 2014 at 1:08 PM, chris snow <ch...@gmail.com> wrote:
> >>
> >> Hi Sanjiva,
> >>
> >> Packer allows you to control most aspects of image creation, but AFAIK
> >> rely on automating the distro's installation mechanism (e.g. Debian
> preseed
> >> or red hat kick start). During the installation you start the guest OS
> so
> >> you can add and remove packages as you please. For example, on the
> >> cloudstack image, I scripted replacing the standard kernel with the xen
> >> kernel packages, and rebooted during the install to pick up the new
> kernel
> >> to perform other xen dependent setup. When I ran into issues early on
> with
> >> xen, I was considering building the kernel from source. There is a lot
> of
> >> flexibility.
> >>
> >> Vagrant and packer also work with docker although I haven't tried that
> >> yet.
> >>
> >> In terms of Stratos, I have a vision forming that using vagrant and
> packer
> >> we could build images for different environments (aws, virtual box,
> docker,
> >> etc) and orchestrate the setup of stratos in those environments using
> >> vagrant - with the potential for reusing the stratos setup scripts
> between
> >> those environments. However, one step at a time, starting with vagrant
> to
> >> setup cloudstack+stratos.
> >>
> >> Cheers,
> >>
> >> Chris
> >>
> >> On 17 Mar 2014 00:47, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >> >
> >> > Interesting ... it would be cool to combine these with something like
> >> > rPath to build a minimal Linux image with just the exact bits in it.
> Looks
> >> > like rPath is gone - what's the way people build custom images now?
> Or is
> >> > that gone with just more memory and more disk being normal??
> >> >
> >> >
> >> > On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Hi Sanjiva,
> >> >>
> >> >> Vagrant works on top of an existing image (box). There are plenty of
> >> >> boxes for vagrant. Ubuntu for example provides vagrant boxes [1],
> although
> >> >> the disk size is a little small to be useful. Opscode also
> provide some
> >> >> pretty good boxes [2]. If these still don't meet your needs, you can
> copy
> >> >> the packer definitions from opscode and modify them to build your
> own box
> >> >> from scratch [3]. Packer is definitely worth a look too.
> >> >>
> >> >> Many thanks,
> >> >>
> >> >> Chris
> >> >>
> >> >> ---
> >> >> [1] http://cloud-images.ubuntu.com/vagrant/
> >> >> [2] https://github.com/opscode/bento
> >> >> [3] https://github.com/opscode/bento/tree/master/packer
> >> >> [4] http://packer.io
> >> >>
> >> >> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com>
> wrote:
> >> >>>
> >> >>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts
> as
> >> >>> well!
> >> >>>
> >> >>> I'm not familiar with vagrant - just checking it out. Does it build
> a
> >> >>> VM image or does it set up the environment to run the image?
> >> >>>
> >> >>> Sanjiva.
> >> >>>
> >> >>>
> >> >>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
> >> >>> wrote:
> >> >>>>
> >> >>>> Hi Sanjiva,
> >> >>>>
> >> >>>> For VM images, vagrant makes life very easy for users; setting up
> >> >>>> disks, setting up network cards, setting up memory, configuring
> guest proxy
> >> >>>> settings, running provisioning scripts, etc.
> >> >>>>
> >> >>>> I am working on a vagrant setup of cloudstack + Stratos. My
> project
> >> >>>> is here [1]. It isn't ready for general use yet, but I'm making
> good
> >> >>>> progress. Although my scripts are buggy, with a few commands I can
> >> >>>> checkout, build and provision a cloudstack developer environment.
> I am now
> >> >>>> working on the scripts to do the same for Stratos.
> >> >>>>
> >> >>>> Initially, the memory requirements will be high on my environment,
> >> >>>> but for me the first goal is automation, the next goal will be
> efficiency.
> >> >>>>
> >> >>>> Many thanks,
> >> >>>> Chris
> >> >>>>
> >> >>>> ---
> >> >>>> [1] https://github.com/snowch/devcloud-script
> >> >>>>
> >> >>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com>
> wrote:
> >> >>>>>
> >> >>>>> I think right now we need to focus on getting a single trivial
> >> >>>>> server mechanism to be able to run Stratos without too much of
> stuff having
> >> >>>>> to be set up. I'd love to see two developer distros:
> >> >>>>>
> >> >>>>> - a VM image that has everything in it and runs in under 4GB with
> >> >>>>> OpenStack + Docker. It doesn't matter whether this uses one
> Carbon server to
> >> >>>>> run it all or whether we use RabbitMQ or other AMQP broker.
> (Carbon stuff
> >> >>>>> HAS to run in one server - else its a bug in those products .. so
> the
> >> >>>>> decision should not be based on ability to run in one JVM but
> rather just
> >> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 -
> I think
> >> >>>>> we're nearly there for it.
> >> >>>>>
> >> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
> >> >>>>> plugin to jClouds that spins up Docker images as processes and
> there's one
> >> >>>>> JVM that works as the SM+CC+LB+AS+all. Thus the download becomes
> one JVM
> >> >>>>> plus a URL to a Docker image registry from which the images are
> booted up
> >> >>>>> and run (obviously a local registry will do better). We don't
> have this
> >> >>>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its
> not that
> >> >>>>> hard to make it work).
> >> >>>>>
> >> >>>>> For production deployments obviously this one server stuff is
> >> >>>>> nonsense .. so we need to have full decoupled distributed
> execution. For
> >> >>>>> that we should ship puppet scripts to get them up and running
> plus maybe
> >> >>>>> Boto scripts for someone to get it all up on EC2 with one
> command. Again its
> >> >>>>> totally fine to use whatever broker here and whatever other
> pluggable
> >> >>>>> components people want to use (and we need to make sure all the
> parts are
> >> >>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
> >> >>>>>
> >> >>>>> Makes sense?
> >> >>>>>
> >> >>>>> Sanjiva.
> >> >>>>>
> >> >>>>>
> >> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
> >> >>>>> <pr...@gmail.com> wrote:
> >> >>>>>>
> >> >>>>>> Hi Chris,
> >> >>>>>>
> >> >>>>>> Yes good point. Other day Azeez did the same suggestion.
> >> >>>>>>
> >> >>>>>> Thanks
> >> >>>>>>
> >> >>>>>> --Pradeep
> >> >>>>>> sent from my phone
> >> >>>>>>
> >> >>>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com>
> wrote:
> >> >>>>>>>
> >> >>>>>>> Hi Pradeep - I don't know enough about how the profiles work to
> >> >>>>>>> have a
> >> >>>>>>> view on that :(
> >> >>>>>>>
> >> >>>>>>> One thing I'm wondering though is how much memory will be saved
> if
> >> >>>>>>> we
> >> >>>>>>> use RabbitMQ (or another MQ) instead of MB?
> >> >>>>>>>
> >> >>>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
> >> >>>>>>> <pr...@gmail.com> wrote:
> >> >>>>>>> > btw,
> >> >>>>>>> >
> >> >>>>>>> > Now im working on MB and CEP bits.
> >> >>>>>>> >
> >> >>>>>>> > IMHO, we should not create MB and CEP only profiles in
> stratos.
> >> >>>>>>> > However,
> >> >>>>>>> > adding MB/CEP features (the ones that we use) to default
> profile
> >> >>>>>>> > (the
> >> >>>>>>> > profile that has all) makes sense.
> >> >>>>>>> >
> >> >>>>>>> > WDYT?
> >> >>>>>>> >
> >> >>>>>>> > Are we all on same page..
> >> >>>>>>> >
> >> >>>>>>> > thanks
> >> >>>>>>> >
> >> >>>>>>> >
> >> >>>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow
> >> >>>>>>> > <ch...@gmail.com> wrote:
> >> >>>>>>> >>
> >> >>>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to
> your
> >> >>>>>>> >> findings!
> >> >>>>>>> >>
> >> >>>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
> >> >>>>>>> >> <pr...@gmail.com>
> >> >>>>>>> >> wrote:
> >> >>>>>>> >> > Hi Guys,
> >> >>>>>>> >> >
> >> >>>>>>> >> > I started on the $subject. This thread is to track the
> >> >>>>>>> >> > progress..
> >> >>>>>>> >> >
> >> >>>>>>> >> > thanks,
> >> >>>>>>> >> >
> >> >>>>>>> >> >
> >> >>>>>>> >> > --
> >> >>>>>>> >> > Pradeep Fernando.
> >> >>>>>>> >> > http://pradeepfernando.blogspot.com/
> >> >>>>>>> >>
> >> >>>>>>> >>
> >> >>>>>>> >>
> >> >>>>>>> >> --
> >> >>>>>>> >> Check out my professional profile and connect with me on
> >> >>>>>>> >> LinkedIn.
> >> >>>>>>> >> http://lnkd.in/cw5k69
> >> >>>>>>> >
> >> >>>>>>> >
> >> >>>>>>> >
> >> >>>>>>> >
> >> >>>>>>> > --
> >> >>>>>>> > Pradeep Fernando.
> >> >>>>>>> > http://pradeepfernando.blogspot.com/
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> --
> >> >>>>>>> Check out my professional profile and connect with me on
> LinkedIn.
> >> >>>>>>> http://lnkd.in/cw5k69
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>> Sanjiva Weerawarana, Ph.D.
> >> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
> >> >>>>> 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1
> 650 265 8311
> >> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >> >>>>> Lean . Enterprise . Middleware
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Sanjiva Weerawarana, Ph.D.
> >> >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >> >>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345
> )
> >> >>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> 8311
> >> >>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >> >>> Lean . Enterprise . Middleware
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Sanjiva Weerawarana, Ph.D.
> >> > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >> > email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> >> > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >> > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >> > Lean . Enterprise . Middleware
> >
> >
> >
> >
> > --
> > __________________________________________________________________
> > Damitha Kumarage
> > http://people.apache.org/
> > __________________________________________________________________
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Hi Damitha,
If you haven't already, take a look at the Vagrant docs getting
started [1] - this will give you the gist of vagrant
Create a new directory for your vagrant project, and create a
Vagrantfile. This is what I am using:
Vagrant.configure("2") do |config|
# opscode vagrant boxes have 40Gb disk size which should be enough
for stratos
config.vm.box = "opscode-ubuntu-12.04"
config.vm.box_url =
"http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-12.04_chef-provisionerless.box"
# set the box hostname
config.vm.hostname = "paas.stratos.org"
# tweak the vm
config.vm.provider "virtualbox" do |v|
v.customize ["modifyvm", :id, "--memory", 5120]
end
# I have a bash script stratos_dev.sh in my vagrant project folder
# at the moment I run that script manually from inside the guest,
but when the script is finished, I will setup vagrant to automate it
fully
# see http://docs.vagrantup.com/v2/provisioning/shell.html for
more information on vagrant shell scripting
config.vm.provision "shell", inline: "ln -sf
/vagrant/stratos_dev.sh /home/vagrant/stratos_dev.sh", privileged:
false
end
My cloudstack+stratos project is here [2]. It may be easier for you
to follow the instructions at that page for running the stratos box.
Note that my stratos script is still a work-in-progress.
Is your host machine sitting behind a proxy server? If it is, you
will need a vagrant plugin to configure the guest to use the proxy.
Any questions, please give me a shout.
Many thanks,
Chris
---
[1] http://docs.vagrantup.com/v2/getting-started/
[2] https://github.com/snowch/devcloud-script/
On Tue, Mar 18, 2014 at 5:27 AM, damitha kumarage <da...@gmail.com> wrote:
> Hi Chris,
> In Vagrantdocs it says machines are provisioned on top of virtualbox. So,
> can vagrant spin up a virtualbox instance which run Stratos, starting from a
> vagrantfile? Since I have already created a virtualbox image which run
> Stratos in 5G memory(not yet with single jvm in which case it should reduce
> further.), could you please explain a bit how I can get this setup automate
> using vagrant (using a vagrantfile?).
>
> Damitha
>
>
> On Mon, Mar 17, 2014 at 1:08 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> Packer allows you to control most aspects of image creation, but AFAIK
>> rely on automating the distro's installation mechanism (e.g. Debian preseed
>> or red hat kick start). During the installation you start the guest OS so
>> you can add and remove packages as you please. For example, on the
>> cloudstack image, I scripted replacing the standard kernel with the xen
>> kernel packages, and rebooted during the install to pick up the new kernel
>> to perform other xen dependent setup. When I ran into issues early on with
>> xen, I was considering building the kernel from source. There is a lot of
>> flexibility.
>>
>> Vagrant and packer also work with docker although I haven't tried that
>> yet.
>>
>> In terms of Stratos, I have a vision forming that using vagrant and packer
>> we could build images for different environments (aws, virtual box, docker,
>> etc) and orchestrate the setup of stratos in those environments using
>> vagrant - with the potential for reusing the stratos setup scripts between
>> those environments. However, one step at a time, starting with vagrant to
>> setup cloudstack+stratos.
>>
>> Cheers,
>>
>> Chris
>>
>> On 17 Mar 2014 00:47, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>> >
>> > Interesting ... it would be cool to combine these with something like
>> > rPath to build a minimal Linux image with just the exact bits in it. Looks
>> > like rPath is gone - what's the way people build custom images now? Or is
>> > that gone with just more memory and more disk being normal??
>> >
>> >
>> > On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
>> > wrote:
>> >>
>> >> Hi Sanjiva,
>> >>
>> >> Vagrant works on top of an existing image (box). There are plenty of
>> >> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
>> >> the disk size is a little small to be useful. Opscode also provide some
>> >> pretty good boxes [2]. If these still don't meet your needs, you can copy
>> >> the packer definitions from opscode and modify them to build your own box
>> >> from scratch [3]. Packer is definitely worth a look too.
>> >>
>> >> Many thanks,
>> >>
>> >> Chris
>> >>
>> >> ---
>> >> [1] http://cloud-images.ubuntu.com/vagrant/
>> >> [2] https://github.com/opscode/bento
>> >> [3] https://github.com/opscode/bento/tree/master/packer
>> >> [4] http://packer.io
>> >>
>> >> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>> >>>
>> >>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>> >>> well!
>> >>>
>> >>> I'm not familiar with vagrant - just checking it out. Does it build a
>> >>> VM image or does it set up the environment to run the image?
>> >>>
>> >>> Sanjiva.
>> >>>
>> >>>
>> >>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi Sanjiva,
>> >>>>
>> >>>> For VM images, vagrant makes life very easy for users; setting up
>> >>>> disks, setting up network cards, setting up memory, configuring guest proxy
>> >>>> settings, running provisioning scripts, etc.
>> >>>>
>> >>>> I am working on a vagrant setup of cloudstack + Stratos. My project
>> >>>> is here [1]. It isn't ready for general use yet, but I'm making good
>> >>>> progress. Although my scripts are buggy, with a few commands I can
>> >>>> checkout, build and provision a cloudstack developer environment. I am now
>> >>>> working on the scripts to do the same for Stratos.
>> >>>>
>> >>>> Initially, the memory requirements will be high on my environment,
>> >>>> but for me the first goal is automation, the next goal will be efficiency.
>> >>>>
>> >>>> Many thanks,
>> >>>> Chris
>> >>>>
>> >>>> ---
>> >>>> [1] https://github.com/snowch/devcloud-script
>> >>>>
>> >>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>> >>>>>
>> >>>>> I think right now we need to focus on getting a single trivial
>> >>>>> server mechanism to be able to run Stratos without too much of stuff having
>> >>>>> to be set up. I'd love to see two developer distros:
>> >>>>>
>> >>>>> - a VM image that has everything in it and runs in under 4GB with
>> >>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server to
>> >>>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon stuff
>> >>>>> HAS to run in one server - else its a bug in those products .. so the
>> >>>>> decision should not be based on ability to run in one JVM but rather just
>> >>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>> >>>>> we're nearly there for it.
>> >>>>>
>> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
>> >>>>> plugin to jClouds that spins up Docker images as processes and there's one
>> >>>>> JVM that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
>> >>>>> plus a URL to a Docker image registry from which the images are booted up
>> >>>>> and run (obviously a local registry will do better). We don't have this
>> >>>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>> >>>>> hard to make it work).
>> >>>>>
>> >>>>> For production deployments obviously this one server stuff is
>> >>>>> nonsense .. so we need to have full decoupled distributed execution. For
>> >>>>> that we should ship puppet scripts to get them up and running plus maybe
>> >>>>> Boto scripts for someone to get it all up on EC2 with one command. Again its
>> >>>>> totally fine to use whatever broker here and whatever other pluggable
>> >>>>> components people want to use (and we need to make sure all the parts are
>> >>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>> >>>>>
>> >>>>> Makes sense?
>> >>>>>
>> >>>>> Sanjiva.
>> >>>>>
>> >>>>>
>> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando
>> >>>>> <pr...@gmail.com> wrote:
>> >>>>>>
>> >>>>>> Hi Chris,
>> >>>>>>
>> >>>>>> Yes good point. Other day Azeez did the same suggestion.
>> >>>>>>
>> >>>>>> Thanks
>> >>>>>>
>> >>>>>> --Pradeep
>> >>>>>> sent from my phone
>> >>>>>>
>> >>>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>> >>>>>>>
>> >>>>>>> Hi Pradeep - I don't know enough about how the profiles work to
>> >>>>>>> have a
>> >>>>>>> view on that :(
>> >>>>>>>
>> >>>>>>> One thing I'm wondering though is how much memory will be saved if
>> >>>>>>> we
>> >>>>>>> use RabbitMQ (or another MQ) instead of MB?
>> >>>>>>>
>> >>>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>> >>>>>>> <pr...@gmail.com> wrote:
>> >>>>>>> > btw,
>> >>>>>>> >
>> >>>>>>> > Now im working on MB and CEP bits.
>> >>>>>>> >
>> >>>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>> >>>>>>> > However,
>> >>>>>>> > adding MB/CEP features (the ones that we use) to default profile
>> >>>>>>> > (the
>> >>>>>>> > profile that has all) makes sense.
>> >>>>>>> >
>> >>>>>>> > WDYT?
>> >>>>>>> >
>> >>>>>>> > Are we all on same page..
>> >>>>>>> >
>> >>>>>>> > thanks
>> >>>>>>> >
>> >>>>>>> >
>> >>>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow
>> >>>>>>> > <ch...@gmail.com> wrote:
>> >>>>>>> >>
>> >>>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> >>>>>>> >> findings!
>> >>>>>>> >>
>> >>>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>> >>>>>>> >> <pr...@gmail.com>
>> >>>>>>> >> wrote:
>> >>>>>>> >> > Hi Guys,
>> >>>>>>> >> >
>> >>>>>>> >> > I started on the $subject. This thread is to track the
>> >>>>>>> >> > progress..
>> >>>>>>> >> >
>> >>>>>>> >> > thanks,
>> >>>>>>> >> >
>> >>>>>>> >> >
>> >>>>>>> >> > --
>> >>>>>>> >> > Pradeep Fernando.
>> >>>>>>> >> > http://pradeepfernando.blogspot.com/
>> >>>>>>> >>
>> >>>>>>> >>
>> >>>>>>> >>
>> >>>>>>> >> --
>> >>>>>>> >> Check out my professional profile and connect with me on
>> >>>>>>> >> LinkedIn.
>> >>>>>>> >> http://lnkd.in/cw5k69
>> >>>>>>> >
>> >>>>>>> >
>> >>>>>>> >
>> >>>>>>> >
>> >>>>>>> > --
>> >>>>>>> > Pradeep Fernando.
>> >>>>>>> > http://pradeepfernando.blogspot.com/
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Check out my professional profile and connect with me on LinkedIn.
>> >>>>>>> http://lnkd.in/cw5k69
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Sanjiva Weerawarana, Ph.D.
>> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
>> >>>>> 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >>>>> Lean . Enterprise . Middleware
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Sanjiva Weerawarana, Ph.D.
>> >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> >>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> >>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> >>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> >>> Lean . Enterprise . Middleware
>> >
>> >
>> >
>> >
>> > --
>> > Sanjiva Weerawarana, Ph.D.
>> > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> > email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> > Lean . Enterprise . Middleware
>
>
>
>
> --
> __________________________________________________________________
> Damitha Kumarage
> http://people.apache.org/
> __________________________________________________________________
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by damitha kumarage <da...@gmail.com>.
Hi Chris,
In Vagrantdocs it says machines are provisioned on top of virtualbox. So,
can vagrant spin up a virtualbox instance which run Stratos, starting from
a vagrantfile? Since I have already created a virtualbox image which run
Stratos in 5G memory(not yet with single jvm in which case it should reduce
further.), could you please explain a bit how I can get this setup automate
using vagrant (using a vagrantfile?).
Damitha
On Mon, Mar 17, 2014 at 1:08 PM, chris snow <ch...@gmail.com> wrote:
> Hi Sanjiva,
>
> Packer allows you to control most aspects of image creation, but AFAIK
> rely on automating the distro's installation mechanism (e.g. Debian preseed
> or red hat kick start). During the installation you start the guest OS so
> you can add and remove packages as you please. For example, on the
> cloudstack image, I scripted replacing the standard kernel with the xen
> kernel packages, and rebooted during the install to pick up the new kernel
> to perform other xen dependent setup. When I ran into issues early on with
> xen, I was considering building the kernel from source. There is a lot of
> flexibility.
>
> Vagrant and packer also work with docker although I haven't tried that
> yet.
>
> In terms of Stratos, I have a vision forming that using vagrant and packer
> we could build images for different environments (aws, virtual box, docker,
> etc) and orchestrate the setup of stratos in those environments using
> vagrant - with the potential for reusing the stratos setup scripts between
> those environments. However, one step at a time, starting with vagrant to
> setup cloudstack+stratos.
>
> Cheers,
>
> Chris
>
> On 17 Mar 2014 00:47, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >
> > Interesting ... it would be cool to combine these with something like
> rPath to build a minimal Linux image with just the exact bits in it. Looks
> like rPath is gone - what's the way people build custom images now? Or is
> that gone with just more memory and more disk being normal??
> >
> >
> > On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com>
> wrote:
> >>
> >> Hi Sanjiva,
> >>
> >> Vagrant works on top of an existing image (box). There are plenty of
> boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
> the disk size is a little small to be useful. Opscode also provide some
> pretty good boxes [2]. If these still don't meet your needs, you can copy
> the packer definitions from opscode and modify them to build your own box
> from scratch [3]. Packer is definitely worth a look too.
> >>
> >> Many thanks,
> >>
> >> Chris
> >>
> >> ---
> >> [1] http://cloud-images.ubuntu.com/vagrant/
> >> [2] https://github.com/opscode/bento
> >> [3] https://github.com/opscode/bento/tree/master/packer
> >> [4] http://packer.io
> >>
> >> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >>>
> >>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
> well!
> >>>
> >>> I'm not familiar with vagrant - just checking it out. Does it build a
> VM image or does it set up the environment to run the image?
> >>>
> >>> Sanjiva.
> >>>
> >>>
> >>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com>
> wrote:
> >>>>
> >>>> Hi Sanjiva,
> >>>>
> >>>> For VM images, vagrant makes life very easy for users; setting up
> disks, setting up network cards, setting up memory, configuring guest proxy
> settings, running provisioning scripts, etc.
> >>>>
> >>>> I am working on a vagrant setup of cloudstack + Stratos. My project
> is here [1]. It isn't ready for general use yet, but I'm making good
> progress. Although my scripts are buggy, with a few commands I can
> checkout, build and provision a cloudstack developer environment. I am now
> working on the scripts to do the same for Stratos.
> >>>>
> >>>> Initially, the memory requirements will be high on my environment,
> but for me the first goal is automation, the next goal will be efficiency.
> >>>>
> >>>> Many thanks,
> >>>> Chris
> >>>>
> >>>> ---
> >>>> [1] https://github.com/snowch/devcloud-script
> >>>>
> >>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> >>>>>
> >>>>> I think right now we need to focus on getting a single trivial
> server mechanism to be able to run Stratos without too much of stuff having
> to be set up. I'd love to see two developer distros:
> >>>>>
> >>>>> - a VM image that has everything in it and runs in under 4GB with
> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff HAS to run in one server - else its a bug in those products .. so the
> decision should not be based on ability to run in one JVM but rather just
> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
> we're nearly there for it.
> >>>>>
> >>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
> plugin to jClouds that spins up Docker images as processes and there's one
> JVM that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
> plus a URL to a Docker image registry from which the images are booted up
> and run (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
> hard to make it work).
> >>>>>
> >>>>> For production deployments obviously this one server stuff is
> nonsense .. so we need to have full decoupled distributed execution. For
> that we should ship puppet scripts to get them up and running plus maybe
> Boto scripts for someone to get it all up on EC2 with one command. Again
> its totally fine to use whatever broker here and whatever other pluggable
> components people want to use (and we need to make sure all the parts are
> pluggable: load balancers, message broker, the CEP engine, etc.)).
> >>>>>
> >>>>> Makes sense?
> >>>>>
> >>>>> Sanjiva.
> >>>>>
> >>>>>
> >>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <
> pradeepfn@gmail.com> wrote:
> >>>>>>
> >>>>>> Hi Chris,
> >>>>>>
> >>>>>> Yes good point. Other day Azeez did the same suggestion.
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>> --Pradeep
> >>>>>> sent from my phone
> >>>>>>
> >>>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Hi Pradeep - I don't know enough about how the profiles work to
> have a
> >>>>>>> view on that :(
> >>>>>>>
> >>>>>>> One thing I'm wondering though is how much memory will be saved if
> we
> >>>>>>> use RabbitMQ (or another MQ) instead of MB?
> >>>>>>>
> >>>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
> pradeepfn@gmail.com> wrote:
> >>>>>>> > btw,
> >>>>>>> >
> >>>>>>> > Now im working on MB and CEP bits.
> >>>>>>> >
> >>>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
> However,
> >>>>>>> > adding MB/CEP features (the ones that we use) to default profile
> (the
> >>>>>>> > profile that has all) makes sense.
> >>>>>>> >
> >>>>>>> > WDYT?
> >>>>>>> >
> >>>>>>> > Are we all on same page..
> >>>>>>> >
> >>>>>>> > thanks
> >>>>>>> >
> >>>>>>> >
> >>>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
> wrote:
> >>>>>>> >>
> >>>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
> findings!
> >>>>>>> >>
> >>>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
> pradeepfn@gmail.com>
> >>>>>>> >> wrote:
> >>>>>>> >> > Hi Guys,
> >>>>>>> >> >
> >>>>>>> >> > I started on the $subject. This thread is to track the
> progress..
> >>>>>>> >> >
> >>>>>>> >> > thanks,
> >>>>>>> >> >
> >>>>>>> >> >
> >>>>>>> >> > --
> >>>>>>> >> > Pradeep Fernando.
> >>>>>>> >> > http://pradeepfernando.blogspot.com/
> >>>>>>> >>
> >>>>>>> >>
> >>>>>>> >>
> >>>>>>> >> --
> >>>>>>> >> Check out my professional profile and connect with me on
> LinkedIn.
> >>>>>>> >> http://lnkd.in/cw5k69
> >>>>>>> >
> >>>>>>> >
> >>>>>>> >
> >>>>>>> >
> >>>>>>> > --
> >>>>>>> > Pradeep Fernando.
> >>>>>>> > http://pradeepfernando.blogspot.com/
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Check out my professional profile and connect with me on LinkedIn.
> >>>>>>> http://lnkd.in/cw5k69
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sanjiva Weerawarana, Ph.D.
> >>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214
> 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265
> 8311
> >>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>>>> Lean . Enterprise . Middleware
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Sanjiva Weerawarana, Ph.D.
> >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> >>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> >>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> >>> Lean . Enterprise . Middleware
> >
> >
> >
> >
> > --
> > Sanjiva Weerawarana, Ph.D.
> > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> > email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> > Lean . Enterprise . Middleware
>
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Hi Sanjiva,
Packer allows you to control most aspects of image creation, but AFAIK rely
on automating the distro's installation mechanism (e.g. Debian preseed or
red hat kick start). During the installation you start the guest OS so you
can add and remove packages as you please. For example, on the cloudstack
image, I scripted replacing the standard kernel with the xen kernel
packages, and rebooted during the install to pick up the new kernel to
perform other xen dependent setup. When I ran into issues early on with
xen, I was considering building the kernel from source. There is a lot of
flexibility.
Vagrant and packer also work with docker although I haven't tried that
yet.
In terms of Stratos, I have a vision forming that using vagrant and packer
we could build images for different environments (aws, virtual box, docker,
etc) and orchestrate the setup of stratos in those environments using
vagrant - with the potential for reusing the stratos setup scripts between
those environments. However, one step at a time, starting with vagrant to
setup cloudstack+stratos.
Cheers,
Chris
On 17 Mar 2014 00:47, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>
> Interesting ... it would be cool to combine these with something like
rPath to build a minimal Linux image with just the exact bits in it. Looks
like rPath is gone - what's the way people build custom images now? Or is
that gone with just more memory and more disk being normal??
>
>
> On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> Vagrant works on top of an existing image (box). There are plenty of
boxes for vagrant. Ubuntu for example provides vagrant boxes [1], although
the disk size is a little small to be useful. Opscode also provide some
pretty good boxes [2]. If these still don't meet your needs, you can copy
the packer definitions from opscode and modify them to build your own box
from scratch [3]. Packer is definitely worth a look too.
>>
>> Many thanks,
>>
>> Chris
>>
>> ---
>> [1] http://cloud-images.ubuntu.com/vagrant/
>> [2] https://github.com/opscode/bento
>> [3] https://github.com/opscode/bento/tree/master/packer
>> [4] http://packer.io
>>
>> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
well!
>>>
>>> I'm not familiar with vagrant - just checking it out. Does it build a
VM image or does it set up the environment to run the image?
>>>
>>> Sanjiva.
>>>
>>>
>>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>>>
>>>> Hi Sanjiva,
>>>>
>>>> For VM images, vagrant makes life very easy for users; setting up
disks, setting up network cards, setting up memory, configuring guest proxy
settings, running provisioning scripts, etc.
>>>>
>>>> I am working on a vagrant setup of cloudstack + Stratos. My project
is here [1]. It isn't ready for general use yet, but I'm making good
progress. Although my scripts are buggy, with a few commands I can
checkout, build and provision a cloudstack developer environment. I am now
working on the scripts to do the same for Stratos.
>>>>
>>>> Initially, the memory requirements will be high on my environment, but
for me the first goal is automation, the next goal will be efficiency.
>>>>
>>>> Many thanks,
>>>> Chris
>>>>
>>>> ---
>>>> [1] https://github.com/snowch/devcloud-script
>>>>
>>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>>>
>>>>> I think right now we need to focus on getting a single trivial server
mechanism to be able to run Stratos without too much of stuff having to be
set up. I'd love to see two developer distros:
>>>>>
>>>>> - a VM image that has everything in it and runs in under 4GB with
OpenStack + Docker. It doesn't matter whether this uses one Carbon server
to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
stuff HAS to run in one server - else its a bug in those products .. so the
decision should not be based on ability to run in one JVM but rather just
making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
we're nearly there for it.
>>>>>
>>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct
plugin to jClouds that spins up Docker images as processes and there's one
JVM that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM
plus a URL to a Docker image registry from which the images are booted up
and run (obviously a local registry will do better). We don't have this
no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
hard to make it work).
>>>>>
>>>>> For production deployments obviously this one server stuff is
nonsense .. so we need to have full decoupled distributed execution. For
that we should ship puppet scripts to get them up and running plus maybe
Boto scripts for someone to get it all up on EC2 with one command. Again
its totally fine to use whatever broker here and whatever other pluggable
components people want to use (and we need to make sure all the parts are
pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>>>
>>>>> Makes sense?
>>>>>
>>>>> Sanjiva.
>>>>>
>>>>>
>>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
wrote:
>>>>>>
>>>>>> Hi Chris,
>>>>>>
>>>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> --Pradeep
>>>>>> sent from my phone
>>>>>>
>>>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi Pradeep - I don't know enough about how the profiles work to
have a
>>>>>>> view on that :(
>>>>>>>
>>>>>>> One thing I'm wondering though is how much memory will be saved if
we
>>>>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>>
>>>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
pradeepfn@gmail.com> wrote:
>>>>>>> > btw,
>>>>>>> >
>>>>>>> > Now im working on MB and CEP bits.
>>>>>>> >
>>>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
However,
>>>>>>> > adding MB/CEP features (the ones that we use) to default profile
(the
>>>>>>> > profile that has all) makes sense.
>>>>>>> >
>>>>>>> > WDYT?
>>>>>>> >
>>>>>>> > Are we all on same page..
>>>>>>> >
>>>>>>> > thanks
>>>>>>> >
>>>>>>> >
>>>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
wrote:
>>>>>>> >>
>>>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
findings!
>>>>>>> >>
>>>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
pradeepfn@gmail.com>
>>>>>>> >> wrote:
>>>>>>> >> > Hi Guys,
>>>>>>> >> >
>>>>>>> >> > I started on the $subject. This thread is to track the
progress..
>>>>>>> >> >
>>>>>>> >> > thanks,
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> > --
>>>>>>> >> > Pradeep Fernando.
>>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> --
>>>>>>> >> Check out my professional profile and connect with me on
LinkedIn.
>>>>>>> >> http://lnkd.in/cw5k69
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > Pradeep Fernando.
>>>>>>> > http://pradeepfernando.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>>> http://lnkd.in/cw5k69
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sanjiva Weerawarana, Ph.D.
>>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>>> Lean . Enterprise . Middleware
>>>
>>>
>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
Re: Running stratos in one JVM
Posted by Sanjiva Weerawarana <sa...@wso2.com>.
Interesting ... it would be cool to combine these with something like rPath
to build a minimal Linux image with just the exact bits in it. Looks like
rPath is gone - what's the way people build custom images now? Or is that
gone with just more memory and more disk being normal??
On Sun, Mar 16, 2014 at 10:34 PM, chris snow <ch...@gmail.com> wrote:
> Hi Sanjiva,
>
> Vagrant works on top of an existing image (box). There are plenty of boxes
> for vagrant. Ubuntu for example provides vagrant boxes [1], although the
> disk size is a little small to be useful. Opscode also provide some
> pretty good boxes [2]. If these still don't meet your needs, you can copy
> the packer definitions from opscode and modify them to build your own box
> from scratch [3]. Packer is definitely worth a look too.
>
> Many thanks,
>
> Chris
>
> ---
> [1] http://cloud-images.ubuntu.com/vagrant/
> [2] https://github.com/opscode/bento
> [3] https://github.com/opscode/bento/tree/master/packer
> [4] http://packer.io
> On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>
>> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
>> well!
>>
>> I'm not familiar with vagrant - just checking it out. Does it build a VM
>> image or does it set up the environment to run the image?
>>
>> Sanjiva.
>>
>>
>> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>
>>> Hi Sanjiva,
>>>
>>> For VM images, vagrant makes life very easy for users; setting up disks,
>>> setting up network cards, setting up memory, configuring guest proxy
>>> settings, running provisioning scripts, etc.
>>>
>>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>>> here [1]. It isn't ready for general use yet, but I'm making good
>>> progress. Although my scripts are buggy, with a few commands I can
>>> checkout, build and provision a cloudstack developer environment. I am now
>>> working on the scripts to do the same for Stratos.
>>>
>>> Initially, the memory requirements will be high on my environment, but
>>> for me the first goal is automation, the next goal will be efficiency.
>>>
>>> Many thanks,
>>> Chris
>>>
>>> ---
>>> [1] https://github.com/snowch/devcloud-script
>>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>>> I think right now we need to focus on getting a single trivial server
>>>> mechanism to be able to run Stratos without too much of stuff having to be
>>>> set up. I'd love to see two developer distros:
>>>>
>>>> - a VM image that has everything in it and runs in under 4GB with
>>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>>>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>>>> stuff HAS to run in one server - else its a bug in those products .. so the
>>>> decision should not be based on ability to run in one JVM but rather just
>>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>>> we're nearly there for it.
>>>>
>>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>>> to jClouds that spins up Docker images as processes and there's one JVM
>>>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>>>> URL to a Docker image registry from which the images are booted up and run
>>>> (obviously a local registry will do better). We don't have this
>>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>>>> hard to make it work).
>>>>
>>>> For production deployments obviously this one server stuff is nonsense
>>>> .. so we need to have full decoupled distributed execution. For that we
>>>> should ship puppet scripts to get them up and running plus maybe Boto
>>>> scripts for someone to get it all up on EC2 with one command. Again its
>>>> totally fine to use whatever broker here and whatever other pluggable
>>>> components people want to use (and we need to make sure all the parts are
>>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>>
>>>> Makes sense?
>>>>
>>>> Sanjiva.
>>>>
>>>>
>>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>>>
>>>>> Hi Chris,
>>>>>
>>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>>
>>>>> Thanks
>>>>>
>>>>> --Pradeep
>>>>> sent from my phone
>>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>>
>>>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>>>> view on that :(
>>>>>>
>>>>>> One thing I'm wondering though is how much memory will be saved if we
>>>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>>
>>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
>>>>>> pradeepfn@gmail.com> wrote:
>>>>>> > btw,
>>>>>> >
>>>>>> > Now im working on MB and CEP bits.
>>>>>> >
>>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>>>> However,
>>>>>> > adding MB/CEP features (the ones that we use) to default profile
>>>>>> (the
>>>>>> > profile that has all) makes sense.
>>>>>> >
>>>>>> > WDYT?
>>>>>> >
>>>>>> > Are we all on same page..
>>>>>> >
>>>>>> > thanks
>>>>>> >
>>>>>> >
>>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>>>> findings!
>>>>>> >>
>>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>>>>> pradeepfn@gmail.com>
>>>>>> >> wrote:
>>>>>> >> > Hi Guys,
>>>>>> >> >
>>>>>> >> > I started on the $subject. This thread is to track the progress..
>>>>>> >> >
>>>>>> >> > thanks,
>>>>>> >> >
>>>>>> >> >
>>>>>> >> > --
>>>>>> >> > Pradeep Fernando.
>>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> --
>>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>>> >> http://lnkd.in/cw5k69
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > Pradeep Fernando.
>>>>>> > http://pradeepfernando.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>>> http://lnkd.in/cw5k69
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>>> Lean . Enterprise . Middleware
>>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Hi Sanjiva,
Vagrant works on top of an existing image (box). There are plenty of boxes
for vagrant. Ubuntu for example provides vagrant boxes [1], although the
disk size is a little small to be useful. Opscode also provide some
pretty good boxes [2]. If these still don't meet your needs, you can copy
the packer definitions from opscode and modify them to build your own box
from scratch [3]. Packer is definitely worth a look too.
Many thanks,
Chris
---
[1] http://cloud-images.ubuntu.com/vagrant/
[2] https://github.com/opscode/bento
[3] https://github.com/opscode/bento/tree/master/packer
[4] http://packer.io
On 16 Mar 2014 15:27, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as
> well!
>
> I'm not familiar with vagrant - just checking it out. Does it build a VM
> image or does it set up the environment to run the image?
>
> Sanjiva.
>
>
> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>
>> Hi Sanjiva,
>>
>> For VM images, vagrant makes life very easy for users; setting up disks,
>> setting up network cards, setting up memory, configuring guest proxy
>> settings, running provisioning scripts, etc.
>>
>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>> here [1]. It isn't ready for general use yet, but I'm making good
>> progress. Although my scripts are buggy, with a few commands I can
>> checkout, build and provision a cloudstack developer environment. I am now
>> working on the scripts to do the same for Stratos.
>>
>> Initially, the memory requirements will be high on my environment, but
>> for me the first goal is automation, the next goal will be efficiency.
>>
>> Many thanks,
>> Chris
>>
>> ---
>> [1] https://github.com/snowch/devcloud-script
>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>
>>> I think right now we need to focus on getting a single trivial server
>>> mechanism to be able to run Stratos without too much of stuff having to be
>>> set up. I'd love to see two developer distros:
>>>
>>> - a VM image that has everything in it and runs in under 4GB with
>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>>> stuff HAS to run in one server - else its a bug in those products .. so the
>>> decision should not be based on ability to run in one JVM but rather just
>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>> we're nearly there for it.
>>>
>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>> to jClouds that spins up Docker images as processes and there's one JVM
>>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>>> URL to a Docker image registry from which the images are booted up and run
>>> (obviously a local registry will do better). We don't have this
>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>>> hard to make it work).
>>>
>>> For production deployments obviously this one server stuff is nonsense
>>> .. so we need to have full decoupled distributed execution. For that we
>>> should ship puppet scripts to get them up and running plus maybe Boto
>>> scripts for someone to get it all up on EC2 with one command. Again its
>>> totally fine to use whatever broker here and whatever other pluggable
>>> components people want to use (and we need to make sure all the parts are
>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>
>>> Makes sense?
>>>
>>> Sanjiva.
>>>
>>>
>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>
>>>> Thanks
>>>>
>>>> --Pradeep
>>>> sent from my phone
>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>
>>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>>> view on that :(
>>>>>
>>>>> One thing I'm wondering though is how much memory will be saved if we
>>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>
>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com> wrote:
>>>>> > btw,
>>>>> >
>>>>> > Now im working on MB and CEP bits.
>>>>> >
>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>>> However,
>>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>>> > profile that has all) makes sense.
>>>>> >
>>>>> > WDYT?
>>>>> >
>>>>> > Are we all on same page..
>>>>> >
>>>>> > thanks
>>>>> >
>>>>> >
>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>>> findings!
>>>>> >>
>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com>
>>>>> >> wrote:
>>>>> >> > Hi Guys,
>>>>> >> >
>>>>> >> > I started on the $subject. This thread is to track the progress..
>>>>> >> >
>>>>> >> > thanks,
>>>>> >> >
>>>>> >> >
>>>>> >> > --
>>>>> >> > Pradeep Fernando.
>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>> >> http://lnkd.in/cw5k69
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Pradeep Fernando.
>>>>> > http://pradeepfernando.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>> http://lnkd.in/cw5k69
>>>>>
>>>>
>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
One other benefit to using vagrant is that the vagrant scripts can be
the living implementation of the wiki setup documents. If something
changes in the codebase that breaks the automated setup scripts, it is
a good indication that the wiki documents will be broken as well.
I've been thinking about setting up a jenkins vagrant job that
periodically runs vagrant to ensure nothing has broken the setup
steps.
On Sun, Mar 16, 2014 at 3:27 PM, Sanjiva Weerawarana <sa...@wso2.com> wrote:
> Hey Chris - that's awesome .. totally +1 for having vagrant scripts as well!
>
> I'm not familiar with vagrant - just checking it out. Does it build a VM
> image or does it set up the environment to run the image?
>
> Sanjiva.
>
>
> On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Sanjiva,
>>
>> For VM images, vagrant makes life very easy for users; setting up disks,
>> setting up network cards, setting up memory, configuring guest proxy
>> settings, running provisioning scripts, etc.
>>
>> I am working on a vagrant setup of cloudstack + Stratos. My project is
>> here [1]. It isn't ready for general use yet, but I'm making good progress.
>> Although my scripts are buggy, with a few commands I can checkout, build and
>> provision a cloudstack developer environment. I am now working on the
>> scripts to do the same for Stratos.
>>
>> Initially, the memory requirements will be high on my environment, but for
>> me the first goal is automation, the next goal will be efficiency.
>>
>> Many thanks,
>> Chris
>>
>> ---
>> [1] https://github.com/snowch/devcloud-script
>>
>> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>>>
>>> I think right now we need to focus on getting a single trivial server
>>> mechanism to be able to run Stratos without too much of stuff having to be
>>> set up. I'd love to see two developer distros:
>>>
>>> - a VM image that has everything in it and runs in under 4GB with
>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server to
>>> run it all or whether we use RabbitMQ or other AMQP broker. (Carbon stuff
>>> HAS to run in one server - else its a bug in those products .. so the
>>> decision should not be based on ability to run in one JVM but rather just
>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>> we're nearly there for it.
>>>
>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>> to jClouds that spins up Docker images as processes and there's one JVM that
>>> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
>>> to a Docker image registry from which the images are booted up and run
>>> (obviously a local registry will do better). We don't have this no-IaaS-IaaS
>>> yet so this can come maybe as 4.1.0 or whatever (its not that hard to make
>>> it work).
>>>
>>> For production deployments obviously this one server stuff is nonsense ..
>>> so we need to have full decoupled distributed execution. For that we should
>>> ship puppet scripts to get them up and running plus maybe Boto scripts for
>>> someone to get it all up on EC2 with one command. Again its totally fine to
>>> use whatever broker here and whatever other pluggable components people want
>>> to use (and we need to make sure all the parts are pluggable: load
>>> balancers, message broker, the CEP engine, etc.)).
>>>
>>> Makes sense?
>>>
>>> Sanjiva.
>>>
>>>
>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Chris,
>>>>
>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>
>>>> Thanks
>>>>
>>>> --Pradeep
>>>> sent from my phone
>>>>
>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>>
>>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>>> view on that :(
>>>>>
>>>>> One thing I'm wondering though is how much memory will be saved if we
>>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>
>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando
>>>>> <pr...@gmail.com> wrote:
>>>>> > btw,
>>>>> >
>>>>> > Now im working on MB and CEP bits.
>>>>> >
>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>>> > However,
>>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>>> > profile that has all) makes sense.
>>>>> >
>>>>> > WDYT?
>>>>> >
>>>>> > Are we all on same page..
>>>>> >
>>>>> > thanks
>>>>> >
>>>>> >
>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>>> > wrote:
>>>>> >>
>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>>> >> findings!
>>>>> >>
>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando
>>>>> >> <pr...@gmail.com>
>>>>> >> wrote:
>>>>> >> > Hi Guys,
>>>>> >> >
>>>>> >> > I started on the $subject. This thread is to track the progress..
>>>>> >> >
>>>>> >> > thanks,
>>>>> >> >
>>>>> >> >
>>>>> >> > --
>>>>> >> > Pradeep Fernando.
>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>> >> http://lnkd.in/cw5k69
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Pradeep Fernando.
>>>>> > http://pradeepfernando.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>> http://lnkd.in/cw5k69
>>>
>>>
>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700;
> cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by Sanjiva Weerawarana <sa...@wso2.com>.
Hey Chris - that's awesome .. totally +1 for having vagrant scripts as well!
I'm not familiar with vagrant - just checking it out. Does it build a VM
image or does it set up the environment to run the image?
Sanjiva.
On Sat, Mar 15, 2014 at 1:06 PM, chris snow <ch...@gmail.com> wrote:
> Hi Sanjiva,
>
> For VM images, vagrant makes life very easy for users; setting up disks,
> setting up network cards, setting up memory, configuring guest proxy
> settings, running provisioning scripts, etc.
>
> I am working on a vagrant setup of cloudstack + Stratos. My project is
> here [1]. It isn't ready for general use yet, but I'm making good
> progress. Although my scripts are buggy, with a few commands I can
> checkout, build and provision a cloudstack developer environment. I am now
> working on the scripts to do the same for Stratos.
>
> Initially, the memory requirements will be high on my environment, but for
> me the first goal is automation, the next goal will be efficiency.
>
> Many thanks,
> Chris
>
> ---
> [1] https://github.com/snowch/devcloud-script
> On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
>
>> I think right now we need to focus on getting a single trivial server
>> mechanism to be able to run Stratos without too much of stuff having to be
>> set up. I'd love to see two developer distros:
>>
>> - a VM image that has everything in it and runs in under 4GB with
>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>> stuff HAS to run in one server - else its a bug in those products .. so the
>> decision should not be based on ability to run in one JVM but rather just
>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>> we're nearly there for it.
>>
>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>> to jClouds that spins up Docker images as processes and there's one JVM
>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>> URL to a Docker image registry from which the images are booted up and run
>> (obviously a local registry will do better). We don't have this
>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>> hard to make it work).
>>
>> For production deployments obviously this one server stuff is nonsense ..
>> so we need to have full decoupled distributed execution. For that we should
>> ship puppet scripts to get them up and running plus maybe Boto scripts for
>> someone to get it all up on EC2 with one command. Again its totally fine to
>> use whatever broker here and whatever other pluggable components people
>> want to use (and we need to make sure all the parts are pluggable: load
>> balancers, message broker, the CEP engine, etc.)).
>>
>> Makes sense?
>>
>> Sanjiva.
>>
>>
>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> Hi Chris,
>>>
>>> Yes good point. Other day Azeez did the same suggestion.
>>>
>>> Thanks
>>>
>>> --Pradeep
>>> sent from my phone
>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>
>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>> view on that :(
>>>>
>>>> One thing I'm wondering though is how much memory will be saved if we
>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>
>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>>> wrote:
>>>> > btw,
>>>> >
>>>> > Now im working on MB and CEP bits.
>>>> >
>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>> However,
>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>> > profile that has all) makes sense.
>>>> >
>>>> > WDYT?
>>>> >
>>>> > Are we all on same page..
>>>> >
>>>> > thanks
>>>> >
>>>> >
>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>> findings!
>>>> >>
>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>>> pradeepfn@gmail.com>
>>>> >> wrote:
>>>> >> > Hi Guys,
>>>> >> >
>>>> >> > I started on the $subject. This thread is to track the progress..
>>>> >> >
>>>> >> > thanks,
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Pradeep Fernando.
>>>> >> > http://pradeepfernando.blogspot.com/
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>> >> http://lnkd.in/cw5k69
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Pradeep Fernando.
>>>> > http://pradeepfernando.blogspot.com/
>>>>
>>>>
>>>>
>>>> --
>>>> Check out my professional profile and connect with me on LinkedIn.
>>>> http://lnkd.in/cw5k69
>>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Hi Sanjiva,
For VM images, vagrant makes life very easy for users; setting up disks,
setting up network cards, setting up memory, configuring guest proxy
settings, running provisioning scripts, etc.
I am working on a vagrant setup of cloudstack + Stratos. My project is
here [1]. It isn't ready for general use yet, but I'm making good
progress. Although my scripts are buggy, with a few commands I can
checkout, build and provision a cloudstack developer environment. I am now
working on the scripts to do the same for Stratos.
Initially, the memory requirements will be high on my environment, but for
me the first goal is automation, the next goal will be efficiency.
Many thanks,
Chris
---
[1] https://github.com/snowch/devcloud-script
On 15 Mar 2014 06:24, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> I think right now we need to focus on getting a single trivial server
> mechanism to be able to run Stratos without too much of stuff having to be
> set up. I'd love to see two developer distros:
>
> - a VM image that has everything in it and runs in under 4GB with
> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff HAS to run in one server - else its a bug in those products .. so the
> decision should not be based on ability to run in one JVM but rather just
> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
> we're nearly there for it.
>
> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin to
> jClouds that spins up Docker images as processes and there's one JVM that
> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
> to a Docker image registry from which the images are booted up and run
> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
> hard to make it work).
>
> For production deployments obviously this one server stuff is nonsense ..
> so we need to have full decoupled distributed execution. For that we should
> ship puppet scripts to get them up and running plus maybe Boto scripts for
> someone to get it all up on EC2 with one command. Again its totally fine to
> use whatever broker here and whatever other pluggable components people
> want to use (and we need to make sure all the parts are pluggable: load
> balancers, message broker, the CEP engine, etc.)).
>
> Makes sense?
>
> Sanjiva.
>
>
> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Hi Chris,
>>
>> Yes good point. Other day Azeez did the same suggestion.
>>
>> Thanks
>>
>> --Pradeep
>> sent from my phone
>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>
>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>> view on that :(
>>>
>>> One thing I'm wondering though is how much memory will be saved if we
>>> use RabbitMQ (or another MQ) instead of MB?
>>>
>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>> > btw,
>>> >
>>> > Now im working on MB and CEP bits.
>>> >
>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>> However,
>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>> > profile that has all) makes sense.
>>> >
>>> > WDYT?
>>> >
>>> > Are we all on same page..
>>> >
>>> > thanks
>>> >
>>> >
>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>> >>
>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>> findings!
>>> >>
>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>> pradeepfn@gmail.com>
>>> >> wrote:
>>> >> > Hi Guys,
>>> >> >
>>> >> > I started on the $subject. This thread is to track the progress..
>>> >> >
>>> >> > thanks,
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Pradeep Fernando.
>>> >> > http://pradeepfernando.blogspot.com/
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Check out my professional profile and connect with me on LinkedIn.
>>> >> http://lnkd.in/cw5k69
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Pradeep Fernando.
>>> > http://pradeepfernando.blogspot.com/
>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
Re: Running stratos in one JVM
Posted by Lakmal Warusawithana <la...@wso2.com>.
Hi Sanjiva
On Sat, Mar 15, 2014 at 11:53 AM, Sanjiva Weerawarana <sa...@wso2.com>wrote:
> I think right now we need to focus on getting a single trivial server
> mechanism to be able to run Stratos without too much of stuff having to be
> set up. I'd love to see two developer distros:
>
> - a VM image that has everything in it and runs in under 4GB with
> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff HAS to run in one server - else its a bug in those products .. so the
> decision should not be based on ability to run in one JVM but rather just
> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
> we're nearly there for it.
>
Yes, already has running docker+openstack with Sratos alpha packs. It need
at least 5.2 GB RAM. But with this single JVM effort we can make it under
4GB. And it is pre configured virtual box image, its going to be very easy
for developers, beginners.
>
> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin to
> jClouds that spins up Docker images as processes and there's one JVM that
> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
> to a Docker image registry from which the images are booted up and run
> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
> hard to make it work).
>
+1 for make direct docker support in 4.1.0 release, with this we can
support bare-metal well as IaaS for Stratos. Also it will give two level of
auto scaling.
>
> For production deployments obviously this one server stuff is nonsense ..
> so we need to have full decoupled distributed execution. For that we should
> ship puppet scripts to get them up and running plus maybe Boto scripts for
> someone to get it all up on EC2 with one command. Again its totally fine to
> use whatever broker here and whatever other pluggable components people
> want to use (and we need to make sure all the parts are pluggable: load
> balancers, message broker, the CEP engine, etc.)).
>
> Makes sense?
>
> Sanjiva.
>
>
> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Hi Chris,
>>
>> Yes good point. Other day Azeez did the same suggestion.
>>
>> Thanks
>>
>> --Pradeep
>> sent from my phone
>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>
>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>> view on that :(
>>>
>>> One thing I'm wondering though is how much memory will be saved if we
>>> use RabbitMQ (or another MQ) instead of MB?
>>>
>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>> > btw,
>>> >
>>> > Now im working on MB and CEP bits.
>>> >
>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>> However,
>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>> > profile that has all) makes sense.
>>> >
>>> > WDYT?
>>> >
>>> > Are we all on same page..
>>> >
>>> > thanks
>>> >
>>> >
>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>> >>
>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>> findings!
>>> >>
>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>> pradeepfn@gmail.com>
>>> >> wrote:
>>> >> > Hi Guys,
>>> >> >
>>> >> > I started on the $subject. This thread is to track the progress..
>>> >> >
>>> >> > thanks,
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Pradeep Fernando.
>>> >> > http://pradeepfernando.blogspot.com/
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Check out my professional profile and connect with me on LinkedIn.
>>> >> http://lnkd.in/cw5k69
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Pradeep Fernando.
>>> > http://pradeepfernando.blogspot.com/
>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
--
Lakmal Warusawithana
Software Architect; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Running stratos in one JVM
Posted by damitha kumarage <da...@gmail.com>.
Hi Nirmal,
Great I woulld like to mentor that project
Damitha
On Tue, Mar 18, 2014 at 8:06 AM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi Damitha,
>
> Just noticed that there's a student interested in that project. Can you
> please assign that 'writing agent in Python' to you and be the mentor of it
> ?
>
>
> On Sun, Mar 16, 2014 at 10:24 AM, damitha kumarage <da...@gmail.com>wrote:
>
>> Hi Sanjiva,
>> Yes nicely formulated the requirement.
>> It is nice if we can make the 4.1.0 or whatever next release with agent
>> written in Python as well. Then the developer has the luxury of spinning up
>> many low memory cartridge instances in his environment. Still no body has
>> taken this as a GSoC project.
>>
>> Damitha
>>
>>
>> On Sat, Mar 15, 2014 at 11:53 AM, Sanjiva Weerawarana <sa...@wso2.com>wrote:
>>
>>> I think right now we need to focus on getting a single trivial server
>>> mechanism to be able to run Stratos without too much of stuff having to be
>>> set up. I'd love to see two developer distros:
>>>
>>> - a VM image that has everything in it and runs in under 4GB with
>>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>>> stuff HAS to run in one server - else its a bug in those products .. so the
>>> decision should not be based on ability to run in one JVM but rather just
>>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>>> we're nearly there for it.
>>>
>>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>>> to jClouds that spins up Docker images as processes and there's one JVM
>>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>>> URL to a Docker image registry from which the images are booted up and run
>>> (obviously a local registry will do better). We don't have this
>>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>>> hard to make it work).
>>>
>>> For production deployments obviously this one server stuff is nonsense
>>> .. so we need to have full decoupled distributed execution. For that we
>>> should ship puppet scripts to get them up and running plus maybe Boto
>>> scripts for someone to get it all up on EC2 with one command. Again its
>>> totally fine to use whatever broker here and whatever other pluggable
>>> components people want to use (and we need to make sure all the parts are
>>> pluggable: load balancers, message broker, the CEP engine, etc.)).
>>>
>>> Makes sense?
>>>
>>> Sanjiva.
>>>
>>>
>>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> Yes good point. Other day Azeez did the same suggestion.
>>>>
>>>> Thanks
>>>>
>>>> --Pradeep
>>>> sent from my phone
>>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>>
>>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>>> view on that :(
>>>>>
>>>>> One thing I'm wondering though is how much memory will be saved if we
>>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>>
>>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com> wrote:
>>>>> > btw,
>>>>> >
>>>>> > Now im working on MB and CEP bits.
>>>>> >
>>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>>> However,
>>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>>> > profile that has all) makes sense.
>>>>> >
>>>>> > WDYT?
>>>>> >
>>>>> > Are we all on same page..
>>>>> >
>>>>> > thanks
>>>>> >
>>>>> >
>>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>>> findings!
>>>>> >>
>>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>>>> pradeepfn@gmail.com>
>>>>> >> wrote:
>>>>> >> > Hi Guys,
>>>>> >> >
>>>>> >> > I started on the $subject. This thread is to track the progress..
>>>>> >> >
>>>>> >> > thanks,
>>>>> >> >
>>>>> >> >
>>>>> >> > --
>>>>> >> > Pradeep Fernando.
>>>>> >> > http://pradeepfernando.blogspot.com/
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>>> >> http://lnkd.in/cw5k69
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Pradeep Fernando.
>>>>> > http://pradeepfernando.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Check out my professional profile and connect with me on LinkedIn.
>>>>> http://lnkd.in/cw5k69
>>>>>
>>>>
>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> __________________________________________________________________
>> Damitha Kumarage
>> http://people.apache.org/
>> __________________________________________________________________
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
Re: Running stratos in one JVM
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Damitha,
Just noticed that there's a student interested in that project. Can you
please assign that 'writing agent in Python' to you and be the mentor of it
?
On Sun, Mar 16, 2014 at 10:24 AM, damitha kumarage <da...@gmail.com>wrote:
> Hi Sanjiva,
> Yes nicely formulated the requirement.
> It is nice if we can make the 4.1.0 or whatever next release with agent
> written in Python as well. Then the developer has the luxury of spinning up
> many low memory cartridge instances in his environment. Still no body has
> taken this as a GSoC project.
>
> Damitha
>
>
> On Sat, Mar 15, 2014 at 11:53 AM, Sanjiva Weerawarana <sa...@wso2.com>wrote:
>
>> I think right now we need to focus on getting a single trivial server
>> mechanism to be able to run Stratos without too much of stuff having to be
>> set up. I'd love to see two developer distros:
>>
>> - a VM image that has everything in it and runs in under 4GB with
>> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
>> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
>> stuff HAS to run in one server - else its a bug in those products .. so the
>> decision should not be based on ability to run in one JVM but rather just
>> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
>> we're nearly there for it.
>>
>> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin
>> to jClouds that spins up Docker images as processes and there's one JVM
>> that works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a
>> URL to a Docker image registry from which the images are booted up and run
>> (obviously a local registry will do better). We don't have this
>> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
>> hard to make it work).
>>
>> For production deployments obviously this one server stuff is nonsense ..
>> so we need to have full decoupled distributed execution. For that we should
>> ship puppet scripts to get them up and running plus maybe Boto scripts for
>> someone to get it all up on EC2 with one command. Again its totally fine to
>> use whatever broker here and whatever other pluggable components people
>> want to use (and we need to make sure all the parts are pluggable: load
>> balancers, message broker, the CEP engine, etc.)).
>>
>> Makes sense?
>>
>> Sanjiva.
>>
>>
>> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>>
>>> Hi Chris,
>>>
>>> Yes good point. Other day Azeez did the same suggestion.
>>>
>>> Thanks
>>>
>>> --Pradeep
>>> sent from my phone
>>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>>
>>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>>> view on that :(
>>>>
>>>> One thing I'm wondering though is how much memory will be saved if we
>>>> use RabbitMQ (or another MQ) instead of MB?
>>>>
>>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>>> wrote:
>>>> > btw,
>>>> >
>>>> > Now im working on MB and CEP bits.
>>>> >
>>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>>> However,
>>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>>> > profile that has all) makes sense.
>>>> >
>>>> > WDYT?
>>>> >
>>>> > Are we all on same page..
>>>> >
>>>> > thanks
>>>> >
>>>> >
>>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>>> findings!
>>>> >>
>>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>>> pradeepfn@gmail.com>
>>>> >> wrote:
>>>> >> > Hi Guys,
>>>> >> >
>>>> >> > I started on the $subject. This thread is to track the progress..
>>>> >> >
>>>> >> > thanks,
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Pradeep Fernando.
>>>> >> > http://pradeepfernando.blogspot.com/
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Check out my professional profile and connect with me on LinkedIn.
>>>> >> http://lnkd.in/cw5k69
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Pradeep Fernando.
>>>> > http://pradeepfernando.blogspot.com/
>>>>
>>>>
>>>>
>>>> --
>>>> Check out my professional profile and connect with me on LinkedIn.
>>>> http://lnkd.in/cw5k69
>>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> __________________________________________________________________
> Damitha Kumarage
> http://people.apache.org/
> __________________________________________________________________
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Running stratos in one JVM
Posted by damitha kumarage <da...@gmail.com>.
Hi Sanjiva,
Yes nicely formulated the requirement.
It is nice if we can make the 4.1.0 or whatever next release with agent
written in Python as well. Then the developer has the luxury of spinning up
many low memory cartridge instances in his environment. Still no body has
taken this as a GSoC project.
Damitha
On Sat, Mar 15, 2014 at 11:53 AM, Sanjiva Weerawarana <sa...@wso2.com>wrote:
> I think right now we need to focus on getting a single trivial server
> mechanism to be able to run Stratos without too much of stuff having to be
> set up. I'd love to see two developer distros:
>
> - a VM image that has everything in it and runs in under 4GB with
> OpenStack + Docker. It doesn't matter whether this uses one Carbon server
> to run it all or whether we use RabbitMQ or other AMQP broker. (Carbon
> stuff HAS to run in one server - else its a bug in those products .. so the
> decision should not be based on ability to run in one JVM but rather just
> making it dirt simple to use.) This distro needs to be in 4.0.0 - I think
> we're nearly there for it.
>
> - next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin to
> jClouds that spins up Docker images as processes and there's one JVM that
> works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
> to a Docker image registry from which the images are booted up and run
> (obviously a local registry will do better). We don't have this
> no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
> hard to make it work).
>
> For production deployments obviously this one server stuff is nonsense ..
> so we need to have full decoupled distributed execution. For that we should
> ship puppet scripts to get them up and running plus maybe Boto scripts for
> someone to get it all up on EC2 with one command. Again its totally fine to
> use whatever broker here and whatever other pluggable components people
> want to use (and we need to make sure all the parts are pluggable: load
> balancers, message broker, the CEP engine, etc.)).
>
> Makes sense?
>
> Sanjiva.
>
>
> On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
>
>> Hi Chris,
>>
>> Yes good point. Other day Azeez did the same suggestion.
>>
>> Thanks
>>
>> --Pradeep
>> sent from my phone
>> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>>
>>> Hi Pradeep - I don't know enough about how the profiles work to have a
>>> view on that :(
>>>
>>> One thing I'm wondering though is how much memory will be saved if we
>>> use RabbitMQ (or another MQ) instead of MB?
>>>
>>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>>> wrote:
>>> > btw,
>>> >
>>> > Now im working on MB and CEP bits.
>>> >
>>> > IMHO, we should not create MB and CEP only profiles in stratos.
>>> However,
>>> > adding MB/CEP features (the ones that we use) to default profile (the
>>> > profile that has all) makes sense.
>>> >
>>> > WDYT?
>>> >
>>> > Are we all on same page..
>>> >
>>> > thanks
>>> >
>>> >
>>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>>> wrote:
>>> >>
>>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>>> findings!
>>> >>
>>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <
>>> pradeepfn@gmail.com>
>>> >> wrote:
>>> >> > Hi Guys,
>>> >> >
>>> >> > I started on the $subject. This thread is to track the progress..
>>> >> >
>>> >> > thanks,
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Pradeep Fernando.
>>> >> > http://pradeepfernando.blogspot.com/
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Check out my professional profile and connect with me on LinkedIn.
>>> >> http://lnkd.in/cw5k69
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Pradeep Fernando.
>>> > http://pradeepfernando.blogspot.com/
>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
Re: Running stratos in one JVM
Posted by Sanjiva Weerawarana <sa...@wso2.com>.
I think right now we need to focus on getting a single trivial server
mechanism to be able to run Stratos without too much of stuff having to be
set up. I'd love to see two developer distros:
- a VM image that has everything in it and runs in under 4GB with OpenStack
+ Docker. It doesn't matter whether this uses one Carbon server to run it
all or whether we use RabbitMQ or other AMQP broker. (Carbon stuff HAS to
run in one server - else its a bug in those products .. so the decision
should not be based on ability to run in one JVM but rather just making it
dirt simple to use.) This distro needs to be in 4.0.0 - I think we're
nearly there for it.
- next is a "no-IaaS-IaaS" based distro. That, we write a direct plugin to
jClouds that spins up Docker images as processes and there's one JVM that
works as the SM+CC+LB+AS+all. Thus the download becomes one JVM plus a URL
to a Docker image registry from which the images are booted up and run
(obviously a local registry will do better). We don't have this
no-IaaS-IaaS yet so this can come maybe as 4.1.0 or whatever (its not that
hard to make it work).
For production deployments obviously this one server stuff is nonsense ..
so we need to have full decoupled distributed execution. For that we should
ship puppet scripts to get them up and running plus maybe Boto scripts for
someone to get it all up on EC2 with one command. Again its totally fine to
use whatever broker here and whatever other pluggable components people
want to use (and we need to make sure all the parts are pluggable: load
balancers, message broker, the CEP engine, etc.)).
Makes sense?
Sanjiva.
On Fri, Mar 14, 2014 at 7:59 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> Hi Chris,
>
> Yes good point. Other day Azeez did the same suggestion.
>
> Thanks
>
> --Pradeep
> sent from my phone
> On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
>
>> Hi Pradeep - I don't know enough about how the profiles work to have a
>> view on that :(
>>
>> One thing I'm wondering though is how much memory will be saved if we
>> use RabbitMQ (or another MQ) instead of MB?
>>
>> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > btw,
>> >
>> > Now im working on MB and CEP bits.
>> >
>> > IMHO, we should not create MB and CEP only profiles in stratos. However,
>> > adding MB/CEP features (the ones that we use) to default profile (the
>> > profile that has all) makes sense.
>> >
>> > WDYT?
>> >
>> > Are we all on same page..
>> >
>> > thanks
>> >
>> >
>> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com>
>> wrote:
>> >>
>> >> Hey Pradeep - this is exciting stuff! Looking forward to your
>> findings!
>> >>
>> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pradeepfn@gmail.com
>> >
>> >> wrote:
>> >> > Hi Guys,
>> >> >
>> >> > I started on the $subject. This thread is to track the progress..
>> >> >
>> >> > thanks,
>> >> >
>> >> >
>> >> > --
>> >> > Pradeep Fernando.
>> >> > http://pradeepfernando.blogspot.com/
>> >>
>> >>
>> >>
>> >> --
>> >> Check out my professional profile and connect with me on LinkedIn.
>> >> http://lnkd.in/cw5k69
>> >
>> >
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
Hi Chris,
Yes good point. Other day Azeez did the same suggestion.
Thanks
--Pradeep
sent from my phone
On Mar 14, 2014 3:47 PM, "chris snow" <ch...@gmail.com> wrote:
> Hi Pradeep - I don't know enough about how the profiles work to have a
> view on that :(
>
> One thing I'm wondering though is how much memory will be saved if we
> use RabbitMQ (or another MQ) instead of MB?
>
> On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com>
> wrote:
> > btw,
> >
> > Now im working on MB and CEP bits.
> >
> > IMHO, we should not create MB and CEP only profiles in stratos. However,
> > adding MB/CEP features (the ones that we use) to default profile (the
> > profile that has all) makes sense.
> >
> > WDYT?
> >
> > Are we all on same page..
> >
> > thanks
> >
> >
> > On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com> wrote:
> >>
> >> Hey Pradeep - this is exciting stuff! Looking forward to your findings!
> >>
> >> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com>
> >> wrote:
> >> > Hi Guys,
> >> >
> >> > I started on the $subject. This thread is to track the progress..
> >> >
> >> > thanks,
> >> >
> >> >
> >> > --
> >> > Pradeep Fernando.
> >> > http://pradeepfernando.blogspot.com/
> >>
> >>
> >>
> >> --
> >> Check out my professional profile and connect with me on LinkedIn.
> >> http://lnkd.in/cw5k69
> >
> >
> >
> >
> > --
> > Pradeep Fernando.
> > http://pradeepfernando.blogspot.com/
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Hi Pradeep - I don't know enough about how the profiles work to have a
view on that :(
One thing I'm wondering though is how much memory will be saved if we
use RabbitMQ (or another MQ) instead of MB?
On Fri, Mar 14, 2014 at 10:10 AM, Pradeep Fernando <pr...@gmail.com> wrote:
> btw,
>
> Now im working on MB and CEP bits.
>
> IMHO, we should not create MB and CEP only profiles in stratos. However,
> adding MB/CEP features (the ones that we use) to default profile (the
> profile that has all) makes sense.
>
> WDYT?
>
> Are we all on same page..
>
> thanks
>
>
> On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hey Pradeep - this is exciting stuff! Looking forward to your findings!
>>
>> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > Hi Guys,
>> >
>> > I started on the $subject. This thread is to track the progress..
>> >
>> > thanks,
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: Running stratos in one JVM
Posted by Sanjiva Weerawarana <sa...@wso2.com>.
+1 .. that's right IMO because CEP and MB are external dependencies .. so
its fine to have it so the features run in the default profile but if you
want the full thing you just download the product.
Sanjiva.
On Fri, Mar 14, 2014 at 3:40 PM, Pradeep Fernando <pr...@gmail.com>wrote:
> btw,
>
> Now im working on MB and CEP bits.
>
> IMHO, we should not create MB and CEP only profiles in stratos. However,
> adding MB/CEP features (the ones that we use) to default profile (the
> profile that has all) makes sense.
>
> WDYT?
>
> Are we all on same page..
>
> thanks
>
>
> On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com> wrote:
>
>> Hey Pradeep - this is exciting stuff! Looking forward to your findings!
>>
>> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com>
>> wrote:
>> > Hi Guys,
>> >
>> > I started on the $subject. This thread is to track the progress..
>> >
>> > thanks,
>> >
>> >
>> > --
>> > Pradeep Fernando.
>> > http://pradeepfernando.blogspot.com/
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
Re: Running stratos in one JVM
Posted by Pradeep Fernando <pr...@gmail.com>.
btw,
Now im working on MB and CEP bits.
IMHO, we should not create MB and CEP only profiles in stratos. However,
adding MB/CEP features (the ones that we use) to default profile (the
profile that has all) makes sense.
WDYT?
Are we all on same page..
thanks
On Fri, Mar 14, 2014 at 3:32 PM, chris snow <ch...@gmail.com> wrote:
> Hey Pradeep - this is exciting stuff! Looking forward to your findings!
>
> On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com>
> wrote:
> > Hi Guys,
> >
> > I started on the $subject. This thread is to track the progress..
> >
> > thanks,
> >
> >
> > --
> > Pradeep Fernando.
> > http://pradeepfernando.blogspot.com/
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Running stratos in one JVM
Posted by chris snow <ch...@gmail.com>.
Hey Pradeep - this is exciting stuff! Looking forward to your findings!
On Wed, Mar 12, 2014 at 5:31 PM, Pradeep Fernando <pr...@gmail.com> wrote:
> Hi Guys,
>
> I started on the $subject. This thread is to track the progress..
>
> thanks,
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69