Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ifc9c9bfe03dbc5b5f94e4c532d42b2c973748738
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
Issue-ID: OOM-654
|
|
With the support of DCAE added lately, some change was done
to accomadate the resolution of some ONAP service for DCAE.
Among other things, UEB configuration in SDC is now using
external resolution, no longer the internal K8S one. Hence
for deployement not deploying DCAEGEN2, we still have to deploy
the loadblancer service.
Change-Id: I93d0c01920755beed3eeb05d158530c05c255383
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
Issue-ID: OOM-608
|
|
And fix DNS Designate proxy setup
Change-Id: I46c265ba8f66f81503b8cdc8c0f90f9e5956da86
Issue-ID: OOM-608
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
- 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
Change-Id: I64ec6faf7b45b293bf7110e9e23e31798bf9b841
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
Issue-ID: OOM-508
|
|
Change-Id: Iac46cbae69404d17e1f4e59f85ed18fc7ecd01dd
Issue-ID: OOM-432
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Add option to disable any deployment by using conditions in helm
templates. Each deployment will get helm parameter - boolean flag
allowing to disable it. The flags can be listed in the custom
values.yaml file that can be passed to the createAll script with
'-v' command line option.
Change-Id: I32b795de46c72915c2201c94c23f4e061971bb56
Issue-ID: OOM-380
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
It needs to use single quotes to wrap YAML values otherwise
the bootstrap process will fail.
The sample file in the dcaegen2 ONAP project used single quotes
and when making the sample I just chose double quotes as preference.
Issue-ID: OOM-345
Change-Id: Ia9c0a2558bd15190f536cc45aa40568b623178ee
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
launching the dcaegen2 bootstrap container in OOM K8s.
-based on dcaegen2/deployments/bootstrap/README-docker.md
-requires an openstack private key pair file locally
-requires mining and updating a yaml configuration file
as per the comments in the sample file given.
-unfortunately, my attempts to bundle the secret and configmap
in the helm package didn't work out as they are external files
so I create them using the createAll.bash script.
Issue-ID: OOM-107
Change-Id: I221f60af66ea0f7e97ddd8b92819dce9aa6b5a81
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|