Modify

Ticket #937 (closed enhancement: wontfix)

Opened 12 years ago

Last modified 11 years ago

WL: add support for distro-specific bcfg2/Packages/config.xml files

Reported by: https://www.google.com/accounts/o8/id?id=AItOawmSAqcanZjC_zUMz6-24nRYFLJWSQtV0vw Owned by: desai
Priority: minor Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-server Version: 1.0
Keywords: Cc:

Description

Currently, we have both ubuntu and centos packages defined in bcfg2/Packages/config.xml. This causes ubuntu to download all the ubuntu and centos files, greatly increasing the time it takes to initialize the bcfg2-server. Desired solutions would be to have distro-specific files or have bcfg2 recognize what repo files to download.

Attachments

config.xml (5.1 KB) - added by https://www.google.com/accounts/o8/id?id=AItOawmSAqcanZjC_zUMz6-24nRYFLJWSQtV0vw 12 years ago.

Change History

Changed 12 years ago by https://www.google.com/accounts/o8/id?id=AItOawmSAqcanZjC_zUMz6-24nRYFLJWSQtV0vw

comment:1 Changed 12 years ago by desai

I'm not entirely sure I follow. Do you want the server to demand load the files based on which clients connect to that server? If the sources are in the config, i think the server will definitely need all of the data, right?

comment:2 Changed 12 years ago by https://www.google.com/accounts/o8/id?id=AItOawmSAqcanZjC_zUMz6-24nRYFLJWSQtV0vw

Well. in our case, we're not using a centralized bcfg2-server - each client has it's own server (on the same system as the client). But we're only using one set of bcfg2 configs for all supported distributions.

Is there a way in this case to load only the needed repository data?

comment:3 Changed 11 years ago by desai

  • Status changed from new to closed
  • Resolution set to wontfix

The big problem here is that you have both of your servers setup to be able to serve configurations for all clients. There isn't a way for the server to know a priori if it will need to serve data to a client in a given group. I don't think there is any way we can robustly accomplish what you're suggesting here.

I'd suggest an alternative approach, where you use a distributed versioning system that can cherrypick changes for different server types.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.