headers
Al Tobey | 1 Dec 02:13
Picon
Gravatar

Re: koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

On Nov 30, 2007 2:56 AM, Tom Brown <tom@...> wrote:
>
> >
> >
> > I've applied Al Tobey's --autonet patch to koan upstream.
> >
> > This seems like it will fix your problem for profile based reinstalls,
> > because it will add in the IP info on the kernel command line based on
> > what you are currently using.
> >
> > Might be worth checking out.   You should be able to use koan 0.6.4
> > from git with your existing Cobbler install.
> >
>
> thanks for the effort here - alas it does not work for me as it makes
> grub look like this
>
> kernel /vmlinuz ro root=LABEL=/1 ksdevice=eth0 lang= kssendmac syslog=19
> 2.168.10.4:25150 text ks=file:ks.cfg ip=$ip_address netmask=$subnet
> hostname=$ho
> stname nameserver=$nameserver gateway=$gateway

I would think that would cause anaconda to fail anyways.

In your template, try putting a check around the net config something like:

#if $varExists('ip_address')
  network --bootproto=static ...
#end if
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel P. Berrange | 1 Dec 18:10
Picon
Favicon

Re: Virt-Manager: Supporting additional para-virtual OS's

On Fri, Nov 30, 2007 at 02:57:16PM +0000, Daniel P. Berrange wrote:
> On Thu, Nov 29, 2007 at 08:14:50PM -0800, Robert Nelson wrote:
> > Daniel P. Berrange wrote:
> > >>I spent some time reworking the virtinst code to support OpenSolaris and 
> > >>make it much easier to support additional OSes.  I've attached the patch 
> > >>file to get some feedback on the work so far.
> > >>    
> > >
> > >Thanks for this. Took me a little while to get to grips with it, but I
> > >like the resulting structure.  I'm going todo  a few tests and if it
> > >works I'll commit it to the repo.
> > >
> > >BTW, for any large patches in the future, its handy for review if you
> > >do separate patches  for re-factoring existing code, vs adding new
> > >capabilities. It would have made it easier to review if the splitting
> > >up of the DistroManager.py file were a simple no-functional-change
> > >refactoring. Also helps people browsing the SCM history in the future
> > >to distinguish the changes. No need to change this existing patch 
> > >though, I'll just add as is...
> > 
> > Please hold off on committing this patch.  I have an updated and better 
> > version coming shortly.  I'll post it as two patches to make the SCM 
> > history more readable.  I'll also post it to a new thread.
> 
> So it turned out to be a little more complicated than I expected. At first
> I liked the idea of having OSDistro create & use the ImageFetcher class
> directly, however, there are circumstances where we need to use the OSDistro
> class without the ImageFetcher, so this dependancy causes problems.
> 
> Second, the FullVirtGuest/ParaVirtGuest classes now call into the installer
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard W.M. Jones | 4 Dec 11:54
Picon
Favicon

Re: solaris virt-install patches

Mark Johnson wrote:
> from conversation on #xen.... current Solaris virt-install patches attached.
> 
> Disclaimers :-)
>   This are informational only (e.g. not proposing they be applied)..
>   They still need cleanup etc.. These patches are what are in the
>     current solaris builds.
>   We are currently still working on the lastest version of virt-install.

Hi Mark,

It was a bit hard to read your patches because they weren't attached 
with a text MIME-type.  Renaming them as '*.txt' or '*.patch', or 
reconfiguring your MUA should fix that.

mac-address-parse:  Looks fine

use-virsh-console:  Sensible patch

outgoing:
This patch seems to be corrupt in some way.  A diff of a diff?

solaris-support:

Solaris puts the Python interpreter in /bin instead of /usr/bin.  This 
will break things on Linux so we should fix this so it can find the 
Python interpreter along the path.  No idea how to fix this with Python 
but I'm sure there's a standard way involving 'env' or something similar.

The rest of the patch looks sensible.  In general all this code needs
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Johnson | 4 Dec 14:05
Picon

Re: solaris virt-install patches

On Dec 4, 2007 5:54 AM, Richard W.M. Jones <rjones@...> wrote:
> Mark Johnson wrote:
> > from conversation on #xen.... current Solaris virt-install patches attached.
> >
> > Disclaimers :-)
> >   This are informational only (e.g. not proposing they be applied)..
> >   They still need cleanup etc.. These patches are what are in the
> >     current solaris builds.
> >   We are currently still working on the lastest version of virt-install.
>
> Hi Mark,
>
> It was a bit hard to read your patches because they weren't attached
> with a text MIME-type.  Renaming them as '*.txt' or '*.patch', or
> reconfiguring your MUA should fix that.

Sorry about that.. :-(

> mac-address-parse:  Looks fine
>
> use-virsh-console:  Sensible patch
>
> outgoing:
> This patch seems to be corrupt in some way.  A diff of a diff?

I was in a rush, included that file by mistake..

> solaris-support:
>
> Solaris puts the Python interpreter in /bin instead of /usr/bin.  This
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rainer Duffner | 4 Dec 18:58
Picon

Question about cobbler - variable substitution

Hi,

I'm doing some tests with cobbler.
I created a kickstart-template with things like:

network --bootproto=static --device=$ksmetadev --onboot=on --ip=$ksip
--netmask=$ksnetmask --gateway=$ksgw --nameserver=$ksns

clearpart --all --drives=sda
part /boot --fstype ext3 --size=100 --ondisk=sda
part pv.2 --size=0 --grow --ondisk=sda
volgroup VolGroup00 --pesize=32768 pv.2
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=512
--grow --maxsize=$ksmaxswap
logvol / --fstype ext3 --name=root --vgname=VolGroup00 --size=$ksmaxslash
logvol /var/log --fstype ext3 --name=varlog --vgname=VolGroup00
--size=$ksmaxvarlog
logvol /var/spool --fstype ext3 --name=varspool --vgname=VolGroup00
--size=$ksmaxvarspool --grow

In the "system" config in the webinterface, I have a corresponding
ksmeta entry:
ksgw=192.168.1.1 ksmaxslash=5000 ksmaxvarspool=2048 ksip=192.168.1.3
ksmetadev=eth0 ksnetmask=255.255.255.0 ksmaxswap=1100
kshostname=host1.intern ksmaxvarlog=2048 ksns=192.168.1.2

I can see that the kickstart file that is being fetched doesn't have all
the expansions, yet.

It's fetched from
(Continue reading)

Permalink | Reply | 9 comments |
headers
Michael DeHaan | 4 Dec 19:42
Picon
Favicon

Re: Question about cobbler - variable substitution

Rainer Duffner wrote:
> Hi,
>
> I'm doing some tests with cobbler.
> I created a kickstart-template with things like:
>
> network --bootproto=static --device=$ksmetadev --onboot=on --ip=$ksip
> --netmask=$ksnetmask --gateway=$ksgw --nameserver=$ksns
>
> clearpart --all --drives=sda
> part /boot --fstype ext3 --size=100 --ondisk=sda
> part pv.2 --size=0 --grow --ondisk=sda
> volgroup VolGroup00 --pesize=32768 pv.2
> logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=512
> --grow --maxsize=$ksmaxswap
> logvol / --fstype ext3 --name=root --vgname=VolGroup00 --size=$ksmaxslash
> logvol /var/log --fstype ext3 --name=varlog --vgname=VolGroup00
> --size=$ksmaxvarlog
> logvol /var/spool --fstype ext3 --name=varspool --vgname=VolGroup00
> --size=$ksmaxvarspool --grow
>
>
> In the "system" config in the webinterface, I have a corresponding
> ksmeta entry:
> ksgw=192.168.1.1 ksmaxslash=5000 ksmaxvarspool=2048 ksip=192.168.1.3
> ksmetadev=eth0 ksnetmask=255.255.255.0 ksmaxswap=1100
> kshostname=host1.intern ksmaxvarlog=2048 ksns=192.168.1.2
>
> I can see that the kickstart file that is being fetched doesn't have all
> the expansions, yet.
(Continue reading)

Permalink | Reply | 8 comments |
headers
Rainer Duffner | 4 Dec 20:55
Picon

Re: Question about cobbler - variable substitution


Am 04.12.2007 um 19:42 schrieb Michael DeHaan:

>
> How are you installing?
>
> PXE menus?   Koan with --profile?    These use the kickstart  
> rendering.
>
> PXE with a set MAC address?  Koan with --system?   These use the  
> kickstarts_sys rendering.
>

Well, when it PXE-TFTP-boots, I get into a menu - but I actually  
don't want to do that ;-)
I want to use a MAC-based system.
Did I do something wrong? I just added the systems via the web-GUI  
and assumed it would select the right system via the MAC-address I  
entered.

cheers,
Rainer
--

-- 
Rainer Duffner
CISSP, LPI, MCSE
rainer@...
Permalink | Reply | 7 comments |
headers
Michael DeHaan | 4 Dec 21:05
Picon
Favicon

Re: Question about cobbler - variable substitution

Rainer Duffner wrote:
>
> Am 04.12.2007 um 19:42 schrieb Michael DeHaan:
>
>>
>> How are you installing?
>>
>> PXE menus? Koan with --profile? These use the kickstart rendering.
>>
>> PXE with a set MAC address? Koan with --system? These use the 
>> kickstarts_sys rendering.
>>
>
>
> Well, when it PXE-TFTP-boots, I get into a menu - but I actually don't 
> want to do that ;-)
> I want to use a MAC-based system.
> Did I do something wrong? I just added the systems via the web-GUI and 
> assumed it would select the right system via the MAC-address I entered.
>
It will ... provided the MAC addresses match up. It sounds like they 
might not.

If you have the MAC entry, it should boot directly to whatever the 
system is assigned to and not sit on the menu.
Permalink | Reply | 6 comments |
headers
Rainer Duffner | 4 Dec 21:23
Picon

Re: Question about cobbler - variable substitution


Am 04.12.2007 um 21:05 schrieb Michael DeHaan:

> Rainer Duffner wrote:
>>
>>
>> Well, when it PXE-TFTP-boots, I get into a menu - but I actually  
>> don't want to do that ;-)
>> I want to use a MAC-based system.
>> Did I do something wrong? I just added the systems via the web-GUI  
>> and assumed it would select the right system via the MAC-address I  
>> entered.
>>
> It will ... provided the MAC addresses match up. It sounds like  
> they might not.
>
> If you have the MAC entry, it should boot directly to whatever the  
> system is assigned to and not sit on the menu.
>

Well, the menu comes after I type "menu".
This was already the case in my test-environment, but it generally  
worked there because I was hardcoding the partition-information and  
the network-configuration was at the profile-level (which is a  
mistake, of course).

Here's from the "systems" file in /var/lib/cobbler/ :

-
     depth: 2
(Continue reading)

Permalink | Reply | 5 comments |
headers
Michael DeHaan | 4 Dec 22:25
Picon
Favicon

Re: Question about cobbler - variable substitution

Rainer Duffner wrote:

Take a look in /tftpboot/pxelinux.cfg/ and see if you can find the 
"encoded" file that matches the MAC address you entered. It should be 
there. This is
the file that the PXE boot process will request and use for system 
configuration. Next, compare that with what you see in the system BIOS 
to ensure that it actually matches up.
It sounds like it's not matching up to me.
> I assume I don't have to assign a fixed IP to every host on the 
> PXE-network via dhcpd.conf?

The TFTP/PXE stage that identifies your system by MAC address does not 
rely on having a static MAC set.
The order is encoded MAC, then encoded IP, then default. Except if you 
are using IA64 arches (elilo), when you must have the IP -- it doesn't 
do boot-by-MAC.
You can add a -vv in your /etc/xinetd.d/tftp file to see a bit more from 
TFTP in syslog.

Hopefully that helps. It really sounds like the MAC addresses aren't 
right to me, maybe a typo somewhere?

>
>
> cheers,
> Rainer
Permalink | Reply | 4 comments |

Gmane