Re: [Discuss] Deployment policy needs to be validated

Yeah.Good point Raj. It is better to have that validation too. Thanks, Gayan On Mon, Feb 16, 2015 at 1:19 PM, Rajkumar Rajaratnam wrote: > To be more clear, > > I am not telling we need to validate "network partitions" while deploying > deployment policy. I am telling we should validate whether

Re: [Discuss] Deployment policy needs to be validated

To be more clear, I am not telling we need to validate "network partitions" while deploying deployment policy. I am telling we should validate whether all the network partitions given in the deployment policy are already *deployed/added or not*. This validation is different from network partitions

Re: [Discuss] Deployment policy needs to be validated

Hi Gayan, Please find my comments inline. On Mon, Feb 16, 2015 at 12:41 PM, Gayan Gunarathne wrote: > Hi Raj, > > I think we don't need to validate the network partition stuff with the > deployment policy.It should validate through network partition management > API. > The validation I am talk

Re: [Discuss] Deployment policy needs to be validated

Hi Raj, I think we don't need to validate the network partition stuff with the deployment policy.It should validate through network partition management API. Deployment policy has only the reference to the network partitions.Network partition management is done through separate REST API methods.

[Discuss] Deployment policy needs to be validated

Hi Devs, I guess $Subject is not done at the moment. I am in the process of adding the validation. This is the sample deployment policy. { "id": "deployment-policy-2", "networkPartition": [ { "id": "network-partition-1", "partitionAlgo": "one-after-another",

Re: Add Me to Apache stratos JIRA

Hi, We are still unable to assign JIRA's to myself. Do i need to create a JIRA for this directed towards the Apache Infra team or are the credentials/access be given through stratos.apache? Thanks & Regards Shavindri Dissanayake Technical Writer LinkedIn Profile

Re: Adding CLI commands to describe a tenant and list available tenants

Hi all, Please find the PR[1] for the $subject. [1] - https://github.com/apache/stratos/pull/228 On Mon, Feb 16, 2015 at 10:50 AM, Dinithi De Silva wrote: > Hi all, > > I am adding the missed CLI commands for describing a tenant[1] and list > available tenants by a part of the domain name[2]. >

[GitHub] stratos pull request: Adding CLI commands to describe a tenant and...

GitHub user dinithis opened a pull request: https://github.com/apache/stratos/pull/228 Adding CLI commands to describe a tenant and list available tenants by part of the domain name Adding CLI commands to describe a tenant and list available tenants by part of the domain name You

Adding CLI commands to describe a tenant and list available tenants

Hi all, I am adding the missed CLI commands for describing a tenant[1] and list available tenants by a part of the domain name[2]. [1] describe-tenant [2] list-tenants-by-partial-domain -- *Dinithi De Silva* Associate Software Engineer, WSO2 Inc. m:+94716667655 | e:dinit...@wso2.com | w: www.ws

[jira] [Commented] (STRATOS-1184) Docker image for php:4.1.0-alpha does not get downloaded

[ https://issues.apache.org/jira/browse/STRATOS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322350#comment-14322350 ] Mariangela Hills commented on STRATOS-1184: --- When I checked the very next day

Re: Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

Hi David, On Mon, Feb 16, 2015 at 6:46 AM, david hbase wrote: > build from source, running Stratos as all in one. I just turn on the > activeMQ and puppet master, then run the ./bin/stratos.sh > > Did you build from the 4.0.0-rc4 tag? Recommend to used 4.0.0-rc4 tag or binary release on [1]. 4.

Re: Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

The screenshot has been attached. Thanks -D On Sun, Feb 15, 2015 at 5:29 PM, david hbase wrote: > The port 9443 is listening now: > > root@stratos40build05:/opt/stratos-installer# telnet stratos40build05 9443 > > Trying 127.0.0.1... > > Connected to stratos40build05. > > Escape character is '^]

Re: Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

Hi , Seems you are running all in one setup. Could you try weather AS service is running on the host by telnet as telnet stratos40build05 9443 On Mon, Feb 16, 2015 at 6:48 AM, david hbase wrote: > web console is working, but can not create partition via web UI > > Error: Error while getting av

Re: Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

web console is working, but can not create partition via web UI Error: Error while getting available partitions. Cause : The service cannot be found for the endpoint reference (EPR) https://stratos40build05:9443/services/AutoscalerService/ -D On Sun, Feb 15, 2015 at 5:16 PM, david hbase wrote:

Re: Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

build from source, running Stratos as all in one. I just turn on the activeMQ and puppet master, then run the ./bin/stratos.sh not sure about the AS service. could you send the detail instruction? Thanks -D On Sun, Feb 15, 2015 at 5:05 PM, Udara Liyanage wrote: > Hi, > > Are you running Stra

Re: Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

Hi, Are you running Stratos all in one setup or as distributed setup. According to the error Stratos manager can not access autoscaler service at " https://stratos40build05:9443/services/AutoscalerService/"; . Could you please verify AS is running on the specified host. On Mon, Feb 16, 2015 at 6:

Stratos 4.0 ERROR {org.apache.axis2.engine.AxisEngine}

Hi, Team I need to push the Stratos deployment with POC now. Since Stratos 4.1 is not in stable version yet, so I am trying to make the Stratos 4.0 working with openstack now. Please advice and thanks in adv, -D The Error log as following: [2015-02-16 00:51:16,123] INFO {org.wso2.carbon.ui.int

Re: [Discuss] [Diagram] Stratos 4.1.0 Messaging Model

Great work Imesh. Should openstack and ec2 iaases be also included in this diagram? On Sun, Feb 15, 2015 at 11:17 PM, Gayan Gunarathne wrote: > Great work Imesh. Indeed It is really useful diagram. > > I think we can add event names to the message flow and maintain this > diagram in our wiki as

Re: [Discuss] [Diagram] Stratos 4.1.0 Messaging Model

Thanks Gayan! I have now corrected the error which Sajith pointed out and added the diagram to the Wiki [1]. We need to update this page when we get time. [1] https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Stratos+Pub-Sub+Communication Thanks On Sun, Feb 15, 2015 at 11:17 PM, Gayan Gu

[Discuss] Impressed with Kubernetes Documentation

Hi Devs, I'm impressed with how Kubernetes has organized their documentation [1]. It is nicely arranged, simple and easier to find content. I think we can take this as a reference for re-arranging Stratos documentation for 4.1.0. [1] https://github.com/GoogleCloudPlatform/kubernetes/tree/master/

[jira] [Resolved] (STRATOS-1189) Introduce REST API methods for add/update deployment policies

[ https://issues.apache.org/jira/browse/STRATOS-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayan Gunarathne resolved STRATOS-1189. --- Resolution: Fixed Fixed with 30a47842a13fd603e4bd93291d0c534f2fbe9874 > Introduce

[jira] [Updated] (STRATOS-1189) Introduce REST API methods for add/update deployment policies

[ https://issues.apache.org/jira/browse/STRATOS-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayan Gunarathne updated STRATOS-1189: -- Affects Version/s: 4.1.0 Alpha Fix Version/s: 4.1.0 > Introduce REST API meth

[jira] [Created] (STRATOS-1189) Introduce REST API methods for add/update deployment policies

Gayan Gunarathne created STRATOS-1189: - Summary: Introduce REST API methods for add/update deployment policies Key: STRATOS-1189 URL: https://issues.apache.org/jira/browse/STRATOS-1189 Project: S

Re: [Discuss] [Diagram] Stratos 4.1.0 Messaging Model

Great work Imesh. Indeed It is really useful diagram. I think we can add event names to the message flow and maintain this diagram in our wiki as well. Thanks, Gayan On Sun, Feb 15, 2015 at 11:01 PM, Imesh Gunaratne wrote: > Great! nice to hear that Sajith! > > What you have thought is correct

Re: REST API methods for managing deployment policies

This deployment policy modification are inline with the email [1] I will share the document regarding this modification. [1] 4.1 deployment policy questions Thanks, Gayan On Sun, Feb 15, 2015 at 10:31 PM, Gayan Gunarathne wrote: > Hi Shaheedur, > > With the REST API re-factor, there were chang

Re: [Discuss] [Diagram] Stratos 4.1.0 Messaging Model

Great! nice to hear that Sajith! What you have thought is correct, solid lines represent message publishers and dashed lines show message subscribers. Yes that's a mistake, cloud controller to instance notifier topic should be a solid line. Thanks On Sun, Feb 15, 2015 at 10:55 PM, Sajith Kariyaw

Re: [Discuss] [Diagram] Stratos 4.1.0 Messaging Model

Hi Imesh, Great work, this is useful! Could you please explain a bit the difference between dashed and solid arrows, and the directions, ? As I understood solid arrow towards MB represent "publishes", and dashed arrow represents "subscribes". But why CC -> Instance Notifier topic is dashed? On S

Re: Cartridge Agent - Auto Commit functionality

+1 It need to be pass through the application definition and we can pass that value through event or cartridge payload to the cartridge.IMO If we can pass it through the cartridge payload , we will able to maintain that value as system parameter and can use where ever we want. Thanks, Gayan On S

Re: Cartridge Agent - Auto Commit functionality

Hi Chamila, A good finding! Yes I also cannot see the autoCommit attribute in Artifact Repository bean in the application definition. This functionality might be needed for certain cartridges for propagating changes that they do via the UI. Therefore we may need to add it. Thanks On Sun, Feb 15

Re: 4.1 deployment policy questions

Hi Shaheed, Please find comments inline: On Sun, Feb 15, 2015 at 8:03 PM, Shaheedur Haque (shahhaqu) < shahh...@cisco.com> wrote: > OK, I think we are close. In the following reply, I am only concerned > with the users view, not any Stratos internal concepts or names. > > > > I define an “appli

Re: REST API methods for managing deployment policies

Hi Shaheedur, With the REST API re-factor, there were changes happen with the REST API method definitions.As a result our API methods change some what. As an example v 4.0 rest API was POST /policy/deployment Now for v 4.1.0 we introduce it as POST /deploymentPolicies to align with the REST API st

Re: REST API methods for managing deployment policies

Shaheed: I still could not go through the new APIs in detail, do you think they are different from 4.0.0? Gayan: Thanks for the update! IMO it would be better to put all the information of this modification in a Google document and share in this thread. Thanks On Sun, Feb 15, 2015 at 10:21 PM, G

Re: REST API methods for managing deployment policies

Sorry for the late reply.Now I have completed the followings. Rest API method for adding deployment policy Rest API method updating deployment policy Rest API method for removing deployment policy Also I have added the deployment policy to our samples. Also found that "SubscribableInfo" section

Re: SubscriptionDomainAddedEvent and SubscriptionDomainRemovedEvent

Thanks for the explanation Imesh. On Feb 15, 2015 7:24 PM, "Imesh Gunaratne" wrote: > Hi Chamila, > > These domain mapping events are only used by load balancers. > > Thanks > > On Sunday, February 15, 2015, Chamila De Alwis wrote: > >> Hi Udara, Imesh, >> >> Thanks for the detailed explanation.

RE: REST API methods for managing deployment policies

Is there a reason not to make these APIs exactly like they were for 4.0? From: Imesh Gunaratne [mailto:im...@apache.org] Sent: 15 February 2015 03:56 To: dev Subject: Re: REST API methods for managing deployment policies Gayan/Udara: It would be great if you guys can keep updating a mail thread w

RE: 4.1 deployment policy questions

OK, I think we are close. In the following reply, I am only concerned with the users view, not any Stratos internal concepts or names. I define an “application instance” to be something which is created in response to combining an application.json (which contains references to named deployment

Re: SubscriptionDomainAddedEvent and SubscriptionDomainRemovedEvent

Hi Chamila, These domain mapping events are only used by load balancers. Thanks On Sunday, February 15, 2015, Chamila De Alwis wrote: > Hi Udara, Imesh, > > Thanks for the detailed explanation. I am concerned over the cartridge > agent's behavior when receiving these events. Should the agent u

Re: SubscriptionDomainAddedEvent and SubscriptionDomainRemovedEvent

Hi Udara, Imesh, Thanks for the detailed explanation. I am concerned over the cartridge agent's behavior when receiving these events. Should the agent update any of its data based on these events or should it only expose them to the extensions/plugins? Regards, Chamila de Alwis Software Engineer

Cartridge Agent - Auto Commit functionality

Hi, In the cartridge agent's artifact management, the auto commit flag can be set either by configuration (ex: Puppet) or via the ArtifactUpdatedEvent. Currently this is read from the configuration only. Is this now specified as a subscribable info in the application definition? I can't find a sa

Re: [Discuss] Fixing Grouping Functionality

I think I found the reason for not publishing Artifact Updated event. It looks like the Mock IaaS is responding fast and SM is receiving the Instance Started event before receiving the Application Created event. I'm now fixing this. Thanks On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne wrote:

[jira] [Commented] (STRATOS-1188) Add inline help with form rendering logic

[ https://issues.apache.org/jira/browse/STRATOS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321809#comment-14321809 ] ASF GitHub Bot commented on STRATOS-1188: - Github user asfgit closed the pull re

Re: 4.1 deployment policy questions

Hi Shaheed, On Sun, Feb 15, 2015 at 12:09 AM, Shaheedur Haque (shahhaqu) < shahh...@cisco.com> wrote: > Imesh, Gayan, > > > > I look forward to the updated JSON samples; they will no doubt help reduce > confusion. > > > Yes we will send this ASAP. > Just to comment briefly on the replies you

[jira] [Created] (STRATOS-1188) Add inline help with form rendering logic

Dakshika Jayathilaka created STRATOS-1188: - Summary: Add inline help with form rendering logic Key: STRATOS-1188 URL: https://issues.apache.org/jira/browse/STRATOS-1188 Project: Stratos

[jira] [Commented] (STRATOS-1188) Add inline help with form rendering logic

[ https://issues.apache.org/jira/browse/STRATOS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321794#comment-14321794 ] ASF GitHub Bot commented on STRATOS-1188: - GitHub user dakshika opened a pull re

[Discuss] Fixing Grouping Functionality

Hi Devs, I just did a quick test to verify grouping functionality with sample applications and following is the current status: ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot Activatingdependent-scaling/sample-cartridgesActivates but found few errorsArtifact update event is

Re: [Discuss] [Issue] Application Monitor is not created if Complete Topology was not received

I have now fixed this issue by publishing the Complete Topology event at the Cloud Controller startup. Now the server is usable as soon as it prints the managerment console URL. The problem was that the topology synchronizer task was not running initially when its scheduled. Thanks On Fri, Feb 6

Re: REST API methods for managing deployment policies

Gayan/Udara: It would be great if you guys can keep updating a mail thread with the progress of this modification; which tasks are done and which tasks to be started. Then others should also be able to contribute when you are not around. Thanks On Fri, Feb 13, 2015 at 7:41 PM, Gayan Gunarathne w

[GitHub] stratos pull request: After alpha 5 fixes - including [STRATOS-118...

GitHub user dakshika opened a pull request: https://github.com/apache/stratos/pull/227 After alpha 5 fixes - including [STRATOS-1188] You can merge this pull request into a Git repository by running: $ git pull https://github.com/dakshika/stratos after-alpha-5 Alternatively

[GitHub] stratos pull request: After alpha 5 fixes - including [STRATOS-118...

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/227 --- 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

PR for inline help support in UI

Hi Devs, please merge this PR: https://github.com/apache/stratos/pull/227 Regards, Dakshika *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911