openstack/fuel-plugins
Code Issues Proposed changes
f145f30498
fuel-plugins/CHANGELOG.md
Ilya Kutukov f145f30498 Fuel plugin builder v5 
- Now it is possible to deliver Fuel release configuration using the Fuel plugin
  [bp/release-as-a-plugin](https://blueprints.launchpad.net/fuel/+spec/release-as-a-plugin)
  Using flag ``is_release: true`` in ``metadata.yaml: releases:`` section you coud
  define new fuel release.
  Also you could define ``base_release: release_template.yaml`` inside release
  description to share single template between multiple releases.
- ``*_path`` directive in is now supported in ``metadata.yaml``.
  Now you could require folder, external file or merged glob output using keys
  like ``deployment_tasks_path: 'dt.yaml'``
- It is possible to define graphs linked with plugin or releases
  directive inside ``metadata.yaml``, see the examples.
- All yaml root files is not not required except ``metadata.yaml``.
- Templates and examples for the Fuel plugins package ``v5.0.0`` are added.
- Fuel plugin builder is refactored to make all configurations traceable and
  decouple logic working with file system with validation logic and building
  logic.
  [LP1539598](https://bugs.launchpad.net/fuel/+bug/1539598)
- Docker environment for building and creating plugins example.
- Experimental ``JSON`` manifests support added.
- Schemas are aligned with Fuel versions.
- Advanced build process reporting.
  Now FPB trying to detect all possible problems in plugin configuration
  and report them instead of failing of first of them and also could warn user
  without stopping execution.
- Now it is possible to build plugin package v4.0.0 without ``tasks.yaml``

Change-Id: I55d0313db7cd64ab16802a75ff0d9edd16782d01
Implements-blueprint: release-as-a-plugin
Closes-Bug: #1539598
Closes-Bug: #1552248
2016-10-13 03:04:59 +03:00

7.9 KiB
Raw Blame History

Changelog

5.0.0 (Not relesed)

New package version "5.0.0" includes the following features:

  • Now it is possible to deliver Fuel release configuration using the Fuel plugin bp/release-as-a-plugin Using flag is_release: true in metadata.yaml: releases: section you coud define new fuel release. Also you could define base_release: release_template.yaml inside release description to share single template between multiple releases.
  • *_path directive in is now supported in metadata.yaml. Now you could require folder, external file or merged glob output using keys like deployment_tasks_path: 'dt.yaml'
  • It is possible to define graphs linked with plugin or releases directive inside metadata.yaml, see the examples.
  • All yaml root files is not not required except metadata.yaml.
  • Templates and examples for the Fuel plugins package v5.0.0 are added.
  • Fuel plugin builder is refactored to make all configurations traceable and decouple logic working with file system with validation logic and building logic. LP1539598

Also, this release include several experimental features and improvements:

  • Docker environment for building and creating plugins example.

  • Experimental JSON manifests support added.

  • Schemas are aligned with Fuel versions.

  • Advanced build process reporting. Now FPB trying to detect all possible problems in plugin configuration and report them instead of failing of first of them and also could warn user without stopping execution.

    Reporting tree provides nice hierarchical output and extends integration abilities by providing different output formats: json, yaml, plaintext

Bugfixes:

  • Now it is possible to build plugin package v4.0.0 without tasks.yaml LP1552248

4.1.0 (2016-06-29)

Bugfixes:

  • tasks.yaml is now optional for package version "4.0.0" LP1552248
  • Fuel Mitaka (9.0) is supported by default in package version "4.0.0" LP1549276
  • Use more reliable way to check for fpm Ruby GEM LP1561069
  • Add ability for role to conflict with all roles by using * sign LP1547590
  • Do not execute uninstall.sh on plugin upgrade LP1564123
  • Add possiblity to use generators in environment_config.yaml LP1557562
  • Don't put any code to PREUN section if uninstall.sh doesn't exist or empty LP1574478
  • Allow a user to specify any arbitrary string as role name for cross-deps LP1557997
  • Add deployment tasks v2.1 validation support LP1590389

4.0.0 (2016-02-26)

New package version "4.0.0" includes the following features:

  • New flag is_hotpluggable in metadata.yaml that allows to install and use plugin on previously deployed environments.
  • Plugin can specify settings group using "group" field in metadata in environment_config.yaml file.
  • New group equipment added to groups list in metadata.yaml.
  • New components.yaml file that allows to declare new components.

Bugfixes:

  • Fix of missing strategy parameter in V3 and V4 deployment tasks LP1522785

3.0.0 (2014-09-16)

New package version "3.0.0" includes the following features:

  • New node_roles.yaml file that allows to add new node roles.
  • New volumes.yaml file that allows to add new volumes and/or define "node roles <-> volumes" mapping.
  • New deployment_tasks.yaml file that allows to declare pre/post- and regular deployment tasks for any node role. Unlike tasks.yaml, the tasks go through global deployment graph and that provides ability to execute task at any place during deployment, or overwrite/skip already existing ones.
  • New network_roles.yaml file that allows to add new network roles and reserve some VIPs, to be proceed by plugin.

Bugfixes:

  • Fix executing of deploy.sh deployment script LP1463441
  • Remove "Origin" field from Ubuntu's Release file in order to reduce probability of broken apt pinning LP1475665

2.0.4 (2014-06-23)

2.0.3 (2014-06-08)

2.0.2 (2014-05-15)

2.0.1 (2014-05-08)

2.0.0 (2014-04-30)

1.0.2 (2014-12-19)

1.0.1 (2014-11-20)

1.0.0 (2014-11-13)

Initial public release

  • Plugin create
  • Plugin build
  • Plugin check