-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a quick guide for setting up the remote (and LXC) spawners #5838
Comments
I am mostly leaving this for the future where we improve some of the new user experience before @wsakernel's output gets lost deep in the comments of a merged pull request. |
This Documents some crucial steps for a new user of the remote spawner plugin. Reference: avocado-framework#5838 Signed-off-by: Cleber Rosa <[email protected]>
This Documents some crucial steps for a new user of the remote spawner plugin. Reference: avocado-framework#5838 Signed-off-by: Cleber Rosa <[email protected]>
Thanks for this @pevogam. I've added your text as close to verbatim as possible to #5846 |
I actually only meant to keep track of this for now for post-LTS since I did not want to add any additional issues to the respective milestone but thank a lot for adding it! |
This Documents some crucial steps for a new user of the remote spawner plugin. Reference: avocado-framework#5838 Signed-off-by: Cleber Rosa <[email protected]>
solved in #5846 |
Let's reuse @wsakernel's effort in documenting some crucial steps for a new user of the remote (and LXC) spawners. Instructions are as follows:
First add the slot to your avocado config file:
Then you need a JSON file of the same name as the slot. Its contents are the command line parameters of the
remote_login
function of classremote
, e.g.:Final important detail: the remote site also needs avocado installed.
The text was updated successfully, but these errors were encountered: