Re: [Spacewalk-devel] Split of spacewalk yum repo?
On Mon, Sep 07, 2009 at 08:42:23AM +0200, Miroslav Suchý wrote: Jesus M. Rodriguez wrote: yum/0.7/proxy yum/0.7/server IMO this does not bring any benefit. A lot of packages are common. If you install proxy, yum will not install Spacewalk server packages and vice versa. Right. On the other hand, the split will make it easier to repo sync just the proxy repo to your Spacewalk server. Plus, it's what we do with Satellite and RHN Proxy as well. But if you install Proxy or Spacewalk, yum will install new client tools. Well, that's why Jesus had that yum/0.7/client there as well. -- Jan Pazdziora Senior Software Engineer, Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Split of spacewalk yum repo?
Miroslav Suchý wrote: I suggest to split yum repo to two parts. One is Spacewalk and Proxy. Second is client tools. Do you agree? Do you disagree? Any comments? OK. No objections heard. Jesus can you give me contact on RH person responsible of http://spacewalk.redhat.com/yum/ ? If I understand the process I had to prepare the content in svn/branches/spacewalk_web/ once done, send ticket to And that is all. Dennis, can you do the necessary steps (in mash?) to generate two yum repos? Client packages should be: rhcfg* rhn-custom-info osad rhn-applet-actions rhn-custom-info rhn-kickstart* rhn-virtualization* spacewalk-koan rhnlib rhnmd rhnsd rhn-check rhn-setup yum-rhn-plugin koan spacewalk-certs-tools spacewalk-koan Everything else should stay in the yum repo as it is now. From Brandon's list I rejected: jabberpy perl-IO-stringy rhnpush spacewalk-proxy-installer spacewalk-ssl-cert-check spacewalk-ssl-cert-check They are needed for Spacewalk server/Proxy and with older releases it may be unable to install or run. So we should have them server yum repo and not in client repo. -- 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] Split of spacewalk yum repo?
Jan Pazdziora wrote: On Mon, Sep 07, 2009 at 08:42:23AM +0200, Miroslav Suchý wrote: Jesus M. Rodriguez wrote: yum/0.7/proxy yum/0.7/server IMO this does not bring any benefit. A lot of packages are common. If you install proxy, yum will not install Spacewalk server packages and vice versa. Right. On the other hand, the split will make it easier to repo sync just the proxy repo to your Spacewalk server. Plus, it's what we do with Satellite and RHN Proxy as well. But we do it, because we take money for each of them. In Spacewalk it is in one pack for one price :) But if you install Proxy or Spacewalk, yum will install new client tools. Well, that's why Jesus had that yum/0.7/client there as well. That is why I did not argued about client. I'm only against server/proxy split. -- Miroslav Suchy Red Hat Satellite Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Proposal to remove tables: rhn_db_environment, rhn_enviroment
I'm working on:
https://bugzilla.redhat.com/show_bug.cgi?id=476851
Bug 226915 - [ 976930 ] Monitoring failure on Satellite with external
db (where db name != db instance name)
Which start to be PITA and one solution which comes to my mind is to
remove tables: rhn_db_environment and rhn_enviroment. It has been used
in past [1]. It relate database name to enviroment. E.g.
'dev01a' = 'dev' environment;
But today it contain only one record:
insert into rhn_db_environment(db_name,environment) values
('WEBDEV','LICENSE');
where webdev is replaced during installation with dbname (but some parts
of our code take is as instance name).
Rhn_enviroment is even more simplier:
SQL select * from RHN_ENVIRONMENT;
NAME DESCRIPTION
---
LICENSE Licensed Software Model
Only part of Spacewalk, which use it is rhn_config_macro table, which is
AFAIK used only by monitoring. Main server do not use it.
So here comes the question: Do we want to deploy Spacewalk in highly
clustered environment with several databases or not? May I remove those
tables in question or not?
If I do not get any objection till Wednesday I will start working on the
removal.
Attached is (completly untested and unverified) patch. Just to give you
overview.
[1] For those with access to old Satellite svn - revision 45606 as example
--
Miroslav Suchy
Red Hat Satellite Engineering
From 1bc0febfc1ae667bc46937c2d230ed6951201f3b Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Miroslav=20Such=C3=BD?= msu...@redhat.com
Date: Mon, 7 Sep 2009 16:39:09 +0200
Subject: [PATCH] 476851 - removal of tables: rhn_db_environment, rhn_enviroment
---
.../domain/monitoring/config/DbEnvironment.hbm.xml | 18 --
.../domain/monitoring/config/DbEnvironment.java| 59
.../monitoring/config/MonitoringConfigFactory.java | 17 --
.../config/test/MonitoringConfigTest.java | 19 --
.../satellite/ConfigureSatelliteCommand.java |2 -
.../test/ConfigureSatelliteCommandTest.java| 13
monitoring/SatConfig/general/NOCpulse-ini |8 +--
monitoring/nocpulse-common/NOCpulse.ini.txt|9 +--
.../perl-API/NOCpulse/NOCpulseini.pm |7 +--
schema/spacewalk/common/data/data.deps |2 -
.../spacewalk/common/data/rhn_db_environment.sql | 44 ---
schema/spacewalk/common/data/rhn_environment.sql | 44 ---
.../spacewalk/common/tables/rhn_config_macro.sql |3 -
.../spacewalk/common/tables/rhn_db_environment.sql | 32 ---
schema/spacewalk/common/tables/rhn_environment.sql | 28 -
schema/spacewalk/common/tables/tables.deps |2 -
.../spacewalk/oracle/synonyms/db_environment.sql | 28 -
schema/spacewalk/oracle/synonyms/environment.sql | 28 -
spacewalk/setup/bin/spacewalk-setup| 33 ---
.../setup/share/upgrade/rhn-enable-monitoring.pl |3 -
.../rhn/RHN/DB/DataSource/xml/probe_queries.xml|6 +--
web/modules/rhn/RHN/DB/SatInstall.pm | 21 ---
22 files changed, 6 insertions(+), 420 deletions(-)
delete mode 100644 java/code/src/com/redhat/rhn/domain/monitoring/config/DbEnvironment.hbm.xml
delete mode 100644 java/code/src/com/redhat/rhn/domain/monitoring/config/DbEnvironment.java
delete mode 100644 schema/spacewalk/common/data/rhn_db_environment.sql
delete mode 100644 schema/spacewalk/common/data/rhn_environment.sql
delete mode 100644 schema/spacewalk/common/tables/rhn_db_environment.sql
delete mode 100644 schema/spacewalk/common/tables/rhn_environment.sql
delete mode 100644 schema/spacewalk/oracle/synonyms/db_environment.sql
delete mode 100644 schema/spacewalk/oracle/synonyms/environment.sql
diff --git a/java/code/src/com/redhat/rhn/domain/monitoring/config/DbEnvironment.hbm.xml b/java/code/src/com/redhat/rhn/domain/monitoring/config/DbEnvironment.hbm.xml
deleted file mode 100644
index aa17ec8..000
--- a/java/code/src/com/redhat/rhn/domain/monitoring/config/DbEnvironment.hbm.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-?xml version=1.0 encoding=UTF-8?
-!DOCTYPE hibernate-mapping
-PUBLIC -//Hibernate/Hibernate Mapping DTD 3.0//EN
-http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd;
-hibernate-mapping
-class name=com.redhat.rhn.domain.monitoring.config.DbEnvironment
-table=rhn_db_environment
-id name=environment type=string column=environment
-meta attribute=scope-setprotected/meta
-generator class=assigned/
-/id
-property name=dbName column=db_name type=string length=255 /
-/class
-query name=DbEnvironment.loadByEnvironment
-![CDATA[from com.redhat.rhn.domain.monitoring.config.DbEnvironment where environment = :environment]]
-/query
-
-/hibernate-mapping
diff --git a/java/code/src/com/redhat/rhn/domain/monitoring/config/DbEnvironment.java
