-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Infoblox scenario guide #45664
Infoblox scenario guide #45664
Conversation
The test
|
The test
|
The test
|
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.
Nice work. I made a few suggestions for making it even better.
Module list | ||
============ | ||
|
||
See :ref:`nios_net tools_modules` for a full list of NIOS modules for this release. |
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.
In the published doc, this is rendered as "See Nios for a full list of NIOS modules for this release." That looks a bit weird to my eye. How about tightening this up and specifying the text for the link - something like:
You can review simple example tasks in the documentation for any of the :ref:`NIOS modules <nios_net tools_modules>` or look at the `Use cases with modules` section for more elaborate examples.
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.
Actually, I might get rid of the "Module list" heading and put the shortened content in the Introduction.
Retrieving all network views | ||
---------------------------- | ||
|
||
This example playbook uses the ``set_fact`` module with the ``nios`` lookup plugin to retrieve all the network views, which are then saved in the ``networkviews`` variable: |
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 think "this example playbook" is fluff - how about rewording these examples using the pattern: To do X, use Y: <example_playbook>? So for this one:
To retrieve all network views and save them in a variable, use the `set_fact` module with the `nios` lookup plugin:
|
||
You can use ``nios`` modules in tasks to simplify common Infoblox workflows. | ||
|
||
For these examples, you need to set up your NIOS credentials. See `Credentials and authenticating`_. |
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.
What do you think about shortening this section by putting the link in the sentence?
You can use the ``nios`` modules in tasks to simplify common Infoblox workflows. Be sure to set up your `NIOS credentials <nios_credentials>` before following these examples.
or something like that?
|
||
To use the Infoblox dynamic inventory script: | ||
|
||
1. Download the ``infoblox.yaml`` file and save it in the ``/etc/ansible`` directory. |
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.
Do you want these to be hard-coded numbers, or a #-style list?
|
||
You can also implicitly use the Infoblox dynamic inventory script by including it in your inventory directory (``etc/ansible/hosts`` by default). | ||
|
||
See :ref:`dynamic_inventory` for more details. |
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 feel like the whitespace in the rendered HTML makes it hard to parse the page - maybe try having fewer paragraphs/newlines?
The test
|
The test
|
Please take a look at the draft in stage: http://docs.testing.ansible.com/ansible/latest/scenario_guides/guide_infoblox.html NOTE: This link may or may not work due to QA workflows |
Use cases with modules | ||
====================== | ||
|
||
You can use the ``nios`` modules in tasks to simplify common Infoblox workflows. Be sure to set up your `NIOS credentials <nios_credentials>`_ before following these examples. |
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.
Currently this looks like a link to a new file, rather than a relative link
http://docs.testing.ansible.com/ansible/latest/scenario_guides/nios_credentials
I really appreciate this document being created. I was a little confused though by the mention of the WAPI only in one specific spot. I assume the modules can ONLY talk to the WAPI so maybe a statement specifying that near the top and then no other mention of it. Would it be appropriate to mention in the prerequisites or authentication section that you need a NIOS account with the WAPI feature enabled? Or is that outside the scope of the document? |
972e0ad
to
6ed7724
Compare
* creates infoblox scenario guide * adds link to infoblox guide from modules * adds WAPI to prerequisites (cherry picked from commit df36559)
* creates infoblox scenario guide * adds link to infoblox guide from modules * adds WAPI to prerequisites (cherry picked from commit df36559)
SUMMARY
Closes issue #42964
Create Infoblox Scenario Guide
ISSUE TYPE
COMPONENT NAME
docs.ansible.com
ANSIBLE VERSION
ADDITIONAL INFORMATION