diff options
Diffstat (limited to 'doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml')
| -rw-r--r-- | doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml | 126 |
1 files changed, 0 insertions, 126 deletions
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml deleted file mode 100644 index 90ffb23..0000000 --- a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml +++ /dev/null | |||
| @@ -1,126 +0,0 @@ | |||
| 1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
| 2 | <chapter id="instantiation"> | ||
| 3 | <title>Instantiation</title> | ||
| 4 | |||
| 5 | <para>When a VNF is onboarded and available in the VNF catalog, it can be | ||
| 6 | instantiated (deployed) on connected uCPE devices. The instantiation wizard uses | ||
| 7 | the configurations provided when the VNF is onboarded, as a template for | ||
| 8 | instantiation. Before the instantiation, however, the uCPE device needs | ||
| 9 | to be prepared:</para> | ||
| 10 | |||
| 11 | <orderedlist> | ||
| 12 | <listitem> | ||
| 13 | <para>Physical NICs used with the VNF directly (through SR-IOV or PCI | ||
| 14 | Passthrough) or indirectly (through bridges) need to be configured | ||
| 15 | (Device->Configuration->OpenVSwitch->Host Interfaces).</para> | ||
| 16 | |||
| 17 | <note> | ||
| 18 | <para>Before configuring any physical NICs determine which is used for | ||
| 19 | managing the uCPE device. Altering the configuration of a NIC may cause | ||
| 20 | connectivity issues.</para> | ||
| 21 | </note> | ||
| 22 | </listitem> | ||
| 23 | |||
| 24 | <listitem> | ||
| 25 | <para>Add any needed bridges, connecting them to the physical NICs | ||
| 26 | previously configured or making them integration bridges (without | ||
| 27 | physical NIC) for service chaining.</para> | ||
| 28 | </listitem> | ||
| 29 | </orderedlist> | ||
| 30 | |||
| 31 | <para>Once the physical NICs and bridges are configured, the VNF can be | ||
| 32 | instantiated using the Instantiation Wizard.</para> | ||
| 33 | |||
| 34 | <section id="using_wiz"> | ||
| 35 | <title>Using the Instantiation Wizard</title> | ||
| 36 | |||
| 37 | <orderedlist> | ||
| 38 | <listitem> | ||
| 39 | <para>Enter the Instantiation Wizard by accessing VNF->Instances | ||
| 40 | and hitting <literal>Add</literal>.</para> | ||
| 41 | </listitem> | ||
| 42 | |||
| 43 | <listitem> | ||
| 44 | <para>Fill out the following mandatory fields:</para> | ||
| 45 | |||
| 46 | <itemizedlist spacing="compact"> | ||
| 47 | <listitem> | ||
| 48 | <para>Name (a descriptive name).</para> | ||
| 49 | </listitem> | ||
| 50 | |||
| 51 | <listitem> | ||
| 52 | <para>Device (the uCPE device to instantiate the VNF on).</para> | ||
| 53 | </listitem> | ||
| 54 | |||
| 55 | <listitem> | ||
| 56 | <para>Networking Configuration:</para> | ||
| 57 | |||
| 58 | <itemizedlist spacing="compact"> | ||
| 59 | <listitem> | ||
| 60 | <para>Connect each configured NIC with a bridge, SR-IOV or PCI | ||
| 61 | Passthrough.</para> | ||
| 62 | </listitem> | ||
| 63 | |||
| 64 | <listitem> | ||
| 65 | <para>Set up each NIC with a driver method (DPDK or | ||
| 66 | e1000).</para> | ||
| 67 | </listitem> | ||
| 68 | </itemizedlist> | ||
| 69 | |||
| 70 | <note> | ||
| 71 | <para>All configured NICs must be set up before instantiating a | ||
| 72 | VNF. Failure to do so will end in a failed instantiation.</para> | ||
| 73 | </note> | ||
| 74 | </listitem> | ||
| 75 | </itemizedlist> | ||
| 76 | </listitem> | ||
| 77 | |||
| 78 | <listitem> | ||
| 79 | <para>Add VNF specific configuration by uploading a Cloud-Init file | ||
| 80 | (when the Cloud-Init is used).</para> | ||
| 81 | </listitem> | ||
| 82 | |||
| 83 | <listitem> | ||
| 84 | <para>Add any VNF specific files (e.g license files).</para> | ||
| 85 | </listitem> | ||
| 86 | |||
| 87 | <listitem> | ||
| 88 | <para>Hit the <literal>Create</literal> button to deploy the VNF.</para> | ||
| 89 | </listitem> | ||
| 90 | </orderedlist> | ||
| 91 | </section> | ||
| 92 | |||
| 93 | <section id="enter_console"> | ||
| 94 | <title>Entering the VNF Console</title> | ||
| 95 | |||
| 96 | <para>Once the VNF is deployed, the VNF console can be entered using SSH | ||
| 97 | and virsh commands. The VNF Console is a typical starting point for | ||
| 98 | determining a successful deployment and configuring a VNF beyond Day | ||
| 99 | Zero.</para> | ||
| 100 | |||
| 101 | <orderedlist spacing="compact"> | ||
| 102 | <listitem> | ||
| 103 | <para>SSH to the uCPE device from the Enea uCPE Manager | ||
| 104 | (Device->SSH) with default user and password: | ||
| 105 | <literal>root</literal>.</para> | ||
| 106 | </listitem> | ||
| 107 | |||
| 108 | <listitem> | ||
| 109 | <para>In SSH:</para> | ||
| 110 | |||
| 111 | <orderedlist> | ||
| 112 | <listitem> | ||
| 113 | <para>Use the <command>virsh list</command> command to list all | ||
| 114 | running VNFs and to determine the VNF's instance number.</para> | ||
| 115 | </listitem> | ||
| 116 | |||
| 117 | <listitem> | ||
| 118 | <para>Use the <command>virsh console <instance | ||
| 119 | number></command> command to enter the VNF specific | ||
| 120 | console.</para> | ||
| 121 | </listitem> | ||
| 122 | </orderedlist> | ||
| 123 | </listitem> | ||
| 124 | </orderedlist> | ||
| 125 | </section> | ||
| 126 | </chapter> | ||