This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
OpenStack Summit Tokyo 2015
OpenStack New Features proposed by
1. Log Request ID mapping[Cross-Project: Nova, Cinder, Glance, Neutron and others]
2. Masakari: VMHA for OpenStack Compute3. Unshelve performance improvement [Nova]4. Availability Zone Support [Neutron]5. Linuxbridge Distributed Virtual Router (DVR) [Neutron]6. OPNFV Integration [Congress]7. Enable New Agents [Neutron]
OpenStack Summit Tokyo 2015
What it is
Why it is important
How it works
Log Request ID mapping [Nova, Cinder, Glance, Neutron and others]
Current status and Future plan
It outputs its own request ID with the request ID received from another component in an API response to the log within one line.
This function enables us to track API calls between components easily and is crucial for automated log analysis.For example, a volume creation based on an existing image(Glance) (API call from cinder to glance).
It adds a function to get request ID in a response from another component in clients(python-*client).It adds a function to output its own request ID and the request ID in a response from another component within one line to the log in the caller.
The spec has been approved in the community (openstack-specs)We will implement it in each client ( python-*client ) and then implement log outputs in each component.Reference https://review.openstack.org/#/c/156508
OpenStack Summit Tokyo 2015
Log Request ID mapping [Nova, Cinder, Glance, Neutron and others]
It provides Virtual Machine High Availability (VMHA) for “Pets” service model.It recovers automatically a VM instance in case of VM or hypervisor failure to minimize the downtime.
Cloud-native application handles High Availability at its own layer.Sometimes, customers and/or applications still prefer “Pets” service model.
It monitors status of VM and KVM Host with pacemaker.It rescues VM with Nova API when errors occurs.No modification to OpenStack components.
It’s published for the community under Apache license at github https://github.com/ntt-sic/masakariYou can download the source code and try it.Sponsor Demo: http://sched.co/4M84
It speeds up unshelving(powering on) a VM by utilizing VM image ‘cache’.
It solves the issue that it takes long time to unshelve(power on) a VM when VM’s image size is large.
It keeps a VM image in an instance store by configuration when shelving(powering off) the VM. (=‘cache’)* Assumption: Compute nodes share their instance store.It boots the VM by utilizing the ‘cache’(not downloading the image from glance) when unshelving(powering on) the VM.
We proposed a spec for Mitaka release in the nova community.
It enables network resources to get High Availability.
When breakdown happens, it doesn’t affect user’s resources.It improves the reliability.
It added extension API and attribute to each resource.
It’s under development, partially implemented (API and DB updates are merged).It’s needed to discuss about the development for other use cases (Segment, Cell).Reference https://blueprints.launchpad.net/neutron/+spec/add-availability-zone
It enables operators to use DVR function with Linuxbridge.
Some operators want to use Linuxbirdge since it’s stable than openvswitch and maintenance cost is low.
It achieves routing by ebtables.
We proposed an implementation for Proof of Concept.It’s need to consider about the development for SNAT and DHCP.Reference https://bugs.launchpad.net/neutron/+bug/1504039