Hi,
It’s been quite some time we provided an update regarding XCI to the OPNFV
community so here it is.
Infra/CICD Improvements/Implementations:
* CI Evolution:
* We are activating different phases in XCI pipelines. Currently verify,
post-merge, and daily are activated.
* We are gradually increasing the bar for promotion and will be
activating Functest Smoke and Yardstick on different phases.
* Scenarios owned by projects:
* Scenarios are developed in project repos who own them and they get
plugged into XCI.
* When a patch comes in to the project repo where the scenario is
located, XCI starts the deployment and testing of that scenario and provides
feedback directly on the patch.
* Ability to Override Versions:
* Projects have ability to override versions of upstream components
depending on their needs.
* This makes it possible for projects to use different versions than
what’s set within XCI by default. (XCI is constantly bumping to later versions)
* Full Isolation from Host:
* XCI leaves nearly nothing XCI-specific on the host system and all the
deployment and test activities are driven from a VM located on jumphost.
* This enables reproducibility and predictability of CI and also limits
the potential issues that could be caused due to the leftovers on hosts systems.
* Sandbox users will benefit from this greatly since their machines will
not be heavily impacted by the use of the sandbox so they can use the same
machine for other purposes.
* Being Agnostic to host OS:
* Thanks to the isolation summarized above, the OS of the jumphost
doesn’t matter since the user can decide what OS to provision the target nodes
with a single environment variable.
* PDF, IDF:
* PDF and IDF are natively supported.
* Dynamic CI:
* With the help of PDF, IDF, isolation from host and being OS agnostic,
XCI will be ready to demonstrate the concepts of dynamic CI when the baremetal
work is concluded.
* Baremetal:
* Baremetal work is full in progress and it will be available soon.
Versions:
* OpenStack:
* Rocky
* XCI brought in OpenStack Rocky same day as OpenStack released Rocky.
* OpenDaylight:
* Oxygen
* Will move to Fluorine soon.
* Kubernetes:
* v1.10.4
* Will gradually move to the tip of master in collaboration with CNCF
Cross Cloud CI Team.
* OSM:
* v4.0.1
* Collaboration with OSM community has started to move to latest on
master.
* ONAP:
* Initial integration using Beijing in collaboration with Orange by
reusing/adapting Ansible role is in progress.
* Will move to Casablanca and then to master once the initial
integration is concluded.
Scenario/Feature Support:
* OpenStack:
* Integrated: os-nosdn-nofeature, os-odl-nofeature, os-odl-sfc,
os-odl-bgpvpn, os-nosdn-osm
* WIP: os-odl-sfc_osm
* TBD: os-nosdn-vmha, blazar, congress
* K8S:
* Integrated: k8-calico-nofeature, k8-canal-nofeature,
k8-contiv-nofeature, k8-flannel-nofeature, k8-nosdn-istio, k8-nosdn-nofeature
* WIP: k8-calico-onap
/Fatih
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21905):
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21905
Mute This Topic: https://lists.opnfv.org/mt/25138111/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
