OOM deployment results from today: Besides a minor issue that I worked around for now (https://gerrit.onap.org/r/#/c/29071/), I was able to start up DCAE via OOM on both Wind River lab and my own OpenStack with Designate (no proxy). On both environments, only DCAE and UUI failed health checks as follows:
------------------------------------------------------------------------------ Basic DCAE Health Check | FAIL | [ | cdap | | | | | 1c1c99c96bca47cfacd950932f89409b_cdap_app_cdap_app_tca | cdap_broker | config_binding_service | deployment_handler | inventory | platform_dockerhost | | component_dockerhost | 7911cc59914340d5b4c549ac599c5408_dcae-analytics-holmes-engine-management | cb08cc6e229e4c49b2b73f170b62685c_dcaegen2-collectors-ves | dd04a13962834b18ada0575c0e62b81b_dcae-analytics-holmes-rule-management | | cloudify_manager ] does not contain match for pattern 'service-change-handler'. ------------------------------------------------------------------------------ usecaseui-gui API Health Check | FAIL | 502 != 200 ------------------------------------------------------------------------------ DCAE health check failed even though all DCAE VMs started. UUI consistently fails health checks when deployed by OOM, even though it usually succeeds when deployed by heat. At this point I suspect both of these failures to be some sort of race conditions during startup, but we can get the project teams involved once we retry the deployments a few more times to observe the behavior. The above was deployed using the OOM amsterdam branch as of today. Thanks, Gary From: Alexis de Talhouët [mailto:[email protected]] Sent: Wednesday, January 24, 2018 8:48 AM To: onap-discuss <[email protected]>; Gary Wu <[email protected]> Subject: Re: [OpenLab] DNS Designate zone for simpledemo.onap.org Gary, all, Actually, digging and thinking about this, the solution that has been implemented in OOM to support DCAE will not work with a shared DNS Designate backend, e.g. if multiple ONAP instances are deployed, each one of them need its own DNS Designate. The reason for that is, to accommodate DCAE VM resolution of .simpledemo.onap.org<http://simpledemo.onap.org> hosts (aai, msb, sdc, policy), OOM creates a simpledemo.onap.org<http://simpledemo.onap.org>. zone in which it will create the A record and a bunch of CNAME, as it was done in the DNS VM. The thing is, that simpledemo.onap.org<http://simpledemo.onap.org> zone will have records pointing to a given instance of ONAP, and you cannot have multiple zones sharing the same zone. Which means, we need https://gerrit.onap.org/r/#/c/28347/ for Amsterdam ASAP so OOM can be used in the OpenLab. That patch basically instantiate a small OpenStack in OOM with only the support for keystone and designate. This way, no need to rely on infrastructure dns designate support. Alexis On Jan 24, 2018, at 11:19 AM, Alexis de Talhouët <[email protected]<mailto:[email protected]>> wrote: Greetings, I’m trying to add a DNS zone in the DNS Designate of OpenLab, but I’m getting the following failure: openstack zone create [email protected]<mailto:[email protected]> '--description=DNS zone bridging DCAE and OOM' --type=PRIMARY simpledemo.onap.org<http://simpledemo.onap.org/>. Unable to create zone because another tenant owns a subzone of the zone Can I get assistance with this? Thanks, Alexis
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
