ReleaseNotes1507

Differences between revisions 1 and 40 (spanning 39 versions)
⇤ ← Revision 1 as of 2014-04-16 09:48:06 →
Size: 4522
Editor: james-page
Comment:
← Revision 40 as of 2015-04-23 08:29:47 → ⇥
Size: 5550
Editor: james-page
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== General Charm Updates == ## page was copied from ServerTeam/OpenStackCharms/ReleaseNotes1501
<<TableOfContents>>
Line 3: Line 4:
=== Icehouse support for 12.04 and 14.04 === == Summary ==
Line 5: Line 6:
All OpenStack charms now support deployment of OpenStack 2014.1 (Icehouse) on Ubuntu 12.04 LTS and Ubuntu 14.04 LTS; 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
 * 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 [[ServerTeam/OpenStackCharms/ReleaseNotes1501|15.01]] charm release notes in terms of charm features delivered since the last Ubuntu release.

== New Charm Features ==

=== OpenStack Kilo support for 14.04 and 15.04 ===

All !OpenStack charms now support deployment of !OpenStack 2015.1 (Kilo) on Ubuntu 14.04 LTS and Ubuntu 15.04; this support includes the following charms:
Line 9: Line 39:
 * cinder-ceph
Line 18: Line 49:
 * neutron-api
 * neutron-openvswitch
Line 19: Line 52:
To deploy OpenStack Icehouse on Ubuntu 12.04, use the 'openstack-origin' configuration option, for example: To deploy !OpenStack Kilo on Ubuntu 14.04, use the 'openstack-origin' configuration option, for example:
Line 24: Line 57:
  openstack-origin: cloud:precise-icehouse   openstack-origin: cloud:trusty-kilo
Line 29: Line 62:
OpenStack Icehouse is provided as the default OpenStack release on Ubuntu 14.04 so no additional configuration is required in 14.04 deployments. !OpenStack Kilo is provided as the default !OpenStack release on Ubuntu 15.04 so no additional configuration is required in 15.04 deployments.
Line 31: Line 64:
=== Active/Active and SSL RabbitMQ === === Neutron - Distributed Virtual Router ===
Line 33: Line 66:
All OpenStack charms now feature support for use with the rabbitmq-server charm configured in native active/active HA mode. To deploy RabbitMQ in this mode: The neutron-api charm now has a enable-dvr option to turn on Distributed Virtual Routing. When this is enabled each Compute Node will provide North/South DNAT (floating IP traffic) as well as East/West L3 forwarding (traffic between VM in the same tenant), North/South SNAT still goes through the neutron gateway.
Line 35: Line 68:
{{{
juju deploy rabbitmq-server
juju add-unit -n 1 rabbitmq-server
}}}		 Prerequisites:
 * Compute having external connectivity
 * l2-population is enabled
 * Openstack relealse >= Juno
 * enable-l3ha is disabled
Line 40: Line 74:
Charms should be related to the rabbitmq-server charm as before: More details of DVR can be found [[https://wiki.openstack.org/wiki/Neutron/DVR|here]]
Line 42: Line 76:
{{{
juju add-relation cinder rabbitmq-server
}}}		 === Neutron - Router High Availability ===
Line 46: Line 78:
The rabbitmq-server charm also now supports use of SSL connections, for example: The neutron-api charm now has a enable-l3ha option. If this option is enabled then subsequent routers are created with the 'ha' flag set. This will enable automatic failover of a router should the gateway unit that it resides on fail.
Line 48: Line 80:
{{{
juju set rabbitmq-server ssl=only
}}}		 Prerequisites:
 * More than 1 neutron gateway node
 * l2-population is disabled
 * Openstack relealse >= Juno
 * enable-dvr is disabled
Line 52: Line 86:
This will force all RabbitMQ connections to operate over SSL. Options for the ssl config flag include: More details on L3 HA can be found [[https://wiki.openstack.org/wiki/Neutron/L3_High_Availability_VRRP|Here]]
Line 54: Line 88:
 * 'only': configure RabbitMQ server over a SSL port only.
 * 'off': configure RabbitMQ server over a non-SSL port only.
 * 'both': configure RabbitMQ server with SSL and non-SSL ports.		 === Percona Cluster - Improved HA failure detection ===
Line 58: Line 90:
'''NOTE''': This feature is not yet compatible with RabbitMQ server in native Active/Active HA mode. 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.
Line 60: Line 92:
=== SSL MySQL === === Deployment from source ===
Line 62: Line 94:
TBC '''EXPERIMENTAL FEATURE'''
Line 64: Line 96:
=== PostgreSQL === The following charms now have support for deploying OpenStack directly from git repositories:
Line 66: Line 98:
Support for use of PostgreSQL as the database for OpenStack components has been added to the OpenStack charms. This feature can be used by deploying the postgresql charm and relating services to it - for example:  * cinder
 * keystone
 * glance
 * nova-cloud-controller
 * nova-compute
 * neutron-api
 * quantum-gateway
 * neutron-openvswitch
Line 68: Line 107:
{{{
juju deploy postgresql
juju add-relation cinder postgresql:db
}}}		 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 73: Line 109:
The nova-cloud-controller charm requires access to two databases (neutron and nova), so the procedure is slightly different: Further deploy from source enablement is expected during the 15.07 charm development cycle.
Line 75: Line 111:
{{{
juju add-relation nova-cloud-controller:pgsql-nova-db postgresql:db
juju add-relation nova-cloud-controller:pgsql-neutron-db postgresql:db
}}}		 === Monitoring ===
Line 80: Line 113:
'''NOTE''': Its not possible to switch an existing MySQL deployment to PostgreSQL - the charms will error and fail-safe if you try todo this.
Line 82: Line 114:
=== Upgrading 12.04 deployments to Icehouse === == Deprecation Notices ==
Line 84: Line 116:
'''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. === quantum-gateway ===
Line 86: Line 118:
Existing Havana and Grizzly deployments of OpenStack on Ubuntu 12.04 can be upgraded to Icehouse by issuing: 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 88: Line 120:
{{{
juju upgrade-charm <charm-name>
juju set <charm-name> openstack-origin=cloud:precise-icehouse
}}}		 === MySQL HA with Ceph ===
Line 93: Line 122:
for each OpenStack charm in your deployment. Services which cannot be upgraded directly from Grizzly->Icehouse will be stepped automatically through the Havana release first. 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 95: Line 124:
== New Charm Features == 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 97: Line 126:
=== Neutron - Modular Layer 2 plugin === 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 99: Line 128:
The nova-cloud-controller, nova-compute and quantum-gateway charms will deploy the Modular Layer 2 (ml2) plugin, using the Open vSwitch L2 driver and GRE tunnelling, by default for Icehouse. === hacluster - default transport ===
Line 101: Line 130:
Existing Havana deployments using the older Open vSwitch (ovs) plugin will be automatically migrated to the ml2 plugin on upgrade. For the 15.04 charm release, the hacluster charm will continue to use multicast as its default transport option for cluster communications.
Line 103: Line 132:
=== Neutron - Enabled Extensions === 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 105: Line 134:
The following extensions/drivers have been enabled for Icehouse deployments: === Deployments without using the neutron-api charm ===
Line 107: Line 136:
 * Metering
 * Load Balancing as-a Service - using the default haproxy implementation.
 * Firewall as-a Service - using the default iptables implementation
 * VPN as-a Service - using OpenSwan IPSec VPN.		 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.07 this will switch to False which will disable the management of neutron services and config by the nova-compute charm. The neutron-api service should be deployed to run and manage the neutron-server service and if ovs is being used then the neutron-openvswitch subordinate should be deployed and attatched to the nova-compute service.
Line 112: Line 138:
=== Swift - default middleware === == Bugs Fixed ==
Line 114: Line 140:
The following middleware has been added to the default swift-proxy pipeline for OpenStack Icehouse:

 * gatekeeper
 * staticweb
 * bulk
 * slo - static large objects
 * dlo - dynamic large objects
 * tempurl
 * formpost
 * container-quotas
 * account-quotas
 * container_sync

In addition, container versioning has also been enabled in the swift-storage charm.

For more details on these features, please refer to the [[http://docs.openstack.org/developer/swift/middleware.html|upstream documentation]].		 For the full list of bugs resolved for the 15.04 release please refer to https://launchpad.net/charms/+milestone/15.04

Contents

  1. Summary
  2. New Charm Features
    1. OpenStack Kilo support for 14.04 and 15.04
    2. Neutron - Distributed Virtual Router
    3. Neutron - Router High Availability
    4. Percona Cluster - Improved HA failure detection
    5. Deployment from source
    6. Monitoring
  3. Deprecation Notices
    1. quantum-gateway
    2. MySQL HA with Ceph
    3. hacluster - default transport
    4. Deployments without using the neutron-api charm
  4. Bugs Fixed

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

OpenStack Kilo support for 14.04 and 15.04

All OpenStack charms now support deployment of OpenStack 2015.1 (Kilo) on Ubuntu 14.04 LTS and Ubuntu 15.04; this support includes the following charms:

  • keystone
  • cinder
  • cinder-ceph
  • glance
  • nova-cloud-controller
  • nova-compute
  • quantum-gateway
  • swift-proxy
  • swift-storage
  • ceilometer
  • ceilometer-agent
  • heat
  • neutron-api
  • neutron-openvswitch

To deploy OpenStack Kilo on Ubuntu 14.04, use the 'openstack-origin' configuration option, for example: 

cat > config.yaml << EOF
nova-cloud-controller:
  openstack-origin: cloud:trusty-kilo
EOF
juju deploy --config config.yaml nova-cloud-controller

OpenStack Kilo is provided as the default OpenStack release on Ubuntu 15.04 so no additional configuration is required in 15.04 deployments.

Neutron - Distributed Virtual Router

The neutron-api charm now has a enable-dvr option to turn on Distributed Virtual Routing. When this is enabled each Compute Node will provide North/South DNAT (floating IP traffic) as well as East/West L3 forwarding (traffic between VM in the same tenant), North/South SNAT still goes through the neutron gateway.

Prerequisites:

  • Compute having external connectivity
  • l2-population is enabled

  • Openstack relealse >= Juno

  • enable-l3ha is disabled

More details of DVR can be found here

Neutron - Router High Availability

The neutron-api charm now has a enable-l3ha option. If this option is enabled then subsequent routers are created with the 'ha' flag set. This will enable automatic failover of a router should the gateway unit that it resides on fail.

Prerequisites:

  • More than 1 neutron gateway node
  • l2-population is disabled

  • Openstack relealse >= Juno

  • enable-dvr is disabled

More details on L3 HA can be found Here

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.

Monitoring

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.

Deployments without using the neutron-api charm

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.07 this will switch to False which will disable the management of neutron services and config by the nova-compute charm. The neutron-api service should be deployed to run and manage the neutron-server service and if ovs is being used then the neutron-openvswitch subordinate should be deployed and attatched to the nova-compute service.

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)