These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
jauby suggested an idea (#2011) · Sep 14, 2017 at 09:39 PM · portalcloudshell
Right now with our dynamic environment, we put all of our resources on the root folder of Cloudshell Resource Manager so that when a user clicks +resource on the canvas, they immediately see all the devices that are in our dynamic pool of equipment. If we were to put the resources in a folder on the root, we would have to explain to all of our users that adding a resource to the canvas requires them to click the + resource button, locate the correct directory and then find a device that suits them. This approach is not as user friendly as just click +resource and see all available devices.
It would be much neater if you could set a domain's root resource folder the same way you set the domain topologies folder found on the domains page in CloudShell Resource Manager. Then we could put all of our resources in the folder of our choice to organize the Cloudshell Resource Manager better and provide a user friendly experience.
Thanks,
Joe
rguerrer commented · Sep 14, 2017 at 10:20 PM
To be able to set the root folder for each domain would be amazing. This is perfect for trouble shooting and organization in Cloudshell Manager.
Dan Michlin commented · Sep 24, 2017 at 11:13 AM
Hi, Thank you for posting this idea , we will consider it. looking forward for the votes
Kimo Saper commented · Sep 26, 2017 at 04:57 PM
The idea here is that from CloudShell, based on the Domain you're currently working in, the device list display (canvas, blueprint, inventory search) would reflect a different starting point in the directory tree, based on preferences set for that domain.
Ryan Guerrero commented · Mar 22, 2018 at 10:35 PM
Allow a domain to have a root resource folder. I created an idea box ticket some time ago on this. Issue is when user goes to add device to the canvas, they would have to drill down to the correct folder or use the search box. Would be nice to let them browse through the set root folder of resources for that domain so we don’t have to put all Dynamic domain resources in the root folder of Cloudshell Resource Manager
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Help us make things better. Share your great idea or vote for other people's.
API call to open (raise) the output window in the Web Portal
add the version/patch ID to the build number in the Cloudshell portal help
Make Resource Descriptions visible in CloudShell
Set of quali components informations published on cloudshell portal
Allow editing attribute values of deployed apps in portal
CloudShell Web Portal calendar view
Option for CloudShell to Kill and Rebuild Shell venvs