UEFI Support?
by Bill Peck
Has anyone started working on UEFI support in cobbler? I'm guessing we
would want to write UEFI configs for x86, x86_64 and ia64. They would
co-exist with pxe and efi entries.
Thoughts?
14 years
Interest in moving from mod_python to mod_wsgi?
by Devan Goodwin
The Spacewalk team has been working on moving their stuff to mod_wsgi
and in the process realized that Cobbler still uses mod_python, so
they were wondering if we have any plans to do the same. Looking
around a bit it seems like this is generally regarded as a good idea,
mod_python appears to be considered quite poor for performance and
memory, and I'm hearing it's now unmaintained as well. Looking through
the cobbler source it seems we've got a number of mod_python hacks as
well. mod_wsgi is in Fedora and EPEL as far back as EL4.
Anyone feel this is a particularly bad idea?
Thanks,
Devan
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
14 years
cobbler cli user doesn't work after 1.x to 2.0.1 upgrade
by Chris Kelly
Hello-
I upgraded from 1.x to 2.0.1 and the cobbler cli user no longer works.
example:
[root@admin1 ~]# cobbler system add --name=foobar
cobbler.cexceptions.CX:'user <DIRECT> does not have access to
resource: xedit_system'
[root@admin1 ~]#
Looking around in the source code, I see:
/usr/lib/python2.4/site-packages/cobbler/modules/authz_ownership.py
def authorize(api_handle,user,resource,arg1=None,arg2=None):
"""
Validate a user against a resource.
All users in the file are permitted by this module.
"""
if user == "<DIRECT>":
# CLI should always be permitted
return True
...
so that should fall through fine. However, we are using LDAP
([authentication] module = authn_ldap) and I don't see any such code
in the LDAP module. It doesn't seem that adding similar code to the
authn_ldap.py file (and clearing pyo and pyc files and restarting
cobblerd) does the trick.
We are using the config file to manage users ([authorization] module =
authz_configfile) and adding <DIRECT> as a user there doesn't let root
on the command line back in.
Any ideas? Thanks!
-Chris
14 years
Rename deletes the system.
by Niels Basjes
Hi,
I have a brand new CentOS 5.4 32bit system (running inside VMware
server) with cobbler cobbler 2.0.3.1 (build from tag in official git
repo).
I create a system using the webinterface.
I give the name "foo" , select any profile and save.
Now in the list of systems I click the "Rename" option and I change
"foo" into "Foo".
I click the 'Ok' and the system has been deleted.
A rename works fine of the name is different in more than just upper/lower case.
--
Best regards,
Niels Basjes
14 years, 1 month
The ks_mirror should be public_content_t ??
by Niels Basjes
Hi,
I have a brand new CentOS 5.4 32bit system (running inside VMware
server) with cobbler cobbler 2.0.3.1 (build from tag in official git
repo).
Now I got it all running fine if selinux is disabled.
If I enable selinux my 'to-be-installed' system won't load the kernel (vmlinuz)
I figured out what goes wrong. I'm not sure if I did something
incorrect or if this is an issue with cobbler.
cobbler check says:
1 : you need to set some SELinux content rules to ensure cobbler
serves content correctly in your SELinux environment, run the
following: /usr/sbin/semanage fcontext -a -t public_content_t
"/tftpboot/.*"
To double checked that
[root@deployer ~]# /usr/sbin/semanage fcontext -a -t public_content_t
"/tftpboot/.*"
/usr/sbin/semanage: File context for /tftpboot/.* already defined
It turns out that my rsync-ed tree at
/var/www/cobbler/ks_mirror/CentOS5-i386 was still at
httpd_sys_content_t
The hardlinks created by a "cobbler sync" mean that
/tftpboot/images/CentOS5-i386/vmlinuz is also httpd_sys_content_t
causing it to fail.
Now I did a "chcon -R -t public_content_t
/var/www/cobbler/ks_mirror/CentOS5-i386" and it all works again.
But shouldn't cobbler have done this?
Or at least cobbler check should have instructed me to do this?
--
Best regards,
Niels Basjes
14 years, 1 month
2.0.3 Change In Snippet Behaviour
by Devan Goodwin
As a result of my changes for remote snippetdir some behaviour has
changed for snippets containing un-escaped $ characters. Basically you
will see an unexpanded $SNIPPET() macro remaining in your final
kickstart file with 2.0.3.
This is related to a switch from using Cheetah's "#include $filename"
to a "#include source=$content", done to support remote snippetdirs
over http. (as obviously the snippet may no longer be on the local
filesystem) For some reason, including filenames is more forgiving
than the source method.
The workaround is to escape $'s (that aren't meant to be Cheetah
macros), or use #raw.
Two default snippets currently have every $ escaped but one,
partition_select and pre_partition_select.
After about a half dozen attempts to restore the old more forgiving
behaviour and keep remote snippets I've yet to find a way, but after
enough digging I'm going to now propose we:
1) Fix the default snippets with missing escapes.
2) Respin another 2.0.3.z RPM.
3) Keep the new behaviour, you'll have to escape $'s you don't want
Cheetah interpreting.
Based on the fact that virtually every $ in the default snippets are
escaped, and the comments here:
https://fedorahosted.org/cobbler/wiki/KickstartTemplating#Escaping, it
doesn't seem like this was reliable in the first place. Granted the
change in behaviour sucks, but I'm going to propose it may not be
worth the effort to restore.
Thoughts?
Devan
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
14 years, 1 month
uploading to github
by Zubin Mithra
hello,
is it possible for me to clone the main official repository and then
push to github? if so how do i do that?
cheers!!!
Zubin
14 years, 1 month
EPEL and cobbler 2.x
by Aaron Lippold
I noticed that the EPEL pkgs aren't being updated. Does that need to
be picked up or is there a reason it's not being pushed?
Thanks,
Aaron Lippod
lippold(a)gmail.com
AIM/YAHOO: aaronlippold
14 years, 1 month
sphinx documentation
by Corey Osman
Hi,
I am at Pycon 2010 this week and I sat through a tutorial for sphinx
which is a documentation system that goes above and beyond what
reStructuredTex does. This is the same system that the python library
reference uses.
It works by using introspection. So however your class and functions
are defined it will automatically document them. As a bonus if you
have included text in a doc string it will add that for the function.
It will even document todo lists. I think this would be a great
resource for cobbler developers. I would suggest these files be in
the cobbler repo so everyone can document new classes and add helpful
text or code snippets to demonstrate how things are supposed to be
used. I am no expert at this documentation syntax but have created a
sample cobbler api reference in about 3 hours. Its even got a search
function for looking up functions and such. If you click on the
source link on the left nav you can see what the sphinx syntax is
like. Check it out.
http://www.logicminds.biz/cobblerdocs
http://sphinx.pocoo.org/
Corey
14 years, 2 months