Hi,
Nope war file will not be removed when the mock iaas is disabled or
enabled. You have to manually remove the web app.
When the web app exist , it will be loaded into the memory which would
consume some memory. Additionally if you enable Ghost Deployment, the web
pp will be unloaded after sometime even the web app exist physically, thus
memory will not be used.
Enable Ghost deployment
In* reposiroty/conf/carbon.xml*
<GhostDeployment>
<Enabled>false</Enabled>
<PartialUpdate>false</PartialUpdate>
</GhostDeployment>
On Fri, May 22, 2015 at 10:08 PM, Martin Eppel (meppel) <mep...@cisco.com>
wrote:
> Is the war file automatically excluded when the Mock IaaS is disabled or
> do we have to manually change the pom file (which one ?) to not include
> the war file ?
>
Btw, Is this documented ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* Friday, May 22, 2015 9:30 AM
> *To:* dev
> *Cc:* Mariangela Hills; Shavindri Dissanayake
> *Subject:* Re: Mock IaaS is enabled by default
>
>
>
> Hi Martin,
>
>
>
> In a production system we need to disable the Mock IaaS (via mock-iaas.xml
> file) and remove the mock-iaas.war file from the webapps folder. The
> reasons are:
>
> - Mock IaaS web application would consume resources.
> - Mock IaaS API is not secured, therefore anyone could invoke it and
> create N number of threads.
>
> Thanks
>
>
>
> On Fri, May 22, 2015 at 9:45 AM, Martin Eppel (meppel) <mep...@cisco.com>
> wrote:
>
> Thanks for the clarification
>
>
>
> Regards
>
>
>
> Martin
>
>
>
> *From:* Udara Liyanage [mailto:ud...@wso2.com]
> *Sent:* Thursday, May 21, 2015 7:08 PM
> *To:* dev
> *Cc:* Mariangela Hills; Shavindri Dissanayake
> *Subject:* RE: Mock IaaS is enabled by default
>
>
>
> Hi,
>
> You can have defined several iaas s in cloud-controller.xml. However you
> define what iaas(s) you need by network partition/partition. So instances
> will be spawned in the partitions defined for application regardless of
> what other iaas s available. So having Mock IaasS enabled by default will
> not have impact in your case.
>
> Hi Udara,
>
>
>
> If the Mock IaaS is enabled by default, what is the expected behavior ?
>
>
>
> I installed a system with OpenStack as IaaS and left the configuration
> (inadvertently) in the default mode with Mock IaaS enabled – however, when
> I deployed an application all VMs are spun up by Open stack (which in hind
> sight is surprising).
>
> Is the mentioned default configuration overwritten by setting the
> iaasprovider in the cloud controller.xml (to openstack) ?
>
> Will there any (unexpected) side effects if the default is left to be set
> to MockIaaS but the cloud controller specifies a different IaaS ?
>
>
>
> What is the recommended setting for a real deployment (Mock IaaS disabled
> ?!)
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Udara Liyanage [mailto:ud...@wso2.com]
> *Sent:* Wednesday, May 20, 2015 8:52 PM
> *To:* dev
> *Cc:* Mariangela Hills; Shavindri Dissanayake
> *Subject:* Mock IaaS is enabled by default
>
>
>
> Hi Mari,
>
>
>
> Mock IaaS is enabled by default now. Please update the step 2(b) with that.
>
>
>
> [1]
> https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Install+Stratos+with+the+Mock+IaaS+in+a+Testing+Environment
>
>
>
> --
>
>
> Udara Liyanage
>
> Software Engineer
>
> WSO2, Inc.: http://wso2.com
>
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
>
> phone: +94 71 443 6897
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
