On Tue, Jan 21, 2014 at 8:29 AM, Lakmal Warusawithana <[email protected]>wrote:
> Hi Azeez, > > I have mention the cartridge type in this thread previously, here i list > again for your convenience. > > > 1. Application Cartridge - (e.g wordpress, drupal .etc - which does > not required external artifact repo) > 2. Data cartridge (e.g. MySQL, Mongo .etc - which does not required > external artifact repo) > 3. Framework cartridge (e.g. PHP, Ruby, Node.js .etc - which required > external artifact repo) > 4. LB cartridge (e.g Stratos LB, HAProxy LB - which does not required > external artifact repo) > > Based on these type, Front end and backend functionalities may change. for > e.g. whether it required a artifact repo or not ..etc > > It is fine to categorize cartridges for documentation purposes, but does the Stratos framework need to have prior knowledge about these cartridges? Do we have to change anything to introduce a new cartridge type? > > > On Tue, Jan 21, 2014 at 8:14 AM, Afkham Azeez <[email protected]> wrote: > >> Why is it necessary to classify the LB cartridge as a special cartridge? >> What are the other cartridge types available? Why do we need to specify >> cartridge types in the first place? >> >> >> On Thu, Jan 16, 2014 at 11:17 PM, Isuru Haththotuwa <[email protected]>wrote: >> >>> Hi Devs, >>> >>> >>> Currently it seems that identifying a LB cartridge is done using a >>> property in cartridge definition ("name": "load.balancer", "value": >>> "true"). The Autoscaler looks at this to decide whether to assign a normal >>> Cluster Monitor or a LB Cluster Monitor. If this property is not available, >>> there is no way to do this. IMHO, we should not add this as a property, but >>> as a mandatory field. WDYT of adding a unique property to identify the LB >>> cartridge? Furthermore, we could extend this approach to uniquely identify >>> the four basic cartridge categories as previously discussed in the mail >>> thread with subject [1]. >>> >>> [1]. A Better Model for Generic Types of Cartridges >>> >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com, >> *Member; Apache Software Foundation; >> **http://www.apache.org/*<http://www.apache.org/> >> >> *email: **[email protected]* <[email protected]> >> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * >> *http://blog.afkham.org* <http://blog.afkham.org> >> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * linked-in: **http://lk.linkedin.com/in/afkhamazeez >> <http://lk.linkedin.com/in/afkhamazeez>* >> >> *Lean . Enterprise . Middleware* >> >> > > > -- > Lakmal Warusawithana > Software Architect; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com, *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> *email: **[email protected]* <[email protected]> * cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
