Date and Time: UTC 14:00, Thursday March 05, 2015
Convenor: Bin Hu (AT&T)
Howard (Huawei) requested to postpone it.
Author was not present. Postponed
It was discussed on Feb 26. Iben has taken actions. It was postponed until Iben gives explicit information of how he wants to proceed further.
Howard (Huawei) described this proposal. It was targeted to address the issues related to geo diversity, and allow NFVI to be deployed in a distributed manner across multiple geographical locations. Howard indicated that Huawei is working with RedHat and Orange on project.
There are 3 types of questions and related discussions.
The first type of questions focused on gap analysis, or where the problem is. Howard indicated that the Gap Analysis is a work in progress, and primarily for OpenStack. The Tricircle effort just started, and no further progress could be shared. The "Proprietary Orchestration Layer" column needs more information of specifics of who are providing what solution on market today. Currently, there is no such information yet.
The second type of questions focused on which components of OpenStack should be targeted, or what is the scope of the project. Howard introduced that they would start to communicate with OpenStack Keystone team. Then the question became that Keystone is an identity service for authentication and authorization. Authentication certainly plays a role in multisite scenario, however, other component's roles might be more important in supporting geo diversity. So the roles of particular OpenStack components in supporting multisite scenario need to be clarified. A diagram / picture might help.
The third type of questions focused on collaboration with other OPNFV projects in supporting geo diversity. For example, Copper's policy framework will define a way of describing the intent of geo diversity, and will enforce the policy execution in multisite scenario. Doctor, Promise and resource scheduler projects will handle failover, fault tolerance, and resource related operations when multisite scenario is deployed. So those internal dependencies are not identified in this proposal, and how this proposal will collaborate with those internal projects is not clear. A picture / diagram might help.
There were discussions on the idea of coordinating Blueprint drafting and submission process within OPNFV, which also applies to this proposal which also targets to submit Blueprints.
Give the scope and complexity of this proposal, and those uncertainty, the consensus is that:
- The scope of this project needs to be narrowed down. If indeed Keystone is the primarily focus, the scope should be narrowed to focus on the problem and targeted enhancement of Keystone in supporting multisite environment.
- The roles of other OpenStack components need to be added and clarified. A diagram may be helpful to describe the scenario of those components in support of multisite. This will give a better overview of big picture.
- The dependencies, roles and collaboration model with Copper, Doctor etc. other OPNFV projects need to be added and clarified, A diagram may be helpful too.
This deals with OPNFV software upgrade. Granularity level needs to be clarified - upstream components at each level of stack, modules and sub-modules of upstream components, and nodes / clusters at deployed sites etc. The proposal has its value. The author of proposal was absent though and further discussion of proposal details was unable to proceed.
Uli (Huawei) had an action to reach out to the author of the proposal, and:
- discuss some comments on the proposal
- encourage author to participate in the discussion next week
Howard suggested to add Documentation project proposals into agenda.
Bryan suggested to add background information of OpenStack Blueprints into our wiki site. Dave Neary edited wiki and added information there https://wiki.opnfv.org/community/openstack. All projects, who have already submitted Blueprints or are planning to submit Blueprints in the future, are encouraged to add their Blueprint information to this table to allow for easier tracking and coordination inside OPNFV.