Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 938809 Details for
Bug 1142709
Trying to deploy hosted-engine via iSCSI device fails due to selinux issue on EL7 and Fedora
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
English description of my steps until the failure happened
installation_hosted-engine-engl.md (text/plain), 6.46 KB, created by
Thomas Keppler
on 2014-09-18 08:55:34 UTC
(
hide
)
Description:
English description of my steps until the failure happened
Filename:
MIME Type:
Creator:
Thomas Keppler
Created:
2014-09-18 08:55:34 UTC
Size:
6.46 KB
patch
obsolete
>### <a name="sys"></a>1. System > >[scroll up](#top) > >a. Fresh CentOS7-Installation > > * Please use minimal install! > > * Best practice would be to configure the NICs from the installer > >b. Misc stuff after install: > > * Edit NICs in _/etc/sysconfig/network-scripts_ (-> Change ONBOOT and DEFROUTE accordingly) > * **ONBOOT** always to **yes** (activated the NIC at boot time) > * **DEFROUTE** on all NICs to **no**. Only at the NIC facing public side **yes** > >c. Edit the hosts file (see: _conf/hosts_) > > #Privates Netz - VM Nodes (enp5s0f1) > 192.168.1.1 xxx-mgmtgate xxx-mgmtgate.xxx.xxx.edu > 192.168.1.2 xxx-vmnode1 xxx-vmnode1.xxx.xxx.edu > 192.168.1.3 xxx-vmnode2 xxx-vmnode2.xxx.xxx.edu > 192.168.1.4 xxx-vmnode3 xxx-vmnode3.xxx.xxx.edu > 192.168.1.5 xxx-vmnode4 xxx-vmnode4.xxx.xxx.edu > 192.168.1.100 xxx-vmengine1 xxx-vmengine1.xxx.xxx.edu > > #Privates 10Gb/s Netz - enp130s0f0 > 10.0.0.1 gluster1 > 10.0.0.2 gluster2 > 10.0.0.3 gluster3 > 10.0.0.4 gluster4 > 10.0.0.100 iscsi1 > >d. Update the machine and install standard tools > > yum -y upgrade && yum -y install vim nano tmux net-tools traceroute wget tar > >e. enable sshd and start it up > > systemctl enable sshd && systemctl start sshd > >f. add epel-repos, install htop, then reboot > > wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-1.noarch.rpm && yum -y install epel-release-7-1.noarch.rpm && yum -y upgrade && yum -y install htop && rm epel-release-7-1.noarch.rpm --force && reboot > >### <a name="ovi"></a>3. oVirt > >[scroll up](#top) > >**NOTES**: > > * Before you deploy, make sure you have an ISO with Fedora 20 handy (make sure the permissions are set correctly, do this: chown vdsm:kvm && chmod 777, after the ovirt-hosted-engine-setup package has been installed) > * Always use the _private_ interface to bind to ovirtmgmt (normally enp5s0f1) > * VNC Server == Hostname of the node > >a. add ovirt 3.5 repos > > yum -y install http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm && yum -y install http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35-snapshot.rpm && yum -y upgrade > >i. install ovirt-hosted-engine-setup, correct file permissions and deploy > > yum -y install ovirt-hosted-engine-setup && chown vdsm:kvm **PATH_TO_ISO** && chmod 777 **PATH_TO_ISO** && hosted-engine --deploy > >### <a name="dep"></a>4. Deployment > >[nach oben](#top) > >* Preparing the Hosts for the Engine-VM > > a. "Do you want to continue?" => yes > > i. "Please specify the storage you would like to use" => iscsi > > i. "Please specify the iSCSI portal IP address:" => 10.0.0.100 > > i. "Please specify the iSCSI portal port [3260]" => **ENTER** > > i. "Please specify the iSCSI portal user" => **ENTER** > > i. "Please specify the target name" => 0 or **ENTER** > > i. "Please specify the lun id" => **ENTER** > > i. "Please provide storage domain name." => **ENTER** > > i. "Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]" => **ENTER** > > i. "Please indicate a nic to set ovirtmgmt bridge on:" => enp5s0f1 > > i. "iptables was detected on your computer, do you wish setup to configure it?" => yes > > i. "Please indicate a pingable gateway IP address" => 192.168.1.1 (priv. IP of the Gateway) > > i. "Please specify the device to boot the VM from" => cdrom > > i. "Please specify the CPU type to be used by the VM" => _use host's architecture => see /proc/cpuinfo_ > > i. "Please specify path to installation media you would like to use" => **PATH_TO_ISO** > > i. "Please specify the number of virtual CPUs for the VM" => according to the host, min. 2_ > > i. "Please specify the disk size of the VM in GB" => _min. 25GB_ > > i. "You may specify a unicast MAC address for the VM" => 22:33:aa:bb:33:22 > > i. "Please specify the memory size of the VM in MB" => _min. 4096MB (==4GB)_ > > i. "Please specify the console type you would like to use to connect to the VM" => vnc > > i. "Enter the name which will be used to identify this host inside the Administrator Portal" => xxx-vmnode1 > > i. "Enter 'admin@internal' user password that will be used for accessing the Administrator Portal" => *** > > i. "Please provide the FQDN[...]" => xxx-vmengine1.xxx.xxx.edu > > i. _Schritte bzgl. Mailserver_ => Standardwerte nutzen! > > i. "Please provide the email address from which notifications will be sent" => noreply@ovirt.xxx.xxx.edu > > i. "Please provide a comma-separated list of email addresses which will get notifications" => *** > > i. "Please confirm installation settings" => _If everything's alright, go for it!_ > > _If everything worked out you'll see: "You can now connect to the VM with the following command:"_ > >* Installation of the Engine-VM > > a. Connect to the VM via VNC, IP is that of the host, not that of the VM! > > i. Install the OS (Don't forget to conf the NIC!) > > a. Use minimal install > > i. Configure the NIC's settings: > > IP: 192.168.1.100 > Subnetz: 255.255.0.0 (/16) > Gateway: 192.168.1.1 > > **"Verbinden sobald verfügbar"** (first checkbox in the first tab) > > i. Automatic partitioning is OK > > i. Press "1" in the wizard, after the installation is complete, reconnect via VNC > > i. Now go ahead and install the engine onto the VM (see "Engine_Installation")... > >a. **Installation of the engine:** > > a. > > yum -y install ovirt-engine && yum -y upgrade && engine-setup > > i. "Configure engine on this host" => Yes > > i. "Configure WebSocket Proxy on this host" => Yes > > i. "Setup has found updates for some packages, do you wish to update them now?" => Yes > > i. "Do you want Setup to configure the firewall?" => Yes > > i. "Host fully qualified DNS name of this server" => **ENTER** > > i. "Where is the Engine database located?" => Local > > i. "[...]Would you like Setup to automatically configure postgresql[...]" => Automatic > > i. "Engine admin password" => *** > > i. "Application mode" => Both > > i. "Default storage type:" => Shared > > i. "Organization name for certificate" => xxx.xxx.edu > > i. "Setup can configure the default page of the web server to present the application home page.[...]" => Yes > > i. "Setup can configure apache to use SSL using a certificate issued from the internal CA.[...]" => Automatic > > i. "Configure an NFS share on this server to be used as an ISO Domain" => Yes > > ** Only change options in agreement with the ovirt-group ** > > i. "Configuration Preview" => OK (if it really **IS** OK ;)) > >b. Back in the --deploy process, hit 1 again and proceed as is stated on the screen
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1142709
:
938391
|
938756
|
938757
| 938809 |
941013
|
941018