ReleaseNotes1507
|
Size: 4522
Comment:
|
Size: 6447
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 * openstack-dashboard |
|
| Line 19: | Line 53: |
| 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 58: |
| openstack-origin: cloud:precise-icehouse | openstack-origin: cloud:trusty-kilo |
| Line 29: | Line 63: |
| 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 65: |
| === Active/Active and SSL RabbitMQ === | '''NOTE''': In order to use Juju with Ubuntu 15.04, you'll have to use the 1.23 release which is currently in pre-release testing. |
| Line 33: | Line 67: |
| 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: | === 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 * Overlay network type is vxlan More details of DVR can be found [[https://wiki.openstack.org/wiki/Neutron/DVR|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 * Overlay network type is vlan, gre or vxlan More details on L3 HA can be found [[https://wiki.openstack.org/wiki/Neutron/L3_High_Availability_VRRP|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. === ØMQ? === === 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 === The Openstack charms can now be related to the nrpe charm to provide basic Nagios monitoring. To allow alert thresholds to be tweaked per service deploy each a nrpe subordinate charm per Openstack Service. e.g. |
| Line 36: | Line 123: |
| juju deploy rabbitmq-server juju add-unit -n 1 rabbitmq-server |
juju deploy nrpe nrpe-glance juju deploy nrpe nrpe-cinder juju deploy nagios juju deploy glance juju deploy cinder juju add-relation nrpe-glance glance juju add-relation nrpe-glance nagios juju add-relation nrpe-cinder cinder juju add-relation nrpe-cinder nagios |
| Line 40: | Line 134: |
| Charms should be related to the rabbitmq-server charm as before: | The thresholds can then tweaked: |
| Line 43: | Line 137: |
| juju add-relation cinder rabbitmq-server | juju set nrpe_glance "load=-w 2,2,2 -c 4,4,4" juju set nrpe_cinder "load=-w 4,4,4 -c 10,10,10" |
| Line 46: | Line 141: |
| The rabbitmq-server charm also now supports use of SSL connections, for example: | == Deprecation Notices == |
| Line 48: | Line 143: |
| {{{ juju set rabbitmq-server ssl=only }}} |
=== quantum-gateway === |
| Line 52: | Line 145: |
| This will force all RabbitMQ connections to operate over SSL. Options for the ssl config flag include: | 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 54: | Line 147: |
| * '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. |
=== MySQL HA with Ceph === |
| Line 58: | Line 149: |
| '''NOTE''': This feature is not yet compatible with RabbitMQ server in native Active/Active HA mode. | 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 60: | Line 151: |
| === SSL MySQL === | 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 62: | Line 153: |
| TBC | 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 64: | Line 155: |
| === PostgreSQL === | === hacluster - default transport === |
| Line 66: | Line 157: |
| 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: | For the 15.04 charm release, the hacluster charm will continue to use multicast as its default transport option for cluster communications. |
| Line 68: | Line 159: |
| {{{ juju deploy postgresql juju add-relation cinder postgresql:db }}} |
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 73: | Line 161: |
| The nova-cloud-controller charm requires access to two databases (neutron and nova), so the procedure is slightly different: | === Deployments without using the neutron-api charm === |
| Line 75: | Line 163: |
| {{{ juju add-relation nova-cloud-controller:pgsql-nova-db postgresql:db juju add-relation nova-cloud-controller:pgsql-neutron-db postgresql:db }}} |
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 80: | Line 165: |
| '''NOTE''': Its not possible to switch an existing MySQL deployment to PostgreSQL - the charms will error and fail-safe if you try todo this. | == Bugs Fixed == |
| Line 82: | Line 167: |
| === Upgrading 12.04 deployments to Icehouse === '''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 Havana and Grizzly deployments of OpenStack on Ubuntu 12.04 can be upgraded to Icehouse by issuing: {{{ juju upgrade-charm <charm-name> juju set <charm-name> openstack-origin=cloud:precise-icehouse }}} 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. == New Charm Features == === Neutron - Modular Layer 2 plugin === 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. Existing Havana deployments using the older Open vSwitch (ovs) plugin will be automatically migrated to the ml2 plugin on upgrade. === Neutron - Enabled Extensions === The following extensions/drivers have been enabled for Icehouse deployments: * 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. === Swift - default middleware === 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 |
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
- openstack-dashboard
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.
NOTE: In order to use Juju with Ubuntu 15.04, you'll have to use the 1.23 release which is currently in pre-release testing.
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
- Overlay network type is vxlan
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
- Overlay network type is vlan, gre or vxlan
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.
ØMQ?
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
The Openstack charms can now be related to the nrpe charm to provide basic Nagios monitoring. To allow alert thresholds to be tweaked per service deploy each a nrpe subordinate charm per Openstack Service. e.g.
juju deploy nrpe nrpe-glance juju deploy nrpe nrpe-cinder juju deploy nagios juju deploy glance juju deploy cinder juju add-relation nrpe-glance glance juju add-relation nrpe-glance nagios juju add-relation nrpe-cinder cinder juju add-relation nrpe-cinder nagios
The thresholds can then tweaked:
juju set nrpe_glance "load=-w 2,2,2 -c 4,4,4" juju set nrpe_cinder "load=-w 4,4,4 -c 10,10,10"
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)