You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`-- pallet_project
|-- project.clj
`-- src
`-- com
`foo
|-- nodes.clj ; nodes, servers, and group definitions
Assume you have a group specification in nodes.clj such as:
(def
^{:doc "Defines a group spec that can be passed to converge or lift."}
backend
(group-spec
"backend"
:extends [backend-server]
:node-spec backend-node))
Using the Leiningen plugin will require you to specify a fully qualified namespace to the group created by group-spec. For instance, to start a single backend running in your AWS cloud, you could use:
When using a node-list computing service provider, you must still specify the full path to the Clojure object that defines the group you want to affect change on, but the name specified in the node-list must match the name given to the group-spec.
For example, assume I have an image running on my local machine in VirtualBox. I can add the following into ~/.pallet/config.clj
(defpallet
;; A list of Virtual Box images
:services
{:vbox {:provider "node-list"
:node-list [["my-vm" "backend" "192.168.56.101" :debian]]}}
)
To lift the my-phase on that virtual machine using Leiningen requires the following command:
As usual, the -P vbox defines the compute service. In this case, it tells Leiningen to use the existing nodes given in the node-list. Specifying com.foo.nodes/backend tells Leiningen which group you want to lift to. When that is happening, Pallet runs through all of the nodes listed in the provider and matches the second parameter ("backend" in this case) to identify which nodes actually correspond to the target group.
The text was updated successfully, but these errors were encountered:
When reading http://palletops.com/doc/how-tos/using-pallet-with-existing-servers/, it wasn't clear to me how the group name should be specified. Especially when using the lein plugin. I recommend adding something like the following:
Assume your lein project looks something like:
Assume you have a group specification in nodes.clj such as:
Using the Leiningen plugin will require you to specify a fully qualified namespace to the group created by
group-spec
. For instance, to start a single backend running in your AWS cloud, you could use:When using a node-list computing service provider, you must still specify the full path to the Clojure object that defines the group you want to affect change on, but the name specified in the node-list must match the name given to the group-spec.
For example, assume I have an image running on my local machine in VirtualBox. I can add the following into ~/.pallet/config.clj
To lift the my-phase on that virtual machine using Leiningen requires the following command:
As usual, the -P vbox defines the compute service. In this case, it tells Leiningen to use the existing nodes given in the node-list. Specifying com.foo.nodes/backend tells Leiningen which group you want to lift to. When that is happening, Pallet runs through all of the nodes listed in the provider and matches the second parameter ("backend" in this case) to identify which nodes actually correspond to the target group.
The text was updated successfully, but these errors were encountered: