[GitHub] stratos pull request: Adding das extension files

Github user Thanu closed the pull request at: https://github.com/apache/stratos/pull/466 --- 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 enab

[GitHub] stratos pull request: Adding das extension files

Github user Thanu commented on the pull request: https://github.com/apache/stratos/pull/466#issuecomment-141358271 Closing this p/r to refactor the code. --- 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 doe

[jira] [Commented] (STRATOS-1568) PCA deletes the repository path when cloning the GIt repo

[ https://issues.apache.org/jira/browse/STRATOS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804293#comment-14804293 ] Akila commented on STRATOS-1568: Fixed in 3043dc3ac07546d33001918212a88d12df7f6be2 >

[jira] [Resolved] (STRATOS-1568) PCA deletes the repository path when cloning the GIt repo

[ https://issues.apache.org/jira/browse/STRATOS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1568. Resolution: Fixed > PCA deletes the repository path when cloning the GIt repo > --

Improvements to Python cartridge agent artifact distribution

Hi, There were few issues in PCA related to artifact distribution; - If an artifact is deleted PCA fails to push the delete commit to remote repo because checkout job gets executed first causing deleted file to bepulled again - When cloning the Git repo, PCA will delete the whole directory in re

[jira] [Created] (STRATOS-1568) PCA deletes the repository path when cloning the GIt repo

Akila created STRATOS-1568: -- Summary: PCA deletes the repository path when cloning the GIt repo Key: STRATOS-1568 URL: https://issues.apache.org/jira/browse/STRATOS-1568 Project: Stratos Issue Type:

Re: Application ID length validation

Idea for using the application ID as a service name to clearly distinguish the Kubernetes service against the application ID.If we are using other unique identifier, we won't be identify service belongs to the application. OTOH we use application ID to identify the application and IMO we can have

Re: Application ID length validation

+1 decoupling application id and kub8 service name. What if we repeatedly query the existing service names and increment the seq no until an available service name is found? This is what we do when generating pod names. On Thu, Sep 17, 2015 at 8:40 PM, Pubudu Gunatilaka wrote: > Hi Gayan, > > Ca

Re: Application ID length validation

Hi Gayan, Can't we limit the Kubernetes service name rather than limiting the application id. If we are deploying multiple applications, it would be better if we can have meaningful name for the application ids. If we are going to limit the kubernetes service name, we may have to come up with anot

Application ID length validation

Added the logic to validate the application ID length.This is because we are using the application ID as a Kubernetes service name which supports up-to 24 characters. But I could enable the application ID validation length to 20 as integration test are failed due to integration test samples applic

[jira] [Created] (STRATOS-1567) Validate the application id length

Gayan Gunarathne created STRATOS-1567: - Summary: Validate the application id length Key: STRATOS-1567 URL: https://issues.apache.org/jira/browse/STRATOS-1567 Project: Stratos Issue Type:

[GitHub] stratos pull request: Adding das extension files

GitHub user Thanu opened a pull request: https://github.com/apache/stratos/pull/466 Adding das extension files This P/R includes following changes: 1. Deleting existing das extensions files. 2. Adding Stratos Metering Service dashboard composite application and spark udf ins