brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Turli <>
Subject Re: Vanilla Software Process: Declaring Security Groups in Openstack
Date Fri, 19 Jun 2015 12:50:46 GMT
Hi Daniel,

thanks for reporting this!

If you already have already defined a securityGroup in your openstack
installation, you can use use it specifying something like:


otherwise, Brooklyn will create and configure a new securityGroup opening
the ports required by your entity (by default it will open 22 to access the
VM via SSH)

There is a PR that should fix a bug with Openstack SecurityGroup Extension,, reported at
Do you have bandwidth to test this fix and report the results?


On Mon, 15 Jun 2015 at 18:32 Daniel Seybold <>

> Hi dev-guys,
> I'm trying to create a custom YAML file using the
> brooklyn.entity.basic.VanillaSoftwareProcess
> Unfortunately I'm not able to get the security groups working for my
> Openstack.
> Here is a sample of my YAML
> name: Simple Ghost Server Example
> location:
>    named:Openstack
> services:
> - type: brooklyn.entity.basic.VanillaSoftwareProcess
>    name: Simple Ghost Server
>      autoAssignFloatingIp: true
>      privateKeyFile: /path/to/keys
>      templateOptions:
>          availabilityZone: default
>    brooklyn.config:
>          http.port: 2368
>          httpPort: 2368
>    launch.command: |
>      ....
> If have found both spellings of HttpPort in your documentation:
> But none of them did work.
> Or is the wrong approach for declaring security groups using the
> VanillaSoftwareProcess?
> Thanks in advance for your help!
> Cheers,
> 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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message