Build failed in Jenkins: Stratos-41x-Commit-Build » Apache Stratos - Kubernetes API Java Client #44

See Changes: [ravihansa3000] Set labels for identification when creating K8s pods and services [ravihansa3000] Adding annotations in K8s when creating services and pods

Build failed in Jenkins: Stratos-41x-Commit-Build #44

See Changes: [ravihansa3000] Fixed issue with logging in pca [ravihansa3000] Use a global counter for generating sequence ids for Kub services and pods [ravihansa3000] Set labels for identification when creating K8s pods and

Re: Stratos-41x build trend

Yeah.It is not a issue with the Stratos source. That's happen some intermittent issues occurs in the build server. Thanks, Gayan On Sun, Sep 20, 2015 at 10:34 AM, Akila Ravihansa Perera wrote: > Hi Gayan, > > If you go through the full log you will notice that JVM has crashed at > 2015-09-19 >

Re: Openstack Availability zone settings in partition definition not working

On 9/20/15, 2:09 AM, Akila Ravihansa Perera wrote: Hi Vanson, Thanks for reporting this. This has been a known issue causing problems when updating IaaS parameters. A work-around would be to redeploy the cartridge definition which forces it to re-build. I haven't tested it though. Your solution

Re: Openstack Availability zone settings in partition definition not working

Hi Vanson, Thanks for reporting this. This has been a known issue causing problems when updating IaaS parameters. A work-around would be to redeploy the cartridge definition which forces it to re-build. I haven't tested it though. Your solution also works, but were you able to look into to the per

Openstack Availability zone settings in partition definition not working

Stratos developers, I found an issue where defining an availability "zone" property in a partition has no affect on controlling the placement of a VM launched under openstack. The code which builds the template (iaas.initialize) used by jclouds is executed only once before stratos appends the

Re: Stratos-41x build trend

Hi Gayan, If you go through the full log you will notice that JVM has crashed at 2015-09-19 00:41:42. 2015-09-19 00:41:42 INFO {org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader}:70 - # A fatal error has been detected by the Java Runtime Environment: Likely cause is system went

Stratos-41x build trend

Hi All, Following the release branch build trend for lat week. [image: collapse] [image: Success > Console Output] #14S

Re: Multi-region Kubernetes service un-deployment

@Udara Great. Once you finish the tests, let us know the results. @Akila I know you are facing some merge conflict issues when you try to push your changes. Please let us know once you are done.I think we can start the 4.1.3 release work after that. Thanks, Gayan On Sun, Sep 20, 2015 at 6:14 AM,

Jenkins build is back to stable : Stratos-41x-Nightly-Build » Apache Stratos - Integration Tests #14

See

Jenkins build is back to stable : Stratos-41x-Nightly-Build #14

See

Re: Multi-region Kubernetes service un-deployment

Hi Gayan, I performed a quick smoke test with two clusters and it was successful. I will do some more tests and let you know the results. On Sat, Sep 19, 2015 at 10:47 AM, Gayan Gunarathne wrote: > Additionally we have removed the kubernetesClusterId from the > ClusterContext and added the kube

Re: Multi-region Kubernetes service un-deployment

Additionally we have removed the kubernetesClusterId from the ClusterContext and added the kubernetesClusterId to the kuberentesServices.Idea behind that is we can't have kubernetesClusterId in ClusterContext as there can be one or more Kubernetes clusters in the case of multi-region deployment.But

[GitHub] stratos pull request: Fixed issue with logging in pca

GitHub user pubudu538 opened a pull request: https://github.com/apache/stratos/pull/467 Fixed issue with logging in pca An error message can be found in agent log due to this. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pubudu

Re: Improvements to Python cartridge agent artifact distribution

On Fri, Sep 18, 2015 at 12:31 AM, Akila Ravihansa Perera wrote: > > > Few improvements were made to resolve these issues. > - Now PCA will run the commit job first. If the Git clone has not been > done it will skip in that iteration. > Does this mean it will add all the files available in the gi

Re: Multi-region Kubernetes service un-deployment

I had an offline discussion on this with Gayan. It looks like the root cause of this problem is that we have added Kubernetes Cluster ID to the Cluster Context. This seems to be incorrect. A cluster can have multiple Kubernetes Clusters if its a multi-region deployment. We need to remove the prope

Re: Application ID length validation

May be we could add a label containing application id to the pods and services. On Friday, September 18, 2015, Dinithi De Silva wrote: > As per the offline discussion, we will revert back to the previous way of > handling the pod ids and service ids. So we will use service IDs as > service1, ser

Re: Multi-region Kubernetes service un-deployment

We might need to use cluster id and network partition id as the key of this map. Once we are done with this fix shall we do 4.1.3 release build? Thanks On Friday, September 18, 2015, Gayan Gunarathne wrote: > When we try to un-deploy the application in a multi region deployment, It > will thro