VietOpenStack meetup 7th Kilo overview
•
0 likes•335 views
The document discusses the OpenStack Kilo release from the OpenStack Foundation. Some key points: - Kilo aimed to create a stable core platform for interoperability and integrating new technologies. - It focused on defining stable core services and saw key growth in integrated projects like Ironic for bare-metal provisioning. - Major components like Nova, Keystone, Glance, Cinder, Neutron, Ceilometer, and Horizon received new features, improvements, and bug fixes related to areas like performance, security, manageability and advanced networking services. - The discussion section raises questions about factors that would motivate upgrading to Kilo like improved stability, performance and flexibility, and challenges that may come with
Report
Share
VietOpenStack meetup 7th Kilo overview
- 1. “The Promise of Stability” Release Overview Thang Man 1 Viet OpenStack Meetup 7th @Saigon 2015
- 2. $ cat /me.info ★ Open Source Cloud Computing Follower mvthang manvanthang manthang.wordpress.com 2
- 3. Agenda ● Kilo overview ● Upgrade to Kilo, why not? 3
- 4. "During the Kilo release cycle, the OpenStack community tightly defined a stable set of core services, creating a solid platform for interoperability and to integrate emerging technologies." -- OpenStack Foundation. 4
- 5. OpenStack Kilo Key Themes 5
- 7. Integrated Projects in Kilo Ironic Bare-metal Provisioning 7
- 8. New Features and Improvements of Core Services 8
- 9. Compute - Nova API versioning management * v2.1 and micro-versions provide reliable, strongly validated API definitions. LibVirt Driver (QEMU/KVM) * Performance features: NUMA-aware scheduling, CPU Pinning, Huge Pages. * Consistency snapshot: quiescing (freezing) guest filesystems using QEMU guest agent during snapshotting an active instance. 9
- 10. Identity - Keystone Hierarchical Multitenancy * Nested Projects and Quotas. Fernet Token * A non-persistent, lightweight, secure and recently proposed alternative to UUID token. Identity Federation * Keystone act as a Federated Identity Provider (IdP) consuming identity properties issued by an external Identity Provider, such as SAML or OpenID. 10
- 11. Image - Glance Dealing with unexpected images * Provide the ability to temporarily deactivate an image to prevent non-admin users from downloading or instances from being built with it. Enhancing Import Image process * Basic conversion during the import process of images with formats supported by qemu-img convert: raw, qcow2, vdi, vmdk, vpc. 11
- 12. Block Storage - Cinder * New database schema upgrade will not require restarting Cinder services. * Attach a single volume to multiple instances. * Oversubscription with thin provisioning. Backup features * Incremental volume backup. * Support for encrypted volumes. 12
- 13. Networking - Neutron * API extension for MTU Selection and Advertisement. * Port-security support for the OVS ML2 Driver. * DVR supports VLANs in addition to VXLAN/GRE. Advanced networking services * New LBaaS v2 API (experimental). * More supported vendor drivers for VPNaaS, FWaaS, LBaaS. 13
- 14. Measurement - Ceilometer Additional meters * Collect metrics for amount of memory consumed by a VM process from the host. * Metering Ceph object storage. * Disk meters for LibVirt. Publishing support * Publish events and samples to Kafka, ElasticSearch or HTTP targets. 14
- 15. Dashboard - Horizon Instances * Launch Instance Wizard (beta). * Live/cold migrate all VMs from marked host for maintenance or rescue VMs. Volumes * Volume Types and QoS Specs management. * Volume transfer between projects. Networks * Specify physical network name for a new virtual network. 15
- 16. Discussion: Upgrade to Kilo Why or Why Not? 16
- 17. Questions 1. What key factors will motivate we to do upgrade? And how do Kilo meet our expectations? - stability, security - performance, scalability - flexibility, manageability - interoperability - … 2. Which features we currently lack of, and has implemented in Kilo? 3. Which bugs we haven't fixed yet, but resolved in Kilo? 17
- 18. Questions 4. If upgrade, … - what challenges we have to overcome? - what impacts we have to deal with? - how much budget (time, human) we need? 5. If not upgrade, … - DIY everything! - waiting for a release more preferable than Kilo? 18
- 19. Reference * OpenStack Community Contribution Stats http://stackalytics.com * Kilo Release Note https://wiki.openstack.org/wiki/ReleaseNotes/Kilo * Project Hosting & Management https://launchpad.net/openstack * OpenStack Kilo - April 2015 http://www.slideshare.net/openstack/openstack-kilo-april-2015-47589256 19