Re: autoscaler issue with multiple cartridges + subscriptions

Hi David, I have few concerns about your deployment policies. 1. I see only 2 deployment policies defined: static-1, autoscale-1-2 But in the cartridge subscription I can see a deployment policy named autoscale-1-5. Where did that come from? Can you share your complete deployment policy/policies?

Re: [gsoc] Unable to Access the Stratos UI interface

For AWS internal calls, it's always better to use private IP of the instance rather than public IPs. On Fri, Aug 1, 2014 at 8:29 AM, Akila Ravihansa Perera wrote: > Hi Asiri, > > I presume you were able to telnet to ActiveMQ only after changing the > security group in EC2? > > Check your /etc/h

Re: autoscaler issue with multiple cartridges + subscriptions

Hi David, Is there any possibility of enabling following logger in the log4j.properties file ? log4j.logger.org.apache.stratos.autoscaler.rule.RuleLog=DEBUG For each service cluster, we run a Cluster Monitor and that is responsible for monitoring and scaling the cluster? On Thu, Jul 31, 2014

Re: autoscaler issue with multiple cartridges + subscriptions

On Fri, Aug 1, 2014 at 11:30 AM, Nirmal Fernando wrote: > Hi David, > > Is there any possibility of enabling following logger in the > log4j.properties file ? > > log4j.logger.org.apache.stratos.autoscaler.rule.RuleLog=DEBUG > > For each service cluster, we run a Cluster Monitor and that is respo

Re: stratos docker provider

Yes, seems like different people doing same thing without collaborating :) I've done the initial docker implementation for stratos months back and [1] is the email thread. In fact I implemented a jclouds API for docker too and then later realized there's another implementation (one that has been p

Re: stratos docker provider

Guys, I see that we've stopped/suspended or conflicted that feature for a while. I myself willing to contribute but can't see any method to collaborate with another guys interesting on that. Each of us works dependently and then make many conflictions. My recommendation is that we need a hangout t

[GitHub] stratos pull request: Fix Readme.md format (add missing line break...

Github user maicole commented on the pull request: https://github.com/apache/stratos/pull/5#issuecomment-50766643 Thanks, Chris. Glad I could help a bit. Hope to see more adoption of Stratos! --Michael On Mon, Jul 28, 2014 at 1:25 PM, Chris Snow wrote:

Re: [gsoc] Unable to Access the Stratos UI interface

Hi Asiri, I presume you were able to telnet to ActiveMQ only after changing the security group in EC2? Check your /etc/hosts file again for any duplicate entries for that hostname. Also try doing a dnslookup and see whether stratos.apache.org actually points to the desired IP. Thanks. On Fri, A

Re: [gsoc] Unable to Access the Stratos UI interface

On Thu, Jul 31, 2014 at 11:23 PM, Akila Ravihansa Perera wrote: > Hi Asiri, > > I think this is because of the EC2 security group that you have configured > in your instance. Have you opened the ports required by Stratos and > ActiveMQ (Message Broker)? > Yep after changing the security group se

Re: CLI resource path auto-completion support

Great work Sajith! This is very useful! On Thu, Jul 31, 2014 at 10:44 AM, Nirmal Fernando wrote: > Nice work Sajith! > > > On Thu, Jul 31, 2014 at 1:48 PM, Sajith Kariyawasam > wrote: > >> Hi, >> >> I have just added $subject, which I thought will be useful. >> Now the resource-path will be au

Re: [gsoc] Unable to Access the Stratos UI interface

Hi, Can you check whether ActiveMQ is accessible from Stratos machine. Try telnet 54.191.61.79 61616 Touched, not typed. Erroneous words are a feature, not a typo.

Re: stratos docker provider

Hi Chris, I don't have anything solid to present yet. I haven't been able to get the code developed by Imesh to work. AFAIK it does not address security aspects when using Docker containers. I've been going through Docker API documentation to come up with a good design. Thanks. On Thu, Jul 31, 2

Re: [gsoc] Unable to Access the Stratos UI interface

Hi Asiri, I think this is because of the EC2 security group that you have configured in your instance. Have you opened the ports required by Stratos and ActiveMQ (Message Broker)? Thanks. On Thu, Jul 31, 2014 at 11:11 PM, Asiri Liyana Arachchi wrote: > Output of curl -iv https://ip:9443/conso

Re: [gsoc] Unable to Access the Stratos UI interface

Hi Asiri, What exactly is the error that you get? Can you post the output of the following curl -iv https://ip:9443/console *IMPORTANT* - Please revoke your EC2 credentials and identity from AWS that you have shared publicly on the list (if the setup.conf credentials are valid). Also you need

Re: stratos docker provider

Hi Akila, I haven't started on this yet, so have yet to look through Imesh's code. Have you managed to get anything running yet with docker? Many thanks, Chris On Thu, Jul 31, 2014 at 6:11 PM, Akila Ravihansa Perera wrote: > Hi Chris, > > I've been working on it for some time. But still I'm g

[jira] [Resolved] (STRATOS-728) Wiki documentation for stratos in docker images

[ https://issues.apache.org/jira/browse/STRATOS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chris snow resolved STRATOS-728. Resolution: Fixed > Wiki documentation for stratos in docker images >

[jira] [Created] (STRATOS-730) Puppet in docker image

chris snow created STRATOS-730: -- Summary: Puppet in docker image Key: STRATOS-730 URL: https://issues.apache.org/jira/browse/STRATOS-730 Project: Stratos Issue Type: Sub-task Reporte

Re: stratos docker provider

Hi Chris, I've been working on it for some time. But still I'm going through the work Imesh has been doing and familiarizing myself with the Docker API. Currently I'm working on an implementation plan for Docker IaaS provider support. Will share the details soon. Please share your ideas on this.

stratos docker provider

Is anyone working on the Stratos docker provider that was started by Imesh [1]? I would like to work on this, but just wanted to see if anyone is already working on it ... --- [1] https://issues.apache.org/jira/browse/STRATOS-693

[gsoc] Unable to Access the Stratos UI interface

Hi all, I'm trying to start stratos on an ec2 instance. I'va attached the log file here with. Everything seems fine except this error ERROR {org.wso2.stratos.identity.saml2.sso.mgt.ui.Util} - The configuration element 'TenantRegistrationPage' not found in '/opt/stratos/apache-stratos-default

Re: CLI resource path auto-completion support

Nice work Sajith! On Thu, Jul 31, 2014 at 1:48 PM, Sajith Kariyawasam wrote: > Hi, > > I have just added $subject, which I thought will be useful. > Now the resource-path will be auto-completed once the tab key is pressed. > > * stratos> deploy-cartridge --resource-path ./cart* > * cart-mys

[jira] [Created] (STRATOS-729) registry.docker.com account for uploading stratos in docker images

chris snow created STRATOS-729: -- Summary: registry.docker.com account for uploading stratos in docker images Key: STRATOS-729 URL: https://issues.apache.org/jira/browse/STRATOS-729 Project: Stratos

[jira] [Created] (STRATOS-727) Security hardening for stratos in docker images (e.g. changing keystore)

chris snow created STRATOS-727: -- Summary: Security hardening for stratos in docker images (e.g. changing keystore) Key: STRATOS-727 URL: https://issues.apache.org/jira/browse/STRATOS-727 Project: Stratos

[jira] [Created] (STRATOS-728) Wiki documentation for stratos in docker images

chris snow created STRATOS-728: -- Summary: Wiki documentation for stratos in docker images Key: STRATOS-728 URL: https://issues.apache.org/jira/browse/STRATOS-728 Project: Stratos Issue Type: Sub

[jira] [Resolved] (STRATOS-726) EC2, OpenStack and vCloud support for stratos in docker images

[ https://issues.apache.org/jira/browse/STRATOS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chris snow resolved STRATOS-726. Resolution: Fixed > EC2, OpenStack and vCloud support for stratos in docker images > -

[jira] [Created] (STRATOS-726) EC2, OpenStack and vCloud support for stratos in docker images

chris snow created STRATOS-726: -- Summary: EC2, OpenStack and vCloud support for stratos in docker images Key: STRATOS-726 URL: https://issues.apache.org/jira/browse/STRATOS-726 Project: Stratos

[jira] [Updated] (STRATOS-725) Too many open files - HTTP Status 500 error

[ https://issues.apache.org/jira/browse/STRATOS-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-725: Summary: Too many open files - HTTP Status 500 error (was: Too many open files - HTTP Sta

[jira] [Updated] (STRATOS-725) Too many open files - HTTP Status 500 error from carbon.xml

[ https://issues.apache.org/jira/browse/STRATOS-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-725: Description: Stratos was running for more than 1 day and once I tried to unsubscribe from

[jira] [Updated] (STRATOS-725) Too many open files - HTTP Status 500 error from carbon.xml

[ https://issues.apache.org/jira/browse/STRATOS-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-725: Description: Stratos was running for more than 1 day and once I tried to unsubscribe from

[jira] [Updated] (STRATOS-725) Too many open files - HTTP Status 500 error from carbon.xml

[ https://issues.apache.org/jira/browse/STRATOS-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-725: Attachment: fd_stratos.dump > Too many open files - HTTP Status 500 error from carbon.xml

[jira] [Created] (STRATOS-725) Too many open files - HTTP Status 500 error from carbon.xml

Lasindu Charith created STRATOS-725: --- Summary: Too many open files - HTTP Status 500 error from carbon.xml Key: STRATOS-725 URL: https://issues.apache.org/jira/browse/STRATOS-725 Project: Stratos

Jenkins build is back to normal : Stratos-Master-Nightly-Build #212

See

Jenkins build is back to normal : Stratos-Master-Nightly-Build » Apache Stratos - Distribution #212

See

CLI resource path auto-completion support

Hi, I have just added $subject, which I thought will be useful. Now the resource-path will be auto-completed once the tab key is pressed. * stratos> deploy-cartridge --resource-path ./cart* * cart-mysql.json cart-php.json cart-jboss.json * Committed in 75d3efbf23d22dc8868f3d8