Date and Time
: 6:00am PDT / UTC 13:00, Thursday July 23, 2015Convener
: Bin Hu (AT&T)Participants
:No update from community
No update from community
No update from community
No update from community. Bin will look into details of the projects
Hongbo (Huawei) described 2 changes that have been made after the discussion last week. One is the name of the proposal, and the other is the list of available tools being added. Hongbo also sent an email to Manuel for further comments.
Manuel said that the proposal is clearer, and he has no further comment. Because most of the questions last week were from Bryan, Manuel is not sure if Bryan has further comment or not. Bin clarified that Bryan's questions were answered at the meeting last week, and the request to add the list of available tools was done.
Dave (RedHat) asked if the goal is to create new tools or modify existing tools. Hongbo said that the existing tools will be reused. If needed, the existing tools will be modified to fit the need of the project.
Because all questions were answered and clarified, and necessary revisions were made and improved the proposal, this proposal is technically ready for TSC creation review. The group reached the consensus to recommend it for TSC creation review next week.
This is the continuation of the discussion last week.
Dave (RedHat) asked what is the difference between this proposal and OSCAR. Stuart answered that this proposal will enable OpenContrail to be selected as the virtual networking technology in OPNFV deployments. Thus the main tasks of the project will be integration of OpenContrail artifacts into the OPNFV CI infrastructure, and ensuring support in the various installer projects. Therefore this project will feed OpenContrail as an element into the stack for installers before deployment. OSCAR is a post-installer deployment project, which will use the BGS stack as one of its initially supported stacks in order to exercise the ability to deploy at scale and on multiple sites.
Dave (RedHat) further asked if the intention is to make it available for all installers, and if an installer must support all stacks. Stuart said that ideally, it would be very nice for an installer to support all stacks. But in reality, each installer may only focus on one stack.
Iben (Spirent) shared the policy architecture covered by Copper. Bin clarified that this project is at the stage before installer. Copper's policy architecture is for operation and assumes that all SDN controllers have been deployed and in operation, which is at the stage after deployment (thus after installer).
Iben (Spirent) further asked the question about what is the first installer. Stuart said it is Jojo through JOID project. They are working with Canonical and made a good progress. Narinder (Canonical) confirmed that they are in close collaboration.
Dave (RedHat) indicated that it is not a good idea to force all installers to support it. Stuart said that it is not mandated. Each installer surely has its own focus and priority. Current target is JOID (Jojo) installer. They are also working on a Fuel version, which is not an OPNFV effort.
Because all questions were answered and clarified, and the work is already in good progress, the group feels that technically this proposal is ready for TSC creation review. The group reaches the consensus to recommend it for TSC creation review next week.
Frank is absent, and no one presented it.
Because this project has been discussed in mailing list and various occasions for quite a while, many installer projects have decided to join and support the guidelines and requirements of Genesis, Bin suggested that this proposal is technically ready and we should recommend it for TSC creation review.
Arnaud (Orange) seconded it, and Dave (RedHat) said it would be a good move. The group agreed to recommend it for TSC creation review next week.
Arnaud presented it.
Bin pointed out a typo in the installation flow, which should be to install "OpenStack" instead of "OpenSteak". Arnaud agreed.
Because this project has been progressing as a separate installer in BGS, it is technically ready for TSG creation review. The group reaches the consensus to recommend it for TSC creation review next week.
Inactive and postponed until author wishes to resume discussion
Meeting adjourned.