Agenda of OSCAR Project Meeting on May 28, 2015
Stuart briefly reviewed the candidate architecture described at the kickoff meeting. The function of OSCAR as described in the proposal is to mediate between an abstract northbound API
and southbound interfaces to specific tools such as Cobbler and Puppet. The northbound API
would allow definition and lifecycle management of different OPNFV stacks.
The question arising now is whether this approach lines up with operational requirements of service providers, and if OPNFV as an organization actually wants to host a project that will create and maintain code rather than simply providing blueprints to upstream projects.
Activity in the BGS project identified and tested several installers, and it seems likely that other stacks will also have multiple installers (e.g. OpenContrail has a script method and a Cobbler/Puppet method).
Signing on for supporting multiple installers for multiple stacks seems like a tall order for the OSCAR project.
An idea that may be worth pursuing is for OSCAR to define an API
for stack lifecycle management which could be supported by installers as they are written, rather than building an implementation with a plugin for each installer/stack.
oscar_project/meeting20150528.txt · Last modified: 2015/05/28 19:38 by Stuart Mackie