-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disassociate/change a security group from a Virtual Machine's NIC #5612
Labels
Milestone
Comments
larshith
changed the title
Modify Security Group rule for existing VM's
Disassociate/change a security group from a Virtual Machine's NIC
Nov 16, 2021
Duplicated in: #2411. We'll keep this one |
rsmontero
added
Priority: High
Status: Accepted
Type: Feature
Category: Drivers - Network
and removed
Status: Pending
labels
Nov 30, 2021
paczerny
pushed a commit
to OpenNebula/docs
that referenced
this issue
Jan 18, 2022
rsmontero
pushed a commit
to OpenNebula/docs
that referenced
this issue
Jan 25, 2022
rsmontero
added a commit
that referenced
this issue
Jan 28, 2022
Author: Pavel Czerný <pczerny@opennebula.systems>
rsmontero
pushed a commit
that referenced
this issue
Jan 28, 2022
rsmontero
pushed a commit
that referenced
this issue
Feb 1, 2022
FrederickBor
pushed a commit
to FrederickBor/docs
that referenced
this issue
Feb 9, 2022
Signed-off-by: Frederick Borges <fborges@opennebula.io>
@tinova PRs to be approved: |
tinova
pushed a commit
to OpenNebula/docs
that referenced
this issue
Feb 11, 2022
@paczerny please check that the sunstone implementation is correct, and we can close this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
How do we change a security group associated with a NIC of the Virtual Machine? We don't see any option to remove/add any security to a NIC of the Virtual Machine.
Use case
Currently, a small modification in VM with respective Security Group ends up with a complete rewrite of the Security Group rules.
Scenario:
Suppose a customer has spun up a Virtual Machine by accidentally attaching a security group named "default" which allows "all" Ingress communication, and without the knowledge, he has deployed his applications onto the VM. The customer then notices the Security group allowing "all" traffic. Customer decides to create a new security group to meet his needs and tries associating it to the VM NIC. But there is no option to do it. It also wouldn't be a viable option to change the firewall rules of the security group "default" as it would affect other VMs (let's say). We know that the NIC detach-attach and choosing the Security Group at that time does the work, but we think that it is not considered to be the best possible solution.
Interface Changes
Sunstone
Progress Status
The text was updated successfully, but these errors were encountered: