cloudstack/docs/en-US/hypervisor-host-install-security-policies.xml
Wido den Hollander b6a610e2db docs: Work on Management Server and Hypervisor Host installation
The Hypervisor installation describes what cloud-setup-agent is actually doing, but this way administrators know what the tool is doing.

We could remove all these things from cloud-setup-agent and require system administrators to perform these steps them selfs, this way
we don't break anything on their systems.

It would make setting up Hypervisors a bit harder, but would be much better on the longer run.
2012-08-16 17:27:54 +02:00

69 lines
3.6 KiB
XML

<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="hypervisor-host-install-security-policies">
<title>Configure the Security Policies</title>
<orderedlist>
<listitem>
<para>Configure SELinux (RHEL and CentOS)</para>
<orderedlist numeration="loweralpha">
<listitem>
<para>Check to see whether SELinux is installed on your machine. If not, you can skip this section.</para>
<para>In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:</para>
<programlisting># rpm -qa | grep selinux</programlisting>
</listitem>
<listitem>
<para>Set the SELINUX variable in /etc/selinux/config to "permissive". This ensures that the permissive setting will be maintained after a system reboot.</para>
<para>In RHEL or CentOS:</para>
<programlisting># vi /etc/selinux/config</programlisting>
<para>Change the following line</para>
<programlisting>SELINUX=enforcing</programlisting>
<para>to this</para>
<programlisting>SELINUX=permissive</programlisting>
</listitem>
<listitem>
<para>Then set SELinux to permissive starting immediately, without requiring a system reboot.</para>
<programlisting># setenforce permissive</programlisting>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Configure Apparmor (Ubuntu)</para>
<orderedlist numeration="loweralpha">
<listitem>
<para>Check to see whether AppArmor is installed on your machine. If not, you can skip this section.</para>
<para>In Ubuntu AppArmor is installed and enabled by default. You can verify this with:</para>
<programlisting># dpkg --list 'apparmor'</programlisting>
</listitem>
<listitem>
<para>Disable the AppArmor profiles for libvirt</para>
<programlisting>ln -s /etc/apparmor.d/usr.sbin.libvirtd /etc/apparmor.d/disable/</programlisting>
<programlisting>ln -s /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper /etc/apparmor.d/disable/</programlisting>
<programlisting>apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd</programlisting>
<programlisting>apparmor_parser -R /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper</programlisting>
</listitem>
</orderedlist>
</listitem>
</orderedlist>
</section>