Updates to the conceptual model to separate app operator and developer roles #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… addition of applications.
'Workload' to fit with the rest of the model.
…ec into jsheehan-model-updates
dumbnose
requested review from
mikkelhegn,
technosophos and
vturecek
as code owners
hongchaodeng
approved these changes
Oct 4, 2019
| - __Traits__ for assigning operational features to instances of components. | ||
| - __Application configuration__, defines a deployment of components, their traits, and application scopes. | ||
| - __Application configuration__, defines a configuration of an application, its traits, and additional scopes, such as network scopes. |
There was a problem hiding this comment.
Suggested change
| - __Application configuration__, defines a configuration of an application, its traits, and additional scopes, such as network scopes. | |
| - __Application configuration__, defines a configuration of an application, its traits, and additional scopes (such as network scopes). |
| @@ -154,7 +157,7 @@ An application configuration has the following parts: | |||
|
|
|||
| ## Representing Hydra Objects as Schematics | |||
|
|
|||
| The Hydra specification represents Hydra schematics (components, trait definitions, application configurations, etc.) as _schematics_. A schematic is a structured document that provides a declaration of an object or an object's desired state. Throughout this specification, schematics are represented in [YAML]() formatting. However, nothing in this specification forecloses the possibility of representing schematics as JSON documents or other similarly structured textual or binary representations. | |||
| The Hydra specification represents Hydra schematics (components, applications, trait definitions, application configurations, etc.) as _schematics_. A schematic is a structured document that provides a declaration of an object or an object's desired state. Throughout this specification, schematics are represented in [YAML]() formatting. However, nothing in this specification forecloses the possibility of representing schematics as JSON documents or other similarly structured textual or binary representations. | |||
There was a problem hiding this comment.
Suggested change
| The Hydra specification represents Hydra schematics (components, applications, trait definitions, application configurations, etc.) as _schematics_. A schematic is a structured document that provides a declaration of an object or an object's desired state. Throughout this specification, schematics are represented in [YAML]() formatting. However, nothing in this specification forecloses the possibility of representing schematics as JSON documents or other similarly structured textual or binary representations. | |
| The Hydra specification represents Hydra schematics (components, applications, trait definitions, application configurations, etc.) as _schematics_. A schematic is a structured document that provides a declaration of an object or an object's desired state. Throughout this specification, schematics are represented in YAML formatting. However, nothing in this specification forecloses the possibility of representing schematics as JSON documents or other similarly structured textual or binary representations. |
hongchaodeng
requested changes
Nov 1, 2019
|
|
||
| - __Component__, where developers declare the operational characteristics of the code they deliver _in infrastructure neutral terms_. | ||
| - __Scopes__, a way to loosely couple components into groups with common characteristics. | ||
| - __Applications__, where developers group components together into a single, deployable unit and specifies cross-component info, such as health scopes. |
There was a problem hiding this comment.
This point of Applications concept does not exist yet.
It is related to #148, but for now we might want to hold or modify this PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the change to the conceptual model that we discussed last week. I didn't update every single page to reflect this change. I wanted everyone to first see the proposed adjustments before changing any additional references to the concepts. So, please take a look and provide feedback. I'll be on vacation for the next week. So, I won't be able to react to any changes until I get back. Thanks.