Cookbook¶
Task-oriented recipes for adopting the SDK, ordered the way a real deployment
grows. They follow one fabric from its first tenant to confident day-2
operation — the commerce platform, a prod VRF, a 10.30.0.0/16 address
plan — so the recipes read as one continuous story, not twelve disconnected
snippets.
Every recipe takes one operator goal through the same arc — describe the desired state as a design, plan it against the fabric, push it, verify it through the read side. Every code block on these pages is executable and runs as a test in the SDK’s own suite; copy any recipe and adapt the names.
Recipes stay within the curated vocabulary;
where a position is not curated, the recipe shows the honest escape hatch
(.mo(), bind_dn(), static_path()).
Warning
These recipes are not production configuration.
They are purely illustrative — their only purpose is to help you learn the SDK progressively and understand how it works. They are not configuration recommendations and not architecture guidance: the names, addressing, and settings are chosen to teach the SDK, not to model a well-designed fabric.
For production, always follow Cisco’s official design guidance (Cisco Validated Designs) and engage a qualified data center network architect to design for your own environment and requirements. The project accepts no responsibility or liability for any misinterpretation or misuse of this material.
Provision — grow the deployment¶
Start here and read in order: each recipe adds a layer to the same fabric.