-
Notifications
You must be signed in to change notification settings - Fork 7
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
Remove visible todos from lsm doc #7201
Conversation
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.
- I see there are still some TODO's left in the following places:
- Regarding the follow up ticket: We should make sure to include a reference in that ticket to this PR. That way it's easier to determine what the different bullets in the ticket mean.
@@ -10,8 +10,6 @@ In the network, this virtual wire is implemented as a VXlan tunnel, tied to both | |||
Each such tunnel requires a "VXLAN Network Identifier (VNI)" that uniquely identifies the tunnel. | |||
In the allocation phase, the orchestrator selects a VNI and ensures no other customer is assigned the same VNI. | |||
|
|||
.. todo: add picture of service |
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 TODO is not mentioned in the follow-up ticket that was created.
docs/lsm/index.rst
Outdated
TODO: Three set of attributes | ||
Each service instance defines 3 sets of its attributes that are used in different situations: | ||
|
||
- ``candidate_attributes``: The set of attributes used when the service instance model state is candidate or designed. |
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.
I don't think we should explain this in term of the model state. The model state is a purely internal state of the orchestrator. You cannot see this state on the web-console for example. I think we should explain this more from the end-user perspective. This attribute set is mainly used to validate a change before activating (deploying) it.
docs/lsm/index.rst
Outdated
Each service instance defines 3 sets of its attributes that are used in different situations: | ||
|
||
- ``candidate_attributes``: The set of attributes used when the service instance model state is candidate or designed. | ||
- ``active_attributes``: The set of attributes when the model is evaluated with only active instances. |
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 is not True. These attributes are also used when a validation compile is done for another service instance for example.
docs/lsm/index.rst
Outdated
- ``rollback_attributes``: The set of attributes that can be used to rollback active attributes that result in an error | ||
state. | ||
|
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.
- ``rollback_attributes``: The set of attributes that can be used to rollback active attributes that result in an error | |
state. | |
- ``rollback_attributes``: The set of attributes that can be used to rollback active attributes that result in an error state. | |
docs/lsm/index.rst
Outdated
entity InterfaceIPAssignment extends lsm::ServiceEntity: | ||
""" | ||
Interface details. | ||
|
||
Updating service entities | ||
========================= | ||
:attr router_ip: The IP address of the SR linux router that should be configured. | ||
:attr router_name: The name of the SR linux router that should be configured. | ||
:attr interface_name: The name of the interface of the router that should be configured. | ||
:attr address: The IP-address to assign to the given interface. | ||
""" | ||
|
||
std::ipv_any_address router_ip | ||
string router_name | ||
string interface_name | ||
|
||
std::ipv_any_interface address | ||
lsm::attribute_modifier address__modifier="rw+" | ||
end | ||
|
||
implement InterfaceIPAssignment using parents |
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.
When we include a model in the docs, we usually add the model to a separate file. Then we can use that file to add a test case that verifies whether the model actually compiles and we can use the same file to include the model (or part of it) in the docs. We should do the same here. Otherwise the code included in the docs might no longer compile due to future changes to the lsm module or compiler.
Co-authored-by: arnaudsjs <2684622+arnaudsjs@users.noreply.github.com>
Processing this pull request |
# Description add docs/ remove todos follow-up ticket: 1. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/inmanta-core/7202 2. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/std/504 3. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/apt/281 closes #7134 # Self Check: Strike through any lines that are not applicable (`~~line~~`) then check the box - [x] Attached issue to pull request - [ ] Changelog entry - [ ] Type annotations are present - [ ] Code is clear and sufficiently documented - [ ] No (preventable) type errors (check using make mypy or make mypy-diff) - [ ] Sufficient test cases (reproduces the bug/tests the requested feature) - [ ] Correct, in line with design - [x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: ) - [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see [test-fixes](https://internal.inmanta.com/development/core/tasks/build-master.html#test-fixes) for more info)
# Description add docs/ remove todos follow-up ticket: 1. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/inmanta-core/7202 2. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/std/504 3. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/apt/281 closes #7134 # Self Check: Strike through any lines that are not applicable (`~~line~~`) then check the box - [x] Attached issue to pull request - [ ] Changelog entry - [ ] Type annotations are present - [ ] Code is clear and sufficiently documented - [ ] No (preventable) type errors (check using make mypy or make mypy-diff) - [ ] Sufficient test cases (reproduces the bug/tests the requested feature) - [ ] Correct, in line with design - [x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: ) - [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see [test-fixes](https://internal.inmanta.com/development/core/tasks/build-master.html#test-fixes) for more info)
Merged into branches master in 8e189d3 |
# Description add docs/ remove todos follow-up ticket: 1. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/inmanta-core/7202 2. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/std/504 3. https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/gh/inmanta/apt/281 closes #7134 # Self Check: Strike through any lines that are not applicable (`~~line~~`) then check the box - [x] Attached issue to pull request - [ ] Changelog entry - [ ] Type annotations are present - [ ] Code is clear and sufficiently documented - [ ] No (preventable) type errors (check using make mypy or make mypy-diff) - [ ] Sufficient test cases (reproduces the bug/tests the requested feature) - [ ] Correct, in line with design - [x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: ) - [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see [test-fixes](https://internal.inmanta.com/development/core/tasks/build-master.html#test-fixes) for more info)
Processing #7219. |
Pull request opened by the merge tool on behalf of #7201
Processing #7218. |
Pull request opened by the merge tool on behalf of #7201
Description
add docs/ remove todos
follow-up ticket:
closes #7134
Self Check:
Strike through any lines that are not applicable (
~~line~~
) then check the box