Forum Replies Created
-
Posts
-
This notebook will be removed from the upcoming update to the Jupyter Notebooks. As Hussam said you do not need to run it, everything should ‘just work’ so long as you use DNS names and not IP addresses.
In general the error you see is because host’s own name is not in /etc/resolv.conf (you can add it there). This error is harmless.
1 user thanked author for this post.
Your *bastion* key is not properly set up. No other notebooks will execute properly until you can run this notebook all the way through. You can try to troubleshoot your setup – make sure that ~/work/fabric_config/fabric_rc file has a variable declaration
FABRIC_BASTION_KEY_LOCATIONthat points to the correct file – this is the most likely problem.Alternatively you can regenerate a bastion key pair and try from the beginning:
- Please go to the FABRIC portal click Experiments -> Manage SSH keys
- Select the ‘Bastion’ tab and generate a new Bastion key pair.
- Download both the public and the private parts of the keypair
- Copy the private part of the key pair into the ~/work/fabric_config/ directory in your Jupyter Hub (assuming you are using the Jupyter Hub)
- Note that in the file browser in Jupyter Hub ~/work/ is not visible, which is fine – you can simply select fabric_config and drag and drop the key file in there
- Re execute ‘Configure Environment’ notebook
- Making sure to update the path to the bastion private key with the new name
- Re execute ‘Hello FABRIC’ notebook start to finish and make sure it completes
Here is the article I promised:
– https://learn.fabric-testbed.net/knowledge-base/fabric-nvme-drives/
1 user thanked author for this post.
Also we do provide images with Docker pre-configured. There is a notebook in the examples that shows how to list available images, the docker ones are easy to tell apart since they have the word
dockerin them.You can safely ignore this – it is not an error, but a FutureWarning – we will update our code to avoid it in the future.
FacilityPort is a special permission generally not granted to educational classes. Did you create a slice JSON file yourself under Tutorials project and then give it to your students to instantiate in the portal using your class project?
I believe you continue to have problems with your ssh key setup. Have you been able to successfully run Hello FABRIC notebook start to finish?
Hello @yoursunny,
Let me put together a short learn article on this subject (with a table, like you ask). The NVMes in each site are indeed the same, but they differ across sites. They are all read-optimized 1TB models though.
Your bastion SSH key is not properly set up. There are several possibilities:
– You did not create the bastion key in the portal
– You did not install the private part of the keypair into the Jupyter Hub
– You did not put the correct name of the private key into the configuration when running ‘Configure my environment’ notebook
This error can be ignored – there’s a missing binary in the container you are using (which container type did you select?)
You can proceed to hello fabric tutorial.
The error message shows that they are there. I suggest restarting your container to be sure you do not have some cruft.
File->Hub Control Panel->Stop container -> wait … -> Start container
It appears you copied extra characters ‘<‘ and ‘>’ together with your project ID. The Project ID field actually has a useful copy-to-clipboard button to help avoid mistakes like this.
Your environment does not appear to be set up. Please be sure to run ‘Configure your environment’ as well as ‘Hello FABRIC!’ tutorials first. Until those succeed other tutorials will not work.
In general please be sure you are familiar with the articles in this documentation section:
