Difference between revisions of "Blazar/Program"
m (Sergey Lukjanov moved page Climate/Program to Blazar/Program: Climate project has been renamed to the Blazar project due to the possible trademark issues.) |
|||
| Line 3: | Line 3: | ||
== Description == | == Description == | ||
| − | Resource Reservation program aims to provide resources reservations possibilities to OpenStack based cloud via contract-based mechanism called lease between service ( | + | Resource Reservation program aims to provide resources reservations possibilities to OpenStack based cloud via contract-based mechanism called lease between service (Blazar) and user. Resource reservation initiative includes close integration with other OpenStack projects to support different resources. |
== Mission Statement == | == Mission Statement == | ||
| Line 9: | Line 9: | ||
== Scope == | == Scope == | ||
| − | Our team is working on providing OpenStack with resource reservation opportunity in time-based manner, including close integration with all other OS projects. As | + | Our team is working on providing OpenStack with resource reservation opportunity in time-based manner, including close integration with all other OS projects. As Blazar initiative is targeting to provide not only compute resources revervation, but also volumes, network resources, storage nodes reservation opportunity, we consider it is not about being a part of some existing OpenStack program. This initiative needs to become a part of completely new '''Resource Reservation Program''', that aims to implement time-based cloud resource management. |
== Maturity == | == Maturity == | ||
| − | Resource Reservation initiative has been developed during all last year, and now there is great effective team working on it including talented people from Mirantis, Bull, Inria, Intel and eNovance. We believe that this project will have great future as a part of OpenStack ecosystem and will bring new features and possibilities to it. Our team is having weekly meetings ([https://wiki.openstack.org/wiki/Meetings/ | + | Resource Reservation initiative has been developed during all last year, and now there is great effective team working on it including talented people from Mirantis, Bull, Inria, Intel and eNovance. We believe that this project will have great future as a part of OpenStack ecosystem and will bring new features and possibilities to it. Our team is having weekly meetings ([https://wiki.openstack.org/wiki/Meetings/Blazar Fridays 15:00 UTC) and we have already released Blazar 0.1.0 as our first proposal on how reservation opportunity will look in future. Now we've almost finished work on 0.1.1 release containing some technical improvements and bug fixes, and are collecting (and starting implementing) scope for 0.2.x release branch. |
| − | Current | + | Current Blazar PTL is Dina Belova (DinaBelova on IRC), and she was chosen by Blazar ATCs during official voting - https://wiki.openstack.org/wiki/Blazar/PTL |
== Deliverables == | == Deliverables == | ||
| − | + | Blazar roadmap may be found [https://wiki.openstack.org/wiki/Blazar/Roadmap here]. | |
Revision as of 20:57, 5 June 2014
Official Title
Resource Reservation
Description
Resource Reservation program aims to provide resources reservations possibilities to OpenStack based cloud via contract-based mechanism called lease between service (Blazar) and user. Resource reservation initiative includes close integration with other OpenStack projects to support different resources.
Mission Statement
Provide ability to manage different cloud resources in time, by offering their planning and resources allocation/reclaiming process automation.
Scope
Our team is working on providing OpenStack with resource reservation opportunity in time-based manner, including close integration with all other OS projects. As Blazar initiative is targeting to provide not only compute resources revervation, but also volumes, network resources, storage nodes reservation opportunity, we consider it is not about being a part of some existing OpenStack program. This initiative needs to become a part of completely new Resource Reservation Program, that aims to implement time-based cloud resource management.
Maturity
Resource Reservation initiative has been developed during all last year, and now there is great effective team working on it including talented people from Mirantis, Bull, Inria, Intel and eNovance. We believe that this project will have great future as a part of OpenStack ecosystem and will bring new features and possibilities to it. Our team is having weekly meetings ([https://wiki.openstack.org/wiki/Meetings/Blazar Fridays 15:00 UTC) and we have already released Blazar 0.1.0 as our first proposal on how reservation opportunity will look in future. Now we've almost finished work on 0.1.1 release containing some technical improvements and bug fixes, and are collecting (and starting implementing) scope for 0.2.x release branch. Current Blazar PTL is Dina Belova (DinaBelova on IRC), and she was chosen by Blazar ATCs during official voting - https://wiki.openstack.org/wiki/Blazar/PTL
Deliverables
Blazar roadmap may be found here.
