hacking anaconda to run post install

I would like to perform some hackery on anaconda that would let me, post 
installation, parse out _only_ the partitioning statements and create 
those partitions that are defined.  Any idea how to go about doing this? 
Has it been done already?

James S. Martin, RHCE
Contractor
Administrative Office of the United States Courts
Washington, DC
[phone]

[John Summerfied]

[e-mail] wrote:
> I would like to perform some hackery on anaconda that would let me, post 
> installation, parse out _only_ the partitioning statements and create 
> those partitions that are defined.  Any idea how to go about doing this? 
> Has it been done already?

What do you want that you can't get from the kickstart file that's 
already left in ~root?
> James S. Martin, RHCE
> Contractor

Is that like a constrictor?

[e-mail] wrote on 08/31/2006 01:02:04 AM:
> [e-mail] wrote:
> > I would like to perform some hackery on anaconda that would let me,

post
> > installation, parse out _only_ the partitioning statements and create 
> > those partitions that are defined.  Any idea how to go about doing

this?
> > Has it been done already?
>
> What do you want that you can't get from the kickstart file that's 
> already left in ~root?

Basically I'm looking for a way to easily contstruct partitions/lvm/raid 
post install using the partioning syntax provided in the kickstart file.

Why?  Because a lot of machines have already been built with a simple 2 
drive mirror and now are adding additional storage.

For example:

I have a called partitions.cfg that contains something like this:

# Raid 1 IDE config
part raid.11    --size 1000     --asprimary     --ondrive=sda
part raid.12    --size 1000     --asprimary     --ondrive=sda
part raid.13    --size 2000     --asprimary     --ondrive=sda
part raid.14    --size 8000                     --ondrive=sda
part raid.15    --size 1 --grow                 --ondrive=sda

part raid.21    --size 1000     --asprimary     --ondrive=sdc
part raid.22    --size 1000     --asprimary     --ondrive=sdc
part raid.23    --size 2000     --asprimary     --ondrive=sdc
part raid.24    --size 8000                     --ondrive=sdc
part raid.25    --size 1 --grow                 --ondrive=sdc

# You can add --spares=x 
raid /opt          --fstype ext3 --device md0 --level=RAID1 raid.11 
raid.21
raid /safe      --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22
raid swap       --fstype swap --device md2 --level=RAID1 raid.13 raid.23
raid /usr       --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24
raid pv.01      --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25

# LVM configuration so that we can resize /var and /usr/local later
volgroup sysvg pv.01 
logvol /var             --vgname=sysvg  --size=8000     --name=var
logvol /var/freespace   --vgname=sysvg  --size=8000 --name=freespacetouse
logvol /usr/local       --vgname=sysvg  --size=1 --grow --name=usrlocal

Now I go and run anconda using this file as input .. It then parses out 
the file, creates the partitions, sets up the raid and the logvols.
> > James S. Martin, RHCE
> > Contractor
>
> Is that like a constrictor?

Are you calling me some sort of cold-blooded snake? :)
> --
>
> Cheers
> John
>
> -- spambait
> [e-mail]  [e-mail]
> Tourist pics

http://portgeographe.environmentaldisasters.cds.merseine.nu/
> do not reply off-list
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[John Summerfied]

[e-mail] wrote:
> [e-mail] wrote on 08/31/2006 01:02:04 AM:
> > [e-mail] wrote:
> > > I would like to perform some hackery on anaconda that would let me,
>
> post
> > > installation, parse out _only_ the partitioning statements and create 
> > > those partitions that are defined.  Any idea how to go about doing
>
> this?
> > > Has it been done already?
> >
> > What do you want that you can't get from the kickstart file that's 
> > already left in ~root?
>
> Basically I'm looking for a way to easily contstruct partitions/lvm/raid 
> post install using the partioning syntax provided in the kickstart file.
>
> Why?  Because a lot of machines have already been built with a simple 2 
> drive mirror and now are adding additional storage.
>
> For example:
>
> I have a called partitions.cfg that contains something like this:
>
> # Raid 1 IDE config
> part raid.11    --size 1000     --asprimary     --ondrive=sda
> part raid.12    --size 1000     --asprimary     --ondrive=sda
> part raid.13    --size 2000     --asprimary     --ondrive=sda
> part raid.14    --size 8000                     --ondrive=sda
> part raid.15    --size 1 --grow                 --ondrive=sda
>
> part raid.21    --size 1000     --asprimary     --ondrive=sdc
> part raid.22    --size 1000     --asprimary     --ondrive=sdc
> part raid.23    --size 2000     --asprimary     --ondrive=sdc
> part raid.24    --size 8000                     --ondrive=sdc
> part raid.25    --size 1 --grow                 --ondrive=sdc
>
> # You can add --spares=x 
> raid /opt          --fstype ext3 --device md0 --level=RAID1 raid.11 
> raid.21
> raid /safe      --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22
> raid swap       --fstype swap --device md2 --level=RAID1 raid.13 raid.23
> raid /usr       --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24
> raid pv.01      --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25
>
> # LVM configuration so that we can resize /var and /usr/local later
> volgroup sysvg pv.01 
> logvol /var             --vgname=sysvg  --size=8000     --name=var
> logvol /var/freespace   --vgname=sysvg  --size=8000 --name=freespacetouse
> logvol /usr/local       --vgname=sysvg  --size=1 --grow --name=usrlocal
>
> Now I go and run anconda using this file as input .. It then parses out 
> the file, creates the partitions, sets up the raid and the logvols.

That's a better description of what you want to do; I wasn't at all 
clear before.

Given the amount of clutter in Anaconda, for what you want, I think I'd 
peruse the source to discover the bit needed and create a separate tool 
based on it.

This page, which I've just found, may be helpful:-)
http://www.wanware.com/tsgdocs/snack.html

Now, if the newt team would grab that, fill in the missing bits, they'd 
have a fairly handy document to add to the newt package:-))
> > > James S. Martin, RHCE
> > > Contractor
> >
> > Is that like a constrictor?
>
> Are you calling me some sort of cold-blooded snake? :)

Like an Anaconda? I thought you were.
> > --
> >
> > Cheers
> > John
> >
> > -- spambait
> > [e-mail]  [e-mail]
> > Tourist pics
>
> http://portgeographe.environmentaldisasters.cds.merseine.nu/
> > do not reply off-list
> >
> > Anaconda-devel-list mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Paul Nasrat]

On Thu, 2006-08-31 at 10:24 -0400, [e-mail] wrote:
> [e-mail] wrote on 08/31/2006 01:02:04 AM:
> > [e-mail] wrote:
> > > I would like to perform some hackery on anaconda that would let me,
>
> post
> > > installation, parse out _only_ the partitioning statements and create 
> > > those partitions that are defined.  Any idea how to go about doing
>
> this?
> > > Has it been done already?
> >
> > What do you want that you can't get from the kickstart file that's 
> > already left in ~root?
>
> Basically I'm looking for a way to easily contstruct partitions/lvm/raid 
> post install using the partioning syntax provided in the kickstart file.

I'd look at pykickstart for the parsing you can define handlers for your
conf and possibly use partedUtils/pyparted to do some of the work.

Paul