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 >.
Sadanand Hegde suggested an idea (#2078) · Oct 02, 2017 at 02:36 PM · l2 connectivitylayer 1
Customer wants to use L2 switch in conjunction with L1 in an environment in order to minimize the use of expensive L1. We probably have some solution for this, in specific use cases. This needs to be formalized
Thanks,
Sadanand
Alona Getzler commented · Oct 03, 2017 at 01:53 PM
Hi, thank you for posting this idea. Adding an official support to L1 and L2 combination fits our roadmap and we will consider it. It will be great if you can detail the specific use cases you have in mind as it will help us with evaluating the right solution for this. Looking forward to see the votes and comments.
Hi Alona,
The use case I came across is where one of the endpoints is connected to a L2 directly, the other endpoint is connected to a L2 switch through the L1 switch. In this case, user expects VLAN to be configured on both interfaces of L2 switch.
Test eqpt <- -> L1 <- -> L2 <--> DUT
Regards,
Sadanand
Paul Sherratt commented · Nov 19, 2021 at 07:27 PM
Hello,
We have the same use-case as above and would like to see this implemented too.
It would also be useful if a logical route connector would resolve both L1 and L2 paths, since using the visual connector for L2 paths (e.g. with P2P VLAN Default service) is awkward with abstract resources: unless port attributes are bound on the abstract resource, any available port may be resolved for a sandbox even if the port is not connected to a L2 switch and to add those port attributes, we may need to modify several shell drivers.
While we could work around the issue with the visual connector by developing a L2 driver which masquerades as a L1 shell, this would then not play well with deployed Apps which depend on the P2P VLAN service on the B-end if these are connected to another resource via L2.
Kind regards,
Paul
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.