Repository navigation
An Config option to simply allow nested VM access #10286
Description
The required feature described as a wish
As asked in this discusssion: #10225
I would like to have an easier way to allow network traffic to nested VM's in basic networking installations.
Currently you would need to manually "hack" the security_group.py script to just not execute anything at all.
This would be useful for inhouse non security sensitive installation where people could simply host e.g. test CloudStack installations
or other virtualization platforms to test.
Activity
DaanHoogland commentedon Jan 28, 2025
@rp- , do you have any implementation design in mind?
And do you have plans to do this yourself?
rp- commentedon Jan 28, 2025
I may find time to do it myself, but may design would be rather simple, introduce some config option either on the management server or in the agent.properties and simply don't call the
security_group.py?But maybe there are better options or some parts of the
security_group.pyare useful to execute?I would need some opinions or dig deeper into it.
DaanHoogland commentedon Jan 28, 2025
go for simple first, we can extend later as users (read you ;) see extra requirements. We only need to take care not to paint ourselves in a corner.
jerome079 commentedon Apr 4, 2025
Hi, @bradywilkin and I are students at the University of Texas at Austin. As part of our virtualization class, we would like to contribute to Apache Cloudstack and resolve this issue.
github-actions commentedon Dec 24, 2025
This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.