Jump to: navigation, search

IcehouseDocTesting

Revision as of 05:10, 30 March 2014 by Fifieldt (talk | contribs) (Install Guide)

Install Guide

Section Ubuntu 12.04 Fedora RHEL openSUSE SLES CentOS 6.4 Debian Ubuntu 14.04 SL6
Overview and architecture ✚2 ✚2 ✚2 ✚2 ✚2 ✚2 ✚2
Basic Operating System Configuration
Configuring the Identity Service ✚rc1 Warning.svg Warning.svg Warning.svg Warning.svg ✚2 Warning.svg Warning.svg Warning.svg
Install and Configure OpenStack Clients Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Configuring the Image Service ✚3 Warning.svg Warning.svg Warning.svg Warning.svg ✚2 Warning.svg Warning.svg Warning.svg
Configuring the Compute Services Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Adding a Dashboard Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Adding Block Storage Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Adding Object Storage Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Using Neutron Networking Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Using Heat Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Using Ceilometer Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg
Overall Guide Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg Warning.svg

Warning.svg doc not tested | ✗ has some failures | ✔ tested 100% OK | ✚X tested OK with release candidate(rcX)/milestone(X)

TODO:

  • Basics/Networking needs a revamp to take into account the new architectures. It should provide more general advice.
  • Basics/Database python-mysqldb could move to the install line of necessary places, rather than splitting by controller/node at this point and expecting people to refer back to it later. Should provide more general advice on database location.