kcloud
September 4, 2015, 3:47pm
1
When using EC2 VPCs, security group ids are expected, the below changes were necessary to make the template work:
oneadmin@/usr/lib/one/ruby#: diff ec2_driver.rb.orig ec2_driver.rb
124c124
< :opt => 'security_groups',
---
> :opt => 'security_group_ids',
Otherwise, VMs using subnet IDs will not launch in VPCs, they will fail with the below error:
The parameter groupName cannot be used with the parameter subnet
dmolina
(Daniel Molina)
September 10, 2015, 10:17am
2
Hi,
Thank you for reporting this. There is already a ticket for it and we will try to include it for the final release:
http://dev.opennebula.org/issues/3753
Cheers
dmolina
(Daniel Molina)
September 15, 2015, 1:26pm
4
Hi,
It should be fixed in master. I have included an extra option for security_group_ids instead of replacing the existing security_groups
http://dev.opennebula.org/projects/opennebula/repository/revisions/de34c04d4f53e39f83acffce6570de660a3f7a94/diff/
Cheers
kcloud
September 30, 2015, 3:54pm
5
Thanks Daniel!
Working as expected now. Would be worth updating the documentation with the new attribute: http://docs.opennebula.org/4.14/advanced_administration/cloud_bursting/ec2g.html
dmolina
(Daniel Molina)
October 1, 2015, 8:50am
6
Thank you for the feedback, I have just updated the docs in master.