Version 3 (modified by desai, 16 years ago) (diff)


Tracking Development Releases of Bcfg2

This page provides an overview of issues users should be aware of when running Bcfg2 prereleases.

Fixed Issues


Description Severity Fix Revision
SSHbase traceback upon new entry addition Serious [3617]
Diffs not displayed in interactive client mode Serious [3618]
Failure on error path in POSIX driver Cosmetic [3622]

Known issues

None at this time

New features

Release Information

  • 0.9.5pre3
    • support for info.xml files (described here?)
    • support for package instance mappings. (described here?)
    • added output options to bcfg2-query suitable for use with pdsh
    • fixed binary file uploads and bcfg2-admin pull
    • removed spurious -q in
    • Improve client error message when entries are incomplete (print missing fields)
    • child process management fix in server
    • dynamic reporting system tb fix
  • 0.9.5pre2
    • changed django reports admin to dev e-mail address
    • Add secondary config file for webservers (so that webservers don't need access to bcfg2.conf)
    • updated init script for agent mode
    • Add support for altsrc bindings to TGenshi
    • Implementing selective forking server, which runs read-only requests in child processes. Should dramatically improve scalability
    • merge realname into path for altsrc templates in TCheetah
    • Switch default to RPMng/YUMng (RPM/Yum are still around just not enabled by default)
    • quiet down RPMng a little (patch from lueningh)
    • Implement bcfg2-remote -H -
    • Add a realname attribute in altsrc bound entries and add TCheetah support
    • Add default attribute to basic group in default config
    • Fix use of altsrc when using Package entries with file attributes
    • Improve error handling in bcfg2-admin (Step towards resolving Ticket #469)
    • Switch DebInit? to use invoke-rc.d (Resolves Ticket #434)
    • Fix bcfg2-info build command
    • add altsrc to schema
  • 0.9.5pre1
    • Reporting System Features:
      • Hosts may be "expired" to prevent them from showing up in reports. Data still exists for them, so if one views a calendar date before they were expired, they'll still show up.
      • requires action The config file for reports has changed locations from the inappropriate location inside the bcfg2 python module, to be part of bcfg2.conf. Please look at the included example bcfg2.conf to see the new format
      • requires action Reporting System may be installed at any URL, that is, it can be installed in a sub directory and not at the root of a virtual host. Django 0.96 is now required.
    • Bcfg2 Agent Mode:
      • Initial release of this functionality
      • Client may run in an idle mode waiting for reconfiguration command from the server
      • Use bcfg2-remote to initiate a client's reconfiguration operation
      • Uses fingerprint based authentication for https xml-rpc connection
      • Useful for instant reconfiguration of client without ssh'ing to host
      • still need to add daemonize code and init script support (next pre)
    • Binary diff uploads now work properly
    • Added the TGenshi plugin (contributed by Jeff Ollie)
    • Added the SGenshi plugin
      • is intended for use as a structure, like bundler or base.
      • only uses the genshi xml format
      • results in completely programmable bundles
      • this could eventually replace both bundler and base, as it is
      • more powerful
    • Added entry remapping support
      • with the addition of an extra altsrc attribute, entries can be remapped to a different source.
      • For example, if you have the same config file with different paths on different architectures, you can add altsrc to use the same plugin and repository on all architectures. ie: <ConfigFile name='/etc/inet/hosts' altsrc='/etc/hosts'/> will cause all linux and solaris systems to use the same plugin source for data on all clients.
      • This feature was motivated by the need manage a bunch of config files using the same template