Hi Alexis,
I think it would be better to clarify that: proxy the DNS Designate
requests is the enhanced feature by MultiCloud to federate services from
different underlying VIM instances. In ONAP Amsterdam release it has been
implemented to support both vanilla OpenStack Ocata (and Newton as well, not
tested yet) and Titanium Cloud, and more to come in future releases. I had
tested with vanilla OpenStack Ocata and it works well.
To utilize it , the consumer presuppose that the MultiCloud services
are ready and the VIM instances are registered. So for DCAEgen2 which has been
the actually consumer in ONAP Amsterdam release, the bootstrap VM did this part
, the VIM instance information (both underlying OpenStack and the proxied one
which exposes Designate services) are passed in by HEAT template/environment
file. I believe OOM can support this in similar way.
This federation can be designed/implemented in various way but why it
was designed/implemented is that MultiCloud do the federation and the
consumers will be transparent with regards who provides DNSaaS services.
BTW, I do think it will be valuable that OOM can offer the similar proxy to
DNS designate, I would like to share our experiences.
Best Regards,
Bin Yang, Solution Readiness Team, Wind River
Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189
Skype: yangbincs993
-----Original Message-----
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Friday, January 19, 2018 6:34 AM
To: onap-discuss
Subject: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with Multicloud
Titanium
Hi experts,
In the dcae_vm_init.sh script, we have the possibility to proxy the DNS
Designate requests to an OpenStack other than the one on which we spawn DCAE.
But this feature only allow to proxy to Multicloud Titanium cloud, it doesn’t
allow to proxy to an other plain OpenStack instance.
I was wondering whether a contribution to address this is Amsterdam would be
accepted, if yes, I can do it.
Basically, I’d like to leverage the dnaas_* config bits to establish a
connection to an OpenStack directly, instead of using Multi-cloud.
I would have a add a param to let the user choose whether the use Multicloud
Titanium or plain OpenStack.
Please, let me know what you think of this?
FYI, I tend to think we should be able to have DNS Designate running where ever
we want in the infra, as long as it’s provided. Moreover, we’re working on
providing it in OOM, so it’s not required in ppl infra.
Thanks,
Alexis
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
