Jump to: navigation, search

Difference between revisions of "VancouverSummit2018Summary"

(Created page with "== Introduction == This page summarizes the discussions had during the Cinder related Forum sessions at OpenStack Summit in Vancouver, May 21-24, 2018. The full list of Ether...")
(No difference)

Revision as of 14:04, 30 May 2018

Introduction

This page summarizes the discussions had during the Cinder related Forum sessions at OpenStack Summit in Vancouver, May 21-24, 2018.

The full list of Etherpads for Forum sessions may be seen here.


Monday May 21, 2018

Standalone Cinder Introduction

Etherpad: https://etherpad.openstack.org/p/YVR18-Standalone-Cinder-Intro

Summary

There was a lot of interest in this topic and the session was well attended. John Griffith did a great job of providing an overview of what Standalone Cinder is, how it is being used and how it might be used in the future.

Key Points

  • What is Standalone Cinder for?
    • It is a way for users to take the robust technology that is in Cinder and use it to support other storage solutions.
  • How is it different from the CSI plugin for Cinder?
    • Unlike the plugin it doesn't require the whole OpenStack infrastructure to be installed.
    • Can be used with no-auth to function without Keystone.
  • All management functionality between Cinder and Standalone Cinder is the same.
  • Cinder is modular. Whatever additional pieces that a person may need can be plugged in.
  • Standalone Cinder currently has a lot more functionality than CSI.
  • Challenges going forward are with how to handle attachment/detachment in standalone environments.


YouTube Link: https://www.youtube.com/watch?v=jh9HSp0FURs

Planning to use Placement in Cinder

Etherpad: https://etherpad.openstack.org/p/YVR-cinder-placement

Summary

A placement service has been under development for quite some time now. The goal is to be able to provide better control over where compute, networking and storage resources are placed in the user's environment. This is a concept that has not yet been adopted by Cinder. The goal of the discussion was to make the Cinder team aware of what is available and to start discussion on how we could/could not use the placement service.

Key Points

  • Cinder team shared that our current scheduler design keeps status or resource in-memory:
    • As a result we can only achieve an HA environment by doing active/passive scheduler configuration.
    • Design is racey and has issues in HA environments.
  • Concerns were raised about if the placement service could be deployed as an HA Active/Active service.
    • CERN is currently running with 20 instances today and seeing no issues.
    • All state is kept in the database for the placement service.
    • Locking is handled through SQL and should be robust.
    • Potentially resolves the other HA Active/Active issues we have been looking at in Cinder.
  • The negative:
    • Makes Cinder dependent on another service.
    • This, obviously, impacts Standalone Cinder

To Dos

  • Take the discussion back to the team and highlight the positives/negatvies.
  • Decide if we want to go forward using the placement service.
  • Determine how we will handle the impact on Standalone Cinder if we do choose to use it.


YouTube Link:

Tuesday May 22, 2018

Cinder High Availability (HA) Discussion

Etherpad: https://etherpad.openstack.org/p/YVR18-cinder-ha-forum

Summary

Key Points

  • Cinder team shared that our current scheduler design keeps status or resource in-memory:
    • As a result we can only achieve an HA environment by doing active/passive scheduler configuration.
    • Design is racey and has issues in HA environments.
  • Concerns were raised about if the placement service could be deployed as an HA Active/Active service.
    • CERN is currently running with 20 instances today and seeing no issues.
    • All state is kept in the database for the placement service.
    • Locking is handled through SQL and should be robust.
    • Potentially resolves the other HA Active/Active issues we have been looking at in Cinder.
  • The negative:
    • Makes Cinder dependent on another service.
    • This, obviously, impacts Standalone Cinder

To Dos

  • Take the discussion back to the team and highlight the positives/negatvies.
  • Decide if we want to go forward using the placement service.
  • Determine how we will handle the impact on Standalone Cinder if we do choose to use it.


YouTube Link: