The Click-driven platform has been one of the most popular vnf platforms that allow flexible composition of packet-processing functionalities. The key strength of Click is its inherent extensibility for functional components: a new feature can be easily implemented by module integration. While Click’s flexible design has satisfied many demands for rapid prototyping, its internal architecture has not caught up with the potential software upgrade.
The packet-processing functionalities are out-of-work during upgrade. This will bring several insufficiencies e.g. unable to quickly recover from downtime.
With no mechanism to reconstruct lost states for network elements, stateful functionalities are unable to correctly handle packets after upgrade, leading to service disruption.
Development of new modules requires intimate knowledge of complex library implementation, let alone correctly deal with states. It is frustrating that the visibility of current upgrade is pretty poor and the learning curve is rather steep.
CLICK-UP, which is the effort towards software upgrades of Click-driven stateful network elements.
The module integration scheme of service context aware in CLICK-UP.
The functionality-neutral modules won't be shipped with redundantly.
The state safe scheme of CLICK-UP. A state synchronization scheme
which enforcedly integrated into modules.
The lightweight runtime library of CLICK-UP. In order to clarify service semantics, simplifying tedious orchestration and unifying api.
The frontend dashboard of CLICK-UP. Operators can interact with the GUI and conduct upgrade intends.