-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-
None
-
OOM Sprint 7
- add nginx container to reverse proxy hostname coming from
DCAE world to OOM world. - create DNS zone in Designate for simpledemo.onap.org. to point to the
K8S hosts where dcaegen2 service is running. - add heat stack to deploy DCAE
- update SDC configuration file to dynamically inject the UEB servers
as those are in reality the k8s nodes ip addresses, as the dmaap
service port is exposed by the dcaegen2 service. This is done because
the service-change-handler container deployed by DCAE is getting the
UEB servers IP list from SDC itself, hence to enable resolution in the
DCAE VM, the IP has to be reachable. (Hence this config assume DCAE VMs
can route to K8S hosts). Previous config was using
dmaap.onap-message-router for UEB servers host, but this is not
resolvable by any DNS. - add knob to deploy DCAE or not
- add DCAE related parameters in onap-parameters.yaml (initial config)
- fix DCAE healthcheck
- add support to keystone v2.0 and v3
- fix vm_properties robot file
- blocks
-
LOG-48 Logging Configuration - DCAEGEN2
- Closed
-
DCAEGEN2-1067 Deploying DCAEGEN2 late in a sequenced deployment will cause the secondary cloudify orchestration pods DEP* to fail
- Closed
-
DCAEGEN2-1068 DCAEGEN2 failed redeployment leaves cloudify orchestrated dev-dcae namespace pods up
- Closed
-
OOM-1089 DCAE pods are not getting purged
- Closed
- is blocked by
-
OOM-424 DCAE installation is not possible today
- Closed
- relates to
-
DOC-245 Review of DCAEGEN2 docs - using DCEA cloudify-manager to orchestrate CDAP
- Closed
-
INT-340 Create a minimal configuration
- Closed
-
INT-346 Minimal HEAT deployment for vFW (with/without closed-loop)
- Closed
-
LOG-167 get DCAEGEN2/designate running on OOM-HEAT bridge - for closed-loop logging
- Closed
-
DCAEGEN2-300 DCAE controller error with neutron_plugin env substitutions in Cloudify centos_vm blueprint
- Closed
- links to