Revision as of 15:44, 2 February 2011

Release Notes, Bexar

The Bexar release introduces large file support for OpenStack Object Storage (Swift), the OpenStack Image registry and Delivery service (Glance) and a lot of new features in OpenStack Compute (Nova).

<<TableOfContents()>>

New Features

OpenStack Object Storage (Swift)

• Large objects (greater than 5 GB) can now be downloaded using OpenStack Object Storage. While there is still a limit on the size of a single uploaded object, with this release the download size of a single object is virtually unlimited with the concept of segmentation. Refer to Managing Large Objects for more information.
• An experimental S3 compatibility middleware has been added to OpenStack Object Storage. This middleware intercepts S3 style requests and authorization, and transforms them into swift requests.
• Initial i18n support for logging messages.
• Swauth is a swift compatible authentication and authorization service implemented on top of swift as wsgi middleware. This will replace the dev_auth service in a future release.
• Advanced rate limiting middleware

OpenStack Compute (Nova)

• Support for raw disk images with libvirt and XenAPI hypervisors, without the complexity of a separate ramdisk or kernel image.
• IPv6 support in all network modes but FlatManager. Use the new use_ipv6 flag, and refer to BexarIpv6supportReadme for more information.
• Support for a lot of new volume backends to provide highly available block volumes for VMs: Sheepdog, CEPH/RADOS, and iSCSI (XenAPI only)
• Microsoft Hyper-V support. Refer to HypervInstall for information.
• Lots of new features have been added around the Openstack API, for example admin features to pause, suspend, lock and password reset instances, but also support for per-instance diagnostics.
• New "rescue" mode allowing an instance to mount affected disks and fix problems (see rescue_image_id, rescue_kernel_id and rescue_ramdisk_id flags)
• Web-based serial console to access instances where networking fails (requires instances with serial console enabled). This is available through the Openstack API or the new euca-get-ajax-console tool (and introduces a new nova-ajax-console-proxy type of node)
• Possibility to do hardware staging: new added services can be specifically load-tested before being made generally available to cloud users (administered by the nova-manage service commands)
• Database versioning and migration support, for painless migration from one version to another
• Instances now use copy-on-write by default for better performance (you can use the use_cow_images flag to control that)
• Support for availability zones, through the introduction of a new scheduler: ZoneScheduler
• A DirectAPI, using introspection to exhibit features, is now available for developers to control Nova locally
• Some features that were partly implemented in the Austin release got finalized in Bexar: IP allocation was moved down the chain, project VPNs are supported and Nova now fully supports iptables-driven security groups.
• Finally, lots of efforts were spent unifying the code around common standards for using the new Glance clients, for i18n, logging, service handling (through eventlet), or using paste.deploy for the API nodes.

OpenStack Image Registry and Delivery service (Glance)

• Glance APIs (for registry and delivery) were unified, and a specific client class created
• Support for one-stop uploading a raw data images (through a POST to the Glance API)
• Glance can now store and fetch image data on a S3-like backend

Others

There were also deliveries outside those core projects during the Bexar development timeframe, in particular:

• The OpenStack Dashboard, a reference implementation of a web-based console for OpenStack Compute projects is now available. Refer to OpenStackDashboard for more information.
• A deployment tool to deploy Nova on multiple servers. Refer to NovaInstall/NovaDeploymentTool for more information.

Known Issues and Limitations

Nova

• IPv6 is not supported in FlatManager network mode.
• You can't upload images to the S3ImageService (objectstore) from the Openstack API (only Glance is supported), see Bug 709355
• You can't use FlatDHCPManager network mode on a multiple machines deployment without using multiple interfaces (Bug 710959). Recommended mode of operation for deploying Nova on multiple machines is to use VLAN-supporting managed switches with VlanManager network mode.
• When a compute node dies, its instances may still be reported as running (Bug 661214)
• When a VM dies, a compute node won't realize until it's restarted (Bug 661260)
• CA code doesn't get installed by "setup.py install" (see workaround in Bug 683137)
• When using XenAPI, the compute node doesn't clean up if a vm fails to spawn (Bug 694935) or if it loses it's xapi session (Bug 692994)

Glance

•  ?