Several designs as one

A deployment can hold more than one design, so designs that belong together, such as a site and its racks, are managed under one name. This chapter builds a second site in Germany with a rack in it, as one deployment called berlin-dc.

Deploy the site

1. Open tutorial/site_foundation in the catalogue, select Deploy, and choose your NetBox.

2. Leave New deployment selected and name it berlin-dc.

3. Fill in the variables:

   Variable	Value
   site_name	Berlin DC
   site_slug	berlin-dc
   region	Germany
   supernet	10.20.0.0/16

4. Select Plan: 2 creates, the site and its prefix.

5. Select Apply Changes.

Add the rack to it

1. Open tutorial/compute_rack, select Deploy, and choose your NetBox.
2. Under Deployment, select Change an existing deployment, or add this design to one, and choose berlin-dc. The deploy page says the plan adds the design to it.
3. Set rack_name to B1 and site_slug to berlin-dc.
4. Select Plan: 260 creates, the rack and its contents, with the 11 types adopted from the racks in Riga.
5. Select Apply Changes.

In NetBox, Berlin DC is in Germany, with rack B1 in it.

What each design owns

On the Deployments page, berlin-dc is one row: two designs, 273 objects. Open it. Each design in the deployment has its own section, with its own variables and sessions:

• tutorial/site_foundation owns 2: the site and the prefix.
• tutorial/compute_rack owns 271: the 260 it created and the 11 it adopted.

Each design is planned on its own. Redeploying the rack never deletes the site, and the site doesn't know about the rack. What they share, if anything, stays while either describes it. That independence is what lets you take a deployment apart one design at a time, which the next chapter does, and it's also why the order matters there.

Next, tear down and release.