-
Notifications
You must be signed in to change notification settings - Fork 246
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
Updates to the conceptual model to separate app operator and developer roles #185
base: master
Are you sure you want to change the base?
Conversation
… addition of applications.
'Workload' to fit with the rest of the model.
…ec into jsheehan-model-updates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after nit
- __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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- __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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
|
||
- __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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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.