Refactored Chapter 4 regarding Tacker

I mde Chapter 4 Installing Tacker a section (4.1)
of Chapter 4 Tacker and added a new section (4.2 Using Tacker)

Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>

1 files changed, 195 insertions, 28 deletions

diff --git a/book-enea-nfv-core-installation-guide/doc/tacker.xml b/book-enea-nfv-core-installation-guide/doc/tacker.xml
index 249e6d9..b8d6e6f 100644
--- a/book-enea-nfv-core-installation-guide/doc/tacker.xml
+++ b/book-enea-nfv-core-installation-guide/doc/tacker.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <chapter id="tacker">
-  <title>Installing Tacker</title>
+  <title>Tacker</title>
 
   <para><emphasis role="bold">Tacker</emphasis> is an OpenStack project,
   building a generic VNF Manager and a NFV Orchestrator in order to deploy and
@@ -9,21 +9,24 @@
   and provides a functional stack to Orchestrate Network Services end-to-end
   using VNFs.</para>
 
-  <para>Execute the following in the Fuel master console:</para>
+  <section id="install_tacker">
+    <title>Installing Tacker</title>
 
-  <orderedlist>
-    <listitem>
-      <para>Go to the tacker plugin directory:<programlisting>cd /var/www/nailgun/plugins/tacker-1.0/repositories/tacker</programlisting></para>
-    </listitem>
+    <para>Execute the following in the Fuel master console:</para>
 
-    <listitem>
-      <para>Execute the following to install Ansible: <programlisting>yum install ansible</programlisting></para>
-    </listitem>
+    <orderedlist>
+      <listitem>
+        <para>Go to the tacker plugin directory:<programlisting>cd /var/www/nailgun/plugins/tacker-1.0/repositories/tacker</programlisting></para>
+      </listitem>
 
-    <listitem>
-      <para>Run the initialization script:<programlisting>./files/init.sh</programlisting>This
-      will create a hosts file for ansible
-      <literal>/etc/ansible/hosts</literal> of the form:<programlisting>**********
+      <listitem>
+        <para>Execute the following to install Ansible: <programlisting>yum install ansible</programlisting></para>
+      </listitem>
+
+      <listitem>
+        <para>Run the initialization script:<programlisting>./files/init.sh</programlisting>This
+        will create a hosts file for ansible
+        <literal>/etc/ansible/hosts</literal> of the form:<programlisting>**********
 [controllers]
 node-3 mac_addr+68:05:ca:46:8b:64 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=******
 node-2 mac_addr+68:05:ca:46:8c:d4 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=******
@@ -37,19 +40,183 @@ node-4 mac_addr+68:05:ca:46:8c:c2 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=***
 controllers
 computes
 **********</programlisting></para>
-    </listitem>
-
-    <listitem>
-      <para>Use your favorite text editor to manually edit
-      <literal>ipmi_ip</literal> with the ip address of the ipmi interface,
-      <literal>ipmi_user</literal> with the user for accessing the ipmi
-      interface, and <literal>ipmi_psss</literal> with the password used by
-      the user to access the ipmi interface for all the nodes.</para>
-    </listitem>
-
-    <listitem>
-      <para>Run the ansible playbook responsible with the installation and
-      configuration of tacker plugin.<programlisting>ansible-playbook tacker_deploy.yaml</programlisting></para>
-    </listitem>
-  </orderedlist>
+      </listitem>
+
+      <listitem>
+        <para>Use your favorite text editor to manually edit
+        <literal>ipmi_ip</literal> with the ip address of the ipmi interface,
+        <literal>ipmi_user</literal> with the user for accessing the ipmi
+        interface, and <literal>ipmi_psss</literal> with the password used by
+        the user to access the ipmi interface for all the nodes.</para>
+      </listitem>
+
+      <listitem>
+        <para>Run the ansible playbook responsible with the installation and
+        configuration of tacker plugin.<programlisting>ansible-playbook tacker_deploy.yaml</programlisting></para>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="install_tacker">
+    <title>Using Tacker</title>
+
+    <para>After Tacker has been installed and configured, perform the
+    following in order to start a VNF:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Log in using SSH to the controller node where Tacker has been
+        installed (Example here node-5) and authenticate with
+        openstack:</para>
+
+        <programlisting>[root@fuel ~]# ssh node-5
+root@node-5:~# . openrc</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Activate the virtual environment for Tacker:</para>
+
+        <programlisting>root@node-5:~# source /usr/share/tacker_venv/bin/activate</programlisting>
+
+        <para>All subsequent commands will be executed in the venv.</para>
+      </listitem>
+
+      <listitem>
+        <para>Register a default VIM:</para>
+
+        <programlisting>(tacker_venv) root@node-5:~# tacker vim-register --is-default --config-file
+testvim.yaml --description 'Default VIM' defaultVim</programlisting>
+
+        <para>The sample .yaml file has the following contents</para>
+
+        <programlisting>auth_url: '&lt;keystone-auth_url&gt;'
+username: 'admin'
+password: '&lt;password&gt;'
+project_name: 'admin'
+project_domain_name: 'Default'
+user_domain_name: 'Default'
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Define a VNF Descriptor (VNFD):</para>
+
+        <programlisting>(tacker_venv) root@node-5:~# tacker vnfd-create --vnfd-file testvnf.yaml TestVNF</programlisting>
+
+        <para>The sample .yaml file has the following contents:</para>
+
+        <programlisting>tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0
+
+description: Demo example
+
+metadata:
+  template_name: sample-tosca-vnfd
+
+topology_template:
+
+  node_templates:
+    VDU1:
+      type: tosca.nodes.nfv.VDU.Tacker
+      capabilities:
+        nfv_compute:
+          properties:
+            num_cpus: 1
+            mem_size: 512 MB
+            disk_size: 1 GB
+      properties:
+        image: TestVM
+        flavor: m1.tiny
+        availability_zone: nova
+        mgmt_driver: noop
+        metadata: {metering.vnf: VDU1}
+        monitoring_policy:
+          name: noop    # was ping
+          # parameters:
+          #   monitoring_delay: 45
+          #   count: 3
+          #   interval: 1
+          #   timeout: 2
+          # actions:
+          #   failure: respawn
+    CP1:
+      type: tosca.nodes.nfv.CP.Tacker
+      properties:
+        order: 0
+        anti_spoofing_protection: false
+      requirements:
+        - virtualLink:
+            node: VL1
+        - virtualBinding:
+            node: VDU1
+
+    VL1:
+      type: tosca.nodes.nfv.VL
+      properties:
+        network_name: admin_internal_net
+        vendor: Tacker
+
+    FIP1:
+      type: tosca.nodes.network.FloatingIP
+      properties:
+         floating_network: admin_floating_net
+      requirements:
+        - link:
+            node: CP1
+
+  outputs:
+    mgmt_ip-VDU1:
+      description: 'management ip address'
+      value: { get_attr: [FIP1, floating_ip_address] }
+
+  policies:
+    - vdu1_respawn_on_error:
+        type: tosca.policies.tacker.AlarmingEvent
+        targets: [VDU1]
+        triggers:
+            vdu1_down:
+                event_type:
+                    type: tosca.events.resource.event
+                    implementation: ceilometer
+                condition:
+                    resource: compute.instance.*
+                    field: traits.state
+                    value: error
+                    op: eq
+                metadata: VDU1
+                actions: [respawn]</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Start a VNF:</para>
+
+        <programlisting>(tacker_venv) root@node-5:~# tacker vnf-create --vnfd-name TestVNF someVnf</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Verify:</para>
+
+        <programlisting>(tacker_venv) root@node-5:~# tacker vnf-list</programlisting>
+
+        <programlisting>+------------+---------+-----------------------+--------+----------+-----------+
+| id         | name    | mgmt_url              | status | vim_id   | vnfd_id   |
++------------+---------+-----------------------+--------+----------+-----------+
+| &lt;VNF-UUID&gt; | someVnf | {"VDU1": "&lt;MGMT-IP&gt;"} | ACTIVE | &lt;VIM-ID&gt; | &lt;VNFD-ID&gt; |
++------------+---------+-----------------------+--------+----------+-----------+
+</programlisting>
+
+        <programlisting> root@node-5:~# nova list</programlisting>
+
+        <programlisting>+-----------+---------------+--------+------------+-------------+
+| ID        | Name          | Status | Task State | Power State |
++-----------+---------------+--------+------------+-------------+
+| &lt;VM-UUID&gt; | ta-&lt;NAME&gt;     | ACTIVE | -          | Running     |
++-----------+---------------+--------+------------+-------------+
+-------------------------------------------------+
+ Networks                                        |
+-------------------------------------------------+
+ admin_internal_net=&lt;INTERNAL-IP&gt;, &lt;FLOATING-IP&gt; |
+-------------------------------------------------+</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
 </chapter>
\ No newline at end of file