-
Notifications
You must be signed in to change notification settings - Fork 262
Tutorial Fails with Client.Timeout #910
Comments
TLDR: I got it working. You need to specify a list of Controller implementation(s) to the Manager plugin using the Launch Infrakit INFRAKIT_MANAGER_CONTROLLERS=resource \
infrakit plugin start manager group resource vanilla simulator In another shell:
To verify:
For the record, it does not seem to matter which controller implementation you use when committing the group. For example, the commit will work if you use From my perspective, this issue may be closed unless you would like to target it against the docs. |
If you’d like to correct the docs that would be awesome! If not I’ll try
and take your notes and do it once I’m back.
Thanks for your work!
…On Wed, 26 Sep 2018 at 20:16, Robert Bergstrom ***@***.***> wrote:
TLDR: I got it working. You need to specify a list of Controller
implementation(s) to the Manager plugin using the
INFRAKIT_MANAGER_CONTROLLERS environment variable as well as add the
controller plugin to the plugin list. This changes the group command to
use the Stack interface instead of the Group interface. So to achieve
similar results in the tutorial, use the group/groups command to commit
the given group.yml file. Detailed commands are below.
*Launch Infrakit*
INFRAKIT_MANAGER_CONTROLLERS=resource \
infrakit plugin start manager group resource vanilla simulator
In another shell:
infrakit local group/groups commit -y ./group.yml
To verify:
infrakit local group/workers ls
ID LOGICAL TAGS
1537985111915511818 - custom.tag1=tutorial,custom.tag2=single-instance,custom.tag3=by-group,infrakit.config.hash=oskdoyfaewtrrmwlychnja3ejwz574ue,infrakit.group=workers,simulator=simulator
1537985111916528594 - custom.tag1=tutorial,custom.tag2=single-instance,custom.tag3=by-group,infrakit.config.hash=oskdoyfaewtrrmwlychnja3ejwz574ue,infrakit.group=workers,simulator=simulator
1537985111916885134 - custom.tag1=tutorial,custom.tag2=single-instance,custom.tag3=by-group,infrakit.config.hash=oskdoyfaewtrrmwlychnja3ejwz574ue,infrakit.group=workers,simulator=simulator
1537985111917523752 - custom.tag1=tutorial,custom.tag2=single-instance,custom.tag3=by-group,infrakit.config.hash=oskdoyfaewtrrmwlychnja3ejwz574ue,infrakit.group=workers,simulator=simulator
1537985111917927281 - custom.tag1=tutorial,custom.tag2=single-instance,custom.tag3=by-group,infrakit.config.hash=oskdoyfaewtrrmwlychnja3ejwz574ue,infrakit.group=workers,simulator=simulator
For the record, it does not seem to matter which controller implementation
you use when committing the group. For example, the commit will work if you
use pool instead.
From my perspective, this issue may be closed unless you would like to
target it against the docs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#910 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABlQJs_QPqcHhlXHrkPxspgYX-dQxiNKks5ue8SMgaJpZM4W5U1P>
.
|
If you following the tutorial here, you can provision an instance using the provided example file. However, continuing the example by committing a group fails with an error.
To reproduce
With infrakit started and using the provided group.yml file:
infrakit local group commit -y ./group.yml --log-debug-V 0 --log 5
Result
Comments
Outside of a potential regression, it seems as though the Group plugin is proxing for a real Controller implementation which does not exist in the tutorial setup. I can see some recent Controller implementations, but I am not sure which one to use in this case.
The text was updated successfully, but these errors were encountered: