This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
oscar_project:meeting20150528 [2015/05/28 19:28] Stuart Mackie created |
oscar_project:meeting20150528 [2015/05/28 19:38] (current) Stuart Mackie |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Agenda of OSCAR Project Meeting on April 03, 2015 ==== | + | ==== Agenda of OSCAR Project Meeting on May 28, 2015 ==== |
* Roll call | * Roll call | ||
Line 13: | Line 13: | ||
**Minutes** | **Minutes** | ||
- | * Stuart briefly reviewed the candidate architecture described at the kickoff meeting. The function of OSCAR was to mediate between an abstract API northbound, which would allow definition and lifecycle management of different OPNFV stacks, and southbound interfaces to specific tools such as Cobbler and Puppet. 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. | + | * 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). | * 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. | * Signing on for supporting multiple installers for multiple stacks seems like a tall order for the OSCAR project. | ||
Line 22: | Line 23: | ||
* Solicit feedback from the wider OPNFV team on the approach of having OSCAR essentially change into an API definition project | * Solicit feedback from the wider OPNFV team on the approach of having OSCAR essentially change into an API definition project | ||
* Reduce the frequency of calls to bi-weekly or monthly while OSCAR is in its current contemplative stage. | * Reduce the frequency of calls to bi-weekly or monthly while OSCAR is in its current contemplative stage. | ||
+ | * Update the meeting page to have the correct info. | ||