[Komal Thareja]

Hi Kriti,

I created a slice on MASS for a Layer2 Network as well as Layer3 network. Both slices were able to pass traffic.

This may be something specific to your slice or configuration. Please share your slice id. We can help to take a look but would also recommend checking configuration on your side as well.

Thank you for letting us know about the portal. We will work on addressing that as well.

Thanks,

Komal

[Komal Thareja]

Hi Kriti,

Could you please open the Calendar by clicking on the small square shown next to Lease End at to choose the timestamp and then click on Extend?

Also, you can extend your slice by following methods as well:

• Notebook accessible from Start_here -> Extend Slice Reservation
• slice-commander command line utility available in JH container


fabric@fall:system-29%$ slice-commander
Usage: renew <days> [SliceName1, SliceName2, ...]


Please let us know if you run into issues or errors.

Thanks,

Komal

[Komal Thareja]

The maintenance is complete and the new model has been deployed.

[Komal Thareja]

Hi Prateek,

It seems that the teaching materials are somewhat outdated. Users no longer need to manually complete the steps under “Configure your Jupyter environment.” Instead, they can simply run the latest jupyter-examples-rel1.7.*/configure_and_validate.ipynb notebook to set up their Jupyter Hub environment.

If you have any questions or encounter any issues, don’t hesitate to reach out.

Thanks,
Komal

[Komal Thareja]

I also wanted to mention another option you can utilize: TailScale, which doesn’t require Ext services. You might find the Jupyter example helpful—check it out here.

Thanks,
Komal

[Komal Thareja]

Hi Sourya,

While your request is being reviewed, please consider trying the workaround suggested by @yoursunny here: https://learn.fabric-testbed.net/forums/topic/reaching-the-internet-from-a-fabnet-node/#post-7605

Thanks,
Komal

[Komal Thareja]

Hi Sourya,

We offer FabNetv*Ext services that allow internet access; however, these services require special permission due to the potential security risks they pose. The Project Lead for your project can request these permissions as specified here!

Please consider checking the following examples on how to use these services:

https://github.com/fabric-testbed/jupyter-examples/tree/main/fabric_examples/fablib_api/create_l3network_fabnet_ipv4ext_manual

https://github.com/fabric-testbed/jupyter-examples/tree/main/fabric_examples/fablib_api/create_l3network_fabnet_ipv6ext_manual

Feel free to reach out in case you run into issues or have queries.

Thanks,
Komal

[Komal Thareja]

@Tejas – Notebook is not attached. Could you please share it? You may have to change the file extension to .txt

[Komal Thareja]

Thank you Kim! Could you also please open a terminal on JH and try SSH to the VM using the command displayed above?

ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@137.222.230.26

Thanks,
Komal

[Komal Thareja]

Hi Kim,

Both of your VMs are accessible via SSH. I can verify with Nova SSH key. I also verified that your SSH keys are pushed in to the VM.

Could you please share the output of the following?
Please run the following snippet in a notebook cell before the configure step.
If this does show the management IPs for the VMs, please try running the configure cells again and let us know if it works.


slice = fablib.get_slice(slice_name)

slice.show();

slice.list_nodes();

Thanks,
Komal

[Komal Thareja]

Hi Tejas,

It looks like SSH connection to bastion host is failing. Could you please re-rerun this notebook jupyter-examples-rel1.7.*/configure_and_validate.ipynb? Please retry your notebook after that.

Please let us know if the issue persists.

Thanks,

Komal

[Komal Thareja]

Hi Sepideh,

Disk usage of your container is 100%. You seem to have output_file which seems to be taking majority of the space.

The /home/fabric/work directory (1GB) in the JupyterHub environment serves as persistent storage for code, notebooks, scripts, and other materials related to configuring and running experiments, including the addition of extra Python modules. However, it is not designed to handle large datasets or output files.

Please consider removing un-needed files or move output_file to avoid this error.

Additionally, if you need more disk space, I recommend setting up your own FABRIC environment on your laptop or machine to run your experiments. This approach will allow you to capture more data and reduce reliance on Jupyter Hub. Consider configuring a local Python environment for the FABRIC API as described here, and run the notebooks locally.


fabric@spring:work-100%$ du -sh *
20K 5_clients_1_server.ipynb
60K fabric_config
228K hipft.ipynb
95M jupyter-examples-rel1.5.5
96M jupyter-examples-rel1.6.1
28K lost+found
686M output_file
82M rel1.7.0.tar.gz4q_e8dq5.tmp
0 rel1.7.0.tar.gzceav1uzw.tmp
0 rel1.7.0.tar.gzds9a6279.tmp
0 rel1.7.0.tar.gzgmqadnvv.tmp
0 rel1.7.0.tar.gziuc6xzxa.tmp


Thanks,

Komal

[Komal Thareja]

Hi Ilya,

Yes, it’s possible to pin vCPUs to physical cores. The following APIs on the node class may be of interest:

– node.get_cpu_info() provides information about the VM’s CPU in relation to the host.
– You can pin specific vCPUs to physical cores using node.poa(operation="cpupin", vcpu_cpu_map=vcpu_cpu_map).

In this case, vcpu_cpu_map is a dictionary mapping each vCPU to the desired physical core.

For more details, please refer to the documentation here. Let us know if you have any questions or encounter any issues!

Thanks,
Komal

[Komal Thareja]

Hi Khawar,

Ubuntu 18.04 LTS reached the end of its standard support on May 31, 2023, and is no longer available on FABRIC. Thank you for bringing the list of images to our attention. We will update it to reflect this change.

Thanks,

Komal

[Komal Thareja]

Hi Yuanjun,

I suspect the bastion keys are expired. These keys are only on your JH container and are not pushed to your VMs. Sliver keys i.e. VM keys should not be affected. The error indicated above for SSH failure indicates login to bastion server was denied and hence the suggestion.

 

The error observed in the multi-processing pool cleanup can be ignored. We will address that error but it should not impact regeneration of the keys. Could you please see if you are able to SSH to your VMs?

Bastion key expiry can also be verified from the portal via: Experiments -> Manage SSH Keys.

Thanks,

Komal

[Author]

Posts