Hi, Some of the ONAP components will support clustering at the end of the Beijing release but the only working example that you could try now is described here: https://wiki.onap.org/display/DW/SDN-C+Clustering+on+Kubernetes
Cheers, Roger From: <[email protected]> on behalf of "[email protected]" <[email protected]> Date: Tuesday, March 13, 2018 at 10:30 AM To: "[email protected]" <[email protected]> Subject: [onap-discuss] OON ONAP SDNC in Kubernetes Hi, I am running an Amsterdam instance running on OOM Kubernetes 64 GB VM. I tried adding another VM to the Cluster, and Rancher now sees 2 nodes. I scaled SDNC to 2, and Rancher deployed the 2nd replica on the 2nd node. I deleted the 2nd node from Openstack, and Rancher detected that the node was disconnected. However kubernetes still show the 2nd node is still running, and that the 2nd SDNC replica pod is running on 2nd node. I waited to see if there’s a timeout until K8S detects and redeploys the pod, without success. Is this the correct way to perform scaling for ONAP components under K8S ? Is multi-node installation supported by OOM ONAP on K8S ? Thanks. Abdelmuhaimen Seaudi Orange Labs Egypt Email: [email protected]<mailto:[email protected]> Mobile: +2012 84644 733 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. 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
