Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
The OOM is moving to using Consul to provide health checks for all ONAP
components. This push adds deployment of a 3 node Consul Server cluster
and a single Consul agent to the 'OneClick' deployment.
As a first step, health check scripts for the A&AI microservices have
also been included. Support for additional ONAP components will follow.
Issue-ID: OOM-86
Change-Id: Ib63f3d8b1b745551c9ec55b6529d022b32006e9c
Signed-off-by: gfraboni <gino.fraboni@amdocs.com>
|
|
Portal container names now include a hyphen. K8s deployment
descriptors updated to point to new containers.
Change-Id: I7b6b08a9d707b1b9747c6f45de70df7392cfca8f
Issue-Id: OOM-310
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Replaced underscore with hypen. Underscores not supported in yaml.
Change-Id: I5b45708cc39aac346a03d4d25ed82ab4080bd608
Issue-Id: OOM-309
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
https://gerrit.onap.org/r/#/c/7773/ was not picked up
when the appc move to 1.1. was done in the OOM project.
Issue-ID: OOM-308
Change-Id: Ic2d6d89cce8d1076b7a4e1decf8665d760209a68
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
|
|
Issue-ID: OOM-307
Change-Id: Ic7261ae2bf34f5490b67daf01851aea1913bd585
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
This change to robot caused demo init stop working in OOM
as we were using tenantName to keystone auth.
https://gerrit.onap.org/r/#/c/11539/
This fixes the issue and requires a new parameter to
onap-parameters.yaml.
steps to workaround will be provided in the jira comments
Issue-ID: INT-149
Change-Id: I3dad07b24313a5bc6637b602a8c52835544155e8
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Added the initial deployment yamls for CLAMP and updated one-click
Issue-ID: OOM-12
Change-Id: I48c842d77bf95ad53dcff9ab28edf542b1cb4bf5
Signed-off-by: Dusan Rozman <dusan.rozman@amdocs.com>
|
|
|
|
Change-Id: Iaff7c8d58d913528c05a16302b5a1e18d7824dc1
Issue-Id: OOM-18
Signed-off-by: liangke <lokyse@163.com>
|
|
Issue-Id: OOM-113
Change-Id: I669e5e7f0298fc80ab472cd874e6384b24e72c7d
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
|
|
Deploying MSB first and kube2msb last will ensure
all the ONAP services can be registered to MSB.
Issue-Id: OOM-278
Change-Id: I3210f407c7b338b765117f8f2ba7a1d4920f3b32
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
The json format is not correct due to lacking of a comma.
Issue-Id: OOM-222
Change-Id: I5af614d02e8cddd96efa80d09d72dcf264756ae1
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Issue-Id: OOM-223
Change-Id: Ie1ad56e163bc00b91465e25359d272122ae8ebfd
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Change-Id: I0801156481c8306cc7599a27d50b981385968a70
Issue-Id: OOM-18
Signed-off-by: liangke <lokyse@163.com>
|
|
|
|
|
|
|
|
Change-Id: I12780f57f5f2070e5603d25a7fd6a78320220845
Issue-ID: OOM-277
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
Deployment of: Logstash + ElasticSearch + Kubana with all the configuration files- fix hostPath in PersistentVolume
Issue-ID:OOM-110
Change-Id: Id8e831667ebd99b501504f12be5b382422e1599b
Signed-off-by: itay <Itay.Hassid@Amdocs.Com>
|
|
|
|
|
|
Make sure time zones on the containers are in sync with the hosting machines
Change-Id: Ie22608bda63cbcdf564f73adcdd3e829afad05ca
Issue-ID: OOM-299
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
OOM deployment configuration for CLI.
Change-Id: I4b34c64be7fba5c3bcfbb35ea497b6e5abde8305
Issue-ID: CLI-41
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
|
|
was the cause of the robot failure for policy in oom
Issue-ID: OOM-297
Change-Id: Iabb24cc7a007ef852cde3ebe2cbb9226bb4153b3
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Signed-off-by: Ahmed Alabulrahman <ahmed.alabdulrahman@amdocs.com>
|
|
Deployment of: Logstash + ElasticSearch + Kubana with all the configuration files
Issue-ID:OOM-110
Change-Id: I1788485ccb283f0ec4dc8910479072a6cf034e5f
Signed-off-by: Itay Hassid <itay.hassid@amdocs.com>
|
|
Issue-Id: OOM-302
Change-Id: I16eb5dbd707609d27a100b9112965cf8d7a17879
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
This reverts commit 59ffd500ea34c201fbb3edc39e64655fa8381be0.
Tested locally and does not work. DmaaP fails to come up causing
many other pods to crash loop.
failed to start container "dmaap": Error response from daemon:
{"message":"invalid header field value "oci runtime error:
container_linux.go:247:starting container process caused
"process_linux.go:359: container init caused "rootfs_linux.go:53:
mounting "/var/lib/kubelet/pods/9ae222e0-98a9-11e7-badd-02cfc855c3b9
/volumes/kubernetes.io~secret/mykey" to rootfs "/var/lib/docker/aufs/mnt
/b92c56185f3371cb1f091679780d40797dd2c6124cd00cb8fe68da2b247363a8"
at "/var/lib/docker/aufs/mnt/.../appl/dmaapMR1/etc/keyfile" caused
"not a directory"""n""}
Issue-ID: OOM-293
Change-Id: I348ffa14718bd6e89e99f2859cf6612c10370559
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
|
|
Deploy multiple namespaces fails due to existing persistence volumes.
"persistent-volume "appc-db" already exists"
Need to change all persistent volume names to include namespace.
Change-Id: I40a3048bef14f813b133ea75e2f664f669183e82
Issue-ID: OOM-294
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
|
|
Issue-Id: OOM-229
Change-Id: I932d9f5bd902f5aa30b1f18a0a83435474f4ee46
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
|
|
|
|
This is the initial seed of the dcae gen 1 deployment specifications
using onap 1.1 component containers.
All containers come up, however, there are issues with some of the containers
that will be flushed out during integration.
Change-Id: I6b74262168ae54bb7859d81de1ade6b59d1c42b1
Issue-Id: OOM-176
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
changed location of used certs and keys files, updated deploy yamls and create/delete all
Issue-ID: OOM-293
Change-Id: I53766b7028d6b725bf381875105b196246ff2ee1
Signed-off-by: Keren Joseph <keren.joseph@amdocs.com>
|
|
|
|
Use domain name instead of IP, so a fixed cluster IP is not needed anymore.
Issue-Id: OOM-113
Change-Id: Idd0444d4a9ff9b366e73316a7c6f26ffcd5ff725
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
|
|
|
|
Improve error handling to createAll sh
Issue-ID: OOM-289
Change-Id: I325df5ee98aebb39f52676311fc05d7bb6fc5388
Signed-off-by: tzvika avni <tzvikaa@amdocs.com>
|
|
Issue-Id: OOM-234
Change-Id: Ie18c2744c60b08ec8cfd80804c99da20530f7f65
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
on master branch there were changes to portals vm_init script
and docker-compose process that needed to be ported to oom.
src of config are on master in portal/deliveries/
reverted the docker image name changes. upstream master
has introuced a "-" between apps, db and wms. these images
were cauing NPEs during portal spring boot so went back to original
image names until further notice.
Issue-ID: OOM-276
Change-Id: I708628f4b375325f2f2b753d1a374699b763098a
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Change-Id: I36b65c1124232646b257cf9d91ad2f7758023473
Issue-Id: OOM-260
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Issue-Id: OOM-113
Change-Id: I9282869fd5d48e9eb48540f92fe46692e1f27835
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Issue-Id: OOM-113
Change-Id: I41e6f72337a15c1d07b444b09171204d8eb378ec
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|