Mike, Root pwd worked. Ssh is still broken. su - admin produced an error message - too fast to be caputured with my eyes. It seemed simiar to the one before. ssh admin@ip also failed: ssh admin@192.168.36.114 The authenticity of host '192.168.36.114 (192.168.36.114)' can't be established. RSA key fingerprint is 0b:e5:90:dd:68:15:e5:f4:d5:3c:34:83:b8:77:f4:a3. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.36.114' (RSA) to the list of known hosts. Permission denied (publickey,gssapi-keyex,gssapi-with-mic). - David ________________________________________ From: Mike Burns [mburns@redhat.com] Sent: Monday, February 13, 2012 5:55 AM To: Li, David Cc: users@ovirt.org Subject: RE: [Users] Pxeboot - pwd/login issue On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote:
Mike,
Tried the new ssh patch and the problem still there. Both options were used BOOTIF and ssh_pwauth
When I logged in first time and changed pwd, any subsequent logins were rejected. Again I couldn't capture the error message.
Tried to ssh into the node, but was rejected too:
[xxx oVirtNode]# ssh admin@192.168.36.114 The authenticity of host '192.168.36.114 (192.168.36.114)' can't be established. RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.36.114' (RSA) to the list of known hosts. Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Hmm, looks like something isn't right with ssh_pwauth then. I'll look into that, but for now, try using rootpw instead of adminpw. Then login as root. Once you're in as root, you can su - admin to go the the TUI (or in this case, get the stack trace for why the TUI is failing). Mike
- David ________________________________________ From: Mike Burns [mburns@redhat.com] Sent: Friday, February 10, 2012 11:34 AM To: Li, David Cc: users@ovirt.org Subject: RE: [Users] Pxeboot - pwd/login issue
On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote:
ok, I have already patched like this. Hope this is ok:
[lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git checkout FETCH_HEAD remote: Counting objects: 57, done remote: Finding sources: 100% (39/39) remote: Total 39 (delta 28), reused 39 (delta 28) Unpacking objects: 100% (39/39), done. From http://gerrit.ovirt.org/p/ovirt-node * branch refs/changes/07/1807/1 -> FETCH_HEAD Warning: you are leaving 1 commit behind, not connected to any of your branches:
07d8a0f Add archipel option with stateless boot
If you want to keep them by creating a new branch, this may be a good time to do so with:
git branch new_branch_name 07d8a0fc5007c5f74f9421b7a565cd2db2d9e772
HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git checkout FETCH_HEAD remote: Counting objects: 62, done remote: Finding sources: 100% (44/44) remote: Total 44 (delta 32), reused 44 (delta 32) Unpacking objects: 100% (44/44), done. From http://gerrit.ovirt.org/p/ovirt-node * branch refs/changes/08/1808/1 -> FETCH_HEAD Warning: you are leaving 5 commits behind, not connected to any of your branches:
a94c33c fix ssh_pwauth handling in autoinstall 893a095 Add archipel option with stateless boot a1053cb regenerate repos.ks when building iso 237870c Add network configure before dropping into emergency shell 5bb3613 add error handling to recent rhn.py commit
If you want to keep them by creating a new branch, this may be a good time to do so with:
git branch new_branch_name a94c33c6d0957391a48ab0cd2e78e4a15e5ad80e
HEAD is now at 3daa6d3... when stateless, don't execute store_config and remove_config [lid@FC16-1 ovirt-node]$
I *think* you're ok, because I pushed the commits such that this last command should get both. The way to check is to run
$ git log
and look at the commits in the log. You should see both the commits "fix ssh_pwauth handling..." and "when stateless..." commits at the top of the log.
ONE MORE QUESTION: do I need to run 'make publish' before make iso?
Yes, always rerun make publish. In general, I'd say rerun the autogen.sh too, but in this case you're fine.
Mike
- David ________________________________________ From: Mike Burns [mburns@redhat.com] Sent: Friday, February 10, 2012 11:19 AM To: Li, David Cc: users@ovirt.org Subject: Re: [Users] Pxeboot - pwd/login issue
On Fri, 2012-02-10 at 11:09 -0800, Li, David wrote:
Ok, what's the right cmd to get both? Do I have to start from scratch?
No need to start from scratch.
First, figure out the name of the remote. $ git remote show It will most likely return just one entry, and it's probably named origin. If it's something other than origin, then just substitute in the following commands:
$ git fetch origin $ git reset --hard origin/master $ git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git cherry-pick FETCH_HEAD $ git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git cherry-pick FETCH_HEAD
$ git status # should show something like: # On branch master # Your branch is ahead of 'origin/master' by 2 commits.
Now you should be good to build.
Mike
-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Friday, February 10, 2012 11:01 AM To: Li, David Cc: users@ovirt.org Subject: Re: [Users] Pxeboot - pwd/login issue
On Fri, 2012-02-10 at 10:49 -0800, Li, David wrote:
Mike, I think I got a glimpse of the error message - something like "persistent storage not available" after I tried to login with the new passwd. Does this make sense?
Try this patch with the other one I just sent:
Mike
David
-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Friday, February 10, 2012 7:37 AM To: Li, David Cc: users@ovirt.org Subject: RE: [Users] Pxeboot - pwd/login issue
On Fri, 2012-02-10 at 07:17 -0800, Li, David wrote: > Hi Mike, > > I ran into the login/pwd problem again with this new build. Kernel > option adminpw worked but only for a short time. I was asked to > change pwd immediately after login but then rejected again after I did
> There was an short-lived error message on the screen but I wasn't > able to capture it.
You can try booting with "BOOTIF=eth0 ssh_pwauth=1" in the command
This will configure networking and enable SSH password authentication. Then you can ssh admin@<your host> and it will show you the error.
> > I tried the latest from archipel source and it worked without > password issue. I pulled it from: > > git clone https://github.com/primalmotion/Archipel.git
I'm using git://github.com/primalmotion/Node.git
The only differences I see between the 2 are some minor formatting and conditional changes in recipe/Makefile.am and a couple patches that were pushed since the github repo was updated. These patches are all on the gerrit.ovirt.org side.
Note: there is an incompatible change that was merged into master this morning. I'm working on a rebase of the archipel stuff now to include it.
Mike
> > There might be a few updates right after you pulled it last time. > > Would you mind merge the new updates into ovirt node again? > > Thanks. > > David > > > >-----Original Message----- > >From: Mike Burns [mailto:mburns@redhat.com] > >Sent: Thursday, February 09, 2012 5:10 PM > >To: Li, David > >Cc: Perry Myers; users@ovirt.org > >Subject: Re: [Users] Pxeboot > > > >On Thu, 2012-02-09 at 17:05 -0800, Li, David wrote: > >> Mike, > >> Built it finally! > >> Thanks a lot! > > > >Woot! > > > >> > >> >-----Original Message----- > >> >From: Mike Burns [mailto:mburns@redhat.com] > >> >Sent: Thursday, February 09, 2012 4:18 PM > >> >To: Li, David > >> >Cc: Perry Myers; users@ovirt.org > >> >Subject: Re: [Users] Pxeboot > >> > > >> >On Thu, 2012-02-09 at 15:50 -0800, Li, David wrote: > >> >> MIke, > >> >> > >> >> Got something new this time in make publish: > >> >> > >> >> /bin/sh: -c: line 36: syntax error near unexpected token `)' > >> >> /bin/sh: -c: line 36: `)' > >> >> make[1]: *** [repos.ks] Error 1 > >> >> make[1]: Leaving directory > >> >> `/home/lid/workspace/ovirt/node-archipel- > >> >2.2.2/ovirt-node/recipe' > >> >> make: *** [distdir] Error 1 > >> >> > >> >> [lid@FC16-1 ovirt-node]$ echo $OVIRT_CACHE_DIR > >$OVIRT_LOCAL_REPO > >> >> /home/lid/ovirt-cache file:///home/lid/ovirt-cache/ovirt > >> >> [lid@FC16-1 ovirt-node]$ > >> > > >> >Oops, bad merge on my part. > >> > > >> >$ git reset --hard origin/master #sets you back to head of the > >> >master branch $ git fetch http://gerrit.ovirt.org/p/ovirt-node > >> >refs/changes/38/1738/3 && git cherry-pick FETCH_HEAD # checks > >> >out the > >new version of the patch set. > >> > > >> >Mike > >> > > >> >> > >> >> > >> >> - David > >> >> ________________________________________ > >> >> From: Mike Burns [mburns@redhat.com] > >> >> Sent: Thursday, February 09, 2012 2:12 PM > >> >> To: Li, David > >> >> Cc: Perry Myers; users@ovirt.org > >> >> Subject: Re: [Users] Pxeboot > >> >> > >> >> On Thu, 2012-02-09 at 13:34 -0800, Li, David wrote: > >> >> > Mike, > >> >> > > >> >> > It seems it needs couple vdsm pkgs: > >> >> > > >> >> > ./node-creator ovirt-node-image.ks Error creating Live CD : > >> >> > Failed to find package 'vdsm-cli' : No > >> >> > package(s) available to install mv ovirt-node-image.iso > >> >> > ovirt-node-image-2.2.3-0.1fc16.git16688ea.iso > >> >> > mv: cannot stat `ovirt-node-image.iso': No such file or > >> >> > directory > >> >> > make: *** [ovirt-node-image.iso] Error 1 > >> >> > > >> >> > > >> >> > can I remove them from ks files? > >> >> > >> >> Not if you want to use ovirt-node with ovirt-engine. There > >> >> was a bug in that patch set that is fixed in patch set 2 > >> >> (along with the bad ===== package). I hadn't pulled the > >> >> patch set together and uploaded to gerrit yet, but it's there now. > >> >> > >> >> git fetch http://gerrit.ovirt.org/p/ovirt-node > >> >> refs/changes/38/1738/2 && git checkout FETCH_HEAD > >> >> > >> >> This should fix the problem. > >> >> > >> >> Mike > >> >> > >> >> > > >> >> > - David > >> >> > ________________________________________ > >> >> > From: Mike Burns [mburns@redhat.com] > >> >> > Sent: Thursday, February 09, 2012 12:07 PM > >> >> > To: Li, David > >> >> > Cc: Perry Myers; users@ovirt.org > >> >> > Subject: Re: [Users] Pxeboot > >> >> > > >> >> > On Thu, 2012-02-09 at 11:52 -0800, Li, David wrote: > >> >> > > It's still the same error: > >> >> > > > >> >> > > [lid@FC16-1 ovirt-node]$ cd recipe/ > >> >> > > [lid@FC16-1 recipe]$ make ovirt-node-image.iso ( \ > >> >> > > echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ > >> >> > > echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ > >> >> > > echo "PACKAGE=ovirt-node-image" ;\ > >> >> > > echo "VERSION=2.2.3" ;\ > >> >> > > echo "RELEASE=0.1fc16.git16688ea" ;\ > >> >> > > ) > version.ks > >> >> > > ./node-creator ovirt-node-image.ks Error creating Live CD : > >> >> > > Failed to find package '=======' : No package(s) > >> >> > > available to install mv ovirt-node-image.iso > >> >> > > ovirt-node-image-2.2.3-0.1fc16.git16688ea.iso > >> >> > > mv: cannot stat `ovirt-node-image.iso': No such file or > >> >> > > directory > >> >> > > make: *** [ovirt-node-image.iso] Error 1 > >> >> > > [lid@FC16-1 recipe]$ echo $OVIRT_LOCAL_REPO > >> >> > > file:///home/lid/ovirt-cache/ovirt > >> >> > > [lid@FC16-1 recipe]$ ll /home/lid/ovirt-cache/ovirt/ > >> >> > > total > >> >> > > 12 drwxr-xr-x. 2 lid lid 4096 Feb 9 11:10 noarch > >> >> > > drwxrwxr-x. 2 lid lid 4096 Feb 9 11:10 repodata drwxrwxr-x. > >> >> > > 2 lid lid 4096 Feb 9 > >> >> > > 11:10 src > >> >> > > >> >> > That's a bug in the patch. edit recipe/common-pkgs.ks and > >> >> > remove the last line which is "=======" > >> >> > > >> >> > Mike > >> >> > > > >> >> > > > >> >> > > Did make publish store the rpms in $OVIRT_LOCAL_REPO? > >> >> > > > >> >> > > - David > >> >> > > ________________________________________ > >> >> > > From: Mike Burns [mburns@redhat.com] > >> >> > > Sent: Thursday, February 09, 2012 11:44 AM > >> >> > > To: Li, David > >> >> > > Cc: Perry Myers; users@ovirt.org > >> >> > > Subject: RE: [Users] Pxeboot > >> >> > > > >> >> > > On Thu, 2012-02-09 at 11:40 -0800, Li, David wrote: > >> >> > > > The error seems a little stubborn. > >> >> > > > > >> >> > > > [lid@FC16-1 recipe]$ echo $OVIRT_LOCAL_REPO > >> >> > > > file://home/lid/ovirt-cache/ovirt > >> >> > > > >> >> > > You need 3 slashes. file:///home/lid/ovirt-cache/ovirt > >> >> > > > >> >> > > > [lid@FC16-1 recipe]$ make ovirt-node-image.iso ( \ > >> >> > > > echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ > >> >> > > > echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ > >> >> > > > echo "PACKAGE=ovirt-node-image" ;\ > >> >> > > > echo "VERSION=2.2.3" ;\ > >> >> > > > echo "RELEASE=0.1fc16.git16688ea" ;\ > >> >> > > > ) > version.ks > >> >> > > > ./node-creator ovirt-node-image.ks Error creating Live CD : > >> >> > > > Unable to download from repo : Cannot retrieve > >> >> > > > repository metadata (repomd.xml) for repository: local. > >> >> > > > Please verify its path and try again mv > >> >> > > > ovirt-node-image.iso > >> >> > > > ovirt-node-image-2.2.3-0.1fc16.git16688ea.iso > >> >> > > > mv: cannot stat `ovirt-node-image.iso': No such file or > >> >> > > > directory > >> >> > > > make: *** [ovirt-node-image.iso] Error 1 > >> >> > > > > >> >> > > > There is also a pop-up window: Unable to open a folder > >> >> > > > for _ovirt-node-imag > >> >> > > > > >> >> > > > maybe it's looking at the wrong place? > >> >> > > > > >> >> > > > > >> >> > > > - David > >> >> > > > ________________________________________ > >> >> > > > From: Mike Burns [mburns@redhat.com] > >> >> > > > Sent: Thursday, February 09, 2012 11:15 AM > >> >> > > > To: Li, David > >> >> > > > Cc: Perry Myers; users@ovirt.org > >> >> > > > Subject: RE: [Users] Pxeboot > >> >> > > > > >> >> > > > On Thu, 2012-02-09 at 10:57 -0800, Li, David wrote: > >> >> > > > > ok, that's my bad:) > >> >> > > > > > >> >> > > > > Ran into error at the last iso build step: > >> >> > > > > > >> >> > > > > Start building ISO image.... > >> >> > > > > ( \ > >> >> > > > > echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ > >> >> > > > > echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ > >> >> > > > > echo "PACKAGE=ovirt-node-image" ;\ > >> >> > > > > echo "VERSION=2.2.3" ;\ > >> >> > > > > echo "RELEASE=0.1.fc16.git16688ea" ;\ > >> >> > > > > ) > version.ks > >> >> > > > > ./node-creator ovirt-node-image.ks Error creating Live CD : > >> >> > > > > Unable to download from repo : Cannot retrieve > >> >> > > > > repository metadata (repomd.xml) for repository: local. > >> >> > > > > Please verify its path and try again mv > >> >> > > > > ovirt-node-image.iso > >> >> > > > > ovirt-node-image-2.2.3-0.1.fc16.git16688ea.iso > >> >> > > > > mv: cannot stat `ovirt-node-image.iso': No such file > >> >> > > > > or directory > >> >> > > > > make: *** [ovirt-node-image.iso] Error 1 > >> >> > > > > >> >> > > > IIRC, this is usually because you have OVIRT_LOCAL_REPO > >> >> > > > defined, but not correctly. It needs to be like this: > >> >> > > > file:///home/mburns/rpmbuild/RPMS > >> >> > > > > >> >> > > > Ok, I just looked at the Node Building page, and it > >> >> > > > needs some > >updates. > >> >> > > > Try this from the base directory of the git repo > >> >> > > > > >> >> > > > $ export OVIRT_CACHE_DIR=${HOME}/ovirt-cache > >> >> > > > $ export > >> >> > > > OVIRT_LOCAL_REPO=file://${OVIRT_CACHE_DIR}/ovirt > >> >> > > > $ ./autogen.sh --with-image-minimizer $ make publish > >> >> > > > #this builds the rpms and puts them in > >> >> > > > ${OVIRT_CACHE_DIR} $ cd recipe $ make > >> >> > > > ovirt-node-image.iso > >> >> > > > > >> >> > > > Mike > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > I wonder which repo my machine is lacking? > >> >> > > > > > >> >> > > > > - David > >> >> > > > > ________________________________________ > >> >> > > > > From: Mike Burns [mburns@redhat.com] > >> >> > > > > Sent: Thursday, February 09, 2012 10:02 AM > >> >> > > > > To: Li, David > >> >> > > > > Cc: Perry Myers; users@ovirt.org > >> >> > > > > Subject: Re: [Users] Pxeboot > >> >> > > > > > >> >> > > > > On Thu, 2012-02-09 at 09:47 -0800, Li, David wrote: > >> >> > > > > > Got an error: > >> >> > > > > > [lid@FC16-1 ovirt-node]$ git fetch > >> >> > > > > > http://gerrit.ovirt.org/ > >> >> > > > > > refs/changes/38/1738/1&&git cherry-pick FETCH_HEAD > >> >> > > > > > fatal: http://gerrit.ovirt.org/info/refs not found: > >> >> > > > > > did you run git > >> >update-server-info on the server? > >> >> > > > > > >> >> > > > > Bad copy/paste: > >> >> > > > > > >> >> > > > > git fetch http://gerrit.ovirt.org/p/ovirt-node > >> >> > > > > refs/changes/38/1738/1 && git cherry-pick FETCH_HEAD > >> >> > > > > > > >> >> > > > > > any ideas? > >> >> > > > > > > >> >> > > > > > - David > >> >> > > > > > ________________________________________ > >> >> > > > > > From: Mike Burns [mburns@redhat.com] > >> >> > > > > > Sent: Thursday, February 09, 2012 8:37 AM > >> >> > > > > > To: Li, David > >> >> > > > > > Cc: Perry Myers; users@ovirt.org > >> >> > > > > > Subject: Re: [Users] Pxeboot > >> >> > > > > > > >> >> > > > > > On Thu, 2012-02-09 at 08:30 -0800, Li, David wrote: > >> >> > > > > > > Mike, > >> >> > > > > > > > >> >> > > > > > > Two quick questions before I kick off a build: > >> >> > > > > > > > >> >> > > > > > > 1. Git errors. Do they matter? > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > [lid@FC16-1 node-archipel-2.2.2]$ git clone > >> >> > > > > > > http://gerrit.ovirt.org/p/ovirt-node.git > >> >refs/changes/38/1738/1&&git checkout FETCH_HEAD Cloning into > >> >refs/changes/38/1738/1... > >> >> > > > > > > remote: Counting objects: 14791, done > >> >> > > > > > > remote: Finding sources: 100% (14791/14791) > >> >> > > > > > > remote: Total 14791 (delta 10855), reused 14778 > >> >> > > > > > > (delta > >> >> > > > > > > 10855) Receiving objects: 100% (14791/14791), > >> >> > > > > > > 16.92 MiB > >> >> > > > > > > | 154 > >> >KiB/s, done. > >> >> > > > > > > Resolving deltas: 100% (10855/10855), done. > >> >> > > > > > > fatal: Not a git repository (or any of the parent > >> >> > > > > > > directories): .git > >> >> > > > > > > >> >> > > > > > try this instead: > >> >> > > > > > > >> >> > > > > > git clone http://gerrit.ovirt.org/p/ovirt-node.git > >> >> > > > > > cd ovirt-node > >> >> > > > > > git fetch http://gerrit.ovirt.org/p/ovirt-node > >> >> > > > > > refs/changes/38/1738/1 && git cherry-pick > >> >> > > > > > FETCH_HEAD > >> >> > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > 2. Build machine. > >> >> > > > > > > > >> >> > > > > > > I am using a x86_64 FC16 VM as the build machine. > >> >> > > > > > > My target is > >> >x86_64 Intel board. Is this ok? > >> >> > > > > > > >> >> > > > > > Should be fine. > >> >> > > > > > > >> >> > > > > > Mike > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > - David > >> >> > > > > > > ________________________________________ > >> >> > > > > > > From: Mike Burns [mburns@redhat.com] > >> >> > > > > > > Sent: Thursday, February 09, 2012 8:16 AM > >> >> > > > > > > To: Li, David > >> >> > > > > > > Cc: Perry Myers; users@ovirt.org > >> >> > > > > > > Subject: RE: [Users] Pxeboot > >> >> > > > > > > > >> >> > > > > > > On Thu, 2012-02-09 at 08:10 -0800, Li, David wrote: > >> >> > > > > > > > Not sure where the boot log is since I can't login. > >> >> > > > > > > > > >> >> > > > > > > > I got the source from > >> >> > > > > > > > https://github.com/primalmotion/archipel-node > >> >> > > > > > > > and followed the build instructions in > >> >> > > > > > > > http://ovirt.org/wiki/Node_Building > >> >> > > > > > > > > >> >> > > > > > > > maybe I should rebuild the iso from the ovirt > >> >> > > > > > > > node source tree > >> >as you have pulled in archipel changes yesterday. How do I do that? > >> >> > > > > > > > >> >> > > > > > > git fetch http://gerrit.ovirt.org/p/ovirt-node > >> >> > > > > > > refs/changes/38/1738/1 && git checkout FETCH_HEAD > >> >> > > > > > > > >> >> > > > > > > That command will checkout the current version of > >> >> > > > > > > the archipel-node changes. Then you can just > >> >> > > > > > > follow the Node_Building process. Note that the > >> >> > > > > > > changes aren't merged into master yet. I'm still > >> >> > > > > > > in the process of reviewing > >them. > >> >> > > > > > > > >> >> > > > > > > Mike > >> >> > > > > > > > > >> >> > > > > > > > - David > >> >> > > > > > > > > >> >> > > > > > > > > >> >> > > > > > > > >-----Original Message----- > >> >> > > > > > > > >From: Mike Burns [mailto:mburns@redhat.com] > >> >> > > > > > > > >Sent: Thursday, February 09, 2012 7:22 AM > >> >> > > > > > > > >To: Li, David > >> >> > > > > > > > >Cc: Perry Myers; users@ovirt.org > >> >> > > > > > > > >Subject: Re: [Users] Pxeboot > >> >> > > > > > > > > > >> >> > > > > > > > >On Thu, 2012-02-09 at 07:06 -0800, Li, David wrote: > >> >> > > > > > > > >> Mike, > >> >> > > > > > > > >> > >> >> > > > > > > > >> I added adminpw as a kernel option. After > >> >> > > > > > > > >> boot, I tried > >> >"admin/abc123" > >> >> > > > > > > > >> and "root/abc123" but not able to login. > >> >> > > > > > > > >> Any idea? > >> >> > > > > > > > >> > >> >> > > > > > > > > > >> >> > > > > > > > >Are there any errors in your build or boot logs? > >> >> > > > > > > > > > >> >> > > > > > > > >Mike > >> >> > > > > > > > > > >> >> > > > > > > > >> David > >> >> > > > > > > > >> > >> >> > > > > > > > >> > >> >> > > > > > > > >> >-----Original Message----- > >> >> > > > > > > > >> >From: Mike Burns [mailto:mburns@redhat.com] > >> >> > > > > > > > >> >Sent: Wednesday, February 08, 2012 6:53 PM > >> >> > > > > > > > >> >To: Li, David > >> >> > > > > > > > >> >Cc: Perry Myers; users@ovirt.org > >> >> > > > > > > > >> >Subject: Re: [Users] Pxeboot > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >On Wed, 2012-02-08 at 17:11 -0800, Li, David wrote: > >> >> > > > > > > > >> >> Ok, I built an iso out of archipel and > >> >> > > > > > > > >> >> pxebooted it with stateless option. Now > >> >> > > > > > > > >> >I got a "localhost" login prompt. Any idea > >> >> > > > > > > > >> >what should I put > >> >in as user/pwd? > >> >> > > > > > > > >> >> David > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >You will need to pass a password in on the > >> >> > > > > > > > >> >command line as well > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >adminpw=<hashed_password> > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >You can generate the hashed password using: > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >$ openssl passwd > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >Assuming the password was abc123 > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >$ openssl passwd abc123 > >> >> > > > > > > > >> >tKrQfufCbosr6 > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >adminpw=tKrQfufCbosr6 > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >Mike > >> >> > > > > > > > >> > > >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> >-----Original Message----- > >> >> > > > > > > > >> >> >From: Mike Burns > >> >> > > > > > > > >> >> >[mailto:mburns@redhat.com] > >> >> > > > > > > > >> >> >Sent: Wednesday, February 08, 2012 4:31 > >> >> > > > > > > > >> >> >PM > >> >> > > > > > > > >> >> >To: Li, David > >> >> > > > > > > > >> >> >Cc: Perry Myers; users@ovirt.org > >> >> > > > > > > > >> >> >Subject: RE: [Users] Pxeboot > >> >> > > > > > > > >> >> > > >> >> > > > > > > > >> >> >On Wed, 2012-02-08 at 15:43 -0800, Li, > >> >> > > > > > > > >> >> >David wrote: > >> >> > > > > > > > >> >> >> Ok, I think we are on the same page > >> >> > > > > > > > >> >> >> now regarding > >> >stateless node. > >> >> > > > > > > > >> >> >> It looks like the achipel diff you > >> >> > > > > > > > >> >> >> just pulled in might be able to do > >> >> > > > > > > > >> >> >> this. But I can't quite make it out > >> >> > > > > > > > >> >> >> what the kernel option should > >> >> > > > > > > > >be. > >> >> > > > > > > > >> >> >> Is it "stateless=1"? > >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> > > >> >> > > > > > > > >> >> >stateless=1 or just stateless, both will work. > >> >> > > > > > > > >> >> > > >> >> > > > > > > > >> >> > > >> >> > > > > > > > >> >> >> David > >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> >> >-----Original Message----- > >> >> > > > > > > > >> >> >> >From: Mike Burns > >> >> > > > > > > > >> >> >> >[mailto:mburns@redhat.com] > >> >> > > > > > > > >> >> >> >Sent: Wednesday, February 08, 2012 > >> >> > > > > > > > >> >> >> >3:27 PM > >> >> > > > > > > > >> >> >> >To: Li, David > >> >> > > > > > > > >> >> >> >Cc: Perry Myers; users@ovirt.org > >> >> > > > > > > > >> >> >> >Subject: Re: [Users] Pxeboot > >> >> > > > > > > > >> >> >> > > >> >> > > > > > > > >> >> >> >On Wed, 2012-02-08 at 15:19 -0800, > >> >> > > > > > > > >> >> >> >Li, David > >wrote: > >> >> > > > > > > > >> >> >> >> Perry, > >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> I am glad you brought this up. > >> >> > > > > > > > >> >> >> >> I 'd be perfectly happy to run the > >> >> > > > > > > > >> >> >> >> root fs entirely in > >> >RAM. > >> >> > > > > > > > >> >> >> >> In fact that would > >> >> > > > > > > > >> >> >> >be ideal for me. It's just I am not > >> >> > > > > > > > >> >> >> >quite sure how to use pxeboot to achieve
that. line. this.
> >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> I am doing a test now using the > >> >> > > > > > > > >> >> >> >> tftpboot files > >> >created from the iso. > >> >> > > > > > > > >> >> >> >> As far as I see, the kernel boot > >> >> > > > > > > > >> >> >> >> options > >> >(pxelinux.cfg/default) has: > >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> root=live:/ovirt-node-image-2.2.2-1.1. > >> >> > > > > > > > >> >> >> >> fc1 6.i so > >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> With this I can only pxeboot to the > >> >> > > > > > > > >> >> >> >> intall screen. What should I use > >> >> > > > > > > > >> >> >> >> to let the > >> >> > > > > > > > >> >> >> >kernel mount the root fs in memory? > >> >> > > > > > > > >> >> >> >Something like > >> >> > > > > > > > >root=/dev/ram0? > >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> David > >> >> > > > > > > > >> >> >> > > >> >> > > > > > > > >> >> >> >It's not currently possible with ovirt-node. > >> >> > > > > > > > >> >> >> >That's the whole stateless feature > >> >> > > > > > > > >> >> >> >that we outlined. Once we actually > >> >> > > > > > > > >> >> >> >have it implemented, it will be > >> >> > > > > > > > >> >> >> >something along the lines of adding > >> >> > > > > > > > >> >> >> >"stateless" to > >> >> > > > > > > > >> >> >the kernel commandline. > >> >> > > > > > > > >> >> >> > > >> >> > > > > > > > >> >> >> >Mike > >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> >-----Original Message----- > >> >> > > > > > > > >> >> >> >> >From: Perry Myers > >> >> > > > > > > > >> >> >> >> >[mailto:pmyers@redhat.com] > >> >> > > > > > > > >> >> >> >> >Sent: Wednesday, February 08, 2012 > >> >> > > > > > > > >> >> >> >> >2:54 PM > >> >> > > > > > > > >> >> >> >> >To: Mike Burns > >> >> > > > > > > > >> >> >> >> >Cc: Li, David; users@ovirt.org > >> >> > > > > > > > >> >> >> >> >Subject: Re: [Users] Pxeboot > >> >> > > > > > > > >> >> >> >> > > >> >> > > > > > > > >> >> >> >> >On 02/08/2012 05:03 PM, Mike Burns wrote: > >> >> > > > > > > > >> >> >> >> >> On Wed, 2012-02-08 at 13:46 > >> >> > > > > > > > >> >> >> >> >> -0800, Li, David > >> >wrote: > >> >> > > > > > > > >> >> >> >> >>> Mike, > >> >> > > > > > > > >> >> >> >> >>> > >> >> > > > > > > > >> >> >> >> >>> If I understand this correctly, > >> >> > > > > > > > >> >> >> >> >>> today I should be able to > >> >> > > > > > > > >> >> >> >> >>> pxeboot and nfs mount the > >> >root fs from a remote server. > >> >> > > > > > > > >> >> >> >> >>> Apart from setting up the pxe > >> >> > > > > > > > >> >> >> >> >>> stuff, I 'd have to populate > >> >> > > > > > > > >> >> >> >> >>> the ovirt node root fs on the > >> >> > > > > > > > >> >> >> >> >>> server > >> >> > > > > > > > >> >> >> >> >>> - perhaps steal it from a disk install. > >> >> > > > > > > > >> >> >> >> >>> In other words I am concerned > >> >> > > > > > > > >> >> >> >> >>> about the point from which the > >> >> > > > > > > > >> >> >> >> >>> kernel starts to execute /init > >> >> > > > > > > > >> >> >> >> >>> script (in the initramfs) to > >> >> > > > > > > > >> >> >> >> >>> the > >> >point /init is able to mount the final root fs from a remote server. > >> >> > > > > > > > >> >> >> >> >> > >> >> > > > > > > > >> >> >> >> >> No, there is no way to set this > >> >> > > > > > > > >> >> >> >> >> up currently in > >> >ovirt-node. > >> >> > > > > > > > >> >> >> >> >> You could install using a remote > >> >> > > > > > > > >> >> >> >> >> iscsi lun if you have a hardware > >> >> > > > > > > > >> >> >> >> >> iscsi HBA, but there isn't a way > >> >> > > > > > > > >> >> >> >> >> to mount a remote nfs share as > >> >> > > > > > > > >> >> >> >> >> the > >> >> > > > > > > > >> >> >root fs. > >> >> > > > > > > > >> >> >> >> >> > >> >> > > > > > > > >> >> >> >> >> Supporting a remote NFS share as > >> >> > > > > > > > >> >> >> >> >> the root fs isn't even something > >> >> > > > > > > > >> >> >> >> >> that requested as an RFE at this > >> >> > > > > > > > >> >> >> >> >> point or on the roadmap as far > >> >> > > > > > > > >> >> >> >> >> as > >> >I'm aware. > >> >> > > > > > > > >> >> >> >> >> > >> >> > > > > > > > >> >> >> >> >> It sounds like what you're > >> >> > > > > > > > >> >> >> >> >> really looking for is a shared > >> >> > > > > > > > >> >> >> >> >> root fs that multiple hosts could use. > >> >> > > > > > > > >> >> >> >> >> This is something that we will > >> >> > > > > > > > >> >> >> >> >> probably look into eventually, > >> >> > > > > > > > >> >> >> >> >> but it's not on the immediate > >> >> > > > > > > > >> >> >roadmap. > >> >> > > > > > > > >> >> >> >> > > >> >> > > > > > > > >> >> >> >> >Given that the rootfs of oVirt > >> >> > > > > > > > >> >> >> >> >Node is fairly small and in a > >> >> > > > > > > > >> >> >> >> >truly stateless environment would > >> >> > > > > > > > >> >> >> >> >just run out of system RAM, > >> >> > > > > > > > >> >> >> >> >there's no real reason to try to > >> >> > > > > > > > >> >> >> >> >do a shared NFS based > >> >> > > > > > > > >rootfs. > >> >> > > > > > > > >> >> >> >> >It's an unnecessary complication I > >> >> > > > > > > > >> >> >> >> >think, if the end goal is to move > >> >> > > > > > > > >> >> >> >> >to truly > >> >> > > > > > > > >> >> >> >stateless. > >> >> > > > > > > > >> >> >> >> > > >> >> > > > > > > > >> >> >> >> >For larger systems where the > >> >> > > > > > > > >> >> >> >> >rootfs is on the order of GB's, > >> >> > > > > > > > >> >> >> >> >shared root may make more > >> >sense. > >> >> > > > > > > > >> >> >> >> > >> >____________________________________________ > >> >> > > > > > > > >> >> >> >> ___ Users mailing list > >> >> > > > > > > > >> >> >> >> Users@ovirt.org > >> >> > > > > > > > >> >> >> >> http://lists.ovirt.org/mailman/list > >> >> > > > > > > > >> >> >> >> inf o/u ser s > >> >> > > > > > > > >> >> >> > > >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> > > >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> > >> >_______________________________________________ > >> >> > > > > > > > >> >> Users mailing list Users@ovirt.org > >> >> > > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/user > >> >> > > > > > > > >> >> s > >> >> > > > > > > > >> > > >> >> > > > > > > > >> > >> >> > > > > > > > >> > >> >_______________________________________________ > >> >> > > > > > > > >> Users mailing list Users@ovirt.org > >> >> > > > > > > > >> http://lists.ovirt.org/mailman/listinfo/users > >> >> > > > > > > > > > >> >> > > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > _______________________________________________ > >> >> > > > > > > Users mailing list > >> >> > > > > > > Users@ovirt.org > >> >> > > > > > > http://lists.ovirt.org/mailman/listinfo/users > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > _______________________________________________ > >> >> > > > > > Users mailing list > >> >> > > > > > Users@ovirt.org > >> >> > > > > > http://lists.ovirt.org/mailman/listinfo/users > >> >> > > > > > >> >> > > > > > >> >> > > > > >> >> > > > > >> >> > > > >> >> > > > >> >> > > _______________________________________________ > >> >> > > Users mailing list > >> >> > > Users@ovirt.org > >> >> > > http://lists.ovirt.org/mailman/listinfo/users > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > Users mailing list > >> >> > Users@ovirt.org > >> >> > http://lists.ovirt.org/mailman/listinfo/users > >> >> > >> >> > >> >> _______________________________________________ > >> >> Users mailing list > >> >> Users@ovirt.org > >> >> http://lists.ovirt.org/mailman/listinfo/users > >> > > >> > >> _______________________________________________ > >> Users mailing list > >> Users@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > > >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users