Uh oh!
There was an error while loading. Please reload this page.
[UI] Add option to specify account/project while deploying VMs and creating networks - #8919
Conversation
DaanHoogland
commented
Apr 16, 2024
@BryanMLima , have you also logged in as the other user to manipulate/delete the resources created? (nice feature btw) |
DaanHoogland
commented
Apr 16, 2024
blueorangutan
commented
Apr 16, 2024
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
blueorangutan
commented
Apr 16, 2024
UI build: ✔️ |
DaanHoogland
commented
Apr 16, 2024
It doesn't work in qa. maybe due to an older backend. |
DaanHoogland
commented
Apr 16, 2024
@blueorangutan package |
blueorangutan
commented
Apr 16, 2024
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
blueorangutan
commented
Apr 16, 2024
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9272 |
DaanHoogland
commented
Apr 16, 2024
@blueorangutan test alma9 kvm-alma9 keepEnv |
blueorangutan
commented
Apr 16, 2024
@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + kvm-alma9) has been kicked to run smoke tests |
blueorangutan
commented
Apr 16, 2024
[SF] Trillian test result (tid-9846)
|
DaanHoogland
left a comment
There was a problem hiding this comment.
tested ok, Note that during VM deployment the target user must already have a network to deploy the VM in or there will be no option to the admin to deploy
@DaanHoogland, thanks for testing. In the view of VM deploy, you can create a new network and specify the domain and account, therefore, there is no need to pre-create the network for the account.
Yes, I was able to manage the resources (VM and network) as expected. |
lgtm, also tested manipulating the VMs in the user end in both domain and project scopes and it is working fine. |
weizhouapache
left a comment
There was a problem hiding this comment.
good improvement
code lgtm, not tested yet
DaanHoogland
commented
Apr 23, 2024
@BryanMLima are you going to do more work or can we merge? |
BryanMLima
commented
Apr 23, 2024
I added the component to the Isolated and L2 networks forms (shared networks already has the scope field, so I didn't want to change that). Now, root and domain admins can also create network to any account and project while deploying VMs (and when only creating networks, as it is the same component). We just need another round of tests for this one. |
BryanMLima
commented
Apr 23, 2024
@DaanHoogland, I also removed the duplicate fields mentioned in #6442 (comment). |
KlausDornsbach
commented
Apr 23, 2024
Nice addition. Tested, it works fine for the cases aforementioned |
DaanHoogland
commented
Apr 24, 2024
blueorangutan
commented
Apr 24, 2024
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
blueorangutan
commented
Apr 24, 2024
UI build: ✔️ |
DaanHoogland
commented
Apr 30, 2024
blueorangutan
commented
Apr 30, 2024
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
blueorangutan
commented
Apr 30, 2024
UI build: ✔️ |
9fcc187 to
6991793CompareBryanMLima
commented
May 22, 2024
@weizhouapache@KlausDornsbach, can you guys have a look at this PR with the latest change? |
vladimirpetrov
commented
Jun 10, 2024
@blueorangutan package |
blueorangutan
commented
Jun 10, 2024
@vladimirpetrov a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
blueorangutan
commented
Jun 10, 2024
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9837 |
vladimirpetrov
left a comment
There was a problem hiding this comment.
LGTM based on manual testing. Tested VMs and all three network types with different accounts, projects and domains.


Description
This PR adds a new component (
OwnershipSelection) to specify the account/project when creating a VM and networks (can also be used for other resources in the future). This component makes it easy for operators with roles Admin and Domain Admin to create VMs for any account and/or project that it has permission.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I deployed a number of VMs using different accounts and projects in different domains.
How did you try to break this feature and the system with this change?
I tried to verify that the UI only showed the permissions according to the account/project selected.