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 >.
TSI Support suggested an idea (#5279) · Oct 28, 2020 at 08:47 PM · setupmanagementappsresources
We frequently need the ability to control/sequence the startup of resources and (notably) apps into different launch groups, which upon setup will deploy, provision, and perform config management based upon their assigned order.
In effect, the entire current setup routine would run start to finish for each group, then move to the next group, with an assignable delay period before the next group starts.
This is often required when more launching more complex scenarios that involve servers that must startup (and often be provisioned) before clients come online and attempt to join the domain or interact with other devices. It's also used to control hypervisor load when starting large environments.
A minimum of five startup groups is desired.
Alona Getzler commented · Feb 01, 2021 at 10:00 PM
Hi, thank you for posting. It is possible to customize your setup script to deploy in such a cascading manner. As a reference see the "3 tier applciation" example in this article. You can also add custom attribute to identify the launch group of each app.
TSI Support commented · Feb 03, 2021 at 02:10 PM
Hi Alona, we are currently using a custom startup script to address this issue, but are encountering more and more customers with large environments that need this capability, hence the request for official product inclusion.
The startup script solution works passably for staggered startup where where each orchestration step runs serially (all provisioning groups, then all connectivity groups, then all configuration groups), but becomes much more complex when each group needs to run through the complete deployment process. For example, group one performs provisioning, then connectivity, then configuration and fully deploys, then group two begins from scratch, then group three, etc.
We worked extensively with Dan and Leeor on this issue and confirmed that OOTB functionality would be a worthwhile inclusion request for the product.
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.
More granular control for 'Admin Only' resources
App Dependencies and Deployment Order
App Management Page should include deployment path with filter
Prompt for updated apps in the blueprint
Add python support to Custom Script App Config Method
Improvement to building resources in blueprints
have the option to run some of the same setup script optionally in a different blueprints
Cloudshell portal: ability to copy the name of an app/resource directly from the diagram