OpenStack - User contributions [en]

Translations:ReleaseNotes/Liberty/55/en

2016-08-13T02:14:56Z

FuzzyBot: Importing a new version from external source

=== Upgrade Notes ===

Translations:ReleaseNotes/Liberty/14/en

2016-08-13T02:14:36Z

FuzzyBot: Importing a new version from external source

=== Upgrade Notes ===

Translations:I18nTeam/23/en

2016-08-13T02:14:29Z

FuzzyBot: Importing a new version from external source

== Contribute to translation tools ==
Go to this page [[I18n/Tools|tools]] to understand the tools/scripts which are support our translation platform. If you want to help to report bugs, add more wishlists, and improve them, you can report bugs and fix bugs [https://bugs.launchpad.net/openstack-i18n here]. Mark bugs with a tag "'''tools'''".

Translations:ReleaseNotes/Liberty/121/en

2016-08-13T02:13:54Z

FuzzyBot: Importing a new version from external source

* Databases (Trove)
** Added initial support for database cluster creation and management. Vertica and MongoDB are currently supported (https://blueprints.launchpad.net/horizon/+spec/database-clustering-support).

Translations:ReleaseNotes/Liberty/9/en

2016-08-13T02:13:39Z

FuzzyBot: Importing a new version from external source

* Added the ability to specify ranges for Static Large Object (SLO) segments.

Translations:ReleaseNotes/Liberty/146/en

2016-08-13T02:13:15Z

FuzzyBot: Importing a new version from external source

Updated project guide that includes some details on operating, installing, configuring, developing to and using the service: http://docs.openstack.org/developer/glance/

Translations:ReleaseNotes/Liberty/80/en

2016-08-13T02:12:25Z

FuzzyBot: Importing a new version from external source

=== Upgrade notes ===

ReleaseNotes/Juno/en

2016-08-13T02:11:28Z

FuzzyBot: Importing a new version from external source

<languages />

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]
= OpenStack 2014.2 (Juno) Release Notes =

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== General Upgrade Notes ==

* The simplejson package is an optional requirement in most projects, therefore it's not listed in all project's requirements.txt file. However, if you're using it, e.g. better performance with python 2.6 on RHEL 6, then you will need simplejson >= 2.2.0. See https://bugs.launchpad.net/oslo-incubator/+bug/1361230 for details.

== OpenStack Object Storage (Swift) ==

=== Key New Features ===

The Juno integrated release includes three releases of OpenStack Swift: 2.0.0, 2.1.0, and 2.2.0. The changelog for these releases is available at https://github.com/openstack/swift/blob/2.2.0.rc1/CHANGELOG#L1-L173. Please refer to that document for release details.

Important new features are highlighted below. Please read the CHANGELOG and associated documentation.

* Storage policies
* Keystone v3 support
* Server-side account-to-account copy
* Better partition placement when adding a new server, zone, or region.
* Zero-copy GET responses using splice()
* Parallel object auditor

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

As always, you can upgrade your Swift cluster with no downtime for end-users. Please refer to sample config files and documentation before every release.

* There have been some logging changes that need to be called out. In all cases, well-behaved log processors will not be affected.
** Storage node (account, container, object) logs now have the PID logged at the end of the log line.
** Object daemons now send a user-agent string with their full name (e.g. "obj" is now "object").
* Once an additional storage policy has been enabled, downgrading to Swift pre-2.0.0 will cause any additional storage policies to become unavailable.
* As part of an effort to eventually update the default port to swift to an non-IANA-assigned range, bind_port is now a required setting. Anyone currently explicitly setting the ports will not be affected. However, if you do not currently set the ports, please ensure that your *_server.conf has bind_port set to match your ring as part of your upgrade.
* Note that storage policies include a new daemon, the container-reconciler.
* TempURL default allowed methods config setting now also allows POST and DELETE. This means tempurls can be created for these verbs. It does not affect any existing tempurls.
* A list of all updated, deprecated or removed options in swift can be found at: http://docs.openstack.org/trunk/config-reference/content/swift-conf-changes-master.html

== OpenStack Compute (Nova) ==

===Instance features===

* Allow users to specify an image to use for rescue instead of the original base image. [https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/allow-image-to-be-specified-during-rescue specification]
* Allow images to specify if a config drive should be used. [https://blueprints.launchpad.net/nova/+spec/config-drive-image-property launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/config-drive-image-property specification]
* Give users and administrators the ability to control the vCPU topology exposed to guests via flavors. [https://blueprints.launchpad.net/nova/+spec/virt-driver-vcpu-topology launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-vcpu-topology specification]
* Attach All Local Disks During Rescue. [https://blueprints.launchpad.net/nova/+spec/rescue-attach-all-disks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rescue-attach-all-disks specification]

===Networking===

* Improve the nova-network code to allow per-network settings. [https://blueprints.launchpad.net/nova/+spec/better-support-for-multiple-networks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/better-support-for-multiple-networks specification]
* Allow deployers to add hooks which are informed as soon as networking information for an instance is changed. [https://blueprints.launchpad.net/nova/+spec/instance-network-info-hook launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/instance-network-info-hook specification]
* Enable nova instances to be booted up with SR-IOV neutron ports. [https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/pci-passthrough-sriov specification]
* Permit VMs to attach multiple interfaces to one network. [https://blueprints.launchpad.net/nova/+spec/multiple-if-1-net launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/nfv-multiple-if-1-net specification]

===Scheduling===

* Extensible Resource Tracking. The set of resources tracked by nova is hard coded, this change makes that extensible, which will allow plug-ins to track new types of resources for scheduling. [https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/extensible-resource-tracking specification]
* Allow a host to be evacuated, but with the scheduler selecting destination hosts for the instances moved. [https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/find-host-and-evacuate-instance specification]
* Add support for host aggregates to scheduler filters. launchpad: [https://blueprints.launchpad.net/nova/+spec/per-aggregate-disk-allocation-ratio disk]; [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-instances-per-host instances]; and [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-io-ops-per-host IO ops] [http://specs.openstack.org/openstack/nova-specs/specs/juno/per-aggregate-filters specification]

===Other===

* i18n Enablement for Nova, turn on the lazy translation support from Oslo i18n and updating Nova to adhere to the restrictions this adds to translatable strings. [https://blueprints.launchpad.net/nova/+spec/i18n-enablement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/i18n-enablement specification]
* Offload periodic task sql query load to a slave sql server if one is configured. [https://blueprints.launchpad.net/nova/+spec/juno-slaveification launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/juno-slaveification specification]
* Only update the status of a host in the sql database when the status changes, instead of every 60 seconds. [https://blueprints.launchpad.net/nova/+spec/on-demand-compute-update launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/on-demand-compute-update specification]
* Include status information in API listings of hypervisor hosts. [https://blueprints.launchpad.net/nova/+spec/return-status-for-hypervisor-node launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/return-status-for-hypervisor-node specification]
* Allow API callers to specify more than one status to filter by when listing services. [https://blueprints.launchpad.net/nova/+spec/servers-list-support-multi-status launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/servers-list-support-multi-status specification]
* Add quota values to constrain the number and size of server groups a users can create. [https://blueprints.launchpad.net/nova/+spec/server-group-quotas launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/server-group-quotas specification]

===Hypervisor driver specific===

====Hyper-V====

* Support for differencing vhdx images. [https://blueprints.launchpad.net/nova/+spec/add-differencing-vhdx-resize-support launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-differencing-vhdx-resize-support specification]
* Support for console serial logs. [https://blueprints.launchpad.net/nova/+spec/hyper-v-console-log launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-console-log specification]
* Support soft reboot. [https://blueprints.launchpad.net/nova/+spec/hyper-v-soft-reboot launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-soft-reboot specification]

====Ironic====

* Add a virt driver for Ironic. [https://blueprints.launchpad.net/nova/+spec/add-ironic-driver launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-ironic-driver specification]

====libvirt====

* Performance improvements to listing instances on modern libvirts. [https://blueprints.launchpad.net/nova/+spec/libvirt-domain-listing-speedup launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-domain-listing-speedup specification]
* Allow snapshots of network backed disks. [https://blueprints.launchpad.net/nova/+spec/libvirt-volume-snap-network-disk launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-volume-snap-network-disk specification]
* Enable qemu memory balloon statistics for ceilometer reporting. [https://blueprints.launchpad.net/nova/+spec/enabled-qemu-memballoon-stats launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/enabled-qemu-memballoon-stats specification]
* Add support for handing back unused disk blocks to the underlying storage system. [https://blueprints.launchpad.net/nova/+spec/libvirt-disk-discard-option launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-disk-discard-option specification]
* Meta-data about an instance is now recorded in the libvirt domain XML. This is intended to help administrators while debugging problems. [https://blueprints.launchpad.net/nova/+spec/libvirt-driver-domain-metadata launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-driver-domain-metadata specification]
* Support namespaces for LXC containers. [https://blueprints.launchpad.net/nova/+spec/libvirt-lxc-user-namespaces launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-lxc-user-namespaces specification]
* Copy-on-write cloning for RBD-backed disks. [https://blueprints.launchpad.net/nova/+spec/rbd-clone-image-handler launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rbd-clone-image-handler specification]
* Expose interactive serial consoles. [https://blueprints.launchpad.net/nova/+spec/serial-ports launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/serial-ports specification]
* Allow controlled shutdown of guest operating systems during VM power off. [https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/user-defined-shutdown specification]
* Intelligent NUMA node placement for guests. [https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-numa-placement specification]

====vmware====

* Move the vmware driver to using the oslo vmware helper library. [https://blueprints.launchpad.net/nova/+spec/use-oslo-vmware launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/use-oslo-vmware specification]
* Add support for network interface hot plugging to vmware. [https://blueprints.launchpad.net/nova/+spec/vmware-hot-plug launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-hot-plug specification]
* Refactor the vmware driver's spawn functionality to be more maintainable. This work was internal, but is mentioned here because it significantly improves the supportability of the VMWare driver. [https://blueprints.launchpad.net/nova/+spec/vmware-spawn-refactor launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-spawn-refactor specification]

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

* A list of all updated, deprecated or removed options in Nova can be found at: http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html
* The nova-manage flavor subcommand is deprecated in Juno and will be removed in the 2015.1 (K) release: https://review.openstack.org/#/c/86122/
* https://review.openstack.org/#/c/102212/
* Minimum required libvirt version is now 0.9.11: https://review.openstack.org/#/c/58494/
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.
* Debug log output in python-novaclient has [https://review.openstack.org/#/c/98443/ changed slightly] to improve readability. The sha1 hash of the keystone token is now printed instead of the token itself - greatly shortening the amount of content being printed while still retaining the ability to determine token mismatch scenarios. In addition, some extra '\n' characters that were being added are removed. ''Double-check any log parsers!''
* libvirt.volume_drivers config param for nova.conf is deprecated, to be removed in the Lxxxx release. In general, this should affect only a small number of developers working on drivers. If this is you, the recommended approach is to continue your work inside a nova tree.

== OpenStack Image Service (Glance) ==
=== Key New Features ===
* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Key New Features ===

* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Known Issues ===

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

== OpenStack Dashboard (Horizon) ==

=== Key New Features ===

==== Sahara ====

The OpenStack Data Processing project (Sahara) was formally included into the integrated release in Juno and Horizon includes broad support for managing your data processing. You can specify and build clusters to utilize several data types with user specified jobs while tracking the progress of those jobs.

==== Neutron Features ====

Neutron added several new features in Juno, including:
* DVR (Distributed Virtual Routing)
* L3 HA support
* IPv6 subnet modes

Horizon provides support for these new features with the Juno release. These features provide much greater flexibility in specifying software defined networks.

An existing feature in Neutron that Horizon now supports is the MAC learning extension.

==== Glance Features ====
In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

==== Cinder Features ====
In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

Other features of the Cinder API not previously supported by Horizon added in Juno include:
* Enabling resetting the state of a snapshot
* Enabling resetting the state of a volume
* Supporting upload-to-image
* Volume retype
* QoS (quality of service) support

==== Trove ====
Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Another addition is support for utilizing and restoring from incremental database backups.

To improve support for Neutron based clouds, when creating a database instance, the user can now specify the NIC for the database instance on creation allowing direct access to the instance by the user.

==== Nova ====

The new nova instance actions panel provides a list of all actions taken on all instances in the current project allowing users to view resulting errors or actions taken by other users on those instances.

Administrators now have the ability to evacuate instances off hypervisors which can aid in system maintenance by providing a mechanism to migrate all instances to other hosts.

==== Improved Plugin Support ====
The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:
* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:

* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

==== Enhanced RBAC support ====

In an ongoing effort to support richer role based access control (RBAC) in Horizon, the views for several more services were enhanced with RBAC checks to determine user access to actions. The newly supported services are compute, network and orchestration. These changes allow operators to implement finer grained access control than just "member" and "admin".

The identity panels (domains, projects, users, roles, groups) have also been converted to support RBAC at the view level. The identity panels have been moved from the admin dashboard into their own 'Identity' dashboard and accessibility is determined by policies alone. This is the first step toward consolidating the near duplicate content of the project and admin dashboards into single views supporting a wide range of roles.

==== UX Changes ====

In Juno, Horizon transitioned to utilizing Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Havana release.

==== JavaScript Libraries Extracted ====
As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

==== Conversion from LESS to SCSS ====
The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

=== Known Issues ===

==== Rendering issues in extensions ====

The conversion to utilizing Bootstrap v3 can cause content extensions written on top of Horizon to have rendering issues. Most of these are fixed by a simple CSS class name substitutions. These issues are primarily seen with buttons and panel content widths.

==== Online Compression ====

With the move to SCSS, there may be issues with utilizing online compression in non-DEBUG mode in Horizon. Offline compression continues to work as in previous releases.

==== Neutron L3 HA ====

The HA property is updateable in the UI, however, the migration itself fails on the agent.
https://bugs.launchpad.net/horizon/+bug/1378525

=== Upgrade Notes ===
* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

== OpenStack Identity (Keystone) ==

=== Key New Features ===

* Keystone now has experimental support for [http://docs.openstack.org/developer/keystone/configure_federation.html#keystone-as-an-identity-provider-idp Keystone-to-Keystone federation], where one instance acts as an Identity Provider, and the other a Service Provider.
* PKIZ is a new token provider available for users of PKI tokens, which simply adds zlib-based compression to traditional PKI tokens.
* The hashing algorithm used for PKI tokens has been made configurable (the default is still MD5, but the Keystone team recommends that deployments migrate to SHA256).
* Identity-driver-configuration-per-domain now supports Internet domain names of arbitrary hierarchical complexity (for example, <code>customer.cloud.example.com</code>).
* The LDAP identity backend now supports <code>description</code> as an attribute of users.
* Identity API v3 requests are now validated via JSON Schema.
* In the case of multiple identity backends, Keystone can now map arbitrary resource IDs to arbitrary backends.
* <code>keystoneclient.middleware.auth_token</code> has been moved into it's own repository, <code>keystonemiddleware.auth_token</code>.
* Identity API v3 now supports a discrete call to retrieve a service catalog, <code>GET /v3/auth/catalog</code>.
* Federated authentication events and local role assignment operations now result in CADF (audit) notifications.
* Keystone can now associate a given policy blob with one or more endpoints.
* Keystone now provides JSON Home documents on the root API endpoints in response to <code>Accept: application/json-home</code> headers.
* Hiding endpoints from client's service catalogs is now more easily manageable via <code>OS-EP-FILTER</code>.
* The credentials collection API is now filterable per associated user (<code>GET /v3/credentials?user_id={user_id}</code>).
* New, generic API endpoints are available for retrieving authentication-related data, such as a service catalog, available project scopes, and available domain scopes.
* Keystone now supports mapping the user <code>enabled</code> attribute to the <code>lock</code> attribute in LDAP (and inverting the corresponding boolean value accordingly).
* A CA certificate file is now configurable for LDAPS connections.
* The templated catalog backend now supports generating service catalogs for Identity API v3.
* Service names were added to the v3 service catalog.
* Services can now be filtered by name (<code> GET /v3/services?name={service_name}</code>).

=== Known Issues ===
==== LDAP paged search results don't work with python-ldap 2.4 ====
When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

==== LDAP paged search results don't work with python-ldap 2.4 ====

When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

A fix for this issue has been proposed, which is expected to be made available in a stable update for Juno. For more details see https://bugs.launchpad.net/keystone/+bug/1381768

=== Upgrade Notes ===

* Due to the simpler out-of-the-box experience, the default token provider is now UUID instead of PKI.
* Database migrations for releases prior to Havana have been dropped, meaning that you must upgrade to the Juno release from either a Havana or Icehouse deployment.
* A comprehensive list of all updated, deprecated or removed options in Keystone can be found at: http://docs.openstack.org/trunk/config-reference/content/keystone-conf-changes-master.html
** All <code>token_api</code> methods are now deprecated.
** LDAP configuration options that previously contained the deprecated <code>tenant</code> terminology have been superseded by options using the term <code>project</code>.
** Proxy methods from the identity backend to the assignment backend (created to provide backwards compatibility as a result of the split of the Assignment backend from the Identity backend), have been removed. This should only affect custom, out-of-tree API extensions.
** Loading authentication plugins solely by class name in <code>keystone.conf</code> is now deprecated in favor of loading them by <code>custom-method-name = custom_package.CustomClass</code> pairs, and then defining the sequence of authentication methods as a list (<code>methods = custom-method-name, password</code>).
** In-tree token drivers (<code>keystone.token.backends</code>) have been moved to <code>keystone.token.persistence.backends</code>. Proxy objects exist to maintain compatibility. If a non-default value is used, it is recommended the value of the <code>driver</code> option in the <code>[token]</code> section of <code>keystone.conf</code> is updated to use the new location.
* All KVS backends besides the <code>token</code> driver have been formally deprecated.
* LDAP/AD configuration: All configuration options containing the term "tenant" have been deprecated in favor of similarly named configuration options using the term "project" (for example, <code>tenant_id_attribute</code> has been replaced by <code>project_id_attribute</code>).

== OpenStack Network Service (Neutron) ==
=== Key New Features ===
* DB migration refactor and new timeline
* Distributed Virtual Router Support (DVR)
* Full IPV6 support for tenant networks
* High Availability for the L3 Agent
* ipset support for security groups in place of iptables (this option is configurable)
* L3 agent performance improvements
* Migration to oslo.messaging library for RPC communication.
* Security group rules for devices RPC call refactoring (a huge performance improvement)
* New Plugins supported in Juno include the following:
** A10 Networks LBaaS driver for the LBaaS V1 API
** Arista L3 routing plugin
** Big Switch L3 routing plugin
** Brocade L3 routing plugin
** Cisco APIC ML2 Driver (including a L3 routing plugin).
** Cisco CSR L3 routing plugin
** Freescale SDN ML2 Mechanism Driver
** Nuage Networks ML2 Mechanism Driver
** SR-IOV capable NIC ML2 Mechanism Driver

=== Known Issues ===
* This is the first release for DVR and HA L3. The Neutron team desires to designate these features as production ready in Kilo and requests that deployers test on non-critical workloads and report any issues.
* FWaaS is still labeled as experimental, as it does not allow you to have more than one FW per tenant.

=== Upgrade Notes ===
* DB migration from the previous releases (icehouse or havana)
** In Icehouse or Hanava releases, the db migration operation is optional. If your Neutron database is not stamped (i.e., there is the db migration version info), please make sure to "stamp icehouse" before running the upgrade db migration to Juno.
** To check if your database is stamped, run the following command:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> current
** If the output of the current version is '''None''', please run:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> stamp icehouse
** and then run the db migration for upgrading Juno:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> upgrade juno
* A list of all updated, deprecated or removed options in neutron can be found at: http://docs.openstack.org/trunk/config-reference/content/neutron-conf-changes-master.html
* Attribute level policies dependent on resources are not enforced anymore. Meaning that some older policies from Icehouse are not needed. (e.g. "get_port:binding:vnic_type": "rule:admin_or_owner").
* The following plugins are deprecated in Juno:
** Cisco Nexus Sub-Plugin (The Nexus 1000V Sub-Plugin is still retained and supported in Juno).
** Mellanox Plugin
** Ryu Plugin
*XML support in the API is deprecated. Users and deployers should migrate to JSON for API interactions as soon as possible since the XML support will be removed in the Kilo (2015.1) release.

== OpenStack Block Storage (Cinder) ==
=== Key New Features ===
* Support for Volume Replication.
* Support for Consistency Groups and Snapshots of Consistency Groups.
* Support for Volume Pools.
* Completion of i18n-enablement
* Honor Glance protected properties in Image Upload
* Enable ability to restrict bandwidth usage on volume-copy operations
* Add Volume Num Weigher Scheduling

=== New Drivers/Plugins ===
* Datera
* Fujitsu ETERNUS
* Fusion IO
* Hitachi HBSD
* Huawei
* Nimble
* Prophetstor
* Pure
* XtremIO
* Oracle ZFS

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Cinder can be found at: http://docs.openstack.org/trunk/config-reference/content/cinder-conf-changes-master.html
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.

== OpenStack Telemetry (Ceilometer) ==
=== Key New Features ===
* Support for partitioning metric collection load across horizontally scaled-out central agents
* New method of partitioning alarm evaluation load using [https://github.com/stackforge/tooz tooz] coordination, as opposed to a hand-crafted protocol
* Much improved SQLAlchemy storage performance & scalability, so that MySQL or PostgreSQL can be used as the metering store for PoCs or small deployments
* Support for hardware-oriented monitoring of IPMI sensors via notifications from either Ironic or a new standalone agent
* More flexible & efficient SNMP monitoring:
** batching queries for multiple SNMP metrics into a single call to each daemon
** dynamic discovery of nodes deployed by TripleO for SNMP polling
** the ability to more easily extend the range of SNMP metrics that ceilometer gathers
** the ability to derive new metrics from arithmetic transformations applied to multiple primary metrics
* Option to split off the alarms persistence into a separate database
* Option to use notifications instead of RPC for metering messages
* Metering of Neutron networking services: LBaaS, FWaaS & VPNaaS
* New XenAPI compute inspector
* Support for persisting events via the MongoDB & Hbase storage drivers (previously limited to SQLAlchemy)
* Support for per-device metering of instance disks
* Use of ceilometer as a collector for os-profiler data
* New Telemetry section of the [http://docs.openstack.org/admin-guide-cloud/content/ch_admin-openstack-telemetry.html Cloud Administrator Guide]

=== Known Issues ===
* [https://bugs.launchpad.net/ceilometer/+bug/1381600 1381600] The new <code>ceilometer-agent-ipmi</code> fails to emit any samples when it encounters unparseable data from <code>ipmitool</code>.

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in ceilometer can be found at: http://docs.openstack.org/trunk/config-reference/content/ceilometer-conf-changes-master.html

== OpenStack Orchestration (Heat) ==
=== Key New Features ===

* Recovery from failures during stack updates
* API to cancel and roll back an in-progress stack update
* Implementation of new resource types:
** OS::Glance::Image
** OS::Heat::SwiftSignal
*** Provides the option to store Wait Condition (and Software Deployment) data in Swift
** OS::Heat::StructuredDeployments
*** Groups code for multiple lifecycle events into a single deployment resource
** OS::Heat::SoftwareDeployments
*** Provides a way of avoiding circular dependencies when deploying an interdependent cluster of servers
** OS::Heat::SoftwareComponent
** OS::Nova::ServerGroup
** OS::Sahara::NodeGroupTemplate
** OS::Sahara::ClusterTemplate
* Remember the previously-supplied parameters when updating a stack
* Improved scalability
* Improved visibility into trees of nested stacks

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in heat can be found at: http://docs.openstack.org/trunk/config-reference/content/heat-conf-changes-master.html

== OpenStack Database service (Trove) ==
=== Key New Features ===
* Support for Asynchronous Replication (master-slave replicas) between provisioned mysql instances.
* Introduction of a new Clustering API with initial support for MongoDB clusters.
* Support for deploying Trove on an OpenStack solution that is using Neutron for networking. Prior to this, only nova-network was supported.
* Support for provisioning PostgreSQL datastore instances.
* Backup and Restore support for Couchbase.
* Support to optionally restrict the Cinder backend used for Trove volumes.
* Support for defining custom datastore configuration parameters in the Trove database (using mgmt API).
* The ability to list all datastore types and versions in a single call

=== Other Incremental Improvements===
* Logging audit to improve log levels throughout the trove components.
* The extensions loading mechanism was improved by adding support for stevedore.
* The ability to support volumes for data is now on a per datastore bases.
* Created and updated timestamps and instance count were added to configuration groups list and details calls.

=== Known Issues ===

* [https://bugs.launchpad.net/trove/+bug/1333852 1333852]: Trove does not support flavor UUIDs -- the Trove flavors API requires flavors with a numerical ID in order to be consistent with the API response for icehouse Trove.

=== Upgrade Notes ===

None yet

== OpenStack Data Processing (Sahara) ==

=== New Key Features ===

* Data processing UI was fully merged into OpenStack Dashboard (horizon).
* Support of CDH 5.x was added.
* Support of Apache Spark was added. Supported versions are 0.9.1 and 1.0.0. Elastic data processing (EDP) engine was refactored a lot to support non-Oozie workflow engines.
* Support of Apache Hadoop 2.4.1 was added in addition to existing 1.2.1 and 2.3.0. Version 2.3.0 is deprecated in Juno.
* Support of multi region deployments.
* Hadoop Swift authentication using [http://docs.openstack.org/developer/sahara/userdoc/advanced.configuration.guide.html#domain-usage-for-swift-proxy-users keystone trust mechanism]. Now Hadoop can access data in Swift without storing credentials in config files.
* [http://docs.openstack.org/developer/sahara/userdoc/configuration.guide.html#sahara-notifications-configuration Ceilometer integration] was added. Now Sahara notifies Ceilometer about all cluster state changes.
* Cluster provisioning error handling was improved. If something goes wrong during scaling, cluster will rollback to original state.
* Added ability to [http://docs.openstack.org/developer/sahara/userdoc/features.html#security-group-management specify security groups for a node group]. Also Sahara could automatically create security group with only required ports open.
* Implemented [http://docs.openstack.org/developer/sahara/userdoc/features.html#running-sahara-in-distributed-mode distributed mode] for Sahara: sahara-all process is decoupled into sahara-api and sahara-engine. You can run several instances of sahara-api and sahara-engine on different hosts. Note that the feature implementation is considered to be in alpha-state.

=== Known Issues ===

* [https://bugs.launchpad.net/sahara/+bug/1271349 Bug 1271349]: Sahara requires root privileges to access VMs via namespaces.

=== Upgrade Notes ===

==== Main binary renamed to sahara-all ====

Please, note that you should use `sahara-all` instead of `sahara-api` to start
the All-In-One Sahara.

==== sahara.conf upgrade ====

We've migrated from custom auth_token middleware config options to the common
config options. To update your config file you should replace the following
old config opts with the new ones.

* "os_auth_protocol", "os_auth_host", "os_auth_port" -> "[keystone_authtoken]/auth_uri" and "[keystone_authtoken]/identity_uri"
* "os_admin_username" -> "[keystone_authtoken]/admin_user"
* "os_admin_password" -> "[keystone_authtoken]/admin_password"
* "os_admin_tenant_name" -> "[keystone_authtoken]/admin_tenant_name"

We've replaced oslo code from sahara.openstack.common.db by usage of oslo.db library.

Also sqlite database is not supported anymore. Please use MySQL or PostgreSQL
db backends for Sahara. Sqlite support was dropped because it doesn't support
(and not going to support, see http://www.sqlite.org/omitted.html) ALTER
COLUMN and DROP COLUMN commands required for DB migrations between versions.

You can find more info about config file options in Sahara repository in file
"etc/sahara/sahara.conf.sample".

==== Sahara Dashboard was merged into OpenStack Dashboard ====

The Sahara Dashboard is not available in Juno release. Instead it's
functionality is provided by OpenStack Dashboard out of the box.
The Sahara UI is available in OpenStack Dashboard in
"Project" -> "Data Processing" tab.

Note that you have to properly register Sahara in Keystone in
order for Sahara UI in the Dashboard to work.

==== VM user name changed for HEAT infrastructure engine ====

We've updated HEAT infrastructure engine ("infrastructure_engine=heat") to
use the same rules for instance user name as in direct engine. Before the
change user name for VMs created by Sahara using HEAT engine was always
'ec2-user'. Now user name is taken from the image registry as it is described
in the documentation.

Note, this change breaks Sahara backward compatibility for clusters created
using HEAT infrastructure engine before the change. Clusters will continue to
operate, but it is not recommended to perform scale operation over them.

==== Anti affinity implementation changed ====

Starting with Juno release anti affinity feature is implemented using server
groups. There should not be much difference in Sahara behavior from user
perspective, but there are internal changes:

* Server group object will be created if anti affinity feature is enabled.
* New implementation doesn't allow several affected instances on the same host even if they don't have common processes. So, if anti affinity enabled for 'datanode' and 'tasktracker' processes, previous implementation allowed to have instance with 'datanode' process and other instance with 'tasktracker' process on one host. New implementation guarantees that instances will be on different hosts.

Note, new implementation will be applied for new clusters only. Old implementation will be applied if user scales cluster created in Icehouse.

== OpenStack Documentation ==

* This release, the OpenStack Foundation funded a five-day book sprint to write the new [http://docs.openstack.org/arch-design/content/arch-guide-how-this-book-is-organized.html OpenStack Architecture Design Guide]. It offers architectures for general purpose, compute-focused, storage-focused, network-focused, multi-site, hybrid, massively scalable, and specialized clouds.
* The Install Guides have had a lot of clean up and standardization: uses common message queue (RabbitMQ), replaces openstack-config (crudini) commands with config file editing for improved learning opportunities and consistency, references a generic SQL database so that MariaDB or MySQL can be substituted, and replaces auth_port and auth_protocol with identity_uri, and auth_host with auth_uri throughout. The Install Guides are thoroughly tested on each distribution and continuously published until the official release packages are available to everyone.
* The [http://docs.openstack.org/high-availability-guide/content/index.html High Availability Guide] now has a separate review team and has moved into a separate repository.
* The [http://docs.openstack.org/security-guide/content/ Security Guide] now has a specialized review team and has moved into a separate repository.
* The long-form API reference documents have been re-purposed to focus on the [http://developer.openstack.org/api-ref.html API Complete Reference].
* The User Guide now contains Database Service for OpenStack information.
* The Command-Line Reference has been updated with new client releases and now contains additional chapters for the common OpenStack client, the trove-manage client, and the Data processing client (sahara).
* The [http://docs.openstack.org/admin-guide-cloud/content/ OpenStack Cloud Administrator Guide] now contains information about Telemetry (ceilometer).

Translations:ReleaseNotes/Juno/53/en

2016-08-13T02:11:27Z

FuzzyBot: Importing a new version from external source

==== Improved Plugin Support ====
The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:
* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

Translations:OpenStack Upstream Training/Info/1/en

2016-08-13T02:11:25Z

FuzzyBot: Importing a new version from external source

== Introduction ==

Translations:ReleaseNotes/Juno/118/en

2016-08-13T02:10:59Z

FuzzyBot: Importing a new version from external source

* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

ReleaseNotes/Juno/en

2016-08-13T02:10:59Z

FuzzyBot: Importing a new version from external source

<languages />

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]
= OpenStack 2014.2 (Juno) Release Notes =

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== General Upgrade Notes ==

* The simplejson package is an optional requirement in most projects, therefore it's not listed in all project's requirements.txt file. However, if you're using it, e.g. better performance with python 2.6 on RHEL 6, then you will need simplejson >= 2.2.0. See https://bugs.launchpad.net/oslo-incubator/+bug/1361230 for details.

== OpenStack Object Storage (Swift) ==

=== Key New Features ===

The Juno integrated release includes three releases of OpenStack Swift: 2.0.0, 2.1.0, and 2.2.0. The changelog for these releases is available at https://github.com/openstack/swift/blob/2.2.0.rc1/CHANGELOG#L1-L173. Please refer to that document for release details.

Important new features are highlighted below. Please read the CHANGELOG and associated documentation.

* Storage policies
* Keystone v3 support
* Server-side account-to-account copy
* Better partition placement when adding a new server, zone, or region.
* Zero-copy GET responses using splice()
* Parallel object auditor

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

As always, you can upgrade your Swift cluster with no downtime for end-users. Please refer to sample config files and documentation before every release.

* There have been some logging changes that need to be called out. In all cases, well-behaved log processors will not be affected.
** Storage node (account, container, object) logs now have the PID logged at the end of the log line.
** Object daemons now send a user-agent string with their full name (e.g. "obj" is now "object").
* Once an additional storage policy has been enabled, downgrading to Swift pre-2.0.0 will cause any additional storage policies to become unavailable.
* As part of an effort to eventually update the default port to swift to an non-IANA-assigned range, bind_port is now a required setting. Anyone currently explicitly setting the ports will not be affected. However, if you do not currently set the ports, please ensure that your *_server.conf has bind_port set to match your ring as part of your upgrade.
* Note that storage policies include a new daemon, the container-reconciler.
* TempURL default allowed methods config setting now also allows POST and DELETE. This means tempurls can be created for these verbs. It does not affect any existing tempurls.
* A list of all updated, deprecated or removed options in swift can be found at: http://docs.openstack.org/trunk/config-reference/content/swift-conf-changes-master.html

== OpenStack Compute (Nova) ==

===Instance features===

* Allow users to specify an image to use for rescue instead of the original base image. [https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/allow-image-to-be-specified-during-rescue specification]
* Allow images to specify if a config drive should be used. [https://blueprints.launchpad.net/nova/+spec/config-drive-image-property launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/config-drive-image-property specification]
* Give users and administrators the ability to control the vCPU topology exposed to guests via flavors. [https://blueprints.launchpad.net/nova/+spec/virt-driver-vcpu-topology launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-vcpu-topology specification]
* Attach All Local Disks During Rescue. [https://blueprints.launchpad.net/nova/+spec/rescue-attach-all-disks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rescue-attach-all-disks specification]

===Networking===

* Improve the nova-network code to allow per-network settings. [https://blueprints.launchpad.net/nova/+spec/better-support-for-multiple-networks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/better-support-for-multiple-networks specification]
* Allow deployers to add hooks which are informed as soon as networking information for an instance is changed. [https://blueprints.launchpad.net/nova/+spec/instance-network-info-hook launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/instance-network-info-hook specification]
* Enable nova instances to be booted up with SR-IOV neutron ports. [https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/pci-passthrough-sriov specification]
* Permit VMs to attach multiple interfaces to one network. [https://blueprints.launchpad.net/nova/+spec/multiple-if-1-net launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/nfv-multiple-if-1-net specification]

===Scheduling===

* Extensible Resource Tracking. The set of resources tracked by nova is hard coded, this change makes that extensible, which will allow plug-ins to track new types of resources for scheduling. [https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/extensible-resource-tracking specification]
* Allow a host to be evacuated, but with the scheduler selecting destination hosts for the instances moved. [https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/find-host-and-evacuate-instance specification]
* Add support for host aggregates to scheduler filters. launchpad: [https://blueprints.launchpad.net/nova/+spec/per-aggregate-disk-allocation-ratio disk]; [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-instances-per-host instances]; and [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-io-ops-per-host IO ops] [http://specs.openstack.org/openstack/nova-specs/specs/juno/per-aggregate-filters specification]

===Other===

* i18n Enablement for Nova, turn on the lazy translation support from Oslo i18n and updating Nova to adhere to the restrictions this adds to translatable strings. [https://blueprints.launchpad.net/nova/+spec/i18n-enablement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/i18n-enablement specification]
* Offload periodic task sql query load to a slave sql server if one is configured. [https://blueprints.launchpad.net/nova/+spec/juno-slaveification launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/juno-slaveification specification]
* Only update the status of a host in the sql database when the status changes, instead of every 60 seconds. [https://blueprints.launchpad.net/nova/+spec/on-demand-compute-update launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/on-demand-compute-update specification]
* Include status information in API listings of hypervisor hosts. [https://blueprints.launchpad.net/nova/+spec/return-status-for-hypervisor-node launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/return-status-for-hypervisor-node specification]
* Allow API callers to specify more than one status to filter by when listing services. [https://blueprints.launchpad.net/nova/+spec/servers-list-support-multi-status launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/servers-list-support-multi-status specification]
* Add quota values to constrain the number and size of server groups a users can create. [https://blueprints.launchpad.net/nova/+spec/server-group-quotas launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/server-group-quotas specification]

===Hypervisor driver specific===

====Hyper-V====

* Support for differencing vhdx images. [https://blueprints.launchpad.net/nova/+spec/add-differencing-vhdx-resize-support launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-differencing-vhdx-resize-support specification]
* Support for console serial logs. [https://blueprints.launchpad.net/nova/+spec/hyper-v-console-log launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-console-log specification]
* Support soft reboot. [https://blueprints.launchpad.net/nova/+spec/hyper-v-soft-reboot launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-soft-reboot specification]

====Ironic====

* Add a virt driver for Ironic. [https://blueprints.launchpad.net/nova/+spec/add-ironic-driver launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-ironic-driver specification]

====libvirt====

* Performance improvements to listing instances on modern libvirts. [https://blueprints.launchpad.net/nova/+spec/libvirt-domain-listing-speedup launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-domain-listing-speedup specification]
* Allow snapshots of network backed disks. [https://blueprints.launchpad.net/nova/+spec/libvirt-volume-snap-network-disk launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-volume-snap-network-disk specification]
* Enable qemu memory balloon statistics for ceilometer reporting. [https://blueprints.launchpad.net/nova/+spec/enabled-qemu-memballoon-stats launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/enabled-qemu-memballoon-stats specification]
* Add support for handing back unused disk blocks to the underlying storage system. [https://blueprints.launchpad.net/nova/+spec/libvirt-disk-discard-option launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-disk-discard-option specification]
* Meta-data about an instance is now recorded in the libvirt domain XML. This is intended to help administrators while debugging problems. [https://blueprints.launchpad.net/nova/+spec/libvirt-driver-domain-metadata launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-driver-domain-metadata specification]
* Support namespaces for LXC containers. [https://blueprints.launchpad.net/nova/+spec/libvirt-lxc-user-namespaces launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-lxc-user-namespaces specification]
* Copy-on-write cloning for RBD-backed disks. [https://blueprints.launchpad.net/nova/+spec/rbd-clone-image-handler launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rbd-clone-image-handler specification]
* Expose interactive serial consoles. [https://blueprints.launchpad.net/nova/+spec/serial-ports launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/serial-ports specification]
* Allow controlled shutdown of guest operating systems during VM power off. [https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/user-defined-shutdown specification]
* Intelligent NUMA node placement for guests. [https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-numa-placement specification]

====vmware====

* Move the vmware driver to using the oslo vmware helper library. [https://blueprints.launchpad.net/nova/+spec/use-oslo-vmware launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/use-oslo-vmware specification]
* Add support for network interface hot plugging to vmware. [https://blueprints.launchpad.net/nova/+spec/vmware-hot-plug launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-hot-plug specification]
* Refactor the vmware driver's spawn functionality to be more maintainable. This work was internal, but is mentioned here because it significantly improves the supportability of the VMWare driver. [https://blueprints.launchpad.net/nova/+spec/vmware-spawn-refactor launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-spawn-refactor specification]

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

* A list of all updated, deprecated or removed options in Nova can be found at: http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html
* The nova-manage flavor subcommand is deprecated in Juno and will be removed in the 2015.1 (K) release: https://review.openstack.org/#/c/86122/
* https://review.openstack.org/#/c/102212/
* Minimum required libvirt version is now 0.9.11: https://review.openstack.org/#/c/58494/
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.
* Debug log output in python-novaclient has [https://review.openstack.org/#/c/98443/ changed slightly] to improve readability. The sha1 hash of the keystone token is now printed instead of the token itself - greatly shortening the amount of content being printed while still retaining the ability to determine token mismatch scenarios. In addition, some extra '\n' characters that were being added are removed. ''Double-check any log parsers!''
* libvirt.volume_drivers config param for nova.conf is deprecated, to be removed in the Lxxxx release. In general, this should affect only a small number of developers working on drivers. If this is you, the recommended approach is to continue your work inside a nova tree.

== OpenStack Image Service (Glance) ==
=== Key New Features ===
* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Key New Features ===

* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Known Issues ===

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

== OpenStack Dashboard (Horizon) ==

=== Key New Features ===

==== Sahara ====

The OpenStack Data Processing project (Sahara) was formally included into the integrated release in Juno and Horizon includes broad support for managing your data processing. You can specify and build clusters to utilize several data types with user specified jobs while tracking the progress of those jobs.

==== Neutron Features ====

Neutron added several new features in Juno, including:
* DVR (Distributed Virtual Routing)
* L3 HA support
* IPv6 subnet modes

Horizon provides support for these new features with the Juno release. These features provide much greater flexibility in specifying software defined networks.

An existing feature in Neutron that Horizon now supports is the MAC learning extension.

==== Glance Features ====
In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

==== Cinder Features ====
In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

Other features of the Cinder API not previously supported by Horizon added in Juno include:
* Enabling resetting the state of a snapshot
* Enabling resetting the state of a volume
* Supporting upload-to-image
* Volume retype
* QoS (quality of service) support

==== Trove ====
Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Another addition is support for utilizing and restoring from incremental database backups.

To improve support for Neutron based clouds, when creating a database instance, the user can now specify the NIC for the database instance on creation allowing direct access to the instance by the user.

==== Nova ====

The new nova instance actions panel provides a list of all actions taken on all instances in the current project allowing users to view resulting errors or actions taken by other users on those instances.

Administrators now have the ability to evacuate instances off hypervisors which can aid in system maintenance by providing a mechanism to migrate all instances to other hosts.

==== Improved Plugin Support ====

The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:

* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

==== Enhanced RBAC support ====

In an ongoing effort to support richer role based access control (RBAC) in Horizon, the views for several more services were enhanced with RBAC checks to determine user access to actions. The newly supported services are compute, network and orchestration. These changes allow operators to implement finer grained access control than just "member" and "admin".

The identity panels (domains, projects, users, roles, groups) have also been converted to support RBAC at the view level. The identity panels have been moved from the admin dashboard into their own 'Identity' dashboard and accessibility is determined by policies alone. This is the first step toward consolidating the near duplicate content of the project and admin dashboards into single views supporting a wide range of roles.

==== UX Changes ====

In Juno, Horizon transitioned to utilizing Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Havana release.

==== JavaScript Libraries Extracted ====
As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

==== Conversion from LESS to SCSS ====
The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

=== Known Issues ===

==== Rendering issues in extensions ====

The conversion to utilizing Bootstrap v3 can cause content extensions written on top of Horizon to have rendering issues. Most of these are fixed by a simple CSS class name substitutions. These issues are primarily seen with buttons and panel content widths.

==== Online Compression ====

With the move to SCSS, there may be issues with utilizing online compression in non-DEBUG mode in Horizon. Offline compression continues to work as in previous releases.

==== Neutron L3 HA ====

The HA property is updateable in the UI, however, the migration itself fails on the agent.
https://bugs.launchpad.net/horizon/+bug/1378525

=== Upgrade Notes ===
* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

== OpenStack Identity (Keystone) ==

=== Key New Features ===

* Keystone now has experimental support for [http://docs.openstack.org/developer/keystone/configure_federation.html#keystone-as-an-identity-provider-idp Keystone-to-Keystone federation], where one instance acts as an Identity Provider, and the other a Service Provider.
* PKIZ is a new token provider available for users of PKI tokens, which simply adds zlib-based compression to traditional PKI tokens.
* The hashing algorithm used for PKI tokens has been made configurable (the default is still MD5, but the Keystone team recommends that deployments migrate to SHA256).
* Identity-driver-configuration-per-domain now supports Internet domain names of arbitrary hierarchical complexity (for example, <code>customer.cloud.example.com</code>).
* The LDAP identity backend now supports <code>description</code> as an attribute of users.
* Identity API v3 requests are now validated via JSON Schema.
* In the case of multiple identity backends, Keystone can now map arbitrary resource IDs to arbitrary backends.
* <code>keystoneclient.middleware.auth_token</code> has been moved into it's own repository, <code>keystonemiddleware.auth_token</code>.
* Identity API v3 now supports a discrete call to retrieve a service catalog, <code>GET /v3/auth/catalog</code>.
* Federated authentication events and local role assignment operations now result in CADF (audit) notifications.
* Keystone can now associate a given policy blob with one or more endpoints.
* Keystone now provides JSON Home documents on the root API endpoints in response to <code>Accept: application/json-home</code> headers.
* Hiding endpoints from client's service catalogs is now more easily manageable via <code>OS-EP-FILTER</code>.
* The credentials collection API is now filterable per associated user (<code>GET /v3/credentials?user_id={user_id}</code>).
* New, generic API endpoints are available for retrieving authentication-related data, such as a service catalog, available project scopes, and available domain scopes.
* Keystone now supports mapping the user <code>enabled</code> attribute to the <code>lock</code> attribute in LDAP (and inverting the corresponding boolean value accordingly).
* A CA certificate file is now configurable for LDAPS connections.
* The templated catalog backend now supports generating service catalogs for Identity API v3.
* Service names were added to the v3 service catalog.
* Services can now be filtered by name (<code> GET /v3/services?name={service_name}</code>).

=== Known Issues ===
==== LDAP paged search results don't work with python-ldap 2.4 ====
When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

==== LDAP paged search results don't work with python-ldap 2.4 ====

When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

A fix for this issue has been proposed, which is expected to be made available in a stable update for Juno. For more details see https://bugs.launchpad.net/keystone/+bug/1381768

=== Upgrade Notes ===

* Due to the simpler out-of-the-box experience, the default token provider is now UUID instead of PKI.
* Database migrations for releases prior to Havana have been dropped, meaning that you must upgrade to the Juno release from either a Havana or Icehouse deployment.
* A comprehensive list of all updated, deprecated or removed options in Keystone can be found at: http://docs.openstack.org/trunk/config-reference/content/keystone-conf-changes-master.html
** All <code>token_api</code> methods are now deprecated.
** LDAP configuration options that previously contained the deprecated <code>tenant</code> terminology have been superseded by options using the term <code>project</code>.
** Proxy methods from the identity backend to the assignment backend (created to provide backwards compatibility as a result of the split of the Assignment backend from the Identity backend), have been removed. This should only affect custom, out-of-tree API extensions.
** Loading authentication plugins solely by class name in <code>keystone.conf</code> is now deprecated in favor of loading them by <code>custom-method-name = custom_package.CustomClass</code> pairs, and then defining the sequence of authentication methods as a list (<code>methods = custom-method-name, password</code>).
** In-tree token drivers (<code>keystone.token.backends</code>) have been moved to <code>keystone.token.persistence.backends</code>. Proxy objects exist to maintain compatibility. If a non-default value is used, it is recommended the value of the <code>driver</code> option in the <code>[token]</code> section of <code>keystone.conf</code> is updated to use the new location.
* All KVS backends besides the <code>token</code> driver have been formally deprecated.
* LDAP/AD configuration: All configuration options containing the term "tenant" have been deprecated in favor of similarly named configuration options using the term "project" (for example, <code>tenant_id_attribute</code> has been replaced by <code>project_id_attribute</code>).

== OpenStack Network Service (Neutron) ==
=== Key New Features ===
* DB migration refactor and new timeline
* Distributed Virtual Router Support (DVR)
* Full IPV6 support for tenant networks
* High Availability for the L3 Agent
* ipset support for security groups in place of iptables (this option is configurable)
* L3 agent performance improvements
* Migration to oslo.messaging library for RPC communication.
* Security group rules for devices RPC call refactoring (a huge performance improvement)
* New Plugins supported in Juno include the following:
** A10 Networks LBaaS driver for the LBaaS V1 API
** Arista L3 routing plugin
** Big Switch L3 routing plugin
** Brocade L3 routing plugin
** Cisco APIC ML2 Driver (including a L3 routing plugin).
** Cisco CSR L3 routing plugin
** Freescale SDN ML2 Mechanism Driver
** Nuage Networks ML2 Mechanism Driver
** SR-IOV capable NIC ML2 Mechanism Driver

=== Known Issues ===
* This is the first release for DVR and HA L3. The Neutron team desires to designate these features as production ready in Kilo and requests that deployers test on non-critical workloads and report any issues.
* FWaaS is still labeled as experimental, as it does not allow you to have more than one FW per tenant.

=== Upgrade Notes ===
* DB migration from the previous releases (icehouse or havana)
** In Icehouse or Hanava releases, the db migration operation is optional. If your Neutron database is not stamped (i.e., there is the db migration version info), please make sure to "stamp icehouse" before running the upgrade db migration to Juno.
** To check if your database is stamped, run the following command:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> current
** If the output of the current version is '''None''', please run:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> stamp icehouse
** and then run the db migration for upgrading Juno:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> upgrade juno
* A list of all updated, deprecated or removed options in neutron can be found at: http://docs.openstack.org/trunk/config-reference/content/neutron-conf-changes-master.html
* Attribute level policies dependent on resources are not enforced anymore. Meaning that some older policies from Icehouse are not needed. (e.g. "get_port:binding:vnic_type": "rule:admin_or_owner").
* The following plugins are deprecated in Juno:
** Cisco Nexus Sub-Plugin (The Nexus 1000V Sub-Plugin is still retained and supported in Juno).
** Mellanox Plugin
** Ryu Plugin
*XML support in the API is deprecated. Users and deployers should migrate to JSON for API interactions as soon as possible since the XML support will be removed in the Kilo (2015.1) release.

== OpenStack Block Storage (Cinder) ==
=== Key New Features ===
* Support for Volume Replication.
* Support for Consistency Groups and Snapshots of Consistency Groups.
* Support for Volume Pools.
* Completion of i18n-enablement
* Honor Glance protected properties in Image Upload
* Enable ability to restrict bandwidth usage on volume-copy operations
* Add Volume Num Weigher Scheduling

=== New Drivers/Plugins ===
* Datera
* Fujitsu ETERNUS
* Fusion IO
* Hitachi HBSD
* Huawei
* Nimble
* Prophetstor
* Pure
* XtremIO
* Oracle ZFS

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Cinder can be found at: http://docs.openstack.org/trunk/config-reference/content/cinder-conf-changes-master.html
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.

== OpenStack Telemetry (Ceilometer) ==
=== Key New Features ===
* Support for partitioning metric collection load across horizontally scaled-out central agents
* New method of partitioning alarm evaluation load using [https://github.com/stackforge/tooz tooz] coordination, as opposed to a hand-crafted protocol
* Much improved SQLAlchemy storage performance & scalability, so that MySQL or PostgreSQL can be used as the metering store for PoCs or small deployments
* Support for hardware-oriented monitoring of IPMI sensors via notifications from either Ironic or a new standalone agent
* More flexible & efficient SNMP monitoring:
** batching queries for multiple SNMP metrics into a single call to each daemon
** dynamic discovery of nodes deployed by TripleO for SNMP polling
** the ability to more easily extend the range of SNMP metrics that ceilometer gathers
** the ability to derive new metrics from arithmetic transformations applied to multiple primary metrics
* Option to split off the alarms persistence into a separate database
* Option to use notifications instead of RPC for metering messages
* Metering of Neutron networking services: LBaaS, FWaaS & VPNaaS
* New XenAPI compute inspector
* Support for persisting events via the MongoDB & Hbase storage drivers (previously limited to SQLAlchemy)
* Support for per-device metering of instance disks
* Use of ceilometer as a collector for os-profiler data
* New Telemetry section of the [http://docs.openstack.org/admin-guide-cloud/content/ch_admin-openstack-telemetry.html Cloud Administrator Guide]

=== Known Issues ===
* [https://bugs.launchpad.net/ceilometer/+bug/1381600 1381600] The new <code>ceilometer-agent-ipmi</code> fails to emit any samples when it encounters unparseable data from <code>ipmitool</code>.

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in ceilometer can be found at: http://docs.openstack.org/trunk/config-reference/content/ceilometer-conf-changes-master.html

== OpenStack Orchestration (Heat) ==
=== Key New Features ===

* Recovery from failures during stack updates
* API to cancel and roll back an in-progress stack update
* Implementation of new resource types:
** OS::Glance::Image
** OS::Heat::SwiftSignal
*** Provides the option to store Wait Condition (and Software Deployment) data in Swift
** OS::Heat::StructuredDeployments
*** Groups code for multiple lifecycle events into a single deployment resource
** OS::Heat::SoftwareDeployments
*** Provides a way of avoiding circular dependencies when deploying an interdependent cluster of servers
** OS::Heat::SoftwareComponent
** OS::Nova::ServerGroup
** OS::Sahara::NodeGroupTemplate
** OS::Sahara::ClusterTemplate
* Remember the previously-supplied parameters when updating a stack
* Improved scalability
* Improved visibility into trees of nested stacks

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in heat can be found at: http://docs.openstack.org/trunk/config-reference/content/heat-conf-changes-master.html

== OpenStack Database service (Trove) ==
=== Key New Features ===
* Support for Asynchronous Replication (master-slave replicas) between provisioned mysql instances.
* Introduction of a new Clustering API with initial support for MongoDB clusters.
* Support for deploying Trove on an OpenStack solution that is using Neutron for networking. Prior to this, only nova-network was supported.
* Support for provisioning PostgreSQL datastore instances.
* Backup and Restore support for Couchbase.
* Support to optionally restrict the Cinder backend used for Trove volumes.
* Support for defining custom datastore configuration parameters in the Trove database (using mgmt API).
* The ability to list all datastore types and versions in a single call

=== Other Incremental Improvements===
* Logging audit to improve log levels throughout the trove components.
* The extensions loading mechanism was improved by adding support for stevedore.
* The ability to support volumes for data is now on a per datastore bases.
* Created and updated timestamps and instance count were added to configuration groups list and details calls.

=== Known Issues ===

* [https://bugs.launchpad.net/trove/+bug/1333852 1333852]: Trove does not support flavor UUIDs -- the Trove flavors API requires flavors with a numerical ID in order to be consistent with the API response for icehouse Trove.

=== Upgrade Notes ===

None yet

== OpenStack Data Processing (Sahara) ==

=== New Key Features ===

* Data processing UI was fully merged into OpenStack Dashboard (horizon).
* Support of CDH 5.x was added.
* Support of Apache Spark was added. Supported versions are 0.9.1 and 1.0.0. Elastic data processing (EDP) engine was refactored a lot to support non-Oozie workflow engines.
* Support of Apache Hadoop 2.4.1 was added in addition to existing 1.2.1 and 2.3.0. Version 2.3.0 is deprecated in Juno.
* Support of multi region deployments.
* Hadoop Swift authentication using [http://docs.openstack.org/developer/sahara/userdoc/advanced.configuration.guide.html#domain-usage-for-swift-proxy-users keystone trust mechanism]. Now Hadoop can access data in Swift without storing credentials in config files.
* [http://docs.openstack.org/developer/sahara/userdoc/configuration.guide.html#sahara-notifications-configuration Ceilometer integration] was added. Now Sahara notifies Ceilometer about all cluster state changes.
* Cluster provisioning error handling was improved. If something goes wrong during scaling, cluster will rollback to original state.
* Added ability to [http://docs.openstack.org/developer/sahara/userdoc/features.html#security-group-management specify security groups for a node group]. Also Sahara could automatically create security group with only required ports open.
* Implemented [http://docs.openstack.org/developer/sahara/userdoc/features.html#running-sahara-in-distributed-mode distributed mode] for Sahara: sahara-all process is decoupled into sahara-api and sahara-engine. You can run several instances of sahara-api and sahara-engine on different hosts. Note that the feature implementation is considered to be in alpha-state.

=== Known Issues ===

* [https://bugs.launchpad.net/sahara/+bug/1271349 Bug 1271349]: Sahara requires root privileges to access VMs via namespaces.

=== Upgrade Notes ===

==== Main binary renamed to sahara-all ====

Please, note that you should use `sahara-all` instead of `sahara-api` to start
the All-In-One Sahara.

==== sahara.conf upgrade ====

We've migrated from custom auth_token middleware config options to the common
config options. To update your config file you should replace the following
old config opts with the new ones.

* "os_auth_protocol", "os_auth_host", "os_auth_port" -> "[keystone_authtoken]/auth_uri" and "[keystone_authtoken]/identity_uri"
* "os_admin_username" -> "[keystone_authtoken]/admin_user"
* "os_admin_password" -> "[keystone_authtoken]/admin_password"
* "os_admin_tenant_name" -> "[keystone_authtoken]/admin_tenant_name"

We've replaced oslo code from sahara.openstack.common.db by usage of oslo.db library.

Also sqlite database is not supported anymore. Please use MySQL or PostgreSQL
db backends for Sahara. Sqlite support was dropped because it doesn't support
(and not going to support, see http://www.sqlite.org/omitted.html) ALTER
COLUMN and DROP COLUMN commands required for DB migrations between versions.

You can find more info about config file options in Sahara repository in file
"etc/sahara/sahara.conf.sample".

==== Sahara Dashboard was merged into OpenStack Dashboard ====

The Sahara Dashboard is not available in Juno release. Instead it's
functionality is provided by OpenStack Dashboard out of the box.
The Sahara UI is available in OpenStack Dashboard in
"Project" -> "Data Processing" tab.

Note that you have to properly register Sahara in Keystone in
order for Sahara UI in the Dashboard to work.

==== VM user name changed for HEAT infrastructure engine ====

We've updated HEAT infrastructure engine ("infrastructure_engine=heat") to
use the same rules for instance user name as in direct engine. Before the
change user name for VMs created by Sahara using HEAT engine was always
'ec2-user'. Now user name is taken from the image registry as it is described
in the documentation.

Note, this change breaks Sahara backward compatibility for clusters created
using HEAT infrastructure engine before the change. Clusters will continue to
operate, but it is not recommended to perform scale operation over them.

==== Anti affinity implementation changed ====

Starting with Juno release anti affinity feature is implemented using server
groups. There should not be much difference in Sahara behavior from user
perspective, but there are internal changes:

* Server group object will be created if anti affinity feature is enabled.
* New implementation doesn't allow several affected instances on the same host even if they don't have common processes. So, if anti affinity enabled for 'datanode' and 'tasktracker' processes, previous implementation allowed to have instance with 'datanode' process and other instance with 'tasktracker' process on one host. New implementation guarantees that instances will be on different hosts.

Note, new implementation will be applied for new clusters only. Old implementation will be applied if user scales cluster created in Icehouse.

== OpenStack Documentation ==

* This release, the OpenStack Foundation funded a five-day book sprint to write the new [http://docs.openstack.org/arch-design/content/arch-guide-how-this-book-is-organized.html OpenStack Architecture Design Guide]. It offers architectures for general purpose, compute-focused, storage-focused, network-focused, multi-site, hybrid, massively scalable, and specialized clouds.
* The Install Guides have had a lot of clean up and standardization: uses common message queue (RabbitMQ), replaces openstack-config (crudini) commands with config file editing for improved learning opportunities and consistency, references a generic SQL database so that MariaDB or MySQL can be substituted, and replaces auth_port and auth_protocol with identity_uri, and auth_host with auth_uri throughout. The Install Guides are thoroughly tested on each distribution and continuously published until the official release packages are available to everyone.
* The [http://docs.openstack.org/high-availability-guide/content/index.html High Availability Guide] now has a separate review team and has moved into a separate repository.
* The [http://docs.openstack.org/security-guide/content/ Security Guide] now has a specialized review team and has moved into a separate repository.
* The long-form API reference documents have been re-purposed to focus on the [http://developer.openstack.org/api-ref.html API Complete Reference].
* The User Guide now contains Database Service for OpenStack information.
* The Command-Line Reference has been updated with new client releases and now contains additional chapters for the common OpenStack client, the trove-manage client, and the Data processing client (sahara).
* The [http://docs.openstack.org/admin-guide-cloud/content/ OpenStack Cloud Administrator Guide] now contains information about Telemetry (ceilometer).

Translations:ReleaseNotes/Juno/63/en

2016-08-13T02:10:47Z

FuzzyBot: Importing a new version from external source

=== Upgrade Notes ===
* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

ReleaseNotes/Juno/en

2016-08-13T02:10:47Z

FuzzyBot: Importing a new version from external source

<languages />

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]
= OpenStack 2014.2 (Juno) Release Notes =

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== General Upgrade Notes ==

* The simplejson package is an optional requirement in most projects, therefore it's not listed in all project's requirements.txt file. However, if you're using it, e.g. better performance with python 2.6 on RHEL 6, then you will need simplejson >= 2.2.0. See https://bugs.launchpad.net/oslo-incubator/+bug/1361230 for details.

== OpenStack Object Storage (Swift) ==

=== Key New Features ===

The Juno integrated release includes three releases of OpenStack Swift: 2.0.0, 2.1.0, and 2.2.0. The changelog for these releases is available at https://github.com/openstack/swift/blob/2.2.0.rc1/CHANGELOG#L1-L173. Please refer to that document for release details.

Important new features are highlighted below. Please read the CHANGELOG and associated documentation.

* Storage policies
* Keystone v3 support
* Server-side account-to-account copy
* Better partition placement when adding a new server, zone, or region.
* Zero-copy GET responses using splice()
* Parallel object auditor

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

As always, you can upgrade your Swift cluster with no downtime for end-users. Please refer to sample config files and documentation before every release.

* There have been some logging changes that need to be called out. In all cases, well-behaved log processors will not be affected.
** Storage node (account, container, object) logs now have the PID logged at the end of the log line.
** Object daemons now send a user-agent string with their full name (e.g. "obj" is now "object").
* Once an additional storage policy has been enabled, downgrading to Swift pre-2.0.0 will cause any additional storage policies to become unavailable.
* As part of an effort to eventually update the default port to swift to an non-IANA-assigned range, bind_port is now a required setting. Anyone currently explicitly setting the ports will not be affected. However, if you do not currently set the ports, please ensure that your *_server.conf has bind_port set to match your ring as part of your upgrade.
* Note that storage policies include a new daemon, the container-reconciler.
* TempURL default allowed methods config setting now also allows POST and DELETE. This means tempurls can be created for these verbs. It does not affect any existing tempurls.
* A list of all updated, deprecated or removed options in swift can be found at: http://docs.openstack.org/trunk/config-reference/content/swift-conf-changes-master.html

== OpenStack Compute (Nova) ==

===Instance features===

* Allow users to specify an image to use for rescue instead of the original base image. [https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/allow-image-to-be-specified-during-rescue specification]
* Allow images to specify if a config drive should be used. [https://blueprints.launchpad.net/nova/+spec/config-drive-image-property launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/config-drive-image-property specification]
* Give users and administrators the ability to control the vCPU topology exposed to guests via flavors. [https://blueprints.launchpad.net/nova/+spec/virt-driver-vcpu-topology launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-vcpu-topology specification]
* Attach All Local Disks During Rescue. [https://blueprints.launchpad.net/nova/+spec/rescue-attach-all-disks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rescue-attach-all-disks specification]

===Networking===

* Improve the nova-network code to allow per-network settings. [https://blueprints.launchpad.net/nova/+spec/better-support-for-multiple-networks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/better-support-for-multiple-networks specification]
* Allow deployers to add hooks which are informed as soon as networking information for an instance is changed. [https://blueprints.launchpad.net/nova/+spec/instance-network-info-hook launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/instance-network-info-hook specification]
* Enable nova instances to be booted up with SR-IOV neutron ports. [https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/pci-passthrough-sriov specification]
* Permit VMs to attach multiple interfaces to one network. [https://blueprints.launchpad.net/nova/+spec/multiple-if-1-net launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/nfv-multiple-if-1-net specification]

===Scheduling===

* Extensible Resource Tracking. The set of resources tracked by nova is hard coded, this change makes that extensible, which will allow plug-ins to track new types of resources for scheduling. [https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/extensible-resource-tracking specification]
* Allow a host to be evacuated, but with the scheduler selecting destination hosts for the instances moved. [https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/find-host-and-evacuate-instance specification]
* Add support for host aggregates to scheduler filters. launchpad: [https://blueprints.launchpad.net/nova/+spec/per-aggregate-disk-allocation-ratio disk]; [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-instances-per-host instances]; and [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-io-ops-per-host IO ops] [http://specs.openstack.org/openstack/nova-specs/specs/juno/per-aggregate-filters specification]

===Other===

* i18n Enablement for Nova, turn on the lazy translation support from Oslo i18n and updating Nova to adhere to the restrictions this adds to translatable strings. [https://blueprints.launchpad.net/nova/+spec/i18n-enablement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/i18n-enablement specification]
* Offload periodic task sql query load to a slave sql server if one is configured. [https://blueprints.launchpad.net/nova/+spec/juno-slaveification launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/juno-slaveification specification]
* Only update the status of a host in the sql database when the status changes, instead of every 60 seconds. [https://blueprints.launchpad.net/nova/+spec/on-demand-compute-update launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/on-demand-compute-update specification]
* Include status information in API listings of hypervisor hosts. [https://blueprints.launchpad.net/nova/+spec/return-status-for-hypervisor-node launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/return-status-for-hypervisor-node specification]
* Allow API callers to specify more than one status to filter by when listing services. [https://blueprints.launchpad.net/nova/+spec/servers-list-support-multi-status launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/servers-list-support-multi-status specification]
* Add quota values to constrain the number and size of server groups a users can create. [https://blueprints.launchpad.net/nova/+spec/server-group-quotas launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/server-group-quotas specification]

===Hypervisor driver specific===

====Hyper-V====

* Support for differencing vhdx images. [https://blueprints.launchpad.net/nova/+spec/add-differencing-vhdx-resize-support launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-differencing-vhdx-resize-support specification]
* Support for console serial logs. [https://blueprints.launchpad.net/nova/+spec/hyper-v-console-log launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-console-log specification]
* Support soft reboot. [https://blueprints.launchpad.net/nova/+spec/hyper-v-soft-reboot launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-soft-reboot specification]

====Ironic====

* Add a virt driver for Ironic. [https://blueprints.launchpad.net/nova/+spec/add-ironic-driver launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-ironic-driver specification]

====libvirt====

* Performance improvements to listing instances on modern libvirts. [https://blueprints.launchpad.net/nova/+spec/libvirt-domain-listing-speedup launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-domain-listing-speedup specification]
* Allow snapshots of network backed disks. [https://blueprints.launchpad.net/nova/+spec/libvirt-volume-snap-network-disk launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-volume-snap-network-disk specification]
* Enable qemu memory balloon statistics for ceilometer reporting. [https://blueprints.launchpad.net/nova/+spec/enabled-qemu-memballoon-stats launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/enabled-qemu-memballoon-stats specification]
* Add support for handing back unused disk blocks to the underlying storage system. [https://blueprints.launchpad.net/nova/+spec/libvirt-disk-discard-option launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-disk-discard-option specification]
* Meta-data about an instance is now recorded in the libvirt domain XML. This is intended to help administrators while debugging problems. [https://blueprints.launchpad.net/nova/+spec/libvirt-driver-domain-metadata launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-driver-domain-metadata specification]
* Support namespaces for LXC containers. [https://blueprints.launchpad.net/nova/+spec/libvirt-lxc-user-namespaces launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-lxc-user-namespaces specification]
* Copy-on-write cloning for RBD-backed disks. [https://blueprints.launchpad.net/nova/+spec/rbd-clone-image-handler launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rbd-clone-image-handler specification]
* Expose interactive serial consoles. [https://blueprints.launchpad.net/nova/+spec/serial-ports launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/serial-ports specification]
* Allow controlled shutdown of guest operating systems during VM power off. [https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/user-defined-shutdown specification]
* Intelligent NUMA node placement for guests. [https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-numa-placement specification]

====vmware====

* Move the vmware driver to using the oslo vmware helper library. [https://blueprints.launchpad.net/nova/+spec/use-oslo-vmware launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/use-oslo-vmware specification]
* Add support for network interface hot plugging to vmware. [https://blueprints.launchpad.net/nova/+spec/vmware-hot-plug launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-hot-plug specification]
* Refactor the vmware driver's spawn functionality to be more maintainable. This work was internal, but is mentioned here because it significantly improves the supportability of the VMWare driver. [https://blueprints.launchpad.net/nova/+spec/vmware-spawn-refactor launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-spawn-refactor specification]

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

* A list of all updated, deprecated or removed options in Nova can be found at: http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html
* The nova-manage flavor subcommand is deprecated in Juno and will be removed in the 2015.1 (K) release: https://review.openstack.org/#/c/86122/
* https://review.openstack.org/#/c/102212/
* Minimum required libvirt version is now 0.9.11: https://review.openstack.org/#/c/58494/
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.
* Debug log output in python-novaclient has [https://review.openstack.org/#/c/98443/ changed slightly] to improve readability. The sha1 hash of the keystone token is now printed instead of the token itself - greatly shortening the amount of content being printed while still retaining the ability to determine token mismatch scenarios. In addition, some extra '\n' characters that were being added are removed. ''Double-check any log parsers!''
* libvirt.volume_drivers config param for nova.conf is deprecated, to be removed in the Lxxxx release. In general, this should affect only a small number of developers working on drivers. If this is you, the recommended approach is to continue your work inside a nova tree.

== OpenStack Image Service (Glance) ==
=== Key New Features ===
* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Key New Features ===

* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Known Issues ===

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.
* glance workers will now be equal to the number of CPUs available by default if not explicitly specified in glance-api.conf and/or glance-registry.conf
** There is no upgrade impact to glance-api workers since glance-api.conf previously hard-coded the workers value to 1 so anyone upgrading to tihs will still get whatever value was set in glance-api.conf prior to this change. There is an upgrade impact to the glance-registry workers since glance-registry.conf did not hard-code the workers value to 1 before this change. So anyone upgrading to this change that does not have workers specified in glance-registry.conf will now be running multiple workers by default when they restart the glance registry service.

== OpenStack Dashboard (Horizon) ==

=== Key New Features ===

==== Sahara ====

The OpenStack Data Processing project (Sahara) was formally included into the integrated release in Juno and Horizon includes broad support for managing your data processing. You can specify and build clusters to utilize several data types with user specified jobs while tracking the progress of those jobs.

==== Neutron Features ====

Neutron added several new features in Juno, including:
* DVR (Distributed Virtual Routing)
* L3 HA support
* IPv6 subnet modes

Horizon provides support for these new features with the Juno release. These features provide much greater flexibility in specifying software defined networks.

An existing feature in Neutron that Horizon now supports is the MAC learning extension.

==== Glance Features ====
In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

==== Cinder Features ====
In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

Other features of the Cinder API not previously supported by Horizon added in Juno include:
* Enabling resetting the state of a snapshot
* Enabling resetting the state of a volume
* Supporting upload-to-image
* Volume retype
* QoS (quality of service) support

==== Trove ====
Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Another addition is support for utilizing and restoring from incremental database backups.

To improve support for Neutron based clouds, when creating a database instance, the user can now specify the NIC for the database instance on creation allowing direct access to the instance by the user.

==== Nova ====

The new nova instance actions panel provides a list of all actions taken on all instances in the current project allowing users to view resulting errors or actions taken by other users on those instances.

Administrators now have the ability to evacuate instances off hypervisors which can aid in system maintenance by providing a mechanism to migrate all instances to other hosts.

==== Improved Plugin Support ====

The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:

* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

==== Enhanced RBAC support ====

In an ongoing effort to support richer role based access control (RBAC) in Horizon, the views for several more services were enhanced with RBAC checks to determine user access to actions. The newly supported services are compute, network and orchestration. These changes allow operators to implement finer grained access control than just "member" and "admin".

The identity panels (domains, projects, users, roles, groups) have also been converted to support RBAC at the view level. The identity panels have been moved from the admin dashboard into their own 'Identity' dashboard and accessibility is determined by policies alone. This is the first step toward consolidating the near duplicate content of the project and admin dashboards into single views supporting a wide range of roles.

==== UX Changes ====

In Juno, Horizon transitioned to utilizing Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Havana release.

==== JavaScript Libraries Extracted ====
As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

==== Conversion from LESS to SCSS ====
The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

=== Known Issues ===

==== Rendering issues in extensions ====

The conversion to utilizing Bootstrap v3 can cause content extensions written on top of Horizon to have rendering issues. Most of these are fixed by a simple CSS class name substitutions. These issues are primarily seen with buttons and panel content widths.

==== Online Compression ====

With the move to SCSS, there may be issues with utilizing online compression in non-DEBUG mode in Horizon. Offline compression continues to work as in previous releases.

==== Neutron L3 HA ====

The HA property is updateable in the UI, however, the migration itself fails on the agent.
https://bugs.launchpad.net/horizon/+bug/1378525

=== Upgrade Notes ===
* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

== OpenStack Identity (Keystone) ==

=== Key New Features ===

* Keystone now has experimental support for [http://docs.openstack.org/developer/keystone/configure_federation.html#keystone-as-an-identity-provider-idp Keystone-to-Keystone federation], where one instance acts as an Identity Provider, and the other a Service Provider.
* PKIZ is a new token provider available for users of PKI tokens, which simply adds zlib-based compression to traditional PKI tokens.
* The hashing algorithm used for PKI tokens has been made configurable (the default is still MD5, but the Keystone team recommends that deployments migrate to SHA256).
* Identity-driver-configuration-per-domain now supports Internet domain names of arbitrary hierarchical complexity (for example, <code>customer.cloud.example.com</code>).
* The LDAP identity backend now supports <code>description</code> as an attribute of users.
* Identity API v3 requests are now validated via JSON Schema.
* In the case of multiple identity backends, Keystone can now map arbitrary resource IDs to arbitrary backends.
* <code>keystoneclient.middleware.auth_token</code> has been moved into it's own repository, <code>keystonemiddleware.auth_token</code>.
* Identity API v3 now supports a discrete call to retrieve a service catalog, <code>GET /v3/auth/catalog</code>.
* Federated authentication events and local role assignment operations now result in CADF (audit) notifications.
* Keystone can now associate a given policy blob with one or more endpoints.
* Keystone now provides JSON Home documents on the root API endpoints in response to <code>Accept: application/json-home</code> headers.
* Hiding endpoints from client's service catalogs is now more easily manageable via <code>OS-EP-FILTER</code>.
* The credentials collection API is now filterable per associated user (<code>GET /v3/credentials?user_id={user_id}</code>).
* New, generic API endpoints are available for retrieving authentication-related data, such as a service catalog, available project scopes, and available domain scopes.
* Keystone now supports mapping the user <code>enabled</code> attribute to the <code>lock</code> attribute in LDAP (and inverting the corresponding boolean value accordingly).
* A CA certificate file is now configurable for LDAPS connections.
* The templated catalog backend now supports generating service catalogs for Identity API v3.
* Service names were added to the v3 service catalog.
* Services can now be filtered by name (<code> GET /v3/services?name={service_name}</code>).

=== Known Issues ===
==== LDAP paged search results don't work with python-ldap 2.4 ====
When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

==== LDAP paged search results don't work with python-ldap 2.4 ====

When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

A fix for this issue has been proposed, which is expected to be made available in a stable update for Juno. For more details see https://bugs.launchpad.net/keystone/+bug/1381768

=== Upgrade Notes ===

* Due to the simpler out-of-the-box experience, the default token provider is now UUID instead of PKI.
* Database migrations for releases prior to Havana have been dropped, meaning that you must upgrade to the Juno release from either a Havana or Icehouse deployment.
* A comprehensive list of all updated, deprecated or removed options in Keystone can be found at: http://docs.openstack.org/trunk/config-reference/content/keystone-conf-changes-master.html
** All <code>token_api</code> methods are now deprecated.
** LDAP configuration options that previously contained the deprecated <code>tenant</code> terminology have been superseded by options using the term <code>project</code>.
** Proxy methods from the identity backend to the assignment backend (created to provide backwards compatibility as a result of the split of the Assignment backend from the Identity backend), have been removed. This should only affect custom, out-of-tree API extensions.
** Loading authentication plugins solely by class name in <code>keystone.conf</code> is now deprecated in favor of loading them by <code>custom-method-name = custom_package.CustomClass</code> pairs, and then defining the sequence of authentication methods as a list (<code>methods = custom-method-name, password</code>).
** In-tree token drivers (<code>keystone.token.backends</code>) have been moved to <code>keystone.token.persistence.backends</code>. Proxy objects exist to maintain compatibility. If a non-default value is used, it is recommended the value of the <code>driver</code> option in the <code>[token]</code> section of <code>keystone.conf</code> is updated to use the new location.
* All KVS backends besides the <code>token</code> driver have been formally deprecated.
* LDAP/AD configuration: All configuration options containing the term "tenant" have been deprecated in favor of similarly named configuration options using the term "project" (for example, <code>tenant_id_attribute</code> has been replaced by <code>project_id_attribute</code>).

== OpenStack Network Service (Neutron) ==
=== Key New Features ===
* DB migration refactor and new timeline
* Distributed Virtual Router Support (DVR)
* Full IPV6 support for tenant networks
* High Availability for the L3 Agent
* ipset support for security groups in place of iptables (this option is configurable)
* L3 agent performance improvements
* Migration to oslo.messaging library for RPC communication.
* Security group rules for devices RPC call refactoring (a huge performance improvement)
* New Plugins supported in Juno include the following:
** A10 Networks LBaaS driver for the LBaaS V1 API
** Arista L3 routing plugin
** Big Switch L3 routing plugin
** Brocade L3 routing plugin
** Cisco APIC ML2 Driver (including a L3 routing plugin).
** Cisco CSR L3 routing plugin
** Freescale SDN ML2 Mechanism Driver
** Nuage Networks ML2 Mechanism Driver
** SR-IOV capable NIC ML2 Mechanism Driver

=== Known Issues ===
* This is the first release for DVR and HA L3. The Neutron team desires to designate these features as production ready in Kilo and requests that deployers test on non-critical workloads and report any issues.
* FWaaS is still labeled as experimental, as it does not allow you to have more than one FW per tenant.

=== Upgrade Notes ===
* DB migration from the previous releases (icehouse or havana)
** In Icehouse or Hanava releases, the db migration operation is optional. If your Neutron database is not stamped (i.e., there is the db migration version info), please make sure to "stamp icehouse" before running the upgrade db migration to Juno.
** To check if your database is stamped, run the following command:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> current
** If the output of the current version is '''None''', please run:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> stamp icehouse
** and then run the db migration for upgrading Juno:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> upgrade juno
* A list of all updated, deprecated or removed options in neutron can be found at: http://docs.openstack.org/trunk/config-reference/content/neutron-conf-changes-master.html
* Attribute level policies dependent on resources are not enforced anymore. Meaning that some older policies from Icehouse are not needed. (e.g. "get_port:binding:vnic_type": "rule:admin_or_owner").
* The following plugins are deprecated in Juno:
** Cisco Nexus Sub-Plugin (The Nexus 1000V Sub-Plugin is still retained and supported in Juno).
** Mellanox Plugin
** Ryu Plugin
*XML support in the API is deprecated. Users and deployers should migrate to JSON for API interactions as soon as possible since the XML support will be removed in the Kilo (2015.1) release.

== OpenStack Block Storage (Cinder) ==
=== Key New Features ===
* Support for Volume Replication.
* Support for Consistency Groups and Snapshots of Consistency Groups.
* Support for Volume Pools.
* Completion of i18n-enablement
* Honor Glance protected properties in Image Upload
* Enable ability to restrict bandwidth usage on volume-copy operations
* Add Volume Num Weigher Scheduling

=== New Drivers/Plugins ===
* Datera
* Fujitsu ETERNUS
* Fusion IO
* Hitachi HBSD
* Huawei
* Nimble
* Prophetstor
* Pure
* XtremIO
* Oracle ZFS

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Cinder can be found at: http://docs.openstack.org/trunk/config-reference/content/cinder-conf-changes-master.html
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.

== OpenStack Telemetry (Ceilometer) ==
=== Key New Features ===
* Support for partitioning metric collection load across horizontally scaled-out central agents
* New method of partitioning alarm evaluation load using [https://github.com/stackforge/tooz tooz] coordination, as opposed to a hand-crafted protocol
* Much improved SQLAlchemy storage performance & scalability, so that MySQL or PostgreSQL can be used as the metering store for PoCs or small deployments
* Support for hardware-oriented monitoring of IPMI sensors via notifications from either Ironic or a new standalone agent
* More flexible & efficient SNMP monitoring:
** batching queries for multiple SNMP metrics into a single call to each daemon
** dynamic discovery of nodes deployed by TripleO for SNMP polling
** the ability to more easily extend the range of SNMP metrics that ceilometer gathers
** the ability to derive new metrics from arithmetic transformations applied to multiple primary metrics
* Option to split off the alarms persistence into a separate database
* Option to use notifications instead of RPC for metering messages
* Metering of Neutron networking services: LBaaS, FWaaS & VPNaaS
* New XenAPI compute inspector
* Support for persisting events via the MongoDB & Hbase storage drivers (previously limited to SQLAlchemy)
* Support for per-device metering of instance disks
* Use of ceilometer as a collector for os-profiler data
* New Telemetry section of the [http://docs.openstack.org/admin-guide-cloud/content/ch_admin-openstack-telemetry.html Cloud Administrator Guide]

=== Known Issues ===
* [https://bugs.launchpad.net/ceilometer/+bug/1381600 1381600] The new <code>ceilometer-agent-ipmi</code> fails to emit any samples when it encounters unparseable data from <code>ipmitool</code>.

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in ceilometer can be found at: http://docs.openstack.org/trunk/config-reference/content/ceilometer-conf-changes-master.html

== OpenStack Orchestration (Heat) ==
=== Key New Features ===

* Recovery from failures during stack updates
* API to cancel and roll back an in-progress stack update
* Implementation of new resource types:
** OS::Glance::Image
** OS::Heat::SwiftSignal
*** Provides the option to store Wait Condition (and Software Deployment) data in Swift
** OS::Heat::StructuredDeployments
*** Groups code for multiple lifecycle events into a single deployment resource
** OS::Heat::SoftwareDeployments
*** Provides a way of avoiding circular dependencies when deploying an interdependent cluster of servers
** OS::Heat::SoftwareComponent
** OS::Nova::ServerGroup
** OS::Sahara::NodeGroupTemplate
** OS::Sahara::ClusterTemplate
* Remember the previously-supplied parameters when updating a stack
* Improved scalability
* Improved visibility into trees of nested stacks

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in heat can be found at: http://docs.openstack.org/trunk/config-reference/content/heat-conf-changes-master.html

== OpenStack Database service (Trove) ==
=== Key New Features ===
* Support for Asynchronous Replication (master-slave replicas) between provisioned mysql instances.
* Introduction of a new Clustering API with initial support for MongoDB clusters.
* Support for deploying Trove on an OpenStack solution that is using Neutron for networking. Prior to this, only nova-network was supported.
* Support for provisioning PostgreSQL datastore instances.
* Backup and Restore support for Couchbase.
* Support to optionally restrict the Cinder backend used for Trove volumes.
* Support for defining custom datastore configuration parameters in the Trove database (using mgmt API).
* The ability to list all datastore types and versions in a single call

=== Other Incremental Improvements===
* Logging audit to improve log levels throughout the trove components.
* The extensions loading mechanism was improved by adding support for stevedore.
* The ability to support volumes for data is now on a per datastore bases.
* Created and updated timestamps and instance count were added to configuration groups list and details calls.

=== Known Issues ===

* [https://bugs.launchpad.net/trove/+bug/1333852 1333852]: Trove does not support flavor UUIDs -- the Trove flavors API requires flavors with a numerical ID in order to be consistent with the API response for icehouse Trove.

=== Upgrade Notes ===

None yet

== OpenStack Data Processing (Sahara) ==

=== New Key Features ===

* Data processing UI was fully merged into OpenStack Dashboard (horizon).
* Support of CDH 5.x was added.
* Support of Apache Spark was added. Supported versions are 0.9.1 and 1.0.0. Elastic data processing (EDP) engine was refactored a lot to support non-Oozie workflow engines.
* Support of Apache Hadoop 2.4.1 was added in addition to existing 1.2.1 and 2.3.0. Version 2.3.0 is deprecated in Juno.
* Support of multi region deployments.
* Hadoop Swift authentication using [http://docs.openstack.org/developer/sahara/userdoc/advanced.configuration.guide.html#domain-usage-for-swift-proxy-users keystone trust mechanism]. Now Hadoop can access data in Swift without storing credentials in config files.
* [http://docs.openstack.org/developer/sahara/userdoc/configuration.guide.html#sahara-notifications-configuration Ceilometer integration] was added. Now Sahara notifies Ceilometer about all cluster state changes.
* Cluster provisioning error handling was improved. If something goes wrong during scaling, cluster will rollback to original state.
* Added ability to [http://docs.openstack.org/developer/sahara/userdoc/features.html#security-group-management specify security groups for a node group]. Also Sahara could automatically create security group with only required ports open.
* Implemented [http://docs.openstack.org/developer/sahara/userdoc/features.html#running-sahara-in-distributed-mode distributed mode] for Sahara: sahara-all process is decoupled into sahara-api and sahara-engine. You can run several instances of sahara-api and sahara-engine on different hosts. Note that the feature implementation is considered to be in alpha-state.

=== Known Issues ===

* [https://bugs.launchpad.net/sahara/+bug/1271349 Bug 1271349]: Sahara requires root privileges to access VMs via namespaces.

=== Upgrade Notes ===

==== Main binary renamed to sahara-all ====

Please, note that you should use `sahara-all` instead of `sahara-api` to start
the All-In-One Sahara.

==== sahara.conf upgrade ====

We've migrated from custom auth_token middleware config options to the common
config options. To update your config file you should replace the following
old config opts with the new ones.

* "os_auth_protocol", "os_auth_host", "os_auth_port" -> "[keystone_authtoken]/auth_uri" and "[keystone_authtoken]/identity_uri"
* "os_admin_username" -> "[keystone_authtoken]/admin_user"
* "os_admin_password" -> "[keystone_authtoken]/admin_password"
* "os_admin_tenant_name" -> "[keystone_authtoken]/admin_tenant_name"

We've replaced oslo code from sahara.openstack.common.db by usage of oslo.db library.

Also sqlite database is not supported anymore. Please use MySQL or PostgreSQL
db backends for Sahara. Sqlite support was dropped because it doesn't support
(and not going to support, see http://www.sqlite.org/omitted.html) ALTER
COLUMN and DROP COLUMN commands required for DB migrations between versions.

You can find more info about config file options in Sahara repository in file
"etc/sahara/sahara.conf.sample".

==== Sahara Dashboard was merged into OpenStack Dashboard ====

The Sahara Dashboard is not available in Juno release. Instead it's
functionality is provided by OpenStack Dashboard out of the box.
The Sahara UI is available in OpenStack Dashboard in
"Project" -> "Data Processing" tab.

Note that you have to properly register Sahara in Keystone in
order for Sahara UI in the Dashboard to work.

==== VM user name changed for HEAT infrastructure engine ====

We've updated HEAT infrastructure engine ("infrastructure_engine=heat") to
use the same rules for instance user name as in direct engine. Before the
change user name for VMs created by Sahara using HEAT engine was always
'ec2-user'. Now user name is taken from the image registry as it is described
in the documentation.

Note, this change breaks Sahara backward compatibility for clusters created
using HEAT infrastructure engine before the change. Clusters will continue to
operate, but it is not recommended to perform scale operation over them.

==== Anti affinity implementation changed ====

Starting with Juno release anti affinity feature is implemented using server
groups. There should not be much difference in Sahara behavior from user
perspective, but there are internal changes:

* Server group object will be created if anti affinity feature is enabled.
* New implementation doesn't allow several affected instances on the same host even if they don't have common processes. So, if anti affinity enabled for 'datanode' and 'tasktracker' processes, previous implementation allowed to have instance with 'datanode' process and other instance with 'tasktracker' process on one host. New implementation guarantees that instances will be on different hosts.

Note, new implementation will be applied for new clusters only. Old implementation will be applied if user scales cluster created in Icehouse.

== OpenStack Documentation ==

* This release, the OpenStack Foundation funded a five-day book sprint to write the new [http://docs.openstack.org/arch-design/content/arch-guide-how-this-book-is-organized.html OpenStack Architecture Design Guide]. It offers architectures for general purpose, compute-focused, storage-focused, network-focused, multi-site, hybrid, massively scalable, and specialized clouds.
* The Install Guides have had a lot of clean up and standardization: uses common message queue (RabbitMQ), replaces openstack-config (crudini) commands with config file editing for improved learning opportunities and consistency, references a generic SQL database so that MariaDB or MySQL can be substituted, and replaces auth_port and auth_protocol with identity_uri, and auth_host with auth_uri throughout. The Install Guides are thoroughly tested on each distribution and continuously published until the official release packages are available to everyone.
* The [http://docs.openstack.org/high-availability-guide/content/index.html High Availability Guide] now has a separate review team and has moved into a separate repository.
* The [http://docs.openstack.org/security-guide/content/ Security Guide] now has a specialized review team and has moved into a separate repository.
* The long-form API reference documents have been re-purposed to focus on the [http://developer.openstack.org/api-ref.html API Complete Reference].
* The User Guide now contains Database Service for OpenStack information.
* The Command-Line Reference has been updated with new client releases and now contains additional chapters for the common OpenStack client, the trove-manage client, and the Data processing client (sahara).
* The [http://docs.openstack.org/admin-guide-cloud/content/ OpenStack Cloud Administrator Guide] now contains information about Telemetry (ceilometer).

Translations:ReleaseNotes/Liberty/133/en

2016-08-13T02:10:02Z

FuzzyBot: Importing a new version from external source

* Added "ENROLL" hardware state, which is the default state for newly created nodes.
* Added "abort" verb, which allows a user to interrupt certain operations while they are in progress.
* Improved query and filtering support in the REST API.
* Added support for CORS middleware.

Translations:User:Smaffulli/5/en

2016-08-13T02:09:42Z

FuzzyBot: Importing a new version from external source

Integer non posuere orci. Donec adipiscing congue suscipit. Praesent egestas sagittis tortor, sit amet porta lorem porttitor sed. Vivamus varius posuere scelerisque. Suspendisse viverra lacus volutpat orci tincidunt mollis. In vestibulum magna nibh. Morbi imperdiet mi mauris. In vulputate iaculis laoreet. Donec vel nisl ac leo ullamcorper tempor id sed orci. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.

Translations:ReleaseNotes/Liberty/39/en

2016-08-13T02:09:40Z

FuzzyBot: Importing a new version from external source

* Pass down the instance name to Ironic driver (https://blueprints.launchpad.net/nova/+spec/pass-down-instance-name-to-ironic-driver)

Translations:PRC Kilo Hackaton/12/en

2016-08-13T02:09:38Z

FuzzyBot: Importing a new version from external source

== Team Build Event ==

PRC Kilo Hackaton/en

2016-08-13T02:09:38Z

FuzzyBot: Importing a new version from external source

<languages />
Huawei and Intel are pleased to host a hackathon ! Come join other OpenStackers to make Kilo a grand success!
Come build your personal network. Learn tips and tricks and gain a better understanding by working closely with others.
Cores and PTLs will be on standby to review patches and vote for merges.

= Kilo Bug Fix Fest =

* Focus: Nova and Neutron
* Location: Shanghai, Intel ZZ site
* Dates: April 13-15, 2015
* Hosts: Huawei and Intel
* Capacity: 20

Sign UP on the [https://etherpad.openstack.org/p/prc_kilo_nova_neutron_hackathon etherpad]!

== Directions ==

Coming soon

== Local Attractions ==

Coming soon

== Dinner plans ==

Possible venues: Coming-soon

Add your name to the [https://etherpad.openstack.org/p/prc_kilo_nova_neutron_hackathon etherpad]!

== Team Build Event ==

On April 13 we're planning a networking event. Sign-up adding your name to he [https://etherpad.openstack.org/p/prc_kilo_nova_neutron_hackathon etherpad]!

= Resources for developers =

List of Release Candidate bugs are most likely to appear on kilo-rc1 pages: https://launchpad.net/openstack/+milestone/kilo-rc1

- https://launchpad.net/nova/+milestone/kilo-rc1
- https://launchpad.net/neutron/+milestone/kilo-rc1
- https://launchpad.net/horizon/+milestone/kilo-rc1
- Etc

Translations:User:Smaffulli/2/en

2016-08-13T02:09:34Z

FuzzyBot: Importing a new version from external source

Proin sed molestie dui, eget ornare risus. Nunc ut dolor imperdiet, molestie augue non, volutpat est. Mauris convallis eget dolor et sagittis. Aenean suscipit porta libero quis gravida. Donec aliquam est id mauris consectetur hendrerit. Pellentesque mollis consectetur ligula, at pretium sapien dapibus in. Quisque quis porta ipsum.

Translations:ReleaseNotes/Liberty/36/en

2016-08-13T02:09:29Z

FuzzyBot: Importing a new version from external source

===== Hyper-V =====

Translations:OpenStack Upstream Training/Info/6/en

2016-08-13T02:09:01Z

FuzzyBot: Importing a new version from external source

== Target Audience ==

Translations:ReleaseNotes/Liberty/Page display title/en

2016-08-13T02:08:48Z

FuzzyBot: Importing a new version from external source

ReleaseNotes/Liberty

Translations:ReleaseNotes/Liberty/139/en

2016-08-13T02:08:39Z

FuzzyBot: Importing a new version from external source

* Newly created nodes default to the new ENROLL state. Previously, nodes defaulted to AVAILABLE, which could lead to hardware being exposed prematurely to Nova.
* The addition of API version headers in Kilo means that any client wishing to interact with the Liberty API must pass the appropriate version string in each HTTP request. Current API version is 1.14.

Translations:ReleaseNotes/Liberty/141/en

2016-08-13T02:08:16Z

FuzzyBot: Importing a new version from external source

=== New Features ===

Translations:OpenStack Upstream Training/Info/34/en

2016-08-13T02:08:04Z

FuzzyBot: Importing a new version from external source

https://etherpad.openstack.org/p/kilo-upstream-training

Translations:ReleaseNotes/Liberty/135/en

2016-08-13T02:08:00Z

FuzzyBot: Importing a new version from external source

* Added a new BootInterface for hardware drivers, which splits functionality out of the DeployInterface.
* iLO virtual media drivers can work without Swift.
* Added Cisco IMC driver.
* Added OCS Driver.
* Added UCS Driver.
* Added Wake-On-Lan Power Driver.
* ipmitool driver supports IPMI v1.5.
* Added support to SNMP driver for “APC MasterSwitchPlus” series PDU’s.
* pxe_ilo driver now supports UEFI Secure Boot (previous releases of theiLO driver only supported this for agent_ilo and iscsi_ilo).
* Added Virtual Media support to iRMC Driver.
* Added BIOS configuration to DRAC Driver.
* PXE drivers now support GRUB2.

Translations:ReleaseNotes/Kilo/45/en

2016-08-13T02:07:45Z

FuzzyBot: Importing a new version from external source

* Adding image member throws 500 when the member name is longer than 255 characters. https://bugs.launchpad.net/glance/+bug/1424038
* Glance v2 API is incompatible with v1 API for owner change. https://bugs.launchpad.net/glance/+bug/1420008
* Glance scrubber doesn't work when registry operates in trusted-auth mode. https://bugs.launchpad.net/glance/+bug/1439666

Translations:ReleaseNotes/Kilo/48/en

2016-08-13T02:06:30Z

FuzzyBot: Importing a new version from external source

== OpenStack Dashboard (Horizon) ==

Translations:ReleaseNotes/Liberty/125/en

2016-08-13T02:06:30Z

FuzzyBot: Importing a new version from external source

* Django 1.8 is now supported, and Django 1.7 is our minimum supported version (https://blueprints.launchpad.net/horizon/+spec/drop-django14-support).
* Database-backed sessions will likely not persist across upgrades due to a change in their structure (https://github.com/openstack/django_openstack_auth/commit/8c64de92f4148d85704b10ea1f7bc441db2ddfee and https://github.com/openstack/horizon/commit/ee2771ab1a855342089abe5206fc6a5071a6d99e).
* Horizon no longer uses QUnit in testing, and it has been removed from our requirements (https://blueprints.launchpad.net/horizon/+spec/replace-qunit-tests-with-jasmine).
* Horizon now has multiple configuration options for the default web URL (<code>WEBROOT</code>), static file location (<code>STATIC_ROOT</code>) and static file URL (<code>STATIC_URL</code>) in its settings files.
* Themes have moved location from <code>openstack_dashboard/static/themes</code>, to <code>openstack_dashboard/themes</code>. Paths may need to be updated accordingly. Furthermore, Horizon is aligning closer with Bootstrap markup, and themes should be built around this ideology; see the top bar and side navigation for details.
* The deprecated <code>OPENSTACK_QUANTUM_NETWORK</code> configuration option has been removed. If you still use it, replace it with <code>OPENSTACK_NEUTRON_NETWORK</code>
* There is now an <code>OPENSTACK_NOVA_EXTENSIONS_BLACKLIST</code> option in the settings, to disable selected extensions for performance reasons (https://github.com/openstack/horizon/commit/18f4b752b8653c9389f8b0471eccaa0659707ebe).
* Trove and Sahara panels now reside in <code>openstack_dashboard/contrib</code>. This is to provide separation for reviews provided mostly by the service teams. In the future, these panels may become plugins rather than being kept in Horizon (https://blueprints.launchpad.net/horizon/+spec/plugin-sanity).
* Horizon requires both a <code>volume</code> and <code>volumev2</code> endpoint for Cinder, even if only using v2.

Translations:OpenStack Upstream Training/Info/11/en

2016-08-13T02:06:18Z

FuzzyBot: Importing a new version from external source

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

Translations:ReleaseNotes/Liberty/88/en

2016-08-13T02:06:10Z

FuzzyBot: Importing a new version from external source

=== Deprecated Features ===

Translations:ReleaseNotes/Kilo/158/en

2016-08-13T02:05:46Z

FuzzyBot: Importing a new version from external source

'''dnsmasq: CommandFilter, dnsmasq, root'''

Translations:ReleaseNotes/Liberty/114/en

2016-08-13T02:05:46Z

FuzzyBot: Importing a new version from external source

* Plugin improvements – Horizon auto discovers JavaScript files for inclusion, and now has mechanisms for pluggable SCSS and Django template overrides.

Translations:ReleaseNotes/Liberty/69/en

2016-08-13T02:05:23Z

FuzzyBot: Importing a new version from external source

==== heat_template_version: 2015-10-15 ====

Translations:ReleaseNotes/Liberty/140/en

2016-08-13T02:05:11Z

FuzzyBot: Importing a new version from external source

== OpenStack Key Manager (Barbican) ==

Translations:OpenStack Upstream Training/Info/19/en

2016-08-13T02:04:53Z

FuzzyBot: Importing a new version from external source

=== How OpenStack is made (3h including 1h30 exercises) ===

Translations:ReleaseNotes/Kilo/15/en

2016-08-13T02:04:32Z

FuzzyBot: Importing a new version from external source

* As a beta release, EC support is nearly fully feature complete, but it is lacking support for some features (like multi-range reads) and has not had a full performance characterization. This feature relies on ssync for durability. Deployers are urged to do extensive testing and not deploy production data using an erasure code storage policy.

Translations:ReleaseNotes/Liberty/52/en

2016-08-13T02:04:20Z

FuzzyBot: Importing a new version from external source

== OpenStack Identity (Keystone) ==

Translations:OpenStack Upstream Training/Info/9/en

2016-08-13T02:03:49Z

FuzzyBot: Importing a new version from external source

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

Translations:ReleaseNotes/Liberty/33/en

2016-08-13T02:03:27Z

FuzzyBot: Importing a new version from external source

* Moved to using ''os-brick'' library for Libvirt volume drivers allowing sharing of logic for volume discovery and removal between Nova and Cinder (http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/use-os-brick-library.html).
* Added ''live_migration_completion_timeout'' and ''live_migration_progress_timeout'' configuration keys to assist with capping the maximum time a live migration should be allowed to run, particularly when progress has halted (https://launchpad.net/bugs/1429220).
* Added logic to manage and scale the maximum downtime setting during live migration to provide larger guest sizes with a better chance of completing migration successfully (https://launchpad.net/bugs/1429220).
* Limit parallel live migrations in progress (https://launchpad.net/bugs/1478108).
* Optionally enable the scaling of VirtIO queues in relation to guest vCPUs if the ''hw_vif_multiqueue_enabled'' image property is set to 'true' (default: 'false') providing enhanced network performance for guests with more than one vCPU, many concurrent connections, and/or relatively large packet sizes (http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/libvirt-virtiomq.html).
* Allow admin to set guest ''Administrator''/''root'' password if QEMU guest agent is installed and enabled via the ''hw_qemu_guest_agent'' image property (http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/libvirt-set-admin-password.html).
* New VIF type to allow routing VM data instead of bridging it (https://blueprints.launchpad.net/nova/+spec/vif-type-tap)
* Add support for InfiniBand SR-IOV for libvirt virtualization (https://blueprints.launchpad.net/nova/+spec/vif-driver-ib-passthrough)
* Add MacVTap as new virtual interface type for libvirt virtualization (https://blueprints.launchpad.net/nova/+spec/libvirt-macvtap-vif)
* Consolidate FS-style libvirt drivers (https://blueprints.launchpad.net/nova/+spec/consolidate-libvirt-fs-volume-drivers)
* EMC ScaleIO Data Client (SDC) Libvirt Volume Driver (https://blueprints.launchpad.net/nova/+spec/emc-sdc-libvirt-volume-driver)
* Implementation of remote FS driver based on `rsync` for libvirt (https://blueprints.launchpad.net/nova/+spec/remote-fs-driver)
* Virtuozzo containers boot from volume (https://blueprints.launchpad.net/nova/+spec/virtuozzo-container-boot-from-volume)
* Add HGST volume type support w/os-brick (https://blueprints.launchpad.net/nova/+spec/add-os-brick-volume-driver-hgst-solutions)
* virtio-net multiqueue (partial) (https://blueprints.launchpad.net/nova/+spec/libvirt-virtio-net-multiqueue)

Translations:ReleaseNotes/Juno/52/en

2016-08-13T02:03:15Z

FuzzyBot: Importing a new version from external source

Administrators now have the ability to evacuate instances off hypervisors which can aid in system maintenance by providing a mechanism to migrate all instances to other hosts.

Translations:ReleaseNotes/Liberty/148/en

2016-08-13T02:03:15Z

FuzzyBot: Importing a new version from external source

* Added support for uploading signed images. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/image-signing-and-verification-support.html .
* Scrubbing of images in parallel is now possible. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/scrub-images-in-parallel.html .
* The health of a Glance node can be monitored using the healthcheck middleware. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/healtcheck-middleware.html .
* The EXPERIMENTAL Artifacts API is now available for use. Please note, it is subject to change in the future until it becomes a standard API.
* S3 store now has proxy support. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/http-proxy-support-for-s3.html .
* Swift store now has v3 authentication support.
* python-glanceclient now support some advanced aspects of keystone sessions.
* python-glanceclient now supports tags for Metadata Definition Catalog.

ReleaseNotes/Juno/en

2016-08-13T02:03:15Z

FuzzyBot: Importing a new version from external source

<languages />

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]

[[Category:Juno|Release Note]]
[[Category:Release Note|Juno]]
= OpenStack 2014.2 (Juno) Release Notes =

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== General Upgrade Notes ==

* The simplejson package is an optional requirement in most projects, therefore it's not listed in all project's requirements.txt file. However, if you're using it, e.g. better performance with python 2.6 on RHEL 6, then you will need simplejson >= 2.2.0. See https://bugs.launchpad.net/oslo-incubator/+bug/1361230 for details.

== OpenStack Object Storage (Swift) ==

=== Key New Features ===

The Juno integrated release includes three releases of OpenStack Swift: 2.0.0, 2.1.0, and 2.2.0. The changelog for these releases is available at https://github.com/openstack/swift/blob/2.2.0.rc1/CHANGELOG#L1-L173. Please refer to that document for release details.

Important new features are highlighted below. Please read the CHANGELOG and associated documentation.

* Storage policies
* Keystone v3 support
* Server-side account-to-account copy
* Better partition placement when adding a new server, zone, or region.
* Zero-copy GET responses using splice()
* Parallel object auditor

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

As always, you can upgrade your Swift cluster with no downtime for end-users. Please refer to sample config files and documentation before every release.

* There have been some logging changes that need to be called out. In all cases, well-behaved log processors will not be affected.
** Storage node (account, container, object) logs now have the PID logged at the end of the log line.
** Object daemons now send a user-agent string with their full name (e.g. "obj" is now "object").
* Once an additional storage policy has been enabled, downgrading to Swift pre-2.0.0 will cause any additional storage policies to become unavailable.
* As part of an effort to eventually update the default port to swift to an non-IANA-assigned range, bind_port is now a required setting. Anyone currently explicitly setting the ports will not be affected. However, if you do not currently set the ports, please ensure that your *_server.conf has bind_port set to match your ring as part of your upgrade.
* Note that storage policies include a new daemon, the container-reconciler.
* TempURL default allowed methods config setting now also allows POST and DELETE. This means tempurls can be created for these verbs. It does not affect any existing tempurls.
* A list of all updated, deprecated or removed options in swift can be found at: http://docs.openstack.org/trunk/config-reference/content/swift-conf-changes-master.html

== OpenStack Compute (Nova) ==

===Instance features===

* Allow users to specify an image to use for rescue instead of the original base image. [https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/allow-image-to-be-specified-during-rescue specification]
* Allow images to specify if a config drive should be used. [https://blueprints.launchpad.net/nova/+spec/config-drive-image-property launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/config-drive-image-property specification]
* Give users and administrators the ability to control the vCPU topology exposed to guests via flavors. [https://blueprints.launchpad.net/nova/+spec/virt-driver-vcpu-topology launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-vcpu-topology specification]
* Attach All Local Disks During Rescue. [https://blueprints.launchpad.net/nova/+spec/rescue-attach-all-disks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rescue-attach-all-disks specification]

===Networking===

* Improve the nova-network code to allow per-network settings. [https://blueprints.launchpad.net/nova/+spec/better-support-for-multiple-networks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/better-support-for-multiple-networks specification]
* Allow deployers to add hooks which are informed as soon as networking information for an instance is changed. [https://blueprints.launchpad.net/nova/+spec/instance-network-info-hook launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/instance-network-info-hook specification]
* Enable nova instances to be booted up with SR-IOV neutron ports. [https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/pci-passthrough-sriov specification]
* Permit VMs to attach multiple interfaces to one network. [https://blueprints.launchpad.net/nova/+spec/multiple-if-1-net launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/nfv-multiple-if-1-net specification]

===Scheduling===

* Extensible Resource Tracking. The set of resources tracked by nova is hard coded, this change makes that extensible, which will allow plug-ins to track new types of resources for scheduling. [https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/extensible-resource-tracking specification]
* Allow a host to be evacuated, but with the scheduler selecting destination hosts for the instances moved. [https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/find-host-and-evacuate-instance specification]
* Add support for host aggregates to scheduler filters. launchpad: [https://blueprints.launchpad.net/nova/+spec/per-aggregate-disk-allocation-ratio disk]; [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-instances-per-host instances]; and [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-io-ops-per-host IO ops] [http://specs.openstack.org/openstack/nova-specs/specs/juno/per-aggregate-filters specification]

===Other===

* i18n Enablement for Nova, turn on the lazy translation support from Oslo i18n and updating Nova to adhere to the restrictions this adds to translatable strings. [https://blueprints.launchpad.net/nova/+spec/i18n-enablement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/i18n-enablement specification]
* Offload periodic task sql query load to a slave sql server if one is configured. [https://blueprints.launchpad.net/nova/+spec/juno-slaveification launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/juno-slaveification specification]
* Only update the status of a host in the sql database when the status changes, instead of every 60 seconds. [https://blueprints.launchpad.net/nova/+spec/on-demand-compute-update launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/on-demand-compute-update specification]
* Include status information in API listings of hypervisor hosts. [https://blueprints.launchpad.net/nova/+spec/return-status-for-hypervisor-node launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/return-status-for-hypervisor-node specification]
* Allow API callers to specify more than one status to filter by when listing services. [https://blueprints.launchpad.net/nova/+spec/servers-list-support-multi-status launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/servers-list-support-multi-status specification]
* Add quota values to constrain the number and size of server groups a users can create. [https://blueprints.launchpad.net/nova/+spec/server-group-quotas launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/server-group-quotas specification]

===Hypervisor driver specific===

====Hyper-V====

* Support for differencing vhdx images. [https://blueprints.launchpad.net/nova/+spec/add-differencing-vhdx-resize-support launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-differencing-vhdx-resize-support specification]
* Support for console serial logs. [https://blueprints.launchpad.net/nova/+spec/hyper-v-console-log launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-console-log specification]
* Support soft reboot. [https://blueprints.launchpad.net/nova/+spec/hyper-v-soft-reboot launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-soft-reboot specification]

====Ironic====

* Add a virt driver for Ironic. [https://blueprints.launchpad.net/nova/+spec/add-ironic-driver launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-ironic-driver specification]

====libvirt====

* Performance improvements to listing instances on modern libvirts. [https://blueprints.launchpad.net/nova/+spec/libvirt-domain-listing-speedup launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-domain-listing-speedup specification]
* Allow snapshots of network backed disks. [https://blueprints.launchpad.net/nova/+spec/libvirt-volume-snap-network-disk launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-volume-snap-network-disk specification]
* Enable qemu memory balloon statistics for ceilometer reporting. [https://blueprints.launchpad.net/nova/+spec/enabled-qemu-memballoon-stats launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/enabled-qemu-memballoon-stats specification]
* Add support for handing back unused disk blocks to the underlying storage system. [https://blueprints.launchpad.net/nova/+spec/libvirt-disk-discard-option launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-disk-discard-option specification]
* Meta-data about an instance is now recorded in the libvirt domain XML. This is intended to help administrators while debugging problems. [https://blueprints.launchpad.net/nova/+spec/libvirt-driver-domain-metadata launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-driver-domain-metadata specification]
* Support namespaces for LXC containers. [https://blueprints.launchpad.net/nova/+spec/libvirt-lxc-user-namespaces launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-lxc-user-namespaces specification]
* Copy-on-write cloning for RBD-backed disks. [https://blueprints.launchpad.net/nova/+spec/rbd-clone-image-handler launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rbd-clone-image-handler specification]
* Expose interactive serial consoles. [https://blueprints.launchpad.net/nova/+spec/serial-ports launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/serial-ports specification]
* Allow controlled shutdown of guest operating systems during VM power off. [https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/user-defined-shutdown specification]
* Intelligent NUMA node placement for guests. [https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-numa-placement specification]

====vmware====

* Move the vmware driver to using the oslo vmware helper library. [https://blueprints.launchpad.net/nova/+spec/use-oslo-vmware launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/use-oslo-vmware specification]
* Add support for network interface hot plugging to vmware. [https://blueprints.launchpad.net/nova/+spec/vmware-hot-plug launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-hot-plug specification]
* Refactor the vmware driver's spawn functionality to be more maintainable. This work was internal, but is mentioned here because it significantly improves the supportability of the VMWare driver. [https://blueprints.launchpad.net/nova/+spec/vmware-spawn-refactor launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-spawn-refactor specification]

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

* A list of all updated, deprecated or removed options in Nova can be found at: http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html
* The nova-manage flavor subcommand is deprecated in Juno and will be removed in the 2015.1 (K) release: https://review.openstack.org/#/c/86122/
* https://review.openstack.org/#/c/102212/
* Minimum required libvirt version is now 0.9.11: https://review.openstack.org/#/c/58494/
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.
* Debug log output in python-novaclient has [https://review.openstack.org/#/c/98443/ changed slightly] to improve readability. The sha1 hash of the keystone token is now printed instead of the token itself - greatly shortening the amount of content being printed while still retaining the ability to determine token mismatch scenarios. In addition, some extra '\n' characters that were being added are removed. ''Double-check any log parsers!''
* libvirt.volume_drivers config param for nova.conf is deprecated, to be removed in the Lxxxx release. In general, this should affect only a small number of developers working on drivers. If this is you, the recommended approach is to continue your work inside a nova tree.

== OpenStack Image Service (Glance) ==
=== Key New Features ===
* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Key New Features ===

* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Known Issues ===

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.
* glance workers will now be equal to the number of CPUs available by default if not explicitly specified in glance-api.conf and/or glance-registry.conf
** There is no upgrade impact to glance-api workers since glance-api.conf previously hard-coded the workers value to 1 so anyone upgrading to tihs will still get whatever value was set in glance-api.conf prior to this change. There is an upgrade impact to the glance-registry workers since glance-registry.conf did not hard-code the workers value to 1 before this change. So anyone upgrading to this change that does not have workers specified in glance-registry.conf will now be running multiple workers by default when they restart the glance registry service.

== OpenStack Dashboard (Horizon) ==

=== Key New Features ===

==== Sahara ====

The OpenStack Data Processing project (Sahara) was formally included into the integrated release in Juno and Horizon includes broad support for managing your data processing. You can specify and build clusters to utilize several data types with user specified jobs while tracking the progress of those jobs.

==== Neutron Features ====

Neutron added several new features in Juno, including:
* DVR (Distributed Virtual Routing)
* L3 HA support
* IPv6 subnet modes

Horizon provides support for these new features with the Juno release. These features provide much greater flexibility in specifying software defined networks.

An existing feature in Neutron that Horizon now supports is the MAC learning extension.

==== Glance Features ====
In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

==== Cinder Features ====
In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

Other features of the Cinder API not previously supported by Horizon added in Juno include:
* Enabling resetting the state of a snapshot
* Enabling resetting the state of a volume
* Supporting upload-to-image
* Volume retype
* QoS (quality of service) support

==== Trove ====
Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Another addition is support for utilizing and restoring from incremental database backups.

To improve support for Neutron based clouds, when creating a database instance, the user can now specify the NIC for the database instance on creation allowing direct access to the instance by the user.

==== Nova ====

The new nova instance actions panel provides a list of all actions taken on all instances in the current project allowing users to view resulting errors or actions taken by other users on those instances.

Administrators now have the ability to evacuate instances off hypervisors which can aid in system maintenance by providing a mechanism to migrate all instances to other hosts.

==== Improved Plugin Support ====

The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:

* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

==== Enhanced RBAC support ====

In an ongoing effort to support richer role based access control (RBAC) in Horizon, the views for several more services were enhanced with RBAC checks to determine user access to actions. The newly supported services are compute, network and orchestration. These changes allow operators to implement finer grained access control than just "member" and "admin".

The identity panels (domains, projects, users, roles, groups) have also been converted to support RBAC at the view level. The identity panels have been moved from the admin dashboard into their own 'Identity' dashboard and accessibility is determined by policies alone. This is the first step toward consolidating the near duplicate content of the project and admin dashboards into single views supporting a wide range of roles.

==== UX Changes ====

In Juno, Horizon transitioned to utilizing Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Havana release.

==== JavaScript Libraries Extracted ====
As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

==== Conversion from LESS to SCSS ====
The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

=== Known Issues ===

==== Rendering issues in extensions ====

The conversion to utilizing Bootstrap v3 can cause content extensions written on top of Horizon to have rendering issues. Most of these are fixed by a simple CSS class name substitutions. These issues are primarily seen with buttons and panel content widths.

==== Online Compression ====

With the move to SCSS, there may be issues with utilizing online compression in non-DEBUG mode in Horizon. Offline compression continues to work as in previous releases.

==== Neutron L3 HA ====

The HA property is updateable in the UI, however, the migration itself fails on the agent.
https://bugs.launchpad.net/horizon/+bug/1378525

=== Upgrade Notes ===

* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

== OpenStack Identity (Keystone) ==

=== Key New Features ===

* Keystone now has experimental support for [http://docs.openstack.org/developer/keystone/configure_federation.html#keystone-as-an-identity-provider-idp Keystone-to-Keystone federation], where one instance acts as an Identity Provider, and the other a Service Provider.
* PKIZ is a new token provider available for users of PKI tokens, which simply adds zlib-based compression to traditional PKI tokens.
* The hashing algorithm used for PKI tokens has been made configurable (the default is still MD5, but the Keystone team recommends that deployments migrate to SHA256).
* Identity-driver-configuration-per-domain now supports Internet domain names of arbitrary hierarchical complexity (for example, <code>customer.cloud.example.com</code>).
* The LDAP identity backend now supports <code>description</code> as an attribute of users.
* Identity API v3 requests are now validated via JSON Schema.
* In the case of multiple identity backends, Keystone can now map arbitrary resource IDs to arbitrary backends.
* <code>keystoneclient.middleware.auth_token</code> has been moved into it's own repository, <code>keystonemiddleware.auth_token</code>.
* Identity API v3 now supports a discrete call to retrieve a service catalog, <code>GET /v3/auth/catalog</code>.
* Federated authentication events and local role assignment operations now result in CADF (audit) notifications.
* Keystone can now associate a given policy blob with one or more endpoints.
* Keystone now provides JSON Home documents on the root API endpoints in response to <code>Accept: application/json-home</code> headers.
* Hiding endpoints from client's service catalogs is now more easily manageable via <code>OS-EP-FILTER</code>.
* The credentials collection API is now filterable per associated user (<code>GET /v3/credentials?user_id={user_id}</code>).
* New, generic API endpoints are available for retrieving authentication-related data, such as a service catalog, available project scopes, and available domain scopes.
* Keystone now supports mapping the user <code>enabled</code> attribute to the <code>lock</code> attribute in LDAP (and inverting the corresponding boolean value accordingly).
* A CA certificate file is now configurable for LDAPS connections.
* The templated catalog backend now supports generating service catalogs for Identity API v3.
* Service names were added to the v3 service catalog.
* Services can now be filtered by name (<code> GET /v3/services?name={service_name}</code>).

=== Known Issues ===
==== LDAP paged search results don't work with python-ldap 2.4 ====
When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

==== LDAP paged search results don't work with python-ldap 2.4 ====

When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

A fix for this issue has been proposed, which is expected to be made available in a stable update for Juno. For more details see https://bugs.launchpad.net/keystone/+bug/1381768

=== Upgrade Notes ===

* Due to the simpler out-of-the-box experience, the default token provider is now UUID instead of PKI.
* Database migrations for releases prior to Havana have been dropped, meaning that you must upgrade to the Juno release from either a Havana or Icehouse deployment.
* A comprehensive list of all updated, deprecated or removed options in Keystone can be found at: http://docs.openstack.org/trunk/config-reference/content/keystone-conf-changes-master.html
** All <code>token_api</code> methods are now deprecated.
** LDAP configuration options that previously contained the deprecated <code>tenant</code> terminology have been superseded by options using the term <code>project</code>.
** Proxy methods from the identity backend to the assignment backend (created to provide backwards compatibility as a result of the split of the Assignment backend from the Identity backend), have been removed. This should only affect custom, out-of-tree API extensions.
** Loading authentication plugins solely by class name in <code>keystone.conf</code> is now deprecated in favor of loading them by <code>custom-method-name = custom_package.CustomClass</code> pairs, and then defining the sequence of authentication methods as a list (<code>methods = custom-method-name, password</code>).
** In-tree token drivers (<code>keystone.token.backends</code>) have been moved to <code>keystone.token.persistence.backends</code>. Proxy objects exist to maintain compatibility. If a non-default value is used, it is recommended the value of the <code>driver</code> option in the <code>[token]</code> section of <code>keystone.conf</code> is updated to use the new location.
* All KVS backends besides the <code>token</code> driver have been formally deprecated.
* LDAP/AD configuration: All configuration options containing the term "tenant" have been deprecated in favor of similarly named configuration options using the term "project" (for example, <code>tenant_id_attribute</code> has been replaced by <code>project_id_attribute</code>).

== OpenStack Network Service (Neutron) ==
=== Key New Features ===
* DB migration refactor and new timeline
* Distributed Virtual Router Support (DVR)
* Full IPV6 support for tenant networks
* High Availability for the L3 Agent
* ipset support for security groups in place of iptables (this option is configurable)
* L3 agent performance improvements
* Migration to oslo.messaging library for RPC communication.
* Security group rules for devices RPC call refactoring (a huge performance improvement)
* New Plugins supported in Juno include the following:
** A10 Networks LBaaS driver for the LBaaS V1 API
** Arista L3 routing plugin
** Big Switch L3 routing plugin
** Brocade L3 routing plugin
** Cisco APIC ML2 Driver (including a L3 routing plugin).
** Cisco CSR L3 routing plugin
** Freescale SDN ML2 Mechanism Driver
** Nuage Networks ML2 Mechanism Driver
** SR-IOV capable NIC ML2 Mechanism Driver

=== Known Issues ===
* This is the first release for DVR and HA L3. The Neutron team desires to designate these features as production ready in Kilo and requests that deployers test on non-critical workloads and report any issues.
* FWaaS is still labeled as experimental, as it does not allow you to have more than one FW per tenant.

=== Upgrade Notes ===
* DB migration from the previous releases (icehouse or havana)
** In Icehouse or Hanava releases, the db migration operation is optional. If your Neutron database is not stamped (i.e., there is the db migration version info), please make sure to "stamp icehouse" before running the upgrade db migration to Juno.
** To check if your database is stamped, run the following command:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> current
** If the output of the current version is '''None''', please run:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> stamp icehouse
** and then run the db migration for upgrading Juno:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file <your plugin config file> upgrade juno
* A list of all updated, deprecated or removed options in neutron can be found at: http://docs.openstack.org/trunk/config-reference/content/neutron-conf-changes-master.html
* Attribute level policies dependent on resources are not enforced anymore. Meaning that some older policies from Icehouse are not needed. (e.g. "get_port:binding:vnic_type": "rule:admin_or_owner").
* The following plugins are deprecated in Juno:
** Cisco Nexus Sub-Plugin (The Nexus 1000V Sub-Plugin is still retained and supported in Juno).
** Mellanox Plugin
** Ryu Plugin
*XML support in the API is deprecated. Users and deployers should migrate to JSON for API interactions as soon as possible since the XML support will be removed in the Kilo (2015.1) release.

== OpenStack Block Storage (Cinder) ==
=== Key New Features ===
* Support for Volume Replication.
* Support for Consistency Groups and Snapshots of Consistency Groups.
* Support for Volume Pools.
* Completion of i18n-enablement
* Honor Glance protected properties in Image Upload
* Enable ability to restrict bandwidth usage on volume-copy operations
* Add Volume Num Weigher Scheduling

=== New Drivers/Plugins ===
* Datera
* Fujitsu ETERNUS
* Fusion IO
* Hitachi HBSD
* Huawei
* Nimble
* Prophetstor
* Pure
* XtremIO
* Oracle ZFS

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Cinder can be found at: http://docs.openstack.org/trunk/config-reference/content/cinder-conf-changes-master.html
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.

== OpenStack Telemetry (Ceilometer) ==
=== Key New Features ===
* Support for partitioning metric collection load across horizontally scaled-out central agents
* New method of partitioning alarm evaluation load using [https://github.com/stackforge/tooz tooz] coordination, as opposed to a hand-crafted protocol
* Much improved SQLAlchemy storage performance & scalability, so that MySQL or PostgreSQL can be used as the metering store for PoCs or small deployments
* Support for hardware-oriented monitoring of IPMI sensors via notifications from either Ironic or a new standalone agent
* More flexible & efficient SNMP monitoring:
** batching queries for multiple SNMP metrics into a single call to each daemon
** dynamic discovery of nodes deployed by TripleO for SNMP polling
** the ability to more easily extend the range of SNMP metrics that ceilometer gathers
** the ability to derive new metrics from arithmetic transformations applied to multiple primary metrics
* Option to split off the alarms persistence into a separate database
* Option to use notifications instead of RPC for metering messages
* Metering of Neutron networking services: LBaaS, FWaaS & VPNaaS
* New XenAPI compute inspector
* Support for persisting events via the MongoDB & Hbase storage drivers (previously limited to SQLAlchemy)
* Support for per-device metering of instance disks
* Use of ceilometer as a collector for os-profiler data
* New Telemetry section of the [http://docs.openstack.org/admin-guide-cloud/content/ch_admin-openstack-telemetry.html Cloud Administrator Guide]

=== Known Issues ===
* [https://bugs.launchpad.net/ceilometer/+bug/1381600 1381600] The new <code>ceilometer-agent-ipmi</code> fails to emit any samples when it encounters unparseable data from <code>ipmitool</code>.

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in ceilometer can be found at: http://docs.openstack.org/trunk/config-reference/content/ceilometer-conf-changes-master.html

== OpenStack Orchestration (Heat) ==
=== Key New Features ===

* Recovery from failures during stack updates
* API to cancel and roll back an in-progress stack update
* Implementation of new resource types:
** OS::Glance::Image
** OS::Heat::SwiftSignal
*** Provides the option to store Wait Condition (and Software Deployment) data in Swift
** OS::Heat::StructuredDeployments
*** Groups code for multiple lifecycle events into a single deployment resource
** OS::Heat::SoftwareDeployments
*** Provides a way of avoiding circular dependencies when deploying an interdependent cluster of servers
** OS::Heat::SoftwareComponent
** OS::Nova::ServerGroup
** OS::Sahara::NodeGroupTemplate
** OS::Sahara::ClusterTemplate
* Remember the previously-supplied parameters when updating a stack
* Improved scalability
* Improved visibility into trees of nested stacks

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in heat can be found at: http://docs.openstack.org/trunk/config-reference/content/heat-conf-changes-master.html

== OpenStack Database service (Trove) ==
=== Key New Features ===
* Support for Asynchronous Replication (master-slave replicas) between provisioned mysql instances.
* Introduction of a new Clustering API with initial support for MongoDB clusters.
* Support for deploying Trove on an OpenStack solution that is using Neutron for networking. Prior to this, only nova-network was supported.
* Support for provisioning PostgreSQL datastore instances.
* Backup and Restore support for Couchbase.
* Support to optionally restrict the Cinder backend used for Trove volumes.
* Support for defining custom datastore configuration parameters in the Trove database (using mgmt API).
* The ability to list all datastore types and versions in a single call

=== Other Incremental Improvements===
* Logging audit to improve log levels throughout the trove components.
* The extensions loading mechanism was improved by adding support for stevedore.
* The ability to support volumes for data is now on a per datastore bases.
* Created and updated timestamps and instance count were added to configuration groups list and details calls.

=== Known Issues ===

* [https://bugs.launchpad.net/trove/+bug/1333852 1333852]: Trove does not support flavor UUIDs -- the Trove flavors API requires flavors with a numerical ID in order to be consistent with the API response for icehouse Trove.

=== Upgrade Notes ===

None yet

== OpenStack Data Processing (Sahara) ==

=== New Key Features ===

* Data processing UI was fully merged into OpenStack Dashboard (horizon).
* Support of CDH 5.x was added.
* Support of Apache Spark was added. Supported versions are 0.9.1 and 1.0.0. Elastic data processing (EDP) engine was refactored a lot to support non-Oozie workflow engines.
* Support of Apache Hadoop 2.4.1 was added in addition to existing 1.2.1 and 2.3.0. Version 2.3.0 is deprecated in Juno.
* Support of multi region deployments.
* Hadoop Swift authentication using [http://docs.openstack.org/developer/sahara/userdoc/advanced.configuration.guide.html#domain-usage-for-swift-proxy-users keystone trust mechanism]. Now Hadoop can access data in Swift without storing credentials in config files.
* [http://docs.openstack.org/developer/sahara/userdoc/configuration.guide.html#sahara-notifications-configuration Ceilometer integration] was added. Now Sahara notifies Ceilometer about all cluster state changes.
* Cluster provisioning error handling was improved. If something goes wrong during scaling, cluster will rollback to original state.
* Added ability to [http://docs.openstack.org/developer/sahara/userdoc/features.html#security-group-management specify security groups for a node group]. Also Sahara could automatically create security group with only required ports open.
* Implemented [http://docs.openstack.org/developer/sahara/userdoc/features.html#running-sahara-in-distributed-mode distributed mode] for Sahara: sahara-all process is decoupled into sahara-api and sahara-engine. You can run several instances of sahara-api and sahara-engine on different hosts. Note that the feature implementation is considered to be in alpha-state.

=== Known Issues ===

* [https://bugs.launchpad.net/sahara/+bug/1271349 Bug 1271349]: Sahara requires root privileges to access VMs via namespaces.

=== Upgrade Notes ===

==== Main binary renamed to sahara-all ====

Please, note that you should use `sahara-all` instead of `sahara-api` to start
the All-In-One Sahara.

==== sahara.conf upgrade ====

We've migrated from custom auth_token middleware config options to the common
config options. To update your config file you should replace the following
old config opts with the new ones.

* "os_auth_protocol", "os_auth_host", "os_auth_port" -> "[keystone_authtoken]/auth_uri" and "[keystone_authtoken]/identity_uri"
* "os_admin_username" -> "[keystone_authtoken]/admin_user"
* "os_admin_password" -> "[keystone_authtoken]/admin_password"
* "os_admin_tenant_name" -> "[keystone_authtoken]/admin_tenant_name"

We've replaced oslo code from sahara.openstack.common.db by usage of oslo.db library.

Also sqlite database is not supported anymore. Please use MySQL or PostgreSQL
db backends for Sahara. Sqlite support was dropped because it doesn't support
(and not going to support, see http://www.sqlite.org/omitted.html) ALTER
COLUMN and DROP COLUMN commands required for DB migrations between versions.

You can find more info about config file options in Sahara repository in file
"etc/sahara/sahara.conf.sample".

==== Sahara Dashboard was merged into OpenStack Dashboard ====

The Sahara Dashboard is not available in Juno release. Instead it's
functionality is provided by OpenStack Dashboard out of the box.
The Sahara UI is available in OpenStack Dashboard in
"Project" -> "Data Processing" tab.

Note that you have to properly register Sahara in Keystone in
order for Sahara UI in the Dashboard to work.

==== VM user name changed for HEAT infrastructure engine ====

We've updated HEAT infrastructure engine ("infrastructure_engine=heat") to
use the same rules for instance user name as in direct engine. Before the
change user name for VMs created by Sahara using HEAT engine was always
'ec2-user'. Now user name is taken from the image registry as it is described
in the documentation.

Note, this change breaks Sahara backward compatibility for clusters created
using HEAT infrastructure engine before the change. Clusters will continue to
operate, but it is not recommended to perform scale operation over them.

==== Anti affinity implementation changed ====

Starting with Juno release anti affinity feature is implemented using server
groups. There should not be much difference in Sahara behavior from user
perspective, but there are internal changes:

* Server group object will be created if anti affinity feature is enabled.
* New implementation doesn't allow several affected instances on the same host even if they don't have common processes. So, if anti affinity enabled for 'datanode' and 'tasktracker' processes, previous implementation allowed to have instance with 'datanode' process and other instance with 'tasktracker' process on one host. New implementation guarantees that instances will be on different hosts.

Note, new implementation will be applied for new clusters only. Old implementation will be applied if user scales cluster created in Icehouse.

== OpenStack Documentation ==

* This release, the OpenStack Foundation funded a five-day book sprint to write the new [http://docs.openstack.org/arch-design/content/arch-guide-how-this-book-is-organized.html OpenStack Architecture Design Guide]. It offers architectures for general purpose, compute-focused, storage-focused, network-focused, multi-site, hybrid, massively scalable, and specialized clouds.
* The Install Guides have had a lot of clean up and standardization: uses common message queue (RabbitMQ), replaces openstack-config (crudini) commands with config file editing for improved learning opportunities and consistency, references a generic SQL database so that MariaDB or MySQL can be substituted, and replaces auth_port and auth_protocol with identity_uri, and auth_host with auth_uri throughout. The Install Guides are thoroughly tested on each distribution and continuously published until the official release packages are available to everyone.
* The [http://docs.openstack.org/high-availability-guide/content/index.html High Availability Guide] now has a separate review team and has moved into a separate repository.
* The [http://docs.openstack.org/security-guide/content/ Security Guide] now has a specialized review team and has moved into a separate repository.
* The long-form API reference documents have been re-purposed to focus on the [http://developer.openstack.org/api-ref.html API Complete Reference].
* The User Guide now contains Database Service for OpenStack information.
* The Command-Line Reference has been updated with new client releases and now contains additional chapters for the common OpenStack client, the trove-manage client, and the Data processing client (sahara).
* The [http://docs.openstack.org/admin-guide-cloud/content/ OpenStack Cloud Administrator Guide] now contains information about Telemetry (ceilometer).

Translations:ReleaseNotes/Kilo/30/en

2016-08-13T02:03:13Z

FuzzyBot: Importing a new version from external source

* Support for generation 2 VMs: https://blueprints.launchpad.net/nova/+spec/hyper-v-generation-2-vms
* Support for SMB based volumes, to sit along side existing iSCSI volume support: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/hyper-v-smbfs-volume-support.html
* Support for x509 certificate based key pairs: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/keypair-x509-certificates.html
* Host power actions now work with Hyper-V: https://blueprints.launchpad.net/nova/+spec/hyper-v-host-power-actions

Translations:ReleaseNotes/Liberty/98/en

2016-08-13T02:02:29Z

FuzzyBot: Importing a new version from external source

N/A

Translations:ReleaseNotes/Liberty/154/en

2016-08-13T02:02:13Z

FuzzyBot: Importing a new version from external source

=== New Features ===

Translations:ReleaseNotes/Liberty/124/en

2016-08-13T02:02:02Z

FuzzyBot: Importing a new version from external source

=== Upgrade Notes ===

Translations:ReleaseNotes/Liberty/143/en

2016-08-13T02:01:59Z

FuzzyBot: Importing a new version from external source

=== Upgrade Notes ===

Translations:ReleaseNotes/Liberty/107/en

2016-08-13T02:01:56Z

FuzzyBot: Importing a new version from external source

=== Deprecated Features ===