Re: Stratos 4.1.0 User Management and Permission Model

Great progress Lasindu, Sorry for the late reply. Subscriber of the cartridges select deployment policies which have min and max. As per our manual scaling capability that we will introduce, they should be given the chance to change the min and max after deployment, at run time. Shall we let him

Re: Stratos 4.1.0 User Management and Permission Model

Great work Lasindu!! Will test and give you some feedback. On Mon, Sep 15, 2014 at 10:44 AM, Lasindu Charith wrote: > Hi all, > > The changes are committed in docker_integration branch > https://github.com/apache/stratos/commit/29bf5f164ea6b77a34b876406cc2d3da95231109 > > *Created JIRAs * > http

[jira] [Resolved] (STRATOS-782) Kubernetes based cartridge deployment

[ https://issues.apache.org/jira/browse/STRATOS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam resolved STRATOS-782. Resolution: Fixed > Kubernetes based cartridge deployment > ---

[jira] [Commented] (STRATOS-782) Kubernetes based cartridge deployment

[ https://issues.apache.org/jira/browse/STRATOS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133600#comment-14133600 ] Sajith Kariyawasam commented on STRATOS-782: Fixed in docker-integration bran

[jira] [Updated] (STRATOS-782) Kubernetes based cartridge deployment

[ https://issues.apache.org/jira/browse/STRATOS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-782: --- Description: Need to have a property to identify whether its a Kubernetes based cartr

[jira] [Updated] (STRATOS-782) Kubernetes based cartridge deployment

[ https://issues.apache.org/jira/browse/STRATOS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-782: --- Description: { "type": "php", "provider": "apache", "host": "apac

Re: Stratos 4.1.0 User Management and Permission Model

Hi all, The changes are committed in docker_integration branch https://github.com/apache/stratos/commit/29bf5f164ea6b77a34b876406cc2d3da95231109 *Created JIRAs * https://issues.apache.org/jira/browse/STRATOS-799 https://issues.apache.org/jira/browse/STRATOS-800 https://issues.apache.org/jira/brow

[jira] [Updated] (STRATOS-772) Modify mock REST endpoint for 4.1.0 changes

[ https://issues.apache.org/jira/browse/STRATOS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiroshica Kulatilake updated STRATOS-772: -- Mock methods for user management are pending - will add as soon as the user manage

[GitHub] stratos pull request: Mock REST endpoint changes for tenant isolat...

Github user shirolk closed the pull request at: https://github.com/apache/stratos/pull/32 --- 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] stratos pull request: Mock REST endpoint changes for tenant isolat...

Github user shirolk commented on the pull request: https://github.com/apache/stratos/pull/32#issuecomment-1606 Thank you Nirmal !! --- 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 fea

[jira] [Updated] (STRATOS-799) Stratos User Management and Permissions model

[ https://issues.apache.org/jira/browse/STRATOS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-799: Description: Associate Carbon User Management Feature and Create a default user role with r

[jira] [Commented] (STRATOS-772) Modify mock REST endpoint for 4.1.0 changes

[ https://issues.apache.org/jira/browse/STRATOS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133566#comment-14133566 ] ASF GitHub Bot commented on STRATOS-772: Github user shirolk closed the pull requ

[jira] [Resolved] (STRATOS-801) Introduce new API methods to create/update/delete users

[ https://issues.apache.org/jira/browse/STRATOS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith resolved STRATOS-801. - Resolution: Implemented Commited in docker_integration branch https://github.com/apache/

[jira] [Updated] (STRATOS-801) Introduce new API methods to create/update/delete users

[ https://issues.apache.org/jira/browse/STRATOS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-801: Component/s: Stratos Manager CLI Affects Version/s: 4.1.0 M

[jira] [Created] (STRATOS-801) Introduce new API methods to create/update/delete users

Lasindu Charith created STRATOS-801: --- Summary: Introduce new API methods to create/update/delete users Key: STRATOS-801 URL: https://issues.apache.org/jira/browse/STRATOS-801 Project: Stratos

[jira] [Resolved] (STRATOS-800) Update REST endpoint with new authorization actions

[ https://issues.apache.org/jira/browse/STRATOS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith resolved STRATOS-800. - Resolution: Fixed Committed in https://github.com/apache/stratos/commit/29bf5f164ea6b77a

[GitHub] stratos pull request: Mock REST endpoint changes for tenant isolat...

Github user nirmal070125 commented on the pull request: https://github.com/apache/stratos/pull/32#issuecomment-1226 PR is merged. Thanks Shiro! --- 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

[jira] [Created] (STRATOS-800) Update REST endpoint with new authorization actions

Lasindu Charith created STRATOS-800: --- Summary: Update REST endpoint with new authorization actions Key: STRATOS-800 URL: https://issues.apache.org/jira/browse/STRATOS-800 Project: Stratos I

[jira] [Resolved] (STRATOS-799) Stratos User Management and Permissions model

[ https://issues.apache.org/jira/browse/STRATOS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith resolved STRATOS-799. - Resolution: Done Commited in docker_integration branch https://github.com/apache/stratos

[jira] [Created] (STRATOS-799) Stratos User Management and Permissions model

Lasindu Charith created STRATOS-799: --- Summary: Stratos User Management and Permissions model Key: STRATOS-799 URL: https://issues.apache.org/jira/browse/STRATOS-799 Project: Stratos Issue T

Re: [GitHub] stratos pull request: Mock REST endpoint changes for tenant isolat...

Thanks Shiro! I'll merge it. On Mon, Sep 15, 2014 at 7:10 AM, shirolk wrote: > Github user shirolk commented on the pull request: > > https://github.com/apache/stratos/pull/32#issuecomment-55546596 > > Hi Nirmal, > > No - though the beans change the validation has been added so far o

Re: Shall we plan for a 4.1.0-M1 developer preview?

Please take a moment to update the status of the tasks listed for 4.1.0 M1; http://goo.gl/vpdZIa Thanks. On Mon, Sep 15, 2014 at 8:58 AM, Nirmal Fernando wrote: > Currently hitting an issue in the docker-integration branch : > https://issues.apache.org/jira/browse/STRATOS-798 > > On Sun, Sep 14

[GitHub] stratos pull request: Fixing STRATOS-798

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

[jira] [Commented] (STRATOS-798) Error while login to Stratos in docker-integration branch

[ https://issues.apache.org/jira/browse/STRATOS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133531#comment-14133531 ] ASF GitHub Bot commented on STRATOS-798: Github user asfgit closed the pull reque

[GitHub] stratos pull request: Fixing STRATOS-798

GitHub user R-Rajkumar opened a pull request: https://github.com/apache/stratos/pull/36 Fixing STRATOS-798 You can merge this pull request into a Git repository by running: $ git pull https://github.com/R-Rajkumar/stratos docker-integration Alternatively you can review and ap

[jira] [Commented] (STRATOS-798) Error while login to Stratos in docker-integration branch

[ https://issues.apache.org/jira/browse/STRATOS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133528#comment-14133528 ] ASF GitHub Bot commented on STRATOS-798: GitHub user R-Rajkumar opened a pull req

Re: Shall we plan for a 4.1.0-M1 developer preview?

Currently hitting an issue in the docker-integration branch : https://issues.apache.org/jira/browse/STRATOS-798 On Sun, Sep 14, 2014 at 11:12 PM, Nirmal Fernando wrote: > Please avoid committing changes that are not available for M1. I am gonna > start an end-to-end testing. > > On Fri, Sep 12,

[jira] [Created] (STRATOS-798) Error while login to Stratos in docker-integration branch

Nirmal Fernando created STRATOS-798: --- Summary: Error while login to Stratos in docker-integration branch Key: STRATOS-798 URL: https://issues.apache.org/jira/browse/STRATOS-798 Project: Stratos

Build failed in Jenkins: Stratos-Master-Nightly-Build #258

See -- Started by timer Building remotely on H10 (Ubuntu ubuntu) in workspace > git rev-parse --is-inside-work-tree Fetching

Jenkins build is back to normal : Stratos-4.0.0-Nightly-Build #119

See

[GitHub] stratos pull request: Mock REST endpoint changes for tenant isolat...

Github user shirolk commented on the pull request: https://github.com/apache/stratos/pull/32#issuecomment-55546596 Hi Nirmal, No - though the beans change the validation has been added so far only to the schema.xsd in the mock module. Thank you, Shiro --- If you

Build failed in Jenkins: Stratos-Master-Nightly-Build #257

See -- Started by timer Building remotely on H10 (Ubuntu ubuntu) in workspace > git rev-parse --is-inside-work-tree Fetching

Build failed in Jenkins: Stratos-4.0.0-Nightly-Build #118

See -- Started by timer Building remotely on H10 (Ubuntu ubuntu) in workspace > git rev-parse --is-inside-work-tree Fetching ch

Code Reviews on 4.1.0/4.2.0 implementation

Hi Devs, Shall we start doing $subject. Main motivation is deliver good quality code and encourage new commiters to work on standard. Shall I suggest following time slots. Also at least 3 commiters/PMC members should be in a review session IMO. Reviews are doing via hangouts. 16/09/2014 - 7.30 p

Re: Shall we plan for a 4.1.0-M1 developer preview?

Please avoid committing changes that are not available for M1. I am gonna start an end-to-end testing. On Fri, Sep 12, 2014 at 10:23 AM, Nirmal Fernando wrote: > I create 4.1.0 M1 and M2 versions in the Jira. Please update the version > of the Jiras you are planning to get to the first developer