Re: [Spacewalk-devel] Bug 207147 - system users are created with uids/gids in user range
Cliff wrote: Dave, or Mirek or someone :) Did we address this within past Spacewalk released? https://bugzilla.redhat.com/show_bug.cgi?id=207147 Bug 207147 - system users are created with uids/gids in user range Yes, we did. Not sure if we could just close it out or not. Closed as duplicate. Thanks, Cliff You are welcome. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Looking for Fedora Package Review
I'm very close to get Spacewalk client tools into Fedora, but I will need to pass review of rhnsd. If somebody is willing to make this review, I will be very happy: https://bugzilla.redhat.com/show_bug.cgi?id=524558 Note, that there is more reviews waiting: https://bugzilla.redhat.com/show_bug.cgi?id=494292 https://bugzilla.redhat.com/show_bug.cgi?id=491331 https://bugzilla.redhat.com/show_bug.cgi?id=491088 But the rhnsd is priority now. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] SHA256 Support - proposal for db schema and code change
We (Jan, Michal and me) did some brainstorming about SHA-256 support and we come with following result: Table: rhnChecksumType: id, label, description, created, modified (we already have this table) rhnContentChecksum: id, checksum_type_id, checksum (PK is id) and in tables rhnPackage, rhnPackageFile, rhnErrataFile... change md5sum to content_checksum_id, which will be FK to rhnContentChecksum. This is change from current logic in sha256-support, where is schema with cardinality 1:N, to cardinality 1:1. We believed (and our faith is supported by rpm maintainers) that there will be never need to have related two or more checksum for one package or one file from one package. That's why we lower the cardinality. We find that even if we mix packages with different checksum (i.e. md5 and sha256) in one repo, you can mix in repomd different checksums and yum will (should) understand it. Benefits of this change is, that it is more general. I.e. if you have tar/rpm package which contains other rpm, which is the same as some other in rhnPackage, we can easily detect it. BTW: the commits in sha256-support have been impossible to merge or rebase in master, so I half cherry-picked and half rewrite to new branch sha256-support2. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] Fix tsdb to install the init script properly
Joshua Roys wrote:
Hello all,
Presently we end up with a directory with the init script inside it:
$ rpm -ql tsdb
/etc/rc.d/init.d/tsdb_local_queue
/etc/rc.d/init.d/tsdb_local_queue/init_script
...
Patch attached.
I do not like it.
Neither that bug, nor your patch :)
Yes what you find, is definitely not correct and bug.
But I have few question:
a) why you put there?:
+%if 0%{!?_initddir:1}
+%define _initddir %{_sysconfdir}/rc.d/init.d
+%endif
Is some platform where _initddir is not defined?
b) Why not instead of:
+mkdir -p $RPM_BUILD_ROOT%{_initddir}
...
-install -d $RPM_BUILD_ROOT%{init_script}
install -m 755 LocalQueue/init_script $RPM_BUILD_ROOT%{init_script}
Simplier:
-install -d $RPM_BUILD_ROOT%{init_script}
-install -m 755 LocalQueue/init_script $RPM_BUILD_ROOT%{init_script}
+install -D -m 755 LocalQueue/init_script $RPM_BUILD_ROOT%{init_script}
c) I agree with:
-%define init_script %{_sysconfdir}/rc.d/init.d/tsdb_local_queue
+%define init_script %{_initddir}/tsdb_local_queue
Unless you have some rationale for a), I will put there b) with those
change and c) tomorrow. Of course I will be happier if you create that
new patch :)
--
Miroslav Suchy
Red Hat Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] Fix tsdb to install the init script properly
Joshua Roys wrote:
On 10/05/2009 12:07 PM, Miroslav Suchý wrote:
a) why you put there?:
+%if 0%{!?_initddir:1}
+%define _initddir %{_sysconfdir}/rc.d/init.d
+%endif
Is some platform where _initddir is not defined?
Yep - _initrddir is defined most places - but it was improperly named.
Recent Fedora rpm macros have moved to _initddir, although they still
have _initrddir.
_initrddir is alias to _initddir, so it seems to me that _initddir is
still primary.
I would rather do something about this only when Fedora in rawhide
delete _initddir and make status quo till then.
But I will not persuade it.
For now I have left a) in - unless the incorrect-but-more-well-known
_initrddir should be used. Or we could just leave it as
%{_sysconfdir}/rc.d/init.d.
Commited as 0c93b6054f5aeb581e3eb2c1a6d93660648ef8f5
Thanks!
Thanks too.
--
Miroslav Suchy
Red Hat Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PATCH: editarea clean up
Colin Coe wrote: Hi all A very long time ago I sent in some patches to make spacewalk use editarea. At the time I was asked to get editarea into Fedora/EPEL and to maintain the package. Well, it took a while but the editarea RPM is now in Fedora/EPEL so the attached patches are to remove the 'embedded' editarea and make spacewalk depend on the editarea RPM. Comments/criticisms welcome. Seems good to me. Applied. Thx. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCHes] scheduled config file compare, diff selinux contexts, ...
Joshua Roys wrote: Hello all, In the hope of someone else finding these useful, here are some patches we've been kicking around for a while and seem to work as expected. Joshua Roys (3): Add task to schedule config file comparisons Set CompareConfigFilesTask to run at 11pm Show number of differing config files in overview Joshua Roys (1): Diff SELinux contexts Joshua Roys (4): Fix system comparison file/dir/symlink counts Plug fd leak Fix two more fd leaks Make debugging osa* network/jabber issues easier I reviewed and commit to git client side patches: 0001-Diff-SELinux-contexts.patch 0004-Make-debugging-osa-network-jabber-issues-easier.patch Can someone check the rest? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] non-Latin characters in domain names
FYI: http://www.icann.org/en/announcements/announcement-30oct09-en.htm From article: "The coming introduction of non-Latin characters represents the biggest technical change to the Internet since it was created four decades ago," said ICANN chairman Peter Dengate Thrush. "Right now Internet address endings are limited to Latin characters – A to Z. But the Fast Track Process is the first step in bringing the 100,000 characters of the languages of the world online for domain names." Do we know what that means for Spacewalk? Will handle it. Can somebody test it? According to my information Fedora 12 should be able to handle such domains. Older Fedoras and RHELs will probably not support it. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] non-Latin characters in domain names
Cliff wrote: Miroslav Suchý wrote: FYI: http://www.icann.org/en/announcements/announcement-30oct09-en.htm From article: "The coming introduction of non-Latin characters represents the biggest technical change to the Internet since it was created four decades ago," said ICANN chairman Peter Dengate Thrush. "Right now Internet address endings are limited to Latin characters – A to Z. But the Fast Track Process is the first step in bringing the 100,000 characters of the languages of the world online for domain names." Do we know what that means for Spacewalk? Will handle it. Can somebody test it? According to my information Fedora 12 should be able to handle such domains. Older Fedoras and RHELs will probably not support it. Interesting - are you able to create a wiki to start capturing thoughts on this? Created (with copy of parts of this email): https://fedorahosted.org/spacewalk/wiki/Features/NonLatinCharacters Linked from Brainbox. - Is there a Fedora page tracking this project for them? AFAIK no. - server Hostname uses this, thus what you type in URL - will tomcat, apache etc in F12 support them? - will our java, perl and python stacks be nice to the request or filter out the chars and end up with a broken url - kickstarts use urls - Proxy server hostname - do things work - client tools communicating to Satellite - rhnpush, config etc - rhel/fedora client tools - yum-rhn-plugin, rhn_check etc I have no idea. We will have to test it and we will see -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Nightly builds for Fedora 12
Nightly builds for Fedora 12 are available at: http://miroslav.suchy.cz/spacewalk/nightly-candidate-f12/ For Red Hat employees - syncing to our internal well-known mirrors right now. Enjoy -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] EOL of nightly repo for F10
Nightly repo for F10 is not updated any more. I will leave it there for few days and will remove it soon. Probably next week. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Split of nightly repo to server and client parts
Nightly repo has been split to server and client parts. Server side should not contain any client packages now. If does, please report. All client packages has been put into new repo: http://miroslav.suchy.cz/spacewalk/nightly-candidate-client/ Server packages are in that old nightly repo. This has been done, to enable installation of Spacewalk on RHEL and not overwrite RHN packages on RHEL and lost support on those packages. If you want to install client packages from Spacewalk you can (if you enable that new repo), but now you are not forced to do it. Hopefully next release of spacewalk will be released in such two repos as well. Client parts in one and Server and Proxy in second. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] new rel-eng script
I created new script rel-eng/last-package-tag, which tell you when was the last time tagged package. Since nightly script pick up all tags and build it, we can safely assume (for most packages) that is was time when the package was built. It it just quick script, so it has to be run as: rel-eng/last-package-tag you can not do: cd rel-eng; ./last-package-tag it will not work. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Debian support - arch of package problem
Lukas Durfina wrote:
I have problem with uploading info about packages to spacewalk. Spacewalk
accepts only some types of architectures, problem is accepting
architecture "all",
because spacewalk knows only equivalent "noarch".
I see 2 possible solutions:
- change type of architecture from "all" to "noarch" before uploading
- patch spacewalk to accept architecture "all"
Can you help me choose the better solution?
Change of all to noarch will be very easy, but I think it will bite us
later.
Patching spacewalk to accept architecture of all is IMO propper way.
I gave it 5 minutes to study and it seems there will be no need to
change the code (at least backend) and it should be enough to only
insert few rows to some tables.
According to my findings it should be enough to insert new rows into
rhnChannelPackageArchCompat.sql
new row to
rhnPackageArch
with reference to lookup_arch_type('rpm'), which means new row in
rhnArchType
new row to:
rhnServerPackageArchCompat
And if we gave debian systems new server_arch, like solaris have we we
only enable to use all architecture for debian systems and not for rpm
systems.
I would vote for i386-debian-linux and amd64-debian-linux and so on.
--
Miroslav Suchy
Red Hat Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] release notes draft
Spacewalk 0.7 release is approaching, we have still a lot of thing to test and to prepare... I went through bugzillas and through all commits till 0.6 release and I wrote draft of release notes: - new script "spacewalk-report" allows you to create reports with output to CSV file https://fedorahosted.org/spacewalk/wiki/Features/ScriptBasedReporting - pages with erratas has column with links to CVE description, erratas can be filtered by its type https://fedorahosted.org/spacewalk/wiki/Features/WebuiErrataAndCvesEnhancements - Spacewalk can be installed on Fedora 12 - top level package spacewalk do not exists any more. It has been split into spacewalk-oracle and spacewalk-postgresql, which depends on oracle or postgresql library. - Spacewalk now track date and time of package installation - config channels now can handle symlinks - support for WebUI based KVM guest management & provisioning - new script "monitoring-data-cleanup" allows you to delete old monitoring data - new script "NOCpulse-ini" allows you edit NOCpulse.ini configuration file - base client packages are now in Fedora (i.e. you are now able to register Fedora machine to Spacewalk, without setting up additional repository) - Spacewalk repositories has been split to server and client parts - client tools now can report diff in selinux context - satellite-sync improvements and of course many bugfixes If I missed some important feature and/or bugfix, let me know. Contributors from community: - Colin Coe - David Nutter - Joshua Roys - Lukáš Ďurfina If I missed your name, let me know. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] Fix creating new config managed symlinks
Joshua Roys wrote: Hello, I discovered that using the "disabled" property causes elements to not be sent when the form submits. The proper property is "readonly." Applied as commit 7936cacc743946a1d18f1926f938e69f9ce4fe3f Thanks, Thanks too. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] release notes draft
Andy Speagle wrote: On Tue, 2009-12-01 at 03:47 -0600, Miroslav Suchý wrote: If I missed some important feature and/or bugfix, let me know. What API changes are being made for 0.7? Good, point. But only change is that system.listPackages now returns additionaly field "installtime". But yeah, I will include it in release notes. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Donations?
Colin Coe wrote: Hi all I'd like to donate the attached script to the community. The functions getSysID() and getServer() are quite ugly. I prefer to use iniparse module. But otherwise it looks good. I will commit it soon and then try to rewrite it to use iniparse. And of course - Thanks! -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] spacewalk 0.7 branched
I branched master and created remote branch origin/SPACEWALK-0.7 Whatever you commit to master will go to Spacewalk 0.8. If you want to put something to 0.7, then you have to put it into master, cherrypick it to origin/SPACEWALK-0.7 and notify me. New bugs against Spacewalk block against tracking bug space08. I will move all NEW, ASSIGNED bug from space07 to space08. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Donations?
Colin Coe wrote: I've only been coding in Python for a week or two now so I didn't know iniparse existed. Having looked though, it seems iniparse doesn't exist on RHEL4 (please correct me if I'm wrong). RHEL4 is one of the Indeed. I will leave it as is then... platforms that this script is needed for. Is there a cleaner way to get the system ID and Satellite/Spacewalk server that will work on RHEL4? import config cfg = config.initUp2dateConfig() #this will get you systemid path cfg['systemIdPath'] #this will give you serverURL from config cfg['serverURL'] You may as wall make successor of up2date_client/rhncli.py which do a lot of things for you. You may check client/rhel/rhn-client-tools where you find a lot of useful libraries. Also you may want to use OptionParser rather then getopt. Check: client/rhel/rhn-client-tools/src/bin/spacewalk-channel.py for example Also, can you advise in which RPM this script is likely to be put? I ask because it is designed to work with nodes not using Spacewalk or Satellite as well as those that are using Spacewalk or Satellite servers. spacewalk-utils Commited as 5a787bbfcdca363df858fbcfe10762e59fb4a175 Can I ask you to write man page for this script as well? You can take utils/*.sgml as example. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] (no subject)
sadas sadas wrote: Hi, First of all, it is better if you write subject next time. I want to write a php script that start/stop centos servers connected to Spacewalk server. Where in oracle database php script can edit so when I use my php to start/stop centos server and spacewalk to execute my command and to stop/start the server? You do not want to use db directly. You really do not want it. It is much better to use API instead. Documentation of API is on: https://url.of.your.spacewalk/rhn/apidoc/ You may want to use API call system.scheduleScriptRun and call it with script #!/bin/sh /usr/bin/halt Dunno how do you want to start it. WakeOnLan? But if you are talking about guest. There is already API for that: system.scheduleGuestAction it can: 'start', 'suspend', 'resume', 'restart', 'shutdown' virtual systems. If this API call does not suite your needs, it is much better instead custom PHP scripting, create new API call in java and contribute it back to Spacewalk project so others can benefit from your work too. PHP script will use only few people (if any). -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] MySQL support for Spacewalk
Miroslav Suchý wrote: I pleased to announce you that Matej Hašuľ started working on his Master Thesis which has goal to add support for MySQL as database backend for Spacewalk. We will track his progress on page: https://fedorahosted.org/spacewalk/wiki/MySQL_support He can work for 3 semesters on his thesis. Therefore the output of this work is targeted on summer 2010. He is supposed to watch our work on PostgreSQL and build upon this work. If you find this project interesting, you can send your patches to Matej for review. FYI: Matej canceled his thesis and choosed different topic. -- Miroslav Suchy Red Hat Satellite Engineering Cloud Computing and Integrated Solution Dept. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] need to add python-ethtool to 0.7 client repo
Justin Sherrill wrote: rhn-client-tools requires python-ethtool yet it's not in the client repo for RHEL, only in the full 0.7 server repo. What needs to be done to get this package added to the client repo? For 0.7 I will copy it there manualy. For future releases and nightly we should file rel-eng ticket. I will take care of that. -- Miroslav Suchy Red Hat Satellite Engineering Cloud Computing and Integrated Solution Dept. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] need to add python-ethtool to 0.7 client repo
Miroslav Suchý wrote: Justin Sherrill wrote: rhn-client-tools requires python-ethtool yet it's not in the client repo for RHEL, only in the full 0.7 server repo. What needs to be done to get this package added to the client repo? For 0.7 I will copy it there manualy. Done. -- Miroslav Suchy Red Hat Satellite Engineering Cloud Computing and Integrated Solution Dept. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] Add --interval option to monitoring-data-cleanup for staged deletion of monitoring data
David Nutter wrote: This patch adds an option --interval to the monitoring-data-cleanup script. --interval accepts a date delta like "1 week" and if set Applied with only small change in man page (missing quotes in param in example). Thx. -- Miroslav Suchy Red Hat Satellite Engineering Cloud Computing and Integrated Solution Dept. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Why are Spacewalk packages removed from CentOS?
Hi, severals users of Spacewalk [1] reported that Spacewalk client tools are removed [2] from CentOS (they are present in RHEL). It's about packages: rhn-check rhn-client-tools rhnlib rhnsd rhn-setup rhn-setup-gnome yum-rhn-plugin I dig up in history [3] and find that the reason was probably reference to rhn.redhat.com. Since current Spacewalk (default) configuration should not hit rhn.redhat.com I'm curious if those packages can be put back to CentOS? Or is some other reason behind removal of those packages? 1: https://fedorahosted.org/spacewalk/ 2: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.4#head-6dfcd9ddca9da9913268c2192ff83c5207442aa8 3: https://www.redhat.com/archives/spacewalk-devel/2008-July/msg00042.html -- Miroslav Suchy Red Hat Satellite Engineering Cloud Computing and Integrated Solution Dept. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] space09 created
I created space09 tracking bug. https://bugzilla.redhat.com/show_bug.cgi?id=559281 I moved all currently reported, but untracked bugs (59 bugs) under this tracker. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Script for pushing packages to Fedora
I created script rel-eng/push-packages-to-fedora.sh This script for every package which passed Fedora review do: - create srpm from Spacewalk git checkout - update your Fedora dist-cvs checkout of that package - if in Fedora is different version then: - import new srpm to Fedora dist-cvs for devel branch - build that package in Koji It is executed (on my machine) as: ./push-package-to-fedora.sh ~/fedora/cvs/ ~/rhn/spacewalk.pub/ It do everything automaticaly, but review of spec changes before commiting to dist-cvs. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Script for pushing packages to Fedora
On 02/11/2010 07:00 PM, Devan Goodwin wrote: FYI I think you can do most of this with tito build --release if you'd like. All that syncing with CVS and building with Koji was done for internal builds, and while untested with Fedora, I think it's exactly the same. (minimal changes could be required but it should be close) Let me know if you'd like to use it and have any issues. No, thanks. Tito is good for building one package from git. But it could not do version compare, review of spec... So I will rather stick just with this simple wrapper around make verrel ./common/cvs-import.sh make build which are maintained by Fedora guys for free. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Spacewalk Answer file
On 02/18/2010 06:41 PM, Travis Camechis wrote: Is there any documentation on the wiki about the possible values for a spacewalk answer file? I haven't seen any and if there is can some one point me to it and if not it might not be bad idea to put up on the wiki somewhere. Answer file for Spacewalk proxy is documented in: man configure-proxy.sh But if you meant answear file for spacewalk-setup (i.e. answer file for Spacewalk server), then I have to agree. No documentation at all. Feel free to create it. Either as wiki page or patch to man page of spacewalk-setup. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk-monitoring-selinux dependency problem
On 03/04/2010 02:02 PM, Marcus Moeller wrote: Hi all. I am setting up a Spacewalk proxy on a SELinux aware system and struggled during package install as spacewalk-monitoring-selinux seems to requires oracle-instantclient-selinux which then requires oracle-instantclient itself. Which is correct since spacewalk-proxy-monitoring (that one should requires spacewalk-monitoring-selinux) require oracle-instantclient too. It is becouse one of the probes set are Oracle probes. So what is your problem? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] New repository for Debian packages
Lukas has in his own repository build only 32bit build of debian packages. So I created new subproject in OpenSuse Build Service and there are two new repositories: For Debian 5.0: http://download.opensuse.org/repositories/home:/xsuchy:/debian-spacewalk/Debian_5.0/ For Ubuntu 9.10: http://download.opensuse.org/repositories/home:/xsuchy:/debian-spacewalk/xUbuntu_9.10/ The packages are available for both i586 and amd64 architecture. Lukas kindly fixed all errors with build services, so all packages are now built. Current list is: jabberpy osad python-ethtool rhn-client-tools rhn-functions rhn-setup rhncfg rhnlib rhnsd Note that all packages are still higly experimental and you are only able to register debian machine to Spacewalk and nothing more righ now. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Hardware info - Storage
When you click on system detail and Hardware tab - there is information about storage devices. Currently there is columns: Description Bus Device Physical First three are populated, but column Physical is always empty. According the code, there is value of scsi.host for scsi devices. The question is: does it make some sense? Should we remove that column. Rename it? Put there some information which has sense? Leave it as is? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Hardware info - detached devices
When we send information to rhnParent from client one of the attribute is "detached" and it is defined as: dev['detached'] = 0 Nothing more. And in server we have whole column DETACHED in table RHNDEVICE, which store this interesting zero. Q1: What is detached? Or what is should be? This column have been there from first day of this table without any description what it should be. Detachable device? Q2: Should I try to put there sometime something other then zero? Or should I wipe it from earth? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] rhn-client-tools: dependency on hal is gone
I just tagged rhn-client-tools-0.9.5-1, which no longer require hal (only F-13 and newer). I appreciate any testing. Known problems are: not properly detected: tape, floppy and printers I however find several problems or weird thing, which I would like to share and hear your comments. Only physical block devices are reported. I can report logical devices without problem (e.g. LVM, partitions...). Do we want it? Keyboards and mouse are not listed in HW tabs. It is propperly sent, but not displayed. The same behaviour was with old code. Is it bug or feature? Old rhn-client-tools sent from function dictionary where one key/value is: 'system.formfactor': 'unknown' In new release I do not send this. IMO is no way how to fetch this value and I see no sense for this data. Any objections? Storage devices are now reported as "block" bus, which is change from previous release where was reported as "pci". Description of device is sent in format vendor|dev_description. Should we split it? BTW Section of storage devices do not strip that | prefix from description. So in webUI it is shown as (ATA|ST3500630NS). Bug or feature? I suppose this is bug. If I classify network device as NETWORK it will not appear in HW tab. I had to set it as OTHER. Any objection if I file it as bug? For some usb devices (controlers and hubs) are now correctly listed bus type - "pci" instead of "MISC". -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Hardware info - detached devices
On 03/18/2010 11:04 AM, Miroslav Suchý wrote: Q1: What is detached? Or what is should be? This column have been there from first day of this table without any description what it should be. Detachable device? detached: This is for devices that the user wants to leave as configured, even though they may not be probed. Cardbus cards, if detected, are automatically marked as this; a user may want to mark this themselves for some USB devices. Q2: Should I try to put there sometime something other then zero? Or should I wipe it from earth? Since udev only returns attached devices we should set it always to 0. But old klients (probably which use kudzu) still use it. Keeping it alive. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] removing tito from spacewalk git
On 03/26/2010 10:26 PM, Justin Sherrill wrote: Hi, Is there any reason why we shouldn't remove tito from spacewalk git? It's maintained as an upstream project and can be installed via the fedora repos or epel. If no objects i'm gonna remove him! +-0 It is schizophrenic to have it in repo when it live its own live in upstream. But on the other hand we sometimes need to customize tito (e.g commit e443533d5aa9f98d01f3152bd5ebaac3ee0f2e52) and when we do such change we need to propagate it to other team members quite fast. I'm not sure writing emails "heya download new version of tito from ustream" is the right thing. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Help with Debian support
On 04/09/2010 10:52 AM, Lukas Durfina wrote: Hi, I am working on Debian support for Spacewalk. And I would appreciate some help. First of all it is necessary to aplly this upgrade on database http://miroslav.suchy.cz/spacewalk/git-repo/schema/spacewalk/upgrade/spacewalk-schema-0.8-to-spacewalk-schema-0.9/001-debian-support.sql or use night build. We need only this schema change? No need to change somthing in satellite code? I though you had some patches for backend as well. Just wondering... -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Help with Debian support
On 04/09/2010 02:01 PM, Lukas Durfina wrote: On Fri, 09 Apr 2010 12:27:19 +0200, Miroslav Suchý wrote: We need only this schema change? No need to change somthing in satellite code? I though you had some patches for backend as well. Just wondering... Patches for satelitte(spacewalk) code will be for pushing packages. I will prepare that patches too, but it needs deb package for rhnpush, which is not ready yet. Then it is hard to provide you the response, since I could not reproduce it. I'm eager to see even not final patch. I work with not finished code all the time :) -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [Spacewalk-list] red hat channels
On 04/10/2010 12:00 AM, rob morrien wrote: rob morrien napsal(a): Is there a way that i can sync the redhat channels from the satellite server to my spacewalk server. http://www.redhat.com/pdf/ISS_Best_Practices_Whitepaper.pdf Miroslav Suchy Short question: is this also working for satellite server 5.1 No. You need at least RHN Satellite 5.3 (or Spacewalk 0.5) -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Help with Debian support
On 04/10/2010 01:17 PM, Lukas Durfina wrote: On Fri, 09 Apr 2010 15:19:03 +0200, Miroslav Suchý wrote: Then it is hard to provide you the response, since I could not reproduce it. I'm eager to see even not final patch. I work with not finished code all the time :) I found a problem. The changes in db schema were not completed. Shame on me... Now registering and also subscribing into the software channels is ok. Can someone review and apply an attached patch? I will send patch for uploading deb packages soon. Applied. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] fedora Support
On 04/16/2010 05:16 PM, Dennis Gilmore wrote: Hey All, We should drop support for Fedora 11 and add Fedora 13. Fedora 11 will be EOL in ~2 months, -1, when it will eol in 2 months, why drop it now. We will delete it when it will die, but why do it sooner? to that end ive started building 0.9 for F-13 most of it is built. -1 I do not like the fact that packages for F-13 will be built on some not-yet-released packages. Unless we will distinguished it by some dist tag, which will be overwriten by normal dist tag and we rebuild all packages after release of F-13. I do not want to build our packages on top of rawhide or beta. If it some packages are part of Fedora, then good. But most of our packages are not there. Yet. there are some supporting deps that need building. Do you mind to share with us? Which deps? I would like to make the switch to only build for EL-5 F-12 and F-13 but wante dto run it by everyone first. Commiting this changes 3 hours after sending this proposal is not enough. IMO. I reverted this commit in master. I leave fate of you commit in SPACEWALK-1.0 branch in hand of release nanny and on the opinion of others. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Help with Debian support
On 04/10/2010 09:27 PM, Lukas Durfina wrote: So, here is the patch for the backend code. I have several comments: backend/server/importlib/debPackage.py: Why is tagMap and _already_mapped attributes of class? Why not use attributes of instance and use regular constructor? Then we will not need createPackage function. backend/server/importlib/importLib.py I really do not like, that header will be sometimes array and sometime object. Can we do something with that? backend/server/rhnPackageUpload.py I really do not like the process try/load deb/except/load rpm. I know we already do it for mpm, but if we can decide which object to use using file extension, then it will be much better. But this can be done later using another commit. backend/spacewalk/common/deb_handling/* Can you say from where it was picked up? E.g from which debian package, or where is the original upstream. So we can later sync. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] fedora Support
On 04/19/2010 03:43 PM, Dennis Gilmore wrote: > We have in the past, and it wont get support for most of the life of > 1.0 We done it *once* in past. But not always. For F-12 we built packages month after release. For F-11 month before release. For F-10 three month after release And even if we did it only once ... I do not think it was wise movement. And F-11 will be supported for more then 2 months, but we are releasing Spacewalk now. Commiting this changes 3 hours after sending this proposal is not enough. IMO. I reverted this commit in master. I leave fate of you commit in SPACEWALK-1.0 branch in hand of release nanny and on the opinion of others. I find that to be unacceptable. Adding back F-11 would be ok but just reverting is downright rude. This comes to two thing: a) do we want to build F-13 packages on beta? Unless we have some tool for rebuild after F-13, I'm strongly against it. It can broke functionality later if not rebuilt. We can discuss it, but until majority agree, I think we should not add it. Or unless it is released. b) do we want to remove support of F-11, when it has still 1/6 of its life remaining? Again we can discuss it, but removing it now would cut off those who are still using F-11. So I decided that without prior discussion I want to have F-13 removed and F-11 added. Which leads to complete revert of your commit. Do not take it personally. If others will disagree with me, I will be first who will revert my own revert. I would like to ask others for their opinion. And there was one other reason, if you look on Koji: http://koji.rhndev.redhat.com/koji/tasks?state=failed&view=tree&method=all&order=-completion_time Your step has as consequence completely overfilled koji with failing tasks. Doing such change on Friday is really not good thing. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] fedora Support
On 04/19/2010 11:14 PM, Dennis Gilmore wrote: None of those failures were any of my doing. it looks like Shannon does not have the proper permissions to do a build from SRPM. I just now fixed his permissions. Shannon just push it to next page. Look on failed task during weekend. Currently: http://koji.rhndev.redhat.com/koji/tasks?start=100&state=failed&view=tree&method=all&order=-completion_time -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Help with Debian support
On 04/20/2010 10:32 AM, Lukas Durfina wrote: On Mon, 19 Apr 2010 13:20:02 +0200, Miroslav Suchý wrote: On 04/10/2010 09:27 PM, Lukas Durfina wrote: So, here is the patch for the backend code. I have several comments: backend/server/importlib/debPackage.py: Why is tagMap and _already_mapped attributes of class? Why not use attributes of instance and use regular constructor? Then we will not need createPackage function. Just curious question: What is wrong with that way? I have used it, because all other packages classes (rpmPackage, rpmBinaryPackage, mpmBinaryPackage) are implemented in that style. With attributes of class you can do: #!/usr/bin/python class A: foo = None a = A() b = A() A.foo = 1 print b.foo # will print 1 Which can be sometime helpfull, but usually you do not want to do this as this can lead to accidental bug. The fact that we have something dane in past is not excuse. Our code is sometimes worth of rewrite :) -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] /var/lib/nocpulse/libexec/status
I'm moving /var/lib/nocpulse/libexec/status to /usr/bin/rhn-probe-status It is probably nobody using. But if you do, I want to inform you about this change. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] read_cpuinfo in the client code
On 04/22/2010 08:30 AM, Jan Pazdziora wrote: It looks like we have the same or very similar loop for most platforms. Maybe it would make sense to have the top level while and parsing of the /proc/cpuinfo to be common code, and only do the ifs when reading in the specific fields. Patches welcome, if anyone wants to give it a try. Patch commited as 95dd86629dfc2d8a6ef67846cb446f4c56c2289d Thank for noticing such ugliness in our code. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Pushed first commit
On 04/23/2010 02:14 PM, Colin Coe wrote: Hmm, I see it in 'gitk' and 'git log' shows: Do: git pull --rebase gitk --all notice that remote/master is few comits behind master, which is only your local commit git push check gitk again and notice that master and remote/master point to the same commit -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] miroslav.suchy.cz outage
On 04/26/2010 08:09 AM, Miroslav Suchy wrote: I will have to switch off machine miroslav.suchy.cz for aprox. one hour this morning. So you might expirience outage of nightly repo. Done. Website should be online. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk-postgresql
On 04/25/2010 04:00 AM, Travis Camechis wrote: Does anyone know why the spacewalk-postgresql install requires oracle-instant-client? due Monitoring probes: http://www.mail-archive.com/spacewalk-l...@redhat.com/msg04074.html -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Moving postgres support forward
On 04/29/2010 11:57 PM, James Hogarth wrote: Hi all, Great to see the 1.0 milestone reached. Friday afternoons in my team we assign to 'personal projects' and I've been thinking about trying to help with the postgres side of things during this time I have 'free'. The pgsql head in git hasn't had a commit in 9 months... is this even valid anymore? Well... So what is status of PostgreSQL in Spacewalk? Yes, no one touched it for 9 months. We had other priorities. But anyway, what we have now: We partially convert our initial schema. There is some tool called Chameleon: https://fedorahosted.org/chameleon which was written by Jeff Ortel specially for Spacewalk. Chameleon can translate Oracle schema to PostgreSQL schema. But it is far from perfect. First - it is completely undocumented. Second - it can not translate everything. Just look at schema/spacewalk/postgres/manual/* how many things are converted manually. And maintaing two sets of SQLs schemas is no way. This will not work. So we need something that will be able to translate *everything*. If it will be enhanced Chameleon or we start from scratch (e.g. by writing rules for good old sed) - that is question... And we just focused on initial schema for now. No one looked on SQL queries in our code. How do we (automatically) translate it to postgresql? Some queries are separated from code (hbm.xml) some are still in middle of the code. How we will handle this? What is the best way? How this all affect speed of code? Then there are some infrastructural changes which should be probably done prior finishing Pg support. A lot of question. We should decide some design questions, before we start coding. If you really want to help. You can take a look on Chameleon and investigate if it is worth of continuing in it and write some documentation for it. Or you can start with some simple Spacewalk bugs and first get overview of Spacewalk internals, before you start with more complex task, which Pg support is for sure. Or you can do some review of Spacewalk packages for Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=F-Spacewalk Or anything else. But jumping directly on Pg support as you first contribution is probably not good idea. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] dependency issues in the spacewalk repo
On 04/30/2010 10:07 AM, Rudolf Kastl wrote: Heyyas, actually as stated on irc various times already the spacewalk-postgresql package still pulls in proprietary oracle dependencys: due Monitoring probes: http://www.mail-archive.com/spacewalk-l...@redhat.com/msg04074.html - Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Remove jabberd from our repos?
On 04/30/2010 01:46 PM, Marcus Moeller wrote: You may want to talk to Miroslav about that. Huh? Why me? I'm ok with removing jabberd from our repo, if it is in fedora and epel. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Fwd: Fedora 'gitspacewalk' sponsor needed for transif
This one is for Transifex. I created https://bugzilla.redhat.com/show_bug.cgi?id=589149 We will be then able to manage our POT files using: https://translate.fedoraproject.org/ I have no idea if it will be for good or bad. If we will not like it, we can cancel it later. Mirek Original Message Subject: Fedora 'gitspacewalk' sponsor needed for transif Date: Wed, 05 May 2010 13:56:48 + From: accou...@fedoraproject.org To: gitspacewalk-spons...@fedoraproject.org Fedora user msuchy has requested membership for transif in the gitspacewalk group and needs a sponsor. Please go to https://admin.fedoraproject.org/accounts/group/view/gitspacewalk to take action. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Translations
You can help with Spacewalk translation at: https://translate.fedoraproject.org/projects/p/spacewalk/ You should be able to log in using you FAS account. You are encouraged to work on following components: rhnsd yum-rhn-plugin rhn-client-tools Please do *not* work on spacewalk-server as 8bit characted currently make problem in xmlrpc communitacion. All changes in Transifex will be automaticaly saved in master branch of our git repo. Some people already done translation for Polish and German, which is cool. Thx It seems that Transifex is unable to import and use our translation from Java. This remains as TODO. Suggestions are welcome. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] color guide for treeview lists
On 05/06/2010 11:41 PM, Máirín Duffy wrote: Hi, Partha and Justin have been working on a feature to let you identify and delete duplicate system profiles more easily. As part of this feature they've created a treeview listview in the UI. I created the following guide today showing the new colors that should be used in these listviews to fit the rest of the Spacewalk branding. I added it to the Spacewalk wiki, here it is: https://fedorahosted.org/spacewalk/attachment/wiki/ArtAndDesignStuff/color-guide.png I'm going to be looking to make some CSS changes for this as well but as it may be a handy resource at some point (maybe not) I figured I'd post about it here. Which reminds me... will you do css using the old-fashion way or use :nth-child() pseudo class from CSS3? It should be recognized by most today's browsers (but *cough* IE). Just asking. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Spacewalk 1.1 preparation
I just edited Roadmap to better reflect reality. The last task for Spacewalk 1.1 is support for F-13, which will be nice to have. Jan and Jan (adelton and jblazek) are going to work on this and you can probably expect one week before this get resolved. Do you see any other blocker for release? Any volunteers for release nanny? Milan volunteered. Any objections? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] %changelogs in our packages
On 06/01/2010 04:59 PM, Jan Pazdziora wrote: Hello, what is our position on the length of the %changelog section in our rpms? Now that we've released Spacewalk 1.0 and most core Spacewalk packages are in version 1.0, might it make sense to trim any changelog items for versions pre 1.0? Or maybe any changelog items older than say two years? One of the reasons I care about the length of the changelog section of our rpms is that it pollutes our (Spacewalk's) database when such rpms are synced/pushed -- we store each item as separate record in rhnPackageChangeLog, and if new version of the same package is added, it generally contains all the versions that the previous version contained, plus one new item/record. Which of course we might want to refactor somehow, eventually. But still -- do we really need changelogs going all the way back? Disks are cheap. And I very often went through the changelogs to see in which version something changed (not our packages). I suppose that for poeple who do not have our repo cloned and do not know git, this information can be usefull. Trimming will save how much data? Several KB? I vote to keep it as is. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Spacewalk 1.1 preparation
On 06/02/2010 04:13 PM, Marcus Moeller wrote: Hi. I just edited Roadmap to better reflect reality. The last task for Spacewalk 1.1 is support for F-13, which will be nice to have. Could one also please take care of this one: http://www.mail-archive.com/spacewalk-l...@redhat.com/msg04640.html Sounds like Anaconda problem to me... According to: https://bugzilla.redhat.com/show_bug.cgi?id=592985#c3 you promised to check server side. Did anaconda sent request to Spacewalk. Do you see it in httpd access log of Spacewalk? Did Spacewalk sent 200 back? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Spacewalk 1.1 preparation
On 06/02/2010 05:08 PM, Marcus Moeller wrote: Hi again. Hi. I just edited Roadmap to better reflect reality. The last task for Spacewalk 1.1 is support for F-13, which will be nice to have. Could one also please take care of this one: http://www.mail-archive.com/spacewalk-l...@redhat.com/msg04640.html Sounds like Anaconda problem to me... According to: https://bugzilla.redhat.com/show_bug.cgi?id=592985#c3 you promised to check server side. Did anaconda sent request to Spacewalk. Do you see it in httpd access log of Spacewalk? Did Spacewalk sent 200 back? This problem cannot be verified without Spacewalk, that's why it's up to you now :) I thought that this happen between anaco...@f-13 and Spacewalk 1.0. Or why could not you reproduce it again? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Maintance Window Specification
I've been working on this specification some time and here it somes: https://fedorahosted.org/spacewalk/wiki/MaintWindow_Spec The main goal is to allow: * Staged deployments: yum download prior to window; install during window * Linking scripts to config deployments (think: deploy config files and then restart service X) * Reoccurring remote commands Especially "Linking scripts to config deployments" is very similar to what Puppet do. And you may ask: "Why you are reinventing wheel. Why do not you use Puppet for this." Well, I asked this question myself and my answer is that we *want to* use Puppet. Someday. The problem is that if Spacewalk want to integrate with Puppet and provide GUI, we had to store configuration files somewhere (already done), we had to store remote scripts somewhere. And we should store it probably store it in DB as storage in plain text files will probably bring some security questions in Spacewalk context. And exactly this is big part of this specification. And even this task is already huge load. Meanwhile we will still use rhncfg-client and rhn_check for the deployment. But once all from this specification is done we can create new module for Puppet to retrieve nodes, config files and scripts etc. (or mirror it the way as we do with cobbler today). But that is probably far future. Anyway ... do you have comments on this specification? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Client for other than *nix OS'es?
On 06/21/2010 01:17 AM, Jason Williams wrote: I was demoing Spacewalk and I realized that it would be a very interesting way to keep inventory and monitor all my systems, not just the *nix based ones. So on a whim I decided to break out my limited The question is what benefit will this bring you beyond simple inventory. You could not monitor it anyway. Well you can do only remote probes like ping, traceroute etc. but all that you can do with any other machine record as parameter of nearly all probes are hostname (which if left empty is set to hostname of that machine). Not sure if somebody will be willing to write equivalent of rhnmd for Windows. Anyway, I thought I would post the simple python script here and see if you guys thought it might be something that one day could fit into Spacewalk/RHN. I've attached the script to this email. It's probably a bit crude due to my limited Python experience, but surprisingly, I've tested it on XP and Windows 7 and it seems to register a system just fine with an activation key. I've done some of the basic Network Monitoring tests with it too and they seem to work just fine. Thoughts? And please feel free to tell me I'm probably barking up the wrong tree if you do think I am. I like it. This script will need some love - at least ability to specify activation key on command line and not hard code. If it will be usefull for somebody (and definitely it will), we can distribute it. Although it will be on bottom of our priorities. So if you are willing to work on it and maintain it, go on. If you polish it I'm willing to accept it. What I would like to see before accepting it: - separate README file, with install instructions - not hardcoded activation key - do not use ~/rhn_sysid but rather ~/systemid so we are more consistent - I would like to be more consistent with rhnreg_ks or rhn_register in both naming of the script and accepted parameters. - put in header license you choosed for this script (GPLv2 is prefered, but it is up to you). -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Client for other than *nix OS'es?
On 06/22/2010 01:20 AM, Jason Williams wrote: Miroslav Suchý wrote: The question is what benefit will this bring you beyond simple inventory. You could not monitor it anyway. Well you can do only remote probes like ping, traceroute etc. but all that you can do with any other machine record as parameter of nearly all probes are hostname (which if left empty is set to hostname of that machine). Not sure if somebody will be willing to write equivalent of rhnmd for Windows. I assumed that the only things it could do right out of the gate were inventory and remote monitoring stuff. Then I realized, if I were to play around with the WMI Python stuff, and learn a bit about how rhnmd did it's communications, I might be able to duplicate a few of the Linux based monitoring metrics. I know it seems like a daunting task, but I was pretty surprised how easy it was to just get the basic stuff going in this proof of concept client. So I was thinking it might not be that hard to get some of that stuff working. *nod* rhnmd is just wrapped around sshd. IIRC sshd exist for Windows, but allow only root to login. But I may be wrong, it is long time I used it. But then there is another obstacle that we asume existence of /proc and basic linux commands. But one step in time, I'm looking to much in future right now :) I'll definitely get to polishing it up now that I know it's something one of the devs thinks is useful. I really only put it together as a "I wonder if this will work" sort of idea. Then when it did, my buddy suggested I ping it off you guys. I'll run through your list and fix the stuff up though. I might even wrap a NSIS installer around it, python, and PyOpenSSL just for good measure. OK. I'm not sure we will be willing to host .EXE files for installer if we could not compile them from scratch. But we can link to your website for such installer. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Removed F10 and F11 from miroslav.suchy.cz
I removed nightly build of F10 (obsolete for some time) and F11 (we stop build for it recently). To be precise I removed dirs: nightly-candidate-f10 nightly-candidate-f11 nightly-candidate-client/f10 nightly-candidate-client/f11 I will remove EL5 and F12 in 2 weeks as official repo is http://koji.spacewalkproject.org/spacewalk/split/ for some time. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] awards for Lukáš Ďurfina
FYI: http://rvokal.livejournal.com/11728.html From article: And the winner is Lukas Durfina with Native support for deb packages in Spacewalk. This project was a master thesis at Brno University of Technology and supported by Miroslav Suchy from Red Hat and Radek Koci at university. More information can be found on the homepage of Spacewalk project. Congrats Lukáš. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Package reviews for Fedora wanted
Can somebody please make package review for Fedora for package spacewalk-backend? https://bugzilla.redhat.com/show_bug.cgi?id=612581 I have other review in queue: https://bugzilla.redhat.com/show_bug.cgi?id=553649 https://bugzilla.redhat.com/show_bug.cgi?id=538057 https://bugzilla.redhat.com/show_bug.cgi?id=491331 You are welcome to do those reviews as well, but spacewalk-backend is my priority due nag mail I'm receiving every day because of broken dependency. Thanks in advance. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Rebase of PyPAM
I find that F13 repo has missing PyPAM package, so I done several tasks: * I rebased from 0.4.2 to 0.5.0 (already 3 years old :) * I submit it to Fedora (BZ 612998 - review is welcome) * and finally I build it to Spacewalk. Enjoy -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [Fwd: removing log5j until we get fedora approval; removed velocity since its in tempjars...]
On 07/09/2010 03:40 PM, Shannon Hughes wrote: justin is working to get it approved into fedora but there was an issue with the Source var in the spec file. To be precise: https://bugzilla.redhat.com/show_bug.cgi?id=574575 IMO it is good spec, but since it is Justin first package he needs sponsor. Only few people can sponsor others. One of them is Dennis Gilmore, who promised to sponsor Justin, but according the BZ it seems he did not response since April. Dennis can you look at this review please? > Shannon - do we still use/have log4j then? Hmm log4j is not replacement for log4j, it is enhancement. log5j requires log4j: $ rpm -qpR /home/msuchy/rpmbuild/RPMS/noarch/log5j-1.2-1.el6.noarch.rpm log4j rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Rebase of PyPAM
On 07/09/2010 11:26 PM, Cliff Perry wrote: We use to carry three patches in our PyPAM package. Are those bugs fixed in the newer version, or are we still maintaining them? Looking at: 1012 rpm2cpio ../../PyPAM-0.4.2-18.rhn.src.rpm | cpio -di [cpe...@cperry 18]$ ls PyPAM-0.4.2-error.patch PyPAM-dlopen.patch PyPAM.spec PyPAM-0.4.2.tar.gz PyPAM-includes.patch version [cpe...@cperry 18]$ I investigated this before the rebase. Patches: PyPAM-includes.patch PyPAM-0.4.2-error.patch are already included in PyPAM 0.5.0 in upstream Patch: PyPAM-dlopen.patch is not included, so I carried it over to new version too. And I informed the upstream about this patch and reason why it is needed. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PostgreSQL status
On 07/11/2010 08:12 AM, Jan Pazdziora wrote:
On Sat, Jul 10, 2010 at 04:52:53PM -0400, Travis Camechis wrote:
Do the oracle dependencies still exist for the postgres install? Just
doesn't seem right having to install oracle parts for the Postgres install.
I believe that we still have the dependency on the
oracle-instantclient-*, primarily because part of the game is
monitoring which has Oracle probes and thus needs Oracle client
libraries.
I think Mirek (?) was working on making that part of monitoring
optional.
I just checked the code we still require Oracle at 2 places in code:
1) package spacewalk-base-minimal
This is due file
modules/rhn/RHN/DB.pm
where we import
use DBD::Oracle qw(:ora_types);
and for blobs we set
$attr->{ora_type} = ORA_BLOB;
Patch for this issue is welcomed.
2) Regarding the monitoring, I had the changes in my local branch, I
worked on that today and pushed it, so if you install
spacewalk-posgresql you should not need DBD::Oracle (if it's still need
it, report it).
I'm going to check if you will have still the option to choose Oracle
probes when you will not have that module installed. (apparently it
should be hidden), will report tomorrow my findings.
--
Miroslav Suchy
Red Hat Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] spacecmd will be in next version of Spacewalk
Those of you who watch commits can notice that spacecmd landed to Spacewalk git repo. Aron Parsons (apars...@redhat.com) will be primary owner of this component. If you want to see this package in Fedora and Epel, grab this review: https://bugzilla.redhat.com/show_bug.cgi?id=616120 Despite of @redhat.com in Aron email, he is not part of RHN Satellite team and he is 3rd person from general Spacewalk community who deserved direct write access source code! Congrats! I'm happy to see our developer community is growing. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Staging content - enabled or disabled by default?
I committed to git code which will allow you pre-cache scheduled content. I.e. you schedule package installation for 20:00, rhn_check will check in at 16:00 and it will see that it will have to install package after 4 hours. So rhn_check will download those packages and at 20:00 you can execute scheduled action faster - do only the installation, not downloading. I done this for package installation and put there hook for all other actions. I would like to ask you folks what should be default. Enabled or disabled by default. Current situation is: There is one switch in Admin -> Organization -> Some org -> Configuration -> Enable Staging Contents Disabling this option will override individual system options. Default is disabled. each system will parse /etc/sysconfig/rhn/up2date for variable staging_content and if set to 0, staging content is disabled even if it was enabled for whole organization. This variable is enabled by default, but only new installation will get this, since during upgrade new config is created as .rpmnew, so you have to enable it manualy, if you want to. So you must have both staging_content in /etc/sysconfig/rhn/up2date and "Enable Staging Contents" in org enabled to enable staging content for individual machines. Do you have any comments for this logic? Do you agree with it or do you have some suggestion? -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] client/tools
May I ask why was removed this line - highlighted inline: On 07/30/2010 01:11 AM, Partha Aji wrote: New commits: commit 145edafbeb6da83bbfbc612da1c6a406712af34a Author: Partha Aji Date: Thu Jul 29 19:07:55 2010 -0400 Made the diff in operation rhncfg client work with symlinks ... --- a/client/tools/rhncfg/config_client/rhncfgcli_diff.py +++ b/client/tools/rhncfg/config_client/rhncfgcli_diff.py @@ -35,11 +34,16 @@ class Handler(handler_base.HandlerBase): if type == 'directory': #dst is a directory, so just tell the user we're skipping the entry print "Entry \'%s\' is a directory, skipping" % dst -return ---^^ elif type == 'symlink': #dst is a symlink, so just tell the user we're skipping the entry -print "Entry \'%s\' is a symbolic link, skipping" % dst -return +srclink = os.path.abspath(os.readlink(src)) +destlink = os.path.abspath(os.readlink(dst)) +if srclink == destlink: +print "No change between the symbolic links '%s' " % dst +else: +print "Symbolic link targets are different." +print "Channel: '%s' -> '%s' System: '%s' -> '%s' " % (dst,srclink, dst, destlink) + else: # if file isn't present, compare to /dev/null so we see the # whole thing in the diff -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Article for Linux Magazine in the UK
On 08/03/2010 07:31 PM, James Hogarth wrote: Hi all, I was considering composing an article for Linux Magazine (if they will accept it) with regards to configuration and use of spacewalk. However before I take the time to write an appropriate submission I just wanted to make sure no one had any objections to such a thing. No objection. In fact we would be pleased. If you will have some questions for developers do not hesitate to ask here or on #spacewalk or #spacewalk-devel on irc.freenode.net. BTW: I think everybody will be glad if you notify us, when the article will be published (of course - if will be accepted). -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] possible breakage of spacewalk-backend
Well with this mine commit, I admit something can break. I tested it on
my own Spacewalk and it works, but I'm not sure what it make to
developer setup...
So if something breaks, you know why :)
I hope nobody is against this change. But if somebody do not like it,
I'm ready to open discussion.
Original Message
Subject: 8 commits - backend/spacewalk-backend.spec
rel-eng/push-packages-to-fedora.sh
Date: Fri, 13 Aug 2010 17:16:27 + (UTC)
From: Miroslav Suchý
Reply-To: Mailing list for spacewalk commits.
To: spacewalk-comm...@lists.fedorahosted.org
backend/spacewalk-backend.spec | 21 -
rel-eng/push-packages-to-fedora.sh | 33
++---
2 files changed, 30 insertions(+), 24 deletions(-)
New commits:
commit e4d1239a60454099f3b867640776b8764f463f01
Author: Miroslav SuchĂ˝
Date: Fri Aug 13 19:14:30 2010 +0200
612581 - move all python libraries to standard python path
there should not be any regression, since %{python_sitelib} is
always in python path and import should always success
diff --git a/backend/spacewalk-backend.spec b/backend/spacewalk-backend.spec
index ae4392d..1ff92d8 100644
--- a/backend/spacewalk-backend.spec
+++ b/backend/spacewalk-backend.spec
@@ -1,10 +1,10 @@
-%global rhnroot %{_prefix}/share/rhn
%global rhnconf %{_sysconfdir}/rhn
%global httpdconf %{rhnconf}/satellite-httpd/conf
%global apacheconfd %{_sysconfdir}/httpd/conf.d
%if 0%{?fedora} < 13 && 0%{?rhel} < 6
%{!?python_sitelib: %global python_sitelib %(%{__python} -c "from
distutils.sysconfig import get_python_lib; print get_python_lib()")}
%endif
+%global rhnroot %{python_sitelib}
Name: spacewalk-backend
Summary: Common programs needed to be installed on the Spacewalk
servers/proxies
@@ -332,7 +332,6 @@ rm -f %{rhnconf}/rhnSecret.py*
%files
%defattr(-,root,root)
%doc PYTHON-LICENSES.txt LICENSE
-%dir %{rhnroot}
%dir %{rhnroot}/common
%{rhnroot}/common/__init__.py*
%{rhnroot}/common/apache.py*
___
spacewalk-commits mailing list
spacewalk-comm...@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/spacewalk-commits
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] possible breakage of spacewalk-backend
On 08/13/2010 07:34 PM, Jan Pazdziora wrote:
On Fri, Aug 13, 2010 at 07:21:36PM +0200, Miroslav Suchý wrote:
Well with this mine commit, I admit something can break. I tested it
on my own Spacewalk and it works, but I'm not sure what it make to
developer setup...
So if something breaks, you know why :)
I hope nobody is against this change. But if somebody do not like
it, I'm ready to open discussion.
I don't like the fact that we will pollute /usr/lib/python2.6 with
multiple directories with very generic names -- common, actions,
classes, etc. Shouldn't we make it
distutils.sysconfig import get_python_lib; print get_python_lib()")}
%endif
+%global rhnroot %{python_sitelib}
%global rhnroot %{python_sitelib}/rhn
This
%global rhnroot %{python_sitelib}/rhn
would require code change from
from common import rhnLib
to
from rhn.common import
which will break things for sure if we forget to change even one import
My approach is not optimal as we populate it with those generic names.
But one step in time.
We can even conflict with some others packages on really generic names like:
common/apache.py
Which is good. Becouse you will get at least error during installation.
If some package Foo has file %{python_sitelib}/common/apache.py and we
do in our code:
from common import apache
then our apache.py will not be loaded and will be imported module from
package Foo and you probably get error in runtime. Which is worse IMO.
But yes, we can move everything to %{python_sitelib}/rhn, but I would
rather do that in begging of 1.3 developers cycler and not now.
instead and change all the relevant imports to have the "rhn."
prefix? Alternatively we could have /usr/share/rhn to be a symlink
to %{python_sitelib}/rhn or something similar.
That's ugly. Since we have there other data which should not be stored
in %{python_sitelib}
E.g. RHN-GPG-KEY, RHNS-CA-CERT
--
Miroslav Suchy
Red Hat Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] possible breakage of spacewalk-backend
On 08/13/2010 07:21 PM, Miroslav Suchý wrote:
Well with this mine commit, I admit something can break. I tested it on
my own Spacewalk and it works, but I'm not sure what it make to
developer setup...
So if something breaks, you know why :)
I hope nobody is against this change. But if somebody do not like it,
I'm ready to open discussion.
Ok. We discussed this internally and I'm going to revert this for now. I
will commit it again in few weeks and will put python modules from
/usr/share/rhn to %{python_sitelib}/rhn (as opposed to pure
%{python_sitelib} what I made on Friday).
--
Miroslav Suchy
Red Hat Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Spam from gitstat
You probably get recently some spam from gistat at http://miroslav.suchy.cz/spacewalk/gitstat/ This was coused by feature "Mail to author", which allow you to send email from web form to author of specific commit. I was not aware of such feature and I disabled it now. Mirek Original Message Subject: FKVKTEOTHZsXpZsXFIC Date: Sun, 12 Sep 2010 21:25:36 +0200 From: gits...@lomenotecka.cz To: msu...@redhat.com qg1TL4 http://bnewgrsyfqgl.com/\";>bnewgrsyfqgl, [url=http://kzoibjlrzkzs.com/]kzoibjlrzkzs[/url], [link=http://ycghlljrwmrg.com/]ycghlljrwmrg[/link], http://gwmhdvgvwqtq.com/ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Slides for FudCon Zurich
During weekend I will be at Fud Con Zurich (with other Spacewalk developers). I will have 2 talks there. If you are unable to attend, you may want to check my slides, if you are interested. http://miroslav.suchy.cz/spacewalk/GoingOpenSourceWay.odp http://miroslav.suchy.cz/spacewalk/Tito.odp Schedule of talks: https://fedoraproject.org/wiki/FUDCon:Zurich_2010#Day_1_-_Friday.2C_2010-09-17 -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PATCH: Repogeneration for debian channels is broken
On 10/02/2010 12:31 PM, Simon Lukasik wrote: Hello list, There are few issues with repo generation for Debian channels: * Process will not complete for most of the cases, because FileNotFoundException is thrown, but rhn_taskomatic_daemon.log is silent. * When Debian channel is deleted, Taskomatic attempts to delete yum metadata which pollutes log, while Debian specific metadata are left on disk. * RepositoryWriter class contains private methods for both Deb and Rpm * Progress of 'Repo Cache Status' for Debian channel is reported on webui as '(none)' I have no problem with first commit (I already applied it). And with the last commit (but that is dependent on 2 an 3). But the 2nd and 3rd commit are big and it is not clear to me if it does not duplicate code of DebPackageWriter.java. The result is probably better by design by I will go through it later when I will have more time. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PATCH: Repogeneration for debian channels is broken
On 10/02/2010 12:31 PM, Simon Lukasik wrote: Hello list, There are few issues with repo generation for Debian channels: * Process will not complete for most of the cases, because FileNotFoundException is thrown, but rhn_taskomatic_daemon.log is silent. * When Debian channel is deleted, Taskomatic attempts to delete yum metadata which pollutes log, while Debian specific metadata are left on disk. * RepositoryWriter class contains private methods for both Deb and Rpm * Progress of 'Repo Cache Status' for Debian channel is reported on webui as '(none)' I didn't address the last issue. Please, could somebody review my patches? Commited. Thx. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Drop of spacewalk-backend-upload-server ?
I just find that no one require package spacewalk-backend-upload-server. rhnpush works even with this package removed. Unless somebody will tell me for what we use /PKG-UPLOAD handler (seems no one use it) or this package in general, then I will delete this package in few days. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Changes to 'debian'
On 10/19/2010 08:24 AM, Jan Pazdziora wrote: On Mon, Oct 18, 2010 at 08:14:16PM +, Miroslav Suchý wrote: New branch 'debian' available with the following commits: Why separate branch and why not master? Because we have no tool, to make debian/control, debian/changelog in sync with master, you have to do it manually. And since it still did not land in Debian main and it is under review (in Debian it is mentors.debian.net) I do not want to bother all of you with those files. On the other hand there is lot of work behind these files already, so I decided that it is time to not depend on my own HDD and public it somewhere. And git seems to me as best place. I do not suppose, that somebody else but me (and probably Simon) will work on this branch. And when right time comes, I may write some new class for Tito and merge this branches together. But this feature is quite distant. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Moving python modules from /usr/share/rhn to python site-packages dir
During followings days I prepared patch which move python modules from package spacewalk-backend from directory /usr/share/rhn to python site-packages (e.g. /usr/lib/python2.4/site-packages). I also moved them into spacewalk dir, to prevent pollution of standard python libs with our common namespace... I tested it a lot. It should have no visible impact (and no bugs). If you find some bug, feel free to hit me with long stick. Consequence for you is that instead of: from satellite_tools import satsync you have to use: from spacewalk.satellite_tools import satsync or instead of: from common import rhnConfig you have to use: from spacewalk.common import rhnConfig etc. Only one exception is apache handlers for /XP, /APP ..., which I kept in /usr/share/rhn as this seem right to me, because they are not modules you can import in ordinary script. This change is only about spacewalk-backend. Although I had to change imports in packages which depends on modules from spacewalk-backend. Other packages still have their modules in /usr/share/rhn and I will focus my attention to them in near future. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] web.apiversion
Can we please increment web.apiversion (in file web/conf/rhn_web.conf)
each time we add/modify new api call? Thx
Mirek
Original Message
Subject: 2 commits - java/code
Date: Mon, 1 Nov 2010 17:33:18 + (UTC)
From: Tomas Lestach
Reply-To: Mailing list for spacewalk commits.
To: spacewalk-comm...@lists.fedorahosted.org
java/code/src/com/redhat/rhn/frontend/action/satellite/GeneralConfigAction.java
|2 -
java/code/src/com/redhat/rhn/frontend/action/satellite/test/GeneralConfigActionTest.java
|5 ++-
java/code/src/com/redhat/rhn/frontend/xmlrpc/satellite/SatelliteHandler.java
| 15 +-
3 files changed, 19 insertions(+), 3 deletions(-)
New commits:
commit c0d9adde56a3d17f4eb5bed1b2516798d60b984d
Author: Tomas Lestach
Date: Mon Nov 1 18:31:07 2010 +0100
647099 - introducing satellite.isMonitoringEnabled API
diff --git
a/java/code/src/com/redhat/rhn/frontend/xmlrpc/satellite/SatelliteHandler.java
b/java/code/src/com/redhat/rhn/frontend/xmlrpc/satellite/SatelliteHandler.java
index 4deaf4c..1daa33e 100644
---
a/java/code/src/com/redhat/rhn/frontend/xmlrpc/satellite/SatelliteHandler.java
+++
b/java/code/src/com/redhat/rhn/frontend/xmlrpc/satellite/SatelliteHandler.java
@@ -14,6 +14,7 @@
*/
package com.redhat.rhn.frontend.xmlrpc.satellite;
+import com.redhat.rhn.common.conf.ConfigDefaults;
import com.redhat.rhn.domain.channel.ChannelFamily;
import com.redhat.rhn.domain.channel.ChannelFamilyFactory;
import com.redhat.rhn.domain.entitlement.Entitlement;
@@ -158,5 +159,17 @@ public class SatelliteHandler extends BaseHandler {
return CertificateFactory.lookupNewestCertificate().getExpires();
}
-
+/**
+ * Indicates if monitoring is enabled on the satellite
+ * @param sessionKey session of the logged in user
+ * @return True if monitoring is enabled
+ *
+ * @xmlrpc.doc Indicates if monitoring is enabled on the satellite
+ * @xmlrpc.param #param("string", "sessionKey")
+ * @xmlrpc.returntype #param("boolean", "True if monitoring is
enabled")
+ */
+public boolean isMonitoringEnabled(String sessionKey) {
+getLoggedInUser(sessionKey);
+return ConfigDefaults.get().isMonitoringBackend();
+}
}
commit 6eb4da56285f4d81b0436e8e66f405b1d40123e2
Author: Tomas Lestach
Date: Mon Nov 1 18:03:18 2010 +0100
replace web.is_monitoring_backend with
ConfigDefaults.WEB_IS_MONITORING_BACKEND
diff --git
a/java/code/src/com/redhat/rhn/frontend/action/satellite/GeneralConfigAction.java
b/java/code/src/com/redhat/rhn/frontend/action/satellite/GeneralConfigAction.java
index b36775a..c655c69 100644
---
a/java/code/src/com/redhat/rhn/frontend/action/satellite/GeneralConfigAction.java
+++
b/java/code/src/com/redhat/rhn/frontend/action/satellite/GeneralConfigAction.java
@@ -60,7 +60,7 @@ public class GeneralConfigAction extends
BaseConfigAction {
private static final String[] BOOLEAN_CONFIG_ARRAY =
{"web.ssl_available",
"web.enable_solaris_support", ConfigDefaults.DISCONNECTED,
-"web.is_monitoring_backend"};
+ConfigDefaults.WEB_IS_MONITORING_BACKEND};
private static final List COMBO_LIST = new LinkedList();
static {
diff --git
a/java/code/src/com/redhat/rhn/frontend/action/satellite/test/GeneralConfigActionTest.java
b/java/code/src/com/redhat/rhn/frontend/action/satellite/test/GeneralConfigActionTest.java
index 5471f2b..07e3d31 100644
---
a/java/code/src/com/redhat/rhn/frontend/action/satellite/test/GeneralConfigActionTest.java
+++
b/java/code/src/com/redhat/rhn/frontend/action/satellite/test/GeneralConfigActionTest.java
@@ -15,6 +15,7 @@
package com.redhat.rhn.frontend.action.satellite.test;
import com.redhat.rhn.common.conf.Config;
+import com.redhat.rhn.common.conf.ConfigDefaults;
import com.redhat.rhn.domain.role.RoleFactory;
import com.redhat.rhn.frontend.action.satellite.GeneralConfigAction;
import com.redhat.rhn.frontend.struts.RhnAction;
@@ -31,7 +32,9 @@ import java.util.Map;
* @version $Rev: 1 $
*/
public class GeneralConfigActionTest extends RhnMockStrutsTestCase {
-private static final String TEST_CONFIG_BOOLEAN =
"web.is_monitoring_backend";
+private static final String TEST_CONFIG_BOOLEAN =
+ConfigDefaults.WEB_IS_MONITORING_BACKEND;
+
public void testTestValue() {
assertTrue(GeneralConfigAction.ALLOWED_CONFIGS.
___
spacewalk-commits mailing list
spacewalk-comm...@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/spacewalk-commits
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] tanukiwrapper no longer in Fedora 14
On 11/12/2010 11:41 AM, Jan Pazdziora wrote: Hello, so it looks like based on http://lists.fedoraproject.org/pipermail/devel/2010-August/142064.html the tanukiwrapper is no longer in Fedora 14. What is the most reasonable course of action for Spacewalk on Fedora 14? Do we want to just take tanukiwrapper-3.2.3-5.fc12 from Fedora 13 and import it to koji and throw it to Spacewalk yum repos? Do we have anybody who would be willing and able to take over the maintenance of tanukiwrapper in Fedora? Are there any alternatives (ideally in Fedora) we should be looking at? I will apply for the ownership. Unless somebody will come with alternative. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] spacewalk-backend in Fedora
I finally get package spacewalk-backend into Fedora. Which is good. But there are also drawback... I just submited it to updates of F13 and F14, so it will appear in updates-testing soon. And after week it may get into stable. I put there 1.2 version (release will be probably tomorrow), which means, that everybody who has F13 or F14 with Spacewalk 1.1 and older should be carefull with "yum upgrade" as upgrading to spacewalk-backend-1.2 (while everything else will remain on 1.1), will break you Spacewalk. And of course it is missing spacewalk-backend-sql-oracle sub-package and Oracle bits are not allowed in Fedora. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Questions about some translations
On 11/19/2010 12:05 AM, Luc de Louw wrote: Dear all, I was asked to contribute some German translations to spacewalk. Of course I'll do that. Translation stats on "backend" went up from AFAIR 44% to now 72%. So far so good. On https://translate.fedoraproject.org/projects/p/spacewalk/c/spacewalk-server/ I detected some strings that I never saw before on my daily work as a sat and spacewalk user. Right now, you could not see translated strings of backend (spacewalk-server), because we do not set header Accepted-Language in XMLRPC protocol. We should address it soon, since we already have several translation in backend. Right now, you can see translated string in rhn-client-tools, yum-rhn-plugin and rhnsd. Other thing is Java translation, which is not supported by Transifex: $ find |grep StringResource |grep -i _de ./code/src/com/redhat/rhn/frontend/strings/template/StringResource_de.xml ./code/src/com/redhat/rhn/frontend/strings/database/StringResource_de.xml ./code/src/com/redhat/rhn/frontend/strings/nav/StringResource_de.xml ./code/src/com/redhat/rhn/frontend/strings/java/StringResource_de.xml ./code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml ./code/src/com/redhat/rhn/common/localization/test/StringResource_de_DE.xml But this is most probably all translated for DE. For high quality translations, it is needed to see the stings in its context. For that I need provoke several error-messages and some help how to provoke them. You can at least see where in code it is used. #: ../server/handlers/xmlrpc/up2date.py:258 #, python-format msgid "Unable to retrieve package header %s" -msgstr "Konnte Paket-Kopf %s nicht abrufen" +msgstr "Konnte Paket-Header %s nicht abrufen" Means that is is used on ../server/handlers/xmlrpc/up2date.py in line 258 Questions: 1. Is this list the right resource to ask questions to ensure strings are understood like they should? Yes, it is. Anything related of Spacewalk development is welcomed here. And development is not just coding. Translation, documentation, design changes are welcomed as well. 2. Is git clone git://git.fedorahosted.org/git/spacewalk.git/ and subsequent git pull the right source for po files? (Transifex is almost unusably slow) Yes. Transifex is doing just the same. 3. Is the master/trunk branch the right one? Yes. 4. Is it fine to run "cd ~/spacewalk/backend/po; make install" and having the newly translated strings available to the installed spacewalk? Probably yes, I never done it. We prefer to do change, commit it to your local git, run: tito build --test --rpm install result (if it is on the same server you can utilize -i option). And if it ok, push the changes. In your case upload .po file using Transifex. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] searching in git using code.google.com
Although "git grep" is almigty, I just find that http://www.google.com/codesearch , which ignored git repositories for long time, now support git (did I miss some announcement?). And guess what..? Spacewalk is indexed as well: http://www.google.com/codesearch?hl=en&lr=&q=package%3Aspacewalk+proxy&sbtn=Search -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Spacewalk documentation updated
It took me some time, but http://spacewalk.redhat.com/documentation/ is now updated to 1.2. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] rhn_register errors
On 12/03/2010 05:28 AM, Colin Coe wrote: PythonHandler spacewalk.server.apacheServer::Handler: AttributeError: 'module' object has no attribute 'File' Michael fixed it toady. Use spacewalk-backend-1.3.21-1 So I tried updating the client to nightly and found that there is a dependency on "python-ethtool>= 0.4" from rhn-client-tools-1.3.1-1.el5.noarch. Looking in http://koji.spacewalkproject.org/spacewalk/split/spacewalk-5E/client/spacewalk-5E-nightly/x86_64/os/ I see python-ethtool-0.3-5.el5.x86_64.rpm. Are there plans to put an I fixed it today. Use rhn-client-tools-1.3.2-1 -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Spacewalk
On 12/09/2010 03:20 AM, Cliff Perry wrote: plus the generated from source schema, java and python docs on the src code: http://git.fedorahosted.org/git/?p=spacewalk.git;a=tree;f=documentation Or better to browse: http://spacewalk.redhat.com/documentation/ And of course if you still will have the question after you read all that docs, you can ask here. We are willing to help. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] (no subject)
On 12/09/2010 10:18 PM, derleader __ wrote: Hi, I need to see how spacewalk installs rpm packages on the servers. In which installation package I can see the source code responsible for package handling (installation, remove)? Client side? rhn-client-tools and its subpackages. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] (no subject)
On 12/10/2010 11:56 AM, derleader __ wrote: 1. How do you move packages from spacewalk to the server? Do you use slot for communication or you use rsync? Client comunicate either using osad (asynchronously) or using rhnsd (synchronously every 4 hours). -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Fwd: [Fedora Update] [comment] rhnlib-2.5.24-1.fc13
FYI Original Message Subject: [Fedora Update] [comment] rhnlib-2.5.24-1.fc13 Date: Wed, 22 Dec 2010 00:07:00 + From: upda...@fedoraproject.org To: msu...@redhat.com The following comment has been added to the rhnlib-2.5.24-1.fc13 update: bodhi - 2010-12-22 00:07:00 (karma: 0) This update has been pushed to stable To reply to this comment, please visit the URL at the bottom of this mail rhnlib-2.5.24-1.fc13 Update ID: FEDORA-2010-19167 Release: Fedora 13 Status: stable Type: bugfix Karma: 3 Notes: build more recent rhnlib, which will allow you to install current : Spacewalk server. Submitter: msuchy Submitted: 2010-12-21 12:44:47 Comments: bodhi - 2010-12-21 12:44:49 (karma 0) This update has been submitted for testing by msuchy. mzazrive - 2010-12-21 12:47:22 (karma 1) adelton - 2010-12-21 12:54:28 (karma 1) Thank you, spacewalk nightly now installs again. tlestach - 2010-12-21 12:56:20 (karma 1) That's awesome! You saved us! Thank you! bodhi - 2010-12-22 00:07:00 (karma 0) This update has been pushed to stable https://admin.fedoraproject.org/updates/rhnlib-2.5.24-1.fc13 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Spacewalk's year 2010 in numbers
Let me allow to summarize year of 2010. I gathered some numbers for you: == Code == We commited 5974 changesets to Spacewalk http://miroslav.suchy.cz/spacewalk/gitstat/chart.php?chart_parameter1=2&showcount=10&submit=1&page=0 Top contributors are Jan Pazdziora and Michael Mráka with 1327 and 1326 commits. We can call it draw. Top contributor outside of Red Hat is Colin Coe with 89 commits. http://miroslav.suchy.cz/spacewalk/gitstat/chart.php?chart_parameter1=5&chart_parameter_ver=spacewalk-java-1.3.31-1&submit=1&chart_parameter2_year=2010&chart_parameter2_month=0&submit=1&showcount=10 We resolved 1012 Bugs. https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=bug_status&chfieldfrom=2010-01-01&bug_status=CLOSED&classification=Red%20Hat&product=Red%20Hat%20Network%20Proxy&product=Red%20Hat%20Network%20Satellite https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=bug_status&chfieldfrom=2010-01-01&bug_status=CLOSED&classification=Other&product=Spacewalk Red Hat is behind of 96% of contributions. http://miroslav.suchy.cz/spacewalk/gitstat/chart.php?chart_parameter1=3&chart_parameter_ver=spacewalk-java-1.3.32-1&submit=1&chart_parameter2_year=2010&chart_parameter2_month=0&submit=1&showcount=10 == Project cost == This is wild estimation, but just guess: Codebase: 2,908,841 (including code and mark up) Effort (est.): 843 Person Years Avg. Salary:$55000 year Estimated cost of project: $ 46,387,055 http://www.ohloh.net/p/spacewalk == Releases == We released 4 releases during year 2010: 0.8, 1.0, 1.1 and 1.2 http://freshmeat.net/projects/spacewalk/releases == IRC == We have nearly 1000 users on #spacewalk and 157 users on #spacewalk-devel. Some numbers from #spacewalk-devel: Is jortel stupid or just asking too many questions? 24.1% lines contained a question! red_alert didn't know that much either. 22.6% of his/her lines were questions. The loudest one was roysjosh, who yelled 10.7% of the time! Another old yeller was gurjeet, who shouted 8.7% of the time! It seems that bmomjian's shift-key is hanging: 1.2% of the time he/she wrote UPPERCASE. For example, like this: LOL mccun934 is a very aggressive person. He/She attacked others 5 times. For example, like this: * mccun934 smacks original author Poor himself, nobody likes him/her. He/She was attacked 2 times. For example, like this: * partha smacks himself cliff brings happiness to the world. 30.3% lines contained smiling faces. :) red_alert is second happiest person, smiling 27.1% of the time. But on the other hand he is on top with usage of sad faces. 5.1% lines contained sad faces. :( e_ is also a sad person, crying 2.5% of the time. bbuckingham wrote the longest lines, averaging 81.1 letters per line. #channel average was 40.3 letters per line. partha wrote the shortest lines, averaging 29.0 characters per line. mccun934 spoke a total of 72286 words! mccun934's faithful follower, partha, didn't speak so much: 61254 words. Lupicite wrote an average of 76.00 words per line. Channel average was 7.15 words per line. More numbers at: http://miroslav.suchy.cz/spacewalk/irc/spacewalk-devel/ And same numbers from #spacewalk: Is pikshik stupid or just asking too many questions? 33.8% lines contained a question! hdoria didn't know that much either. 33.6% of his/her lines were questions. The loudest one was cturner, who yelled 12.1% of the time! Another old yeller was Lokidiabel, who shouted 11.2% of the time! It seems that gregdek's shift-key is hanging: 3.4% of the time he/she wrote UPPERCASE. For example, like this: K. choirboy just forgot to deactivate his/her Caps-Lock. He/She wrote UPPERCASE 3.4% of the time. aking99 is a very aggressive person. He/She attacked others 5 times. For example, like this: * aking99 slaps self Poor self, nobody likes him/her. He/She was attacked 3 times. For example, like this: * aking99 slaps self jds2001 brings happiness to the world. 29.5% lines contained smiling faces. :) red_alert isn't a sad person either, smiling 27.9% of the time. Gh0sty seems to be sad at the moment: 6.7% lines contained sad faces. :( red_alert is also a sad person, crying 4.0% of the time. kok wrote the longest lines, averaging 107.1 letters per line. #channel average was 50.5 letters per line. delhage wrote the shortest lines, averaging 30.1 characters per line. doot was tight-lipped, too, averaging 30.3 characters. jsherrill spoke a total of 88628 words! jsherrill's faithful follower, Gh0sty, didn't speak so much: 50174 words. cdrelic wrote an average of 73.00 words per line. Channel average was 8.94 words per line. More numbers at: http://miroslav.suchy.cz/spacewalk/irc/spacewalk/ I'm looking forward to see you in new year :) -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/l
Re: [Spacewalk-devel] [Spacewalk-list] Spacewalklib: managing Linux systems from Java applications
On 01/02/2011 10:40 PM, Alfredo Moralejo wrote: I've called it spacewalklib and I've created a project in sourceforge for it http://spacewalklib.sourceforge.net/ As it's primarly intended to manage client systems, I've focused in the client management more that in the tool management itself (for example, I did not implement channels creation or cloning yet), however additional features in future may be added if required. Can you please enlighten me, how it differ from classic Spacewalk API? Why should I use this and not API? Additionally reading javadoc I find: >RhnClient(RhnConn rhnconn, java.lang.String hostname) > Constructor class. This is not good. You can have two clients with the same hostname (e.g. localhost.localnet). You should identify clients by systemID. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Process Communication
On 01/05/2011 04:07 PM, derleader __ wrote: Hi, I'm interested what kind of IPC Spacewalk use to pass information between processes? There is a lot of protocols. Spacewalk itself use mostly HTTP(S) and XMLRPC, but there is a lot of underlying technology which use SHM or sockets with plain text. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Process Communication
On 01/05/2011 04:23 PM, derleader __ wrote: >On 01/05/2011 04:07 PM, derleader __ wrote: >> Hi, >> I'm interested what kind of IPC Spacewalk use to pass information >> between processes? > >There is a lot of protocols. >Spacewalk itself use mostly HTTP(S) and XMLRPC, but there is a lot of >underlying technology which use SHM or sockets with plain text. > > >-- >Miroslav Suchy >Red Hat Satellite Engineering Thank you for the reply. Would you give more info about SHM and sockets with plain text. SHM: http://en.wikipedia.org/wiki/Shared_memory E.g. Apache and Tomcat use that. Sockets with plain text: E.g. monitoring programs open sockets and write plain text there while other monitoring program reads those data. http://en.wikipedia.org/wiki/Plain_text http://en.wikipedia.org/wiki/Internet_socket http://en.wikipedia.org/wiki/Unix_domain_socket -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
