The work for transitioning to MCP in OPNFV started late May 2017. Everything from the Fuel implementation was removed and MCP had to be build from scratch. Both Fuel and Armband projects had to fit into the OPNFV milestones. While the Fuel project is now driven by Mirantis, the Armband project is exclusevly driven by Enea and has to rely on the work provided by upstream.
MCP for Armband meant learning new tools, a whole new way of doing things and a better coordination with other projects in OPNFV; not only Fuel, but also testing projects . After two delays in the schedule we managed to catchup in time for the Euphrates release. There was a true community effort between Fuel and Armband projects to sync and help each other in order to be ready on time.
The drawback of this effort was that all the work focused on basic scenarios, thus delivering less features than in Danube release.
Achievements and future work
After the OPNFV ”Euphrates” release, Fuel@OPNFV is closer to become a project that supports both x86_64 and aarch64 architectures in the same repo. Many of the Armband patches were upstreamed in the Fuel project, and the two have now a common documentation. As an acknowledgment of the effort, three out of the four nominated team members – from both projects – won OPNFV Euphrates awards.
The plans for the future are to bring back into OPNFV the features supported by Fuel while continuing the aarch64 support for them.