Hi All,
As we have the instances support for group and cluster, we need to name it
with a unique id as the instances are dynamically added/removed. So, i'm
going to name the group instance as -.
Thanks,
Reka
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile:
+1 for above, then we can provide better UX on console app.
Thank you,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Mon, Dec 15, 2014 at 11:10 AM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> At the moment we have a confusion in the application deploym
Hi Devs,
At the moment we have a confusion in the application deployment process:
- We use two different application definitions for creating applications
and retrieving them (Application|Application Runtime)
- Created application definitions are not persisted
- As a result it is difficult for the
Hi,
You have to secute below database queries
within tools/stratos-installer/resources in addition to mysql.sql in the
under the same directory.
application-mysql.sql
security-mysql.sql
I have added them to setup.sh also. Please take an update from the
4.1.0-test branch.
On Mon, Dec 15, 2014 at
Yah Martin. We are actively working on 4.1.0-test branch. But it is stable
upto deploying or undeploying an application. We have done most of the
fixes for all other scenarios by verifying them. So, some functionality
might there to be fixed. We will merge everything to master once we fixed
the rem
Thanks Lahiru..Yah..It seems that it is working for me now..Not sure
whether this happened due to any local changes. However i didn't have
changes in ParentComponentMonitor where executor service is used..
Thanks,
Reka
On Sun, Dec 14, 2014 at 11:43 PM, Lahiru Sandaruwan
wrote:
>
> Looks like mon
Hi Martin,
This is due to that you have not executed databases related to oAuth added
recently. I will point you to the database location soon.
On Mon, Dec 15, 2014 at 9:50 AM, Martin Eppel (meppel)
wrote:
>
> [Resending it with a slightly different Subject]
>
>
>
> I run into the following iss
Forgot to ask, which branch should I be using, master or test branch ?
Seem like the test branch has a lot of new fixes ?
From: Martin Eppel (meppel)
Sent: Sunday, December 14, 2014 8:22 PM
To: dev
Subject: RE: [Testing] Stratos 4.1.0 Alpha - error deploying cartridge
Thanks, I will look into it
Thanks for the update
Regards
Martin
From: Gayan Gunarathne [mailto:gay...@wso2.com]
Sent: Saturday, December 13, 2014 7:04 AM
To: dev@stratos.apache.org
Subject: Re: [Testing] Stratos 4.1.0 Alpha - error deploying cartridge
Yeah we made category as a mandatory as every cartridge should have a
[Resending it with a slightly different Subject]
I run into the following issue when I tried to deploy a cartridge (based on
Friday’s code from master):
- looks like the database schema has changed and a new field was added.
My question is, how is this supposed to work, do we need to apply the n
Thanks, I will look into it once I get the python cartridge agent working since
the java based one seems to be broken
From: Reka Thirunavukkarasu [mailto:r...@wso2.com]
Sent: Friday, December 12, 2014 8:42 PM
To: dev
Subject: Re: [Testing] Stratos 4.1.0 Alpha - error deploying cartridge
Hi Marti
If to use that we currently have a path conflict with GET
/cartridges/{filter}
This was added to remove the different methods we used to have earlier -
/cartridges/multitenant , /cartridges/singletenant and
cartridges/loadbalancer
However now since we have also introduced a "category" field as we
Hi,
I mixed up with application Creation. Thanks for clarification.
Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 14, 2014 10:54 PM, "Imesh Gunaratne" wrote:
> Hi Dakshika,
>
> It seems like the "id" field is not defined in the deployment policy.
> That's why it is pri
Looks like monitors are working fine for me.
On Sun, Dec 14, 2014 at 11:14 PM, Reka Thirunavukkarasu
wrote:
>
> Please note that i have just pulled and updated with the fresh pack. In
> that only, i found this issue..
>
> On Sun, Dec 14, 2014 at 11:13 PM, Reka Thirunavukkarasu
> wrote:
>>
>> Hi
Thanks Imesh.. !
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Sun, Dec 14, 2014 at 10:46 PM, Imesh Gunaratne wrote:
>
> Thanks Dakshika! Pull request 152 is now merged to 4.1.0-test branch.
>
> Thanks
>
> On Sun, Dec 14, 2014 at 6:50 PM, Dakshika J
Please note that i have just pulled and updated with the fresh pack. In
that only, i found this issue..
On Sun, Dec 14, 2014 at 11:13 PM, Reka Thirunavukkarasu
wrote:
>
> Hi
>
> I'm experiencing the $subject. It is only starting application monitor.
> Then no other monitors are coming up. This bl
Hi
I'm experiencing the $subject. It is only starting application monitor.
Then no other monitors are coming up. This blocks the application
deployment.
Am i missing any configuration?
Thanks,
Reka
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442
Hi Dakshika,
It seems like the "id" field is not defined in the deployment policy.
That's why it is printed as null. We might need to make it mandatory.
Udara: Application deployment happens with a deployment policy.
Thanks
On Sun, Dec 14, 2014 at 8:49 PM, Dakshika Jayathilaka
wrote:
>
> Hi Uda
The problem we have here is that cartridge type is the key of the cartridge
entity. IMO we should be able to retrieve the entity using the key.
Thanks
On Sun, Dec 14, 2014 at 7:24 PM, Shiroshica Kulatilake
wrote:
>
>
> The resource url supported now is
>
> GET /cartridges/{category}/{cartridgeT
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/152#issuecomment-66920292
Thanks Dakshika! This pull request is now merged to 4.1.0-test branch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Thanks Dakshika! Pull request 152 is now merged to 4.1.0-test branch.
Thanks
On Sun, Dec 14, 2014 at 6:50 PM, Dakshika Jayathilaka
wrote:
>
> Hi Imesh,
>
> I have fixed the issues encountered after $(subject). please merge below PR
>
> PR: https://github.com/apache/stratos/pull/152
>
> Thank you
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/152
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Hi Udara,
Thanks for the clarification.
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Sun, Dec 14, 2014 at 6:44 PM, Udara Liyanage wrote:
>
> Hi,
>
> At the time of application deployment, there is no deployment policy
> (please update me if I'm wr
Hi,
+1 currently app is parsed and stored in registry. When deployment policy
is deployed, topology get updated with runtime data. So original definition
is not there anymore. Need to store the definition in registry upon
successfully parsing.
Touched, not typed. Erroneous words are a feature,
The resource url supported now is
GET /cartridges/{category}/{cartridgeType}
On Sun, Dec 14, 2014 at 12:25 PM, Imesh Gunaratne wrote:
>
> Hi Shiro,
>
> I found a problem with GET cartridges method:
> Now it is not possible to get cartridges for a given cartridge type:
>
> GET /cartridges/{cartr
+1 - we need to be able to identify which applications have been deployed.
Currently there is no GET on this
On Sun, Dec 14, 2014 at 6:15 PM, Dakshika Jayathilaka
wrote:
>
> Hi Devs,
>
> We need to have GET applicationDeployments/ endpoint on REST API to list
> down all application deployment de
Hi Imesh,
I have fixed the issues encountered after $(subject). please merge below PR
PR: https://github.com/apache/stratos/pull/152
Thank you,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Sun, Dec 14, 2014 at 12:05 PM, Imesh Gunaratne wrote:
>
GitHub user dakshika opened a pull request:
https://github.com/apache/stratos/pull/152
Fix console app after Removing The Wrapping Object in the Collection
Responses [1036]
Fix console app after Removing The Wrapping Object in the Collection
Responses
You can merge this pull reque
Dakshika Jayathilaka created STRATOS-1036:
-
Summary: Fix Console App After Removing The Wrapping Object in the
Collection Responses
Key: STRATOS-1036
URL: https://issues.apache.org/jira/browse/STRATOS-1036
Hi,
At the time of application deployment, there is no deployment policy
(please update me if I'm wrong) thus deployment policy id is null. I don't
think this is an issue. Plus log is an info log.
Ideally highlighted text should be removed.
Touched, not typed. Erroneous words are a feature, not
Hi Devs,
when i try to do application deployment i'm getting below info logs.
[2014-12-14 18:29:45,673] INFO
{org.apache.stratos.rest.endpoint.api.StratosApiV41Utils} - Starting to
deploy application: [application-id] app_group_v1 *[deployment-policy-id]
null*
[2014-12-14 18:29:45,679] INFO
{o
Great work Dakshita
Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 14, 2014 11:47 AM, "Nirmal Fernando" wrote:
> Great work Dakshika!!
>
> On Sun, Dec 14, 2014 at 9:05 AM, Dakshika Jayathilaka
> wrote:
>>
>> Hi All,
>>
>> Thank you, I'm planning to do group creation and
There seems to be a cyclic dependency which prevents us sending this
information:
Cartridge -> IaasProvider -> Iaas -> IaasProvider -> Iaas
We might need to solve this separately.
On Sun, Dec 14, 2014 at 5:13 PM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> I found $subject. As a result in the CLI/UI
Hi Devs,
We need to have GET applicationDeployments/ endpoint on REST API to list
down all application deployment definitions. currently we have POST and
DELETE only.
I tried to use GET /deploymentPolicies, seems it return incorrect output.
Can Someone have a look
Thank you.
Bst Regards,
*Dak
Hi Devs,
I found $subject. As a result in the CLI/UI we cannot display IaaS provider
information when displaying cartridges.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
+1. A read write locking model can be used (similar to the one we have in
Topology and Applications) at the cluster monitor level.
On Sun, Dec 14, 2014 at 7:19 AM, Nirmal Fernando
wrote:
>
> +1 Reka. I hope this won't be a global level lock rather a cluster level
> lock.
>
> On Sun, Dec 14, 2014
Hi Imesh,
I think this is happens due to the bean class changes when supporting
nested groups. We need to update the beans in CLI as well.
Thanks !
On Sat, Dec 13, 2014 at 8:57 PM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> I found several problems in the CLI where resource paths were not updated
37 matches
Mail list logo