DK101010 opened a new pull request #4828:
URL: https://github.com/apache/cloudstack/pull/4828
### Description
This PR is more an POC and I need some opinions.
Background:
Many of my admins have the problem that they are get an vm name with a
problem but not the related project. In this situation they must check all
project to find them. Currently they are using a script to get all vm's with
related projects, but they want also a opportunity in the ui.
For this reason I build up a new command class as a first step and after
this I want to create a search field in the ui to see a list of vm names and
the related project names. I'm continue thought me that the admin can click on
the vm in this list to jump into the vm details or he can click on the project
to see the project list view with all vms.
========
The api call works and I get all VM's independent of a certian project . But
i have headache with some points.
1. Currently I get to much informations of the vm and I have concerns that I
break the permission concept of cloudstack.
The only things that I have found is to set the ReponseView to restricted
and the details != all.
2. When I call this api call via cloudmonkey, I get the correct and valid
json but I get also this error "on parsing and printing list index out of
range". Not sure if it a bug of cloudmonkey or a misconfiguration of my
ReponseView
3. Not sure which package the right one is to store the new command.
<!---
*********************************************************************************
-->
<!--- NOTE: AUTOMATATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE
DOCUMENTATION. -->
<!--- PLEASE PUT AN 'X' in only **ONE** box -->
<!---
*********************************************************************************
-->
### Types of changes
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Enhancement (improves an existing feature and functionality)
- [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
### Feature/Enhancement Scale or Bug Severity
#### Feature/Enhancement Scale
- [ ] Major
- [x] Minor
#### Bug Severity
- [ ] BLOCKER
- [ ] Critical
- [ ] Major
- [ ] Minor
- [ ] Trivial
### Screenshots (if appropriate):
### How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to
-->
<!-- see how your change affects other areas of the code, etc. -->
<!-- Please read the
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md)
document -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
