August 2008 - cobbler - Fedora Mailing-Lists

by Michael DeHaan

Hi folks, So I've tried on the past to get a article on Cobbler in Wikipedia. Why? So it can show up on the disambiguation page for one. Wikipedia is the #2 hit for searching for "Cobbler" in Google. Other software projects of similar size have Wikipedia pages and it seems like a decent thing to have. It turns out that my couple of attempts to write such an article get deleted, because folks think I am engaging in a Wiki War, or that I'm trying to spam things. Really, I'm not, I want to be as objective as possible. So, here's what I've been told to do by Wikipedia: -- Have some one from the community write a minimal encyclopedic article, and make sure that article is marked as a stub -- Let others expand the article, remaining concise and so forth. -- Once it is no longer a stub later we can edit it as needed. Would someone (preferably not @redhat.com) like to take care of this for me? I would appreciate it very much and would happily add information about the population of elephants to other Wikipedia articles as needed! --Michael

15 years, 8 months

3
4
0 / 0

cobbersysreport utility

by Anderson Silva

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've written a python utility that interacts with the cobbler API, to allow a person to select what fields they want reported formatted for either: media wiki, doku, trac or plain text... here is an example: Trac output: [root@bean2 tmp]# cobblersysreport -s cobbler.re.redhat.com -f trac ||profile||name||hostname||ip_address||vm|| ||RHEL-5-Server-U1-xen-x86_64||build01_re_redhat_com||build01||10.10.42.5||Yes|| ||RHEL-5-Server-U1-xen-x86_64||buildmaster01_re_redhat_com||buildmaster01||10.10.42.6||Yes|| ||RHEL-5-Server-U1-i386||buildnode01_re_redhat_com||buildnode01||10.10.42.10||No|| Doku output: [root@bean2 tmp]# cobblersysreport -s cobbler.re.redhat.com -f doku ^profile^name^hostname^ip_address^vm^ |RHEL-5-Server-U1-xen-x86_64|build01_re_redhat_com|build01|10.10.42.5|Yes| |RHEL-5-Server-U1-xen-x86_64|buildmaster01_re_redhat_com|buildmaster01|10.10.42.6|Yes| |RHEL-5-Server-U1-i386|buildnode01_re_redhat_com|buildnode01|10.10.42.10|No| The fields reported can be picked by the user at /etc/cobblersysreport.conf, which looks like: [root@bean2 tmp]# cat /etc/cobblersysreport.conf # all available fields (assumes only inft0 is available) # fields = 'profile','owners','kickstart','virt_bridge','name',\ # 'parent','virt_cpus','virt_type','dhcp_tag','subnet','virt_bridge',\ # 'hostname','mac_address','ip_address','gateway','vm' # # Fields to Display (order matters) order = 'profile', 'name', 'hostname', 'ip_address', 'vm' The only major limitation of this utility right now it that it only allows 1 interface (intf0) to be selected via the config file. I've talked privately to DeHaan about this and he suggested I share it on the list. I'm interesting into merging this feature upstream (as DeHaan has suggested): like: cobbler system report [--name foo] [--format trac|text|...] But, I am not sure if I should address the intf0 limitation first, and if this feature would really be worth being merged upstream or if it is too specific and would end up bloating the project too much. I am up for discussions... Thanks, AS -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFImcPJECmX3C4JWKgRAiuxAJoDP5ZfQI7U+ug5EoZGNosH/08tQgCfWh4U 1tzHRWxlhGkTfUc5u4K6j34= =dCrx -----END PGP SIGNATURE-----

15 years, 8 months

2
15
0 / 0

Koan now can install SuSE VMs

by Michael DeHaan

I've now applied this: https://fedorahosted.org/pipermail/cobbler/2008-August/000453.html This will allow for installing SuSE VMs on Fedora/RHEL for migration purposes or just general usage. --Michael

15 years, 8 months

1
0
0 / 0

Throttling

by Johnston, Christopher (GAE)

Does cobbler have the ability to throttle the number of servers being built at a single time? I know I can put throttling into yum and into apache to prevent X number of data to be transferred, but curious if there has been some thought on doing this for cobbler. I have a system today that is all home grown built where we sometimes stage around 10-50 builds off at a time (we have A LOT of blades and grid nodes). We are interested in looking at cobbler for the future and this would be a feature that would be of interest. Christopher Johnston Linux Engineering (201) 499-4839 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -------- IRS Circular 230 Disclosure: Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.

15 years, 8 months

3
2
0 / 0

Cobbler survey results

by Michael DeHaan

A while back I emailed out a survey to Cobbler users to better understand a bit about what they manage and other management tools they use. Here are the distilled results. 18 people responded. For comparison, we have over 200 people on the mailing list so this is a small section, but still a very good sample size. I have mixed up the responses so you can not really infer anything from the order of the answers to each question. ------ (A) How many cobbler objects do you have of each type? cobbler distro list | wc -l cobbler profile list | wc -l cobbler system list | wc -l cobbler repo list | wc -l ANSWER Anywhere from 2 to 24 seperate distributions are managed by each cobbler server. The average is about 9, high is 24. Most people have between 1.5 and 2x as many profiles as they have distributions, the high is 25. The average number of system records is 60, though since systems can be installed via profile this does is not a useful metric for determining how many systems cobbler manages, hence question B -- yet the high is an impressive 257 (you can have thousands of systems installed via cobbler and only create system records for critical systems -- in a grid configuration most likely you would just use profiles). The average number of repositories being managed by Cobbler is 10, though some folks are managing a suprisingly high number of repositories -- 30, 50, or 60, while a handful are not using Cobbler to manage their yum repositories. My main takeaway for this is that the "cobbler system" object is still very important, and people are still interested in the customizations it makes possible. This is good, because that was my reason for asking the question -- people aren't just using profiles and stopping there. I'm also surprised to see the yum repo management features are being used a lot more widely than I thought, which is good, so we should possibly spend more time on those in the future. ------ (B) About how many systems (machines and virtual machines) do you have at your organization that are being managed by Cobbler? Ballpark is ok, if you can't say "a lot" is fine too :) ANSWER Lots of answers like 200+, 300+, or "a lot", coupled with a lot of folkks with only 10 or 20 systems. Knowing what I know from those not responding to the survey, Cobbler has quite a few installs in the 1000-3000+ range. >From this, I think we can tell that concentrating on SOHO/lab users as well as Enterprises, like we've been doing, is the continued way to go. We have users in both camps and the needs of both are equally important. --------- (C) How many cobbler servers do you have? ANSWERS: Evenly mixed between having one server and having 2-3 servers is the norm. A couple sites had 5-6 servers with a single master. One site has 13 servers. Conclusion: replication is a very important use case. One user also mentioned failover, so that is something to research in the future I think -- or at least to document. ------- (D) Generally, what does your organization do? You can omit this if you want. Short answers like "school", "university", "hosting", "government", "research", "finance", etc are fine. ANSWERS: universities -- 4 hosting - 2 finance - 3 legal - 1 system administration / consulting - 1 animation - 1 other - 1 home - 1 There's no real niche area here, which is as I expected. From what I know from IRC and other conversations, this is pretty representative. Universities and hosting are some of the main use cases, but there are also a good number of "grid" type setups. I would imagine some organizations are not going to be able to answer the survey in full, in which case, we still appreciate you all as users very much. This was mainly to get a better idea of what is out there. ---- (E) What do you use for config management if any (puppet, cfengine, bcfg2, home grown, proprietary apps) ANSWERS: Widely varied, but a lot of cfengine and puppet. I know of a bit of bcfg2 usage from IRC, but this is about what I would expect. homegrown migrating to puppet none, generates reports mixture of homegrown and puppet cfengine cfengine migrating to puppet cfengine migrating to mixture of homegrown/puppet puppet (starting to learn) cfengine none cfengine/homegrown investigating hoping to use puppet + spacewalk puppet + ssh for loops puppet cfengine --- (F) What do you use for package management if any (yum directly, Satellite, etc) ANSWERS: Note: based on "cobbler repo list", most users using "yum" are using cobbler with yum. yum yum yum yum yum yumyum yum+mrepo yum rhn+yum directly yum rhn+yum for 3rd party content yum, satellite, pkg* commands yum/rpm CONCLUSION: I think this is about what I expected, though I wasn't quite expecting as much use of regular yum for users that might have a Satellite. In all, nothing new, and no new apps identified here. Ok... (G) What do you use for monitoring if any (nagios, proprietary apps, etc) ANSWERS: munin/unicentre mrtg/hobbit cacti+proprietary nagios nagios migrating to opennms nagios func N/A nagios nagios/helix zenoss nagios (investigating) nagios/munin/cacti nagios nagios nagios/cacti/smokeping nagios/munin CONCLUSION: Lots of interest in nagios, so having at least some snippets or something to help with Nagios setup may be worthwhile. Still, lots of other tools out there to where we could built out similar tips/snippets/etc. If anyone thinks that might be useful, let me know, and we can talk about it. It's also interesting to share what people are using with one another, so that is really my reason for asking that question. Good data. ==== (H) Are you using virtualization? If so, which (VMware, Xen, KVM, other)? Are you using Cobbler for virtualization deployment? ANSWERS: vmware/virtualbox (looking at) xen/yes xen/yes xen/yes xen/yes xen/KVM/yes no vmware/no vmware/xen/yes vmware/xen/yes vmware/yes vmware/no xen/yes vmware/xen/other/yes xen/virtualbox/yes vmware/xen/maybe CONCLUSION: cobbler doesn't do virtualbox yet but it seems like we'd want to look at it. Virtualization uptake is actually larger than what I thought among respondants, so either (A) people pick up Cobbler because they want to do virtualization, or (B) there really is that much interest in Virt. Either way, good deal, and good to know. I didn't uncover interest in any other virt types other than virtualbox, and I think if people are using vmware with koan, you are not alone, so ideas on ways we can make it better (and patches) are greatly welcome. (I) Feel free to share whatever else you want :) ANSWERS: Lots of "thanks", to which I have to say, "you're welcome" and glad to be working with all of you. We had a request for a database backend, some comments about more LDAP integration (that might be site specific), and requests to keep doing things to support PXE-less environments like the livecd and cobbler buildiso. One comment about wanting more puppet integration. Etc.. Etc... ---- Ok, so that sums it up, thanks to everyone who submitted things and hopefully this proves to be an interesting window in how people are using Cobbler and what other tools people on this list are using. Thanks! --Michael

15 years, 8 months

1
0
0 / 0

Cobbler image objects now generically PXEable on metal / systems can inherit from images

by Michael DeHaan

This is a neat feature, but takes some explaining. Previously we have been able to support things like memtest through special code, we found the image if installed and added it to certain PXE configs. However you couldn't easily do things like make MAC address AA:BB:CC:DD:EE:FF automatically boot memtest, and so forth. Now, imagine that special code didn't exist and we could do it generically. Also imagine that we weren't booting something as lame as memtest. What if we could easily boot anything we wanted, just as we can deal with kernels and initrds? Now we can. cobbler image add --name=SuperAwesomeLiveEnvironment --file=/opt/live.iso Though we don't have to imagine it, we have this on the devel branch now. Admittedly, I still tested with memtest and not SuperAwesomeLiveEnvironment, though the concept is entirely the same :) Further, we can do things like assign a specific MAC address to boot that live environment: cobbler system add --name=fooserver --mac=AA:BB:CC:DD:EE:FF --image=SuperAwesomeLiveEnvironment The next time that system boots, it will boot that image. This doesn't have to be an installation related image, it might just be a firmware update disk. Note that I didn't use --profile here, I used --image. One of cobbler's goals is to be able to break down the abstraction between physical and virtual machines. Here we are able to use "cobbler image" objects (with cobbler/koan 1.1 and later) to do installs both physically and virtually. The ability to netboot a live-image plays critically into our desire to support net-deploying live image cloning environments, and may also have applications for Stateless environments (LTSP thin clients?). Note that as with cobbler profiles, you can also assign arbitrary "append" options (i..e kernel options) to images. We could also use this to streamline our existing support to memtest, but since that is already "automatic" and relatively clever (it adds it automatically if you have memtestx86+ installed) we probably will leave that as is. Anyhow, feel free to test this feature out on the devel branch with any bootable images. I will say adding this feature was relatively complicated, so with the image support, testing will be very welcome to see if we run into any problems. No changes are in place for any existing profiles or system objects, just note that now systems can also "inherit" from images, or profiles, but not both at the same time. We still need to update the WebUI to take advantage of these features. So, please help test this out, and if everything is good we'll see about updating the Wiki to show how to use this with other tools, such as the firmware update images that are already out there... and we can also do some more testing with live environments and maybe even stateless applications. --Michael

15 years, 8 months

4
15
0 / 0

[PATCH] New option for passing kernel parameters for bootloader

by Lassi Pölönen

Since current kernel options (kopts) in cobbler are only for installer's kernel and are not propagating to installed system, a new option for passing kernel parameters for installed kernel is needed for the purpose. Here's a patch that adds kernel_option_post variable which is available in templating. Second one is a snippet that calls grubby in kickstart's %post section to pass the options to grub's kernel line. -Lassi diff --git a/cobbler/collection.py b/cobbler/collection.py index 04d891a..72f454c 100644 --- a/cobbler/collection.py +++ b/cobbler/collection.py @@ -91,6 +91,7 @@ class Collection(serializable.Serializable): SEARCH_REKEY = { 'kopts' : 'kernel_options', + 'kopts_post' : 'kernel_options_post', 'ksmeta' : 'ks_meta', 'inherit' : 'parent', 'ip' : 'ip_address', diff --git a/cobbler/item.py b/cobbler/item.py index 9ddfc95..e54399a 100644 --- a/cobbler/item.py +++ b/cobbler/item.py @@ -149,6 +149,22 @@ class Item(serializable.Serializable): self.kernel_options = value return True + def set_kernel_options_post(self,options,inplace=False): + """ + Post kernel options are a space delimited list, + like 'a=b c=d e=f g h i=j' or a hash. + """ + (success, value) = utils.input_string_or_hash(options,None) + if not success: + raise CX(_("invalid post kernel options")) + else: + if inplace: + for key in value.keys(): + self.kernel_options_post[key] = value[key] + else: + self.kernel_options_post = value + return True + def set_ksmeta(self,options,inplace=False): """ A comma delimited list of key value pairs, like 'a=b,c=d,e=f' or a hash. diff --git a/cobbler/item_distro.py b/cobbler/item_distro.py index 744bb6d..e434c46 100644 --- a/cobbler/item_distro.py +++ b/cobbler/item_distro.py @@ -31,16 +31,17 @@ class Distro(item.Item): """ Reset this object. """ - self.name = None - self.owners = self.settings.default_ownership - self.kernel = (None, '<<inherit>>')[is_subobject] - self.initrd = (None, '<<inherit>>')[is_subobject] - self.kernel_options = ({}, '<<inherit>>')[is_subobject] - self.ks_meta = ({}, '<<inherit>>')[is_subobject] - self.arch = ('i386', '<<inherit>>')[is_subobject] - self.breed = ('redhat', '<<inherit>>')[is_subobject] - self.source_repos = ([], '<<inherit>>')[is_subobject] - self.depth = 0 + self.name = None + self.owners = self.settings.default_ownership + self.kernel = (None, '<<inherit>>')[is_subobject] + self.initrd = (None, '<<inherit>>')[is_subobject] + self.kernel_options = ({}, '<<inherit>>')[is_subobject] + self.kernel_options_post = ({}, '<<inherit>>')[is_subobject] + self.ks_meta = ({}, '<<inherit>>')[is_subobject] + self.arch = ('i386', '<<inherit>>')[is_subobject] + self.breed = ('redhat', '<<inherit>>')[is_subobject] + self.source_repos = ([], '<<inherit>>')[is_subobject] + self.depth = 0 def make_clone(self): ds = self.to_datastruct() @@ -59,17 +60,18 @@ class Distro(item.Item): """ Modify this object to take on values in seed_data """ - self.parent = self.load_item(seed_data,'parent') - self.name = self.load_item(seed_data,'name') - self.owners = self.load_item(seed_data,'owners',self.settings.default_ownership) - self.kernel = self.load_item(seed_data,'kernel') - self.initrd = self.load_item(seed_data,'initrd') - self.kernel_options = self.load_item(seed_data,'kernel_options') - self.ks_meta = self.load_item(seed_data,'ks_meta') - self.arch = self.load_item(seed_data,'arch','i386') - self.breed = self.load_item(seed_data,'breed','redhat') - self.source_repos = self.load_item(seed_data,'source_repos',[]) - self.depth = self.load_item(seed_data,'depth',0) + self.parent = self.load_item(seed_data,'parent') + self.name = self.load_item(seed_data,'name') + self.owners = self.load_item(seed_data,'owners',self.settings.default_ownership) + self.kernel = self.load_item(seed_data,'kernel') + self.initrd = self.load_item(seed_data,'initrd') + self.kernel_options = self.load_item(seed_data,'kernel_options') + self.kernel_options_post = self.load_item(seed_data,'kernel_options_post') + self.ks_meta = self.load_item(seed_data,'ks_meta') + self.arch = self.load_item(seed_data,'arch','i386') + self.breed = self.load_item(seed_data,'breed','redhat') + self.source_repos = self.load_item(seed_data,'source_repos',[]) + self.depth = self.load_item(seed_data,'depth',0) # backwards compatibility enforcement self.set_arch(self.arch) @@ -160,17 +162,18 @@ class Distro(item.Item): Return a serializable datastructure representation of this object. """ return { - 'name' : self.name, - 'kernel' : self.kernel, - 'initrd' : self.initrd, - 'kernel_options' : self.kernel_options, - 'ks_meta' : self.ks_meta, - 'arch' : self.arch, - 'breed' : self.breed, - 'source_repos' : self.source_repos, - 'parent' : self.parent, - 'depth' : self.depth, - 'owners' : self.owners + 'name' : self.name, + 'kernel' : self.kernel, + 'initrd' : self.initrd, + 'kernel_options' : self.kernel_options, + 'kernel_options_post' : self.kernel_options_post, + 'ks_meta' : self.ks_meta, + 'arch' : self.arch, + 'breed' : self.breed, + 'source_repos' : self.source_repos, + 'parent' : self.parent, + 'depth' : self.depth, + 'owners' : self.owners } def printable(self): @@ -179,26 +182,28 @@ class Distro(item.Item): """ kstr = utils.find_kernel(self.kernel) istr = utils.find_initrd(self.initrd) - buf = _("distro : %s\n") % self.name - buf = buf + _("breed : %s\n") % self.breed - buf = buf + _("architecture : %s\n") % self.arch - buf = buf + _("initrd : %s\n") % istr - buf = buf + _("kernel : %s\n") % kstr - buf = buf + _("kernel options : %s\n") % self.kernel_options - buf = buf + _("ks metadata : %s\n") % self.ks_meta - buf = buf + _("owners : %s\n") % self.owners + buf = _("distro : %s\n") % self.name + buf = buf + _("breed : %s\n") % self.breed + buf = buf + _("architecture : %s\n") % self.arch + buf = buf + _("initrd : %s\n") % istr + buf = buf + _("kernel : %s\n") % kstr + buf = buf + _("kernel options : %s\n") % self.kernel_options + buf = buf + _("post kernel options : %s\n") % self.kernel_options_post + buf = buf + _("ks metadata : %s\n") % self.ks_meta + buf = buf + _("owners : %s\n") % self.owners return buf def remote_methods(self): return { - 'name' : self.set_name, - 'kernel' : self.set_kernel, - 'initrd' : self.set_initrd, - 'kopts' : self.set_kernel_options, - 'arch' : self.set_arch, - 'ksmeta' : self.set_ksmeta, - 'breed' : self.set_breed, - 'owners' : self.set_owners + 'name' : self.set_name, + 'kernel' : self.set_kernel, + 'initrd' : self.set_initrd, + 'kopts' : self.set_kernel_options, + 'kopts_post' : self.set_kernel_options_post, + 'arch' : self.set_arch, + 'ksmeta' : self.set_ksmeta, + 'breed' : self.set_breed, + 'owners' : self.set_owners } diff --git a/cobbler/item_profile.py b/cobbler/item_profile.py index 0e16f46..b87d0db 100644 --- a/cobbler/item_profile.py +++ b/cobbler/item_profile.py @@ -33,40 +33,42 @@ class Profile(item.Item): """ Reset this object. """ - self.name = None - self.owners = self.settings.default_ownership - self.distro = (None, '<<inherit>>')[is_subobject] - self.kickstart = (self.settings.default_kickstart , '<<inherit>>')[is_subobject] - self.kernel_options = ({}, '<<inherit>>')[is_subobject] - self.ks_meta = ({}, '<<inherit>>')[is_subobject] - self.virt_cpus = (1, '<<inherit>>')[is_subobject] - self.virt_file_size = (self.settings.default_virt_file_size, '<<inherit>>')[is_subobject] - self.virt_ram = (self.settings.default_virt_ram, '<<inherit>>')[is_subobject] - self.repos = ([], '<<inherit>>')[is_subobject] - self.depth = 1 - self.virt_type = (self.settings.default_virt_type, '<<inherit>>')[is_subobject] - self.virt_path = ("", '<<inherit>>')[is_subobject] - self.virt_bridge = (self.settings.default_virt_bridge, '<<inherit>>')[is_subobject] - self.dhcp_tag = ("default", '<<inherit>>')[is_subobject] - self.parent = '' - self.server = "<<inherit>>" + self.name = None + self.owners = self.settings.default_ownership + self.distro = (None, '<<inherit>>')[is_subobject] + self.kickstart = (self.settings.default_kickstart , '<<inherit>>')[is_subobject] + self.kernel_options = ({}, '<<inherit>>')[is_subobject] + self.kernel_options_post = ({}, '<<inherit>>')[is_subobject] + self.ks_meta = ({}, '<<inherit>>')[is_subobject] + self.virt_cpus = (1, '<<inherit>>')[is_subobject] + self.virt_file_size = (self.settings.default_virt_file_size, '<<inherit>>')[is_subobject] + self.virt_ram = (self.settings.default_virt_ram, '<<inherit>>')[is_subobject] + self.repos = ([], '<<inherit>>')[is_subobject] + self.depth = 1 + self.virt_type = (self.settings.default_virt_type, '<<inherit>>')[is_subobject] + self.virt_path = ("", '<<inherit>>')[is_subobject] + self.virt_bridge = (self.settings.default_virt_bridge, '<<inherit>>')[is_subobject] + self.dhcp_tag = ("default", '<<inherit>>')[is_subobject] + self.parent = '' + self.server = "<<inherit>>" def from_datastruct(self,seed_data): """ Load this object's properties based on seed_data """ - self.parent = self.load_item(seed_data,'parent','') - self.name = self.load_item(seed_data,'name') - self.owners = self.load_item(seed_data,'owners',self.settings.default_ownership) - self.distro = self.load_item(seed_data,'distro') - self.kickstart = self.load_item(seed_data,'kickstart') - self.kernel_options = self.load_item(seed_data,'kernel_options') - self.ks_meta = self.load_item(seed_data,'ks_meta') - self.repos = self.load_item(seed_data,'repos', []) - self.depth = self.load_item(seed_data,'depth', 1) - self.dhcp_tag = self.load_item(seed_data,'dhcp_tag', 'default') - self.server = self.load_item(seed_data,'server', '<<inherit>>') + self.parent = self.load_item(seed_data,'parent','') + self.name = self.load_item(seed_data,'name') + self.owners = self.load_item(seed_data,'owners',self.settings.default_ownership) + self.distro = self.load_item(seed_data,'distro') + self.kickstart = self.load_item(seed_data,'kickstart') + self.kernel_options = self.load_item(seed_data,'kernel_options') + self.kernel_options_post = self.load_item(seed_data,'kernel_options_post') + self.ks_meta = self.load_item(seed_data,'ks_meta') + self.repos = self.load_item(seed_data,'repos', []) + self.depth = self.load_item(seed_data,'depth', 1) + self.dhcp_tag = self.load_item(seed_data,'dhcp_tag', 'default') + self.server = self.load_item(seed_data,'server', '<<inherit>>') # backwards compatibility if type(self.repos) != list: @@ -214,23 +216,24 @@ class Profile(item.Item): Return hash representation for the serializer """ return { - 'name' : self.name, - 'owners' : self.owners, - 'distro' : self.distro, - 'kickstart' : self.kickstart, - 'kernel_options' : self.kernel_options, - 'virt_file_size' : self.virt_file_size, - 'virt_ram' : self.virt_ram, - 'virt_bridge' : self.virt_bridge, - 'virt_cpus' : self.virt_cpus, - 'ks_meta' : self.ks_meta, - 'repos' : self.repos, - 'parent' : self.parent, - 'depth' : self.depth, - 'virt_type' : self.virt_type, - 'virt_path' : self.virt_path, - 'dhcp_tag' : self.dhcp_tag, - 'server' : self.server, + 'name' : self.name, + 'owners' : self.owners, + 'distro' : self.distro, + 'kickstart' : self.kickstart, + 'kernel_options' : self.kernel_options, + 'kernel_options_post' : self.kernel_options_post, + 'virt_file_size' : self.virt_file_size, + 'virt_ram' : self.virt_ram, + 'virt_bridge' : self.virt_bridge, + 'virt_cpus' : self.virt_cpus, + 'ks_meta' : self.ks_meta, + 'repos' : self.repos, + 'parent' : self.parent, + 'depth' : self.depth, + 'virt_type' : self.virt_type, + 'virt_path' : self.virt_path, + 'dhcp_tag' : self.dhcp_tag, + 'server' : self.server, } @@ -238,24 +241,25 @@ class Profile(item.Item): """ A human readable representaton """ - buf = _("profile : %s\n") % self.name + buf = _("profile : %s\n") % self.name if self.distro == "<<inherit>>": - buf = buf + _("parent : %s\n") % self.parent + buf = buf + _("parent : %s\n") % self.parent else: - buf = buf + _("distro : %s\n") % self.distro - buf = buf + _("dhcp tag : %s\n") % self.dhcp_tag - buf = buf + _("kernel options : %s\n") % self.kernel_options - buf = buf + _("kickstart : %s\n") % self.kickstart - buf = buf + _("ks metadata : %s\n") % self.ks_meta - buf = buf + _("owners : %s\n") % self.owners - buf = buf + _("repos : %s\n") % self.repos - buf = buf + _("server : %s\n") % self.server - buf = buf + _("virt bridge : %s\n") % self.virt_bridge - buf = buf + _("virt cpus : %s\n") % self.virt_cpus - buf = buf + _("virt file size : %s\n") % self.virt_file_size - buf = buf + _("virt path : %s\n") % self.virt_path - buf = buf + _("virt ram : %s\n") % self.virt_ram - buf = buf + _("virt type : %s\n") % self.virt_type + buf = buf + _("distro : %s\n") % self.distro + buf = buf + _("dhcp tag : %s\n") % self.dhcp_tag + buf = buf + _("kernel options : %s\n") % self.kernel_options + buf = buf + _("post kernel options : %s\n") % self.kernel_options_post + buf = buf + _("kickstart : %s\n") % self.kickstart + buf = buf + _("ks metadata : %s\n") % self.ks_meta + buf = buf + _("owners : %s\n") % self.owners + buf = buf + _("repos : %s\n") % self.repos + buf = buf + _("server : %s\n") % self.server + buf = buf + _("virt bridge : %s\n") % self.virt_bridge + buf = buf + _("virt cpus : %s\n") % self.virt_cpus + buf = buf + _("virt file size : %s\n") % self.virt_file_size + buf = buf + _("virt path : %s\n") % self.virt_path + buf = buf + _("virt ram : %s\n") % self.virt_ram + buf = buf + _("virt type : %s\n") % self.virt_type return buf @@ -267,6 +271,7 @@ class Profile(item.Item): 'distro' : self.set_distro, 'kickstart' : self.set_kickstart, 'kopts' : self.set_kernel_options, + 'kopts_post' : self.set_kernel_options_post, 'virt-file-size' : self.set_virt_file_size, 'virt-ram' : self.set_virt_ram, 'ksmeta' : self.set_ksmeta, diff --git a/cobbler/item_system.py b/cobbler/item_system.py index 15d8fae..1cb3746 100644 --- a/cobbler/item_system.py +++ b/cobbler/item_system.py @@ -29,25 +29,26 @@ class System(item.Item): return cloned def clear(self,is_subobject=False): - self.name = None - self.owners = self.settings.default_ownership - self.profile = None - self.image = None - self.kernel_options = {} - self.ks_meta = {} - self.interfaces = {} - self.netboot_enabled = True - self.depth = 2 - self.kickstart = "<<inherit>>" # use value in profile - self.server = "<<inherit>>" # "" (or settings) - self.virt_path = "<<inherit>>" # "" - self.virt_type = "<<inherit>>" # "" - self.virt_cpus = "<<inherit>>" # "" - self.virt_file_size = "<<inherit>>" # "" - self.virt_ram = "<<inherit>>" # "" - self.virt_type = "<<inherit>>" # "" - self.virt_path = "<<inherit>>" # "" - self.virt_bridge = "<<inherit>>" # "" + self.name = None + self.owners = self.settings.default_ownership + self.profile = None + self.image = None + self.kernel_options = {} + self.kernel_options_post = {} + self.ks_meta = {} + self.interfaces = {} + self.netboot_enabled = True + self.depth = 2 + self.kickstart = "<<inherit>>" # use value in profile + self.server = "<<inherit>>" # "" (or settings) + self.virt_path = "<<inherit>>" # "" + self.virt_type = "<<inherit>>" # "" + self.virt_cpus = "<<inherit>>" # "" + self.virt_file_size = "<<inherit>>" # "" + self.virt_ram = "<<inherit>>" # "" + self.virt_type = "<<inherit>>" # "" + self.virt_path = "<<inherit>>" # "" + self.virt_bridge = "<<inherit>>" # "" def delete_interface(self,name): """ @@ -86,17 +87,18 @@ class System(item.Item): # and store (in-memory) in the new format. # (the main complexity here is the migration to NIC data structures) - self.parent = self.load_item(seed_data, 'parent') - self.name = self.load_item(seed_data, 'name') - self.owners = self.load_item(seed_data, 'owners', self.settings.default_ownership) - self.profile = self.load_item(seed_data, 'profile') - self.image = self.load_item(seed_data, 'image') - self.kernel_options = self.load_item(seed_data, 'kernel_options', {}) - self.ks_meta = self.load_item(seed_data, 'ks_meta', {}) - self.depth = self.load_item(seed_data, 'depth', 2) - self.kickstart = self.load_item(seed_data, 'kickstart', '<<inherit>>') - self.netboot_enabled = self.load_item(seed_data, 'netboot_enabled', True) - self.server = self.load_item(seed_data, 'server', '<<inherit>>') + self.parent = self.load_item(seed_data, 'parent') + self.name = self.load_item(seed_data, 'name') + self.owners = self.load_item(seed_data, 'owners', self.settings.default_ownership) + self.profile = self.load_item(seed_data, 'profile') + self.image = self.load_item(seed_data, 'image') + self.kernel_options = self.load_item(seed_data, 'kernel_options', {}) + self.kernel_options_post = self.load_item(seed_data, 'kernel_options_post', {}) + self.ks_meta = self.load_item(seed_data, 'ks_meta', {}) + self.depth = self.load_item(seed_data, 'depth', 2) + self.kickstart = self.load_item(seed_data, 'kickstart', '<<inherit>>') + self.netboot_enabled = self.load_item(seed_data, 'netboot_enabled', True) + self.server = self.load_item(seed_data, 'server', '<<inherit>>') # virt specific self.virt_path = self.load_item(seed_data, 'virt_path', '<<inherit>>') @@ -392,44 +394,46 @@ class System(item.Item): def to_datastruct(self): return { - 'name' : self.name, - 'kernel_options' : self.kernel_options, - 'depth' : self.depth, - 'interfaces' : self.interfaces, - 'ks_meta' : self.ks_meta, - 'kickstart' : self.kickstart, - 'netboot_enabled' : self.netboot_enabled, - 'owners' : self.owners, - 'parent' : self.parent, - 'profile' : self.profile, - 'image' : self.image, - 'server' : self.server, - 'virt_cpus' : self.virt_cpus, - 'virt_bridge' : self.virt_bridge, - 'virt_file_size' : self.virt_file_size, - 'virt_path' : self.virt_path, - 'virt_ram' : self.virt_ram, - 'virt_type' : self.virt_type + 'name' : self.name, + 'kernel_options' : self.kernel_options, + 'kernel_options_post' : self.kernel_options_post, + 'depth' : self.depth, + 'interfaces' : self.interfaces, + 'ks_meta' : self.ks_meta, + 'kickstart' : self.kickstart, + 'netboot_enabled' : self.netboot_enabled, + 'owners' : self.owners, + 'parent' : self.parent, + 'profile' : self.profile, + 'image' : self.image, + 'server' : self.server, + 'virt_cpus' : self.virt_cpus, + 'virt_bridge' : self.virt_bridge, + 'virt_file_size' : self.virt_file_size, + 'virt_path' : self.virt_path, + 'virt_ram' : self.virt_ram, + 'virt_type' : self.virt_type } def printable(self): - buf = _("system : %s\n") % self.name - buf = buf + _("profile : %s\n") % self.profile - buf = buf + _("image : %s\n") % self.image - buf = buf + _("kernel options : %s\n") % self.kernel_options - buf = buf + _("kickstart : %s\n") % self.kickstart - buf = buf + _("ks metadata : %s\n") % self.ks_meta - - buf = buf + _("netboot enabled? : %s\n") % self.netboot_enabled - buf = buf + _("owners : %s\n") % self.owners - buf = buf + _("server : %s\n") % self.server + buf = _("system : %s\n") % self.name + buf = buf + _("profile : %s\n") % self.profile + buf = buf + _("image : %s\n") % self.image + buf = buf + _("kernel options : %s\n") % self.kernel_options + buf = buf + _("kernel options post : %s\n") % self.kernel_options_post + buf = buf + _("kickstart : %s\n") % self.kickstart + buf = buf + _("ks metadata : %s\n") % self.ks_meta + + buf = buf + _("netboot enabled? : %s\n") % self.netboot_enabled + buf = buf + _("owners : %s\n") % self.owners + buf = buf + _("server : %s\n") % self.server - buf = buf + _("virt cpus : %s\n") % self.virt_cpus - buf = buf + _("virt file size : %s\n") % self.virt_file_size - buf = buf + _("virt path : %s\n") % self.virt_path - buf = buf + _("virt ram : %s\n") % self.virt_ram - buf = buf + _("virt type : %s\n") % self.virt_type + buf = buf + _("virt cpus : %s\n") % self.virt_cpus + buf = buf + _("virt file size : %s\n") % self.virt_file_size + buf = buf + _("virt path : %s\n") % self.virt_path + buf = buf + _("virt ram : %s\n") % self.virt_ram + buf = buf + _("virt type : %s\n") % self.virt_type counter = 0 @@ -469,6 +473,7 @@ class System(item.Item): 'profile' : self.set_profile, 'image' : self.set_image, 'kopts' : self.set_kernel_options, + 'kopts_post' : self.set_kernel_options_post, 'ksmeta' : self.set_ksmeta, 'hostname' : self.set_hostname, 'kickstart' : self.set_kickstart, diff --git a/cobbler/modules/cli_distro.py b/cobbler/modules/cli_distro.py index 853b51d..d971fa7 100644 --- a/cobbler/modules/cli_distro.py +++ b/cobbler/modules/cli_distro.py @@ -43,10 +43,11 @@ class DistroFunction(commands.CobblerFunction): if self.matches_args(args,["add"]): p.add_option("--clobber", dest="clobber", help="allow add to overwrite existing objects", action="store_true") if not self.matches_args(args,["dumpvars","remove","report","list"]): - p.add_option("--initrd", dest="initrd", help="absolute path to initrd.img (REQUIRED)") - p.add_option("--kernel", dest="kernel", help="absolute path to vmlinuz (REQUIRED)") - p.add_option("--kopts", dest="kopts", help="ex: 'noipv6'") - p.add_option("--ksmeta", dest="ksmeta", help="ex: 'blippy=7'") + p.add_option("--initrd", dest="initrd", help="absolute path to initrd.img (REQUIRED)") + p.add_option("--kernel", dest="kernel", help="absolute path to vmlinuz (REQUIRED)") + p.add_option("--kopts", dest="kopts", help="ex: 'noipv6'") + p.add_option("--kopts-post", dest="kopts_post", help="ex: 'clocksource=pit'") + p.add_option("--ksmeta", dest="ksmeta", help="ex: 'blippy=7'") if not self.matches_args(args,["find"]): p.add_option("--in-place", action="store_true", default=False, dest="inplace", help="edit items in kopts or ksmeta without clearing the other items") @@ -85,6 +86,8 @@ class DistroFunction(commands.CobblerFunction): obj.set_initrd(self.options.initrd) if self.options.kopts: obj.set_kernel_options(self.options.kopts,self.options.inplace) + if self.options.kopts_post: + obj.set_kernel_options_post(self.options.kopts_post,self.options.inplace) if self.options.ksmeta: obj.set_ksmeta(self.options.ksmeta,self.options.inplace) if self.options.breed: diff --git a/cobbler/modules/cli_profile.py b/cobbler/modules/cli_profile.py index 25ca635..a9de7a6 100644 --- a/cobbler/modules/cli_profile.py +++ b/cobbler/modules/cli_profile.py @@ -43,14 +43,15 @@ class ProfileFunction(commands.CobblerFunction): if not self.matches_args(args,["dumpvars","remove","report","list"]): - p.add_option("--distro", dest="distro", help="ex: 'RHEL-5-i386' (REQUIRED)") - p.add_option("--dhcp-tag", dest="dhcp_tag", help="for use in advanced DHCP configuration") - p.add_option("--inherit", dest="inherit", help="inherit from this profile name, defaults to no") + p.add_option("--distro", dest="distro", help="ex: 'RHEL-5-i386' (REQUIRED)") + p.add_option("--dhcp-tag", dest="dhcp_tag", help="for use in advanced DHCP configuration") + p.add_option("--inherit", dest="inherit", help="inherit from this profile name, defaults to no") p.add_option("--kickstart", dest="kickstart", help="absolute path to kickstart template (RECOMMENDED)") - p.add_option("--ksmeta", dest="ksmeta", help="ex: 'blippy=7'") - p.add_option("--kopts", dest="kopts", help="ex: 'noipv6'") + p.add_option("--ksmeta", dest="ksmeta", help="ex: 'blippy=7'") + p.add_option("--kopts", dest="kopts", help="ex: 'noipv6'") + p.add_option("--kopts-post", dest="kopts_post",help="ex: 'clocksource=pit'") if not self.matches_args(args,["find"]): - p.add_option("--in-place",action="store_true", dest="inplace", default=False, help="edit items in kopts or ksmeta without clearing the other items") + p.add_option("--in-place",action="store_true", dest="inplace", default=False, help="edit items in kopts, kopts_post or ksmeta without clearing the other items") p.add_option("--name", dest="name", help="a name for the profile (REQUIRED)") @@ -99,6 +100,7 @@ class ProfileFunction(commands.CobblerFunction): if self.options.distro: obj.set_distro(self.options.distro) if self.options.kickstart: obj.set_kickstart(self.options.kickstart) if self.options.kopts: obj.set_kernel_options(self.options.kopts,self.options.inplace) + if self.options.kopts_post: obj.set_kernel_options_post(self.options.kopts_post,self.options.inplace) if self.options.ksmeta: obj.set_ksmeta(self.options.ksmeta,self.options.inplace) if self.options.virt_file_size: obj.set_virt_file_size(self.options.virt_file_size) if self.options.virt_ram: obj.set_virt_ram(self.options.virt_ram) diff --git a/cobbler/modules/cli_system.py b/cobbler/modules/cli_system.py index fbf40cb..4c7bb67 100644 --- a/cobbler/modules/cli_system.py +++ b/cobbler/modules/cli_system.py @@ -51,10 +51,11 @@ class SystemFunction(commands.CobblerFunction): p.add_option("--ip", dest="ip", help="ex: 192.168.1.55, (RECOMMENDED)") p.add_option("--kickstart", dest="kickstart", help="override profile kickstart template") p.add_option("--kopts", dest="kopts", help="ex: 'noipv6'") + p.add_option("--kopts-post", dest="kopts_post", help="ex: 'clocksource=pit'") p.add_option("--ksmeta", dest="ksmeta", help="ex: 'blippy=7'") p.add_option("--mac", dest="mac", help="ex: 'AA:BB:CC:DD:EE:FF', (RECOMMENDED)") if not self.matches_args(args, ["find"]): - p.add_option("--in-place", action="store_true", default=False, dest="inplace", help="edit items in kopts or ksmeta without clearing the other items") + p.add_option("--in-place", action="store_true", default=False, dest="inplace", help="edit items in kopts, kopts_post or ksmeta without clearing the other items") p.add_option("--name", dest="name", help="a name for the system (REQUIRED)") @@ -101,6 +102,7 @@ class SystemFunction(commands.CobblerFunction): if self.options.profile: obj.set_profile(self.options.profile) if self.options.image: obj.set_image(self.options.image) if self.options.kopts: obj.set_kernel_options(self.options.kopts,self.options.inplace) + if self.options.kopts_post: obj.set_kernel_options_post(self.options.kopts_post,self.options.inplace) if self.options.ksmeta: obj.set_ksmeta(self.options.ksmeta,self.options.inplace) if self.options.kickstart: obj.set_kickstart(self.options.kickstart) if self.options.netboot_enabled: obj.set_netboot_enabled(self.options.netboot_enabled) diff --git a/cobbler/utils.py b/cobbler/utils.py index a2adfa6..c77e3f1 100644 --- a/cobbler/utils.py +++ b/cobbler/utils.py @@ -427,6 +427,11 @@ def blender(api_handle,remove_hashes, root_obj): if len(kernel_txt) < 244: results["kernel_options"]["kssendmac"] = None + # convert post kernel options to string + if results["kernel_options_post"]: + results["kernel_options_post"] = hash_to_string(results["kernel_options_post"]) + + # make interfaces accessible without Cheetah-voodoo in the templates # EXAMPLE: $ip == $ip0, $ip1, $ip2 and so on. diff --git a/webui_templates/distro_edit.tmpl b/webui_templates/distro_edit.tmpl index be96e7a..10ae09e 100644 --- a/webui_templates/distro_edit.tmpl +++ b/webui_templates/distro_edit.tmpl @@ -146,6 +146,20 @@ function disablename(value) <tr> <td> + <label for="kopts_post">Post Kernel Options</label> + </td> + <td> + <input type="text" size="255" style="width: 400px;" name="kopts_post" id="kopts_post" + #if $distro + value="$distro.kernel_options_post" + #end if + /> + <p class="context-tip">Example: clocksource=pit nosmp noapic nolapic</p> + </td> + </tr> + + <tr> + <td> <label for="ksmeta">Kickstart Metadata</label> </td> <td> diff --git a/webui_templates/profile_edit.tmpl b/webui_templates/profile_edit.tmpl index 0c8f156..79a9bc7 100644 --- a/webui_templates/profile_edit.tmpl +++ b/webui_templates/profile_edit.tmpl @@ -23,7 +23,7 @@ function disablename(value)  @@ -157,6 +157,20 @@ function disablename(value) <tr> <td> + <label for="kopts_post">Post Kernel Options</label> + </td> + <td> + <input type="text" size="255" style="width: 400px;" name="kopts_post" id="kopts_post" + #if $profile + value="$profile.kernel_options_post" + #end if + /> + <p class="context-tip">Example: clocksource=pit nosmp noapic nolapic</p> + </td> + </tr> + + <tr> + <td> <label for="ksmeta">Kickstart Metadata</label> </td> <td> diff --git a/webui_templates/system_edit.tmpl b/webui_templates/system_edit.tmpl index b996520..72b1b81 100644 --- a/webui_templates/system_edit.tmpl +++ b/webui_templates/system_edit.tmpl @@ -176,6 +176,20 @@ function page_onload() { <tr id="id9005"> <td> + <label for="kopts_post">Post Kernel Options</label> + </td> + <td> + <input type="text" size="255" style="width: 400px;" name="kopts_post" id="kopts_post" + #if $system + value="$system.kernel_options_post" + #end if + /> + <p class="context-tip">Example: clocksource=pit nosmp noapic nolapic</p> + </td> + </tr> + + <tr id="id9006"> + <td> <label for="ksmeta">Kickstart Metadata</label> </td> <td> @@ -188,7 +202,7 @@ function page_onload() { </td> </tr> - <tr id="id9006"> + <tr id="id9007"> <td> <label for="netboot">Netboot Enabled</label> </td> #set $kernel_options_post = $getVar('$kernel_options_post', {}) #if len($kernel_options_post) > 0 %post /sbin/grubby --update-kernel=`/sbin/grubby --default-kernel` --args="$kernel_options_post" #end if

15 years, 8 months

2
1
0 / 0

RFE: --drive-layout

by Jim Wildman

As per some of our discussions several weeks ago I think a --drive-layout option would be very useful. It would allow drive layouts to be created and used across profiles, and expose them to view (as opposed to those written into snippets) with the usual reporting mechanisms. I don't see this as replacing snippet based disk layout, but augmenting it. Possible options/syntax/etc.... --drive-layout=name --breed=[lvm,partition] default to lvm with lvm, use VolGroup00, LogVolxx as per anaconda --ondisk default to hda, sda --swap=[recommended,Megs] --mount0=[mount point, must start with slash] --size=[minimum megs] --grow --ondisk override global above thoughts? Jim Wildman jim(a)rossberry.com

15 years, 8 months

1
0
0 / 0

[SURVEY] How are you using Cobbler?

by Michael DeHaan

If you don't mind sharing, I'm curious about a few things. (A) How many cobbler objects do you have of each type? cobbler distro list | wc -l cobbler profile list | wc -l cobbler system list | wc -l cobbler repo list | wc -l (B) About how many systems (machines and virtual machines) do you have at your organization that are being managed by Cobbler? Ballpark is ok, if you can't say "a lot" is fine too :) (C) How many cobbler servers do you have? (D) Generally, what does your organization do? You can omit this if you want. Short answers like "school", "university", "hosting", "government", "research", "finance", etc are fine. (E) What do you use for config management if any (puppet, cfengine, bcfg2, home grown, proprietary apps) (F) What do you use for package management if any (yum directly, Satellite, etc) (G) What do you use for monitoring if any (nagios, proprietary apps, etc) (H) Are you using virtualization? If so, which (VMware, Xen, KVM, other)? Are you using Cobbler for virtualization deployment? (I) Feel free to share whatever else you want :) Basically I'm just curious as to whether system records are in wide use, how many people are using cobbler for repo management, and how many multi-cobbler server setups there are. I'm also a bit curious as to what other apps are in use at the same time, for potential integration/awareness reasons. This can help me better understand where to go in the future, and which corners of things are less relevant to the userbase. Please reply to me off-list. I'll try to report back some non-identifying aggregrate findings. Thanks! --Michael

15 years, 8 months

5
6
0 / 0

Second test email (ignore)

by Michael DeHaan

...

15 years, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

cobbler August 2008