The document outlines the Cross Community CI (XCI) proposal aimed at improving integration and feedback in the Open Platform for NFV (OPNFV) project. It emphasizes the need for early integration, faster feedback, and better visibility through CI/CD practices, detailing components like Bifrost and OpenStack-Ansible. The workflow includes multiple Linux distributions and various deployment scenarios tailored to different resource specifications.

1. Cross Community CI (XCI)
Victor Morales
Senior Cloud Engineer

2. Agenda
• Problem statement
• CI/CD principles & practices
• Proposal
• XCI definition and goals
• Main Components
• Workflow
• Features

3. OPNFV - Problem statement
• Late integration – Takes months
for a feature/fix to be available
• Slow feedback – Takes months
to know if a feature/fix works
• Lack of visibility – Not easy to
see the current state
• Too fragmented – Many ways to
do the same thing

4. CI/CD Principles & Practices
• Fail fast, Fix fast
• Always have a working software
• Small and frequent commits
• Reduce the complexity
• Test early and often
• Avoid surprises

5. Proposal

6. Cross Community (XCI)
• It’s an additional OPNFV service that
enables
• Early integration – Works with master
• Faster and tailored feedback
• Reuse – Use of upstream tooling
• Better visibility.
• It aims to bring Continuous Delivery to
OPNFV
• Ensure composed platforms always work

7. Main components

8. Bifrost
• Standalone Ironic
• Tool for provisioning virtual and bare
metal machines
• Ansible based
• Supports multiple distros
• Ubuntu
• CentOS
• OpenSUSE

9. OpenStack-Ansible
• Tool for installing OpenStack
• Containerized OpenStack
services (LXC)
• Ansible based.
• Supports multiple distros
• Ubuntu
• CentOS

10. XCI Workflow
http://docs.opnfv.org/en/latest/submodules/releng-xci/docs/xci-user-guide.html#how-to-use

11. Features
• Multiple Linux Distributions Support
• Ubuntu
• CentOS (In progress)
• OpenSUSE

12. Features – part 2
• Multiple Scenarios
• Kubernetes without SDN Controller (k8-nosdn-nofeature)
• OpenStack without SDN Controller (os-nosdn-nofeature)
• OpenStack with OpenDaylight Controller (os-odl-nofeature)

13. Features – part 3
Flavor
Number of VM
Nodes
VM Specs Per
Node
Time Estimates
All in One (aio)
1 VM Node
controller &
compute
on single/same
node
1 compute node
vCPUs: 8
RAM: 12GB
Disk: 80GB
NICs: 1
Provisioning: 10
mins
Deployment: 90
mins
Total: 100 mins
Mini
3 VM Nodes
1 deployment
node
1 controller node
1 compute node
vCPUs: 6
RAM: 12GB
Disk: 80GB
NICs: 1
Provisioning: 12
mins
Deployment: 65
mins
Total: 77 mins
No HA
4 VM Nodes
1 deployment
node
1 controller node
2 compute nodes
vCPUs: 6
RAM: 12GB
Disk: 80GB
NICs: 1
Provisioning: 12
mins
Deployment: 70
mins
Total: 82 mins
HA
6 VM Nodes
1 deployment
node
3 controller
nodes
2 compute nodes
vCPUs: 6
RAM: 12GB
Disk: 80GB
NICs: 1
Provisioning: 15
mins
Deployment: 105
mins
Total: 120 mins

14. Additional information
#opnfv-pharos channel
Wednesday 15:00 CET weekly meetings
https://etherpad.opnfv.org/p/xci-meetings