fabric:join — join a container to an existing fabric
] | [
] | [
] | [
] | [
] | [
fabric:joincommand can be used in either of the following scenarios:
- You have an existing fabric, A, and you want to join a standalone container to fabric A.
- You have two separate fabrics, A and B, and you want to transfer a container from fabric B to fabric A.
Table 10.31. fabric:join Arguments
| ||Displays the online help for this command.|
|Forces the provided container name to be used.|
|Specifies the profile to associate with the container after it joins the fabric. The |
|Registers the container with the fabric's ensemble, but does not install a Fabric Agent into the container. The container's configuration is not managed by the fabric and continues to behave like a standalone container except that it can be discovered through the fabric's ensemble.|
| ||The ensemble password for the fabric that you are trying to join. If you do not specify this option, you will be prompted to enter the password.|
| ||Specifies the local resolver policy. Possible values are: |
| ||If you select the |
| ||Specifies the minimum port number of the allowed IP port range. Default is |
| ||Specifies the maximum port number of the allowed IP port range. Default is |
| ||Specifies the URL of one of the Fabric Servers, specified in the format |
|Specifies a unique name for the container to use when joining the fabric. By default, the value of the |
fabric:join myhostA ishmael
myhostAis the hostname of a Fabric Server (you must connect to a Fabric Server, not an ordinary fabric container) and the container is assigned the name
ishmael. You will be prompted to enter the fabric's Zookeeper password.
karaf.nameproperty from the
etc/system.propertiesfile. The default setting for this property is
root. To avoid conflicts, you should either specify a container name or change the value of the
-pargument as follows:
fabric:join -p whaler myhostA ishmael
ishmaelis assigned the profile,
whaler, when it joins the fabric.
fabric:join -n myhostA ishmael