what began as a personal fork of Ansible-NAS to replace FreeNAS, was rewritten and expanded to include other devices and services in my homelab.

ejsb is a grandiose name for the collection of learning, experimentation, and opinionated tooling that i've written to manage my personal infrastructure. this project is about learning and documenting what i've done to share knowledge.

inspired by khuedoan/homelab, i am rewriting it again.

...caution, this is a work in progress, breaking changes ahead...

• asb: (aka Ansible Systems Builder)

• nrf: playing with Nornir + FastAPI to create an asynchronous network API

...are being rewritten

• from Dave Barroso's most-excellent Building Scalable Tooling presentation (emphasis mine):

  Why do we want automation?

  Reliability

  • Does our software do what we claim it does?
  • Can we change it without breaking anything?
  • Test the interactions with the system from a user perspective first, then add tests to simulate (fixed) bugs

  Consistency

  • Avoid cognitive overhead which can lead to bugs, wasted time, and bikeshedding
  • Adopt frameworks and best practices
    • Choose a framework and stick by it unless strictly necessary
    • If you need external services, standardize and adopt them across the board (i.e., databases, message buses, etc)
    • Adopt a coding style (or an opinionated linter) to minimize arguments about style (i.e., black)
  • The goal is to be able to collaborate on multiple projects without having to pay a very expensive context switch cost or waste time arguing about tabs vs spaces or MySQL vs postgres

  Maintainability

  • Readability
    • Code is read more often than it is written so optimize for reading
  • Abstractions
    • Break down your code into different layers of abstraction
    • Each abstraction should be concerned about solving the problem presented in its layer
    • Each abstraction should provide a stable contract so other abstractions can consume it
    • Abstractions are good for the separation of concerns
      • Given the request of deploying a service, can my software identify which parts need to be configured and which parameters need to be set?
      • Given the right input, is my service generating the correct configuration?
      • Given some configuration, is my library able to deploy it correctly to the device?
  • Developer's tooling
    • A developer should have tooling to:
      • Help write code
        • autocompletion, inline documentation, refactoring, etc...
      • Inspect and explore what the program is doing during its execution
      • Observe how the system behaves in production

  Speed is not a goal but a consequence

• khuedoan/homelab

• Ansible-NAS

• Ansible for DevOps

• DebOps

• JulioPDX Nornir+Fastapi

• Sebastian Ramirez

• network MOPs as automated workflows

• how to build a network automation stack with nornir, napalm, and netbox