Projects are boundaries
How JailOps separates projects: what a project keeps apart, why another project is treated like an external host, how the firewall closes projects to each other, and how two projects are connected with addresses on both sides. What a project is not.
What a project separates
Names, quotas, networks, firewall.
A project is the unit you give to a team, a customer or an application. It has its own jails, its own networks and storage grants, its own address sets and firewall policies, and its own quotas and access. A name in one project means nothing in another: two projects can each have a jail called web.
There is no default project. Every command acts in one project that you choose with --project or jailops project switch, so what a command touches is never implicit.
Closed to each other
One rule, no exceptions.
Every jail gets a PF anchor, jailops/PROJECT/JAIL. Each project also has an anchor with the project's mandatory policies and a table of the subnets of the other projects, and each network has its own. A jail without a policy still gets an anchor with the isolation in it. Traffic between projects is let through only by a rule you wrote.
That rule has a consequence that makes the model small: another project is treated exactly like an external host. A rule or an address set can name a jail of its own project (jail:web), but never a jail of another project. What crosses the boundary is an address, nothing else.
The project can also have mandatory policies, a floor: a jail's own policies can add rules but cannot weaken the project's defaults.
Connecting two projects
Addresses, written on both sides.
The web jail of project blog (10.30.0.5) needs the database in project shop (10.20.0.10). Each project says its own half, with the address of the other:
$ jailops firewall address-set create blog --address 10.30.0.5 \ --comment "the web jail of project blog" $ jailops firewall policy create db --default-in deny --default-out allow $ jailops firewall rule add db in --from set:blog --port 5432 \ --comment "the web jail of blog"
$ jailops firewall policy create out-db --default-in deny --default-out allow $ jailops firewall rule add out-db out --to 10.20.0.10 --port 5432 \ --comment "the shop database"
It is two commands where one could have been, and that is the point. Each project's firewall can be read and reviewed on its own. Nothing in one project changes when someone edits the other, and no command writes a rule into a project it was not asked about. The comments say why each address is there.
For a PostgreSQL jail from the catalog, jailops app allow db --from set:blog takes the same set: the app's project lets the addresses in, and the grant adds the role and the pg_hba.conf lines.
Or put them together
The question to ask first.
Do the two things need to talk to each other as one system, a web jail and its database, a forge and its runners? Then they belong in the same project. In one project they reach each other by name (jail:web), the rules follow the jails when their addresses change, and nothing has to be written out. Use two projects when the two are separate on purpose: different teams, a customer, a test setup next to production.
What a project is not
Be exact about the boundary.
- Not a kernel boundary. Jails share the host kernel. A tenant that needs isolation judged on its own terms needs a host of its own: a separate pool splits storage and operations, not the kernel.
- Not isolated from storage a jail was given. A jail with
zfs_delegationor a host directory reaches that storage. - IP traffic is what the firewall filters. Jails hold single addresses behind the host and the host pins their ARP and neighbor entries, so forged ARP or router advertisements from a jail change nothing; the firewall article has how policies and address sets are written and read.
More articles
Jail updates without cron
Replace the nightly script that upgrades every jail: automatic jail upgrades per image, with a health check, a rollback and a record of every run, what they leave alone, and how a new FreeBSD release comes in.
Read the article: Jail updates without cronJail search and shell
Ctrl+K, a few letters, Shift+Enter: find a jail by name, label or app and open its shell. Labels that filter the jail list, bash in new jails, and the jailops command next to every step.
Read the article: Jail search and shellGetting started with the JailOps CLI
Root on the host, the command line and nothing else: install JailOps, build an image, create a network and a jail, reach it by name, snapshot it, open a port and install an app.
Read the article: Getting started with the JailOps CLIJailOps on a netcup server, with IPv6 that stays up
A /64, a router pair and a FreeBSD default that drops their probes. How every jail gets its own IPv6 address on netcup, and the one sysctl that ends the random unreachable alerts.
Read the article: JailOps on a netcup server, with IPv6 that stays upOne small cloud server, many services, solid IPv6
Run your database, web tier and workers on one low-cost server, each jail with its own IPv6 address, and fix the alerts a shared /64 causes with one sysctl.
Read the article: One small cloud server, many services, solid IPv6Write your own app: memcached, from package to catalog
Turn a small FreeBSD package into a JailOps app: the definition line by line, the offline check, a local install, the five traps, and the pull request that puts it in the catalog.
Read the article: Write your own app: memcached, from package to catalogFrom catalog to running service in one command
Install nginx from the app catalog with one command, see each of its steps, and find the data, the configuration, the logs and the snapshot afterwards.
Read the article: From catalog to running service in one commandA firewall you can read
Policies, address sets and jails by name (jail:web), each with a comment, so the firewall can be reviewed by someone who did not write it.
Read the article: A firewall you can readPostgreSQL and git, closed except for who needs them
Close a database and a git server, then let in exactly the web jail and the office, with a comment on every entry.
Read the article: PostgreSQL and git, closed except for who needs themThe life of a jail
A jail starts at boot only when you declared it with --autostart. Why JailOps does it this way, how the order is decided, and how to see it with jailops boot.
Read the article: The life of a jailTab completion for jailops
Press Tab and get the names of your jails, networks and firewall policies, even on another host. How to install and turn on completion in bash, zsh and fish.
Read the article: Tab completion for jailopsTest the firewall before you trust it
Ask the firewall whether a connection would pass, and why, before you try it. Read the answer, put it in a script, and know what it cannot tell you.
Read the article: Test the firewall before you trust itSee a connection before it happens
Pick a From and a To, a protocol and a port, press Run, and see the connection flow through the firewall: what passes, what stops it, and which rule decides.
Read the article: See a connection before it happensLimit what a jail can use
Give a jail a ceiling for memory, processes, CPU, disk, firewall states and bandwidth, one command each, and know what happens when it reaches it.
Read the article: Limit what a jail can useStop every jail cleanly when the host shuts down
A host that reboots should stop its databases before it stops the disks. How JailOps stops the jails in order, and how to start them in order again.
Read the article: Stop every jail cleanly when the host shuts downOne line in pf.conf
The host's firewall stays yours. JailOps asks for one line, and everything for the jails lives below it.
Read the article: One line in pf.confWhat the host tells you by itself
A pool that reports an error, an uplink that goes down, a jail that reaches a limit: they show up in the event stream by themselves.
Read the article: What the host tells you by itselfNetworks the host controls
No bridge, no DHCP. The host hands out the addresses, gives each jail a link of its own and is the router, so jails cannot see or impersonate each other.
Read the article: Networks the host controlsVolumes: data that outlives a jail
Keep the data in a volume and the jail disposable. One volume can be attached to several jails, has its own snapshots and its own backup.
Read the article: Volumes: data that outlives a jailBack up volumes once
One copy of a volume, however many jails use it. Leave volumes out when you want to, bring them back with the jail.
Read the article: Back up volumes onceA private Docker registry
A registry of your own with users in a file: one jail, docker-registry and docker-auth, htpasswd for the passwords, the images on a volume.
Read the article: A private Docker registryNames for jails
A jail is reached by its name inside its project: db.shop.internal, or just db. Create a jail and its name is there; delete it and the name is gone.
Read the article: Names for jails
Try it on one server.
Try the console from the screenshots, install on a clean FreeBSD 15.1 machine, or add JailOps to a host you already run.