You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Nirmal Fernando <ni...@wso2.com> on 2013/11/22 07:13:04 UTC
Region concept is not there in Openstack-nova API ?
Hi All,
Noticed $subject. Is it the case?
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
Re: Region concept is not there in Openstack-nova API ?
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Thanks for investigating. AFAIK Openstack has a 3 layer hierarchy :
>
> Region --> Zone --> Host
> 1 : n
> 1 : m
OK, now we're leaving the land of my OpenStack expertise. I hope one
of the OpenStack gurus on the list (or on IRC?) can shed more light on
this one!
ap
Re: Region concept is not there in Openstack-nova API ?
Posted by Everett Toews <ev...@RACKSPACE.COM>.
The naming on this was a design decision going back before my time. AFAIK, the choice of Zone [1] had to do with the scope of the Region concept in OpenStack and nothing to do with the name itself. I continued to use that naming for consistency.
I agree it's confusing but changing would be a nasty break in backwards compatibility. I'm not sure it's worth it but we can mull it over.
Everett
[1] http://jclouds.apache.org/documentation/reference/location-metadata-design/
On Nov 24, 2013, at 9:22 PM, Nirmal Fernando wrote:
> Thanks Everett. So, jclouds zone = openstack region and jclouds host =
> openstack host. Cool.
>
> Shouldn't this be fixed though?
>
>
> On Mon, Nov 25, 2013 at 4:35 AM, Everett Toews
> <ev...@rackspace.com>wrote:
>
>> That's true but typically only Regions are exposed to end users. In
>> jclouds = OpenStack terminology it's Zone = Region (yes it's confusing). So
>> when you call NovaApi.getConfiguredZones() what's actually being returned
>> is the Regions.
>>
>> You can get an overview of these in the OpenStack Ops Guide - Segregating
>> Your Cloud [1]
>>
>> Regards,
>> Everett
>>
>> [1]
>> http://docs.openstack.org/trunk/openstack-ops/content/scaling.html#segregate_cloud
>>
>> On Nov 22, 2013, at 9:14 PM, Nirmal Fernando wrote:
>>
>>> Hi Andrew,
>>>
>>> Thanks for investigating. AFAIK Openstack has a 3 layer hierarchy :
>>>
>>> Region --> Zone --> Host
>>> 1 : n
>>> 1 : m
>>>
>>>
>>>
>>>
>>> On Sat, Nov 23, 2013 at 5:42 AM, Andrew Phillips <aphillips@qrmedia.com
>>> wrote:
>>>
>>>> Could you give an example of how you're looking to *use* this region
>>>>> property?
>>>>>
>>>>
>>>> PS: Looking at tickets such as JCLOUDS-344 [1] and the corresponding
>> code
>>>> change [2], could it be that what you are looking for is what the
>> jclouds
>>>> OpenStack API refers to as "zones"?
>>>>
>>>> ap
>>>>
>>>> [1] https://issues.apache.org/jira/browse/JCLOUDS-344
>>>> [2] https://github.com/jclouds/jclouds/pull/174/files
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
Re: Region concept is not there in Openstack-nova API ?
Posted by Nirmal Fernando <ni...@wso2.com>.
Thanks Everett. So, jclouds zone = openstack region and jclouds host =
openstack host. Cool.
Shouldn't this be fixed though?
On Mon, Nov 25, 2013 at 4:35 AM, Everett Toews
<ev...@rackspace.com>wrote:
> That's true but typically only Regions are exposed to end users. In
> jclouds = OpenStack terminology it's Zone = Region (yes it's confusing). So
> when you call NovaApi.getConfiguredZones() what's actually being returned
> is the Regions.
>
> You can get an overview of these in the OpenStack Ops Guide - Segregating
> Your Cloud [1]
>
> Regards,
> Everett
>
> [1]
> http://docs.openstack.org/trunk/openstack-ops/content/scaling.html#segregate_cloud
>
> On Nov 22, 2013, at 9:14 PM, Nirmal Fernando wrote:
>
> > Hi Andrew,
> >
> > Thanks for investigating. AFAIK Openstack has a 3 layer hierarchy :
> >
> > Region --> Zone --> Host
> > 1 : n
> > 1 : m
> >
> >
> >
> >
> > On Sat, Nov 23, 2013 at 5:42 AM, Andrew Phillips <aphillips@qrmedia.com
> >wrote:
> >
> >> Could you give an example of how you're looking to *use* this region
> >>> property?
> >>>
> >>
> >> PS: Looking at tickets such as JCLOUDS-344 [1] and the corresponding
> code
> >> change [2], could it be that what you are looking for is what the
> jclouds
> >> OpenStack API refers to as "zones"?
> >>
> >> ap
> >>
> >> [1] https://issues.apache.org/jira/browse/JCLOUDS-344
> >> [2] https://github.com/jclouds/jclouds/pull/174/files
> >>
> >
> >
> >
> > --
> >
> > Thanks & regards,
> > Nirmal
> >
> > Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> > Mobile: +94715779733
> > Blog: http://nirmalfdo.blogspot.com/
>
>
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
Re: Region concept is not there in Openstack-nova API ?
Posted by Everett Toews <ev...@RACKSPACE.COM>.
That's true but typically only Regions are exposed to end users. In jclouds = OpenStack terminology it's Zone = Region (yes it's confusing). So when you call NovaApi.getConfiguredZones() what's actually being returned is the Regions.
You can get an overview of these in the OpenStack Ops Guide - Segregating Your Cloud [1]
Regards,
Everett
[1] http://docs.openstack.org/trunk/openstack-ops/content/scaling.html#segregate_cloud
On Nov 22, 2013, at 9:14 PM, Nirmal Fernando wrote:
> Hi Andrew,
>
> Thanks for investigating. AFAIK Openstack has a 3 layer hierarchy :
>
> Region --> Zone --> Host
> 1 : n
> 1 : m
>
>
>
>
> On Sat, Nov 23, 2013 at 5:42 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>
>> Could you give an example of how you're looking to *use* this region
>>> property?
>>>
>>
>> PS: Looking at tickets such as JCLOUDS-344 [1] and the corresponding code
>> change [2], could it be that what you are looking for is what the jclouds
>> OpenStack API refers to as "zones"?
>>
>> ap
>>
>> [1] https://issues.apache.org/jira/browse/JCLOUDS-344
>> [2] https://github.com/jclouds/jclouds/pull/174/files
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
Re: Region concept is not there in Openstack-nova API ?
Posted by Nirmal Fernando <ni...@wso2.com>.
Hi Andrew,
Thanks for investigating. AFAIK Openstack has a 3 layer hierarchy :
Region --> Zone --> Host
1 : n
1 : m
On Sat, Nov 23, 2013 at 5:42 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
> Could you give an example of how you're looking to *use* this region
>> property?
>>
>
> PS: Looking at tickets such as JCLOUDS-344 [1] and the corresponding code
> change [2], could it be that what you are looking for is what the jclouds
> OpenStack API refers to as "zones"?
>
> ap
>
> [1] https://issues.apache.org/jira/browse/JCLOUDS-344
> [2] https://github.com/jclouds/jclouds/pull/174/files
>
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
Re: Region concept is not there in Openstack-nova API ?
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Could you give an example of how you're looking to *use* this region
> property?
PS: Looking at tickets such as JCLOUDS-344 [1] and the corresponding
code change [2], could it be that what you are looking for is what the
jclouds OpenStack API refers to as "zones"?
ap
[1] https://issues.apache.org/jira/browse/JCLOUDS-344
[2] https://github.com/jclouds/jclouds/pull/174/files
Re: Region concept is not there in Openstack-nova API ?
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Noticed $subject. Is it the case?
I'm hardly the expert here, and this probably makes more sense to some
of the Rackspace folks on the mailing list. But just to clarify: would
this be the same type of "region" as referred to in the Nova command
line client docs [1]?
--os-region-name <region-name>
Defaults to env[OS_REGION_NAME].
Could you give an example of how you're looking to *use* this region property?
Regards
ap
[1] http://docs.openstack.org/user-guide/content/novaclient_commands.html