fuel-dev team mailing list archive
-
fuel-dev team
-
Mailing list archive
-
Message #00241
[openstack-dev] [Fuel] Fuel project 4.0 has reached its GA milestone
Hi All,
Just a quick note to let folks know that the Fuel project
<https://launchpad.net/fuel> has reached its 4.0 GA milestone. This
version of Fuel has been updated to deploy Havana 2013.2.1
<https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.1> including OpenStack
Orchestration (Heat) and optionally OpenStack Telemetry (Ceilometer). It
also deploys the newest version of the Murano project
<https://wiki.openstack.org/wiki/Murano> . Just a few of the other changes
made include:
* The Puppet Master server has been removed from the Fuel Master Node.
Puppet modules and manifests are now synchronized between the master node
and the managed nodes. The modules and manifests are then applied locally.
* The Fuel project has added a framework that enables partners and community
members to localize the Fuel UI by modifying the translate.json
<https://github.com/stackforge/fuel-web/blob/master/nailgun/static/i18n/tran
slation.json> file. A sample that translates the UI into zh-CN (Simplified
Chinese) has been created by a community partner, 99cloud, and can be found
in the file.
* Previously, It was only possible to specify a subnet for a public network
on the Networks tab of the Fuel UI. In this release, it is now possible to
set a flexible range for Fuel use, for example 12.0.0.10 to 12.0.0.20.
* Additional error checking has been added to the Fuel UI when entering
information into the network settings under the Network tab. A full list of
the limitations that are checked can be found on OpenStack Etherpad
<https://etherpad.openstack.org/p/limitations-of-networking-configuration> .
* In earlier releases, Fuel deployed the operating system and OpenStack
components in a single action. Now, it is possible to deploy the operating
system and OpenStack components in separate actions. This option is not
expected to be used for typical deployments but may be useful in focused
development or testing scenarios like OpenStack scalability testing as part
of the OpenStack Rally <https://wiki.openstack.org/wiki/Rally> project.
* Documentation
<http://docs.mirantis.com/fuel/fuel-4.0/reference-architecture.html#advanced
-network-configuration-using-open-vswitch> on how to enable NIC Bonding has
been made more complete and thorough.
* The default value for the Swift ring partition power is now being
calculated according to
https://answers.launchpad.net/swift/+question/211929.
I¹m looking forward to continued involvement from the community on the Fuel
project plus I¹m very excited as we continue discussions around leveraging
pieces of the Fuel project into OpenStack Deployment (TripleO
<https://wiki.openstack.org/wiki/TripleO> ) as we enter the new year.
Happy Holidays to everyone,
- David J. Easter
Product Line Manager, Mirantis