ReleaseNotes1504

Differences between revisions 19 and 57 (spanning 38 versions)
⇤ ← Revision 19 as of 2014-10-29 11:06:52 →
Size: 7022
Editor: james-page
Comment:
← Revision 57 as of 2016-06-20 13:04:30 → ⇥
Size: 8627
Editor: james-page
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 ==

=== OpenStack Juno support for 14.04 and 14.10 ===

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:		 ## page was renamed from UbuntuOpenStack/OpenStackCharms/ReleaseNotes1504
## page was renamed from ServerTeam/OpenStackCharms/ReleaseNotes1504
## page was copied from ServerTeam/OpenStackCharms/ReleaseNotes1501
<<TableOfContents>>

== 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 [[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 11: Line 41:
 * cinder-ceph
Line 22: Line 53:
 * nova-cell

To deploy !OpenStack Juno on Ubuntu 14.04, use the 'openstack-origin' configuration option, for example:		  * openstack-dashboard

To deploy !OpenStack Kilo on Ubuntu 14.04, use the 'openstack-origin' configuration option, for example:
Line 29: Line 60:
  openstack-origin: cloud:trusty-juno   openstack-origin: cloud:trusty-kilo
Line 34: Line 65:
!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.

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:
 !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 release >= 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]]

'''NOTE''': This feature was considered experimental in !OpenStack Juno so is only recommended for use with !OpenStack Kilo.

=== 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 release >= 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]]

'''NOTE''': This feature was considered experimental in !OpenStack Juno so is only recommended for use with !OpenStack Kilo.

=== 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.

=== ZeroMQ ===

The Nova and Neutron charms now provide initial support use of ZeroMQ as an alternative to RabbitMQ for messaging; this is only supported with OpenStack Kilo or later.

To deploy Nova and Neutron with ZeroMQ, make use of the new openstack-zeromq charm (sample subset of juju commands):

{{{
juju deploy redis-server
juju deploy openstack-zeromq
juju add-relation redis-server openstack-zeromq
for svc in nova-cloud-controller nova-compute neutron-api neutron-openvswitch quantum-gateway; do
   juju deploy $svc
   juju add-relation $svc openstack-zeromq
done
}}}

At this point in time ZeroMQ should be considered for testing only. Further work is expected both upstream in !OpenStack and across the !OpenStack charm set during the next development cycle.

=== Deployment from source ===

'''EXPERIMENTAL FEATURE'''

The following charms now have support for deploying OpenStack directly from git repositories:

 * cinder
 * keystone
 * glance
Line 86: Line 132:
 * glance
 * keystone
 * ceph/ceph-osd
Line 90: Line 133:
 * 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.		  * 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.

'''NOTE''': Current support extends to deployment of Icehouse and Juno from source repositories; Kilo support is not yet complete but will be delivered as a stable update between now and the 15.07 charm release.

=== 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"
}}}

=== SSL/HTTPS/PKI ===

All service endpoints can now be configured as https either by having the Keystone charm act as a certificate authority and auto-generate cert/key for each endpoint or by injecting cert/key/ca to be able to use an existing CA. Endpoints can also now choose to use PKI tokens in keystone although the default remains UUID.

To enable https endpoints (using keystone as CA):

{{{
juju set keystone https-service-endpoints='true'
}}}

To enable PKI tokens:

{{{
juju set keystone enable-pki='true'
}}}

For more ssl options see config.yaml

== 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.

=== 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.07 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.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. ZeroMQ
    6. Deployment from source
    7. Monitoring
    8. SSL/HTTPS/PKI
  3. Deprecation Notices
    1. quantum-gateway
    2. MySQL HA with Ceph
    3. hacluster - default transport
    4. nova-cloud-controller and neutron-api charms
  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
  • 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 release >= Juno

  • enable-l3ha is disabled
  • Overlay network type is vxlan

More details of DVR can be found here

NOTE: This feature was considered experimental in OpenStack Juno so is only recommended for use with OpenStack Kilo.

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 release >= Juno

  • enable-dvr is disabled
  • Overlay network type is vlan, gre or vxlan

More details on L3 HA can be found Here

NOTE: This feature was considered experimental in OpenStack Juno so is only recommended for use with OpenStack Kilo.

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.

ZeroMQ

The Nova and Neutron charms now provide initial support use of ZeroMQ as an alternative to RabbitMQ for messaging; this is only supported with OpenStack Kilo or later.

To deploy Nova and Neutron with ZeroMQ, make use of the new openstack-zeromq charm (sample subset of juju commands): 

juju deploy redis-server
juju deploy openstack-zeromq
juju add-relation redis-server openstack-zeromq
for svc in nova-cloud-controller nova-compute neutron-api neutron-openvswitch quantum-gateway; do
   juju deploy $svc
   juju add-relation $svc openstack-zeromq
done

At this point in time ZeroMQ should be considered for testing only. Further work is expected both upstream in OpenStack and across the OpenStack charm set during the next development cycle.

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.

NOTE: Current support extends to deployment of Icehouse and Juno from source repositories; Kilo support is not yet complete but will be delivered as a stable update between now and the 15.07 charm release.

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"

SSL/HTTPS/PKI

All service endpoints can now be configured as https either by having the Keystone charm act as a certificate authority and auto-generate cert/key for each endpoint or by injecting cert/key/ca to be able to use an existing CA. Endpoints can also now choose to use PKI tokens in keystone although the default remains UUID.

To enable https endpoints (using keystone as CA): 

juju set keystone https-service-endpoints='true'

To enable PKI tokens: 

juju set keystone enable-pki='true'

For more ssl options see config.yaml

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.

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.07 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.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)