-
Bug
-
Resolution: Won't Do
-
Medium
-
None
-
Casablanca Release
-
None
-
None
There are more problems with AAF configuration and one host only. Previous bug I assigned to AAF - https://jira.onap.org/browse/AAF-530
This time another bug was generated by OOM team:
AAF defined locator which is a proxy for all users to locate final destination of service we request. Each service may work on another machine in kubernetes cluster. It means is another host. The host is configurable in service config files. Previously configuration files of AAF was in OOM helm charts as resources. It was possible to manipulate them without touching docker images. Each service has defined host name same as kubernetes service.
Now all configuration files was moved to docker image and oom pass environment variables to scripts that configure the AAF files.
The problem is that the is only one variable for all services with host name (except locator):
Example:
"env": [
,
,
,
,
,
,
],
Default value works maybe for testing environment when AAAF is on single VM but it has nothing to do with kubernetes where it should equal service name:
"name": "AAF_REGISTER_AS", "value": "aaf-service"
"name": "AAF_REGISTER_AS", "value": "aaf-gui"
"name": "AAF_REGISTER_AS", "value": "aaf-hello"
"name": "AAF_REGISTER_AS", "value": "aaf-fs"
except:
"name": "AAF_LOCATOR_AS" "value": "aaf-locate"