requirements_projects:resource_scheduler
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
requirements_projects:resource_scheduler [2015/01/22 02:11] Zhiqi Wang [Project description:] |
requirements_projects:resource_scheduler [2015/03/18 02:05] (current) Mingjiang Li [Planned deliverables] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| * Proposed name for the project: ''Resource Scheduler'' | * Proposed name for the project: ''Resource Scheduler'' | ||
| - | * Proposed name for the repository: ''Resource Scheduler'' | + | * Proposed name for the repository: ''Conductor'' |
| * Project Categories: ''(Requirements)'' | * Project Categories: ''(Requirements)'' | ||
| Line 79: | Line 79: | ||
| ==== Dependencies: ==== | ==== Dependencies: ==== | ||
| + | {{ :requirements_projects:rs_3.png?500 |}} | ||
| * Identify similar projects is underway or being proposed in OPNFV or upstream project | * Identify similar projects is underway or being proposed in OPNFV or upstream project | ||
| - | * Copper | + | * Copper: |
| - | * Promise | + | * The Copper focuses on the policy engine, mostly on how to describe the policy with the policy language, but this project doesn't focus on how to implement any single policy. Our project wants to achieve some mechanism and policies, not focus on policy engine. |
| - | * OpenStack | + | * Promise: |
| + | * The Promise focuses on the resourse reservation. However, the network information collection and resource isolation in the resource scheduler project are not the content of the Promise. And the enhanced scheduler considers about the mechanisms above, as well as the performance optimization, which is not consider about the resource reservation. | ||
| * Identify any open source upstream projects and release timeline. | * Identify any open source upstream projects and release timeline. | ||
| * OpenStack Nova | * OpenStack Nova | ||
| Line 104: | Line 106: | ||
| * Zhiqi Wang (HUAWEI: zhiqi.wang@huawei.com) | * Zhiqi Wang (HUAWEI: zhiqi.wang@huawei.com) | ||
| * Ximing Li (HUAWEI: liximing@huawei.com) | * Ximing Li (HUAWEI: liximing@huawei.com) | ||
| - | * Qiao Fu (CMCC: fuqiao@chinamobile.com) | + | * Qiao Fu (China Mobile: fuqiao@chinamobile.com) |
| + | * Hao Pang(HUAWEI: shamrock.pang@huawei.com) | ||
| + | * Yimin Wang (HUAWEI: yimin.wang@huawei.com) | ||
| + | * Qi Liang (HUAWEI: liangqi1@huawei.com) | ||
| + | * Mingjiang Li (HUAWEI: limingjiang@huawei.com) | ||
| * Contributors: | * Contributors: | ||
| * Zhipeng Huang (HUAWEI: huangzhipeng@huawei.com) | * Zhipeng Huang (HUAWEI: huangzhipeng@huawei.com) | ||
| - | * Kin-Yip Liu ((Cavium: Kin-Yip.Liu@caviumnetworks.com) | + | * Kin-Yip Liu (Cavium: Kin-Yip.Liu@caviumnetworks.com) |
| + | * Ryota Mibu (NEC: r-mibu@cq.jp.nec.com) | ||
| ==== Planned deliverables ==== | ==== Planned deliverables ==== | ||
| * Describe the project release package as OPNFV or open source upstream projects. | * Describe the project release package as OPNFV or open source upstream projects. | ||
| - | * Ceilometer project (https://wiki.openstack.org/wiki/Ceilometer ) is the upstream project of this project. It would be aligned with OpenStack release schedule and OPNFV Release 1 schedule. | + | * User requirements of OPNFV Resource Scheduler. |
| - | * Nova project (https://wiki.openstack.org/wiki/Nova ) is the upstream project of this project. It would be aligned with OpenStack release schedule and OPNFV Release 1 schedule. | + | * Gap analysis on Resource Scheduler with open source upstream projects. |
| + | * Propose BPs in Nova project (https://wiki.openstack.org/wiki/Nova ) . | ||
| * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables. | * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables. | ||
| - | * N/A | + | * TBD |
| Line 123: | Line 131: | ||
| * When is the first release planned? | * When is the first release planned? | ||
| - | * Gap analysis is planned to be finished in OPNFV 1st release, i.e. by March, 2015. | + | * Gap analysis is planned to be finished in April, 2015. |
| * OPNFV resource scheduler software framework architecture (including API specification) is planned to be finished by August, 2015. | * OPNFV resource scheduler software framework architecture (including API specification) is planned to be finished by August, 2015. | ||
| * Will this align with the current release cadence | * Will this align with the current release cadence | ||
| - | * Yes, the gap analysis will be part of OPNFV 1st release; others will be part of OPNFV 2nd release. | + | * Yes. |
requirements_projects/resource_scheduler.1421892702.txt.gz · Last modified: 2015/01/22 02:11 by Zhiqi Wang
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
