This cookbook sets up x2go-servers.
There are two kinds of servers (and therefor at least two recipes):
- x2goserver where users can connect to with x2goclient and work remotely. The recipe x2go::server aims to do this.
- X2Go Thinclient Environment servers providing the infrastructure to boot diskless clients from network and start x2goclient. The recipe for that is x2go::thinclientenv.
Not that the X2Go discourage running both roles on one server. And we have no reason to say otherwise.
This cookbook is currently developed on Debian 7.1 (wheezy). It should also work on Ubuntu LTS 12.04 or higher but thats speculation.
Supporting RPM-based distributions is currently not on my roadmap but patches are accepted.
The recipes install what they need.
To provide the netboot environment for the thinclients, the thinclientenv-recipe needs nfs- and tftp-cookbooks.
To make your diskless clients boot the X2Go-TCE you have to configure your dhcp-server to send them to the server with the x2go::thinclientenv recipe. That step is not (yet) done by the x2go-cookbook.
Key | Type | Description | Default |
---|---|---|---|
['x2go']['tce']['basedir'] | Path | Where to install the chroot and nfs-root for the thinclient-environment | /srv/x2gothinclient |
['x2go']['tce']['rootpassword'] | String | Hashed version of the root password for the thinclients. Can be nil. | [nil] |
['x2go']['tce']['extra_packages'] | List of string | Extra packages to install into the environment | nil |
['x2go']['tce']['sessions'] | List of hashs | Sessions for x2goclient. For example (as json): [ { "name": "ltsp02", "command": "KDE", "host": "ltsp02.bcs.bcs", "autostart": "true", "fullscreen": "true" } ] |
[] |
['x2go']['tce']['config']['sessionedit'] | Boolean | Whether users are allowed to edit the sessions on the thinclients. (Changes are lost on restart of the client.) | true |
The default recipe currently does nothing.
{
"name":"my_node",
"run_list": [
"recipe[x2go::server]"
]
}
TODO
This is a public cookbook currently in the stove. So the usual github+opschef steps apply for now:
- Fork the repository on Github
- Create a named feature branch (like
add_component_x
) - Write your change
Write tests for your change (if applicable)Run the tests, ensuring they all passTest your changes:-)- Submit a Pull Request using Github
Authors: Arnold Krille [email protected] for bcs kommunikationslösungen
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.