Provision vm with many hard drives
by Thomas S Hatch
I am trying to provision vms with multiple virtual hard drives and to no
avail, I found some info online which lead me to believe it was possible,
but it didn't seem to work. How might I go about doing this? (if I can...)
-Thomas S Hatch
14 years, 10 months
Koan 111 Connection Refused errors
by William Sweat
Hello,
May be this has been addressed, but I still haven't found anything in the archives about this yet.
I've done a basic cobbler setup and whenever I run "koan -list-profiles -s someserver" I get the error:
[root@localhost ~]# koan --list-profiles -s someserver Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/koan/app.py", line 440, in get_profiles_xmlrpc
data = self.xmlrpc_server.get_profiles()
File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request
verbose=self.__verbose
File "/usr/lib64/python2.4/xmlrpclib.py", line 1129, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.4/xmlrpclib.py", line 1243, in send_content
connection.endheaders()
File "/usr/lib64/python2.4/httplib.py", line 804, in endheaders
self._send_output()
File "/usr/lib64/python2.4/httplib.py", line 685, in _send_output
self.send(msg)
File "/usr/lib64/python2.4/httplib.py", line 652, in send
self.connect()
File "/usr/lib64/python2.4/httplib.py", line 636, in connect
raise socket.error, msg
error: (111, 'Connection refused')
Could not communicate with someserver:25151
My cobbler server is not running any firewall and selinux is disabled (and have even removed it). I can telnet to port 111 with no problem, but when I telnet to 25151 I get a connection refused. So the server is accepting the connection, but something in the python code (or maybe apache) is kicking it out.
I've also added to the apache config "Listen ipaddress:25151" and instead get the error:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/koan/app.py", line 440, in get_profiles_xmlrpc
data = self.xmlrpc_server.get_profiles()
File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request
verbose=self.__verbose
File "/usr/lib64/python2.4/xmlrpclib.py", line 1137, in request
headers
ProtocolError: <ProtocolError for someserver:25151/RPC2: 404 Not Found> Could not communicate with someserver:25151
It seems like it should be a simple fix, but I haven't been able to find it. I've done this on CentOS 5.3, Fedora 10 and Fedora 11.
Thanks,
Will
Findology Interactive Media
14 years, 10 months
For those not following the cobbler-devel mailing list, an update of what's going on with 2.0
by Michael DeHaan
The development branch is coming along nicely thus far.
As I mentioned previously, 2.0 uses Django as the web framework. To
users, this means little, except that the URL to access cobbler
is now http://127.0.0.1/cobbler_web/, and cobbler web is now part of a
seperate optional package called, you guessed it, "cobbler-web".
We can now launch all sorts of background tasks via the web app, making
it possible to use the command line less (if you want). This means
that you can import from the web app (currently in progress), update
repos, do batch power management without the UI blocking (pending), and
also run sync, hardlink, and reposync commands. There is a task
engine that logs each of these actions seperately from the main logfile.
There are also new "filters", making it easy to be able to search any of
the lists by criteria (multiple kinds if neccessary) to only show what
you are looking for.
This is much shinier than the old search feature and I'm excited about it.
We have also introduced "AJAXy" alerts, which show when tasks start or
complete. If you are logged in and your colleague starts an import, you
will
see alerts of what is happening. (Currently it's not smart enough to
say /who/ is doing what, TBA). Mainly though this is intended to just
let you see
the status of those background tasks we mentioned earlier. We may
also include other DHTML/AJAX as time goes on... Cobbler Web is really
starting to look sharp, and I'm happy to see this happen. (Perhaps
we'll also get around to implementing expand/collapse features to hide
groups of fields?)
The next phase after polishing up the web app and making
nearly-everything you can do in the command line tool doable in Cobbler
Web will be "remoting"
the cobbler command line. This means that the cobbler command line
will speak to Cobblerd over XMLRPC instead of running locally. Why is
that? Well,
basically it's to avoid internal fun of trying to keep the command line
in sync with the web app. It will mean that even for very large
configurations of data
the command line will fly, faster than before... though for smaller
configurations it will basically be the same. It will also mean (in the
future) you will probably be able to configure remote cobbler servers
via the command line, if you really want.
(Just to keep things balanced, we have /cut/ some things from the plan
for 2.0 though -- most likely Network Objects, a feature to auto assign
IPs and network information to systems without rekeying a lot of network
info, will not make it. Hopefully in the next release. If someone
wants to come along and help with those, of course, that may help
accelerate things)
The development branch also has another major plus in that we've removed
a lot of code from Cobbler, so it is easier to hack on than ever -- any
contributor
will be able to add a new field to cobbler and not worry about having to
update the web application or command line code to make it usable. It
will just work
from the start. I hope this will open the door for even more exciting
contributions -- though we already have some great ones.
If you do want to contribute, or just keep up with what is going on, you
can do so by subscribing to cobbler-devel here:
https://fedorahosted.org/mailman/listinfo/cobbler-devel
Thanks for the continued interest!
--Michael
14 years, 10 months
core repository priority
by Léon Keijser
Hi,
I'm using yum-priorities in my cobbler-maintained systems in order to
have certain packages 'pinned' to a specific version. Now i noticed that
the distro repository (the 'core-0' repo) is set to priority=1 by
default.
Other than editing /var/www/cobbler/ks_mirror/config/<distr>.repo , is
there a better way of changing the priority?
--
Léon
14 years, 10 months
EPEL is getting a new update system (the same one Fedora uses)
by Michael DeHaan
What this means to use is (hopefully) when Fedora gets new packages the
main EPEL repo should not have to wait a much longer length of time
before getting those same RPMs in the repository.
You can read more about this here:
http://lewk.org/blog/bodhi-epel.html
This also means we can start using epel-testing as a true "testing"
repo, containing updates we would like folks to test, as opposed to just
containing the latest versions that EPEL stable was supposed to have but
haven't updated to yet.
I haven't updated the Wiki instructions about using EPEL testing yet --
I'm going to wait until we actually do a push under the new system,
though in general if you are interested in helping test, this is good
news, and if you are not, it's one less repo to configure and faster
package updates for you.
--Michael
14 years, 10 months
problems with the example on the wiki
by Eric Doutreleau
Hi
i m trying to follow what is written here
https://fedorahosted.org/cobbler/wiki/CobblerTriggers
the server is started on my server i can connect to it
but when i install the client the keys is not erases and i got the
following messages on my server
2009-07-10 17:17:12,657 - api - Exception value: 'cobbler trigger
failed: /var/lib/cobbler/triggers/install/post/clientkeys.py returns 1'
is there a simple way to debug triggers?
thanks in advance for any help
14 years, 10 months
Re: core repository priority
by Jasper Capel
>
> If this isn't possible (which i tend to assume by now) that's OK too.
> It
> just seems weird that cobbler defines this priority without me being
> able to change it through the cobbler cmdline tools.
>
Maybe we should have a priority attribute on distro objects too (atm this isn't possible), then, which would represent the yum priority of the installation tree.
Jasper
14 years, 10 months
Re: core repository priority
by Jasper Capel
----- "Léon Keijser" <keijser(a)stone-it.com> wrote:
> On Thu, 2009-07-09 at 17:33 -0400, Jasper Capel wrote:
> > This should not be an issue, if your reposync'ed repositories for
> RHEL / CentOS (base and updates) are also set to priority=1, you can
> set this on the repo object.
>
> I'm talking about when you do a `cobbler import`, cobbler will
> automatically create a repository for you
> in /var/www/cobbler/ks_mirror/<distro>. This repo doesn't show up in
> `cobbler repo list` so i can't edit it.
>
> And even if i would sync 'base' repositories, i'm still stuck with a
> 'distro repo' with priority=1.
>
Yes, but how is this a problem (please describe the impact this has for you)? :)
Jasper
14 years, 10 months
cobbler installs not being registered in cobbler since upgrading
by Anthony Giggins
I recently upgraded from 1.4.4 to 1.6.6 to resolve some issues
installing centos 5.3, since upgrading I noticed that systems are not
being registered into cobbler.
I checked that I do have
$SNIPPET('cobbler_register') in my kickstarts
Can I can manually register them after they are installed
cobbler-register --server=x.x.x.x --profile=CentOS-5.3-x86_64
--fqdn=server.domain.net.au
I tried to enable anamon in the settings, in my kickstarts and by
starting the anamon service but I don't see to get any output.....
Any pointers on what to look for would be great.
Cheers,
Anthony
14 years, 10 months
Error with RHEL-5.3
by Léon Keijser
Hi,
I've imported a RHEL 5.3 (x86_64) dvd succesfully, created a profile
that has the RHEL's profile as parent and added a system for it. Now
when i try to roll out the system, i get an error from anaconda saying
there's something wrong with the repository:
"Unable to read package metadata. This may be due to a missing repodata
directory. Please ensure that your install tree has been correctly
generated. failure: repodata/primary/xml.gz from
anaconda-base-200901061732.x86_64: [Errno 256] No more mirrors to try."
I've verified that the directory:
/var/www/cobbler/ks_mirror/RHEL53-x86_64/
exists and that there are 4 repositories created:
Server, VT, Cluster and ClusterStorage
I even updated these repositories manually. This all didn't do the
trick. Something i forgot to do?
# rpm -q cobbler
cobbler-1.6.6-1.fc10.x86_64
# rpm -q koan
koan-1.6.6-1.fc10.noarch
regards,
--
Léon
14 years, 10 months
