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

Initial draft of service group how to docs #672

Merged
merged 1 commit into from
Jun 8, 2016
Merged

Initial draft of service group how to docs #672

merged 1 commit into from
Jun 8, 2016

Conversation

davidwrede
Copy link

  • First draft on how to join a service group
  • Left-nav update

Signed-off-by: David Wrede [email protected]

@thesentinels
Copy link
Contributor

By analyzing the blame information on this pull request, we identified @cwebberOps, @juliandunn and @ryankeairns to be potential reviewers

@juliandunn
Copy link
Contributor

It would be good to advise the user that best practice is to name the group appname.environment -- this helps with continuous deployment (and we can point to the topic on that).

# Run packages in a service group
A service group is a logical grouping of services with the same package and topology type connected together in a ring. They are created to share configuration and file updates among the services within those groups and can be segmented based on workflow or deployment needs (QA, Production, and so on). Updates can also be [encrypted](/docs/run-packages-security#service-group-encryption) so that only members of a specific service group can decrypt the contents.

In addition, multiple service groups can reside in the same ring. This allows HTTP API data exposed by supervisors to be shared with other members of the ring regardless of which group they are in.
Copy link
Contributor

Choose a reason for hiding this comment

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

I would just remove HTTP API -- data is fine

@davidwrede
Copy link
Author

Incorporated feedback and squashed commits. Ready for one last look and then MWR.

@juliandunn
Copy link
Contributor

LGTM

@thesentinels r+

@thesentinels
Copy link
Contributor

📌 Commit ba0037c has been approved by juliandunn

@thesentinels
Copy link
Contributor

⌛ Testing commit ba0037c with merge 2181acf...

thesentinels pushed a commit that referenced this pull request Jun 8, 2016
Signed-off-by: David Wrede <[email protected]>

Pull request: #672
Approved by: juliandunn
@thesentinels
Copy link
Contributor

☀️ Test successful - travis

@thesentinels thesentinels merged commit ba0037c into habitat-sh:master Jun 8, 2016
jtimberman pushed a commit that referenced this pull request Jun 12, 2016
Signed-off-by: David Wrede <[email protected]>

Pull request: #672
Approved by: juliandunn
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.

3 participants