[WSO2Con USA 2018] Applying Agile Software Development Principles to WSO2 Product Configuration Management Processes
1 like254 views
Eagle Technology Group, a tribal-owned IT company, applies agile software development to enhance WSO2 product configuration management processes. They implemented a new approach to build deployable WSO2 nodes, focusing on maintaining consistency in configurable items, utilizing a shared repository, and treating configuration as code. Their efforts have resulted in successful software deployments and validation to operate systems on a cloud platform for a Department of Defense client.
[WSO2Con USA 2018] Applying Agile Software Development Principles to WSO2 Product Configuration Management Processes
- 1. Sr Enterprise Systems Engineer/Developer Eagle Technology Group, LLC Applying Agile Software Development Principles to WSO2 Product CM Processes Neil Custer
- 2. ● Information technology engineering and integration ● Enterprise architecture, virtualization, data center solutions ● System and application design, development, deployment and maintenance; agile/scrum practice ● WSO2 Preferred Partner ● Microsoft Gold Partner ● Average of 18+ years of technology experience per employee ● Eagle TG is owned by the Native American Modoc Tribe of Miami, Oklahoma -- SBA Certified 8(a) entity Eagle Technology Group, LLC
- 3. Configuration Management ... a systems engineering process Primary Goal: Maintain consistency of configurable items which affect - product’s performance - functional capabilities - physical attributes ... while taking into account operational concerns Had this all figured out, until --
- 4. ● Forced us to completely change our CM process ● Previously captured CM changes by mods to config files post-product deploy ● Puppet scripts provided no help because-- ● Isolated environments with little/no tooling-- no Internet access; no special tools (e.g. Puppet, Ansible, Chef…) ● Looked for new way to “build” deployable WSO2 nodes … advised to “script everything you can” Along Came WUM
- 5. 1. Build/Maintain a shared repository of Configurable Items* ○ Provides advantages for team contribution ○ Centrally track changes to all Items (repo history) ○ Allows for branching while testing changes to CI 2. Configurable Items (specific to WSO2 product configuration) ○ Dynamically modified configuration files ○ Server certificate keystores befitting the deployment domain ○ Other artifacts as required CM using Software Dev Principles * Any component of an infrastructure under Configuration Management
- 6. 3. Monitor, Download, Test new WSO2 Product Releases ○ Interrogate (WUM) for product updates (pull) at a regular interval/schedule ○ Download/persist the unconfigured release to an “isolated zone” ○ Backup previous instance of fully-configured product instance ○ Deploy new product release using configuration items ○ Test fully-configured product for required capabilities ○ Modify configurable items per any new findings ○ Repeat previous three steps until capabilities tests pass CM using Software Dev Principles
- 7. ● Approach views Configuration as “Code” ● Shared Repository ● “Self-Installing” ● Environmental configuration variances handled thru environment variables ● Build jobs based on desired schedule ● Baseline deploy scripts for each product ● CI/CD, Test, Repeat ● Run the product as a service Software Development Principles
- 8. Standardized WSO2 Node “Deployers” Configurable Items (.xml .jks) Environmental Samples (unit files, env scripts, …) WSO2 Product Source (.zip) Placeholder Backups Installation Scripts (.sh)
- 9. Deployer - A single consolidated, distributable, compressed file (.zip) which features: 1. Folder structure for enabling fully-configured product deployment 2. README.txt file outlining basic environmental requirements for scripts 3. Script files for carrying out the product installation (RHEL/CentOS) 4. Configurable items for the product (config .xmls + keystores + db driver libs + other) 5. WSO2 Product Source (.zip / .tar.gz) Standardized WSO2 Node “Deployers”
- 10. Standardized WSO2 Node “Deployers”
- 11. Standardized WSO2 Node “Deployers” Files Folders Size Pct Installation Scripts 6 1 4903 0.0013% Configurable Items 20 12 2526771 0.6579% Environment Samples 3 1 1449 0.0004% WSO2 Product zip 1 1 381538252 99.3404% Placeholder 1 1 56 0.0000% Totals 31 16 384071431 100.0000%
- 12. ● Among the first systems to get a fully operational suite migrated to our DoD client’s managed cloud platform ● Received suite validation to operate the systems ● Early success has led to the granting of authority to implement additional features, capabilities, and products ● Now being asked to provide an updated enterprise identity management solution ● Able to show many advantages of open source software yet to be realized by other US Government agencies Recent Outcomes