- This topic has 6 replies, 2 voices, and was last updated 1 year, 8 months ago by .
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC General Questions and Discussion › Resource issue – it’s not you it’s me … probably
Remove the host parameter. I think you’re thinking it’s the hostname of your VM but it’s actually the name of the worker node you’re telling it to land on and it doesn’t exist. The name of the VM is the name of the node I think combined with its sliver id.
Thanks Ilya – that looks like it worked. My only question would be about the example from which the host command was derived.
Can you please post the pointer, we will take a look.
Found it – it is under the “start_here” –> “Customizing nodes”
Code snip:
slice_name = ‘MySlice1′
#Create Slice
slice = fablib.new_slice(slice_name)
# Add node
node = slice.add_node(name=’Node1′,
site=’MAX’,
host=’max-w1.fabric-testbed.net’,
cores=4,
ram=16,
disk=100,
image=’default_ubuntu_20′)
#Submit Slice Request
slice.submit()
Right, we need to do a better job explaining it. Max-w1 is a valid worker node name, they are all named <site>-w<index>.fabric-testbed.net
But also you do not need this I don’t think. Experimenters only in rare cases need to place their VM on specific workers. Most of the time you want the placement algorithm do it for you so don’t specify host.
Future versions of this notebook will be more explicit about what host
parameter is for and how to use it.