Re: [Spacewalk-devel] Provisioning
On 03/28/2012 09:08 AM, duncan.in...@virginmoney.com wrote: I wondered if it would add any useful functionality to be able to create a boot.kernel.org-style image on the Spacewalk/Satellite server. The resultant image would then boot a system and go direct to the Spacewalk server for instructions. I know it's a basic copy of PXE booting, but it allows this functionality to exist in a few key areas. What is boot.kernel.org? (asked Google) - Aha. If I understand it correctly it is the same thing as "cobbler makeiso" [1]. Yes, that would be useful. And since Spacewalk already use cobbler, integrate Spacewalk with "cobbler makeiso" can be relatively easy. [1] https://fedorahosted.org/cobbler/wiki/BuildIso -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Provisioning
Hi, I've posted this elsewhere but thought the idea might be useful to Spacewalk. Have been thinking about how to eliminate some of the key-presses in our Satellite kickstart installs and came up with the following: I wondered if it would add any useful functionality to be able to create a boot.kernel.org-style image on the Spacewalk/Satellite server. The resultant image would then boot a system and go direct to the Spacewalk server for instructions. I know it's a basic copy of PXE booting, but it allows this functionality to exist in a few key areas. 1. Deploying to VMware machines. I could create a template with this boot image on. Firing up a machine created from this template would head direct for the Spacewalk server for provisioning. PXE isn't the default boot method for a VMware guest. Using an image like this would get around having to configure the machine to boot into BIOS and then tweak the BIOS settings to boot PXE first. 2. Situations where PXE is not permitted. No - there aren't many. Or so I thought. When adding the PXE settings to your corporate DHCP servers isn't permitted, you can be left high and dry when trying to provision new machines. An ISO image to boot from that heads directly to the Spacewalk server for menu etc would remove the task of having to alter syslinux ISO's whenever a new kickstart is created, for example. The value-add would be that both these scenarios would only need to be done once (barring a change of hostname for the Spacewalk server). All the logic, kickstarts, menu system (if wanted) stay on the Spacewalk server. Would this be at all useful to Spacewalk or have I missed a trick? Cheers Duncan Innes | Linux Architect | Virgin Money This e-mail is intended to be confidential to the recipient. If you receive a copy in error, please inform the sender and then delete this message. Virgin Money do not accept responsibility for changes made to any e-mail after sending. Virgin Money have swept, and believe this e-mail to be free of viruses and profanity but make no guarantees to this effect. Virgin Money Personal Financial Service Limited is authorised and regulated by the Financial Services Authority. Registered in England no. 3072766. Entered on the Financial Services Authority's Register http://www.fsa.gov.uk/register/. Register Number 179271. Church House Trust Limited is authorised and regulated by the Financial Services Authority. Registered in England no. 980698. Entered on the Financial Services Authority's Register http://www.fsa.gov.uk/register/. Register Number 204459. Virgin Money Unit Trust Managers Limited is authorised and regulated by the Financial Services Authority. Registered in England no. 3000482. Entered on the Financial Services Authority's Register. Register Number 171748. Virgin Money Limited. Registered in England no. 4232392. Introducer appointed representative only of Virgin Money Personal Financial Service Limited. Virgin Money Management Services Limited. Registered in England no. 3072772. Virgin Money Holdings (UK) Limited. Registered in England no. 3087587. All the above companies have their Registered office at Discovery House, Whiting Road, Norwich NR4 6EJ. Northern Rock plc - Registered in England (Company No. 6952311). Registered Office: Northern Rock House Gosforth Newcastle upon Tyne NE3 4PL. Authorised and regulated by the Financial Services Authority. All products are open only to residents of the United Kingdom. This message has been checked for viruses and spam by the Virgin Money email scanning system powered by Messagelabs.___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Provisioning over IPv6
Dne 15.12.2011 18:01, Milan Zazrivec napsal(a): Ok, this seems like you simply provisioned your machine over the IPv4 stack. With IPv6 enabled and nothing was broken. That is good news to me as well :) Mirek ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Provisioning over IPv6
> Dne 15.12.2011 17:23, Milan Zazrivec napsal(a): > > How exactly did you test this part? Did you change the network line > > in the kickstart file in any way? Did you append any kernel cmd line > > arguments for the new installation? > > Nope, I did no change. I just scheduled kickstart and did rhn_check on > target machine. > I have system, which has dual stack - it has both IPv4 and IPv6 from DHCP. > I did not test how it will behave in IPv6 only environment as I do not > have such machine. Ok, this seems like you simply provisioned your machine over the IPv4 stack. -MZ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Provisioning over IPv6
Dne 15.12.2011 17:23, Milan Zazrivec napsal(a): How exactly did you test this part? Did you change the network line in the kickstart file in any way? Did you append any kernel cmd line arguments for the new installation? Nope, I did no change. I just scheduled kickstart and did rhn_check on target machine. I have system, which has dual stack - it has both IPv4 and IPv6 from DHCP. I did not test how it will behave in IPv6 only environment as I do not have such machine. Mirek ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Provisioning over IPv6
> I tested Milan work on IPv6 provisioning. > > - if I choose "DHCP using first available interface" or the default > (should be the same): system successfully kickstart (jupiii) How exactly did you test this part? Did you change the network line in the kickstart file in any way? Did you append any kernel cmd line arguments for the new installation? -MZ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Provisioning over IPv6
> I tested Milan work on IPv6 provisioning. > > - if I choose "DHCP using first available interface" or the default > (should be the same): system successfully kickstart (jupiii) > > - if I choose "Use static interface" - and it does not matter if I > choose "IPv6 gateway" - the result is still same: after reboot I got > error from init: > List of available partitions: > No filesystem could mount root, tried: iso9660 > Kernel panic - not syncing: VFS: Unable to mount root fs on > unkown-block(9,1) It's because RHEL-6.2 initrd.img is packed with xz and koan (when trying to repack the ramdisk image) assumes gzip. As a result, koan creates a non-usable ramdisk -> you see this error. -MZ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Provisioning over IPv6
Dne 14.12.2011 10:31, Miroslav Suchy napsal(a): I tested Milan work on IPv6 provisioning. - if I choose "DHCP using first available interface" or the default (should be the same): system successfully kickstart (jupiii) - if I choose "Use static interface" - and it does not matter if I choose "IPv6 gateway" - the result is still same: after reboot I got error from init: List of available partitions: No filesystem could mount root, tried: iso9660 Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(9,1) I forgot to say, that I tested it with RHEL 6.2 kickstarts (which is probably significant). Mirek ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Provisioning over IPv6
I tested Milan work on IPv6 provisioning. - if I choose "DHCP using first available interface" or the default (should be the same): system successfully kickstart (jupiii) - if I choose "Use static interface" - and it does not matter if I choose "IPv6 gateway" - the result is still same: after reboot I got error from init: List of available partitions: No filesystem could mount root, tried: iso9660 Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(9,1) Mirek ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
