Hi Nirmal, Thanks for the detailed explanation.. yes, my interpretation of IaaS instance is wrong. I thought its kind of similar to DB connection instance.. (a one time thing)
thanks, --Pradeep On Sun, Sep 15, 2013 at 1:06 PM, Nirmal Fernando <[email protected]>wrote: > > > > On Sun, Sep 15, 2013 at 12:48 PM, Pradeep Fernando <[email protected]>wrote: > >> Hi Nirmal, >> >> >> On Sun, Sep 15, 2013 at 12:37 PM, Nirmal Fernando <[email protected] >> > wrote: >> >>> Hi Pradeep, >>> >>> >>> On Sun, Sep 15, 2013 at 10:38 AM, Pradeep Fernando >>> <[email protected]>wrote: >>> >>>> Hi Devs, >>>> >>>> While listening to hangout on cloud-controller, the $subject came up.. >>>> May be its a trivial thing. But I still can't get it. >>>> >>>> In the <cartridge>.xml config we can refer multiple IAASes. >>>> >>>> eg: tomat cartridge can refer EC2 and Openstack based IAASes. >>>> >>>> why cant multiple cartridges refer to same IAAS ? eg, >>>> >>>> tomcat cartridge refers to IAAS 'A' >>>> PHP cartridge refers to IAAS 'A' as well.. >>>> >>> >>> You've misunderstood what I explained there in the hangout. >>> >>> In the hangout, I was talking about the Information model of Stratos and >>> was talking from the java Objects point of view. >>> >>> Multiple cartridges referring to same IaaS is a very basic feature of >>> Stratos (conceptually), >>> >>> But, from a programmer's point of view, each Cartridge object, would >>> have its own IaaS instances (Java instances). There's absolutely no >>> requirement what so ever for multiple Cartridges to be referenced to the >>> same IaaS instance. >>> >> >> May be i'm interpreting the IaaS instance wrong... >> Why two cartridges can't refer to same IaaS instance ( by IaaS instance i >> mean the object model created using the IaaS section in >> cloud-controller.xml.) I thought, IaaS instance is one per IaaS and is >> global... >> > > Pradeep, unfortunately that doesn't make sense, right? Cause, IaaS > instance holds and define a Cartridge in a particular IaaS. If we have a > global IaaS instance that would necessarily mean that we have only one real > Cartridge. > > Beside that, what you define in cloud-controller.xml has no usefulness, > unless you create a reference from a Cartridge definition. > > Within a Cartridge definition, you can either put a reference to an IaaS > defined in cloud-controller.xml and override its properties or define a > totally new IaaS. > > So, as you may have already understand, we define IaaSes in > cloud-controller.xml, just to avoid repeating common properties of an IaaS, > in cartridge definitions. > >> >> >> --Pradeep >> >> >> >> >>> >>> Hope you understood it. Do not hesitate to get your confusions cleared, >>> if you have more. >>> >>>> >>>> >>>> thanks in advance, >>>> --Pradeep >>>> >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> C.S.Nirmal J. Fernando >>> Senior Software Engineer, >>> WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> >> >> -- >> Pradeep Fernando. >> http://pradeepfernando.blogspot.com/ >> > > > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Senior Software Engineer, > WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ > -- Pradeep Fernando. http://pradeepfernando.blogspot.com/
