I just packaged 2.4.0 beta6 up, which includes everything I mentioned earlier. I have been testing it quite a bit and it seems pretty solid as far as Ubuntu/ESXi support goes.
The above is part of the reason I keep delaying the release - I'm really trying to make this a solid release with as few new problems as possible while fixing a lot of the glaring issues that have existed for a while (sub-par ubuntu support was at the top of that list). There is one final bug that I think is a blocker for an official release ( https://github.com/cobbler/cobbler/issues/462) which is related to the new distro signatures support. Once I have that fixed, I will not do a beta 7 and will release 2.4.0 officially. So go test beta6 for now, and let me know if you find any problems - specifically with Ubuntu or ESXi 5+ builds. On Fri, May 24, 2013 at 11:02 AM, Bret Wortman <[email protected] > wrote: > Does this mean 2.4.0 is close? I've got a production shop that's waiting > with baited breath (mints close by) for the ability to use the > --available-as flag properly. I don't mean to put on pressure and am happy > to wait until it's production-ready. Just curious is all. > > > * > * > *Bret Wortman* > <http://damascusgrp.com/> > http://damascusgrp.com/ <http://bretwortman.com/> > http://about.me/wortmanbret > > > On Fri, May 24, 2013 at 11:31 AM, James Cammarata <[email protected]> wrote: > >> I've been making a lot of improvements in this area lately, so if this is >> a brand new installation of cobbler I'd recommend you grab the master >> branch via github and use that instead. Specifically, I've been fixing: >> >> * better apt repo support, to address the issue you mention above. >> Specifically now there are not separate repos for things like -security. >> Apt repos now have two new fields (apt_dists and apt_collections) so that >> you can mirror a lot more into a single repo. There are now also snippets >> to use these new repo configurations. >> * templated late/early command scripts support >> * debian network configuration (using the above late_command script >> support) >> * per-interface network gateways (since deb/ubuntu doesn't really have a >> gateway of last resort configuration like redhat does, at least not that >> I've found). >> >> Doing network configuration during the preseed is still a bit tricky, as >> preseed has a few hoops you need to jump through and doesn't always respect >> the d-i directives you specify. You'll probably want to continue to >> manually modify the preseed to use eth1 instead if that's the way you want >> to go. >> >> If you do decide to use the master branch, be sure to back up >> /etc/cobbler, /var/lib/cobbler and /var/www/cobbler to preserve anything >> you might have done so far (make install/make webtest can/will reset some >> files to the defaults). >> >> >> >> On Fri, May 24, 2013 at 9:24 AM, Rainer Duffner >> <[email protected]>wrote: >> >>> Hi, >>> >>> I've installed a brand-new cobbler 2.4b5 server on centos6-amd64. >>> I need to install a couple of Ubuntu12 servers with it. >>> I've never installed Ubuntu before, much less via cobbler - so I'd be >>> grateful for some advice. >>> >>> The idea is to: >>> - install via eth1 >>> - leave eth0 alone, or better, already give it the "final" >>> configuration, via cobbler >>> >>> This works on my CentOS and RedHat installs on my "old" cobbler 2.2.3 >>> server. >>> Obviously, it's not so simple with Ubuntu. >>> >>> >>> I've taken the sample.preseed file and adapted it minimally. >>> >>> One problem I have is: >>> - if I try to enter the default gateway in the cobbler-webgui >>> (Networking (Global)), I get problem that all leases are abandoned >>> because somehow the interface is "up" before it gets an IP via DHCP >>> - so, I try to set the default-gateway via a kickstart meta-parameter >>> - the install then continues, but after the reboot, eth0 is not >>> configured (neither is /etc/resolv.conf) >>> - is one then supposed to run some sort of post-install script that >>> "fixes" the network-configuration? >>> >>> I use >>> $SNIPPET('network_noncore_deb') >>> in the pressed/kickstart file, which reads: >>> >>> d-i netcfg/get_nameservers string $name_servers >>> d-i netcfg/get_ipaddress string $ip_address_eth0 >>> d-i netcfg/get_netmask string $netmask_eth0 >>> d-i netcfg/get_gateway string $ksgateway >>> d-i netcfg/confirm_static boolean true >>> >>> >>> Another issue is that the installer tries to fetch a lot of files that >>> just aren't in my cobbler-repo of the imported CD. >>> How can I import the rest of the repo so that the install doesn't pause >>> so often? >>> >>> A third issue is that with Ubuntu at least, if the dhcp-server does not >>> supply a nameserver, the installation will ask for one.... >>> So I supplied a non-existant one - but still, it bothers me a bit. >>> >>> >>> >>> >>> >>> Thanks in advance >>> _______________________________________________ >>> cobbler mailing list >>> [email protected] >>> https://lists.fedorahosted.org/mailman/listinfo/cobbler >>> >> >> >> _______________________________________________ >> cobbler mailing list >> [email protected] >> https://lists.fedorahosted.org/mailman/listinfo/cobbler >> >> > > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/cobbler > >
_______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
