Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
Change-Id: I9c0905b5d2ef13219e0cf6369bb1321011270540
|
|
This issue trigged by lack of kernel module needed to run iptables.
Change-Id: I8e31024b0e524d766a10994d15b1acfa4e83fb33
Signed-off-by: jialv01 <Jianlin.Lv@arm.com>
|
|
Change-Id: Ic309e4bae5285309a3fe16a5338eb72c6a881926
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: Ib75a486fceef9feb35f8fd6eaad78b97d8e44550
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
|
|
Change-Id: Ie74c889ce0c8714f7e52beec9ace130350728472
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: I88f7b579a825ba7ad25da5074773e5668f0ef000
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: Ic59ce70bec89efd263a095e923409263d8ee94bc
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
|
|
Change-Id: If7ec8818486ec5044f28aa95b5b08f50438b6f1b
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Recompile MACCHIATObin kernel image meet the edge system requirements
and provid a script to facilitate the build of the kernel image.
Change-Id: I5edbaa880d49853c9ee769d38e80e1df05ab7133
Signed-off-by: Jianlin Lv <Jianlin.Lv@arm.com>
|
|
1. fix in containerd private registry
2. master node using docker and worker node without docker
3. rebase containerd to 1.2.2
Change-Id: Ide2a45ed892134269995b8d96aa76d5c3362c6f3
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: I86a037dcb83854471e9c59f22f899e0ba2f023b7
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: Ib43fa8d4b1494e0b48e295941af223647c161f92
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
|
|
Change-Id: Ia82ed5f71ad7fdd49bfc71614ebf0d52920de610
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
1. k8s 1.12.2, docker: 18.03
2. criproxy: 0.12.0, virtlet: v1.4.1
Change-Id: I826bad4407ef4d048f3307dface5683f7d9d10e6
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
|
|
Change-Id: Ifbe25c03de1c11144d093fe710b2a48c5c419b89
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Since Istio 1.0, a new traffic management API, a.k.a. v1alpha3, is being introduced.
And there are also some minor changes in the deployment and clean steps for bookinfo application.
Change-Id: I96c9eb552104dfdce15b4628b29c7cc72ac207b2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
After separately install the CRDs first, it may need a few seconds to wait for Kubernetes to register them.
Change-Id: Ifb66c9688c080a5230b0df9762fb4dd861beaf83
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Since Istio 1.0, there is an independent Istio’s Custom Resource Definitions manifest.
It is recommended to install Istio's CRD first before invoking the istio-demo.yaml to avoid error like:
unable to recognize "install/kubernetes/istio-demo.yaml": no matches for config.istio.io/, Kind=attributemanifest
unable to recognize "install/kubernetes/istio-demo.yaml": no matches for config.istio.io/, Kind=attributemanifest
in https://build.opnfv.org/ci/view/clover/job/clover-daily-deploy-master/210/consoleFull
Change-Id: I9c26458d713ea1e01cb5976e4203843569ba7db2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Add the deployment of Kubernetes VPP Vhostuser scenario with the
help of Compass installer on arm64 platform, which would enable
the containers and VPP vswitch communication with virtio-vhostuser
interface.
Change-Id: I84531dd3730f94a7910f2f5615a193420fdad73f
Signed-off-by: trevortao <trevor.tao@arm.com>
|
|
|
|
|
|
1. add ntp for kubeadm onap
2. support vagrant cross 2 hosts
3. add beijing branch
Change-Id: I50faf8448ddc0efa765b98fecd19c1d7a52bf3a3
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Deploy Multus, SRIOV, Vhostuser(VPP+DPDK) with CRD.
Change-Id: I787d5fd61c75f17d50fbaf8f86c08bdc44c557b8
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
Change-Id: I3d79c13fca011af83e5c9109319f8f4cc49b8b85
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: I9f3d755764a194068c2f3f128eb6d0861fcda555
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Some files don't exist in istio 0.8.0 version.
So it failed to deploy istio in CI.
what this patch do:
1. using istio-demo.yml instead of istio.yml to deploy istio
2. define the ingress gateway when running bookinfo sample
3. rename ingress to ingressgateway
Change-Id: I39ec39320d61e5af8282c6f50bad90240444bc79
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
Change-Id: Idbeda8b36d067a7bd27a8ef19184c5bb5a6daa04
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: Id464f064e9a7c4a55244c3cec4b3303a4ed0a889
Signed-off-by: Bin Lu <bin.lu@arm.com>
|
|
This PR has:
1. Snort VNF.
2. Documentation.
Change-Id: I5df23a1b8cdb65864aa8f432ce547d6cf5f27cde
Signed-off-by: Laura Sofia Enriquez <lsofia.enriquez@gmail.com>
|
|
Change-Id: I6145b406450b0846999223f1e4e6783eb06bb0a9
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
- disable user interactive when clean_bookinfo
- run sleep before status check to save ci varify time
Change-Id: I6072b85c3c941af30263101a3d4dca0537abf1fc
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
To enable auto sidecar injection on specific namespace,
you only need label the namespace with `istio-injection=enabled`, e.g.:
kubectl label namespace default istio-injection=enabled
For details please refer:
https://istio.io/docs/setup/kubernetes/sidecar-injection.html#automatic-sidecar-injection
Change-Id: I2059aa0be2ab3f4f942342850d286281c5f940d4
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
1. Services ports renamed.
2. Added label 'app' inside all the deployment's yamls.
. README.md added with configuration information.
JIRA: CLOVER-3
JIRA: CONTAINER-22
Change-Id: I4c58b9ad6b5e0e598ad6a152f58c8afad084a805
Signed-off-by: Laura Sofia Enriquez <lsofia.enriquez@gmail.com>
|
|
K8S version 1.9
Clearwater deployment from source code using k8s v1.9.
Tests added.
Change-Id: Ifde573768721871b441ecb06a60ac25c0519b73d
Signed-off-by: Laura Sofia Enriquez <lsofia.enriquez@gmail.com>
|
|
|
|
Custom chart to deploy Clearwater with k8s.
This patch depends of gerrit #50467
Change-Id: I5621909d768e6d91668aad9aae70869ae10acecf
JIRA: CONTAINER-22
Signed-off-by: Laura Sofia Enriquez <lsofia.enriquez@gmail.com>
|
|
1. fix kata container deployment failure issue
2. use package instead of source build
3. remove docker installation
4. upgrade to k8s 1.9
Change-Id: Ie7698fb0e6a3a459d42b17d998b21f2dcf3a7854
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: I3a2bf891d3910e395ea976c31454bd6556fc4a3a
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
vagrant 1.8 cannot download vagrant box
Change-Id: I07252a7e5dc11f084419a44dffc1262e981f2b74
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: I55fb7a536539a26c1800f9cf4da1e61749ee3bca
Signed-off-by: Bin Lu <bin.lu@arm.com>
|
|
Update istio installation, since upstream istio 0.5.0 is released.
Fetch istio latest version from github.com instead of hard code it.
Change-Id: If7aca736d631f74f9fdd6828a204895ec342b0ad
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
1. README file
2. Deployement scripts
Change-Id: I1f99ba77e803c8bbc5c40ae783b32ff0c7218375
Signed-off-by: trevortao <trevor.tao@arm.com>
|
|
1. README.rst: installation guide
2. Scenario1: Kubernetes_basic, a basic Kubernetes cluster
with 2 nodes and Flannel CNI plugin, including the
deployment scripts, and an example use case
We may add more Kubernetes scenarios in the future
Change-Id: I3a0189533fdf99f0a80fd76c9e6cf96ff4a7e9f0
Signed-off-by: trevortao <trevor.tao@arm.com>
|
|
Change-Id: I36903535289c51346deea49791fd4a0d6e223a18
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Based on k8s 1.9 (kubeadm_basic) installation, adding
the istio 0.4 installation and simple validation.
Change-Id: Iee2c71974fb2b33df0f9342e0bfd9e96e4dab8f5
Signed-off-by: Yapeng Wu <yapengwu@gmail.com>
|