The document outlines the agenda for a meeting led by Victor Morales, focusing on the XCI project's goals, components, and CI/CD practices aimed at improving feature integration and feedback speed in OPNFV. Key components discussed include Bifrost and OpenStack-Ansible for provisioning and installation of cloud services, along with various scenario features supporting multiple Linux distributions. The proposal emphasizes continuous delivery, visibility, and reusability of upstream tooling to enhance platform reliability.

1. Validating latest changes with XCI
Victor Morales
Senior Cloud Engineer

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

6. 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

7. 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

8. Proposal

9. 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

10. Main components

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

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

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

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

15. 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)

16. Features – part 3
Flavor
Number of VM
Nodes
VM Specs Per
Node
Time Estimates
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

17. Additional information
#opnfv-pharos channel
Wednesday 15:00 CET weekly meetings
https://etherpad.opnfv.org/p/xci-meetings
https://docs.opnfv.org/en/latest/infrastructure/xci.html