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.
Kimo Saper suggested an idea (#3759) · Jun 27, 2018 at 05:14 PM · cloudshellstandard2g shell
CloudShell could use a Shell Standard for NAS. Not sure if there should be separate shells for FibreChannel vs. IP, or if it can be handled by 'Cards'. Proposed below is a basic structure based on defining the NAS type by cards (key attribute noted in '()' ).
NAS - Chassis (Host ID) - Disk (Zone ID) - Disk Array/Storage Group (zone ID) - Disk (zone ID) - Port, Ethernet - Port, FibreChannel (WWN ID) - Card (Host ID) - Disk - Disk Array/Storage Group - Disk - Port, Ethernet - Port, FibreChannel
Gal Cohen commented · Jul 12, 2018 at 08:29 AM
Hi,
Thank you for raising this idea.
We are planing to release in the near future a cloudshell storage standard which should cover the above.
Thanks,
Gal.
Kimo Saper commented · May 21, 2020 at 10:47 PM
Updates here? Almost 2 years later still 'planned'??
Extend your CloudShell capabilities by creating your own Shells. Share your knowledge with the world and be part of our growing community
Help us make things better. Share your great idea or vote for other people's.
Shell Standard and Autoload Need to Support Breakout Cables
Standard Child Component Type: Disk
Need a shell standard for a mobile device (phoe, tables,etc)
Add an option to specify a file-type environment global input
Alias Name for resource that is displayed in resource icon
Enable one click Reservations timeline check from within Environment details
Permitted Users on reservations that exceed their current permissions
CloudShell GUI usability needs to be improved for batch actions
Ability to pop out and resize Instructions Page on cloudshell portal