+1 Great Imesh.Glad to see the issue had been overcome.--On Tue, Jan 27, 2015 at 7:36 PM, Gayan Gunarathne <firstname.lastname@example.org> wrote:+1Great stuff Imesh!Thanks,Gayan--On Tue, Jan 27, 2015 at 7:13 PM, Dakshika Jayathilaka <email@example.com> wrote:Hi Imesh,Great work.. I think we need to add this into documentation.Adding Mari to this..Regards,On Tue, Jan 27, 2015 at 7:04 PM, Imesh Gunaratne <firstname.lastname@example.org> wrote:Please find the Mock IaaS API endpoint configuration in cloud-controller.xml file:<iaasProvider type="mock" name="Mock">
<property name="api.endpoint" value="https://localhost:9443/mock-iaas-api" />
</iaasProvider>Now stratos distribution can start with mock-iaas server profile as follows:sh <stratos-home>/bin/stratos.sh -Dprofile=mock-iaasThis effort will help us to test cloud bursting scenarios and stratos product clustering features with Mock IaaS.ThanksOn Tue, Jan 27, 2015 at 6:55 PM, Imesh Gunaratne <email@example.com> wrote:Hi Devs,I have now fixed the above issue and pushed the modification to master branch.The problem was with the way we package CXF runtime into the distribution. We had written maven logic to get all the dependencies of the REST API/Web App feature and copy them into the CXF runtime folder. It has packaged Stratos dependencies to the CXF runtime and as a result Stratos components have been loaded by the Web App class loader. I removed this logic since CXF runtime is already packaged by the Carbon CXF feature.As a part of this effort I have also refined features, the way we have structured them and feature names.ThanksOn Tue, Jan 27, 2015 at 12:28 PM, Imesh Gunaratne <firstname.lastname@example.org> wrote:Hi Devs,Currently Mock IaaS resides in the Cloud Controller. However to verify cloud bursting scenarios and Stratos product clustering features we need to be able to run Mock IaaS as a separate product. To support this we could expose Mock IaaS as a REST service and create a server profile. By doing that we could start Mock IaaS as a separate product and configure cloud controller to talk to it via the Mock Iaas API.I did almost all the changes required for this functionality and found a problem in accessing Mock IaaS OSGi service from the Mock IaaS API web app. It seems like Mock IaasS API web app creates a separate class loader and it does not re-use the classes loaded by OSGi runtime. Will update the status of this soon.Thanks--Imesh GunaratneTechnical Lead, WSO2Committer & PMC Member, Apache Stratos--Imesh GunaratneTechnical Lead, WSO2Committer & PMC Member, Apache Stratos--Imesh GunaratneTechnical Lead, WSO2Committer & PMC Member, Apache StratosGayan GunarathneTechnical LeadWSO2 Inc.