Configuration Management in CWIC Archie Warnock – A/WWW Enterprises Lingjun Kang – GMU Eugene G. Yu - GMU

Outline Code management and versioning System deployment practices Backups Runtime Environments (Ops vs Dev)

Code Management & Versioning Separate source code components – Mediator – Connectors (multiple) Each component may have separate configuration Testable as standalone Java applications Source stored in source code repositories – One for each component – No explicit version numbers or tags (ie, delivery dates only)

System Deployment Practices Deploy jarfiles to Tomcat on DEV first Local and remote testing on DEV Manually migrate jarfiles from DEV to TEST (but maintain config files specific to the TEST instance) Availability for partner testing, as desired Manually migrate jarfiles from TEST to PROD (but maintain config files specific to the PROD instance) No regular release schedule because changes are relatively infrequent at this point – manual migration is not difficult

Backups Deployed instances and associated config files are also migrated into git repositories USGS provides system backup to separate media of Tomcat file tree, user files, git repositories and virtual host images

Runtime Environments (PROD, TEST, DEV) Each environment runs on a separate virtual machine under Tomcat Processes owned by generic cwicdev user Small variations in config files for each instance (generally, file names and/or locations) Migration path DEV -> TEST -> PROD Not currently using build or deployment tools