Bug 1384296 - oVirt Node livecd unattended installation
Summary: oVirt Node livecd unattended installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-node
Classification: oVirt
Component: Installation & Update
Version: 4.0
Hardware: x86_64
OS: Unspecified
unspecified
low vote
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: Ying Cui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-13 03:23 UTC by vanlos wang
Modified: 2016-10-13 11:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-13 11:16:39 UTC
oVirt Team: Node
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description vanlos wang 2016-10-13 03:23:23 UTC 
Description of problem:
I am want to install ovirt node livecd by pxe, as I know there can be boot from pxe. But the installation proccess is handled by hand, Is it possible to do an unattended installation for oVirt Node LiveCD?

Version-Release number of selected component (if applicable):
3.6
4.0

How reproducible:
Just setup a pxe server and use pxe to install ovirt node

Steps to Reproduce:
1.setup a pxe server
2.generate ovirt node livecd tftpboot resources
3.use pxe to install ovirt node

Actual results:
can boot, can not install 

Expected results:
can boot, can do an unattended installation

Additional info:
Comment 1 Fabian Deutsch 2016-10-13 11:16:39 UTC 
Yes, oVirt Node 4 can be auto-installed using PXE.

To achieve this you can roughly follow the CentOS guidelines for setting up auto installation.

When it comes to the kickstart, you just need to ensure to include the following directives:

…
…
liveimg --url=http://url/to/squashfs
autopart --type=thinp
%post --erroronfail
imgbase layout --init
%end

I'd suggest to move the discussion to a mailinglist i.e. users.

This bug is covering the documentation side of this bug 1371299
Note You need to log in before you can comment on or make changes to this bug.