Remove bundle description files:

- containers-basic
- openssh-server
- os-core
- kvm-host

Signed-off-by: Michael Vincerra <michael.vincerra@intel.com>
This commit is contained in:
Michael Vincerra
2018-10-23 17:21:38 -07:00
parent a1553223bd
commit 6577f229d3
4 changed files with 0 additions and 307 deletions
@@ -1,41 +0,0 @@
.. _containers-basic:
containers-basic
################
The `containers-basic` bundle adds the necessary tools to enable running
containers using Docker*. The bundle includes Intel® |CC| as an
additional Docker runtime.
|CC| enable a hardware backed :abbr:`VM (Virtual Machine)` based
container runtime, compared with the normal software namespace containers
provided by standard Docker `runc` runtime.
Default runtime
===============
If your system has `VT-x` enabled, then, under |CL|, |CC|
will be used as the default Docker runtime, otherwise, the standard Docker
`runc` runtime will be used.
To identify which runtimes are available and which is being used as
the default on your installed system, run the following command.
.. code-block:: console
sudo docker info | grep Runtime
The |CC| runtime will be listed as `cor`.
For more information on |CC| please see the
`Clear Containers runtime GitHub`_.
Working with a proxy
====================
If you are behind an HTTP proxy server, in a corporate
setting for example, please follow the `Docker proxy instructions`_.
.. _Clear Containers runtime GitHub: https://github.com/01org/cc-oci-runtime
.. _Docker proxy instructions:
https://docs.docker.com/engine/admin/systemd/#http-proxy
@@ -1,42 +0,0 @@
.. _bdl-kvm-host:
kvm-host
########
This bundle provides the software needed to run virtual machines.
QEMU
====
|CL| provides :abbr:`QEMU (Quick Emulator)` to perform hardware virtualization.
When possible, qemu would be used together with
:abbr:`KVM (Kernel-based Virtual Machine)` in order to run virtual machines at
near-native speed.
For more information about how to use qemu, please refer to `qemu.org`_
virsh
=====
|CL| provides the virsh program to manage `libvirt`_ guests and the hypervisor.
libvirtd management daemon is not enabled nor started by default. To enable
the hypervisor, perform the following commands as root.
#. Enable the service to start every time the machine boots.
This step is optional
.. code-block:: console
# systemctl enable libvirtd.service
#. Start the libvirtd management daemon service
.. code-block:: console
# systemctl start libvirtd.service
Congratulations! The libvirtd management daemon is running and virsh is ready
to be used.
.. _qemu.org: http://www.qemu.org/
.. _libvirt: http://libvirt.org/
@@ -1,118 +0,0 @@
.. _bdl-openssh-server:
openssh-server
##############
The **openssh-server** bundle provides the OpenSSH\* package needed to enable
a SSH service in |CL-ATTR|. Remote users require a SSH service to be able to
use an encrypted login shell.
|CL| enables the `sshd.socket` unit, which will listen on port 22 by default
and start the OpenSSH service as required. The first time OpenSSH starts, it
generates the server SSH keys needed for the service.
Change default port
*******************
Perform the following steps to change the default listen port for the
OpenSSH service:
#. Open the sshd.socket file:
.. code-block:: bash
sudo systemctl edit sshd.socket
#. Add the `[Socket]` section and `ListenStream` option to the sshd.socket
file as shown below. The first `ListenStream` entry removes the |CL|
default listen port value. The second `ListenStream` entry sets the new
default listen port value. In this example, we set the new default port
to 4200:
.. code-block:: console
[Socket]
ListenStream=
ListenStream=4200
Make sure to include a new line after the last line of text in the sshd.socket file.
#. Verify your changes:
.. code-block:: bash
cat /etc/systemd/system/sshd.socket.d/override.conf
You should see the following output:
.. code-block:: console
[Socket]
ListenStream=
ListenStream=4200
#. Reload the systemd daemon configurations:
.. code-block:: bash
sudo systemctl daemon-reload
#. Restart the sshd.socket unit:
.. code-block:: bash
sudo systemctl restart sshd.socket
#. Confirm the the sshd.socket unit is listening on your new port:
.. code-block:: bash
systemctl status sshd.socket
Enable SFTP
***********
|CL| *disables* the :abbr:`SFTP (SSH File Transfer Protocol)` subsystem by
default due to security considerations. To enable the SFTP subsystem, perform
the following configuration of the :abbr:`SSHD (SSH Daemon)` service file:
#. Create a systemd drop-in directory for the SSHD service:
.. code-block:: bash
mkdir -p /etc/systemd/system/sshd@.service.d
#. Create the following file:
:file:`/etc/systemd/system/sshd@.service.d/sftp.conf`
#. Add the OPTIONS environment variable to the sftp.conf file.
.. code-block:: console
[Service]
Environment="OPTIONS=-o Subsystem=\"sftp /usr/libexec/sftp-server\""
#. Reload systemd configuration:
.. code-block:: bash
systemctl daemon-reload
Congratulations! The SFTP subsystem is enabled.
Enable root login
*****************
To enable root login via SSH, perform the following steps:
#. Create a *ssh* directory in :file:`/etc`, if it does not already exist.
.. code-block:: bash
mkdir /etc/ssh
#. Set the configuration variable.
.. code-block:: bash
echo "PermitRootLogin yes" >> /etc/ssh/sshd_config
@@ -1,106 +0,0 @@
.. _os-core:
os-core
#######
This bundle contains the basic core components of the operating system.
|CLOSIA| relies on `systemd` to provide the basic OS components. The
`systemd` package contains solutions for:
* Service management
* Basic network management
* Hostname management
* Time synchronization management
* Boot control management
* Journal management
Additionally, `os-core` includes the `util-linux` and `coreutils` packages to
provide a set of basic Linux\* command line tools such as `ls`, `cp`, `rm`,
etc.
Static IP
=========
To configure a static IP, follow these steps:
#. Create the file: :file:`/etc/systemd/network/50-static.network` If the
path does not exist, create it.
#. Add, at the very least, the following lines to the
:file:`50-static.network` file:
.. code-block:: console
[Match]
Name=<device_name>
[Network]
Address=<Provide a static IPv4 or IPv6 address with its
prefix length. Separate them with the "/" character.>
Gateway=<The gateway's address>
The `<device_name>` is your network device name, for example: enp1s0 or
enp0s25.
#. To add more options you can consult the `systemd network configuration`_
manual.
#. Restart the *systemd-networkd* service with the following command:
.. code-block:: console
# systemctl restart systemd-networkd
Alternatively, restart |CL|.
#. Check the new IP with the following command:
.. code-block:: console
# ip addr
Setting time
============
Clear Linux uses the `systemd-timesyncd.service` service to synchronize the
system's time. Default :abbr:`NTP (Network Time Protocol)` servers are
configured, for example: `time1.google.com`, `time2.google.com`,
`time3.google.com`, and `time4.google.com`. Manually setting the time via
`timedatectl` or using RTC mode is not possible. If those servers cannot be
reached and the system time is incorrect, follow these steps:
#. Set the timezone, for example, Pacific time:
.. code-block:: console
timedatectl set-timezone America/Los_Angeles
To see a list of timezones, use the following command:
.. code-block:: console
timedatectl list-timezones
#. Go to the :file:`/etc/systemd/` directory, if it does not exist, create
it.
#. Create the :file:`/etc/systemd/timesyncd.conf` file and enter the
following lines:
.. code-block:: console
[Time]
NTP=<Preferred Server>
FallbackNTP=<backup server 1> <backup server 2>
#. Restart the timesync daemon with the following command:
.. code-block:: console
# systemctl restart systemd-timesyncd
.. _systemd network configuration:
https://www.freedesktop.org/software/systemd/man/systemd.network.html