Okay. Thanks Isuru.
On Mon, Nov 10, 2014 at 2:34 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> There is an issue with undeployment where the clusters do not get properly
> removed from Topology. I'm working on a fix now.
>
> On Mon, Nov 10, 2014 at 2:31 PM, Rajkumar Rajaratnam
> wrote:
>
>> Hi Isuru,
Hi,
There is an issue with undeployment where the clusters do not get properly
removed from Topology. I'm working on a fix now.
On Mon, Nov 10, 2014 at 2:31 PM, Rajkumar Rajaratnam
wrote:
> Hi Isuru,
>
> When I undeploy application for docker scenario, this is what I am getting
> in the logs. A
Hi Isuru,
When I undeploy application for docker scenario, this is what I am getting
in the logs. Any idea why I am getting cluster terminating and terminated
events?
TID: [0] [STRATOS] [2014-11-10 14:25:37,319] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
Handlin
Hi all,
Please note that Nirmal has updated kubernetes binaries to latest version
in master branch.
Please use vagrant scripts at [1] if you are going to test kubernetes
scenario on master branch. Earlier one might not work.
1. https://github.com/nirmal070125/vagrant-kubernetes-setup/archive/v2.
Tested undeployment and worked for simple and complex apps. There is an
issue in re-deploying the same app, where it did not get re-activated. Will
look in to this.
On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis wrote:
> Hi,
>
> Lasindu and I are still trying to get the Python CA working. The
We have now merged all changes from the docker-grouping-merge branch to the
master branch. Could not rebase due to the number of conflicts occurred,
therefore a merge was done.
Master branch now can be used for development. Please do a complete build
and run the tests.
Thanks
On Sun, Nov 9, 2014
It seems nearly impossible to rebase changes from docker-grouping-merge
branch to the master.
The docker-grouping-merge branch is nearly 650 commits ahead of the master
and the rebase conflicts almost at each commit. We might need to go ahead
with a merge.
On Sun, Nov 9, 2014 at 10:38 PM, Chamila
It turned out it was an accessibility error. The events are now being
received by the agent and health stats are published to CEP. The app path
for PHP is not being properly set right now, so I'm looking into it now.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.cha
On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan wrote:
> So this could be the Mqtt issue we saw earlier as well?
I'm not sure. It might have been an accessibility issue. I'm in the process
of verifying this now.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.ch
Please try to hold your commits to both docker-grouping-merge and master
branches now.
I'm now merging changes from docker-grouping-merge branch to master.
I did a quick test with rebase and merge, merge worked without a problem
but the rebase failed with conflicts. Will try to resolve conflicts i
Will try to do a rebase Nirmal. Lahiru: Yes this could be. Shall we try to
login to ActiveMQ dashboard and see whether message broker is receiving
those events?
Thanks
On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan wrote:
>
>
> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis
> wrote:
>
>>
On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis wrote:
> Hi,
>
> Lasindu and I are still trying to get the Python CA working. The puppet
> module is operational. But at the moment the CA is not getting the events
> published to the MB.
>
So this could be the Mqtt issue we saw earlier as well?
Please do a rebase instead of merge.
On Sun, Nov 9, 2014 at 12:05 PM, Rajaratnam Rajkumar
wrote:
> Yes Lahiru, merge now :)
>
> On Sunday, November 9, 2014, Chamila De Alwis wrote:
>
>> Hi,
>>
>> Lasindu and I are still trying to get the Python CA working. The puppet
>> module is operational. B
Yes Lahiru, merge now :)
On Sunday, November 9, 2014, Chamila De Alwis wrote:
> Hi,
>
> Lasindu and I are still trying to get the Python CA working. The puppet
> module is operational. But at the moment the CA is not getting the events
> published to the MB.
>
>
> Regards,
> Chamila de Alwis
> S
Hi,
Lasindu and I are still trying to get the Python CA working. The puppet
module is operational. But at the moment the CA is not getting the events
published to the MB.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sun, Nov 9, 2014 at 3:3
Shall we merge to the master now?
On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan wrote:
>
>
> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu
> wrote:
>
>> Fixed the serviceId getting NULL by setting it to the ClusterContext and
>> committed it..
>>
>
> Fine then :)
>
>>
>> On Sun, Nov
On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu wrote:
> Fixed the serviceId getting NULL by setting it to the ClusterContext and
> committed it..
>
Fine then :)
>
> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu
> wrote:
>
>> Hi Lahiru,
>>
>> As you have introduced ClusteContext
On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu wrote:
> Hi Lahiru,
>
> As you have introduced ClusteContext in ClusterMonitor, the serviceId got
> to removed. Is this done purposely? If so, can we update the getServiceId()
> (which referred by several other places) in monitors to return t
Fixed the serviceId getting NULL by setting it to the ClusterContext and
committed it..
On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu wrote:
> Hi Lahiru,
>
> As you have introduced ClusteContext in ClusterMonitor, the serviceId got
> to removed. Is this done purposely? If so, can we upda
Hi Lahiru,
As you have introduced ClusteContext in ClusterMonitor, the serviceId got
to removed. Is this done purposely? If so, can we update the getServiceId()
(which referred by several other places) in monitors to return the correct
serviceId by reading ClusterContext?
Due to this, ClusterMon
Hi
On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa wrote:
>
>
> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa
> wrote:
>
>>
>>
>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu
>> wrote:
>>
>>> Hi all,
>>>
>>> After fixing few issues, i could get the application undeployment
>>> w
On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa wrote:
>
>
> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu
> wrote:
>
>> Hi all,
>>
>> After fixing few issues, i could get the application undeployment working
>> with one cluster now. So the basic undeployment is working fine...Will
>>
Hi Imesh,
Sorry for the late response.
On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne wrote:
> Hi Isuru,
>
> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa
> wrote:
>
>>
>> IMHO we should have the context name 'stratos' in the url. Then it is
>> more intuitive. having just /api doesn't
Hi all,
After fixing few issues, i could get the application undeployment working
with one cluster now. So the basic undeployment is working fine...Will
continue testing with a complex application...
Thanks,
Reka
On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa wrote:
>
>
> On Sun, Nov 9, 201
On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu wrote:
> Hi all,
>
> After fixing few issues, i could get the application undeployment working
> with one cluster now. So the basic undeployment is working fine...Will
> continue testing with a complex application...
>
Great! I will test the s
On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne wrote:
> No, there seems to be a problem with application un-deploy function. For
> me the un-deploy call hangs in the autoscaler. This is currerntly under
> investigation.
>
Got the same issue, will check in this.
>
> Since the basic workflow of s
On Sat, Nov 8, 2014 at 12:15 PM, Rajkumar Rajaratnam
wrote:
> Does anyone know why cluster status filed is commented out on
> Cluster.java?
>
> //private ClusterStatus status;
>
Sorry for the late response, there is a LifeCycleStateManager which was
added recently, and currently status is mainta
I too fixed few application undeployment issues..Will hold the commit now
onwards..
On Sun, Nov 9, 2014 at 12:46 PM, Lahiru Sandaruwan wrote:
>
>
> On Sun, Nov 9, 2014 at 12:38 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Hi Lahiru,
>>
>> Sure, please let us know when you
On Sun, Nov 9, 2014 at 12:38 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi Lahiru,
>
> Sure, please let us know when you finish it.
>
Done just now.
>
>
>
> On Sun, Nov 9, 2014 at 12:17 PM, Lahiru Sandaruwan
> wrote:
>
>> Can you guys hold until i push cluster context change
Hi Lahiru,
Sure, please let us know when you finish it.
On Sun, Nov 9, 2014 at 12:17 PM, Lahiru Sandaruwan wrote:
> Can you guys hold until i push cluster context change. Will do it asap.
>
> On Sun, Nov 9, 2014 at 12:13 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Hi,
Can you guys hold until i push cluster context change. Will do it asap.
On Sun, Nov 9, 2014 at 12:13 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi,
>
> +1, then shall we merge docker-grouping-merge branch to master branch and
> continue testing on it.
>
> Thanks !
>
> On Sun,
Hi,
+1, then shall we merge docker-grouping-merge branch to master branch and
continue testing on it.
Thanks !
On Sun, Nov 9, 2014 at 12:05 PM, Reka Thirunavukkarasu
wrote:
> Hi Imesh,
>
> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne wrote:
>
>> No, there seems to be a problem with applica
Hi Imesh,
On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne wrote:
> No, there seems to be a problem with application un-deploy function. For
> me the un-deploy call hangs in the autoscaler. This is currerntly under
> investigation.
>
> Since the basic workflow of service grouping and docker are w
Hi Imesh,
- Couldn't access the service via LB. LB routes requests to port 80
instead of service proxy port. Looking into it currently.
- Manual scaling is not working
But I guess we can merge to master and fix these there. These are minor
issues.
Thanks.
On Sun, Nov 9, 2014 at 8:38 AM
No, there seems to be a problem with application un-deploy function. For me
the un-deploy call hangs in the autoscaler. This is currerntly under
investigation.
Since the basic workflow of service grouping and docker are working now
shall we merge docker-grouping-merge branch to master branch now?
Hi all,
Did anyone undeploy the application successfully? Were all clusters wiped
out?
Thanks
On Saturday, November 8, 2014, Imesh Gunaratne wrote:
> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis > wrote:
>
>>
>> Don't we also need the event processing chain since it constructs the
>> even
On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis wrote:
>
> Don't we also need the event processing chain since it constructs the
> event objects from the Jsons? Additionally this is done through the Gson
> library, so we would have some difficulty in getting that functionality in
> to python as
Hi Imesh,
On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne wrote:
> My understanding is that we only need the domain classes converted to
> python. They may only contain list of properties. Therefore the generated
> code should be simple enough to validate.
Don't we also need the event processi
I'm on scaling based on dependency ratio. We need a place to keep runtime
information of cluster, which should be also persisted. So it should be the
same place where we keep updated autoscale/deployment policies at
runtime. (manual
scaling)
I'll send mails and get the community idea as well. Im f
Hi
I could bring an application with more than one cluster as Active.
Currently testing the faulty member scenario for VM with the Composite
application and fixing issues. Will update on that..
Thanks,
Reka
On Sat, Nov 8, 2014 at 10:39 PM, Imesh Gunaratne wrote:
> I have now done the followin
I have now done the following changes:
- Added get applications resource to REST API
- Added list-applications command to CLI
- Removed CLI commands subscribe-cartridge, list-cartridge-subscriptions,
unsubscribe-cartridge and deprecated command classes
- Fixed coding convention issues in the CLI
-
My understanding is that we only need the domain classes converted to
python. They may only contain list of properties. Therefore the generated
code should be simple enough to validate.
On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis wrote:
> Hi Imesh,
>
> Is it reliable to follow a code conve
Update:
- Auto-scaling works fine for container scenario
- Faulty members are successfully terminated and new containers are
created successfully
Thanks.
On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne wrote:
> My understanding is that we only need the domain classes converted to
> py
On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis wrote:
> Hi Imesh,
>
> Is it reliable to follow a code conversion tool? Given that this tool
> doesn't guarantee working code, I'm not sure this would be a better option.
>
> *"The generated Python code is not guaranteed to run,"*
>
If it is not g
Hi Imesh,
Is it reliable to follow a code conversion tool? Given that this tool
doesn't guarantee working code, I'm not sure this would be a better option.
*"The generated Python code is not guaranteed to run,"*
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamil
Yes Java agent.
Thanks.
On Sat, Nov 8, 2014 at 6:32 PM, Imesh Gunaratne wrote:
> Thanks for the update Raj, were you using Java cartridge agent?
>
> On Sat, Nov 8, 2014 at 6:21 PM, Rajkumar Rajaratnam
> wrote:
>
>> Hi all,
>>
>> Just to give an update;
>>
>> Simple container scenario is workin
Thanks for the update Raj, were you using Java cartridge agent?
On Sat, Nov 8, 2014 at 6:21 PM, Rajkumar Rajaratnam
wrote:
> Hi all,
>
> Just to give an update;
>
> Simple container scenario is working now with m2 image. Members are
> activated and publishing health stats to CEP. Seems undeployi
Hi all,
Just to give an update;
Simple container scenario is working now with m2 image. Members are
activated and publishing health stats to CEP. Seems undeploying application
is not working. Looking into it currently.
Thanks.
On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne wrote:
> I think w
I think we can use [1] to convert messaging component data model to python
at the build time and the agent can refer that directly. WDYT?
[1] https://github.com/natural/java2python
On Nov 8, 2014 1:28 PM, "Chamila De Alwis" wrote:
> Hi Raj,
>
> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam
Hi Raj,
On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam
wrote:
> Please double check the java agent code too. It works somehow. Don't know
> the reason :)
The Java agent makes use of the org.apache.stratos.messaging component, so
any changes done from a publisher's point of view is reflect
Fixed and pushed to fork. This commit is listed in the already existing PR.
https://github.com/apache/stratos/pull/106
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sat, Nov 8, 2014 at 1:12 PM, Chamila De Alwis wrote:
>
> On Sat, Nov 8, 2
On Sat, Nov 8, 2014 at 1:12 PM, Chamila De Alwis wrote:
>
> On Sat, Nov 8, 2014 at 12:55 PM, Rajkumar Rajaratnam
> wrote:
>
>> When I use m2 java agent docker image, I am getting member activated
>> events. So status is not a compulsory field chamila.
>
>
> I will fix this then. From the existin
On Sat, Nov 8, 2014 at 12:55 PM, Rajkumar Rajaratnam
wrote:
> When I use m2 java agent docker image, I am getting member activated
> events. So status is not a compulsory field chamila.
I will fix this then. From the existing code at the time of writing the
Python agent, I assumed it was mandat
When I use m2 java agent docker image, I am getting member activated
events. So status is not a compulsory field chamila.
I am going to continue with m2 image for now.
Thanks.
On Sat, Nov 8, 2014 at 12:17 PM, Rajkumar Rajaratnam
wrote:
>
>
> On Sat, Nov 8, 2014 at 12:15 PM, Rajkumar Rajaratnam
On Sat, Nov 8, 2014 at 12:15 PM, Rajkumar Rajaratnam
wrote:
> Does anyone know why cluster status filed is commented out on
> Cluster.java?
>
> //private ClusterStatus status;
>
> Thanks.
>
> On Sat, Nov 8, 2014 at 11:41 AM, Chamila De Alwis
> wrote:
>
>>
>> Hi Raj,
>>
>> On Sat, Nov 8, 2014 at
Does anyone know why cluster status filed is commented out on Cluster.java?
//private ClusterStatus status;
Thanks.
On Sat, Nov 8, 2014 at 11:41 AM, Chamila De Alwis wrote:
>
> Hi Raj,
>
> On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam
> wrote:
>
>> File "/mnt/cartridgeagent/modules/eve
Hi Raj,
On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam
wrote:
> File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173, in
> create_from_json
> cluster_obj.status = cluster_str["status"]
> KeyError: 'status'
>
The "status" field is missing from the cluster object. From w
Chamila,
Here is a container agent log. Any idea what event processing fails?
[2014-11-08 04:20:46,152] DEBUG {eventsubscriber.py:on_message} - Message
received: 'topology/CompleteTopologyEvent':
'{"topology":{"serviceMap":{"php":{"serviceName":"php","serviceType":"SingleTenant","clusterIdCluster
As I found this problem this has been caused by the duplicated client id
values which we have set before. Now I have done a fix to set unique client
id values for each topic subscriber and publisher.
I did several verification tests on this fix using a sample event publisher
(sending 1000 events c
Hi Isuru,
On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa
wrote:
>
> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam
> wrote:
>
>> I got containers to be created.
>> But didn't get the member started event. Either agent is not sending or
>> CC is not receiving. Looking into it currently
I guess we need to set clean session to false and use reliable delivery.
WDYT?
MqttConnectOptions connOpts = new MqttConnectOptions();
connOpts.setCleanSession(false);
*
* If set to false both the client and server will maintain state across
* restarts of the client, the server and the connectio
Gayan: I see another issue here:
We have set QOS to 2 in publisher:
MqttMessage mqttMSG = new MqttMessage(message.getBytes());
mqttMSG.setQos(QOS); // QOS => 2
** Quality of Service 2 - indicates that a message should*
** be delivered once. The message will be persisted to disk, and will*
** be
At a particular time we do have multiple listeners and only one topic
publisher for a component. Because of that generating a client id for
subscribers.
+1 for have client id unique according to this
[1].
http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#Mqt
I'll do a quick fix to make the client id unique and run a test.
On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne wrote:
> Gayan: Was there any reason for generating a client id for subscribers and
> setting a fixed value for publishers?
>
> TopicSubscriber.doSubscribe():
> MqttClient mqttClient
AFAIU the client id is used by the message broker for maintaining the
sessions among connection drops and restarts (for reliable message
delivery). Therefore each subscriber and publisher might need to have its
own client with a uniqe identifier.
I will fix this in messaging component.
On Fri, No
Gayan: Was there any reason for generating a client id for subscribers and
setting a fixed value for publishers?
TopicSubscriber.doSubscribe():
MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.getRandomString(
5));
On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa wrote:
>
>
> On
On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa
wrote:
>
> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam
> wrote:
>
>> I got containers to be created.
>> But didn't get the member started event. Either agent is not sending or
>> CC is not receiving. Looking into it currently.
>>
> I'm
On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam
wrote:
> I got containers to be created.
> But didn't get the member started event. Either agent is not sending or CC
> is not receiving. Looking into it currently.
>
I'm seeing this issue as well. The agent is sending the events, but Stratos
i
I got containers to be created.
But didn't get the member started event. Either agent is not sending or CC
is not receiving. Looking into it currently.
On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne wrote:
> Hi Isuru,
>
> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa
> wrote:
>
>>
>> IM
Hi Isuru,
On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa
wrote:
>
> IMHO we should have the context name 'stratos' in the url. Then it is more
> intuitive. having just /api doesn't say that this API belongs to Stratos.
> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>
Hi Imesh,
On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne wrote:
> Please note that we have now introduced API versioning in
> docker-grouping-merge branch. Now the REST API context has been changed as
> follows, no changes were done to existing resource paths:
>
> Previous API URL:
> https://{h
Hi Imesh,
I'll update the CLI with the new API versioning.
Thanks !
On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne wrote:
> Please note that we have now introduced API versioning in
> docker-grouping-merge branch. Now the REST API context has been changed as
> follows, no changes were done to
Please note that we have now introduced API versioning in
docker-grouping-merge branch. Now the REST API context has been changed as
follows, no changes were done to existing resource paths:
Previous API URL:
https://{hostname}:{port}/stratos/admin/{resource-path}
New API URL:
https://{hostname}:
We now have the docker-grouping-branch in a compilable state with latests
modifications. Please test all workflows related to service grouping and
docker, once things are stable will merge this branch to master.
Thanks
On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
manu...@wso2.
Hi,
I have completed deploy-application, undeploy-application,
deploy-service-group and undeploy-service-group commands in CLI and pushed
the changes to docker-grouping-merge branch. I'll compete the other
commands as soon as possible and looks for the UI as well.
Thanks !
On Mon, Nov 3, 2014 at
I have now fixed autoscaler service stub bundle exports and stratos manager
import statements. Currently working on Stratos Manager, seems like there
are duplicated domain classes:
org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
org.apache.stratos.messaging/src/ma
Fixed AS issues
On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith wrote:
> I have fixed some compilation errors in Cloud Controller.
>
> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Hi,
>>
>> I have started on grouping CLI commands.
>>
>> Thanks
I have fixed some compilation errors in Cloud Controller.
On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi,
>
> I have started on grouping CLI commands.
>
> Thanks !
>
> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam
> wrote:
>
>> Fixed messagin
Hi,
I have started on grouping CLI commands.
Thanks !
On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam
wrote:
> Fixed messaging component issues.
>
> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne wrote:
>
>> I have now merged latest changes from 4.0.0-grouping branch to
>> docker-groupin
Fixed messaging component issues.
On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne wrote:
> I have now merged latest changes from 4.0.0-grouping branch to
> docker-grouping-merge branch. We can now fix merge issues in
> docker-grouping-merge branch.
>
> Once features are stable will move changes
I have now merged latest changes from 4.0.0-grouping branch to
docker-grouping-merge branch. We can now fix merge issues in
docker-grouping-merge branch.
Once features are stable will move changes to master branch.
Thanks
On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne wrote:
> Isuru is workin
Isuru is working on a major refactoring task ("[Grouping] Branch may be
Unstable ATM"). Will hold this effort until that is completed.
On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan wrote:
> I have tested grouping feature in EC2 up to instance are spawning. Will be
> testing further.
>
> Tha
I have tested grouping feature in EC2 up to instance are spawning. Will be
testing further.
Thanks.
On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> When and where are we creating and adding cluster monitors (not app
> monitors) to the AutoscalerContext?
> I couldn't find an
Hi,
When and where are we creating and adding cluster monitors (not app
monitors) to the AutoscalerContext?
I couldn't find any places.
Thanks.
On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan wrote:
>
>
> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan
> wrote:
>
>> I get a NPE while tryi
On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan wrote:
> I get a NPE while trying to deploy the app definition without properties,
> looking into it.
>
>
I have added a null check. Will commit the fix.
> [2014-11-01 20:17:18,922] ERROR
> {org.apache.stratos.rest.endpoint.handlers.CustomThrowab
Hi all,
Found that we were using old code in AutoscalerTopologyEventReceiver.
We introduced a monitor hierarchy, and we are letting cluster monitors to
decide and act upon receiving events. That's why we introduced
handle*Event(Event) methods in AbstractClusterMonitor.
When receiving events, we
I get a NPE while trying to deploy the app definition without properties,
looking into it.
[2014-11-01 20:17:18,922] ERROR
{org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
- Internal server error
java.lang.NullPointerException
at
org.apache.stratos.rest.endpoint.servic
Can a service cluster(say php cluster) span across two partitions(in other
words two kub cluster)? I guess kubernetes can manage their containers
within a kub cluster, not between kub clusters? For example, if we say we
need 3 replicas, it can ensure there are 3 replicas in one kub cluster. It
can'
I have now fixed few more issues:
- Removing subscription resource from REST API and CLI.
- Adding isKubernetesCluster property to ApplicationClusterContext.
- Passing properties from Application definition to the cluster objects.
This is needed for Kubernetes.
- Packaging drools files in stratos d
gt;>>>>>>>>>> following components:
>>>>>>>>>>>> - Autoscaler
>>>>>>>>>>>> - Cloud Controller
>>>>>>>>>>>> - CLI
>>>>>>>>>>>>
>>>>>&g
t;>>>>>>>
>>>>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>
A great thought Lakmal! Yes definitely! I was also thinking enabling the
ability to autoscale Kubernetes clusters. We can take this as the first
step towards that.
First we can introduce this feature to define deployment policies for
Kubernetes and then at a later stage we can add the ability to a
gt;>>>>>>>>> the functional issues.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 30, 2014 at 2:
t;>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>> lak...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Great work Imesh! Please keep update the status.
>
gt;>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>> lak...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Great work Imesh! Please keep upda
t 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>> mep...@cisco.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> So target date of GA would be and of November (as was planned
>>>>>>>>>>>> for
t;>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>> branch using git merge tool and found around 50 conflicting
uping branch to docker-grouping-merge
>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>
>>>>>>>> Now w
t;>> - Found issues in messaging component and resolved
>>>>>>> - Currently working on Autoscaler where there are changes in monitor
>>>>>>> classes which have been changed in both branches.
>>>>>>>
>>>>>>> Th
GA end of nov.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>> mep...@cisco.com> wrote:
>>>>>>>
>>>>>>>> So ta
1 - 100 of 113 matches
Mail list logo
