Converted all my documentation on incus projects into a Book (Cookbook)

Hi,

I have been spending time on learning about incus projects , trying to figure out how to build multi-tenancy system leveraging ZFS for storage, OVN for networking, re-using of same ip addresses across projects, ACLs for network isolations - to have a bare minimal multi-tenancy setup.

In the process of my discovery and learning curve, I have captured all the steps to the best of my knowledge, and I am now putting it out as a PDF file as a book titled “Incus Multi-tenancy A Beginner’s Guide”.

I never wrote a book by myself before. Nor do I have the money or time to pay for a professional technical writer to do it on my behalf. My end goal is to get my documentation out to the public, period.

So I created an account on my one man company’s name (fieldday.io) on github and uploaded my PDF file/book. github insisted me on picking up a License. So I picked up Apache2.

I have broken down my documentation steps into multiple tasks and not as chapters. The reason being, each task is a pre-requisite to be completed for the next/upcoming task. To that context, it is just a Cookbook.

I think I went overboard in putting way too many screenshots. Some people like such documentation (I do) and some people don’t. So please go easy on me if you don’t like the format :slight_smile: . But I sincerely hope my diagrams and explanation with regards to networking gives some clarity on how to go accomplish network isolation using ACLs.

Thanks goes to all members of this community in shaping the content and to all my incus gurus that I have mentioned at the end of this book.

Sincerely hope it would be of some use/help.

5 Likes