Skip to content
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

Add support for users to add Security Group to the VM along with other selections like network and storage. #157

Open
anmolsachan opened this issue Jan 30, 2025 · 0 comments

Comments

@anmolsachan
Copy link
Contributor

anmolsachan commented Jan 30, 2025

User Story: As a user, I want to specify a security group for the migrated VM, so that I can enforce the appropriate network security policies in the target OpenStack environment.

Description:
Currently, vJailbreak allows users to select network and storage mappings for migrated VMs but lacks an option to assign security groups. Adding this capability will ensure that migrated VMs have the correct firewall rules and access policies applied upon migration.

Acceptance Criteria:

UI Support:

  • Users can select a security group during migration plan creation.
  • The UI should list available security groups from the target OpenStack project.
  • Users should be able to select multiple security groups per VM if needed.

API & Backend:

  • The security group selection is stored in the migration plan.
  • v2v-helper applies the selected security group to the VM post-migration.
  • If no security group is selected, apply the OpenStack default security group

Validation & Error Handling:

  • Display an error if the selected security group does not exist in the target OpenStack environment.
  • Ensure that the migration process does not proceed if the security group assignment fails.

Logging & Tracking:

  • Include security group details in migration logs.
  • Display assigned security groups in the migration summary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant