Skip to content
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

Merged
merged 29 commits into from
Sep 24, 2018
Merged

Infoblox scenario guide #45664

merged 29 commits into from
Sep 24, 2018

Conversation

samccann
Copy link
Contributor

SUMMARY

Closes issue #42964

Create Infoblox Scenario Guide

ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME

docs.ansible.com

ANSIBLE VERSION
2.8
ADDITIONAL INFORMATION

@samccann samccann added networking Network category docs This issue/PR relates to or includes documentation. labels Sep 14, 2018
@samccann samccann added this to Docsite work in Ansible-maintained Collections Documentation via automation Sep 14, 2018
@ansibot
Copy link
Contributor

ansibot commented Sep 14, 2018

The test ansible-test sanity --test rstcheck [explain] failed with 2 errors:

docs/docsite/rst/scenario_guides/guide_infoblox.rst:124:0: (bash) `<...output omitted...>'
docs/docsite/rst/scenario_guides/guide_infoblox.rst:124:0: (bash) syntax error near unexpected token `newline'

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented Sep 14, 2018

@ansibot ansibot added WIP This issue/PR is a work in progress. Nevertheless it was shared for getting input from peers. affects_2.8 This issue/PR affects Ansible v2.8 ci_verified Changes made in this PR are causing tests to fail. support:core This issue/PR relates to code supported by the Ansible Engineering Team. and removed ci_verified Changes made in this PR are causing tests to fail. labels Sep 14, 2018
@ansibot
Copy link
Contributor

ansibot commented Sep 14, 2018

The test ansible-test sanity --test rstcheck [explain] failed with 2 errors:

docs/docsite/rst/scenario_guides/guide_infoblox.rst:133:0: (bash) `    }'
docs/docsite/rst/scenario_guides/guide_infoblox.rst:133:0: (bash) syntax error near unexpected token `}'

click here for bot help

@ansibot ansibot added ci_verified Changes made in this PR are causing tests to fail. and removed ci_verified Changes made in this PR are causing tests to fail. labels Sep 14, 2018
@ansibot
Copy link
Contributor

ansibot commented Sep 14, 2018

The test ansible-test sanity --test rstcheck [explain] failed with 2 errors:

docs/docsite/rst/scenario_guides/guide_infoblox.rst:135:0: (bash) `    }'
docs/docsite/rst/scenario_guides/guide_infoblox.rst:135:0: (bash) syntax error near unexpected token `}'

click here for bot help

@ansibot ansibot added the ci_verified Changes made in this PR are causing tests to fail. label Sep 14, 2018
Copy link
Contributor

@acozine acozine left a 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.
Copy link
Contributor

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.

Copy link
Contributor

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:
Copy link
Contributor

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`_.
Copy link
Contributor

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.
Copy link
Contributor

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.
Copy link
Contributor

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?

@ansibot
Copy link
Contributor

ansibot commented Sep 14, 2018

The test ansible-test sanity --test rstcheck [explain] failed with 2 errors:

docs/docsite/rst/scenario_guides/guide_infoblox.rst:135:0: (bash) `    }'
docs/docsite/rst/scenario_guides/guide_infoblox.rst:135:0: (bash) syntax error near unexpected token `}'

click here for bot help

@ansibot ansibot removed the ci_verified Changes made in this PR are causing tests to fail. label Sep 17, 2018
@ansibot
Copy link
Contributor

ansibot commented Sep 17, 2018

The test ansible-test sanity --test docs-build [explain] failed with 1 error:

docs/docsite/rst/scenario_guides/guide_infoblox.rst:51:0: undefined-label: undefined label: set_fact (if the link has no caption the label must precede a section header)

click here for bot help

@ansibot ansibot added ci_verified Changes made in this PR are causing tests to fail. and removed ci_verified Changes made in this PR are causing tests to fail. labels Sep 17, 2018
@samccann samccann changed the title [WIP] Infoblox scenario guide Infoblox scenario guide Sep 17, 2018
@ansibot ansibot added needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. and removed WIP This issue/PR is a work in progress. Nevertheless it was shared for getting input from peers. needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. labels Sep 17, 2018
@abenokraitis
Copy link
Contributor

abenokraitis commented Sep 18, 2018

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.
Copy link
Contributor

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

@housysadm
Copy link
Contributor

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?

@acozine acozine merged commit df36559 into ansible:devel Sep 24, 2018
Ansible-maintained Collections Documentation automation moved this from Docsite work to Done Sep 24, 2018
samccann added a commit to samccann/ansible that referenced this pull request Nov 5, 2018
* creates infoblox scenario guide
* adds link to infoblox guide from modules
* adds WAPI to prerequisites

(cherry picked from commit df36559)
abadger pushed a commit that referenced this pull request Nov 5, 2018
* creates infoblox scenario guide
* adds link to infoblox guide from modules
* adds WAPI to prerequisites

(cherry picked from commit df36559)
@samccann samccann deleted the infoblox-guide branch December 6, 2018 21:32
@ansible ansible locked and limited conversation to collaborators Jul 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.8 This issue/PR affects Ansible v2.8 docs This issue/PR relates to or includes documentation. networking Network category support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

6 participants