ReleaseNotes1507
Differences between revisions 21 and 35 (spanning 14 versions)
|
Size: 7285
Comment:
|
Size: 3145
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was copied from UtopicUnicorn/ReleaseNotes/OpenStackCharms ## page was copied from TrustyTahr/ReleaseNotes/OpenStackCharms ## page was renamed from TrustyTahr/ReleaseNote/OpenStackCharms == General Charm Updates == |
## page was copied from ServerTeam/OpenStackCharms/ReleaseNotes1501 <<TableOfContents>> |
| Line 6: | Line 4: |
| === OpenStack Juno support for 14.04 and 14.10 === | == Summary == |
| Line 8: | Line 6: |
| 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.04 OpenStack Charm release includes updates for the following charms: * ceilometer * ceilometer-agent * ceph * ceph-radosgw * cinder * cinder-ceph * glance * hacluster * heat |
| Line 11: | Line 18: |
| * neutron-api * neutron-openvswitch * nova-cloud-controller * nova-compute * openstack-dashboard * quantum-gateway * rabbitmq-server * swift-proxy * swift-storage * percona-cluster These release notes complement the [[ServerTeam/OpenStackCharms/ReleaseNotes1501|15.01]] charm release notes in terms of charm features delivered since the last Ubuntu release. == New Charm Features == === Neutron - Distributed Virtual Router === === Neutron - Router High Availability === === Percona Cluster - Improved HA failure detection === The percona-cluster charm now ensures that the access Virtual IP is always co-located with an active, up-to-date instance of Percona XtraDB Cluster. === Deployment from source === '''EXPERIMENTAL FEATURE''' The following charms now have support for deploying OpenStack directly from git repositories: |
|
| Line 12: | Line 48: |
| * keystone | |
| Line 15: | Line 52: |
| * neutron-api | |
| Line 16: | Line 54: |
| * swift-proxy * swift-storage * ceilometer * ceilometer-agent * heat * neutron-api |
|
| Line 23: | Line 55: |
| * nova-cell | |
| Line 25: | Line 56: |
| To deploy !OpenStack Juno on Ubuntu 14.04, use the 'openstack-origin' configuration option, for example: | 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 27: | Line 58: |
| {{{ cat > config.yaml << EOF nova-cloud-controller: openstack-origin: cloud:trusty-juno EOF juju deploy --config config.yaml nova-cloud-controller }}} |
Further deploy from source enablement is expected during the 15.07 charm development cycle. |
| Line 35: | Line 60: |
| !OpenStack Juno is provided as the default !OpenStack release on Ubuntu 14.10 so no additional configuration is required in 14.10 deployments. | == Deprecation Notices == |
| Line 37: | Line 62: |
| === Upgrading 14.04 deployments to Juno === | === quantum-gateway === |
| Line 39: | Line 64: |
| '''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. | 15.04 is the last release of the 'quantum-gateway' charm; for 15.07 it will be renamed 'neutron-gateway'. Migration instructions will be provided for 15.07 release. |
| Line 41: | Line 66: |
| Existing Icehouse deployments of !OpenStack on Ubuntu 14.04 can be upgraded to Juno by issuing: | === MySQL HA with Ceph === |
| Line 43: | Line 68: |
| {{{ juju upgrade-charm <charm-name> juju set <charm-name> openstack-origin=cloud:trusty-juno }}} |
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 48: | Line 70: |
| for each !OpenStack charm in your deployment. | 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 50: | Line 72: |
| == New Charm Features == | 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 52: | Line 74: |
| === Worker Thread Optimization === | === hacluster - default transport === |
| Line 54: | Line 76: |
| 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: | For the 15.04 charm release, the hacluster charm will continue to use multicast as its default transport option for cluster communications. |
| Line 56: | Line 78: |
| {{{ juju set neutron-api worker-multiplier=4 }}} |
Unicast is generally more universally usable across all Juju providers - we'll be switching the default for 15.07 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 60: | Line 80: |
| the above example increases the default #cores x 2 to #cores x 4. Note that you should ensure that your mysql service can deal with the associated increase in concurrent connections - the mysql charm has a max-connections option that allows you to tweak this. | === Neutron deployments without using the neutron-api charm === |
| Line 62: | Line 82: |
| === Network Segregation Configuration === | == Bugs Fixed == |
| Line 64: | Line 84: |
| 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. NOTE: this feature does not currently support IPv6 privacy extensions. In order for the charms to function correctly, privacy extensions must be disabled and a non-temporary address must be configured/available on your network interface. 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 * openstack-dashboard have been tested and are know to work in IPv6 configurations with the 'prefer-ipv6' configuration option enabled. * swift-proxy * swift-storage 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. 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. === Neutron === The Neutron support in the !OpenStack charms has been refactored into two new charms: * neutron-api: Supporting API and central control operations. * neutron-openvswitch: Supporting deployment of the Neutron ML2 plugin with Open vSwitch on nova-compute nodes. These charms can be introduced into an existing !OpenStack deployment: {{{ 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 }}} Use of these two new charms also allows split of message brokers so that Nova and Neutron can use separate RabbitMQ deployments. Use of these two new charms supports some additional features not enabled in the deprecated neutron support in nova-cloud-controller, specifically: * 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). NOTE: the quantum-gateway charm now includes two amqp interfaces, one for neutron and one for nova, for use in split broker deployments. In single broker deployments, both neutron and nova will use the default 'amqp' relation for messaging configuration. === Nova Cells === 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. === Clustering === 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. 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.04 release please refer to https://launchpad.net/charms/+milestone/15.04 |
Summary
The 15.04 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
These release notes complement the 15.01 charm release notes in terms of charm features delivered since the last Ubuntu release.
New Charm Features
Neutron - Distributed Virtual Router
Neutron - Router High Availability
Percona Cluster - Improved HA failure detection
The percona-cluster charm now ensures that the access Virtual IP is always co-located with an active, up-to-date instance of Percona XtraDB 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
- quantum-gateway
- neutron-openvswitch
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.
Further deploy from source enablement is expected during the 15.07 charm development cycle.
Deprecation Notices
quantum-gateway
15.04 is the last release of the 'quantum-gateway' charm; for 15.07 it will be renamed 'neutron-gateway'. Migration instructions will be provided for 15.07 release.
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.
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.07 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.
Neutron deployments without using the neutron-api charm
Bugs Fixed
For the full list of bugs resolved for the 15.04 release please refer to https://launchpad.net/charms/+milestone/15.04
OpenStack/OpenStackCharms/ReleaseNotes1507 (last edited 2016-06-20 13:04:30 by james-page)