[Paul Ruth]

That looks like a Windows path. Is this on a Windows machine?  I suspect this has something to do with the way you setup the Python virtual environment on Windows.  I’m not very familiar with Windows but will reach out  to one of the FABRIC student who previously got this working and see if he can help.

 

 

[Paul Ruth]

Those notes will eventually be here: https://learn.fabric-testbed.net/article-categories/release-notes/

If you want to install the API that is currently in the jupyter hub you can do this with the following command:

pip install fabrictestbed==1.0.3

[Paul Ruth]

There is a lot more key management functionality in development.  Also, keep in mind we should never have your private bastion key and will not be able to pre-install it for you.

[Paul Ruth]

That is the path to your private bastion host key.  Think of the Jupyterhub environment as private VM/container in the cloud that has all the FABRIC API configuration setup for you.

Each user has two key pairs. The first key pair is the one the is installed on the bastion host.  The other key pair is the one that is installed in the VMs.

In the Hello, FABRIC notebook example the bastion_key_filename needs to point to the bastion private key. This is the private half of the key pair that we installed in your account on the bastion host. By default this private key is not in your Jupyter environment. You will need to copy that private key to Jupyter and set bastion_key_filename to the path to that private key.

In the Hello, FABRIC notebook example the key pair that is used in your VMs are referenced with the vars ssh_key_file_priv and ssh_key_file_pub.  These keys are set to a default key pair that is automatically in your Jupyter environment.  You can use that key pair or create a new one, if you want.  If you want ssh to your VMs from outside of your  Jupyter environment you need to copy the private key to your laptop or other work station.

[Paul Ruth]

Are you able to login from a terminal window?

[Paul Ruth]

Can you retry this. It is working for me this morning.

Paul

[Paul Ruth]

TACC, NCSA, UTAH, and MAX are reopened for users.  Please refrain from using STAR.

[Paul Ruth]

This may or may not be an issue. The utility function in the notebook has a timeout that can be chosen by the user. There is a sane default but larger slices may exceed that timeout.

If you are hitting that timeout and later the VMs become accessible,  you might want to increase the timeout for your use case.

 

[Paul Ruth]

To answer Polina’s question… No, we have not installed you private key in the Jupyter environment (we never had access to your private key).

More detail can be found in this answer from the other topic: https://learn.fabric-testbed.net/forums/topic/test-server-bastion-host-login/#post-982

[Paul Ruth]

I think one issue might be mixing up which key pair is which.  For reference, the initialization code in the Hello, FABRIC note book looks like the following.

Each user has two key pairs. The first key pair is the one the is installed on the bastion host.  The other key pair is the one that is installed in the VMs.

In the Hello, FABRIC notebook example the bastion_key_filename needs to point to the bastion private key. This is the private half of the key pair that we installed in your account on the bastion host. By default this private key is not in your Jupyter environment. You will need to copy that private key to Jupyter and set bastion_key_filename to the path to that private key.

In the Hello, FABRIC notebook example the key pair that is used in your VMs are referenced with the vars ssh_key_file_priv and ssh_key_file_pub.  These keys are set to a default key pair that is automatically in your Jupyter environment.  You can use that key pair or create a new one, if you want.  If you want ssh to your VMs from outside of your  Jupyter environment you need to copy the private key to your laptop or other work station.

bastion_public_addr = 'bastion-1.fabric-testbed.net'
bastion_private_ipv4_addr = '192.168.11.226'
bastion_private_ipv6_addr = '2600:2701:5000:a902::c'

bastion_username = <your bastion id>

bastion_key_filename = os.environ['HOME'] + "/.ssh/id_rsa_fabric"

ssh_key_file_priv=os.environ['HOME']+"/.ssh/id_rsa"
ssh_key_file_pub=os.environ['HOME']+"/.ssh/id_rsa.pub"

ssh_key_pub = None
with open (ssh_key_file_pub, "r") as myfile:
ssh_key_pub=myfile.read()
ssh_key_pub=ssh_key_pub.strip()

Let me know if this was the issue,

Paul

[Paul Ruth]

You will need to put your private key in the Jupyter container at that path (or some whereelse and change the path in the notebook).

You can think of the Jupyter container as a personal computer in the “cloud”.  The benefit is that it comes mostly configured for FABRIC.   The only thing you need to do is add your bastion key.

Another option is to install the FABRIC API on your personal machine (laptop, etc.).  There are some instructions for that here: https://learn.fabric-testbed.net/knowledge-base/install-the-python-api/

Paul

[Paul Ruth]

I think you are asking about your experiment running a service that is accessible over the Internet.

This will be possible. Longer term we will enable L3 services on your experiment’s dataplane that can be connected to the Internet. This service is not ready now. For now, you can expose a service on the Internet using the management plane.  We are working on a way for you to tunnel that service through our bastion host.  We have the tunnel working but need to create some documentation that shows you how to use it.

Paul

[Paul Ruth]

I think you are asking about your experiment running a service that is accessible over the Internet.

This will be possible. Longer term we will enable L3 services on your experiment’s dataplane that can be connected to the Internet. This service is not ready now. For now, you can expose a service on the Internet using the management plane.  We are working on a way for you to tunnel that service through our bastion host.  We have the tunnel working but need to create some documentation that shows you how to use it.

Paul

[Paul Ruth]

Fengping,

We are looking into this. It does look like your slice is up.  We need to investigate more to see what is wrong with the VMs.

I’ll add more info when I know it.

Paul

[Paul Ruth]

Fu Shen,

There isn’t really a way to save the state of a slice. We recommend scripting the configuration of your experiments so that you can easily bring the experiment up/down.  Some configuration can take a long to to build.  In these cases, you might want to create containers to package your software so that the can easily be deployed on the VMs.

I am working on some examples using DockerHub to deploy software.  One example that is not quite done yet but could be useful is a slice that deploys a P4 software switch using DockerHub.

An initial version of the notebook can be found here: https://github.com/fabric-testbed/jupyter-examples/blob/pruth-utils/fabric_examples/beta_functionality/fabric_p4_bmv2/fabric_p4_simple_router.ipynb

Note that this example uses some utility functions to copy scripts into the VMs then runs them.  The scripts run “docker run …” and other configuration.  Building the software in this docker container takes a couple of hours but installing the pre-built container take about a minute.  This streamlines the creation of the experiment and makes it very easy to share the experiment with other users.

Paul

[Author]

Posts