In order to complete day-1 configuration for some NFs, we need to be able to perform NETCONF actions, which have their names and parameters defined in the YANG schema.
Upon initial investigation along with @steiler, we compiled a list of items a solution should consider and reason about:
- Are they only related to config?
- hook them to config
- have a separate Actions CRD
- For config related actions
- we might need pre- and post-commit actions
- what about intermediate actions? Do such things exist?
- could these be chopped into pieces such that we have pre-/post-actions again
- what about re-applying the intent because the target is re-added to the dataserver
- are there actions that must only be called once on initial deployment of the intent?
- when to call stuff relative to the transaction?
- e.g. is it called after the config is deployed network wide or per device after the config is applied?
- how to revert in case of transaction revert
These can and will likely be expanded on as more requirements and use cases are discovered.
In order to complete day-1 configuration for some NFs, we need to be able to perform NETCONF actions, which have their names and parameters defined in the YANG schema.
Upon initial investigation along with @steiler, we compiled a list of items a solution should consider and reason about:
These can and will likely be expanded on as more requirements and use cases are discovered.