Building a Devops Engine

Mike's Notes

Here are some working notes from my current job on Pipi 9.

Resources

• https://en.wikipedia.org/wiki/DevOps_toolchain
• https://en.wikipedia.org/wiki/DevOps
• https://developer.ajabbi.com/eng/9/report/roadmap.html
• https://www.blog.ajabbi.com/2024/12/pipi-builld-roadmap.html
• https://en.wikipedia.org/wiki/Objectives_and_key_results
• https://itrevolution.com/product/the-devops-handbook-second-edition/
• https://www.blog.ajabbi.com/2019/03/next-on-list-is-devops.html

Building a DevOps Engine

By: Mike Peters
22/02/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Tonight, I started back on the DevOps Engine (dvp) after several years of absence (March 2023, to be exact).

The engine is based on The DevOps Handbook, which was written by Gene Kim, Jez Humble, Patrick Debois, and John Willis and published by IT Revolution.

"A DevOps toolchain is a set or combination of tools that aid in delivering, developing, and managing software applications throughout the systems development life cycle, as coordinated by an organisation that uses DevOps practices.

Generally, DevOps tools fit into one or more activities that support specific DevOps initiatives: Plan, Create, Verify, Package, Release, Configure, Monitor, and Version Control." - Wikipedia.

First, I had to solve many other dependencies to determine what needed to be done on this engine. Then, in December 2024, I could create a reasonable roadmap for Pipi, which has been made public and works.

I'm using the published roadmap as if it were a product of the DevOps Engine, and I'm working backwards to correct the necessary process model.

The key priorities are high quality, fast flow speed and automation.

The data model is designed to maximise flow.

Everything is pinned back to the NameSpace Engine (nsp), and any rendering uses the existing working engines.

There is a constant interdependency between these engines, which maintain each other.

The DevOps Engine deals with flow. Each of the 8 steps will have its own engine, often working with other engines, such as the existing Feature Flag Engine or the Canary Engine.

I am already tweaking the roadmap, replacing "Goal" with "Function" and "OKR" (Objective and Key Results).

The Versioning Engine (ver) will also be impacted, as each engine's version increments with DevOps updates and flows onto Pipi's versioning.

Version logging has been off since Pipi 7 and will be turned on once automation is in place. I don't use version control; I keep dated drawings in ring binders. However, version control will become necessary as complexity increases, especially when teams are established.

Here are some of the initial options for the model in the DevOps Engine.

Options

• WBS
• Step
• Priority
• Flow Status
• Started
• Completed
• Time Taken
• Verb
• Function
• OKR
• Scope
• Task
• Assigned
• WIP
• Batch Size
• % Resource Busy

WBS

Example: "1.2".

Step

1. Plan
2. Code
3. Build
4. Test
5. Release
6. Deploy
7. Operate
8. Monitor

Priority

• Low
• Medium
• High

Flow Status

• Yet to Start
• Underway
• Completed

Started

24/12/2024

Completed

25/12/2024

Time Taken

Example: 6,000 seconds.

Verb

• Edit
• Make
• Render
• Test

Function

Example: "Workspace".

OKR

Example: "Workspace Upgrade 3".

Scope

• Name of namespace object.

Task

Example: "Export the Google Sheet to DevOps engine".

Assigned

• Name of person/team/robot responsible.

WIP

• Example: 5

Batch Size

• Example: 1

% Resource Busy

• Example: 85%