Jump to: navigation, search

Difference between revisions of "Bareon/Roadmap"

Line 95: Line 95:
 
|-
 
|-
 
| Extract nailgun data driver into separate repo || [https://blueprints.launchpad.net/bareon/+spec/refactor-data-drivers refactor-data-drivers]
 
| Extract nailgun data driver into separate repo || [https://blueprints.launchpad.net/bareon/+spec/refactor-data-drivers refactor-data-drivers]
 +
|-
 +
| Move content from contrib directory to separate repositories || [https://blueprints.launchpad.net/bareon/+spec/remove-contrib-directory-from-bareon remove-contrib-directory-from-bareon]
 
|}
 
|}
  

Revision as of 12:30, 9 February 2016

Latest releases

No released versions

Release in development

Version 1.0.0
Title Blueprint
Partitioning without provisioning (pluggable do_* actions) pluggable-do-actions

Future releases

Note: release dates and scoping of future releases can be changed.

Version 1.1.0
Title Blueprint
UEFI support uefi-support
Image building process should be extendable improve-image-building
Dynamic volume allocation dynamic-allocation


Version 1.2.0
Title Blueprint
Data driven decommission data-driven-decommission
Version 1.3.0
Title Blueprint
Multi-type image building (tarball, fs, disk) multi-type-image-building
Version 1.4.0
Title Blueprint
Raid support raid-support
Multi-path disk configuration multipath-disks-configuration
Improve dynamic volumes allocation dynamic-allocation-improvments
Version 1.5.0
Title Blueprint
Life cycle management life-cycle-managment
Version 1.6.0
Title Blueprint
LVM mirror support lvm-mirror-support
Disks check after unexpected shutdown disks-check-after-unexpected-shutdown
Backlog
Title Blueprint
Image pre-reboot configuration (good pluggable interface) No blueprint
Image delivery (support several transports [glance, torrent, etc]) No blueprint
Building of CentOS images No blueprint
Extract nailgun data driver into separate repo refactor-data-drivers
Move content from contrib directory to separate repositories remove-contrib-directory-from-bareon
Unsorted
Title Blueprint
Diskless nodes cases (probably should be solved by deployment tools) No blueprint
Using of Ironic for power and dhcp management No blueprint