Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite and re-scope deployment documentation #631

Merged
merged 1 commit into from
Jan 12, 2015

Conversation

ironcladlou
Copy link
Contributor

Make the deployment doc less of a low level technical document/proposal
mashup, and rewrite it for end-user consumption. Architecture and
technical details can be moved to a new document. The upstream proposal
will also be a new document.

@ironcladlou
Copy link
Contributor Author

This is a follow-on to #584

@ironcladlou
Copy link
Contributor Author

cc @pmorie @bparees @pweil-

}
```

In this example, when the `latest` tag value for the `imageRepository` named `openshift/origin-ruby-sample` changes, every container in the `deploymentConfig` matching those in `containerNames` will be updated with the new tag value, and a new `deployment` will be created.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"every container in the deploymentConfig matching those in containerNames" is a bit confusing to me.

maybe: the containers specified in containerNames for deploymentConfig D will be updated ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorporated, thanks

@ironcladlou ironcladlou force-pushed the deployment-docs branch 2 times, most recently from 0c14a70 to 0e4d8c6 Compare January 12, 2015 14:30
Make the deployment doc less of a low level technical document/proposal
mashup, and rewrite it for end-user consumption. Architecture and
technical details can be moved to a new document. The upstream proposal
will also be a new document.
@pmorie
Copy link
Contributor

pmorie commented Jan 12, 2015

LGTM [merge]

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_openshift3/589/) (Image: devenv-fedora_528)

@pmorie
Copy link
Contributor

pmorie commented Jan 12, 2015

[merge] looks like jenkins timeout

@openshift-bot
Copy link
Contributor

Evaluated for origin up to 0e4d8c6

openshift-bot pushed a commit that referenced this pull request Jan 12, 2015
@openshift-bot openshift-bot merged commit 86fd949 into openshift:master Jan 12, 2015
@ironcladlou ironcladlou deleted the deployment-docs branch January 12, 2015 19:51
deads2k pushed a commit to deads2k/origin that referenced this pull request Jul 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants