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 >.
Originally for Mellanox.
This is working demo that creates VMs using the OpenStack REST APIs. The OpenStack resource driver is the main part and could be extended. It is meant to be reusable.
Extensive debug logging in %programdata%\QualiSystems\qs_rest_json_log.txt. You can freely call Log at any time to write a message to this file.
All functions are wrappers around a single function, Query. There is no special order in which functions need to be called, and no initialization.
Auth is done behind the scenes and the token is managed automatically. This also automatically determines the tenant id. This mechanism needs to be slightly enhanced to handle the fact that the token can expire. If you get an error about an expired token, just restart Driver Builder or restart the TestShell server, whatever will reset the project variables.
In your own added functions you will probably call Query. Query gets the service IP and port from the resource and substitutes the tenant id wherever <tenant> occurs in the URL. You need to provide only the HTTP method, the part of the URL after http://host:port, and the JSON body if any. If you get a mysterious error, be sure to check the HTTP method (especially PUT vs. POST).
Setup:
Import models.xml
Build linux_pc driver, register it as "linux_pc", associate it with family Virtual Machine, model OpenStack VM.
Build the "openstack" driver, register it as "openstack_installation", associate it with family "OpenStack Installation", model "OpenStack Installation v2".
To add features to this driver, you will probably want to call the Query function in new ways. It takes JSON input and returns XML output.
Create a resource named "OpenStack":
Build the topology driver "Mellanox Deploy VM and FIO Topo" and register it.
Create a topology containing the "OpenStack" resource and set the topology driver.
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.
How to add link into test report
How to upload files to FTP server?
SMTP - Driver for sending email with cc, bcc, and multiple attachments
Getting driver/exe execution location at runtime
Ranorex Floating License integration with studio
Studio - Output window history length