From 40fb5e3ecf5e2a7dc23b7ef2b062b9d4ed55ac55 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Fri, 26 Jun 2015 12:52:52 -0400 Subject: [PATCH] Update Readme based on feedback from 193709 Change-Id: Ia5d50a45daa20ca3de77fa2d0bf4fca84c0b68f5 --- README.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index cc21627a1..8dceb180e 100644 --- a/README.rst +++ b/README.rst @@ -90,7 +90,7 @@ hardware. When utilizing the dynamic inventory module and accompanying roles this can be supplied in one of three ways, all of which ultimately translate to JSON data that Ansible parses. -The original method is to utilize a CSV file. Its format is below covered in +The original method is to utilize a CSV file. This format is covered below in the `Legacy CSV File Format` section. This has a number of limitations, but does allow a user to bulk load hardware from an inventory list with minimal data transformations. @@ -186,7 +186,7 @@ The CSV file has the following columns: Example definition:: - 00:11:22:33:44:55,root,undefined,192.168.122.1,1,8192,512,NA,NA,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,hostname_100,192.168.2.100,,,, + 00:11:22:33:44:55,root,undefined,192.168.122.1,1,8192,512,NA,NA,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,hostname_100,192.168.2.100,,,,agent_ipmitool This file format is fairly flexible and can be easily modified although the enrollment and deployment playbooks utilize the model