Hi all,
Update on the current progress.
- Tested all the applications in mock IaaS with two separate tenants.
- Removed UUID and tenantId from the Bean classes so that the UUID and
the tenantId is not visible to the end user via UI.
- Modified integration tests to assert each and ever
Hi,
Update on the current progress.
- Now we can deploy the same application in two separate tenants without
any issues.
- We have written an integration test to check this tenant isolation
functionality, using the single-group-app and it was passed successfully.
We will now modify
Great!! Thanks for the update Gayan & Dinithi!!
On Fri, Jul 17, 2015 at 8:42 PM, Dinithi De Silva wrote:
> Hi,
>
> We have successfully tested with a complex application (with four
> cartridges and one cartridge group) by deploying and undeploying it in two
> separate tenants.
> Now I am writing
Hi,
We have successfully tested with a complex application (with four
cartridges and one cartridge group) by deploying and undeploying it in two
separate tenants.
Now I am writing an integration test to verify this functionality.
Thanks
On Thu, Jul 16, 2015 at 12:04 PM, Dinithi De Silva
wrote:
Hi Imesh,
Up to now we were able to deploy the single-cartridge-app, single-group-app
successfully. And also we have tested with a complex application with four
cartridges and one cartridge group.
Now we are in the process of testing the other complex applications with
this implementation and fixi
Hi Imesh,
We generate the cluster ID as "applicationUuid + "." + alias + "." +
cartridgeType + ".domain" and member id is already we generated as the
UUID. Because of that we don't need to change the cartridge agent logic as
we can distinguished the instances based on the unique member id and
clus
Great work Gayan & Dinithi!! I guess this also includes changes to the
messaging component for adding UUIDs for events.
Shall we try to implement a quick integration test to verify this
functionality (may be on high level, not everything)?
Thanks
On Tue, Jul 14, 2015 at 9:43 PM, Gayan Gunarathne
Hi All,
Now we have modified the followings artifacts with the UUID in the tenant
isolation implementation.
Network Partitions
Deployment Policies
Autoscaling Policies
Application Policies
Cartridges
Cartridge Groups
Kubernetes Clusters
Applicatiion
Now integration tests are passed for applicati
On Mon, Jul 6, 2015 at 4:04 PM, Imesh Gunaratne wrote:
> Gayan: Shall we call it "tenant-isolation"?
>
+1
> On Mon, Jul 6, 2015 at 2:22 PM, Dinithi De Silva
> wrote:
>
>> Thanks Gayan. Now I am working on this new branch.
>>
>> On Mon, Jul 6, 2015 at 2:15 PM, Gayan Gunarathne wrote:
>>
>>> Cr
Gayan: Shall we call it "tenant-isolation"?
On Mon, Jul 6, 2015 at 2:22 PM, Dinithi De Silva wrote:
> Thanks Gayan. Now I am working on this new branch.
>
> On Mon, Jul 6, 2015 at 2:15 PM, Gayan Gunarathne wrote:
>
>> Created new branch "tenantisolation" for this.
>>
>> Thanks,
>> Gayan
>>
>> O
Thanks Gayan. Now I am working on this new branch.
On Mon, Jul 6, 2015 at 2:15 PM, Gayan Gunarathne wrote:
> Created new branch "tenantisolation" for this.
>
> Thanks,
> Gayan
>
> On Mon, Jul 6, 2015 at 1:41 PM, Imesh Gunaratne wrote:
>
>> Yes Gayan, we could create a new branch for this.
>>
>>
Created new branch "tenantisolation" for this.
Thanks,
Gayan
On Mon, Jul 6, 2015 at 1:41 PM, Imesh Gunaratne wrote:
> Yes Gayan, we could create a new branch for this.
>
> On Mon, Jul 6, 2015 at 11:23 AM, Gayan Gunarathne wrote:
>
>> +1.
>>
>> Since we are planing to implement this for 4.1.1 m
Yes Gayan, we could create a new branch for this.
On Mon, Jul 6, 2015 at 11:23 AM, Gayan Gunarathne wrote:
> +1.
>
> Since we are planing to implement this for 4.1.1 minor release, shall we
> do this implementation in a new branch?
>
> Thanks,
> Gayan
>
>
> On Tue, Jun 23, 2015 at 2:05 PM, Imesh
+1.
Since we are planing to implement this for 4.1.1 minor release, shall we do
this implementation in a new branch?
Thanks,
Gayan
On Tue, Jun 23, 2015 at 2:05 PM, Imesh Gunaratne wrote:
> +1 Thanks for contributing to this Dinithi!
>
> Few months back Lasindu did a major feature implementati
+1 Thanks for contributing to this Dinithi!
Few months back Lasindu did a major feature implementation for this and due
to merge conflicts found with Composite Application Model and Kubernetes
feature implementation we had to drop the entire branch.
In this effort may be we could do an initial im
Hi,
In the current Stratos implementation, the artifacts which are created by a
particular tenant is visible to all other tenants. I am going to implement
the tenant isolation mechanism, so that the artifacts will be only visible
to the tenant which has created the artifacts.
In order to implemen
16 matches
Mail list logo
