I can speak to the SDN-C work as I have tested it out when it was being done (This already might be known information but here it is anyways…)
The way the replica set’s DNS resolution was done is through a k8s service called “sdnhost-cluster” https://gerrit.onap.org/r/#/c/25467/23/kubernetes/sdnc/templates/all-services.yaml Then any pod running in k8s should be able to reach any of the replicas using a well known host name suffixed by the replica number..like this: {"ip": "sdnc-0.sdnhost-cluster", "port": "8181"}, {"ip": "sdnc-1.sdnhost-cluster", "port": "8181"}, {"ip": "sdnc-2.sdnhost-cluster", "port": "8181"} Mandeep Khinda Software Development Open Network Division +1.613.595.5132 (office) [ocs-a] Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog network<http://blogs.amdocs.com/> – and follow us on Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, LinkedIn<http://www.linkedin.com/company/amdocs> and YouTube<http://www.youtube.com/amdocs>. From: <[email protected]> on behalf of Michael O'Brien <[email protected]> Date: Tuesday, February 13, 2018 at 10:32 AM To: "[email protected]" <[email protected]> Subject: [onap-discuss] [OOM] 20180214: Agenda proposal - weekly OOM meet - discuss AAI cassandra clustering PV on openstack issue Team, I have added a proposed agenda item to the OOM meeting To continue work with the AAI team to help resolve an openstack specific PV issue occurring during Cassandra scale out that is causing issues with DNS. We have been meeting a couple times separately, we will bring this working session into half the OOM meet tomorrow to get the opinion of DNS and PV experts and developers involved in the SDNC cluster POC – from the onap community and the larger OOM team. https://zoom.us/j/118908904 https://wiki.onap.org/display/DW/OOM+Meeting+Notes+-+2018-02-14 See video prep in the last comment on https://jira.onap.org/browse/OOM-591 https://jira.onap.org/browse/AAI-539 Thank you /michael This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
