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
