Bug 521043 - [RFE] Database specific code should be split from spacewalk-setup
Summary: [RFE] Database specific code should be split from spacewalk-setup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Installation
Version: 0.7
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: spacewalk-rfe
TreeView+ depends on / blocked
 
Reported: 2009-09-03 09:53 UTC by Michael Mráka
Modified: 2012-12-10 09:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-10 09:27:03 UTC


Attachments (Terms of Use)

Description Michael Mráka 2009-09-03 09:53:52 UTC
Description of problem:
Support of different database backends requires split of database specific code to independent setup scripts. Otherwise we will install unnecessary drivers/scripts via rpm dependencies.


Version-Release number of selected component (if applicable):
Spacewalk 0.7

How reproducible:


Steps to Reproduce:
1. choose one of database backends (oracle o postgresql as of now)
2. install spacewalk
3. check that no other database backend packages/scripts/files have been installed (e.g. via rpm -q)
  
Actual results:
both oracle and postgresql packages are installed:
oracle-instanclient-basic
oracle-instanclient-sqlplus
cx_Oracle
postgresql-jdbc
postgresql-libs
python-pgsql

Expected results:
successful installation
only drivers for selected db installed

Additional info:

Comment 1 Jan Pazdziora 2010-11-19 16:05:38 UTC
Mass-moving to space13.

Comment 2 Miroslav Suchý 2011-01-19 21:44:14 UTC
Michael, this is already solved, isn't it?
Can we close this one?

Comment 3 Michael Mráka 2011-01-20 09:18:43 UTC
Nope, it's not finished yet.

Comment 4 Miroslav Suchý 2011-04-11 07:34:14 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 5 Miroslav Suchý 2011-04-11 07:37:27 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 6 Jan Pazdziora 2011-07-20 11:52:51 UTC
Aligning under space16.

Comment 7 Jan Pazdziora 2012-12-07 19:31:02 UTC
I'd consider this resolved. With the spacewalk-sql script and the spacewalk-oracle and spacewalk-postgresql packages, you choose the the supported backend during installation. Yes, in pacewalk-setup and Spacewalk::Setup, we have a mix of functions for both databases and we might get to split that out eventually, but right the installation works just fine so I propose closing it as CURRENTRELEASE. Do you concur?


Note You need to log in before you can comment on or make changes to this bug.