Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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>
|
|
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>
|
|
|
|
Issue-Id: OOM-260
Change-Id: I0c44a0b7087b0ce92e07d2e43f72f468645b6ebc
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Provide ability to deploy components in a different path via createAll.sh
Issue-ID: OOM-291
Change-Id: Ia5f0c5e16bf3f9edff6c457176b6f428603d9544
Signed-off-by: tzvika avni <tzvikaa@amdocs.com>
|
|
providing the option to add external helm values file to createAll sh
Issue-ID: OOM-267
Change-Id: Id2f4013113cd578c99c5e4a4a4943f9801bb88c1
Signed-off-by: tzvika avni <tzvikaa@amdocs.com>
|
|
Issue-Id: OOM-260
Change-Id: Icbf74279b10b62b7ef5a57956a40452165d7ec42
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Issue-Id: OOM-113
Change-Id: I9bab3903c4334c0587071eff077f1745bbd4460b
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
|
|
-it appears the variable substitution was not working
and the config map was empty causing the config pod to fail.
I was sure I tested this...alas :'(
Issue-ID: OOM-277
Change-Id: I439d2e0d12f74e76c2fb0a2d44da8aaa473035a7
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
|
|
|
|
To be able to run the vFW/vLB demos, these needed to be done
manually and it was a big mess.
With the power of helm we can now pass data into the config pod
and make some substitutions
Issue-ID: OOM-277
Change-Id: Ie167920fac7896661b81443aa460ce2e6f615187
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
|
|
- up verion containers to use 1.1
- pap and brmsgw report it is waiting for pap 9091 port to be open but pdp and pypdp reports pap 9091 port is open
- removed push-policies.sh from 1.1 due to comment in CR
- removed pypdp container from 1.1 due to comment in CR
- removed pypdp.conf from 1.1 due to comment in CR
- removed ip_addr.txt from 1.1 due to comment in CR
Change-Id: Ibb685ec603a59dba56aa9673044ae1923d993191
Issue-Id: OOM-249
Signed-off-by: Eric Au <kachun.au@amdocs.com>
|
|
|
|
|
|
|
|
On some kubernetes deployments there is a conflict when a volume in docker image
is mounted in kubernetes over NFS. files / directories created inside the container
are not visible inside / outside of the container.
Removing VOLUME declaration from the Dockerfile solve this problem.
Change-Id: I05081a21a64c08e7ad19403a80ad1195a5bd8cb4
Issue-ID: OOM-290
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
removed mounted keystone_interface file
removeed mounted keystone interface file and made required changes to
deployment yaml
Issue-ID: OOM-285
Change-Id: Ic1cf27bfba96433b4c3d8ad86794ca1ff3d9ea0a
Signed-off-by: Ahmed Alabulrahman <ahmed.alabdulrahman@amdocs.com>
|
|
This will add required default configuration for the DCAE Gen 1 v1.1
internal message router. The configuration data is for the internal
version of zookeeper, kafka and dmaap.
Unfortuantely this is a rather large set of data at the moment, as
the containers will not come up without it. As the motivation right
now is just to get DCAE Gen 1 working to support the vFW demo, the
concern around the amount of data will be addressed in a future
user story.
Issue-Id: OOM-176
Change-Id: I226706dfd737f878425a183ca46be95b3acb1dde
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
The nsPrefix value was being ignored when a second '--set' command was
added for nodePortPrefix.
Change-Id: Ib667265320d74eb11196c40d95a48bd35e691133
Issue-Id: OOM-283
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Issue-Id: OOM-260
Change-Id: I323e1be301d7788ea3250381ca0f3d4f767798c3
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
Addition of persistent volumes for all DBs including
persistence of policy mariadb (with initial configuration data)
Change-Id: I029e724c3f8bba7fe3599b0955a4a3d213c08163
Issue-ID: OOM-268
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
|
|
|
|
|