Hi, There should be option to choose which service registration /health check mechanism to use per deployment. e.g. for K8s there is built in service registration/health checks which already been used by the current code base.
Thanks, Avi, From: [email protected] [mailto:[email protected]] On Behalf Of NG, JOHN Sent: Tuesday, July 25, 2017 2:05 AM To: [email protected]; LUCAS, JACK <[email protected]>; HU, JUN NICOLAS <[email protected]>; BENNETT, RICH <[email protected]>; [email protected]; TORAB, HABIB M <[email protected]>; Roger Maitland <[email protected]>; MURRAY, JOHN <[email protected]>; [email protected]; RATH, CHRISTOPHER A <[email protected]>; GAULD, ANDREW G <[email protected]> Cc: [email protected] Subject: Re: [onap-discuss] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction Hi Huabing, I am not sure whether this topic has been discussed yet. We have an alternative proposal and added Slide 6 on the ppt file you uploaded on the MSB page. Please review and share your thoughts. Our proposal is to merge MSB and OOM. We agree that there should be a common software framework and implementation of the service registration and service discovery functions. We agree that there should be a shared Consul instance to support the registration/discovery functions. We want to avoid any potential collisions where multiple parties register services with the same names/URIs – so we might need to work out rules (name spaces) to prevent them. One question we have is whether there is a use case that shows MSB operating outside of OOM for microservices/service endpoints? We could not think of any and so recommend that merging MSB and OOM be considered. We see that microservices and ONAP components being deployed and managed by OOM in a common process: 1. OOM (Cloudify) creates virtualized infrastructure and container/kubernetes cluster via TOSCA based blueprints 2. OOM (Cloudify) triggers (via kubernetes) the dockerized image (microservice or ONAP component module) to be created 3. OOM (Registry) listens for container creation in the pod and registers the new container 4. OOM (Discovery) updates inventory database and begins to health check the new container (microservice or ONAP module) 5. OOM (Discovery) updates health status to Internal/External Gateways 6. OOM (Gateways) route service requests to healthy service endpoints 7. OOM (Cloudify) performs recovery, healing, scale actions based on health status Please provide feedback and we would be happy to discuss. John ------------------------------------------------------- John Ng AT&T Labs – D2 Architecture 200 Laurel Ave, D5-3D16 Middletown, NJ 07748 +1 732 420 3742 +1 732 310 3253 (mobile) [email protected]<mailto:[email protected]> ------------------------------------------------------- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Friday, July 21, 2017 2:33 AM To: LUCAS, JACK <[email protected]<mailto:[email protected]>>; HU, JUN NICOLAS <[email protected]<mailto:[email protected]>>; BENNETT, RICH <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; TORAB, HABIB M <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; MURRAY, JOHN <[email protected]<mailto:[email protected]>>; NG, JOHN <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction Hi there, Will you be able to attend this topic: OOM & MSB Interaction? I would appreciate it if both OOM team and the AT&T cloudify proposal folks could join to discuss it. https://wiki.onap.org/pages/viewpage.action?pageId=8232264<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D8232264&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=5LKtWT5wddsBjHf0brinYQ&m=eiSr4Okc2E51NbwnGRhI8377nWKXQ9xU3K-TWIdEFTQ&s=oPe9m6IvYhtrTOT1MCZzrQplzp6t2LsjQAsuyiVzc3o&e=> Thanks, Huabing 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
