You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Nirmal Fernando <ni...@gmail.com> on 2013/11/20 17:07:02 UTC
Partition definition should just have set of properties (1..n)
All,
IMO $Subject. It's not correct to have a scope. In my view expectation of a
Partition can be "I want my instances in *EC2* IaaS and in *us-east-1*region".
<partition id="p1">
<property name="PROVIDER" value="ec2"/>
<property name="REGION" value="us-east-1"/>
....
</partition>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Partition definition should just have set of properties (1..n)
Posted by Lahiru Sandaruwan <la...@wso2.com>.
+1, we can use properties since the introduction of new IaaS is
easy(Because it might have a different differentiation of location
separation).
On Wed, Nov 20, 2013 at 9:37 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> All,
>
> IMO $Subject. It's not correct to have a scope. In my view expectation of
> a Partition can be "I want my instances in *EC2* IaaS and in *us-east-1*region".
>
> <partition id="p1">
> <property name="PROVIDER" value="ec2"/>
> <property name="REGION" value="us-east-1"/>
> ....
> </partition>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Partition definition should just have set of properties (1..n)
Posted by Udara Liyanage <ud...@wso2.com>.
+1 for proposed method. This way we can go more deeper. Within a partition
we can configure provider and region ...etc. We are not constrained for
just provider or region or zone.
Touched, not typed. Erroneous words are a feature, not a typo.
Re: Partition definition should just have set of properties (1..n)
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi
Why i introduced scope is that when Autoscaler calls to start or terminate
an instance by specifying a partition, then CC can decide the level of
partition from the scope and act accordingly.
Thanks,
Reka
On Thu, Nov 21, 2013 at 9:59 AM, Nirmal Fernando <ni...@gmail.com>wrote:
> Yes, I realized the same, when I go thru Reka's email to dev@.
>
>
> On Thu, Nov 21, 2013 at 8:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks, I think how Reka designed this was as follows:
>>
>> - IaaS provider information is defined in cloud-controller.xml, so that
>> partitions could refer to them using the provider name.
>> - Then partitions could be defined for IaaS Providers, Regions, Zones,
>> etc. This is defined as a enumeration and its called Scope.
>> - If Scope = PROVIDER then the partitions should provide the provider
>> name. Here I think the region would be the region defined in the given
>> provider.
>> - If Scope = REGION then the partition should provide the provider name
>> and the region name. Here the region defined in the provider would get
>> overridden.
>> - If Scope = ZONE then the partition should provide the provider name,
>> region and zone. Similarly the region and the zone defined in the provider
>> would get overridden.
>>
>> Thanks
>>
>>
>>
>> On Thu, Nov 21, 2013 at 7:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> Hi Imesh,
>>>
>>>
>>> On Thu, Nov 21, 2013 at 6:46 PM, Imesh Gunaratne <im...@apache.org>wrote:
>>>
>>>> I think what was meant by scope is the same:
>>>>
>>>> <partition>
>>>>
>>>> <id>P1</id>
>>>>
>>>> <scope>PROVIDER</scope>
>>>>
>>>> <property name="provider" value="ec2"/>
>>>>
>>>> <property name="region" value="us-east-1" />
>>>> </partition>
>>>>
>>>
>>> Part that I don't understand is the rationale behind scope. If I take
>>> the sample you've given, it says scope is 'Provider', what does it means
>>> here? What if I provide scope as 'Region' here? What is the difference to
>>> the final outcome?
>>>
>>>>
>>>> However I think your suggestion looks much cleaner +1
>>>>
>>>>
>>> Great.
>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> On Wed, Nov 20, 2013 at 9:37 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> IMO $Subject. It's not correct to have a scope. In my view expectation
>>>>> of a Partition can be "I want my instances in *EC2* IaaS and in
>>>>> *us-east-1* region".
>>>>>
>>>>> <partition id="p1">
>>>>> <property name="PROVIDER" value="ec2"/>
>>>>> <property name="REGION" value="us-east-1"/>
>>>>> ....
>>>>> </partition>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Partition definition should just have set of properties (1..n)
Posted by Nirmal Fernando <ni...@gmail.com>.
Yes, I realized the same, when I go thru Reka's email to dev@.
On Thu, Nov 21, 2013 at 8:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks, I think how Reka designed this was as follows:
>
> - IaaS provider information is defined in cloud-controller.xml, so that
> partitions could refer to them using the provider name.
> - Then partitions could be defined for IaaS Providers, Regions, Zones,
> etc. This is defined as a enumeration and its called Scope.
> - If Scope = PROVIDER then the partitions should provide the provider
> name. Here I think the region would be the region defined in the given
> provider.
> - If Scope = REGION then the partition should provide the provider name
> and the region name. Here the region defined in the provider would get
> overridden.
> - If Scope = ZONE then the partition should provide the provider name,
> region and zone. Similarly the region and the zone defined in the provider
> would get overridden.
>
> Thanks
>
>
>
> On Thu, Nov 21, 2013 at 7:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi Imesh,
>>
>>
>> On Thu, Nov 21, 2013 at 6:46 PM, Imesh Gunaratne <im...@apache.org>wrote:
>>
>>> I think what was meant by scope is the same:
>>>
>>> <partition>
>>>
>>> <id>P1</id>
>>>
>>> <scope>PROVIDER</scope>
>>>
>>> <property name="provider" value="ec2"/>
>>>
>>> <property name="region" value="us-east-1" />
>>> </partition>
>>>
>>
>> Part that I don't understand is the rationale behind scope. If I take the
>> sample you've given, it says scope is 'Provider', what does it means here?
>> What if I provide scope as 'Region' here? What is the difference to the
>> final outcome?
>>
>>>
>>> However I think your suggestion looks much cleaner +1
>>>
>>>
>> Great.
>>
>>> Thanks
>>>
>>>
>>>
>>> On Wed, Nov 20, 2013 at 9:37 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>> All,
>>>>
>>>> IMO $Subject. It's not correct to have a scope. In my view expectation
>>>> of a Partition can be "I want my instances in *EC2* IaaS and in
>>>> *us-east-1* region".
>>>>
>>>> <partition id="p1">
>>>> <property name="PROVIDER" value="ec2"/>
>>>> <property name="REGION" value="us-east-1"/>
>>>> ....
>>>> </partition>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Partition definition should just have set of properties (1..n)
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks, I think how Reka designed this was as follows:
- IaaS provider information is defined in cloud-controller.xml, so that
partitions could refer to them using the provider name.
- Then partitions could be defined for IaaS Providers, Regions, Zones, etc.
This is defined as a enumeration and its called Scope.
- If Scope = PROVIDER then the partitions should provide the provider name.
Here I think the region would be the region defined in the given provider.
- If Scope = REGION then the partition should provide the provider name and
the region name. Here the region defined in the provider would get
overridden.
- If Scope = ZONE then the partition should provide the provider name,
region and zone. Similarly the region and the zone defined in the provider
would get overridden.
Thanks
On Thu, Nov 21, 2013 at 7:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi Imesh,
>
>
> On Thu, Nov 21, 2013 at 6:46 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think what was meant by scope is the same:
>>
>> <partition>
>>
>> <id>P1</id>
>>
>> <scope>PROVIDER</scope>
>>
>> <property name="provider" value="ec2"/>
>>
>> <property name="region" value="us-east-1" />
>> </partition>
>>
>
> Part that I don't understand is the rationale behind scope. If I take the
> sample you've given, it says scope is 'Provider', what does it means here?
> What if I provide scope as 'Region' here? What is the difference to the
> final outcome?
>
>>
>> However I think your suggestion looks much cleaner +1
>>
>>
> Great.
>
>> Thanks
>>
>>
>>
>> On Wed, Nov 20, 2013 at 9:37 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> All,
>>>
>>> IMO $Subject. It's not correct to have a scope. In my view expectation
>>> of a Partition can be "I want my instances in *EC2* IaaS and in
>>> *us-east-1* region".
>>>
>>> <partition id="p1">
>>> <property name="PROVIDER" value="ec2"/>
>>> <property name="REGION" value="us-east-1"/>
>>> ....
>>> </partition>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
Re: Partition definition should just have set of properties (1..n)
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Imesh,
On Thu, Nov 21, 2013 at 6:46 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I think what was meant by scope is the same:
>
> <partition>
>
> <id>P1</id>
>
> <scope>PROVIDER</scope>
>
> <property name="provider" value="ec2"/>
>
> <property name="region" value="us-east-1" />
> </partition>
>
Part that I don't understand is the rationale behind scope. If I take the
sample you've given, it says scope is 'Provider', what does it means here?
What if I provide scope as 'Region' here? What is the difference to the
final outcome?
>
> However I think your suggestion looks much cleaner +1
>
>
Great.
> Thanks
>
>
>
> On Wed, Nov 20, 2013 at 9:37 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> All,
>>
>> IMO $Subject. It's not correct to have a scope. In my view expectation of
>> a Partition can be "I want my instances in *EC2* IaaS and in *us-east-1*region".
>>
>> <partition id="p1">
>> <property name="PROVIDER" value="ec2"/>
>> <property name="REGION" value="us-east-1"/>
>> ....
>> </partition>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Partition definition should just have set of properties (1..n)
Posted by Imesh Gunaratne <im...@apache.org>.
I think what was meant by scope is the same:
<partition>
<id>P1</id>
<scope>PROVIDER</scope>
<property name="provider" value="ec2"/>
<property name="region" value="us-east-1" />
</partition>
However I think your suggestion looks much cleaner +1
Thanks
On Wed, Nov 20, 2013 at 9:37 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> All,
>
> IMO $Subject. It's not correct to have a scope. In my view expectation of
> a Partition can be "I want my instances in *EC2* IaaS and in *us-east-1*region".
>
> <partition id="p1">
> <property name="PROVIDER" value="ec2"/>
> <property name="REGION" value="us-east-1"/>
> ....
> </partition>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>