[Ovirt-devel] [PATCH node] Introduces the node-admin toolset.

Joey Boggs jboggs at redhat.com
Tue Sep 1 14:17:06 UTC 2009


Darryl L. Pierce wrote:
> On Mon, Aug 31, 2009 at 04:48:41PM -0400, Joey Boggs wrote:
>   
>> So I've got the tool set installed, but not fully tested just yet,  
>> here's some things that need to be changed
>>
>> python -m compileall /usr/lib/python2.6/site-packages/nodeadmin in  
>> common-post.ks of ovirt-node-image otherwise they get removed during  
>> blacklisting
>> # common-blacklist.ks:find / -name '*.py' -exec rm -f {} \;
>>     
>
> That should be okay, though, right? As long as the *.pyc files remain we
> should be okay.
>
>   
Yeah we just need to compile them before the blacklisting parts of  
o-n-i so they hang around
>> __init__.py is commented out, cant get this to copy to buildroot for  
>> some reason, still working on it any ideas?
>> # %{__install} -p -m0644 admin/__init__.py  
>> %{buildroot}%{python_sitelib}/nodeadmin
>>     
>
> Yeah, I've got no idea why that doesn't work.
>
>   
>> missing dependencies, whether via rpm/python failures
>>
>> +python-setuptools  - (needed for load_entry_point in nodeadmin)
>> +dbus-python           +newt
>> +newt-python
>> +pkgconfig
>> +python-devel
>> +slang
>> +slang-devel   
>>     
>
> kk, adding them in.
>
>   
>> The egg creation in ovirt-node package for nodeadmin is failing  
>> somewhere and the install doesnt complete during the build process,  
>> which requires it to be run again on boot. I don't see any obvious  
>> failures, what can I look for?
>>     
>
> I'm not sure. This python stuff is mostly new to me. I can ask some guys
> here ITO, such as ashcrow, to give me some advice on this. 
>
>   




More information about the ovirt-devel mailing list