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 >.
Alon Saggie suggested an idea (#2109) · Oct 11, 2017 at 06:40 PM · appsApplicationpower managementorchestration
As a Blueprint designer, I'd like to control the power-on sequence of groups of Apps in my Blueprint, without having to change the Setup script to be able to do this, as some applications must be deployed before others (e.g. think of a DHCP server that has to be powered on before other VMs can get an IP - but other cases apply).
A solution I'd like to see implemented is to have a numeric attribute on each app ('PowerOnSequenceGroupId') and have the Setup script read the values of this attribute for all the Apps, then orderly power on the VMs based on their group ID (starting from 1, moving to 2, and so on).
I also want to be able to control the delay between the power on of different groups (it's not enough to just contriol the order - you need to make sure that the app is up and running and maybe some process is now running on the machine - maybe have a way to control the trigger that will tell the orchestration it's ok to move to the second group).
Maya Ber commented · Oct 14, 2017 at 02:55 PM
Hi Alon, in the past release we have invested in making the setup script cleaner and easier to modify, in order to make controlling the orchestration sequence simple but still keep it very flexible. It's definitely in our vision to make certain orchestration aspects (like defining the deployment order) even easier, optimally not requiring to make any orchestration modifications.
Please note that this idea is a duplicate of an existing idea (#629), and in order to keep the idea box I am tagging it as a duplicate.
Thanks!
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.
Show the last edited App on the top in manage > app templates when sorted by modified
App Installation to be able to download dependencies from repository (support for requirements.txt)
refresh app from template - indicate latest in blueprint and bulk
have a discovery mechanism for apps,have a discover feature to an app
App Management Page should include deployment path with filter
Make max user reservation value accessible via API
Allow editing attribute values of deployed apps in portal