Since oVirt node doesn’t support pxeboot in the current release, does anyone know if I can use RHEV-H to pxeboot and nfs mout the rootfs?

David _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hi Mike, I read the oVirt node Wiki and had an impression it's not ready in 2.3 yet: http://ovirt.org/wiki/Node_Stateless . Ok, I saw that tool in the ISO. Let me dig in to how to use it. The real question now is if I can nfs mount the the real rootfs which would also be on the TFTP/DHCP server in the final pxe booting stage. Is that something you are doing too?

David >-----Original Message----- >From: Mike Burns [mailto:mburns@redhat.com] >Sent: Wednesday, February 08, 2012 10:11 AM >To: Li, David >Cc: users(a)ovirt.org >Subject: Re: [Users] Pxeboot > >On Wed, 2012-02-08 at 09:53 -0800, Li, David wrote: >> Since oVirt node doesn’t support pxeboot in the current release, does >> anyone know if I can use RHEV-H to pxeboot and nfs mout the rootfs? > >Where does it say that ovirt-node doesn't support pxe boot? I use PXE in my >testing. I haven't heard of any issues with PXE either. > >The livecd-iso-to-pxeboot script in livecd-tools will create the initrd and >vmlinuz files for you to import into your PXE server. > >Mike >> >> David >> >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Mike, I 'd like to understand what it takes to do this. Do we need a special initramfs for oVirt node to help with the stateless pxeboot? Some tools like Dracut and Dracut-network to create such an initramfs?

David >-----Original Message----- >From: Mike Burns [mailto:mburns@redhat.com] >Sent: Wednesday, February 08, 2012 10:35 AM >To: Li, David >Cc: users(a)ovirt.org >Subject: Re: [Users] Pxeboot > >On Wed, 2012-02-08 at 10:24 -0800, Li, David wrote: >> Hi Mike, >> >> I read the oVirt node Wiki and had an impression it's not ready in 2.3 yet: >http://ovirt.org/wiki/Node_Stateless . >> >> Ok, I saw that tool in the ISO. Let me dig in to how to use it. >> The real question now is if I can nfs mount the the real rootfs which would >also be on the TFTP/DHCP server in the final pxe booting stage. Is that >something you are doing too? > >Ok, I think I see where the confusion is now. We support using pxeboot to >install to a local disk, but not full stateless booting and pulling the configuration >from elsewhere. > >It won't really be feasible to so something like this until we have stateless >support worked out, but you're welcome to work with us to get it working. > >Mike > >> >> David >> >> >-----Original Message----- >> >From: Mike Burns [mailto:mburns@redhat.com] >> >Sent: Wednesday, February 08, 2012 10:11 AM >> >To: Li, David >> >Cc: users(a)ovirt.org >> >Subject: Re: [Users] Pxeboot >> > >> >On Wed, 2012-02-08 at 09:53 -0800, Li, David wrote: >> >> Since oVirt node doesn’t support pxeboot in the current release, >> >> does anyone know if I can use RHEV-H to pxeboot and nfs mout the >rootfs? >> > >> >Where does it say that ovirt-node doesn't support pxe boot? I use >> >PXE in my testing. I haven't heard of any issues with PXE either. >> > >> >The livecd-iso-to-pxeboot script in livecd-tools will create the >> >initrd and vmlinuz files for you to import into your PXE server. >> > >> >Mike >> >> >> >> David >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/users >> > >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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.

I understand the challenge you talked about. But this is the very first step. I looked at the archipel but couldn't figure out where it stands on this. No one from their mailing list responded either.

David >-----Original Message----- >From: Mike Burns [mailto:mburns@redhat.com] >Sent: Wednesday, February 08, 2012 11:12 AM >To: Li, David >Cc: users(a)ovirt.org >Subject: Re: [Users] Pxeboot > >On Wed, 2012-02-08 at 10:51 -0800, Li, David wrote: >> Mike, >> >> I 'd like to understand what it takes to do this. >> Do we need a special initramfs for oVirt node to help with the stateless >pxeboot? Some tools like Dracut and Dracut-network to create such an >initramfs? > >There are a few things needed, many of which are discussed on the >Node_Stateless wiki page. There was some work done by some other people >to get a stateless node working for archipel that I haven't pulled back into the >node yet. > >The biggest challenge is that pieces of the oVirt project require there to be >persistent storage locally. For example, when you register a node with the >engine, a manual step is required to approve the node. After this manual step, >some certificates are copied locally into the node and stored. That way, the >node can immediately identify itself with the engine and start working with no >need to identify itself. > >To solve this problem, we need to either 1. remove the need to store stuff >locally 2. provide some way to package up this config and store it somewhere, >then retrieve on boot 3. embed some sort of key or certificate in the pxe >image that allows the engine to know that this valid machine and >automatically approve it. > >The archipel stuff doesn't deal with all of that. My understanding is that they >just start using whatever clients identify themselves. > >I do have a task on my plate to pull the stuff from archipel-node back into >ovirt-node and incorporate what they've done into the overall stateless >design. > >Mike > >> >> David >> >> >-----Original Message----- >> >From: Mike Burns [mailto:mburns@redhat.com] >> >Sent: Wednesday, February 08, 2012 10:35 AM >> >To: Li, David >> >Cc: users(a)ovirt.org >> >Subject: Re: [Users] Pxeboot >> > >> >On Wed, 2012-02-08 at 10:24 -0800, Li, David wrote: >> >> Hi Mike, >> >> >> >> I read the oVirt node Wiki and had an impression it's not ready in 2.3 yet: >> >http://ovirt.org/wiki/Node_Stateless . >> >> >> >> Ok, I saw that tool in the ISO. Let me dig in to how to use it. >> >> The real question now is if I can nfs mount the the real rootfs >> >> which would >> >also be on the TFTP/DHCP server in the final pxe booting stage. Is >> >that something you are doing too? >> > >> >Ok, I think I see where the confusion is now. We support using >> >pxeboot to install to a local disk, but not full stateless booting >> >and pulling the configuration from elsewhere. >> > >> >It won't really be feasible to so something like this until we have >> >stateless support worked out, but you're welcome to work with us to get it >working. >> > >> >Mike >> > >> >> >> >> David >> >> >> >> >-----Original Message----- >> >> >From: Mike Burns [mailto:mburns@redhat.com] >> >> >Sent: Wednesday, February 08, 2012 10:11 AM >> >> >To: Li, David >> >> >Cc: users(a)ovirt.org >> >> >Subject: Re: [Users] Pxeboot >> >> > >> >> >On Wed, 2012-02-08 at 09:53 -0800, Li, David wrote: >> >> >> Since oVirt node doesn’t support pxeboot in the current release, >> >> >> does anyone know if I can use RHEV-H to pxeboot and nfs mout the >> >rootfs? >> >> > >> >> >Where does it say that ovirt-node doesn't support pxe boot? I use >> >> >PXE in my testing. I haven't heard of any issues with PXE either. >> >> > >> >> >The livecd-iso-to-pxeboot script in livecd-tools will create the >> >> >initrd and vmlinuz files for you to import into your PXE server. >> >> > >> >> >Mike >> >> >> >> >> >> David >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> Users mailing list >> >> >> Users(a)ovirt.org >> >> >> http://lists.ovirt.org/mailman/listinfo/users >> >> > >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/users >> > >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >

-----Original Message----- From: Perry Myers [mailto:pmyers@redhat.com] Sent: Wednesday, February 08, 2012 2:54 PM To: Mike Burns Cc: Li, David; users(a)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.

-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Wednesday, February 08, 2012 3:27 PM To: Li, David Cc: Perry Myers; users(a)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 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.fc16.iso > > 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(a)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(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Wednesday, February 08, 2012 4:31 PM To: Li, David Cc: Perry Myers; users(a)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(a)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 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.fc16.iso > >> > >> 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(a)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(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > > >

-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Wednesday, February 08, 2012 6:53 PM To: Li, David Cc: Perry Myers; users(a)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(a)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(a)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 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.fc16.iso > >> >> > >> >> 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(a)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(a)ovirt.org > >> >> http://lists.ovirt.org/mailman/listinfo/users > >> > > >> > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Thursday, February 09, 2012 7:22 AM To: Li, David Cc: Perry Myers; users(a)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(a)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(a)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(a)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 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.fc16.iso > >> >> >> > >> >> >> 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(a)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(a)ovirt.org > >> >> >> http://lists.ovirt.org/mailman/listinfo/users > >> >> > > >> >> > >> > > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

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?

- 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(a)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(a)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(a)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(a)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 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.fc16.iso >> >> >> >> >> >> >> >> 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(a)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(a)ovirt.org >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users >> >> >> > >> >> >> >> >> > >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/users >> > >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >

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

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?

- David ________________________________________ From: Mike Burns [mburns(a)redhat.com] Sent: Thursday, February 09, 2012 8:16 AM To: Li, David Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > >> >> >> >> > >> >> >> >> 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(a)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(a)ovirt.org > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > >> >> >> > > >> >> >> > >> >> > > >> >> > >> >> _______________________________________________ > >> >> Users mailing list > >> >> Users(a)ovirt.org > >> >> http://lists.ovirt.org/mailman/listinfo/users > >> > > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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?

any ideas? - David ________________________________________ From: Mike Burns [mburns(a)redhat.com] Sent: Thursday, February 09, 2012 8:37 AM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 8:16 AM > To: Li, David > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > > >> >> >> >> > > >> >> >> >> 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(a)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(a)ovirt.org > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > > >> >> >> > > > >> >> >> > > >> >> > > > >> >> > > >> >> _______________________________________________ > > >> >> Users mailing list > > >> >> Users(a)ovirt.org > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > >> > > > >> > > >> _______________________________________________ > > >> Users mailing list > > >> Users(a)ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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

I wonder which repo my machine is lacking? - David ________________________________________ From: Mike Burns [mburns(a)redhat.com] Sent: Thursday, February 09, 2012 10:02 AM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 8:37 AM > To: Li, David > Cc: Perry Myers; users(a)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(a)redhat.com] > > Sent: Thursday, February 09, 2012 8:16 AM > > To: Li, David > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > > > >> >> >> >> > > > >> >> >> >> 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(a)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(a)ovirt.org > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > > > >> >> >> > > > > >> >> >> > > > >> >> > > > > >> >> > > > >> >> _______________________________________________ > > > >> >> Users mailing list > > > >> >> Users(a)ovirt.org > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > > >> > > > > >> > > > >> _______________________________________________ > > > >> Users mailing list > > > >> Users(a)ovirt.org > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

The error seems a little stubborn. [lid@FC16-1 recipe]$ echo $OVIRT_LOCAL_REPO 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(a)redhat.com] Sent: Thursday, February 09, 2012 11:15 AM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 10:02 AM > To: Li, David > Cc: Perry Myers; users(a)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(a)redhat.com] > > Sent: Thursday, February 09, 2012 8:37 AM > > To: Li, David > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > Sent: Thursday, February 09, 2012 8:16 AM > > > To: Li, David > > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > > > > >> >> >> >> > > > > >> >> >> >> 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(a)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(a)ovirt.org > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > >> >> >> > > > > > >> >> >> > > > > >> >> > > > > > >> >> > > > > >> >> _______________________________________________ > > > > >> >> Users mailing list > > > > >> >> Users(a)ovirt.org > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > >> > > > > > >> > > > > >> _______________________________________________ > > > > >> Users mailing list > > > > >> Users(a)ovirt.org > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > >

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

Did make publish store the rpms in $OVIRT_LOCAL_REPO? - David ________________________________________ From: Mike Burns [mburns(a)redhat.com] Sent: Thursday, February 09, 2012 11:44 AM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 11:15 AM > To: Li, David > Cc: Perry Myers; users(a)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(a)redhat.com] > > Sent: Thursday, February 09, 2012 10:02 AM > > To: Li, David > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > Sent: Thursday, February 09, 2012 8:37 AM > > > To: Li, David > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > Sent: Thursday, February 09, 2012 8:16 AM > > > > To: Li, David > > > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > > > > > >> >> >> >> > > > > > >> >> >> >> 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(a)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(a)ovirt.org > > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > >> >> >> > > > > > > >> >> >> > > > > > >> >> > > > > > > >> >> > > > > > >> >> _______________________________________________ > > > > > >> >> Users mailing list > > > > > >> >> Users(a)ovirt.org > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > >> > > > > > > >> > > > > > >> _______________________________________________ > > > > > >> Users mailing list > > > > > >> Users(a)ovirt.org > > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users(a)ovirt.org > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Thursday, February 09, 2012 2:12 PM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 12:07 PM > To: Li, David > Cc: Perry Myers; users(a)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(a)redhat.com] > > Sent: Thursday, February 09, 2012 11:44 AM > > To: Li, David > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > Sent: Thursday, February 09, 2012 11:15 AM > > > To: Li, David > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > Sent: Thursday, February 09, 2012 10:02 AM > > > > To: Li, David > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > > Sent: Thursday, February 09, 2012 8:37 AM > > > > > To: Li, David > > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > > > Sent: Thursday, February 09, 2012 8:16 AM > > > > > > To: Li, David > > > > > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > > > > > > > >> >> >> >> > > > > > > > >> >> >> >> 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(a)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(a)ovirt.org > > > > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > >> >> >> > > > > > > > > >> >> >> > > > > > > > >> >> > > > > > > > > >> >> > > > > > > > >> >> _______________________________________________ > > > > > > > >> >> Users mailing list > > > > > > > >> >> Users(a)ovirt.org > > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > >> > > > > > > > > >> > > > > > > > >> _______________________________________________ > > > > > > > >> Users mailing list > > > > > > > >> Users(a)ovirt.org > > > > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Users mailing list > > > > > > Users(a)ovirt.org > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > _______________________________________________ > > > > > Users mailing list > > > > > Users(a)ovirt.org > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

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?

- David ________________________________________ From: Mike Burns [mburns(a)redhat.com] Sent: Thursday, February 09, 2012 12:07 PM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 11:44 AM > To: Li, David > Cc: Perry Myers; users(a)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(a)redhat.com] > > Sent: Thursday, February 09, 2012 11:15 AM > > To: Li, David > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > Sent: Thursday, February 09, 2012 10:02 AM > > > To: Li, David > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > Sent: Thursday, February 09, 2012 8:37 AM > > > > To: Li, David > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > > Sent: Thursday, February 09, 2012 8:16 AM > > > > > To: Li, David > > > > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.iso > > > > > > >> >> >> >> > > > > > > >> >> >> >> 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(a)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(a)ovirt.org > > > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > >> >> >> > > > > > > > >> >> >> > > > > > > >> >> > > > > > > > >> >> > > > > > > >> >> _______________________________________________ > > > > > > >> >> Users mailing list > > > > > > >> >> Users(a)ovirt.org > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > >> > > > > > > > >> > > > > > > >> _______________________________________________ > > > > > > >> Users mailing list > > > > > > >> Users(a)ovirt.org > > > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Users mailing list > > > > > Users(a)ovirt.org > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users(a)ovirt.org > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Thursday, February 09, 2012 4:18 PM To: Li, David Cc: Perry Myers; users(a)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(a)redhat.com] > Sent: Thursday, February 09, 2012 2:12 PM > To: Li, David > Cc: Perry Myers; users(a)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(a)redhat.com] > > Sent: Thursday, February 09, 2012 12:07 PM > > To: Li, David > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > Sent: Thursday, February 09, 2012 11:44 AM > > > To: Li, David > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > Sent: Thursday, February 09, 2012 11:15 AM > > > > To: Li, David > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > > Sent: Thursday, February 09, 2012 10:02 AM > > > > > To: Li, David > > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > > > Sent: Thursday, February 09, 2012 8:37 AM > > > > > > To: Li, David > > > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > > > > > > > Sent: Thursday, February 09, 2012 8:16 AM > > > > > > > To: Li, David > > > > > > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.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(a)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(a)ovirt.org > > > > > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/user > > > > > > > > >> >> >> >> s > > > > > > > > >> >> >> > > > > > > > > > >> >> >> > > > > > > > > >> >> > > > > > > > > > >> >> > > > > > > > > >> >> _______________________________________________ > > > > > > > > >> >> Users mailing list Users(a)ovirt.org > > > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> _______________________________________________ > > > > > > > > >> Users mailing list > > > > > > > > >> Users(a)ovirt.org > > > > > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Users mailing list > > > > > > > Users(a)ovirt.org > > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Users mailing list > > > > > > Users(a)ovirt.org > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

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(a)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-noderefs/changes/38/1738/3 && git > >cherry-pick FETCH_HEAD # checks out the new version of the patch set. > > > >Mike > > > >> > >> > >> - David > >> ________________________________________ > >> From: Mike Burns [mburns(a)redhat.com] > >> Sent: Thursday, February 09, 2012 2:12 PM > >> To: Li, David > >> Cc: Perry Myers; users(a)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(a)redhat.com] > >> > Sent: Thursday, February 09, 2012 12:07 PM > >> > To: Li, David > >> > Cc: Perry Myers; users(a)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(a)redhat.com] > >> > > Sent: Thursday, February 09, 2012 11:44 AM > >> > > To: Li, David > >> > > Cc: Perry Myers; users(a)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(a)redhat.com] > >> > > > Sent: Thursday, February 09, 2012 11:15 AM > >> > > > To: Li, David > >> > > > Cc: Perry Myers; users(a)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(a)redhat.com] > >> > > > > Sent: Thursday, February 09, 2012 10:02 AM > >> > > > > To: Li, David > >> > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > >> > > > > > Sent: Thursday, February 09, 2012 8:37 AM > >> > > > > > To: Li, David > >> > > > > > Cc: Perry Myers; users(a)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(a)redhat.com] > >> > > > > > > Sent: Thursday, February 09, 2012 8:16 AM > >> > > > > > > To: Li, David > >> > > > > > > Cc: Perry Myers; users(a)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(a)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(a)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(a)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(a)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 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.fc16.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(a)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(a)ovirt.org > >> > > > > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/user > >> > > > > > > > >> >> >> >> s > >> > > > > > > > >> >> >> > > >> > > > > > > > >> >> >> > >> > > > > > > > >> >> > > >> > > > > > > > >> >> > >> > > > > > > > >> >> > >_______________________________________________ > >> > > > > > > > >> >> Users mailing list Users(a)ovirt.org > >> > > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users > >> > > > > > > > >> > > >> > > > > > > > >> > >> > > > > > > > >> > >_______________________________________________ > >> > > > > > > > >> Users mailing list > >> > > > > > > > >> Users(a)ovirt.org > >> > > > > > > > >> http://lists.ovirt.org/mailman/listinfo/users > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > _______________________________________________ > >> > > > > > > Users mailing list > >> > > > > > > Users(a)ovirt.org > >> > > > > > > http://lists.ovirt.org/mailman/listinfo/users > >> > > > > > > >> > > > > > > >> > > > > > _______________________________________________ > >> > > > > > Users mailing list > >> > > > > > Users(a)ovirt.org > >> > > > > > http://lists.ovirt.org/mailman/listinfo/users > >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > Users mailing list > >> > > Users(a)ovirt.org > >> > > http://lists.ovirt.org/mailman/listinfo/users > >> > > >> > > >> > _______________________________________________ > >> > Users mailing list > >> > Users(a)ovirt.org > >> > http://lists.ovirt.org/mailman/listinfo/users > >> > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Fri, 2012-02-10 at 14:26 +0200, Cristian Falcas wrote: > > On Fri, Feb 10, 2012 at 03:09, Mike Burns <mburns(a)redhat.com&gt; wrote: > On Thu, 2012-02-09 at 17:05 -0800, Li, David wrote: > > Mike, > > Built it finally! > > Thanks a lot! > > > Woot! > <snip> > > > > Latest git has an error in Makefile: at line 471 it should be > elif [ -n "$(FEDORA)" ]; then \ > instead of > if [ -n "$(FEDORA)" ]; then \ Where are you looking exactly? The current HEAD of the master branch doesn't have this problem. The problem did exist in the second patch set of the stateless/archipel patches, but the third patch set fixed that. Mike > > Best regards, > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

On Wed, 2012-02-08 at 09:53 -0800, Li, David wrote: > Since oVirt node doesn’t support pxeboot in the current release, does > anyone know if I can use RHEV-H to pxeboot and nfs mout the rootfs? Where does it say that ovirt-node doesn't support pxe boot? I use PXE in my testing. I haven't heard of any issues with PXE either. The livecd-iso-to-pxeboot script in livecd-tools will create the initrd and vmlinuz files for you to import into your PXE server.

Hi Douglas, Thanks for the link. However I can't quite tell if this is pxeboot installation or a truly stateless pxeboot that you not only suck in the configurations from the server but also NFS mount the final RHEV-H root fs from the same server. Mike has mentioned oVirt Node 2.3 can only do the install but not the stateless boot. I wonder if this is the same case with RHEV-H.

David >-----Original Message----- >From: Douglas Landgraf [mailto:dougsland@redhat.com] >Sent: Wednesday, February 08, 2012 1:23 PM >To: Mike Burns >Cc: Li, David; users(a)ovirt.org >Subject: Re: [Users] Pxeboot > >Hi Li, David, > >On 02/08/2012 01:11 PM, Mike Burns wrote: >> On Wed, 2012-02-08 at 09:53 -0800, Li, David wrote: >>> Since oVirt node doesn’t support pxeboot in the current release, >>> does anyone know if I can use RHEV-H to pxeboot and nfs mout the rootfs? >> Where does it say that ovirt-node doesn't support pxe boot? I use PXE >> in my testing. I haven't heard of any issues with PXE either. >> >> The livecd-iso-to-pxeboot script in livecd-tools will create the >> initrd and vmlinuz files for you to import into your PXE server. >> >http://docs.redhat.com/docs/en- >US/Red_Hat_Enterprise_Virtualization_for_Servers/2.1/html/5.4- >2.1_Hypervisor_Deployment_Guide/sect-Deployment_Guide- >Preparing_Red_Hat_Enterprise_Virtualization_Hypervisor_installation_media >-Deploying_RHEV_Hypervisors_with_PXE_and_tftp.html > >and > >http://dougsland.livejournal.com/122359.html > >might help you. Fell free to share any doubt with the mailing list. > >-- >Cheers >Douglas _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users