[Users] How to pxeboot ovrit node into memory automatically?
Fabian Deutsch
fabiand at redhat.com
Wed Dec 4 14:17:30 EST 2013
Am Montag, den 02.12.2013, 13:53 -0800 schrieb David Li:
> Hi Fabian,
>
> Everytime the ovirt node boots up, it adds a route entry that I have to manually remove. Otherwise it messed up my routing.
> How do I modify the boot scripts to automatically remove it?
Hey David,
could you file a bug for that route problem?
You can try the following workaround:
# Create /etc/rc.d/rc.local with the commands to run
$ vi /etc/rc.d/rc.local
$ chmod a+x /etc/rc.d/rc.local
$ persist /etc/rc.d/rc.local
/etc/rc.d/rc.local should then be run on every boot.
- fabian
> ----- Original Message -----
> > From: Fabian Deutsch <fabiand at redhat.com>
> > To: David Li <david_li at sbcglobal.net>
> > Cc: "users at ovirt.org" <users at ovirt.org>
> > Sent: Monday, October 28, 2013 7:45 AM
> > Subject: Re: [Users] How to pxeboot ovrit node into memory automatically?
> >
> > Am Montag, den 28.10.2013, 07:42 -0700 schrieb David Li:
> >>
> >> Hi Fabian,
> >>
> >> Yes rootpwd worked too! Thanks.
> >>
> >> Two new problems:
> >>
> >> But I found there is no networking for the stateless node.
> >> What kernel boot options are used to either use DHCP or statically
> > configure the IP address for an interface on the node?
> >>
> >> I also need to have the sshd enabled. Is there a kernel option for that?
> >
> > Hey David,
> >
> > here you can find all the supported boot params in ovirt node:
> > http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=blob;f=scripts/ovirt-init-functions.sh.in;h=c4280caefb89c77afc1e8bec8c925aa7f3039733;hb=HEAD#l214
> >
> > Greetings
> > fabian
> >
> >> David
> >>
> >>
> >>
> >> ----- Original Message -----
> >> > From: Fabian Deutsch <fabiand at redhat.com>
> >> > To: David Li <david_li at sbcglobal.net>
> >> > Cc: "users at ovirt.org" <users at ovirt.org>
> >> > Sent: Friday, October 25, 2013 9:10 AM
> >> > Subject: Re: [Users] How to pxeboot ovrit node into memory
> > automatically?
> >> >
> >> > Am Freitag, den 25.10.2013, 08:57 -0700 schrieb David Li:
> >> >> Hi Fabian,
> >> >>
> >> >> That kernel option worked for me! The node is booted up in RAM.
> > Thanks!
> >> >>
> >> >> My next question is:
> >> >> How do I specify the root login and passwd as boot parameters?
> >> >
> >> > Hey David.
> >> >
> >> > Nice that it worked! Were you able to register to the Engine?
> >> >
> >> > You can use the adminpw= and rootpw= kernel arguments to set
> > passwords.
> >> > use
> >> > $ openssl passwd -salt 42
> >> > to create one or two passwords
> >> >
> >> > Greetings
> >> > fabian
> >> >
> >> >> David
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> > From: Fabian Deutsch <fabiand at redhat.com>
> >> >> > To: David Li <david_li at sbcglobal.net>
> >> >> > Cc: "users at ovirt.org" <users at ovirt.org>
> >> >> > Sent: Thursday, October 24, 2013 11:47 PM
> >> >> > Subject: Re: [Users] How to pxeboot ovrit node into memory
> >> > automatically?
> >> >> >
> >> >> > Am Donnerstag, den 24.10.2013, 16:26 -0700 schrieb David Li:
> >> >> >> Hi,
> >> >> >>
> >> >> >> I was following the instructions at
> >> > http://www.ovirt.org/Node_PXE. My goal
> >> >> > is to use pxeboot (iPXE) to boot the node entirely into RAM
> > with
> >> > rootfs. What I
> >> >> > got now is an installation screen which requires a local
> > storage. My
> >> > system has
> >> >> > no disk and this doesn't quite work for me.
> >> >> >>
> >> >> >> What's are the kernel parameters I need to use to
> > boot the
> >> > node into
> >> >> > RAM automatically? I am OK as the first step with a
> > stateless node.
> >> >> >
> >> >> > Hey David,
> >> >> >
> >> >> > the stateless mode is currently not completely working with
> > oVirt
> >> >> > Engine. That means a Node needs to be approved each time it
> > boots into
> >> >> > the stateless mode.
> >> >> > The stateless mode can be entered by appending stateless to
> > the
> >> > default
> >> >> > kernel arguments.
> >> >> >
> >> >> > Greetings
> >> >> > fabian
> >> >> >
> >> >
> >
More information about the Users
mailing list