Skip to content
This repository has been archived by the owner on Jan 31, 2019. It is now read-only.

securityGroup #9

Open
sebgoa opened this issue Dec 19, 2013 · 3 comments
Open

securityGroup #9

sebgoa opened this issue Dec 19, 2013 · 3 comments

Comments

@sebgoa
Copy link
Contributor

sebgoa commented Dec 19, 2013

Hi, looks like setting the securityGroup does not work.

I believe jclouds only uses securityGroupIds with should be a comma separated list of security group ids. But that did not work in my tests.

Also strange is that this securityGroup is set in the overrides section rather than the options section. If I put it in the options section then the template verification fails.

@uric
Copy link
Contributor

uric commented Dec 23, 2013

Can you share your config? Seems to be working for me, I use this configuration

@sebgoa
Copy link
Contributor Author

sebgoa commented Jan 7, 2014

Hi @uric, happy new year. Trying this again, it seems that it always uses the ''default' security group. If you create another one and try to use it, it will not and revert to using 'default' sg.

@uric
Copy link
Contributor

uric commented Jan 8, 2014

Hi @Runseb can you try with the following configuration:

 "securityGroupNames" : (["secGroup1", "secGroup2"]) as String[]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants