remove compose from documentation.
Bug #1485163 reported by
Steven Dake
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Critical
|
Steven Dake |
Bug Description
I get 4-5 questions a day on how to deploy and they all involve starting off with Compose. The users re generally confused by "well our documentation isn't updated" so fix that problem along with deprecating the compose config-internal related bits.
Changed in kolla: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Steven Dake (sdake) |
milestone: | none → liberty-3 |
Changed in kolla: | |
status: | Confirmed → In Progress |
Changed in kolla: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/213401 /git.openstack. org/cgit/ stackforge/ kolla/commit/ ?id=6efe57e9eb8 0a57c78bea9a2ca 9d170d4efdfeb5
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6efe57e9eb80a57 c78bea9a2ca9d17 0d4efdfeb5
Author: Steven Dake <email address hidden>
Date: Fri Aug 14 20:03:22 2015 -0700
Remove compose from documenation
Receive several quickstart related questions every day. Make a
first pass at cleaning up our documentation to point people
in the right direction. While we are about it remove compose
related bits. Anything in the compose directory will remain as
a reference implementation for how to implement the compose
files to work well with our container content.
Change-Id: I9e832e97ac2bac ca8eab7e1bfbd82 664d2b191b8 Implements: blueprint remove- config- internal
Closes-Bug: #1485163
Paritally-