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.
Jim Pfleger suggested an idea (#1719) · Jul 05, 2017 at 04:23 PM · ciscoNetworkingdriver
As discussed in this forum post, some Cisco devices are configured as an active-active pair, requiring that they be configured in a different way from standalone devices. To get configuration changes made on one member of a pair to propagate automatically to the other member, configuration mode must be initiated with the `config sync` command instead of the usual `config terminal` command.
We would like the capability to designate devices as being part of a pair. When configuring either member of the pair, CloudShell would default to using `config sync` in place of `config terminal` wherever the latter would normally be used. Additionally, we would like the option to run certain commands with `config terminal` as there are some commands that should only be run one member of the pair (e.g. setting IP addresses).
Dan Michlin commented · Aug 03, 2017 at 08:34 AM
Hi Jim, Currently this capability isn't planned in our roadmap , it requires a considerable effort in order to support it with the product, If this is required by many we will consider it. Looking forward for the votes
massoud.sobhani commented · Aug 15, 2017 at 04:25 PM
Jim's request makes a lot of sense. This feature is definitely needed.
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.
provide cloudshell version in driver command context
Run L1 driver from the execution server
API call to get "Estimated setup duration" value from a Blueprint's Properties
Ability to write a python topology driver instead of scripts or authoring
provide dev helpers to assist with debugging resource drivers
Vlan service names should retain the name they got before being "resolved"
Change driver, setup and teardown by regular users
Having access to old(er) versions of shells/drivers/scripts
netwroking: add an attribute to indicate a name of a connected cloud provider