Added sla-dashboard as custom entity #8
Conversation
| ./manage.py runserver $SOCKET & | ||
| echo $! > $PID_FILE | ||
| env: | ||
| SLA_MANAGER_URL: $brooklyn:formatString("http://%s:%s", component("sla-core").attributeWhenReady("host.address"), component("sla-core").attributeWhenReady("http.port")) |
There was a problem hiding this comment.
why are you waiting for this URL if you are not using it?
maybe better to use something like
launch.latch: $brooklyn:component("sla-core").attributeWhenReady("service.isUp")
There was a problem hiding this comment.
What url? SLA_MANAGER_URL? I do use it. But sth strange happens, because brooklyn tries to reassign it each minute.
There was a problem hiding this comment.
you mean SLA_MANAGER_URL is expected by your python app, even if not passed explicitly to manage.py runserver?
There was a problem hiding this comment.
SLA_MANAGER_URL points to slacore endpoint, and has a default value of http://localhost:8080/sla-service (suitable for developing purposes), and overridable with an env var (https://github.com/SeaCloudsEU/sla-dashboard/blob/d06337aea0684a0773f1b3397304b8246188d977/sladashboard/settings.py#L97).
@andreaturli : Could you take a look at it?
I'm mixing the installation process with the launch process, but I don't know how to do it better.