Jesus M. Rodriguez wrote:
2009/5/4 Miroslav Suchý <[email protected]>:
Jesus M. Rodriguez wrote:
upgrade monitoring engine?
* let's not UPGRADE it, let's integrate with something else. --
jmrodri
Can you elaborate on this?
I'm probably just repeating what was said, but when I read upgrade
I see replacing the current engine but still have a tight coupling, i.e.
the current monitoring has sql in our schema files, code in our webapp, etc.
I'd rather have the monitoring engine live outside of Spacewalk, be
a separate project and the integration being probably UI level.
Does this make it any clearer? or did I just make it muddier :)
You made it clearer :)
I completely agree with you.
IPv6
That's fair that we can lead the way, but a lot of the code that doesn't work
with IPv6 isn't even ours. So this is something we can only do part way and then
wait for the rest of the libraries to catch up.
Can be true. But that make it even more urgent. We should then check
which third-party parts are not IPv6 enabled and file BZ in upstream.
And we should done it yesterday :)
download packages using torrent protocol
* Not going to happen. What does this mean? yum / up2date can't use
torrents. I don't think this feature makes sense. -- jmrodri
I thought about something similar to:
http://wiki.debian.org/DebTorrent
What does the torrent really buy us though? For isos I completely
understand how it could work. And even for just packages in a mirror,
but how will it help update a system registered to Spacewalk?
Faster download? Offloading Spacewalk?
But agree that I have rather iso download and sat-sync/rhnpush on mind.
--
Miroslav Suchy
Red Hat Satellite Engineering
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
