This commit lays down the steps you need to take to deploy TLS-e with
TripleO. This is needed because we recently replaced novajoin with
tripleo-ipa which changes how people deploy TLS-everywhere.
Subsequent patches will:
- introduce a guide for public TLS
- remove legacy ssl documentation
Change-Id: I81f6a3ed542aa59c99ab57a5f2454e85ae7fde57
The TLS-everywhere introduction contains some useful information for the
ways you can deploy TLS (public TLS and TLS everywhere). As well as
primers on the components used to implement TLS.
This commit generalizes the introduction so we can re-use it for public
TLS and TLS-everywhere. Subsequent patches will add separate guides that
describe how to accomplish both deployment techniques.
Change-Id: Ieea23577095dd910c9923a8d1285561a72038a46
The existing documentation is full of useful bits for setting up TLS
everywhere and TLS for public-only endpoints. This commit adds an
introduction that attempts to describe the usecases for using TLS.
Additionally, it adds short, concise descriptions of the components
needed in TLS deployments and why they're important.
This is going to be the first of a series of documentation patches
that attempt to refactor the existing TLS/SSL documentation to be more
use-case driven. The goal is to make it easier for readers and TripleO
developers to understand how TLS works in TripleO.
Change-Id: I7eaf8f852eaccf4debd0b5095c2622c53b09de4d
Lance Bragstad