Project Name: Fuel
PTL: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Brief description of project:
- The Fuel deployment toolchain will establish an OPNFV target system on a Pharos compliant lab infrastructure.
- The current definition of an OPNFV target system is OpenStack Stein combined with an SDN controller, such as OpenDaylight.
- The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
- Fuel also supports non-HA deployments, which deploys a single controller, one gateway node and a number of compute nodes.
- Fuel supports x86_64, aarch64 or mixed architecture clusters.
- Furthermore, Fuel is capable of deploying scenarios in a baremetal, virtual or hybrid fashion.
Project lifecycle status: Maintenance (active)
Last 12 months number of commits: 120
Last 12 months committer count: 3
Most recent release project participated: Iruya (9.0.0)
Link to most recent release plan: https://wiki.opnfv.org/display/SWREL/Fuel+Release+Plan+for+OPNFV+Iruya
Next 3 months development plans:
- Maintenance
- Openstack release upgrade
- ODL release upgrade
- VPP release upgrade
- DPDK release upgrade
- (optional, if time permits) Saltstack version release upgrade
- (optional, if time permits) obsolete python2 (currently used by Saltstack master/minions)
- (optional, if time permits) AArch64 (arm64) VPP integration and fixes
Any plans to engage with CNTT?: No
Current active committer list:
- Michael Polenchuk <mpolenchuk@mirantis.com>
- Alexandru Avadanii <Alexandru.Avadanii@enea.com>
- Cristina Pauna <Cristina.Pauna@enea.com>
CI/CD status:
- multiple daily Fuel installation + Functest + Yardstick + Dovetail installation cycles, on both virtual and baremetal status;
- currently 2 baremetal PODs available (lf-pod2 - x86_64, currently broken; arm-pod10 - mixed architecture with x86_64 controllers and aarch64 compute nodes, currently offline but will be back online soon);