On Tue, Feb 17, 2015 at 10:39 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote:
> Hi, > > I have now implemented following deployment policy validations. > > - deployment policy can't be null > - deployment policy id can't be null or empty > - deployment policy should contain at least one network partition > reference > - network partition id can't be null or empty > - network partitions should be already added > - partition algorithm can't be null or empty > - partition algorithm should be either one-after-another or round-robin > - a network partition reference should contain at least one partition > reference > - partition id can't be null or empty > - partitions should be defined in the relevant network partitions (on > network partition deployment) > - partition reference should have a valid max value > > Great work Raj! Regarding the partition algorithm validation, a good suggestion Shiro! Thanks for pointing it. I would like to suggest to hard code the validation for the moment as we have more high priority tasks. May be later on we can improve it. AFAIK we even cannot add algorithms dynamically at present. Thanks -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
