You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@brooklyn.apache.org by Daniel Seybold <da...@uni-ulm.de> on 2015/06/12 15:10:30 UTC

How to use availabilityZone Parameter for location Openstack

Hi dev-guys,

After I get Brookyln running with Openstack it works like a charm by 
creating the VM and starting the applications.

But I'm stuck at one point.

I'm trying to add the *availabilityZone *Paramter to my blueprint but it 
isn't recognized by Openstack.
I assume Brooklyn does support this paramter because Jclouds supports it 
too.

Here a simple Yaml as example (the default availabilityZone exists on 
Openstack):

name: Nginx

location:
   gqt5EHkd (Id of my Openstack)

services:
  - serviceType: brooklyn.entity.proxy.nginx.NginxController
    provisioning.properties:
       autoAssignFloatingIp: true
       availabilityZone: default

Can you give me some advice how I can add the availabilityZone parameter 
in the right way?

Thanks in advance,
Daniel

Re: How to use availabilityZone Parameter for location Openstack

Posted by Daniel Seybold <da...@uni-ulm.de>.

Hi Aled,

thanks for your help and your hint with the named location was very 
useful :-)

I've followed your suggestion and tried the following YAML:

name: Nginx

location:
   named:Openstack

services:
  - serviceType: brooklyn.entity.proxy.nginx.NginxController
    provisioning.properties:
       autoAssignFloatingIp: true
       privateKeyFile: /path/to/keys
       templateOptions:
             availabilityZone: default

But unfortunately the Openstack availabilityZone is still picked randomely.

Do you have any clue why this parameter is still not used correctly?

Or is it possible to add the availabilityZone property to the 
brooklyn.properties file (if yes can you provide me the correct paramter 
name)

Thanks again!

Cheers,
Daniel

Am 12.06.2015 um 15:43 schrieb Aled Sage:
> Hi Daniel,
>
> You should be able to supply this with:
>
>    location:
>       # Id of my Openstack
>       gqt5EHkd
>
>    services:
>      - serviceType: brooklyn.entity.proxy.nginx.NginxController
>        provisioning.properties:
>           autoAssignFloatingIp: true
>    *      templateOptions:**
>    **        availabilityZone: default**
>    *
>
> Explanation: we have pulled out various common properties as top-level 
> configuration, to be passed into jclouds. However, for other 
> parameters such as the jclouds 
> NovaTemplateOptions.availabilityZone(String) you need to explicitly 
> say that this is a field of the jclouds template options.
>
> ---
> For location, you can also use "named locations" rather than having to 
> dig out the location id (if that would be easier for you) [1].
>
> Aled
>
> [1] 
> https://brooklyn.incubator.apache.org/v/latest/ops/locations/index.html
>
>
> On 12/06/2015 14:10, Daniel Seybold wrote:
>> Hi dev-guys,
>>
>> After I get Brookyln running with Openstack it works like a charm by 
>> creating the VM and starting the applications.
>>
>> But I'm stuck at one point.
>>
>> I'm trying to add the *availabilityZone *Paramter to my blueprint but 
>> it isn't recognized by Openstack.
>> I assume Brooklyn does support this paramter because Jclouds supports 
>> it too.
>>
>> Here a simple Yaml as example (the default availabilityZone exists on 
>> Openstack):
>>
>> name: Nginx
>>
>> location:
>>   gqt5EHkd (Id of my Openstack)
>>
>> services:
>>  - serviceType: brooklyn.entity.proxy.nginx.NginxController
>>    provisioning.properties:
>>       autoAssignFloatingIp: true
>>       availabilityZone: default
>>
>> Can you give me some advice how I can add the availabilityZone 
>> parameter in the right way?
>>
>> Thanks in advance,
>> Daniel
>>
>
>

Re: How to use availabilityZone Parameter for location Openstack

Posted by Aled Sage <al...@cloudsoftcorp.com>.

Hi Daniel,

You should be able to supply this with:

    location:
       # Id of my Openstack
       gqt5EHkd

    services:
      - serviceType: brooklyn.entity.proxy.nginx.NginxController
        provisioning.properties:
           autoAssignFloatingIp: true
    *      templateOptions:**
    **        availabilityZone: default**
    *

Explanation: we have pulled out various common properties as top-level 
configuration, to be passed into jclouds. However, for other parameters 
such as the jclouds NovaTemplateOptions.availabilityZone(String) you 
need to explicitly say that this is a field of the jclouds template options.

---
For location, you can also use "named locations" rather than having to 
dig out the location id (if that would be easier for you) [1].

Aled

[1] https://brooklyn.incubator.apache.org/v/latest/ops/locations/index.html

On 12/06/2015 14:10, Daniel Seybold wrote:
> Hi dev-guys,
>
> After I get Brookyln running with Openstack it works like a charm by 
> creating the VM and starting the applications.
>
> But I'm stuck at one point.
>
> I'm trying to add the *availabilityZone *Paramter to my blueprint but 
> it isn't recognized by Openstack.
> I assume Brooklyn does support this paramter because Jclouds supports 
> it too.
>
> Here a simple Yaml as example (the default availabilityZone exists on 
> Openstack):
>
> name: Nginx
>
> location:
>   gqt5EHkd (Id of my Openstack)
>
> services:
>  - serviceType: brooklyn.entity.proxy.nginx.NginxController
>    provisioning.properties:
>       autoAssignFloatingIp: true
>       availabilityZone: default
>
> Can you give me some advice how I can add the availabilityZone 
> parameter in the right way?
>
> Thanks in advance,
> Daniel
>

-- 
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.