ReleaseNotes1504
|
Size: 7547
Comment:
|
Size: 6447
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| The 15.01 OpenStack Charm release includes updates for the following charms: | The 15.04 OpenStack Charm release includes updates for the following charms: |
| Line 27: | Line 27: |
| * percona-cluster | |
| Line 28: | Line 29: |
| This release has mainly been focussed on bug fixing, however some new features have been introduced. | These release notes complement the [[ServerTeam/OpenStackCharms/ReleaseNotes1501|15.01]] charm release notes in terms of charm features delivered since the last Ubuntu release. |
| Line 32: | Line 33: |
| === Clustering === | === OpenStack Kilo support for 14.04 and 15.04 === |
| Line 34: | Line 35: |
| The trusty hacluster charm now supports running in multicast (default) and unicast modes, supporting use of this charm in environments where multicast UDP is not supported. To enable this feature: | 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: |
| Line 37: | Line 56: |
| juju set hacluster corosync_transport=unicast | cat > config.yaml << EOF nova-cloud-controller: openstack-origin: cloud:trusty-kilo EOF juju deploy --config config.yaml nova-cloud-controller |
| Line 40: | Line 63: |
| At this point in time the previous node entries for the multicast cluster have to be removed manually - to complete this action, do the following on one of the members of the cluster: | !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 [[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 43: | Line 123: |
| sudo crm node list | 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 46: | Line 134: |
| New unicast nodes will start at 1001; the original multicast node entries should be deleted using: | The thresholds can then tweaked: |
| Line 49: | Line 137: |
| sudo crm configure > delete <id> |
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 53: | Line 141: |
| The trusty hacluster charm now supports a new ‘debug’ configuration option to increase the verbosity of logging from corosync and pacemaker. | == Deprecation Notices == |
| Line 55: | Line 143: |
| The trusty hacluster charm also includes a number of fixes to improve the way that quorum is handled by corosync and pacemaker. | === quantum-gateway === |
| Line 57: | Line 145: |
| === Ceph === | 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 59: | Line 147: |
| The ceph and ceph-osd charms now support setting sysctl options via charm configuration and provide a sensible default for the ‘kernel.pid_max’ sysctl option. This should support faster recovery in the event of a major outage in a Ceph deployment. | === MySQL HA with Ceph === |
| Line 61: | Line 149: |
| For charm authors, the ceph charm now has a Ceph broker API. This allows Ceph clients to request Ceph cluster actions e.g. create a new pool, via a new api as opposed to performing them on the client side. This will facilitate easily adding new functionality with reduced code impact while reducing the burden on the client to have to elect a leader to perform such actions, avoiding code duplication. | 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 63: | Line 151: |
| === Ceph RADOS Gateway === | 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 65: | Line 153: |
| The ceph-radosgw charm can now be deployed in a clustered configuration using a VIP as the object storage endpoint in conjunction with the hacluster charm: | 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 67: | Line 155: |
| {{{ juju deploy cs:trusty/hacluster hacluster-radosgw juju deploy -n3 cs:trusty/ceph-radosgw juju set ceph-radosgw vip=10.5.100.10 juju add-relation ceph-radosgw hacluster-radosgw }}} |
=== hacluster - default transport === |
| Line 74: | Line 157: |
| The ceph-radosgw charm now also supports using an embedded web container option provided natively by Ceph: | For the 15.04 charm release, the hacluster charm will continue to use multicast as its default transport option for cluster communications. |
| Line 76: | Line 159: |
| {{{ juju set ceph-radosgw use-embedded-webserver=true }}} |
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 80: | Line 161: |
| This avoids using Apache2 and mod_fastcgi, which lacks support for chuck transfer encoding and 100-continue as provided in the Ubuntu archive. | === Deployments without using the neutron-api charm === |
| Line 82: | Line 163: |
| === Keystone === The keystone charm contains a number of improvements to support use of SSL endpoints in highly available deployments. For charm authors, the keystone charm now has an additional ‘identity-notifications’ relation type; this relation is used by keystone to notify other charms when entries in the keystone service catalog change, and was introduced to support use with Ceilometer. === Glance === The glance charm now supports use of custom end-user provided configuration flags via the ‘config-flags’ charm option. === Ceilometer === The ceilometer charm can now be deployed in a clustered configuration using a VIP as the endpoint in conjunction with the hacluster charm: {{{ juju deploy cs:trusty/hacluster hacluster-ceilometer juju deploy -n3 cs:trusty/ceilometer juju set ceilometer vip=10.5.100.20 juju add-relation ceilometer hacluster-ceilometer }}} The ceilometer charm now requires to relations to the keystone charm, to support both service catalog registration of the Ceilometer endpoint and notifications to changes to the service catalog: {{{ juju add-relation ceilometer keystone:identity-service juju add-relation ceilometer keystone:identity-notifications }}} NOTE: relation endpoint types must now be specified to avoid ambiguity. === Neutron === The quantum-gateway charm now has a fast failover option of neutron resources when multiple gateway units are used with the hacluster charm: {{{ juju deploy cs:trusty/hacluster hacluster-ngateway juju deploy -n3 cs:trusty/quantum-gateway neutron-gateway juju set neutron-gateway ha-legacy-mode=True juju add-relation neutron-gateway hacluster-ngateway }}} NOTE: This feature has been introduced to support a level of resilience in Icehouse based deployments. Future charm work will include enablement of native Neutron support for router HA for later OpenStack releases. The neutron charms now also support VLAN and flat networking in additional to GRE and VXLAN for tenant networks. The quantum-gateway charm now also supports setting sysctl options via charm configuration inline with the ceph and nova-compute charms - see the ‘sysctl’ configuration option for details. === Swift === The swift-proxy charm now automatically rebalances rings on scale out of swift-storage services, allowing swift deployments to be managed more directly using Juju. The swift-proxy charm also includes configuration options to set the minimum period between ring rebalancing and an option to completely disable rebalancing - this should be used when adding a number of new swift-storage service units to a deployment, to avoid re-balancing as every new set of storage is added to the swift deployment. === Nova === The nova-cloud-controller charm can now use memcache to store tokens for instance console access, supporting use of instance consoles in HA configuration via the OpenStack dashboard: {{{ juju deploy -n3 cs:trusty/memcached juju deploy -n3 cs:trusty/nova-cloud-controller juju add-relation nova-cloud-controller memcached }}} The nova-cloud-controller charm now includes a ‘nova-alchemy-flags’ to allow Nova database configuration options to be directly tuned by charm users. The nova-compute charm now has support for different storage backends; specifically it now supports local disk (default), Ceph RBD or LVM backends: {{{ juju set nova-compute libvirt-image-backend=rbd juju set nova-compute rbd-pool=nova juju set nova-compute ceph-osd-replication-count=3 juju add-relation ceph nova-compute }}} The nova-compute charm now supports configuring disk cachemodes, allowing configuration of Nova disk usage options - see the ‘disk-cachemodes’ configuration option in the nova-compute charm and the upstream documentation about this feature. The nova-compute charm now also supports setting sysctl options via charm configuration inline with the ceph and quantum-gateway charms - see the ‘sysctl’ configuration option for details. === OpenStack Dashboard === The openstack-dashboard charm now has improved support for use with multi-region clouds. === RabbitMQ === The rabbitmq-server charm now supports deployment in IPv6 only networks: {{{ juju set rabbitmq-server prefer-ipv6=true }}} and use of a specific network for access to the message broker - see the ‘access-network’ configuration option for more details. |
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 176: | Line 167: |
| For the full list of bugs resolved for the 15.01 release please refer to https://launchpad.net/charms/+milestone/15.01 | 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/ReleaseNotes1504 (last edited 2016-06-20 13:04:30 by james-page)