* LDAP Settings material
* Closes#651
* Combining work into single branch
* Updating index
* Fixing code examples
* Adding in note from Johnny's feedabck
* Menu positions, HA terms
* Copy edit of users
* Adding deploy an application
* Updating the overview page to include more text
* Updating with comments from review page
* Updating the constraints and port
* Layout check/fix
Signed-off-by: Mary Anthony <mary@docker.com>
- Close#194 and fix
- Fix and close#425
- Fix and close#417
- Fix and close#420
- Fix and close#422
- Adding in documentation build scripts
- Fix and close#431
- Fix and close#438, and Fix and close#429
- Work on 441
- Adding in commands reference
- Updating all the options to tables
- Updating per Vivek #498
- Adding vivek's last suggestions
Signed-off-by: Mary Anthony <mary@docker.com>
This adds an option in the user pull down to generate a support dump.
While not totally ideal from a UE perspective, we don't really have
a page to do admin tasks, so this'll have to do for now. With this
we can remove the rather ugly docs we have explaining how to get
support dumps via curl.
Non admin users will get the standard permission denied page, as with
all the other admin-only tasks we have.
Creating specs directory; may be moved later
Adding fix for Issue #348
Adding in updates for networking
Updating with Dan's comments: removing old -beta
Updating networking after talking to Madhu
Updated install with HA as optional
Moved HA spec into specs
Did "customer-facing" HA page
Renamed server > controller in docs
Entering comments from reviewers
Signed-off-by: Mary Anthony <mary@docker.com>
This revamps the product and image names. After merging this change,
the bootstrapper image will be known as "dockerorca/ucp" since it is the
primary image customers interact with. The controller will be known as
"dockerorca/ucp-controller" and the corresponding container names are
"ucp" and "ucp-controller". Once we get closer to GA, we'll move the
images under the "docker" org, so the product name will flow nicely from
that "docker/ucp" for the bootstrapping tool, and "docker/ucp-controller"
for the server image.
It turns out that our support dump logic is *really* fast and compact.
Even on a large node (hundreds of containers and thousands of images)
it runs in ~10 seconds and weighs in at a few hundred K. Since we're
running all the dumps in parallel, there's really no need for the added
complexity of saving them to a DB.
This change revamps and simplifies the support dump API. Now you simply
POST to the API endpoint, and it will stream the full zip file containing
all the nodes payloads within. If a node is unreachable, times out,
or has some other catastrophic problem, the contents for that node will
be an error message instead of the normal tar.gz bundle.
I've tested this with a swarm of multiple nodes, confirmed the dumps
match up to the hosts, and the system handles offline nodes, reporting
an error message within the bundle. (it does take a long time in the
failure cases due to a bug in swarm that's slated to be fixed in 1.9,
but curl doesn't give up so this still works fine.)
