Cobbler imports from NAS boxes, etc

I've added some code to Cobbler to make importing things like trees on 
external filers much easier.   Mirroring content to /var/www/cobbler for 
these
configurations is no longer required.   This means that for most users, 
the needs to run "cobbler distro add" vs "cobbler import" will be 
greatly diminished.

This can be invoked (using upstream source) as:

cobbler import --mirror=/path/where/filer/is/mounted --name=filer 
--available-as=nfs://nfsserver.example.org:/is/mounted/here

This will be useful for folks who do not have very large /var partitions 
for mirroring content under the Apache space, or for folks who want
to store their distro trees somewhere else than on the Cobbler server.

"tree" will be set correctly in the kickstart, relative to the path 
where everything is discovered.

If you have multiple distros available in the location, Cobbler will 
crawl through the directories and auto-add all of them.

This will also be in the 0.6.0 release, and I've alreaded updated the 
web import examples and the cobbler manpage.

--Michael

[PATCH] Add a11y names for virt-manager components

Hello all,

Attached is a patch that adds some simple accessibility names for input
components of virt-manager. This is to facilitate future gui testing.

Thanks,
Cole

-- 
Cole Robinson
crobinso@...

diff -r 9a984728fe4b src/vmm-add-hardware.glade
--- a/src/vmm-add-hardware.glade	Mon Jul 30 10:03:45 2007 -0400
+++ b/src/vmm-add-hardware.glade	Sun Jul 29 16:05:10 2007 -0400
@@ -177,6 +177,9 @@
 			      <property name="visible">True</property>
 			      <property name="add_tearoffs">False</property>
 			      <property name="focus_on_click">True</property>
+			      <accessibility>
+				<atkproperty name="AtkObject::accessible_name" translatable="yes">Hardware Type Select</atkproperty>
+			      </accessibility>
 			    </widget>
 			    <packing>
 			      <property name="left_attach">1</property>
@@ -604,6 +607,9 @@
 					  <property name="has_frame">True</property>
 					  <property name="invisible_char">•</property>
 					  <property name="activates_default">False</property>

Re: [PATCH] Add a11y names for virt-manager components

Cole Robinson wrote:
> Hello all,
> 
> Attached is a patch that adds some simple accessibility names for input
> components of virt-manager. This is to facilitate future gui testing.
> 
> Thanks,
> Cole
> 

+1.

I'm going to commit this unless anyone objects...

--Hugh

--

-- 
Red Hat Virtualization Group http://redhat.com/virtualization
Hugh Brock           | virt-manager http://virt-manager.org
hbrock@...    | virtualization library http://libvirt.org

Re: [PATCH] Add a11y names for virt-manager components

Cole Robinson wrote:
> Hello all,
> 
> Attached is a patch that adds some simple accessibility names for input
> components of virt-manager. This is to facilitate future gui testing.
> 
> Thanks,
> Cole
> 

The patch doesn't seem to break anything, but I am getting a warning: 
libglade-WARNING **: Unexpected element <accessibility> inside <widget>. 
You know anything about this?

Thanks,
--Hugh

--

-- 
Red Hat Virtualization Group http://redhat.com/virtualization
Hugh Brock           | virt-manager http://virt-manager.org
hbrock@...    | virtualization library http://libvirt.org

Cobbler + %pre and %post in kickstart

Hello,

I'm curious to know how people deal with pre-install steps like
configuring hardware RAID arrays, or post-install things like
installing server-specific non-Red Hat packages, system setting
tweaks, etc, during kickstart.  Is kickstart's %pre and %post the best
way to do this, or does Cobbler have anything up its sleeve to do this
differently?  It seems like profiles or even perhaps triggers could be
useful, but I'm not quite sure what the best way to accomplish this
would be.

To illustrate my point, say I have 100 Dell PowerEdge 2950 servers all
requiring the same base Red Hat ES 4 installation:  50 need to be
configured with hardware RAID 5 and Apache installed in addition to
the base OS, 30 need to be configured with hardrware RAID 10 and
MySQL, and 20 need to be configured with hardware RAID 1 and
Webalizer.  Obviously, I don't want to manually configure the RAID
arrays prior to provisioning them if I can avoid it.  Provided Dell
has a tool that runs under linux that can configure the hardware RAID
controller *and* I can associate a MAC address to a required RAID
config and additional packages, what is the best way to do both the
pre-install and the post-install steps?

Thanks in advance for any help!

Mike

Re: Cobbler + %pre and %post in kickstart

Hi,

If you find a way to do this outside of the RAID bios I would be very
interested.

There are utilities to manage the raid once the OS is installed but I
believe it's more basic stuff (i.e. check status, list containers, show
hot-swap).

If these utilities could fully managed the raid (i.e. create/delete
containers) then you could potentially build these utilities into the boot
images are provision that way ( no idea if it's possible).

Cheers,
Harry

> Hello,
>
> I'm curious to know how people deal with pre-install steps like
> configuring hardware RAID arrays, or post-install things like
> installing server-specific non-Red Hat packages, system setting
> tweaks, etc, during kickstart.  Is kickstart's %pre and %post the best
> way to do this, or does Cobbler have anything up its sleeve to do this
> differently?  It seems like profiles or even perhaps triggers could be
> useful, but I'm not quite sure what the best way to accomplish this
> would be.
>
> To illustrate my point, say I have 100 Dell PowerEdge 2950 servers all
> requiring the same base Red Hat ES 4 installation:  50 need to be
> configured with hardware RAID 5 and Apache installed in addition to

Re: Cobbler + %pre and %post in kickstart

On 8/2/07, Harry Hoffman <hhoffman@...> wrote:
> If you find a way to do this outside of the RAID bios I would be very
> interested.
>
> There are utilities to manage the raid once the OS is installed but I
> believe it's more basic stuff (i.e. check status, list containers, show
> hot-swap).

Dell actually provides something that *should* work - Dell OpenManage
Deployment Toolkit:

http://support.dell.com/support/downloads/format.aspx?c=us&l=en&s=gen&deviceid=4450&libid=36&releaseid=R158116&vercnt=4&formatcnt=0&SystemID=PWE_2950&servicetag=&os=LIN4&osl=en&catid=-1&impid=-1

I haven't tried using the RAID tools just yet, but it does seem
feasible to shim it into kickstart.  I assume other hardware vendors
have similar tools.

Mike

Re: [PATCH] Add a11y names for virt-manager components

Hugh Brock wrote:
> Cole Robinson wrote:
>> Hello all,
>>
>> Attached is a patch that adds some simple accessibility names for input
>> components of virt-manager. This is to facilitate future gui testing.
>>
>> Thanks,
>> Cole
>>
> 
> The patch doesn't seem to break anything, but I am getting a warning: 
> libglade-WARNING **: Unexpected element <accessibility> inside <widget>. 
> You know anything about this?
> 
> Thanks,
> --Hugh
> 

Hmm, I tried to reproduce it but I'm not seeing it on fully updated F7
at least. I'm guessing this happens when you start up the patched
virt-manager?

- Cole

--

-- 
Cole Robinson
crobinso@...

Re: Cobbler + %pre and %post in kickstart

Mike M wrote:
> On 8/2/07, Harry Hoffman <hhoffman@...> wrote:
>   
>> If you find a way to do this outside of the RAID bios I would be very
>> interested.
>>
>> There are utilities to manage the raid once the OS is installed but I
>> believe it's more basic stuff (i.e. check status, list containers, show
>> hot-swap).
>>     
>
> Dell actually provides something that *should* work - Dell OpenManage
> Deployment Toolkit:
>
> http://support.dell.com/support/downloads/format.aspx?c=us&l=en&s=gen&deviceid=4450&libid=36&releaseid=R158116&vercnt=4&formatcnt=0&SystemID=PWE_2950&servicetag=&os=LIN4&osl=en&catid=-1&impid=-1
>
> I haven't tried using the RAID tools just yet, but it does seem
> feasible to shim it into kickstart.  I assume other hardware vendors
> have similar tools.
>   

Ironically, I used to write hardware RAID configuration software in a 
previous life :)

In theory, it should be possible to (a) retrieve the OEM command line 
tool in %pre (wget?) and configure hardware RAID with it there (in 
%pre), so you wouldn't have to rebuild the initrd just to add the raid 
tools.  Either way, after running the RAID tool in %pre you will 
probably have to do something like scsi-add-single to get Anaconda to 
see the new drives prior to partitioning setup.   Linux does not 

Re: [PATCH] Add a11y names for virt-manager components

Cole Robinson wrote:
> Hugh Brock wrote:
>> Cole Robinson wrote:
>>> Hello all,
>>>
>>> Attached is a patch that adds some simple accessibility names for input
>>> components of virt-manager. This is to facilitate future gui testing.
>>>
>>> Thanks,
>>> Cole
>>>
>> The patch doesn't seem to break anything, but I am getting a warning: 
>> libglade-WARNING **: Unexpected element <accessibility> inside <widget>. 
>> You know anything about this?
>>
>> Thanks,
>> --Hugh
>>
> 
> Hmm, I tried to reproduce it but I'm not seeing it on fully updated F7
> at least. I'm guessing this happens when you start up the patched
> virt-manager?
> 

Yeah, I get it when I open the create wizard actually. I was testing on, 
umm, latest F7 I think. Could be a bad merge since your patch to 
vmm-create.glade merged with offsets. However the message itself is odd; 
<accessibility> should be legal inside <widget>.

Note I see the warning when I run virt-manager from the command line a