Closed JonathanHancock0 closed 4 months ago
Verified working.
To operate you need:
appmodel
for the updated fsm.data.xml
. Update the chosen FSM
configuration in test-session.data.xml
in the RCApplication
from fsmConf-test
to fsmConf-prod
. drunc
with git merge develop
.drunc.json
in ~
with
{
"run_registry_configuration":{
"socket": "http://np04-srv-017.cern.ch:30015/",
"user": "fooUsr",
"password": "barPass"
},
"run_number_configuration":{
"socket": "http://np04-srv-017.cern.ch:30016/",
"user": "fooUsr",
"password": "barPass"
},
"elisa_configuration": {
"socket": "http://np04-srv-017.cern.ch:31900/",
"user": "fooUsr",
"password": "barPass"
}
}
That file contains the connection sockets to the elisa microservice running on the K8s cluster. For now chosen to leave this in JSON, will require someone who knows OKS
to create the structure in the test schema.
To get messages to Elisa run fsm
transitions as fsm <transition_command> elisa_post "<message>"
Drunc can now send messages to the elisa logbooks by sending HTTP requests to the microservice(s) running in the kubernetes cluster. The URL is currrently defined in .drunc, this may be changed later.