From 5926dab11469b581b6c25e54b63aca7965a5148c Mon Sep 17 00:00:00 2001 From: Peter Boy Date: Jun 12 2021 17:45:59 +0000 Subject: Final (hopefully) preparation for going online --- diff --git a/docs/modules/ROOT/pages/container-nspawn.adoc b/docs/modules/ROOT/pages/container-nspawn.adoc deleted file mode 100644 index 10c4213..0000000 --- a/docs/modules/ROOT/pages/container-nspawn.adoc +++ /dev/null @@ -1,194 +0,0 @@ -= Container systemd-nspawn – Installation -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33 -**** -[NOTE] -==== -Work in progress.General conceptualization of content, text completion in progress. - -Request for comments on the content concept -==== - - - -== Some Useful information - -The systemd-nspawn container runtime is part of the systemd system software. It has been offloaded into its own package, systemd-container, a while ago and must now installed separately. The toolset is powerful, yet lightweight and has low runtime overhead. - -The management tools already used for the host system are applied to containers simply by specifying an additional parameter (-m ), e.g. journalctl. Start and stop of containers is done using systemctl in the same way as all other system services. This makes the learning curve quite flat and maintenance quite simple. - -The creation of a container filesystem or the provision of a corresponding image is treated as "out of scope" by systemd-nspawn. There are a number of alternative options. By far the easiest and most efficient way is simply to use dnf in the container's directory, and this is the recommended procedure. Additional options are presented at the end. - -== Installation Destination - -The systemd-nspawn tools as machinctl first search for containers in /var/lib/machines/. If not exist, this directory is automatically created the installation process. For each container to be created, a subdirectory with its name will be generated and the it's directory tree will be created therein. The directory is therefore directly container ROOT. - -According to the default concept of Fedora Server disk partitioning, a separate logical volume should be created for this purpose and mounted at the respective position. There are 2 valid alternatives and one 'quick & dirty' solution: - -* Logical volume of appropriate size for all containers, formatted as BTRFS and mounted at /var/lib/machines -* For eaxch container a thin provisioned logical volume of appropriate inital size, formatted as XFS and mounted at /var/lib/machines/ - -and as a quick solution - -* Logical volume of appropriate size for all containers, formatted as XFS and mounted at /var/lib/machines - -The former one is the most recommended way. - -=== BTRFS Logical Volume - -(comming soon) - -=== Thin Provisioning XFS Volumes per Container - -(comming soon - -=== XFS Logical Volume - -(comming soon) - -== Software Installation - -* Checking SELinux labels according to the choosen storage alternative[source,] ----- -ls -alZ /var/lib/machines ----- - if necessary, fix the SELinux labels -[source,] ----- -[…]# restorecon -vFr /var/lib/machines -[…]# chown root:root /var/lib/machines -[…]# chmod 700 /var/lib/machines ----- - -* Installation step - -[source,] ----- - […]# dnf install systemd-container ----- - - -== Container Creation - -. Creating a Subdirectory - -** According to the storage strategie BTRFS subvolume, LVM thin volume, subdrectory - -. Creating Fedora 33 directory tree - -[source,] ----- - […]# dnf --releasever=33 --best --setopt=install_weak_deps=False --installroot=/var/lib/machines/{ctname}/ install dhcp-client dnf fedora-release glibc glibc-langpack-en glibc-langpack-de iproute iputils less passwd systemd vim-minimal ----- - - - During installation, a message appears several times: - [source,] ----- - Scriptlet executed: {PACKAGE} install-info: File or directory not found for /dev/nul ----- - - Can be savely be ignored. - -== Container Configuration And Commissioning -. **Set the password for root**: - - (for the time being SELinux must be switched into permissive mode, otherwise passwd fails) -[source,] ----- -[…]# setenforce 0 -[…]# systemd-nspawn -D /var/lib/machines/{ctname} passwd -## Example: […]# systemd-nspawn -D /var/lib/machines/testn passwd -[…]# setenforce 1 ----- - -. Configuring Network connectivity - -.. On Host - -.. Inside Container - -. Boot Container and loggin[source,] ----- -[…]# systemd-nspawn -D /var/lib/machines/{ctname} -b - -## expect -## OK Spawning container test01 on /var/l…01. -## OK … -##{ctname} login: ----- - -== Container as System Service -[source,] ----- -[…]# systemctl enable systemd-nspawn@{ctname} -[…]# systemctl start systemd-nspawn@{ctname} -[…]# systemctl status systemd-nspawn@{ctname} ----- - -Loggin to the container [source,] ----- -[…]# machinectl login {ctname} ----- - -Alternately (e.g. if login as root is blocked -[source,] ----- -[…]# machinectl shell {ctname} ----- - - -== Troubleshooting - -=== SELinux blocks container startup -* usual SELinux fix - -=== Root login fails -* journalctl displays: pam_securetty(login:auth): access denied: tty 'pts/0' is not secure ! -* Solution: Delete /etc/securetty[7] and /usr/share/factory/etc/securetty on the container file system. - -=== Using machinetl without root permission - -* (requires polkit fix) - -== Addendum - -=== Containers of foreign distributions - -==== Debian & Ubuntu - -Fedora includes a customized version of the Debian / Ubuntu installer. This can be used to create the file system for corresponding containers. [source,] ----- -[…]# dnf install debootstrap -[…]# debootstrap {distro} {targetdir} {repo-url} ----- - -As an Ubuntu example -[source,] ----- -[…]# debootstrap bionic /var/lib/machines/bionic http://archive.ubuntu.com/ubuntu ----- -and a Debian example[source,] ----- -[…]# debootstrap stable /var/lib/machines/deb http://dev.debian.org/debian ----- - -The installation process displays some error messages, about stub-resolv.con, release agent, of firewall config. These can savely be ignored. - -=== Project mkosi - -* Program very extensive -* Provide customer image management - -The project uses python and pip is a easy installation path. -[source,] ----- -[…]# yum install git -[…]# python3 -m pip install --user git+https://github.com/systemd/mkosi.git ----- -* start the program -* usage by example \ No newline at end of file diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc index 5201c6e..855218d 100644 --- a/docs/modules/ROOT/pages/index.adoc +++ b/docs/modules/ROOT/pages/index.adoc @@ -1,14 +1,9 @@ = Fedora Server Documentation -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Peter Boy; Jan Kuparinen; Peter W. Smith +:page-authors: {author}, {author_2}, {author_3} image::Logo_server2.png[Server] - -[NOTE] -==== -**Beta 1**! Please comment on server mailing list -==== [sidebar] **** Creation Date: 2021-03-10 | Last update: 2021-06-09 | Related Fedora Version(s): 34 @@ -18,49 +13,48 @@ Creation Date: 2021-03-10 | Last update: 2021-06-09 | Related Fedora Version(s): *As a user, you gain the opportunity to use the server of the future right now.* -Fedora Server provides a stable, flexible and universally adaptable basis for the everyday provision of digital services and information of all kinds by organizations and individuals, based on the latest technology and makes them available as early as possible. - -*As a developer or system integrator, you gain an eye on the server of the future.* +Fedora Server provides a stable, flexible and universally adaptable basis for the everyday provision of digital services and information, suitable for use by all kinds of organizations and individuals. +It is based on the latest technology and as such, brings the most modern environment to users as early as possible. -Fedora Server is a platform for developers and system integrators, which provides an implementation of the latest server technology for further evaluation and practical appropriation. +*As a developer or system integrator, you preview the server of the future.* +Fedora Server is a platform for developers and system integrators, providing an implementation of the latest server technology for further evaluation and practical use. -== What's Cooking +== What's in the Pipeline? -Currently, we work on several projects +Currently, several projects are in development: -- We are preparing Fedora Server 35 -- We are working on improving Server's documentation (you currently get a first glimpse) -- We are working on facilitating the deployment of key services by combining rpm and Ansible +- Preparations for Fedora Server 35 +- Improvements to the documentation (you're currently getting a preview) +- Facilitation of the deployment of key services by combining rpm and Ansible Stay tuned. The results will soon be visible. - == Why Use Fedora Server -Fedora Server Edition offers users and system administrators several attractive features +Fedora Server Edition offers users and system administrators several attractive features: -* The biannual release cycle allows the inclusion of the latest versions of system and application software almost immediately. This empowers users and system administrators to swiftly respond to new market options and changing or expanding customer requirements. +* *You get the latest software almost immediately*: Fedora Server's biannual release cycle allows for the inclusion of the latest versions of system and application software almost immediately. This empowers users and system administrators to swiftly respond to new market options and changing or expanding customer requirements. -* A sophisticated and highly engineered release and quality assurance process enables a high level of reliability and stability, despite a comparatively fast release cycle. This achieves an excellent balance between 'bleeding edge' and maturity for productive use in mainstream deployments. +* *You can trust it*: Fedora Server has a sophisticated and highly engineered release and quality assurance process, which enables a high level of reliability and stability, despite a comparatively fast release cycle. It therefore achieves an excellent balance between 'bleeding edge' and maturity for productive use in mainstream deployments. -* Enterprise-grade security minded, the Fedora release engineering results in carefully pre-configured releases, offering uncompromising security without prior extensive configuration work by system administrators. +* *Confidence in security*: Enterprise-grade security minded, the Fedora release engineering results in carefully pre-configured releases, offering uncompromising security without prior extensive configuration by system administrators. -* A great variety of available packages, all of them included in that elaborated release process, opens up a wide range of possibilities for building a server very flexibly according to customer specific needs and wishes. +* *You can get what you need*: Fedora Server has an extensive collection of available packages, all of them subject to the same extensive release process. This opens up a wide range of possibilities for building a server very flexibly according to customer specific needs and wishes. -* Inclusion of modern sysadmin tools (i.e. cockpit, dnf, systemd) in their latest stable version noticeably reduces the burden of system administration. +* *It will help ease a sysadmin workload*: Fedora Server includes the latest stable versions of modern sysadmin tools (i.e. cockpit, dnf, systemd), noticeably reducing the burden of system administration. -* Due to the release cycle less disruptive release jumps combine a very easy update process without re-installation requirements, and the option to skip one release jump, in case new capabilities are not immediately needed. Several small updates are easier to manage than a few but big updates. +* *Less disruption with upgrades*: Fedora Server's short release cycle means less disruptive release jumps. There is a very easy update process without re-installation requirements. There is also the option to skip one release cycle in case new capabilities are not immediately needed. Several small updates are easier to manage than a few big updates. -* Utmost freedom from restrictions imposed by commercial interests or corporate feature management and excellent backwards hardware compatibility (including a complete set of standard kernel drivers). +* *You've got the freedom you want*: Fedora Server allows utmost freedom from restrictions imposed by commercial interests or corporate feature management, combined with excellent backward hardware compatibility (including a complete set of standard kernel drivers). -* Developer find an excellent development environment for the next generation server as well as application software with the latest software versions available. +* *Developers will feel right at home*: Fedora Server is an excellent development environment for the next generation server as well as application software with the latest software versions available. == What You Will Find Here - Server installation and administration guides + -You find information about installation and basic system administration supplementing the general Fedora Installation Guide and System Administration Guide. Several other sections cover specific Fedora Server Edition related options and solutions. This includes virtualisation and containerisation in particular. +You find information about installation and basic system administration supplementing the general Fedora Installation Guide and System Administration Guide. Several other sections cover specific Fedora Server Edition related options and solutions. This includes virtualisation and containerization in particular. - Example Use Cases + @@ -68,7 +62,8 @@ Users describe how they use Fedora Server for a wide variety of tasks as well as - Tutorials + -Detailed step-by-step instructions are given for various typical areas of application. They are intended to enable not only experienced system administrators but also inexperienced users to safely install and configure the system. +Detailed step-by-step instructions are given for various typical areas of application. The tutorials are intended to enable not only experienced system administrators but also inexperienced users to safely install and configure the system. + - People, policies, and working methods diff --git a/docs/modules/ROOT/pages/server-administration.adoc b/docs/modules/ROOT/pages/server-administration.adoc index 7e96c58..ab1c743 100644 --- a/docs/modules/ROOT/pages/server-administration.adoc +++ b/docs/modules/ROOT/pages/server-administration.adoc @@ -1,6 +1,6 @@ = Fedora Server Edition Basic Administration Guide -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Peter Boy; Jan Kuparinen; Emmanuel Seyman +:page-authors: {author}, {author_2}, {author_3} [sidebar] **** diff --git a/docs/modules/ROOT/pages/server-communicating.adoc b/docs/modules/ROOT/pages/server-communicating.adoc index 7946a97..9d24532 100644 --- a/docs/modules/ROOT/pages/server-communicating.adoc +++ b/docs/modules/ROOT/pages/server-communicating.adoc @@ -6,16 +6,11 @@ Peter Boy; Jan Kuparinen **** Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: 2021-06-09 | Related Fedora Version(s): All **** -[NOTE] -==== -Placeholder! Please comment on server mailing list -==== - - For general troubleshooting help related to Fedora, please refer to link:https://ask.fedoraproject.org[Ask Fedora Forum]. If you found a bug, report it! + * link:https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to file a bug]. * Issues about a server can be filed at link:https://pagure.io/fedora-server/issues[the ticketing repository on Pagure]. diff --git a/docs/modules/ROOT/pages/server-community.adoc b/docs/modules/ROOT/pages/server-community.adoc deleted file mode 100644 index ffa39d2..0000000 --- a/docs/modules/ROOT/pages/server-community.adoc +++ /dev/null @@ -1,28 +0,0 @@ -= Server Community, Policies, and Working Methods -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Creation Date: 2021-03-09 | Last update: 2021-03-26 | Related Fedora Version(s): 34 -**** -[NOTE] -==== -First Collection of Ideas! Please comment on server mailing list -==== -[TIP] -==== -Intended content: Basic information on how work on Server is organized. In a first version probably just the most important content of the Working Group and the SIG and a collection of annotated links to the most important information sources (WG wiki, SIG wiki, Pagure, Fedora calendar, anything else?) -==== - - -(We should make the working group more "tangible" and transparent, not just refer to an (anonymous) mailing list.) - - - 1 SIG / Link to SIG Wiki - 1.1 Members of SIG - 2 WG / Link to WG Wiki - 2.1 Members of WG incl. Tasks / area of commitment - 2.1.1 Governance Charter - 3 Product Requirements Document - 4 Various other suitable contents of the Fedora Server Wiki pages \ No newline at end of file diff --git a/docs/modules/ROOT/pages/server-containers.adoc b/docs/modules/ROOT/pages/server-containers.adoc deleted file mode 100644 index aa9c4f1..0000000 --- a/docs/modules/ROOT/pages/server-containers.adoc +++ /dev/null @@ -1,85 +0,0 @@ -= Containerization -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: 2021-03-26 | Related Fedora Version(s): 34 -**** -[NOTE] -==== -Work in progress. Coming soon -==== - - -Planned content: - -(**Preliminary note**) - -* Currently on everyone's lips, prominent subject of public discussion -* Often equated with "Docker" -* But: One size doesn't fit all. There are alternatives, some with a different application profile. -* *Fedora Server supports and allows several alternatives that can be used depending on the local / user's requirement profile.* - -== Overview - -* All containers on a system use the same kernel -* Some kind of isolation using kernel capabilities (cname, etc) to isolate processes from each other -* Differences in implementations, toolset, environment, community -* system container vs application container (main feature existence of an init system) - -== Podman - -* application container -* security enhancement: no root privileges required -* optimized for interaction of several containers to perform a task -* same container image as Docker, mutually usable -* *natively supported by Fedora Server* - -== Docker - -* application container -* dependent on a Damon with ROOT privileges -* huge trove of pre-built containers for all sorts of software -* no native support for Fedora Server, but a *vendor repository* maintained for Fedora - -== LXC (libvirt) - -* system container -* support of container runtime based on kernel capabilities -* rough toolset support (requires composing various xml files) -* *natively supported by Fedora Server* (via libvirt as default virtualization tool) - -== LXC (linux containers) - -* system container -* one of the first implementations of containers -* system containers -* originally base of Docker -* complete toolset, container images, community -* *natively supported by Fedora Server* (just LTS versions) - -== LXD (linux containers) - -* system container -* LXC with advanced toolset -* not natively supported by Fedora, but a *COPR project* available -* *vendor support* for Fedora by third party package manager - -== systemd-nspawn container - -* system container and also configurable as a kind of application container -* rather new development -* toolset highly integrated into systemd system management -* "lightweight virtual machine" -* *natively supported by Fedora Server* - -== Linux Vserver - -* requires modified kernel -* *no native Fedora Server support* - -== OpenVZ - -* Uses a self customized version of RHEL / CentOS -* *Not applicable for Fedora Server* diff --git a/docs/modules/ROOT/pages/server-faq.adoc b/docs/modules/ROOT/pages/server-faq.adoc index ae7841e..9f4bc10 100644 --- a/docs/modules/ROOT/pages/server-faq.adoc +++ b/docs/modules/ROOT/pages/server-faq.adoc @@ -6,10 +6,6 @@ Peter Boy; Jan Kuparinen **** Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): All **** -[NOTE] -==== -Placeholder! Please comment on server mailing list -==== [qanda] Can I see a built preview of this template to get a better idea about the result?:: diff --git a/docs/modules/ROOT/pages/server-installation-sbc.adoc b/docs/modules/ROOT/pages/server-installation-sbc.adoc index a80382b..adccead 100644 --- a/docs/modules/ROOT/pages/server-installation-sbc.adoc +++ b/docs/modules/ROOT/pages/server-installation-sbc.adoc @@ -1,6 +1,6 @@ = Installing Fedora Server on Single Board Computers - Raspberry Pi & Co. -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Fredrik Arneving; Peter Boy; Jan Kuparinen +:page-authors: {author}, {author_2}, {author_3} [sidebar] **** diff --git a/docs/modules/ROOT/pages/server-installation.adoc b/docs/modules/ROOT/pages/server-installation.adoc index ab14571..1fd66aa 100644 --- a/docs/modules/ROOT/pages/server-installation.adoc +++ b/docs/modules/ROOT/pages/server-installation.adoc @@ -1,6 +1,6 @@ = Fedora Server Installation Guide -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Peter Boy; Kevin Fenzi; Jan Kuparinen +:page-authors: {author}, {author_2}, {author_3} [sidebar] **** diff --git a/docs/modules/ROOT/pages/server-troubleshooting.adoc b/docs/modules/ROOT/pages/server-troubleshooting.adoc deleted file mode 100644 index 009a672..0000000 --- a/docs/modules/ROOT/pages/server-troubleshooting.adoc +++ /dev/null @@ -1,40 +0,0 @@ -= Communicating and Getting Help -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: 2021-06-09 | Related Fedora Version(s): 34 -**** -[NOTE] -==== -First Collection of Ideas! Please comment on server mailing list -==== - - -Some examples from the latest discussions - -1. The well known BIOS boot partition issue -2. systemnd-oomd and httpd / jBoss/wildfly -3. UEFI – one ESP for /boot/efi requirement in software RAID 1 / RAID x -4. How manag SELinux issues - Link to Quick docs and to Cockpit SELinux page -+ -Specifically: don’t deactivate but resolve issues - -## Some generic information - - -If you found a bug, report it! - -* link:https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to file a bug]. - -* Issues about a server can be filed at link:https://pagure.io/fedora-server/issues[the ticketing repository on Pagure]. - -* You can chat with us at link:https://web.libera.chat/?channels=#fedora-server[#fedora-server on libera.chat]. - -* You can discuss server issues at link:https://discussion.fedoraproject.org/c/server[Server Discussion Forum]. - -* You can e-mail us on the Server mailing list at link:https://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org/[server@lists.fedoraproject.org]. - -For general troubleshooting help related to Fedora, please refer to link:https://ask.fedoraproject.org[Ask Fedora Forum]. - \ No newline at end of file diff --git a/docs/modules/ROOT/pages/server-tutorials.adoc b/docs/modules/ROOT/pages/server-tutorials.adoc deleted file mode 100644 index ad1dd6f..0000000 --- a/docs/modules/ROOT/pages/server-tutorials.adoc +++ /dev/null @@ -1,24 +0,0 @@ -= Fedora Server Tutorials -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33 -**** -[NOTE] -==== -First Collection of Ideas! Please comment on server mailing list -==== - - -Some ideas: - -- Setting up a dedicated rented off premise Internet Server (example Hetzner) -- Setting up a private local (on premise) Internet server -- Setting up an Internet server for SMEs -- Setting up a homelab / worklab Server -- Setting up a simple private Mail Server -- Setting up a full features Mail Server -- Backup Guide -- (more to come) \ No newline at end of file diff --git a/docs/modules/ROOT/pages/server-usecases.adoc b/docs/modules/ROOT/pages/server-usecases.adoc deleted file mode 100644 index 08a8ff7..0000000 --- a/docs/modules/ROOT/pages/server-usecases.adoc +++ /dev/null @@ -1,27 +0,0 @@ -= Fedora Server Example Use Cases -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33 -**** -[NOTE] -==== -First Collection of Ideas! Please comment on server mailing list -==== - - 1 Setting up a Fedora Local Home Server, including - 1.1 Security considerations - 1.2 Considerations organizing storage - 1.3 Configuring local network - 1.4 file services Windows. Apple, Fedora Workstation - 1.5 media server - 1.6 (personal web server, perhaps rather a bit off the mark) - 1.7 Again, probably providing a configurable / adaptable Ansible playbook - 2 Set up a Home Server Mail Service - (items according to above) - 3 More to come (hopefully) - - - diff --git a/docs/modules/ROOT/pages/server-virtualization.adoc b/docs/modules/ROOT/pages/server-virtualization.adoc index 83980ec..142d98f 100644 --- a/docs/modules/ROOT/pages/server-virtualization.adoc +++ b/docs/modules/ROOT/pages/server-virtualization.adoc @@ -1,6 +1,6 @@ = Virtualization -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Fredrik Arneving; Peter Boy; Jan Kuparinen +:page-authors: {author}, {author_2}, {author_3} [sidebar] **** diff --git a/docs/modules/ROOT/pages/sysadmin-cockpit.adoc b/docs/modules/ROOT/pages/sysadmin-cockpit.adoc deleted file mode 100644 index 22ac9ce..0000000 --- a/docs/modules/ROOT/pages/sysadmin-cockpit.adoc +++ /dev/null @@ -1,38 +0,0 @@ -= System Administration – Cockpit -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[NOTE] -==== -Collection of ideas. __** – Outline proposal –**__ Please comment on server mailing list -==== -[sidebar] -**** -Author: N.N) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33,34 -**** - -Preface / Why Cockoit -(see: Fedora Magazine: https://fedoramagazine.org/managing-software-and-services-with-cockpit ) - - -Allgemeines Management - • Übericht über Auslastung - • Restart System - • Benutzer verwaltung - • (Web) Terminal zugang - • Durchsicht Log Files - • Managing Updates - -Network Management - - • Disabling/Enabling interfaces - • Basic IP configuration (IP, subnet mask, gateway, DNS and such) - • Firewall changes (adding ports/services) - • Advanced configuration (VLAN creation for use in between VMs that require interconnectivity only between Vms) - • What about VPN? - • What about Firewall Management? - -Management Storage - • Anlegen von Log. Volumes (entsprechend dem Storage Konzep9 - - \ No newline at end of file diff --git a/docs/modules/ROOT/pages/sysadmin-postinstall.adoc b/docs/modules/ROOT/pages/sysadmin-postinstall.adoc index 2674351..a65a259 100644 --- a/docs/modules/ROOT/pages/sysadmin-postinstall.adoc +++ b/docs/modules/ROOT/pages/sysadmin-postinstall.adoc @@ -1,6 +1,6 @@ = System Administration – Post Installation Tasks -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Peter Boy; Kevin Fenzi; Jan Kuparinen +:page-authors: {author}, {author_2}, {author_3} [sidebar] **** diff --git a/docs/modules/ROOT/pages/virtualization-install.adoc b/docs/modules/ROOT/pages/virtualization-install.adoc index 948d2f5..eef727e 100644 --- a/docs/modules/ROOT/pages/virtualization-install.adoc +++ b/docs/modules/ROOT/pages/virtualization-install.adoc @@ -1,6 +1,6 @@ = Adding Virtualization Support -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} +Fredrik Arneving; Peter Boy; Jan Kuparinen +:page-authors: {author}, {author_2}, {author_3} [sidebar] **** diff --git a/docs/modules/ROOT/pages/virtualization-vmcloud.adoc b/docs/modules/ROOT/pages/virtualization-vmcloud.adoc index 74ecb5d..f9cefb8 100644 --- a/docs/modules/ROOT/pages/virtualization-vmcloud.adoc +++ b/docs/modules/ROOT/pages/virtualization-vmcloud.adoc @@ -1,11 +1,7 @@ = Virtual Machines based on Cloud Images -Peter Boy; Jan Kuparinen +Peter Boy; Jan Kuparinen; :page-authors: {author}, {author_2} -[NOTE] -==== -**Beta 1**! Please comment on server mailing list -==== [sidebar] **** Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33,34 diff --git a/docs/modules/ROOT/pages/virtualization-vminstall.adoc b/docs/modules/ROOT/pages/virtualization-vminstall.adoc deleted file mode 100644 index a8b62c0..0000000 --- a/docs/modules/ROOT/pages/virtualization-vminstall.adoc +++ /dev/null @@ -1,16 +0,0 @@ -= Installing Virtual Machines using Cockpit -Peter Boy; Jan Kuparinen -:page-authors: {author}, {author_2} - -[sidebar] -**** -Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33 -**** -[NOTE] -==== -Work in progress. Coming soon -==== - - - -