From fd61d2d34342da67f4710d06b4638d61095d816b Mon Sep 17 00:00:00 2001
From: Marian Tanase <mata@enea.se>
Date: Fri, 12 Oct 2018 15:51:50 +0300
Subject: ENEA NFV Core 1.1 Release Notes & Installation Guide Updates

---
 .../doc/post_deploy_scripts.xml                    | 37 ++++++++++++----------
 1 file changed, 21 insertions(+), 16 deletions(-)

(limited to 'book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml')

diff --git a/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml b/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml
index c4668e4..19a05d9 100644
--- a/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml
+++ b/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml
@@ -5,8 +5,8 @@
   <title>Post Deploy Scripts</title>
 
   <para>The Post Deploy Scripts is a collection of ENEA specific software that
-  can be used to easily modify existing environments. These projects can be
-  used in many situations, from installing new components to configuring
+  can be used to easily modify existing environments. These scripts can be
+  used in various situations, from installing new components to configuring
   existing ones in a fast and efficient way. They are located on the Fuel
   Master in <literal>/opt/enea/postdeployscripts/</literal>.</para>
 
@@ -28,7 +28,7 @@
       <para>Provider networks only handle layer-2 connectivity for instances,
       lacking support for features such as routers and floating IP addresses.
       Please refer to the <ulink
-      url="https://docs.openstack.org/ocata/install-guide-ubuntu/launch-instance-networks-provider.html">Openstack
+      url="https://docs.openstack.org/ocata/install-guide-ubuntu/launch-instance-networks-provider.html">OpenStack
       documentation</ulink> for examples on using provider networks.</para>
     </note>
 
@@ -82,7 +82,7 @@
 ./init.sh</programlisting></para>
 
         <para>This will create a hosts file that will be used by Ansible to
-        associate the nodes into groups and to access them. </para>
+        associate the nodes into groups and to access them.</para>
 
         <para>It will also create a file named
         <filename>samplenetworks.json</filename>, which will contain a single
@@ -125,31 +125,36 @@
         some interfaces included:<programlisting> {
     "networks":[
        {
-          "name":"prov-net",
-          "nodes":[
+          "allocation-pool": {
+                "end": "192.168.200.100",
+                "start": "192.168.200.20"
+            },
+            "enable-dhcp": "True",
+            "gateway": "192.168.200.1",
+            "name": "prov-net1",
+            "network-type": "vlan",
+            "nodes":[
              {
-                "name":"node-4",
-                "interfaces":[
-                   "em2p1s0f5"
+                    "interfaces": ["em5p144s0"],
+                    "name": "node-4"
                 ]
              },
              {
-                "name":"node-5",
-                "interfaces":[
-                   "em2p1s0f5"
-                ]
+                    "interfaces": ["em5p144s0"],
+                    "name": "node-5"
              }
-          ]
+          ],
+           "provider-segment": "2251",
+           "range": "192.168.200.0/24" 
        }
     ]
  }
-
  cp samplenetworks.json /opt/enea/postdeployscripts/provider-net/files/networks.json</programlisting>The
         snippet shown above infers the following:</para>
 
         <itemizedlist>
           <listitem>
-            <para>An Openstack provider network called
+            <para>An OpenStack provider network called
             <filename>prov-net</filename> will be created.</para>
           </listitem>
 
-- 
cgit v1.2.3-54-g00ecf