Introduction

What are ops?

  • we think of ops as operations as code
  • an op accepts inputs, produces outputs, and may have side effects
  • ops are designed to be:
    1. Composable: ops can be composed of smaller ops that are defined to run in serial or parallel
    2. Portable: an op's definition contains everything it needs to run and what inputs it expects, and ops leverage docker containers to run anywhere
    3. Distributable: ops can be referenced remotely, and can be remotely invoked
    4. Versionable: an op is defined in a simple yaml file which makes versioning easy using standard source control

What problems do ops solve?

  • automating manual technical operations
  • reliable and easy local development for software services
  • portable pipelines that live and change with the code they build and deploy
  • turning tacit operational knowledge into executable documentation
  • providing microservice development teams with an easy to understand, standard interface for operations

Roadmap

The long term vision being worked towards includes:

Characteristics

  • decentralized (p2p)
  • dependency free
  • vendor & platform agnostic

Deliverables

  • dependency free executable implementing a CLI, web UI, and http API

Contributing

We need your help realizing the long term vision of opctl!

Please open an issue or, fork us and submit a PR.

Support

Join us on Slack or open an issue

results matching ""

    No results matching ""