ReleaseNotes1507
|
Size: 6522
Comment:
|
← Revision 67 as of 2016-06-20 13:04:30 ⇥
Size: 4931
Comment: Drop Ubuntu - that's kinda obvious
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was copied from TrustyTahr/ReleaseNotes/OpenStackCharms ## page was renamed from TrustyTahr/ReleaseNote/OpenStackCharms == General Charm Updates == |
## page was renamed from UbuntuOpenStack/OpenStackCharms/ReleaseNotes1507 ## page was renamed from ServerTeam/OpenStackCharms/ReleaseNotes1507 ## page was copied from ServerTeam/OpenStackCharms/ReleaseNotes1504 ## page was copied from ServerTeam/OpenStackCharms/ReleaseNotes1501 <<TableOfContents>> |
| Line 5: | Line 7: |
| === OpenStack Juno support for 14.04 and 14.10 === | == Summary == |
| Line 7: | Line 9: |
| All !OpenStack charms now support deployment of !OpenStack 2014.2 (Juno) on Ubuntu 14.04 LTS and Ubuntu 14.10; this support includes the following charms: |
The 15.07 OpenStack Charm release includes updates for the following charms: * ceilometer * ceilometer-agent * ceph * ceph-radosgw * cinder * cinder-ceph * glance * hacluster * heat |
| Line 10: | Line 21: |
| * neutron-api * neutron-openvswitch * nova-cloud-controller * nova-compute * openstack-dashboard * quantum-gateway * rabbitmq-server * swift-proxy * swift-storage * percona-cluster == Upgrading == === General === To upgrade an existing deployment to the latest charm version simply use the 'upgrade-charm' command, e.g.: {{{ juju upgrade-charm cinder }}} === Neutron Gateway === The quantum-gateway charm has been renamed 'neutron-gateway' for the 15.07 charm release; to upgrade existing quantum-gateway charm deployments please use: {{{ juju upgrade-charm --switch cs:trusty/neutron-gateway quantum-gateway }}} This will switch the deployment of the quantum-gateway charm to the new charm name. == New Charm Features == === Improved HA deployment support === The !OpenStack charms have been updated to use a new feature of Juju called 'leadership-election'; this allows a charm to discover early in its life cycle whether its a) going to have peers and b) the leader of those peers. With this feature, the charms support deployment of HA configuration in a single shot, removing the requirement to deploy charms and relations sequentially or in phases. '''NOTE:''' Use of this feature requires Juju >= 1.24. '''NOTE:''' Backwards compatibility with earlier Juju versions not supporting leadership election is maintained, but deploying HA configurations in a single shot is not supported in this configuration. '''NOTE:''' If deploying percona-cluster with Juju < 1.24 min-cluster-size needs to be set to the size of the target cluster === Deployment from source === '''EXPERIMENTAL FEATURE''' The following charms now have support for deploying OpenStack directly from git repositories: |
|
| Line 11: | Line 71: |
| * keystone | |
| Line 14: | Line 75: |
| * quantum-gateway * swift-proxy * swift-storage * ceilometer * ceilometer-agent * heat |
|
| Line 21: | Line 76: |
| * neutron-gateway | |
| Line 22: | Line 78: |
| * nova-cell To deploy !OpenStack Juno on Ubuntu 14.04, use the 'openstack-origin' configuration option, for example: {{{ cat > config.yaml << EOF nova-cloud-controller: openstack-origin: cloud:trusty-juno EOF juju deploy --config config.yaml nova-cloud-controller }}} !OpenStack Juno is provided as the default !OpenStack release on Ubuntu 14.10 so no additional configuration is required in 14.10 deployments. === Upgrading 14.04 deployments to Juno === '''WARNING''': Upgrading an !OpenStack deployment is always a non-trivial process. The !OpenStack charms automate alot of the process, however always plan and test your upgrade prior to upgrading production !OpenStack environments. Existing Icehouse deployments of !OpenStack on Ubuntu 14.04 can be upgraded to Juno by issuing: {{{ juju upgrade-charm <charm-name> juju set <charm-name> openstack-origin=cloud:trusty-juno }}} for each !OpenStack charm in your deployment. == New Charm Features == === Worker Thread Optimization === Where appropriate, the !OpenStack charms will automatically configure appropriate worker values for API and RPC processes to optimize use of available CPU resources on deployed units. By default, this is set at twice the number of cores - however it can be tweaked using the worker-multiplier option provided by supporting charms: {{{ juju set neutron-api worker-multiplier=4 }}} the above example increases the default #cores x 2 to #cores x 4. === Network Segregation Configuration === The !OpenStack charms feature support for use of multiple networks for separation of traffic; specifically: * os-data-network: Data network for tenant network traffic supporting instances * os-admin-network: Admin network - used for Admin endpoint binding and registration in keystone * os-public-network: Public network - used for Public endpoint binding and registration in keystone * os-internal-network: Internal network - used for internal communication between OpenStack services and for Internal endpoint registration in keystone in addition the Ceph charms (ceph-osd, ceph) support splitting 'public' access traffic from 'cluster' admin and re-sync traffic, via the ceph-public-network and ceph-cluster-network configuration options. All network configuration options should be provided in standard CIDR format - for example 10.20.0.0/16. This feature should also support IPv6 networking as well, although this should be considered a technical preview for this release (see below). === IPv6 Support === NOTE: this feature only works as described under the Juno OpenStack release and should be considered a technical preview this cycle. A subset of the !OpenStack charms now have a feature to prefer IPv6 networking for binding API endpoints and service-to-service communication: * nova-cloud-controller * nova-compute * glance * keystone * ceph/ceph-osd * neutron-api * cinder |
|
| Line 91: | Line 80: |
| have been tested and are know to work in IPv6 configurations with the 'prefer-ipv6' configuration option enabled. | This feature is enabled by using the new 'openstack-origin-git' configuration option; this can be used to configure a minimal or expanded list of repositories to collate and install - see the README in each charm for specific details. |
| Line 93: | Line 82: |
| * swift-proxy * swift-storage |
For this release, shallow git clones are performed on all repositories, and full isolation of services deployed from source is maintained in Python virtual environments. |
| Line 96: | Line 84: |
| also have this flag, but currently require a patched version of swift to function in an IPv6 environment. There are also changes proposed to the mysql, percona-cluster and rabbitmq-server charms which should land soon to enable this feature in other !OpenStack supporting services. | == Deprecation Notices == |
| Line 98: | Line 86: |
| Further enablement work will be done next cycle to complete this support across the charms, and hopefully have full upstream support for using IPv6 with OpenStack as well. | === 15.10 - MySQL HA with Ceph === |
| Line 100: | Line 88: |
| === Neutron === | The original HA implementation of OpenStack used the MySQL charm in-conjunction with Ceph to provide a traditional active/passive shared block device HA mysql option. |
| Line 102: | Line 90: |
| The Neutron support in the !OpenStack charms has been refactored into two new charms: | Percona XtraDB Cluster, as provided by the percona-cluster charm, provides an active/active MySQL configuration with no requirement for a shared block device. |
| Line 104: | Line 92: |
| * neutron-api: Supporting API and central control operations. * neutron-openvswitch: Supporting deployment of the Neutron ML2 plugin with Open vSwitch on nova-compute nodes. |
Users of the original MySQL HA option should migrate to a Percona XtraDB Cluster deployment between now and the 15.10 charm release, where support for MySQL with Ceph will be removed. |
| Line 107: | Line 94: |
| These charms can be introduced into an existing !OpenStack deployment: | === 15.10 - hacluster - default transport === |
| Line 109: | Line 96: |
| {{{ juju deploy neutron-api juju deploy neutron-openvswitch juju add-relation neutron-api mysql juju add-relation neutron-api keystone juju add-relation neutron-api rabbitmq-server juju add-relation neutron-api quantum-gateway juju add-relation neutron-api neutron-openvswitch juju add-relation neutron-api nova-cloud-controller juju add-relation neutron-openvswitch rabbitmq-server juju add-relation neutron-openvswitch nova-compute }}} |
For the 15.04 charm release, the hacluster charm will continue to use multicast as its default transport option for cluster communications. |
| Line 122: | Line 98: |
| Use of these two new charms also allows split of message brokers so that Nova and Neutron can use separate RabbitMQ deployments. | Unicast is generally more universally usable across all Juju providers - we'll be switching the default for 15.10 including automatic migration and re-configuration of existing multicast clusters. Instructions will also be provided for users who wish to continue to use the multicast transport option. |
| Line 124: | Line 100: |
| Use of these two new charms supports some additional features not enabled in the deprecated neutron support in nova-cloud-controller, specifically: | '''NOTE: Originally planned for 15.07 release, deferred to 15.10''' |
| Line 126: | Line 102: |
| * Support for using the l2population driver for ARP table optimization at scale (l2-population configuration option - defaults to True). * Support for using VXLAN overlay networks instead of GRE (overlay-network-type configuration option - defaults to GRE). |
=== 15.10 - nova-cloud-controller and neutron-api charms === |
| Line 129: | Line 104: |
| === Nova Cells === | Management of neutron configuration and services will be removed from any nova-* charms for the 15.10 charm release. |
| Line 131: | Line 106: |
| The Nova charms now support deployment in Nova Cell configurations using the new nova-cell charm; See the nova-cell charm for details of how this works and how to use in a !OpenStack deployment. A complete guide to this feature with example juju-deployer configurations will be posted soon. | This means that the neutron-api principle charm needs to be deployed to run the neutron-server service and if openvswitch is being used then neutron-openvswitch subordinate charm needs to deployed and attached to the nova-compute charm. This is a fully supported migration path for existing deployments not using these charms. |
| Line 133: | Line 108: |
| === Clustering === | The nova-compute charm now has an option called 'manage-neutron-plugin-legacy-mode'. The default value for this option is True but as of 15.10 this will switch to False which will disable the management of neutron services by default. |
| Line 135: | Line 110: |
| The hacluster charm has gone through some significant re-factoring to support changing configuration options post deployment, supporting upgrades of existing single network, clustered deployments to multi-network clustered deployments. | == Bugs Fixed == |
| Line 137: | Line 112: |
| This charm also now supports direct configuration of the corosync bindiface and port in preference over any configuration provided from the principle charm its deployed with. Configuration of these options via the principle charm will be removed during the 15.04 cycle, users need to migrate to using the direct configuration options prior to the next stable release alongside 15.04. | For the full list of bugs resolved for the 15.07 release please refer to https://launchpad.net/charms/+milestone/15.07 |
Contents
Summary
The 15.07 OpenStack Charm release includes updates for the following charms:
- ceilometer
- ceilometer-agent
- ceph
- ceph-radosgw
- cinder
- cinder-ceph
- glance
- hacluster
- heat
- keystone
- neutron-api
- neutron-openvswitch
- nova-cloud-controller
- nova-compute
- openstack-dashboard
- quantum-gateway
- rabbitmq-server
- swift-proxy
- swift-storage
- percona-cluster
Upgrading
General
To upgrade an existing deployment to the latest charm version simply use the 'upgrade-charm' command, e.g.:
juju upgrade-charm cinder
Neutron Gateway
The quantum-gateway charm has been renamed 'neutron-gateway' for the 15.07 charm release; to upgrade existing quantum-gateway charm deployments please use:
juju upgrade-charm --switch cs:trusty/neutron-gateway quantum-gateway
This will switch the deployment of the quantum-gateway charm to the new charm name.
New Charm Features
Improved HA deployment support
The OpenStack charms have been updated to use a new feature of Juju called 'leadership-election'; this allows a charm to discover early in its life cycle whether its a) going to have peers and b) the leader of those peers. With this feature, the charms support deployment of HA configuration in a single shot, removing the requirement to deploy charms and relations sequentially or in phases.
NOTE: Use of this feature requires Juju >= 1.24.
NOTE: Backwards compatibility with earlier Juju versions not supporting leadership election is maintained, but deploying HA configurations in a single shot is not supported in this configuration.
NOTE: If deploying percona-cluster with Juju < 1.24 min-cluster-size needs to be set to the size of the target cluster
Deployment from source
EXPERIMENTAL FEATURE
The following charms now have support for deploying OpenStack directly from git repositories:
- cinder
- keystone
- glance
- nova-cloud-controller
- nova-compute
- neutron-api
- neutron-gateway
- neutron-openvswitch
- openstack-dashboard
This feature is enabled by using the new 'openstack-origin-git' configuration option; this can be used to configure a minimal or expanded list of repositories to collate and install - see the README in each charm for specific details.
For this release, shallow git clones are performed on all repositories, and full isolation of services deployed from source is maintained in Python virtual environments.
Deprecation Notices
15.10 - MySQL HA with Ceph
The original HA implementation of OpenStack used the MySQL charm in-conjunction with Ceph to provide a traditional active/passive shared block device HA mysql option.
Percona XtraDB Cluster, as provided by the percona-cluster charm, provides an active/active MySQL configuration with no requirement for a shared block device.
Users of the original MySQL HA option should migrate to a Percona XtraDB Cluster deployment between now and the 15.10 charm release, where support for MySQL with Ceph will be removed.
15.10 - hacluster - default transport
For the 15.04 charm release, the hacluster charm will continue to use multicast as its default transport option for cluster communications.
Unicast is generally more universally usable across all Juju providers - we'll be switching the default for 15.10 including automatic migration and re-configuration of existing multicast clusters. Instructions will also be provided for users who wish to continue to use the multicast transport option.
NOTE: Originally planned for 15.07 release, deferred to 15.10
15.10 - nova-cloud-controller and neutron-api charms
Management of neutron configuration and services will be removed from any nova-* charms for the 15.10 charm release.
This means that the neutron-api principle charm needs to be deployed to run the neutron-server service and if openvswitch is being used then neutron-openvswitch subordinate charm needs to deployed and attached to the nova-compute charm. This is a fully supported migration path for existing deployments not using these charms.
The nova-compute charm now has an option called 'manage-neutron-plugin-legacy-mode'. The default value for this option is True but as of 15.10 this will switch to False which will disable the management of neutron services by default.
Bugs Fixed
For the full list of bugs resolved for the 15.07 release please refer to https://launchpad.net/charms/+milestone/15.07
OpenStack/OpenStackCharms/ReleaseNotes1507 (last edited 2016-06-20 13:04:30 by james-page)