Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/413
---
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
Hi All,
We had the hangout and demo as we planned. We discussed about issues in
current code like exception handling commenting etc. And we discussed about
modifications I did, future plans, limitations in GCE like domain mapping,
statistic publishing etc.
I'm planing to do all the modifications
Hi Martin,
I will provide some details according to what i have understood. Please
correct me, if I'm wrong.
A group can consist of different kind of VMs which we called as cartridges
in stratos. In that case, co-located affinity can be provided to VMs which
are part of same group by providing a
+1. Frequent releases are almost always better. Will we be keeping track of
which tasks to target for a specific release through JIRA?
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Tue, Jul 28, 2015
Hi,
As part of our original grouping design we proposed a feature to either
co-locate or not co-locate individual VMs.
Quoting from the original grouping specification:
Quote begin:
Co-Location
VMs within a group will be spun up based on the model of subscriptions,
deployment policies and part
Hi Devs,
Currently I am working on $subject. In Kubernetes there are 3 kinds of
services types. They are NodePort, ClusterIP and LoadBalancer [1]. At the
moment Stratos supports only NodePort type. My intention is to extend this
to have ClusterIP type as well.
*Why We Need ClusterIP*
1. NodePort
Thanks Imesh..!!!
On Wed, Jul 29, 2015 at 8:46 PM, Imesh Gunaratne wrote:
> A great initiative Reka!! This would definitely reduce the testing effort.
> It's good to use a separate set of artifacts for this purpose rather than
> using the samples.
>
+1 for using different artifacts for this pur
GitHub user dinithis opened a pull request:
https://github.com/apache/stratos/pull/413
Remove UUID and tenantId from NetworkPartition Bean and DeploymentPolicy
Bean
Remove UUID and tenantId from NetworkPartition Bean and DeploymentPolicy
Bean
You can merge this pull request into a
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/412
---
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
A great initiative Reka!! This would definitely reduce the testing effort.
It's good to use a separate set of artifacts for this purpose rather than
using the samples. Great work!
On Wed, Jul 29, 2015 at 4:36 PM, Reka Thirunavukkarasu
wrote:
> Hi All,
>
> I'm in the process of writing integratio
GitHub user Thanu opened a pull request:
https://github.com/apache/stratos/pull/412
Adding Metering and Monitoring Service Implementation
This contains Metering and Monitoring service implementation.
You can merge this pull request into a Git repository by running:
$ git pull h
Anuruddha Lanka Liyanarachchi created STRATOS-1483:
--
Summary: Stratos notify the AddTenant listeners when restarted for
existing tenants.
Key: STRATOS-1483
URL: https://issues.apache.org/jira/brow
Hi Gayan,
I have added relevant artifacts to [1] which is inside integration test. I
have added the test scenarios and kind of step by step assertions in [2].
[1]
https://github.com/apache/stratos/tree/master/products/stratos/modules/integration/src/test/resources
[2]
https://github.com/apache/s
Hi Reka,
Great!
I assume that you are creating a separate json artifacts for this
integration testing rather than using the samples. Also what are the
assertions we have applied for artifacts to cover the integration test?
Thanks,
Gayan
On Wed, Jul 29, 2015 at 4:36 PM, Reka Thirunavukkarasu
wr
Thanks Thanuja!
I also need to catch specific exception and log appropriate message.
Thanks and Regards,
Swapnil
On Jul 29, 2015 4:11 PM, "Thanuja Uruththirakodeeswaran"
wrote:
> Hi All,
>
> Please find the code review notes below:
>
>1. Define used constant values as readable constant vari
Hi All,
I'm in the process of writing integration test to cover the CRUD operations
of all the individual and the connected artifacts. The below test cases for
add, get, update and remove will be covered in the integration test with
all possible test scenarios.
1. Autoscaling policy (*Done*)
2. N
Hi All,
Please find the code review notes below:
1. Define used constant values as readable constant variables.
2. Include loadbalancer name length constant (32) in the exception
message in AWSHelper class.
3. In AWSLoadBalancer avoid using "if(clusterMemberSize()==0) break;"
and f
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/411
---
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
GitHub user JaneAarthy reopened a pull request:
https://github.com/apache/stratos/pull/411
Application UI text fix
Changed UI text to "Deploy Application" and removed the application alias
Changed the spinner button text from "Adding Application Policy "to
"Deploying Application
GitHub user JaneAarthy opened a pull request:
https://github.com/apache/stratos/pull/411
Application UI text fix
Changed UI text to "Deploy Application" and removed the application alias
Changed the spinner button text from "Adding Application Policy "to
"Deploying Application"
Github user JaneAarthy closed the pull request at:
https://github.com/apache/stratos/pull/411
---
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
Hi All,
I have started hangout. You can join in for code review.
URL: https://plus.google.com/hangouts/_/g7jnhpysd3dxyyrqycerhd6iyua
Thanks and Regards,
Swapnil
On Mon, Jul 27, 2015 at 1:14 PM, Swapnil Patil
wrote:
> Hi Imesh,
>
> Ok. No problem. We can have this on Wednesday 29th July at 2 P
22 matches
Mail list logo