On Tue, Nov 12, 2013 at 11:51 AM, Reka Thirunavukkarasu <[email protected]>wrote:
> Hi all, > > This is to introduce the partition configuration as part of IaaS > configuration in Cloud Controller. As the initial version, we support > provider (already there), region, zone and host. According to the IaaS, a > user can define any of the above partition in a hierarchical manner. So > that, > > <iaasProvider type="openstack-1" name="openstack specific details"> > > > <className>org.wso2.carbon.stratos.cloud.controller.iaases.OpenstackNovaIaas</className> > <provider>openstack-nova</provider> > <identity > svns:secretAlias="cloud.controller.openstack.identity">xxx</identity> > <credential > svns:secretAlias="cloud.controller.openstack.credential">xxx</credential> > <region> > <!--id as user readablae name for the partition Rg: > region1--> > <id>R1</id> > <!--type as the actually configured name of the partition > in the IaaS > Eg: region can be specified as type RegionOne in Openstack > or us-east-1 in ec2--> > <type>RegionOne</type> > <identity > svns:secretAlias="cloud.controller.openstack.identity">stratos:stratos</identity> > <credential > svns:secretAlias="cloud.controller.openstack.credential">stratos123</credential> > <property name="jclouds.endpoint" value=" > http://cloud.private.wso2.com:5000/v2.0"; /> > <property > name="jclouds.openstack-nova.auto-create-floating-ips" value="false"/> > <property name="jclouds.api-version" value="2.0/" /> > > <imageId>nova/dab37f0e-cf6f-4812-86fc-733acf22d5e6</imageId> > <zone> > <id>Z1</id> > <!--type as the actually configured name of the > partition in the IaaS Eg: zone can be specified as type us-east-1c in ec2--> > <type>zone1</type> > <property name="instanceType" value="m1.large"/> > <property name="keyPair" value="nirmal-key"/> > <host> > <id>H1</id> > <!--type as the actually configured name of the > partition in the IaaS Eg: zone can be specified as type xxx only > inopenstack--> > <type>host11</type> > <property name="instanceType" value="m1.large"/> > </host> > </zone> > <zone> > <id>Z2</id> > <type>zone2</type> > <property name="instanceType" value="m1.small"/> > </zone> > </region> > </iaasProvider> > > Here any of the properties can be overwritten by the child partition. If > any required properties are not found from a partition, then that property > will be taken from the parent partition. > Please provide your feedback on this approach... > Reka, it's good that you followed the same pattern we had in Cartridge design. It's best if you can generate the XSD and validate the definition, if not already done. Question: * Why we need both type and id? * How the policy file and cartridge definition relates? Should one configure policy file and cartridge definition together? > > Thanks, > Reka > > > > -- > Reka Thirunavukkarasu > Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
