EpiJunkie

chyves-demo-clone-use

by EpiJunkie 2016-08-21 06:41:15 UTC
  • FreeBSD / csh / xterm
  • 320

chyves info

chyves info -zvtc

That's what I want displayed, let's make it permanent.

chyves global set default_info_flags=-zvtc

chyves info

mv /chyves/dozer/guests/img-guest/img/FreeBSD-10.3-RELEASE-amd64.raw /chyves/dozer/guests/img-guest/img/FreeBSD.img

chyves info

chyves list clones

chyves list bridges

Next command we will clone 'obsd' into three true ZFS clones ('-c') with unique properties ('u').

chyves obsd clone lvl1_clone1,lvl1_clone2,lvl1_clone3 -cu

chyves info

You can see they have unique properties and are clones of 'obsd'.

chyves list clones

chyves l1_clone2 disk add 3g

chyves info

Next command we will clone a clone into three true ZFS clones ('-c') with exact properties ('e').

chyves l1_clone2 clone lvl2_clone1,lvl2_clone2,lvl2_clone3 -ce

chyves info

Next we will delete one of those level 2 clones but keep the network associations because other clones share the same tap interface.

chyves l2_clone1 delete keepnet

chyves list bridges

For the next set of clones, lets assign them to bridge2.

chyves network bridge2 default

chyves list defaults

Let's also create these clones as independent clones which do not rely on the parent clone.

chyves list clones

Also keep in mind, these names are irrelevant, the 'chyves list clones' command uses the 'origin' ZFS property
to figure out which clones belong to which parents.

chyves img-guest clone independent_1,independent_2,independent_3 -iu

chyves info

chyves list clones

As you can see the independent clones do not show up because these are not true ZFS clones. They are their own.

chyves list bridges

Even though bridge2 is set as the default, the clones were not joined to the default bridge, they mimic what th
eir parent clone configuration. Each tap is recreated on the clone and joined to the same bridge as the parent, no matter how co
mplex the parent network design is.

More by EpiJunkie