[DISCUSS] Basic page layout for the Stratos UIs

Hi all, Attached is the base page layout proposed for the reconstructed UIs. The main areas of this are; 1. The context pane - This should provide logged in users context details plus any general links that are applicable 2. The navigation pane - A vertical tab layout is used to show the main are

Re: [DISCUSS] Patching exiting cartridge instances with updates

What I meant was "rebooting" the same instance [1] [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-reboot.html On Thu, Jul 24, 2014 at 11:21 AM, Sajith Kariyawasam wrote: > > On Mon, Jun 30, 2014 at 5:11 PM, Dinesh Bandara wrote: > >> Hi all, >> >> I have faced in to a sit

Re: [DISCUSS] Patching exiting cartridge instances with updates

On Thu, Jul 24, 2014 at 11:11 AM, Nirmal Fernando wrote: > > > > On Thu, Jul 24, 2014 at 11:03 AM, Dinesh Bandara wrote: > >> >> >> >> On Thu, Jul 24, 2014 at 10:47 AM, Nirmal Fernando > > wrote: >> >>> >>> >>> >>> On Mon, Jun 30, 2014 at 5:11 PM, Dinesh Bandara >>> wrote: >>> Hi all,

Re: [DISCUSS] Patching exiting cartridge instances with updates

How do you guys plan to keep track of patched servers in cluster? On Thu, Jul 24, 2014 at 11:20 AM, Akila Ravihansa Perera wrote: > Hi, > > I think we have to think about how we are going to push Puppet changes > to existing cartridge instances. Currently, cartridge instances will > disable the

Re: [DISCUSS] Patching exiting cartridge instances with updates

On Mon, Jun 30, 2014 at 5:11 PM, Dinesh Bandara wrote: > Hi all, > > I have faced in to a situation that need to update existing cartridge > instances without interrupt the process. AFAIU there are two types of > updates that need to be applied. > >1. OS level/ Security updates >2. Appli

Re: [DISCUSS] Patching exiting cartridge instances with updates

Hi, I think we have to think about how we are going to push Puppet changes to existing cartridge instances. Currently, cartridge instances will disable the Puppet agent after init.sh is executed [1]. This prevent any further Puppet configurations from being applied. We will need to introduce a ne

Re: [DISCUSS] Patching exiting cartridge instances with updates

Hi Dinesh, This is what I have understood, please correct me if I am wrong. A new API is provided where we can specify a particular cluster need to be patched. So the process would be like below? Update the puppet master with relevant changes. Call the API to patch a cluster x AS will select

Re: [DISCUSS] Patching exiting cartridge instances with updates

On Thu, Jul 24, 2014 at 11:03 AM, Dinesh Bandara wrote: > > > > On Thu, Jul 24, 2014 at 10:47 AM, Nirmal Fernando > wrote: > >> >> >> >> On Mon, Jun 30, 2014 at 5:11 PM, Dinesh Bandara wrote: >> >>> Hi all, >>> >>> I have faced in to a situation that need to update existing cartridge >>> instan

Re: [DISCUSS] Patching exiting cartridge instances with updates

On Thu, Jul 24, 2014 at 10:47 AM, Nirmal Fernando wrote: > > > > On Mon, Jun 30, 2014 at 5:11 PM, Dinesh Bandara wrote: > >> Hi all, >> >> I have faced in to a situation that need to update existing cartridge >> instances without interrupt the process. AFAIU there are two types of >> updates th

Re: Building User Stories for Apache Stratos 4.0.1

Hi everyone, The user stories for users of type "Stratos Administrator" have been updated in the shared document. The updates relate to the epics that are available in Stratos today. The other areas have been grayed out for the time being so that we can first focus on getting the existing functio

Re: [DISCUSS] Patching exiting cartridge instances with updates

On Mon, Jun 30, 2014 at 5:11 PM, Dinesh Bandara wrote: > Hi all, > > I have faced in to a situation that need to update existing cartridge > instances without interrupt the process. AFAIU there are two types of > updates that need to be applied. > >1. OS level/ Security updates >2. Appli

Composite App - group model

Hi Isuru, Reka In the json format of the service group we define a group name, which gives each group a unique identifier when it is deployed. Since the grouping we are currently adding . / implementing allows to auto scale entire groups (and nested groups) we have to make sure that we are uniq

RE: Composite App - Where to store service groups

Hi Udara, +1 if this fits better the paradigm to store relevant information. One quick question, how will this change the sequence flow in cases like group deployment, octl restart (restoring the grouping model), etc …. ? As you mentioned, CC (and any “module”) involved needs to be able to acce

Build failed in Jenkins: Stratos-Master-Nightly-Build #205

See -- [...truncated 30403 lines...] Received 0 blocks and 3324 bytes Compression is 0.0% Took 16 ms [JENKINS] Archiving

Build failed in Jenkins: Stratos-Master-Nightly-Build » Apache Stratos - Common Core Feature #205

See -- [INFO] [INFO] -

Re: Stratos stopped working with java.net.SocketException

Touched, not typed. Erroneous words are a feature, not a typo. On Jul 24, 2014 8:55 AM, "Jeffrey Nguyen (jeffrngu)" wrote: > > Hi Devs, > > We have a setup where Stratos stopped functioning after running for about 24 hours. wso2carbon.log shows a lot of exceptions like one listed below. We were

Re: Composite App - Where to store service groups

Hi Udara, On Wed, Jul 23, 2014 at 11:49 AM, Udara Liyanage wrote: > Hi, > > With the current implementation, service groups are stored in SM. When a > CompositeApp is deployed, group details and composite app details should be > sent to CC and then CC fire ApplicationCreatedEvent event with thos

Re: JBoss cartridge for Apache Stratos

Nice one Akila! On Wed, Jul 23, 2014 at 2:00 AM, Akila Ravihansa Perera wrote: > Hi, > > I've developed a Puppet module for JBoss Application Server cartridge > and created a PR in [1]. I've written a blog post explaining all the > steps for deploying a JBoss cartridge in [2]. > > Also I've impro

Re: JBoss cartridge for Apache Stratos

Nice work Akila! On Wed, Jul 23, 2014 at 7:33 PM, Manula Chathurika Thantriwatte < manu...@wso2.com> wrote: > Great stuff Akila !!! > > > On Wed, Jul 23, 2014 at 8:02 AM, Lakmal Warusawithana > wrote: > >> Great work Akila! >> >> >> On Wed, Jul 23, 2014 at 6:30 AM, Akila Ravihansa Perera < >> r

Re: JBoss cartridge for Apache Stratos

Great stuff Akila !!! On Wed, Jul 23, 2014 at 8:02 AM, Lakmal Warusawithana wrote: > Great work Akila! > > > On Wed, Jul 23, 2014 at 6:30 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi, >> >> I've developed a Puppet module for JBoss Application Server cartridge >> and created

[jira] [Commented] (STRATOS-706) member terminate event should log reason

[ https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071575#comment-14071575 ] Nirmal Fernando commented on STRATOS-706: - Hi Shaheed, All logs should be there

[jira] [Commented] (STRATOS-706) member terminate event should log reason

[ https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071553#comment-14071553 ] Shaheed Haque commented on STRATOS-706: --- Any update on this, or am I missing someh

Re: [jira] [Commented] (STRATOS-706) member terminate event should log reason

Any update on this, or am I missing somehting obvious? On Thursday 17 Jul 2014 09:40:55 Shaheedur Haque wrote: > > I am confused. I thought that with the single JVM packaging, all Stratos logs > went to /opt/wso2/apace-stratos/repository/logs/wso2carbon.log (and its > neighbours): > > root@oc