<div dir="ltr"><div style="font-family:monospace,monospace" class="gmail_default">Dear colleagues,<br><br>Newton cycle is getting to its end and it is time to look at what we've<br>managed to achieve by the moment.<br><br>* Improved task based deployment engine (memory efficiency, code<br>Â structure, graph sequences, noop run).<br>* Re-implemented OS provisioning as a graph. Now it is one of the graphs in<br>Â the default deployment graph sequence.<br>* Improved graph API and UX. Now it is possible to upload/download<br>Â custom graphs, run particular graphs, see per-task deployment<br>Â progress.<br>* Aligned the functionality of the new version of fuelclient with the<br>Â old one. Now all subcommands are available in `fuel2` and we are ready<br>Â to deprecate old `fuel` command.<br>* We are on our way to get rid of ISO. (ISOless BVT is ready, review<br>Â jobs are in progress).<br>* Improved LCM UX including IaC (using git repository as a source for<br>Â cluster configuration).<br>* We begun implementing cluster upgrade procedure as a graph. In the<br>Â future in-place OpenStack cluster upgrades will be a native part Fuel<br>Â functionality.<br>* We also put some efforts to research container based deployment<br>Â possibilities (K8s and Docker). We introduced a bunch of<br>Â experimental repositories (fuel-ccp-*) where the team is now working<br>Â on CI/CD like UX for containerized OpenStack deployment.<br><br>There are also many things that we were planning but didn't manage<br>to do. I'm not going to nominate myself as a PTL for Ocata cycle, but I'll<br>continue to contribute to Fuel to make it a perfect deployment<br>tool and I'm looking forward for other Fuel team members to run for PTL role.<br><br></div><div style="font-family:monospace,monospace" class="gmail_default">Thanks.<br></div><div style="font-family:monospace,monospace" class="gmail_default"><br><br clear="all"></div><div><div class="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
</div>