Forum Replies Created
-
Posts
-
You are able to access the nodes by adding each other’s public ssh keys into the slice, but the individuals whom did not create the slice will not be able to see the slice via the api, this is a feature that is on the road map but is currently not implemented.
1 user thanked author for this post.
Hello,
A way to run a python file can be to create a code cell on the ipynb notebook and type:
“%run <relative_path_to_python file>.py”alternatively you can open a terminal and run your python file as “python <python_file_name>.py” (be sure to be in the correct directory)
hope this helps
hello, has this issue been resolved, if not could you try to use an in-private window to view the page?
Hello,
there should have been an update in the ticket earlier today, to summarize: a solution to this request is coming very soon and just needs to be added to the fablib interface. There might be a beta-release today or tomorrow. You can ask for more details in the help portal request
1 user thanked author for this post.
Hello,
Are you able to login to the fabric portal?
https://portal.fabric-testbed.net/loginhello,
this looks like the configuration for your ssh keys failed, Have you run the configure_enviorment, and the hello fabric notebooks in the fabric_config folder? if you have not please refer to the following steps: https://github.com/fabric-testbed/teaching-materials/blob/main/SSH%20Config%20File.md#for-jupyter-hub
and them run the Hello fabric notebook to test if the configuration was successful, then you can run the experiments
This may indicate that you may be having problems with the SSH key setup, have you tried running the “ConfigureEnviorment” and “HelloFabric” notebooks on the “fabric_config” directory?
The configuration is fine and should work, this error looks similar but it is different, this error occurred because the original slice and this new slice you are trying to create have the same name, you can ether close the previous slice via the portal under “experiments” or if you are still working on the same assignment, just clear, reset notebook and re run the “ipv4 routing” notebook via the fast-forward or reload buttons on the notebook
No problem, you can run the assignment once the slice status shows as “stableOK”, also in the future please use the “Fabric Educators” forum for future questions regarding these sets of experiments
Hello,
please try replacing the following values on the second cell in the ‘createslice’ notebook
“
cores = 2
ram = 2
disk = 10“
<br style=”font-weight: 400;” />
My appologies, What the problem is with the path is that it is missing a “/” before work when the path was set,
export FABRIC_BASTION_SSH_CONFIG_FILE=${HOME}’/work/fabric_config/ssh_config’
not
export FABRIC_BASTION_SSH_CONFIG_FILE=${HOME}’work/fabric_config/ssh_config’
There path on the output shows “/home/fabricwork/fabric_config/ssh_config”, I believe the correct pathing should be “/~/work/fabric_config/ssh_config” or “/work/fabric_config/ssh_config” the directory “fabricwork” should not be there, is this a folder you created?
I’m not sure if this might be the case, but you may have accidentally saved the notebook after running it, the kernel might be shut down, but the state (visually) remains there, you can try to hit the fast-forward button next to the “markdown dropdown” to shut the kernel down and re-run the notebook at the same time or left-click and ‘clear output’ to see it visually different, do let me know if this was not the problem, and if that is the case could you show me a picture of the interface i spoke of before and any error messages you encounter?
In terms of the path made: let me know if any other items were modified in the configure.ipynb notebook if you are still having problems after changing the following lines, i believe the only problem with the pathing might be the second line where the “ssh_config file” was changed.
the following are the default paths:
export FABRIC_BASTION_PRIVATE_KEY_LOCATION=${HOME}/work/fabric_config/{bastion Key name}
export FABRIC_BASTION_SSH_CONFIG_FILE=${HOME}’/work/fabric_config/ssh_config’
export FABRIC_RC_FILE=${HOME}’/work/fabric_config/fabric_rc’Hello Yuvaraj,
could you provide an image of the environment setup you used to create the path?, regarding the kernel there should be a button on the top left bar in the shape of a circle with a square in the middle, in this interface you should be able to see the kernels that are currently running, and you should be able to shut the intended kernel there.
