Engineering with a "Pseudo" Development Environment

Engineering Ansible collections and roles in the RWS Domain/DC is termed as “engineering light” due to its use of a “pseudo” development environment. This setup poses specific challenges such as limited access to resets.
Categories:

The Ansible development environment within the RWS Domain/DC is recognized as a “pseudo” environment for two primary reasons. Firstly, performing resets and snapshots of VMs is not straightforward. These actions require a formal request to the infrastructure team via a TopDesk change request, which typically takes a minimum of one day to address. For intensive Ansible engineering work, the capability to reset the environment multiple times per day is vital.

Secondly, this environment is shared among various engineers, including those not in the GIS Platform team. This can result in considerable periods of unavailability, sometimes extending for a week or more.

Additional Information

For additional insights and guidance:

  • Discover the unique Ansible project types within the C2 Platform approach by visiting Ansible Projects.
  • RWS adopts an “open, unless” policy, leading to the GIS Platform’s Execution Environment (EE) being included in the GitLab Open Source Program. This enables access to GitLab Ultimate.
  • Understand the critical differences between operating (using) and engineering with Ansible here.
  • Development Environment: Experience unparalleled flexibility and productivity through local development, a reality realized by embracing the "open, unless" approach.

Last modified December 30, 2024: rws engineering light #97722 RWS-1103 (98310f6)