My only concern is then, clients should be responsible for generating an available id (this will be hard, in a multi-tenant scenario).
May be we can recommend to define the deployment policy id in following format; deployment policy id = application id + random string ? On Wed, Dec 3, 2014 at 7:56 AM, Lakmal Warusawithana <lak...@wso2.com> wrote: > > > On Wed, Dec 3, 2014 at 7:35 AM, Shiroshica Kulatilake <sh...@wso2.com> > wrote: > >> >> From what I understood a deployment policy is tightly linked to the >> application structure - so if we do reuse it then the applications will >> also have to be similar structure wise - leaving details like the network >> partition details, partition details and algorithm to be changed. >> >> Arn't deployment policy ids still unique ? >> >> > For simplicity, shall we make deployment policy id unique across the > platform? > > > >> On Wed, Dec 3, 2014 at 7:15 AM, Nirmal Fernando <nirmal070...@gmail.com> >> wrote: >> >>> Hi All, >>> >>> $Subject right? If so, should we allow multiple deployment policies with >>> the same id for different applications ? >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> >> >> -- >> Shiroshica Kulatilake >> >> Architect, >> WSO2, Inc. http://wso2.com/ >> Phone: +94 776523867 >> > > > > -- > Lakmal Warusawithana > Vice President, Apache Stratos > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
