Tommy,Thanks a lot for your information. For the first question, I'll dive into
the codes tomorrow cuz I have no computer in hand for now to do this. For the
3rd question, what if we want to get the external ip and port of our micro
service itself? We have to register ourselves to the MSB using those type of
information. Can we achieve this by declaring ourselves in the "services"
part?Regards,Guangrong
原始邮件
发件人:CARPENTER,TOMMYJ(TOMMYJ)
收件人:JI, LUSHENG (LUSHENG)
抄送人:付光荣10144542HWANG, MICHAEL(MICHAEL)onap-discuss@lists.onap.org
日期:2017-08-29 21:22:08
主题:Re: Questions on DCAE APIs
I have answered what I could inline but Mike has clarify the second:
Q: Is the complete entry point information of the config binding service
included in the ENV variable `CONFIG_BINDING_SERVICE` so that we could use the
value of this variable to access the config binding service?
Right now we do not have Consul’s DNS in the installation yet, so no.
Currently the name CONFIG_BINDING_SERVICE just points to the string
“config_binding_service”, which is the name that the CBS is registered in in
Consul. You will need to look that up in Consul first via Consul’s service
discovery layer. There is a CBS client library for python here that you can
look at to understand (or use if your code is Python):
https://gerrit.onap.org/r/gitweb?p=dcaegen2/utils.gita=treef=python-cbs-docker-clienth=6f579cecb39786d219d16a9cbacdc0d0e691d1d5hb=62fd5bed6a6f8ff8c6b159e38d7462edda0cc3b0
Q: What if we want to expose more than one ENV(not limited to the `port` only)
variables using the EXPOSE instruction? Is that supported?
I think you can do this but Mike has to clarify.
-----------------------------------------------------------------------------------------------------------------------
API Doc: service-discovery.md
Q: There's no detailed specification on service discovery. Do I miss it or is
it not provided yet? If it's not provided, when will that be uploaded to the
gerrit repo? This interface is quite crutial for us.
If you use the CBS, it handles this for you.
Essentially you will describe your expected interfaces via the “streams” and
“services” part of the component spec. That should be very detailed in the
documentation. After you do this, when you pull from the CBS, the IP:Ports will
be automatically given to you as a value under “Config_key” (see documentation
about “config_key”).
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
