On Sun, Dec 15, 2013 at 9:20 PM, chris snow <[email protected]> wrote:
> What is the licensing issue with shipping cartridges? > > We cant shipped GPL components, that if we want add VM images. > If cartridges were defined as puppet modules so the cartridges so the > operating system (or application) specific functionality was abstracted by > puppet would that get around any license issues? > > Yes, this will resolve the issue. > > On Sun, Dec 15, 2013 at 11:51 AM, Lahiru Sandaruwan <[email protected]>wrote: > >> >> >> >> On Sun, Dec 15, 2013 at 1:03 PM, Lakmal Warusawithana <[email protected]>wrote: >> >>> >>> >>> >>> On Sun, Dec 15, 2013 at 10:51 AM, Lahiru Sandaruwan <[email protected]>wrote: >>> >>>> Awesome stuff Chris, >>>> >>>> What i like about this article most is that it explain Stratos >>>> correctly using minimum number of words :) >>>> >>>> I think we can use the word PaaS in the introduction to tell that >>>> Stratos is a PaaS. >>>> >>> >>> better to use with "Stratos is a PaaS framework." which you can build a >>> PaaS. >>> >> >> Yeah, better we use the word 'framework' and explain how simple it is to >> create to totally new PaaS with Stratos. >> >> So it's just creating a new cartridge and add it to IaaS. We can provide >> sample cartridges in Stratos web site, but may not be able ship those with >> release artifacts due to Ubuntu licence etc. >> >>> >>> >>>> >>>> Also we can have an step to show what happens after monitoring in >>>> diagram, in-addition to step 6, may be we add a step called "scale runtime" >>>> or something. >>>> >>>> >>>> Thanks. >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Sun, Dec 15, 2013 at 10:11 AM, chris snow <[email protected]>wrote: >>>> >>>>> In the developer guide [1], these is a section "How does Apache >>>>> Stratos (Incubating) work?". >>>>> >>>>> After reading this section, it would be useful for the reader to have >>>>> the option to go through a quick hands on demo of the workflow that was >>>>> explained in the section. >>>>> >>>>> Does the wso2 live demo service support the workflow outlined in the >>>>> dev guide using git for a repo? If not, do the VMware images support the >>>>> workflow? Are there any other options for a developer to quickly try out >>>>> the workflow? >>>>> >>>>> Many thanks, >>>>> Chris >>>>> --- >>>>> [1] >>>>> https://docs.google.com/document/d/1GiEsqVbqhp0rBqf6LhpNqB57TVxIApNg9o1Sk0zI9Oo/edit >>>>> >>>> >>>> >>>> >>>> -- >>>> -- >>>> 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 >>>> >>>> >>> >>> >>> -- >>> Lakmal Warusawithana >>> Software Architect; WSO2 Inc. >>> Mobile : +94714289692 >>> Blog : http://lakmalsview.blogspot.com/ >>> >>> >> >> >> -- >> -- >> 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 >> >> > > > -- > Check out my professional profile and connect with me on LinkedIn. > http://lnkd.in/cw5k69 > -- Lakmal Warusawithana Software Architect; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
