diff options
author | mrpa <miruna.paun@enea.com> | 2021-09-08 17:10:09 +0200 |
---|---|---|
committer | mrpa <miruna.paun@enea.com> | 2021-09-08 17:10:09 +0200 |
commit | 54386e07a52582e58b3c4fb24e6cbc8bd0c6a795 (patch) | |
tree | 4e137883a25ec002a417b8d7809cac968fcce868 /doc/book-enea-edge-getting-started/doc/vnf_mg.xml | |
parent | 43021dae86481d75899c7e512f6d2f9cd9dce48a (diff) | |
parent | 1677f82bb972ba060630cd1c08394459f9bb751b (diff) | |
download | nfv-access-documentation-54386e07a52582e58b3c4fb24e6cbc8bd0c6a795.tar.gz |
Merge the code from develop to master for 2.5.0demo_CPDX-3644demo_CPDX-3634
Change-Id: I47ebb99993f4603ef34f2366f679cc267bf0c995
Diffstat (limited to 'doc/book-enea-edge-getting-started/doc/vnf_mg.xml')
-rw-r--r-- | doc/book-enea-edge-getting-started/doc/vnf_mg.xml | 136 |
1 files changed, 129 insertions, 7 deletions
diff --git a/doc/book-enea-edge-getting-started/doc/vnf_mg.xml b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml index 058be40..beea8fc 100644 --- a/doc/book-enea-edge-getting-started/doc/vnf_mg.xml +++ b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml | |||
@@ -10,7 +10,7 @@ | |||
10 | <title>Onboarding a VNF</title> | 10 | <title>Onboarding a VNF</title> |
11 | 11 | ||
12 | <para>The onboarding of a VNF means adding it to the Enea Edge Management | 12 | <para>The onboarding of a VNF means adding it to the Enea Edge Management |
13 | application VNF Catalogue and preparing it for instantiation (deployment | 13 | application VNF Catalog and preparing it for instantiation (deployment |
14 | on connected uCPE devices). This is accomplished using the Enea Edge | 14 | on connected uCPE devices). This is accomplished using the Enea Edge |
15 | Management Onboarding graphical user interface.</para> | 15 | Management Onboarding graphical user interface.</para> |
16 | 16 | ||
@@ -210,9 +210,8 @@ | |||
210 | Management application.</para> | 210 | Management application.</para> |
211 | 211 | ||
212 | <note> | 212 | <note> |
213 | <para>CAUTION: The user MUST save and use the same order for the | 213 | <para>The user MUST save and use the same order for the virtual |
214 | virtual interfaces during both the onboarding and instantiation | 214 | interfaces during both the onboarding and instantiation phases.</para> |
215 | phases.</para> | ||
216 | </note> | 215 | </note> |
217 | 216 | ||
218 | <para><emphasis role="bold">Cloud Init Tab</emphasis></para> | 217 | <para><emphasis role="bold">Cloud Init Tab</emphasis></para> |
@@ -228,7 +227,7 @@ | |||
228 | <para>To onboard a VNF you must specify the <literal>Cloud-Init | 227 | <para>To onboard a VNF you must specify the <literal>Cloud-Init |
229 | Datasource</literal> that the VNF uses. This information is procured | 228 | Datasource</literal> that the VNF uses. This information is procured |
230 | from the VNF Vendor. Choose one of the following methods to specify | 229 | from the VNF Vendor. Choose one of the following methods to specify |
231 | the datasource:</para> | 230 | the data-source:</para> |
232 | 231 | ||
233 | <itemizedlist spacing="compact"> | 232 | <itemizedlist spacing="compact"> |
234 | <listitem> | 233 | <listitem> |
@@ -320,7 +319,7 @@ | |||
320 | </itemizedlist> | 319 | </itemizedlist> |
321 | 320 | ||
322 | <note> | 321 | <note> |
323 | <para>The last three properties are useful in conjuction with the | 322 | <para>The last three properties are useful in conjunction with the |
324 | <literal>vnfMgmt</literal> bridge type. They allow the user to map the | 323 | <literal>vnfMgmt</literal> bridge type. They allow the user to map the |
325 | internal VNF management port to an external port, useful for VNF | 324 | internal VNF management port to an external port, useful for VNF |
326 | configuration from WAN.</para> | 325 | configuration from WAN.</para> |
@@ -498,7 +497,8 @@ | |||
498 | role="bold">Reverse SSH</emphasis> . By default, the start port | 497 | role="bold">Reverse SSH</emphasis> . By default, the start port |
499 | will be <literal>7000</literal> and the maximum number of ports | 498 | will be <literal>7000</literal> and the maximum number of ports |
500 | allocated to all devices is 10. Only one port per device is | 499 | allocated to all devices is 10. Only one port per device is |
501 | allowed.</para> | 500 | allowed. The maximum number of ports allocated can be increased |
501 | up to 65536, if necessary.</para> | ||
502 | 502 | ||
503 | <para>When the SSH window is closed, the tunnel configuration is | 503 | <para>When the SSH window is closed, the tunnel configuration is |
504 | deleted on the uCPE device and the tunnel is destroyed, so that | 504 | deleted on the uCPE device and the tunnel is destroyed, so that |
@@ -526,4 +526,126 @@ | |||
526 | </listitem> | 526 | </listitem> |
527 | </orderedlist> | 527 | </orderedlist> |
528 | </section> | 528 | </section> |
529 | |||
530 | <section id="vnf_snapshots"> | ||
531 | <title>VNF Snapshots</title> | ||
532 | |||
533 | <para>The following sections describe the mechanism of saving | ||
534 | (snapshotting) and restoring a VNF context on the uCPE device using the | ||
535 | Enea Edge Management application.</para> | ||
536 | |||
537 | <para>The uCPE devices should be connected to the Enea Edge Management | ||
538 | application and should have at least one VNF instantiated.</para> | ||
539 | |||
540 | <section id="vnf_live_snapshot"> | ||
541 | <title>VNF Live Snapshot</title> | ||
542 | |||
543 | <para>To perform a snapshot of an existing VNF on a uCPE device, do the | ||
544 | following in the Enea Edge Management application:</para> | ||
545 | |||
546 | <orderedlist> | ||
547 | <listitem> | ||
548 | <para>Select the uCPE device and access the <emphasis | ||
549 | role="bold">Configuration</emphasis> menu, then select <emphasis | ||
550 | role="bold">Virtual Machines</emphasis> and <emphasis | ||
551 | role="bold">VMs</emphasis>.</para> | ||
552 | </listitem> | ||
553 | |||
554 | <listitem> | ||
555 | <para>Select a virtual machine and click the <emphasis | ||
556 | role="bold">Snapshots..</emphasis> button. The <emphasis | ||
557 | role="bold">VM Snapshot Table on <device-name> (IP)</emphasis> | ||
558 | window will open.</para> | ||
559 | </listitem> | ||
560 | |||
561 | <listitem> | ||
562 | <para>Press the <emphasis role="bold">Create</emphasis> button and | ||
563 | the <emphasis role="bold">Create VM Snapshot on <device-name> | ||
564 | (IP)</emphasis> window will open.</para> | ||
565 | </listitem> | ||
566 | |||
567 | <listitem> | ||
568 | <para>Change the file name, if needed, and press the <emphasis | ||
569 | role="bold">Create</emphasis> button. The current pop-up window will | ||
570 | close after a few seconds and a new entry will be shown in the | ||
571 | <emphasis role="bold">VM Snapshot Table on <device-name | ||
572 | (IP)></emphasis>.</para> | ||
573 | </listitem> | ||
574 | </orderedlist> | ||
575 | </section> | ||
576 | |||
577 | <section id="restore_snapshot"> | ||
578 | <title>Restoring a VNF Snapshot</title> | ||
579 | |||
580 | <para>When needed, a VNF snapshot can be restored by doing the | ||
581 | following:</para> | ||
582 | |||
583 | <orderedlist> | ||
584 | <listitem> | ||
585 | <para>Select the uCPE device and access the <emphasis | ||
586 | role="bold">Configuration</emphasis> menu, then select <emphasis | ||
587 | role="bold">Virtual Machines</emphasis> and choose <emphasis | ||
588 | role="bold">VMs</emphasis>.</para> | ||
589 | </listitem> | ||
590 | |||
591 | <listitem> | ||
592 | <para>Select a virtual machine and press the <emphasis | ||
593 | role="bold">Snapshots</emphasis> button. The <emphasis | ||
594 | role="bold">VM Snapshot Table on <device-name> (IP)</emphasis> | ||
595 | window will open.</para> | ||
596 | </listitem> | ||
597 | |||
598 | <listitem> | ||
599 | <para>Select the snapshot entry from table.</para> | ||
600 | </listitem> | ||
601 | |||
602 | <listitem> | ||
603 | <para>Press the <emphasis role="bold">Restore</emphasis> button. A | ||
604 | success message will appear in the same window: <literal>Restored VM | ||
605 | from snapshot</literal>.</para> | ||
606 | </listitem> | ||
607 | </orderedlist> | ||
608 | </section> | ||
609 | |||
610 | <section id="delete_snapshot"> | ||
611 | <title>Deleting a VNF Snapshot</title> | ||
612 | |||
613 | <para>Deleting an older snapshot can be performed by doing the | ||
614 | following:</para> | ||
615 | |||
616 | <orderedlist> | ||
617 | <listitem> | ||
618 | <para>Select the uCPE device and access the <emphasis | ||
619 | role="bold">Configuration</emphasis> menu, then select <emphasis | ||
620 | role="bold">Virtual Machines</emphasis> and choose <emphasis | ||
621 | role="bold">VMs</emphasis>.</para> | ||
622 | </listitem> | ||
623 | |||
624 | <listitem> | ||
625 | <para>Select a virtual machine and press the <emphasis | ||
626 | role="bold">Snapshots..</emphasis> button. The <emphasis | ||
627 | role="bold">VM Snapshot Table on <device-name> (IP)</emphasis> | ||
628 | window will open.</para> | ||
629 | </listitem> | ||
630 | |||
631 | <listitem> | ||
632 | <para>Select the snapshot entry from the table.</para> | ||
633 | </listitem> | ||
634 | |||
635 | <listitem> | ||
636 | <para>Press the <emphasis role="bold">Delete</emphasis> | ||
637 | button.</para> | ||
638 | </listitem> | ||
639 | </orderedlist> | ||
640 | |||
641 | <para>A success message will be shown in the same window: | ||
642 | <literal>Snapshot deleted</literal>. The snapshot file will be deleted | ||
643 | from the uCPE device and the table will be updated.</para> | ||
644 | |||
645 | <note> | ||
646 | <para>Deleting a VNF instance automatically deletes all snapshots | ||
647 | associated with it.</para> | ||
648 | </note> | ||
649 | </section> | ||
650 | </section> | ||
529 | </chapter> \ No newline at end of file | 651 | </chapter> \ No newline at end of file |