Idea ID: 2877317

Use Application Name instead of Port from VTS

Status: Accepted

Backlog item for a future release.

See status update history

Currently, we're using port numbers to identify and route traffic to our various applications. While this approach has served us well, it can become cumbersome to manage, especially as we scale and add more services.

To address this, I suggest that we transition from using port numbers to using application names as identifiers. Instead of specifying port numbers, we can use clear and intuitive application names to access our services. This change not only streamlines our configuration but also makes it easier for team members to work with our services.

Here's how it would work:

  • Each application will have a unique name.
  • We'll maintain a mapping of these application names to their corresponding ports and internal service addresses.
  • Nginx, our web server, will be configured to route traffic to the appropriate service based on the provided application name.

This transition will simplify our server configuration and improve the accessibility of our services, making it easier for team members to interact with different applications.

Tags:

Parents
  • Hello guys
    This is a very valid enhancement.
    We see two ways to implement this capability.

    1. The VTS server should work in the Nginx (port forwarding) way.
      This method would still ensure that you the customer would still be required to do the Application-PortNumber mapping in the Reverse Proxy, and of cause, replace the port number with application name in all the scripts.
    2. An alternative is to keep the server intact as it is , and you can run the server in either the normal or the Nginx way. We could look to provide a new VTS connection API (or update the current one) and what you would need to do is to provide the mapping file and replace the port number with application name in all the scripts.

     So having discussed this with the team we have decided to accept option 1 and have added a code change feature into our backlog for a future release.
    Thanks David

     

  • @David McLeish,

    Can you confirm that with option 1 it is also possible to use an more complex URL? We have a proxy server to access VTS UI in AWS and use:
    https://server/VTS-eu and https://server/VTS-us to access different VTS servers in AWS. Having this access path also for the VTS API (lrvts_connect_ex) would be great. Supporting the format https://server/VTS-us/APPLICATION

    I think that this is more than your option 1 proposal, because you want to give VTS nginx capabilities, but at least I like support for access via a reverse proxy for both UI and API.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Comment
  • @David McLeish,

    Can you confirm that with option 1 it is also possible to use an more complex URL? We have a proxy server to access VTS UI in AWS and use:
    https://server/VTS-eu and https://server/VTS-us to access different VTS servers in AWS. Having this access path also for the VTS API (lrvts_connect_ex) would be great. Supporting the format https://server/VTS-us/APPLICATION

    I think that this is more than your option 1 proposal, because you want to give VTS nginx capabilities, but at least I like support for access via a reverse proxy for both UI and API.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Children
No Data