Hi Reka,
I am not sure about all the use cases but I followed up with our team regarding
the termination order when we discussed it in a previous email thread (see
attached response) and it seems necessary to consider the startup order in the
termination. I’ll copy him on the email for some hel
Hi Guys,
I am going to migrate our setup to Kubernetes 0.4.1 and also the API
client, if there's any changes needed.
After Kubernetes 0.4.1, K8s team is doing a drastic change by introducing
an IP for a service proxy. With this we might have to do some changes to
the way we access service proxies
Hi Isuru,
On Tue, Oct 28, 2014 at 3:46 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> On Tue, Oct 28, 2014 at 2:43 PM, Reka Thirunavukkarasu
> wrote:
>
>> Hi
>>
>> On Tue, Oct 28, 2014 at 2:22 PM, Isuru Haththotuwa
>> wrote:
>>
>>>
>>>
>>> On Tue, Oct 28, 2014 at 1:48 PM, Reka Thirunavukkarasu
>>> wr
Hi All,
We have now completed 4.1.0-M3 milestone and the master branch is now open
for commits.
Thanks
On Tue, Oct 28, 2014 at 1:13 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> We are now in the process of finalizing 4.1.0 M3 milstone. Shall we please
> hold our commits for master branch until we
Hi Devs,
Apache Stratos 4.1.0-M3 Developer Preview is now ready. This is a developer
preview/snapshot of the current development track and it could be used as a
baseline for contributing to the product stack.
*Main Features*
- Python Cartridge Agent
- Ability to update Autoscaling & Deployment Po
Hi Martin,
Thanks for bringing this up.
On Wed, Oct 29, 2014 at 2:13 AM, Martin Eppel (meppel)
wrote:
> Hi Reka,
>
>
>
> Eventually termination has to follow (in reverse order) the startup
> sequence:
>
>
>
> If A depends on B, B on C (startup sequence first C, second B, third A)
>
>
>
> And
Hi,
I remember a similar discussion in another thread. In a single tenanted
cartridge also you can have a similar extension in cartridge agent.
Touched, not typed. Erroneous words are a feature, not a typo.
[
https://issues.apache.org/jira/browse/STRATOS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187177#comment-14187177
]
Udara Liyanage commented on STRATOS-922:
[2014-10-28 23:20:36,389] INFO
{org.ap
Raghavendra Rangrej created STRATOS-923:
---
Summary: vcloud: Status not updated to Inactive for faulty
cartridge
Key: STRATOS-923
URL: https://issues.apache.org/jira/browse/STRATOS-923
Project: St
Udara Liyanage created STRATOS-922:
--
Summary: member become obsolete even application became active
Key: STRATOS-922
URL: https://issues.apache.org/jira/browse/STRATOS-922
Project: Stratos
I
[
https://issues.apache.org/jira/browse/STRATOS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186995#comment-14186995
]
Isuru Haththotuwa commented on STRATOS-921:
---
Fixed in commits 636d9bb0e85a6e91d
[
https://issues.apache.org/jira/browse/STRATOS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa resolved STRATOS-921.
---
Resolution: Fixed
> Can't Undeploy the Application till the Members become Active
> -
Isuru Haththotuwa created STRATOS-921:
-
Summary: Can't Undeploy the Application till the Members become
Active
Key: STRATOS-921
URL: https://issues.apache.org/jira/browse/STRATOS-921
Project: Stra
[
https://issues.apache.org/jira/browse/STRATOS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186801#comment-14186801
]
Imesh Gunaratne commented on STRATOS-896:
-
This feature is now implemented to all
[
https://issues.apache.org/jira/browse/STRATOS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-896.
-
Resolution: Fixed
This functionality was introduced in 4.1.0-M3.
> A New Feature to Upda
[
https://issues.apache.org/jira/browse/STRATOS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-896:
Comment: was deleted
(was: This functionality was introduced in 4.1.0-M3.)
> A New Feature
[
https://issues.apache.org/jira/browse/STRATOS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-896:
Fix Version/s: 4.1.0 M3
> A New Feature to Update Autoscaling & Deployment Policies in Runt
[
https://issues.apache.org/jira/browse/STRATOS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills closed STRATOS-920.
> Wiki - Stratos 4.1.0 - M3 - Developer Preview - Getting Started Guide
> -
[
https://issues.apache.org/jira/browse/STRATOS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-920.
--
Resolution: Fixed
Fix Version/s: 4.1.0 M3
Added content in [1].
[1]
https://cw
Mariangela Hills created STRATOS-920:
Summary: Wiki - Stratos 4.1.0 - M3 - Developer Preview - Getting
Started Guide
Key: STRATOS-920
URL: https://issues.apache.org/jira/browse/STRATOS-920
Project
Rajkumar Rajaratnam created STRATOS-919:
---
Summary: Error while AS asks CC to terminate an instance that are
not in the topology
Key: STRATOS-919
URL: https://issues.apache.org/jira/browse/STRATOS-919
Hi Jerad,
Docker integration branch deprecated now. Please use master branch.
Thanks.
On Tue, Oct 28, 2014 at 4:34 PM, Jerad Rutnam wrote:
> Hi Sajith,
>
> Thanks for the reply. Sorry, didn't notice the "NoClassDefFoundError".
> And I'm using "docker-integration" branch.
> I'll check with Udar
Hi Sajith,
Thanks for the reply. Sorry, didn't notice the "NoClassDefFoundError". And
I'm using "docker-integration" branch.
I'll check with Udara an find that thread. Do I need to change the branch
to "master" and do a build? Or ill just check the thread first.
Thanks,
On Tue, Oct 28, 2014 at 4
Its a class not found exception
java.lang.NoClassDefFoundError:
com/jcraft/jsch/agentproxy/usocket/NCUSocketFactory, which is the same
issue Udara has mentioned, please refer that thread.
Are you working on the master branch?
On Tue, Oct 28, 2014 at 3:55 PM, Jerad Rutnam wrote:
> Hi,
>
>
Hi,
On Tue, Oct 28, 2014 at 2:43 PM, Reka Thirunavukkarasu
wrote:
> Hi
>
> On Tue, Oct 28, 2014 at 2:22 PM, Isuru Haththotuwa
> wrote:
>
>>
>>
>> On Tue, Oct 28, 2014 at 1:48 PM, Reka Thirunavukkarasu
>> wrote:
>>
>>> Hi
>>>
>>> On Tue, Oct 28, 2014 at 1:16 PM, Isuru Haththotuwa
>>> wrote:
>>
Hi Devs,
WSO2 App-Factory which is an aPaaS uses apache stratos as the underline
PaaS framework. We need an improvement in stratos cartridge agent as per
the following description.
Based on the current setup of the app-factory it is necessary to inform
from cartridge side to app-factory side
Hmm yeah we are creating a new member, add it to the topology and
sending InstanceSpawnedEvent.
My concern was whether it is expensive to update the topology again and
again. But then realized that we are doing it every time when CC receives
each instance status event :)
So yeah, no problem. We c
Each event meant to carry a new set of information.
On Tue, Oct 28, 2014 at 11:07 AM, Rajkumar Rajaratnam
wrote:
> Hmm yeah we are creating a new member, add it to the topology and
> sending InstanceSpawnedEvent.
>
> My concern was whether it is expensive to update the topology again and
> again
MemberSpawned event will update it, isn't it?
On Tue, Oct 28, 2014 at 10:53 AM, Rajkumar Rajaratnam
wrote:
> Seems we are having a problem here. If we are adding to the topology as
> soon as CC gets a instance start up call, at that point we do not have
> information such as member ip, allocated
Seems we are having a problem here. If we are adding to the topology as
soon as CC gets a instance start up call, at that point we do not have
information such as member ip, allocated port and so on. If we add it to
the topology at this point, then we might need to update topology again
once we get
On Tue, Oct 28, 2014 at 3:00 PM, Nirmal Fernando
wrote:
> I think the correct approach would be to introduce a new topology event to
> fill the blind area between real instance creation via CC and member
> spawned event. So, as soon as CC receives a instance start up call, CC
> would add the memb
Hi,
I'm working on new UI console implementation started by Rukmal. I'll post
details soon.
Thank you,
Bst Regards,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Oct 28, 2014 at 11:00 AM, Imesh Gunaratne wrote:
> Hi Devs,
>
> Is anyone work
Hi Jerad,
Could you please attach the detailed log?
Thanks,
Sajith
On Tue, Oct 28, 2014 at 2:52 PM, Udara Liyanage wrote:
> Hi Jerad,
>
> From which branch you built the packs.
> Could you please check the fix mentioned by sajith in thread "Partition
> deployment issue" exist in your repositor
[
https://issues.apache.org/jira/browse/STRATOS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills closed STRATOS-912.
> Wiki - Document Composite Application Support
>
I think the correct approach would be to introduce a new topology event to
fill the blind area between real instance creation via CC and member
spawned event. So, as soon as CC receives a instance start up call, CC
would add the member to topology and will send a new event with a new state
possibly
Hi Jerad,
>From which branch you built the packs.
Could you please check the fix mentioned by sajith in thread "Partition
deployment issue" exist in your repository.
On Tue, Oct 28, 2014 at 2:43 PM, Jerad Rutnam wrote:
> Hi,
>
> I'm trying to create a partition in Stratos and im getting an erro
Hi,
I'm trying to create a partition in Stratos and im getting an error. can
anyone help me on getting this configured correctly?
*error*
Unable to build Iaas of this IaasProvider [Provider] : openstack. Unable to
build the jclouds object for iaas of type: openstack
*json config*
{
"id": "OS-P
Hi
On Tue, Oct 28, 2014 at 2:22 PM, Isuru Haththotuwa
wrote:
>
>
> On Tue, Oct 28, 2014 at 1:48 PM, Reka Thirunavukkarasu
> wrote:
>
>> Hi
>>
>> On Tue, Oct 28, 2014 at 1:16 PM, Isuru Haththotuwa
>> wrote:
>>
>>> Thanks Reka for starting this Thread.
>>>
>>> Found two issues related to undeplo
Hi Raj,
On Tue, Oct 28, 2014 at 2:23 PM, Rajkumar Rajaratnam
wrote:
> CC will add it to the topology, send member created event and send member
> terminated soon after that. Now AS will get this event and remove the
> member from its lists. We can't send member terminated events for members
> w
Hi,
I found the cause for this. Let me summarize.
- AS asks CC to create a container
- CC schedule a new task and returning member contexts to AS
- AS adding the members to pending list
- CC is also adding member contexts to its data holder
- But CC will not add it to the topology
On Tue, Oct 28, 2014 at 1:48 PM, Reka Thirunavukkarasu
wrote:
> Hi
>
> On Tue, Oct 28, 2014 at 1:16 PM, Isuru Haththotuwa
> wrote:
>
>> Thanks Reka for starting this Thread.
>>
>> Found two issues related to undeploying an Application:
>>1. https://issues.apache.org/jira/browse/STRATOS-918 -
Github user nirmal070125 commented on the pull request:
https://github.com/apache/stratos/pull/97#issuecomment-60723928
I'd like to review this PR. Await my feedback.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Hi
On Tue, Oct 28, 2014 at 1:16 PM, Isuru Haththotuwa
wrote:
> Thanks Reka for starting this Thread.
>
> Found two issues related to undeploying an Application:
>1. https://issues.apache.org/jira/browse/STRATOS-918 - Fixed now.
>
> 2. Undeploying an Application doesn't remove it properly
Thanks Reka for starting this Thread.
Found two issues related to undeploying an Application:
1. https://issues.apache.org/jira/browse/STRATOS-918 - Fixed now.
2. Undeploying an Application doesn't remove it properly until the
Member is activated. Looking in to this now.
On Tue, Oct 28, 2
Github user asankasanjaya commented on the pull request:
https://github.com/apache/stratos/pull/97#issuecomment-60719171
Sample configuration:
org.apache.stratos.cloud.controller.iaases.CloudstackIaas
cloudstack
Hi Devs,
We are now in the process of finalizing 4.1.0 M3 milstone. Shall we please
hold our commits for master branch until we complete this.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Hi all,
This is to update the testing Developer Preview-3 for the end to end work
flow. Since we have introduced the termination behaviour, we are executing
the following steps to verify flow.
* Deploy an composite application with nested groups
* Autoscaler wil bring them using defined startup
47 matches
Mail list logo
