summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml')
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml43
1 files changed, 0 insertions, 43 deletions
diff --git a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
index 160190f..afcdec6 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
@@ -346,33 +346,11 @@ node0.1048576kB = 3 </programlisting>
346 </listitem> 346 </listitem>
347 </itemizedlist> 347 </itemizedlist>
348 348
349 <para>Optional parameters for sending status notifications to a
350 server. All three must be provided if used:</para>
351
352 <itemizedlist>
353 <listitem>
354 <para><literal>notify_user</literal>. Server SSH username.</para>
355 </listitem>
356
357 <listitem>
358 <para><literal>notify_pass</literal>. Server SSH password.</para>
359 </listitem>
360
361 <listitem>
362 <para><literal>notify_path</literal>. Location where notification
363 files will be placed, specified in <literal>Server
364 IP:directory</literal> format.</para>
365 </listitem>
366 </itemizedlist>
367
368 <para>Installation Configuration File Example:</para> 349 <para>Installation Configuration File Example:</para>
369 350
370 <programlisting> 351 <programlisting>
371 image_url = http://192.168.1.100/enea-nfv-access-xeon-d.hddimg.gz 352 image_url = http://192.168.1.100/enea-nfv-access-xeon-d.hddimg.gz
372 install_drive = /dev/sda 353 install_drive = /dev/sda
373 notify_user = username
374 notify_pass = password
375 notify_path = 192.168.1.100:/home/user/status_notifications
376 354
377</programlisting> 355</programlisting>
378 </section> 356 </section>
@@ -415,27 +393,6 @@ node0.1048576kB = 3 </programlisting>
415 <para>The uCPE devices should be configured in BIOS to boot from the 393 <para>The uCPE devices should be configured in BIOS to boot from the
416 installation drive first in order to automatically start the Enea NFV 394 installation drive first in order to automatically start the Enea NFV
417 Access Run Time Platform when the installation is finished.</para> 395 Access Run Time Platform when the installation is finished.</para>
418
419 <section>
420 <title>Server Notifications</title>
421
422 <para>Optionally, the uCPE devices can send a notification file to a
423 server once the installation is complete and Enea NFV Access Run Time
424 Platform has successfully booted. Notifications are enabled by
425 providing the <literal>notify_*</literal> parameters in the
426 installation configuration file.</para>
427
428 <para>Each uCPE device will push a file to the server location
429 specified in the installation configuration file. The file name will
430 be the MAC address of the PXE boot network interface in order to
431 uniquely identify the device.</para>
432
433 <note>
434 <para>Note that the status notification will only be sent on the
435 first boot after installation is done, subsequent reboots of the
436 uCPE device will not cause any new notifications to be sent.</para>
437 </note>
438 </section>
439 </section> 396 </section>
440 </section> 397 </section>
441</chapter> 398</chapter>