Do we need a review?
--Srinath
On Tue, Nov 6, 2012 at 1:22 PM, Amila Suriarachchi am...@wso2.com wrote:
On Tue, Nov 6, 2012 at 12:43 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, Nov 5, 2012 at 6:48 PM, Amila Suriarachchi am...@wso2.comwrote:
Hi Srinath,
On Mon, Jul 9, 2012 at 3:21
Hi Srinath,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not deploying artifacts inside
the CApp back to repo, but deploying them by extracting them into a temp
directory and invoking the respective deployers
hi Srinath,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not deploying artifacts inside
the CApp back to repo, but deploying them by extracting them into a temp
directory and invoking the respective deployers
The relevant JIRA - https://wso2.org/jira/browse/CARBON-13078
On Mon, Nov 5, 2012 at 6:51 PM, Amila Suriarachchi am...@wso2.com wrote:
hi Srinath,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not deploying
On Mon, Nov 5, 2012 at 6:48 PM, Amila Suriarachchi am...@wso2.com wrote:
Hi Srinath,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not deploying artifacts inside
the CApp back to repo, but deploying them by
On Tue, Nov 6, 2012 at 12:43 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, Nov 5, 2012 at 6:48 PM, Amila Suriarachchi am...@wso2.com wrote:
Hi Srinath,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not
On Tue, Nov 6, 2012 at 12:43 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, Nov 5, 2012 at 6:48 PM, Amila Suriarachchi am...@wso2.com wrote:
Hi Srinath,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not
Hi Isuru,
I believe this new C-App deploymement location can be derived using tenant?
Otherwise the Dev Studio C-App deployment feature will be broken.
Thanks and Regards,
Harshana
On Jul 28, 2012 8:14 PM, Isuru Suriarachchi is...@wso2.com wrote:
On Sat, Jul 28, 2012 at 4:06 AM, Samisa
On Sat, Jul 28, 2012 at 8:33 PM, Harshana Martin harsh...@wso2.com wrote:
Hi Isuru,
I believe this new C-App deploymement location can be derived using tenant?
Yes.. It's CARBON_HOME/tmp/tenants/tenant_id/carbonapps/
Thanks,
~Isuru
Otherwise the Dev Studio C-App deployment feature will be
On Sat, Jul 28, 2012 at 6:43 PM, Isuru Suriarachchi is...@wso2.com wrote:
On Sat, Jul 28, 2012 at 4:06 AM, Samisa Abeysinghe sam...@wso2.comwrote:
Charitha - good catch!
Isuru, thanks for the quick fix!!
AS folks, can we please do a preliminary verification of the fix done by
Isuru,
On Thu, Jul 26, 2012 at 12:17 AM, Isuru Suriarachchi is...@wso2.com wrote:
Oh.. I was planning to create different directories for different tenants
inside repository/carbonapps. But looks like I've missed that. I'll fix it
and let you know..
Tenants have their own temp directory right? If
On Thu, Jul 26, 2012 at 2:55 PM, Afkham Azeez az...@wso2.com wrote:
On Thu, Jul 26, 2012 at 12:17 AM, Isuru Suriarachchi is...@wso2.comwrote:
Oh.. I was planning to create different directories for different tenants
inside repository/carbonapps. But looks like I've missed that. I'll fix it
Hi,
It seems we have not thought about MT aspects of this model. Now, the
carbonapps directory is taken out from repository/deployment/server and the
all CApps will be stored in common carbonapps directory regardless of the
tenant who deployed CApp. Because of this, any tenant can see others
Oh.. I was planning to create different directories for different tenants
inside repository/carbonapps. But looks like I've missed that. I'll fix it
and let you know..
Thanks,
~Isuru
On Wed, Jul 25, 2012 at 10:31 PM, Charitha Kankanamge chari...@wso2.comwrote:
Hi,
It seems we have not
On Mon, Jul 9, 2012 at 10:55 AM, Muhammed Shariq sha...@wso2.com wrote:
On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.com wrote:
Hi all,
I'm trying to fix [1]. Here's the root cause for this issue..
Imagine a Carbon cluster with 2 nodes where the svn based deployment
On Sat, Jul 7, 2012 at 11:01 AM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi Isuru,
I'd like to add a third option to the list for consideration. :)
How about doing the synchronization between cluster nodes AFTER the
C-App's extracted artifacts are deployed?
This is kind of not possible
Hi Isuru,
On Sat, Jul 7, 2012 at 9:48 AM, Isuru Suriarachchi is...@wso2.com wrote:
Harshana, good point.. Actually I had forgot about the lib artifacts.
Anyway as Azeez mentioned, we only allow lib artifacts for super tenant. So
it's kind of broken already.
If we want the libs to work with
On Mon, Jul 9, 2012 at 12:20 PM, Isuru Suriarachchi is...@wso2.com wrote:
On Mon, Jul 9, 2012 at 10:55 AM, Muhammed Shariq sha...@wso2.com wrote:
On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.comwrote:
Hi all,
I'm trying to fix [1]. Here's the root cause for this issue..
Hi Isuru,
In a review we talked about possibility of not deploying artifacts inside
the CApp back to repo, but deploying them by extracting them into a temp
directory and invoking the respective deployers directly, without using the
hot deployment. IMHO, that is the clean way to handle CApp
Hi Isuru,
For the release, can we ask users to run the cluster in a mode where only
one node write to the SVN repo and other nodes will just read?
Also, please explain your fixes to someone/ commit them to the new trunk
once we are done with the release. I think those fixes are the right long
On Mon, Jul 9, 2012 at 5:07 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
For the release, can we ask users to run the cluster in a mode where only
one node write to the SVN repo and other nodes will just read?
I think we always recommend only one R/W node in a cluster.
Also,
On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:
Hi Isuru,
In a review we talked about possibility of not deploying artifacts inside
the CApp back to repo, but deploying them by extracting them into a temp
directory and invoking the respective deployers directly,
On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.com wrote:
Hi all,
I'm trying to fix [1]. Here's the root cause for this issue..
Imagine a Carbon cluster with 2 nodes where the svn based deployment
synchronizer (DS) is configured. When a C-App is deployed to node1, it is
Hi all,
I'm trying to fix [1]. Here's the root cause for this issue..
Imagine a Carbon cluster with 2 nodes where the svn based deployment
synchronizer (DS) is configured. When a C-App is deployed to node1, it is
extracted and individual artifacts are copied into respective hot
directories. When
Hi Isuru,
Please find my comments inline.
On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.com wrote:
Hi all,
I'm trying to fix [1]. Here's the root cause for this issue..
Imagine a Carbon cluster with 2 nodes where the svn based deployment
synchronizer (DS) is configured.
On Sat, Jul 7, 2012 at 2:39 AM, Harshana Martin harsh...@wso2.com wrote:
Hi Isuru,
Please find my comments inline.
On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.com wrote:
Hi all,
I'm trying to fix [1]. Here's the root cause for this issue..
Imagine a Carbon cluster
Harshana, good point.. Actually I had forgot about the lib artifacts.
Anyway as Azeez mentioned, we only allow lib artifacts for super tenant. So
it's kind of broken already.
If we want the libs to work with option 2, we can simply add a new deployer
for libs as well.. :)
Thanks,
~Isuru
On Sat,
Hi Isuru,
I'd like to add a third option to the list for consideration. :)
How about doing the synchronization between cluster nodes AFTER the C-App's
extracted artifacts are deployed? I'm not sure whether it's possible to do
with the current architecture, but if it is, then I think things will
28 matches
Mail list logo
