Principal Engineer, Ericsson Software Technology
CurrentONAP Policy Framework:I am working as Ericsson's lead in the ONAP Policy Framework, acting as an architect and lead developer with a team of developers from Ericsson who are working with teams from other project partners on the ONAP Policy Framework. Our major achievement has been in evolving the architecture of the ONAP Policy Framework so that it is model driven, modular, scalable and pluggable.see https://docs.onap.org/projects/onap-policy-parent/en/latest/architecture/architecture.htmlDay to day, we are working on delivering enhancements to the Policy Framework. Development is in Java, Javascript and other languages. The development process uses the usual agile methodology and toolchains (Eclipse/Maven/Jenkins/Confluence/Jira etc).Search for "Liam Fallon" at the link below to see my contribution history to ONAPhttps://lfanalytics.io/projects/lfn%2Fonap/dashboardI am an active member of the Control Loop subcommittee. I see this as a natural continuation of the research work I did in the Ericsson NM lab. I am leading the implementation of the TOSCA Defined Control Loop PoC being executed in the ONAP Guilin release, see:https://wiki.onap.org/display/DW/TOSCA+Defined+Control+Loop+PoC+in+ONAP+Rel+GI also take part in ONAP community initiatives such as contributing to improving the ONAP Release process and managing the Java checkstyle profile for ONAP.