Despite being very specific env variables, in the past we applied an additional mechanism to calculate those values based on OXPO_ID, SDXLC_URLS, OXPO_NAMES and OXPO_URLS. This approach, although apparently useful to help on the docker compose file, leads to high coupling between fully independent OXPs: now one OXP instance has to be aware of all others. In my opinion, the benefit of having this instantiation mechanism is not worthy.
Hi,
Currently, the kytos-sdx-topology Napp utilizes a few environment variables to setup OXP specific information, such as:
Despite being very specific env variables, in the past we applied an additional mechanism to calculate those values based on OXPO_ID, SDXLC_URLS, OXPO_NAMES and OXPO_URLS. This approach, although apparently useful to help on the docker compose file, leads to high coupling between fully independent OXPs: now one OXP instance has to be aware of all others. In my opinion, the benefit of having this instantiation mechanism is not worthy.