First draft of At A Glance article - #53
Conversation
| Suppose that we have nodes in Amsterdam and London, and we want to establish a core link between them. | ||
|
|
||
| On the Subscriptions page, we can see that we already have a subscription for each node, so we create a link via the New Subscription dropdown. | ||
|  |
There was a problem hiding this comment.
Maybe we can look into a way to allow users to click on an image so it pops out into a larger version, in some kind of modal. Currently I can only read what's on the image by right clicking and opening it in a new tab, otherwise it's just a bit too small. (I'll have a look into plugins)
There was a problem hiding this comment.
Having an issue running that branch, commented on it in that MR
Mark90
left a comment
Mark90
left a comment
There was a problem hiding this comment.
Great start! Left some comments.
I'm also not sure yet where best to place this in the nav bar
| Suppose that we have nodes in Amsterdam and London, and we want to establish a core link between them. | ||
|
|
||
| On the Subscriptions page, we can see that we already have a subscription for each node, so we create a link via the New Subscription dropdown. | ||
|  |
| # Behind the Scenes | ||
|
|
||
| So what's actually happening behind the scenes when we run these workflows? | ||
|
|
||
| WFO provides none of the facilities for talking to Netbox, NSO, Ansible, etc. | ||
| These features are implemented by other packages or by the software team leveraging the framework. |
There was a problem hiding this comment.
This section could probably be expanded a little more
There was a problem hiding this comment.
I elaborated a bit, but I'm not sure if it's in the direction you have in mind. What would feel most helpful / relevant to share?
There was a problem hiding this comment.
On second read it is good actually. "WFO provides none of the facilities for talking to Netbox, NSO, Ansible, etc." is fair, although for ansible there is the option to use LSO.
Maybe we could also briefly describe in the next paragraph the (at least for us, and in example-orchestrator) common pattern of implementing a services/netbox.py module for system interaction, and using that in workflow steps.
2 participants
Here's my first pass at a draft of the "not a video" crash course.
The goal is provide a brief elevator pitch that's accessible to network operators, developers, managers, etc. People want to know what it is, what it does, and what it would look like to use it.
Some open questions for reviewers:
Closes #19