On Thu, Dec 5, 2013 at 9:32 AM, Udara Liyanage <[email protected]> wrote:
> Hi, > > Partition, deployment policies, auto scaler policy deployments are also > thought to be fallow the same way I guess. > +1 > > > On Wed, Dec 4, 2013 at 3:49 AM, Isuru Haththotuwa <[email protected]> wrote: > >> On Wed, Dec 4, 2013 at 2:00 PM, Kishanthan Thangarajah < >> [email protected]> wrote: >> >>> On Wed, Dec 4, 2013 at 12:42 PM, Isuru Haththotuwa <[email protected]> >>> wrote: >>> > On Wed, Dec 4, 2013 at 12:23 PM, Reka Thirunavukkarasu <[email protected]> >>> > wrote: >>> >> >>> >> +1 for the Rest API support for cartridge deployment. Since we can >>> deploy >>> >> using the Rest API, are we going to get rid of the file based hot >>> deployment >>> >> of the cartridges? >>> > >>> > In my opinion we should provide deployment through the Rest API only. >>> So >>> > ideally we should remove file system based deployment. >>> >>> Any particular reason on why this option should be removed? Also all >>> the other options such as update, undeployment, etc handled via REST? >>> >> Yes, the plan is to support all operations via REST. >> >> Couple of reasons: >> 1. It will be a clean and a consistent API - Currently operations such >> as subscription, etc. are supported via the Rest API while to deploy a >> cartridge you need to copy it to the relevant directory. >> 2. A user can easily access and operate Stratos via a Rest client, won't >> need access to the internals such as the file system. >> >>> >>> > However, hot >>> > deployment should be available. >>> >> >>> >> >>> >> Thanks, >>> >> Reka >>> >> >>> >> >>> >> On Wed, Dec 4, 2013 at 12:17 PM, Lahiru Sandaruwan <[email protected]> >>> >> wrote: >>> >>> >>> >>> +1. Ultimately we should be able to view, edit, and deploy new >>> cartridge >>> >>> definitions using UIs. >>> >>> >>> >>> Thanks. >>> >>> >>> >>> >>> >>> On Wed, Dec 4, 2013 at 12:08 PM, Isuru Haththotuwa <[email protected]> >>> >>> wrote: >>> >>>> >>> >>>> Hi Devs, >>> >>>> >>> >>>> The current Rest API supports operations such as tenant management, >>> >>>> listing available cartridges, subscribing, unsubscribing, etc. But >>> still the >>> >>>> cartridge definition deployment happens through the file system. In >>> my view >>> >>>> it is better if we can do this through the Rest API as well. WDYT? >>> >>>> >>> >>>> -- >>> >>>> Thanks and Regards, >>> >>>> >>> >>>> Isuru H. >>> >>>> Software Engineer, WSO2 Inc. >>> >>>> +94 716 358 048 >>> >>>> >>> >>>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> -- >>> >>> Lahiru Sandaruwan >>> >>> Software Engineer, >>> >>> Platform Technologies, >>> >>> WSO2 Inc., http://wso2.com >>> >>> lean.enterprise.middleware >>> >>> >>> >>> email: [email protected] cell: (+94) 773 325 954 >>> >>> blog: http://lahiruwrites.blogspot.com/ >>> >>> twitter: http://twitter.com/lahirus >>> >>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>> >>> >>> >> >>> >> >>> >> >>> >> -- >>> >> Reka Thirunavukkarasu >>> >> Software Engineer, >>> >> WSO2, Inc.:http://wso2.com, >>> >> Mobile: +94776442007 >>> >> >>> >> >>> > >>> > >>> > >>> > -- >>> > Thanks and Regards, >>> > >>> > Isuru H. >>> > Software Engineer, WSO2 Inc. >>> > +94 716 358 048 >>> > >>> > >>> >> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> Software Engineer, WSO2 Inc. >> +94 716 358 048* <http://wso2.com/>* >> >> >> > > > -- > Udara Liyanage > Software Engineer > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > web: http://udaraliyanage.wordpress.com > phone: +94 71 443 6897 > -- Thanks and Regards, Isuru H. Software Engineer, WSO2 Inc. +94 716 358 048* <http://wso2.com/>*
