Installation Guide - Changes for Kilo¶

Alternatives¶

None.

Assignee(s)¶

Primary assignee:

Matt Kassawara (ionosphere80)

Other contributors:

Anyone with installation experience

Work Items¶

• Mandatory changes
  • Overall
    • As necessary, make changes to successfully install OpenStack on Ubuntu 14.04, RHEL 7, CentOS 7, Fedora 21, SLES 12, and openSUSE 13.2 using native methods.
    • For RabbitMQ, create and use “openstack” account instead of the guest account.
    • As necessary, note that stock configuration files might require adding configuration stanzas/options rather than editing them.
    • As necessary, change any defaults in stock configuration files that generate deprecation warnings.
    • As necessary, replace “tenant” with “project” to align with Identity v3 API terminology.
    • As necessary, replace “message broker” with “message queue” to improve wording.
  • Identity
    • Enable version 3 API.
    • Replace deprecated eventlet (default web server) with Apache using configuration in upstream keystone repository.
    • Replace SQL token storage driver with Memcached to improve performance.
    • Replace deprecated python-keystoneclient commands with python-openstackclient commands.
  • Image Service
    • Enable version 2 API.
  • Block Storage
    • Replace deprecated v1 API with v2 API.
• Optional changes
  • Overall
    • Where available, use the /etc/mysql/conf.d directory for additional database configuration.
    • Install upstream RabbitMQ package if distribution includes an old version.
    • Replace python-serviceclient commands with generic python-openstackclient commands.
  • Networking
    • Standardize location for Open vSwitch agent configuration.
    • Add content for Linux Bridge agent.
  • Object Storage
    • Add content for standalone (keystone + swift) deployment.

Note: To simplify patches and shrink the review cycle, patches can address one distribution rather than all distributions. Use separate patches to address the same content for additional distributions. Reviewers should take this into account so that one distribution can complete patches, tests, and publication independent of other distributions.