afonso/core-extra
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

initial commit removing all related xen code, docs, files

Browse source
This commit is contained in:
Blake J. Harnden 2018-03-07 15:47:14 -08:00
parent 940e10ef5e
commit a5370ee28c
39 changed files with 80 additions and 1771 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/install.rst
View file

@ -449,9 +449,6 @@ This causes a separate init script to be installed that is tailored towards SUSE
The `zypper` command is used instead of `yum`.
For OpenSUSE/Xen based installations, refer to the `README-Xen` file included
in the CORE source.
The Quagga routing suite is recommended for routing,
:ref:`Quagga_Routing_Software` for installation.

28
doc/machine.rst
View file

@ -22,9 +22,9 @@ netns
The *netns* machine type is the default. This is for nodes that will be
backed by Linux network namespaces. See :ref:`Linux` for a brief explanation of
netns. This default machine type is very lightweight, providing a minimum
netns. This default machine type is very lightweight, providing a minimum
amount of
virtualization in order to emulate a network.
virtualization in order to emulate a network.
Another reason this is designated as the default machine type
is because this virtualization technology
typically requires no changes to the kernel; it is available out-of-the-box
@ -54,7 +54,7 @@ isolated or virtualized environment, but directly on the operating system.
Physical nodes must be assigned to servers, the same way nodes
are assigned to emulation servers with :ref:`Distributed_Emulation`.
The list of available physical nodes currently shares the same dialog box
and list as the emulation servers, accessed using the *Emulation Servers...*
and list as the emulation servers, accessed using the *Emulation Servers...*
entry from the *Session* menu.
.. index:: GRE tunnels with physical nodes
@ -65,27 +65,7 @@ is drawn to indicate network tunneling. A GRE tunneling interface will be
created on the physical node and used to tunnel traffic to and from the
emulated world.
Double-clicking on a physical node during runtime
Double-clicking on a physical node during runtime
opens a terminal with an SSH shell to that
node. Users should configure public-key SSH login as done with emulation
servers.
.. _xen:
xen
===
.. index:: xen machine type
The *xen* machine type is an experimental new type in CORE for managing
Xen domUs from within CORE. After further development,
it may be documented here.
Current limitations include only supporting ISO-based filesystems, and lack
of integration with node services, EMANE, and possibly other features of CORE.
There is a :file:`README-Xen` file available in the CORE source that contains
further instructions for setting up Xen-based nodes.

3
doc/man/Makefile.am
View file

@ -12,7 +12,7 @@ if WANT_GUI
endif
if WANT_DAEMON
DAEMON_MANS = vnoded.1 vcmd.1 netns.1 core-daemon.1 coresendmsg.1 \
core-cleanup.1 core-xen-cleanup.1 core-manage.1
core-cleanup.1 core-manage.1
endif
man_MANS = $(GUI_MANS) $(DAEMON_MANS)
@ -25,7 +25,6 @@ generate-mans:
$(HELP2MAN) --version-string=$(CORE_VERSION) --no-info --source CORE $(top_srcdir)/daemon/sbin/core-daemon -o core-daemon.1.new
$(HELP2MAN) --version-string=$(CORE_VERSION) --no-info --source CORE $(top_srcdir)/daemon/sbin/coresendmsg -o coresendmsg.1.new
$(HELP2MAN) --version-string=$(CORE_VERSION) --no-info --source CORE $(top_srcdir)/daemon/sbin/core-cleanup -o core-cleanup.1.new
$(HELP2MAN) --version-string=$(CORE_VERSION) --no-info --source CORE $(top_srcdir)/daemon/sbin/core-xen-cleanup -o core-xen-cleanup.1.new
$(HELP2MAN) --version-string=$(CORE_VERSION) --no-info --source CORE $(top_srcdir)/daemon/sbin/core-manage -o core-manage.1.new
.PHONY: diff

1
doc/man/core-cleanup.1
View file

@ -20,7 +20,6 @@ remove the core-daemon.log file
.BR core-gui(1),
.BR core-daemon(1),
.BR coresendmsg(1),
.BR core-xen-cleanup(1),
.BR vcmd(1),
.BR vnoded(1)
.SH BUGS

28
doc/man/core-xen-cleanup.1
View file

@ -1,28 +0,0 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.40.4.
.TH CORE-XEN-CLEANUP "1" "2014-08-06" "CORE-XEN-CLEANUP" "User Commands"
.SH NAME
core-xen-cleanup \- clean-up script for CORE Xen domUs
.SH DESCRIPTION
usage: core\-xen\-cleanup [\-d]
.IP
Clean up all CORE Xen domUs, bridges, interfaces, and session
directories. Options:
.TP
\fB\-h\fR
show this help message and exit
.TP
\fB\-d\fR
also kill the Python daemon
.SH "SEE ALSO"
.BR core-gui(1),
.BR core-daemon(1),
.BR coresendmsg(1),
.BR core-cleanup(1),
.BR vcmd(1),
.BR vnoded(1)
.SH BUGS
Warning! This script will remove logical volumes that match the name "/dev/vg*/c*-n*-" on all volume groups. Use with care.
Report bugs to
.BI core-dev@pf.itd.nrl.navy.mil.

5
doc/usage.rst
View file

@ -1436,7 +1436,6 @@ Default Services and Node Types
Here are the default node types and their services:
.. index:: Xen
.. index:: physical nodes
* *router* - zebra, OSFPv2, OSPFv3, and IPForward services for IGP
@ -1450,10 +1449,6 @@ Here are the default node types and their services:
* *prouter* - a physical router, having the same default services as the
*router* node type; for incorporating Linux testbed machines into an
emulation, the :ref:`Machine_Types` is set to :ref:`physical`.
* *xen* - a Xen-based router, having the same default services as the
*router* node type; for incorporating Xen domUs into an emulation, the
:ref:`Machine_Types` is set to :ref:`xen`, and different *profiles* are
available.
Configuration files can be automatically generated by each service. For
example, CORE automatically generates routing protocol configuration for the