The _get_service_id function in Orchestrator class queries keystone for a service id, calling the KeystoneUtils.get_service_id funcion with the same IP address as the orchestrator itself (self.ip). It also hard-codes the port 5001:
|
service_id = KeystoneUtils.get_service_id(admin_domain_user, |
|
admin_domain_password, |
|
service_name, |
|
ip=self.ip, |
|
port=5001) |
This doesn't work in environments where the orchestrator and keystone are in separate hosts or pods (like kubernetes), with different service names.
Maybe the Orchestrator class constructor should accept a couple of optional parameters, such as keystone_host, keystone_port, that could default to the same IP as the orchestrator itself and port 5001.
The _get_service_id function in Orchestrator class queries keystone for a service id, calling the
KeystoneUtils.get_service_idfuncion with the same IP address as the orchestrator itself (self.ip). It also hard-codes the port 5001:iotqatools/iotqatools/orchestator_utils.py
Lines 109 to 113 in 026ec1a
This doesn't work in environments where the orchestrator and keystone are in separate hosts or pods (like kubernetes), with different service names.
Maybe the Orchestrator class constructor should accept a couple of optional parameters, such as
keystone_host,keystone_port, that could default to the same IP as the orchestrator itself and port 5001.