Cliff wrote: >>> 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. >> >> I'm a little confused as to what the purpose of the >> rhn_db_environment and rhn_environment are used >> for?
That's crucial question. It looks like nobody here knows ;). According to Mirek's investigation it's rudiment from old good hosted ages and it has never been utilized by satellite. >>> 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. >> >> Why wouldn't we want to have a highly clustered environment with >> several databases? > > Under the do no harm to Satellite motto for changing/cleaning up > Spacewalk - I do know that some customers use Oracle RAQ environments > for external databases. Does this proposed code change break them, or > make it easier to use or no difference either way? I can't imagine how this table(s) can affect Oracle RAC. So - no difference. > Cliff > >> That sounds like a useful feature, is it only used by monitoring? Can >> we have this >> type of environment by using configuration settings instead of a database >> table? -- Michael Mráka Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
