Hi Udara,
There should be an agent.log file alongside the error.log file. The other
location is the /tmp/agent.screen.log.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Fri, Dec 19, 2014 at 1:09 PM, Udara Liyanage wrote:
>
> Hi Chamila,
>
Udara Liyanage created STRATOS-1045:
---
Summary: Application deployment does not recover after restart
Key: STRATOS-1045
URL: https://issues.apache.org/jira/browse/STRATOS-1045
Project: Stratos
Hi,
I think that worked. Thanks Raj.
On Fri, Dec 19, 2014 at 12:09 PM, Rajkumar Rajaratnam
wrote:
>
> Hi Udara,
>
> Seems that the cert has changed at amazon side.
>
> Can you import the amazon cert into the client-truststore and try again?
>
> Thanks.
>
> On Fri, Dec 19, 2014 at 12:02 PM, Udar
Udara Liyanage created STRATOS-1046:
---
Summary: Applcation undeployment is not succefull if application
did not become ACTIVE
Key: STRATOS-1046
URL: https://issues.apache.org/jira/browse/STRATOS-1046
Hi Chamila,
Earlier it was /var/log/apache/stratos . However it is not found in that
location. I only find the error.log within agent folder.
I see the below log config, however can not find agent.log.
[handler_log_file]
class=logging.FileHandler
level=INFO
formatter=default
args=("agent.log", "w
Hi Udara,
Seems that the cert has changed at amazon side.
Can you import the amazon cert into the client-truststore and try again?
Thanks.
On Fri, Dec 19, 2014 at 12:02 PM, Udara Liyanage wrote:
>
> Hi,
>
> Below exception is thrown when application is deployed.
>
> Region I have specified in
Hi,
Below exception is thrown when application is deployed.
Region I have specified in cloud-controller.xml and partition of the
deployment policy is ap-souteast-1.
TID: [0] [STRATOS] [2014-12-19 06:18:56,376] ERROR
{org.jclouds.http.handlers.BackoffLimitedRetryHandler} - Cannot retry
after se
Hi Dakshika,
We will remove it from backend.
Thanks.
On Fri, Dec 19, 2014 at 11:37 AM, Dakshika Jayathilaka
wrote:
>
> Hi Devs,
>
> AFAIK we have removed lowerLimit from definition. But in REST, deployment
> policy return lowerLimit as wel.
>
> [{"id" : "autoscale_policy_c4", "instanceRoundingF
Thank you Lahiru..
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Fri, Dec 19, 2014 at 11:44 AM, Lahiru Sandaruwan
wrote:
>
> Hi Dakshika,
>
> We will remove it from backend.
>
> Thanks.
>
> On Fri, Dec 19, 2014 at 11:37 AM, Dakshika Jayathilaka
> w
Hi
On Fri, Dec 19, 2014 at 11:40 AM, Lakmal Warusawithana
wrote:
>
>
>
> On Fri, Dec 19, 2014 at 11:16 AM, Imesh Gunaratne
> wrote:
>>
>> Hi Devs,
>>
>> It seems like we the existing application runtime domain model does not
>> represent instances in an hierarchical manner. Instances are defined
Github user nuwand commented on a diff in the pull request:
https://github.com/apache/stratos/pull/136#discussion_r22091127
--- Diff:
components/org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/api/StratosApiV41Utils.java
---
@@ -725,6 +725,91 @@ sta
Github user nuwand commented on a diff in the pull request:
https://github.com/apache/stratos/pull/136#discussion_r22091086
--- Diff:
components/org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/api/StratosApiV41Utils.java
---
@@ -725,6 +725,91 @@ sta
On Fri, Dec 19, 2014 at 11:16 AM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> It seems like we the existing application runtime domain model does not
> represent instances in an hierarchical manner. Instances are defined at
> each element but instance hierarchy is not visible.
>
> Shall we update the
Hi Devs,
AFAIK we have removed lowerLimit from definition. But in REST, deployment
policy return lowerLimit as wel.
[{"id" : "autoscale_policy_c4", "instanceRoundingFactor" : 0, "isPublic" :
false, "loadThresholds" : {"loadAverage" : {"lowerLimit" : 0, "threshold" :
75}, "memoryConsumption" : {"l
Hi Devs,
It seems like we the existing application runtime domain model does not
represent instances in an hierarchical manner. Instances are defined at
each element but instance hierarchy is not visible.
Shall we update the REST API application runtime domain model to represent
this?
Thanks
-
I have now verified this fix and pushed it to master branch. Please review.
Thanks
On Fri, Dec 19, 2014 at 10:46 AM, Imesh Gunaratne wrote:
>
> Hi Martin,
>
> The above error (related to the child policy) may have occurred due to the
> modification we did to change the "childId" attribute to "al
Hi Martin,
The above error (related to the child policy) may have occurred due to the
modification we did to change the "childId" attribute to "alias" in the
deployment policy. This was discussed in mail thread "[Discuss] The term
"ChildId" in the Deployment Policy refers to "Alias" in the Applica
Hi Imesh,
Me too encounter the same NPE
On Fri, Dec 19, 2014 at 3:33 AM, Martin Eppel (meppel)
wrote:
>
> I tried to fix it by adding a check (see code snippet) which resolved
> the NPE below but caused a new one – I guess it needs more than that …
>
>
>
> Code snippet:
>
> …
>
> *if (scalingDe
+1 for implementing application validation which we are not having at the
moment.
Thanks,
Reka
On Fri, Dec 19, 2014 at 12:43 AM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> I found the following error when deploying an application without
> deploying the cartridge groups. May be we need to have an a
Hi,
When I list deployment policies, I can find the deployed deployment policy.
Application undeployment logs are below. I thing undeployment did not
completed successfully.
TID: [0] [STRATOS] [2014-12-19 04:52:46,681] INFO
{org.apache.stratos.autoscaler.monitor.cluster.VMClusterMonitor} -
Pub
Hi,
I created an application and deployed with an deployment policy. Then I
undeployed and deleted the application
curl -X DELETE -H "Content-Type: application/json"
-d@'json/dep_single_group.json'
-k -v -u admin:admin
https://54.151.228.132:9443/api/applications/app_cartridge_v1/undeploy
curl -
Imesh Gunaratne created STRATOS-1044:
Summary: Validate Cartridge Groups when adding an Application
Key: STRATOS-1044
URL: https://issues.apache.org/jira/browse/STRATOS-1044
Project: Stratos
Hi Imesh,
I used the endpoint you have mentioned.
I have put the commands I have used and log correspond to the command.
On Fri, Dec 19, 2014 at 8:23 AM, Reka Thirunavukkarasu
wrote:
>
> Yah..I used this undeploy post to remove all the runtime of the
> application. Whatever we created using depl
Yah..I used this undeploy post to remove all the runtime of the
application. Whatever we created using deploy will be removed using this
POST undeploy command.
Thanks,
Reka
On Thu, Dec 18, 2014 at 11:57 PM, Imesh Gunaratne wrote:
>
> Hi Udara,
>
> We have introduced the following API method to u
I tried to fix it by adding a check (see code snippet) which resolved the NPE
below but caused a new one – I guess it needs more than that …
Code snippet:
…
if (scalingDependencies != null && !scalingDependencies.isEmpty()) {
for (ScalingDependentList scalingDependentList :
Hi Devs,
I'm seeing the below NPE in ParentComponentMonitor:
[2014-12-19 01:15:25,836] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
- Publishing Application Active event for [application]: single-group-app
[instance]:single-group-app-1
[2014-12-19 01:15:25,
Thanks Lakmal, yes I think we can reuse cluster min/max for Kubernetes
replica min/max.
On Fri, Dec 19, 2014 at 12:50 AM, Lakmal Warusawithana
wrote:
>
>
>
> On Fri, Dec 19, 2014 at 12:21 AM, Imesh Gunaratne
> wrote:
>>
>> Hi Devs,
>>
>> Currently we define Docker/Kubernetes configuration in the
On Fri, Dec 19, 2014 at 12:21 AM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> Currently we define Docker/Kubernetes configuration in the cartridge
> definition using a property called deployerType.
>
> This properly can only have the value "kubernetes". I think it would be
> better if we could reuse t
Hi Devs,
I found the following error when deploying an application without deploying
the cartridge groups. May be we need to have an application definition
validation rule to detect this at the application creation time.
[2014-12-18 23:19:12,809] ERROR
{org.apache.axis2.rpc.receivers.RPCInOnlyMes
Hi Devs,
Currently we define Docker/Kubernetes configuration in the cartridge
definition using a property called deployerType.
This properly can only have the value "kubernetes". I think it would be
better if we could reuse the IaasProvider section for this. WDYT?
A sample cartridge definition:
Hi Udara,
We have introduced the following API method to undeploy an application [1]:
POST /applications/{applicationId}/undeploy
Reka: Did you made the above modifcation to undeploy an application and
then delete it if we receive a DELETE request for a running application?
[1]
https://cwiki.apa
Hi Reka,
Thank I will continue testing tomorrow.
Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 18, 2014 11:16 PM, "Reka Thirunavukkarasu" wrote:
> Hi Udara,
>
> I have fixed the flow in ff9379f66cd5c66dfa3bcba42df4c949407f2883. With
> the same undeploy application comm
Hi Udara,
I have fixed the flow in ff9379f66cd5c66dfa3bcba42df4c949407f2883. With the
same undeploy application command, application runtime will get removed
after wiping out the members of the clusters. Now i could undeploy
the application and deploy the same again without any issue.
Thanks,
Rek
It seems that we are not removing the runtime and trying to remove the
policy/persisted application. Since we have changed the application
deployment flow, the earlier application undeployment is no longer working.
We will have to fix this...
Thanks,
Reka
On Thu, Dec 18, 2014 at 7:30 PM, Udara Li
Hi Imesh,
I deployed application and deployment policy. Instances got started up
successfully. Now I want to terminate the instances.
I tried undeploying as below.
*curl -X DELETE -H "Content-Type: application/json"
-d@'json/dep_single_group.json' -k -v -u admin:admin
https://54.151.228.132:9443/
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/136#issuecomment-67485237
Thanks Kasun for pointing out this.
Yeah it is better to have whole exception than only the message.
I added PR#154 for this.
Thanks,
Gayan
[
https://issues.apache.org/jira/browse/STRATOS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1043:
-
Description: Currently CLI JAR file contains all the dependent classes.
According to thi
[
https://issues.apache.org/jira/browse/STRATOS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1043:
-
Description: Currently CLI JAR file contains all the dependent classes.
According to thi
[
https://issues.apache.org/jira/browse/STRATOS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1043.
--
Resolution: Fixed
Fixed with commit revision: 7e6aaf1fd46afcc9f16d510c76b9af322720e1f2
Imesh Gunaratne created STRATOS-1043:
Summary: Refine CLI JAR File and Distribution Structure
Key: STRATOS-1043
URL: https://issues.apache.org/jira/browse/STRATOS-1043
Project: Stratos
Is
[
https://issues.apache.org/jira/browse/STRATOS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1043:
-
Affects Version/s: 4.1.0 M5
> Refine CLI JAR File and Distribution Structure
> -
[
https://issues.apache.org/jira/browse/STRATOS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1043:
-
Component/s: CLI
> Refine CLI JAR File and Distribution Structure
>
[
https://issues.apache.org/jira/browse/STRATOS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1043:
-
Fix Version/s: 4.1.0 Alpha
> Refine CLI JAR File and Distribution Structure
> --
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/156#issuecomment-67478035
Thanks for your contribution Dakshika! I have now merged this pull request
to master branch.
---
If your project is set up for it, you can reply to this email and have yo
I thought the other way around: application.id
Since the entity name is already there, we might not need to repeat it in
the property name.
Thanks
On Thu, Dec 18, 2014 at 3:20 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
>
> Hi,
>
> +1, I think "application.applicationId" convent
Github user kasun04 commented on a diff in the pull request:
https://github.com/apache/stratos/pull/136#discussion_r22037055
--- Diff:
components/org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/api/StratosApiV41Utils.java
---
@@ -725,6 +725,91 @@ st
GitHub user dakshika opened a pull request:
https://github.com/apache/stratos/pull/156
Bring deployment json definition into application section
done initial work for [1042]
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dakshika
Dakshika Jayathilaka created STRATOS-1042:
-
Summary: Bring deployment json definition into application section
Key: STRATOS-1042
URL: https://issues.apache.org/jira/browse/STRATOS-1042
Project:
Hi,
+1, I think "application.applicationId" convention is more readable.
Thanks !
On Thu, Dec 18, 2014 at 3:12 PM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> As I noticed we have named most of the identity fields in the domain
> classes in the REST API as "id":
> applicationLevelNetworkPartition.i
[
https://issues.apache.org/jira/browse/STRATOS-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1041:
-
Summary: Ability to define Cartridge Groups inline in the Application
Definition (was:
Imesh Gunaratne created STRATOS-1041:
Summary: Ability to Define Cartridge Groups inline in the
Application Definition
Key: STRATOS-1041
URL: https://issues.apache.org/jira/browse/STRATOS-1041
Pro
Hi Devs,
As I noticed we have named most of the identity fields in the domain
classes in the REST API as "id":
applicationLevelNetworkPartition.id
childLevelNetworkPartition.id
childLevelPartition.id
partition.id
autoscalingPolicy.id
However application identity field is named as "applicationId":
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1040:
-
Attachment: screenshot-2.png
> Refine Cloud Controller Package Structure
> -
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1040:
-
Description: I found twenty two top level packages in cloud controller and
several unuse
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1040.
--
Resolution: Fixed
Fixed as shown in attached image: screenshot-2.png
> Refine Cloud C
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1040:
-
Fix Version/s: 4.1.0 Alpha
> Refine Cloud Controller Package Structure
> ---
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1040:
-
Description: I found twenty two top level packages in cloud controller and
several unuse
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1040:
-
Attachment: screenshot-1.png
> Refine Cloud Controller Package Structure
> -
[
https://issues.apache.org/jira/browse/STRATOS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1040:
-
Summary: Refine Cloud Controller Package Structure (was: Refine Cloud
Controller Packag
Imesh Gunaratne created STRATOS-1040:
Summary: Refine Cloud Controller Package Strcture
Key: STRATOS-1040
URL: https://issues.apache.org/jira/browse/STRATOS-1040
Project: Stratos
Issue Ty
Thanks Reka! Yes, we will use the master branch from now on.
Thanks
On Thu, Dec 18, 2014 at 1:06 PM, Reka Thirunavukkarasu
wrote:
>
> Thanks Udara and Imesh for merging 4.1.0-test to master..Will continue to
> work in master..
>
> Thanks,
> Reka
>
> On Thu, Dec 18, 2014 at 12:40 PM, Imesh Gunara
[
https://issues.apache.org/jira/browse/STRATOS-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1034:
-
Component/s: REST API
> Cartridge Definition in Cartridge Deployment API Method is Diffe
[
https://issues.apache.org/jira/browse/STRATOS-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1034.
--
Resolution: Fixed
> Cartridge Definition in Cartridge Deployment API Method is Differe
[
https://issues.apache.org/jira/browse/STRATOS-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251383#comment-14251383
]
Imesh Gunaratne commented on STRATOS-1034:
--
Fixed with commit revision: 8a2faa2
[
https://issues.apache.org/jira/browse/STRATOS-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1034:
-
Fix Version/s: 4.1.0 Alpha
> Cartridge Definition in Cartridge Deployment API Method is
[
https://issues.apache.org/jira/browse/STRATOS-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne reassigned STRATOS-1034:
Assignee: Imesh Gunaratne
> Cartridge Definition in Cartridge Deployment API Meth
66 matches
Mail list logo
