| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2659 |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for this neat feature @rhtyd, I just have one issue with it
When adding a project I get an error saying 'an account or projectid needs to be passed', I suppose there's something wrong with the passing of the projectId
Here's the steps:
Sorry, something went wrong.
|
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-3471)
|
Sorry, something went wrong.
|
@anuragaw a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2713 |
Sorry, something went wrong.
|
@anuragaw a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-3530)
|
Sorry, something went wrong.
Sorry, something went wrong.
|
Fixed merge conflicts and cleaned up some code left over. @rhtyd , @shwstppr |
Sorry, something went wrong.
We may have to ask @rhtyd or @PaulAngus if this is the expected behaviour or not. |
Sorry, something went wrong.
|
@anuragaw can you address this bug if you've time today? |
Sorry, something went wrong.
|
Looking now @rhtyd |
Sorry, something went wrong.
|
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2874 |
Sorry, something went wrong.
updateTemplate permissions API
The older UI was confusing as it showed both project and accounts. The list of accounts and projects with add/remove wasn't consistent and instead showed everything. This patch updates the dialogue layout logic to only allow users to select accounts or project one at a time. The lists are also populated such that users see accounts/projects which don't have permissions to add and accounts/projects that have permissions to remove.
…date template permissions
|
@anuragaw a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-118 |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-120 |
Sorry, something went wrong.
…em in list api calls
|
When admins share project owned templates we will now get a distinct message. |
Sorry, something went wrong.
|
@anuragaw a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✖centos7 ✔debian. JID-140 |
Sorry, something went wrong.
|
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-142 |
Sorry, something went wrong.
|
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-171)
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM based on manual testing for positive and negative results
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Problem: CloudStack users want the ability to share templates with other accounts or projects through the UI.
Root Cause: The ‘updateTemplatePermissions’ is only available via API and needs to be integrated with the UI in order to allow users to share templates with other accounts within the same domain, and also with projects that the sharing account has access to.
Solution: The CloudStack UI template view has been extended to include a button that allows users to update template permissions through the ‘updateTemplatePermissions’ API. This API supports 3 operations i.e. add, remove or reset. The reset operation does not require any parameters and it simply removes all permissions for a template. The add and remove parameters require either accounts or projects to be specified for sharing or stop sharing templates. The ‘listAccounts’ API has been extended to allow users to see all the accounts within the same domain if the global setting ‘allow.view.all.domain.accounts’ is set to true. This allows the accounts selection to be a multi-selection.
Types of changes
Screenshots (if appropriate):
Reset Operation hides the Accounts and Project ID fields as this operation does not require any additional parameters to be set.
Operation = Reset; Account and Project fields not displayed

Operation = Add/Remove , global setting: 'allow.user.view.all.domain.accounts' = false;

Operation = Add , global setting: 'allow.user.view.all.domain.accounts' = true; Domain has 3 accounts in total (bt1, bt2 and bt3). Logged in user is bt1 and so it is not shown on the dropdown list.

Operation = Remove , global setting: 'allow.user.view.all.domain.accounts' = true; Domain has 3 accounts in total (bt1, bt2 and bt3). The current template was only shared with bt2 by bt1 so dropdown menu only shows accounts that the current template has been shared with.

How Has This Been Tested?