[Komal Thareja]

Hi Zhihe,

This was a bug, a fix has been deployed on the default container. Could you please try running this notebook again?

Thanks,

Komal

[Komal Thareja]

Yes please Nirmala – Just keep the following in that file:

This should allow you to delete older examples.

{
"examples": [
{
"url": "default",
"location": "/home/fabric/work"
}
]
}

Best,

Komal

[Komal Thareja]

Hi Philip,

We discussed this internally, and the minimum supported bandwidth value is 1 Gbps. At this time, we don’t have plans to provide more fine-grained options. If you need to simulate lower bandwidth, we recommend using tools such as tc.

Best,

Komal

[Komal Thareja]

Hi Jacob,

Thank you for sharing the details. I discussed the energy consumption measurement topic with the team earlier today.

As mentioned before, we do not currently support energy consumption measurements on the VMs. The network team also confirmed that such measurement capabilities are not available on the network devices.

For identifying the geolocation of hops, we recommend using the L2PTP (Layer 2 Point-to-Point) network, where the user explicitly defines the network path by specifying the SITEs for each hop. You can then use fablib.list_sites() to obtain the geo-coordinates.

Please refer to this artifact for guidance on setting up an L2PTP slice:
https://artifacts.fabric-testbed.net/artifacts/7e439627-96be-45e0-ab67-50bb607f06e4

 

Also, regarding the renewal request, I see that it was submitted yesterday. Michael will follow up on that through the ticket.

Best,

Komal

• This reply was modified 1 month, 1 week ago by Komal Thareja.

[Komal Thareja]

Hi Nirmala,

You don’t need to keep the example notebooks, so please go ahead and remove them.

Could you also take a look at the contents of /home/fabric/fabric_config/fabric_config.json? I suspect there may be multiple entries in that file. If so, please delete it as well—this should prevent the older examples from being retained when you log in again.

Best,

Komal

[Komal Thareja]

Hi Jacob,

At the moment, energy consumption measurements are not passed into the VMs. I’ll bring this up in our planning meeting so it can be considered for inclusion in a future release.

For location information, we currently expose the geo-coordinates for all FABRIC sites, which you can retrieve using fablib.list_sites(). One possible approach to determine the location of hops is to map IPs → Sites → Locations.

Could you share your slice ID or specify the type of network service you’re using for your WAN experiment?

Best,

Komal

[Komal Thareja]

Hi Rasman,

The dataplane was down at MASS. The link has been restored, could you please try running the iPerf3 cells again from the notebook. Apologies for the inconvenience.

Thanks,

Komal

[Komal Thareja]

Hi Rasman,

I was able to run iperf3 optimized notebook without issues. I am unable to access your notebook. It says Page Not Found.

Could you please share your slice ID?

Thanks,

Komal

[Komal Thareja]

Thank you @yoursunny for sharing the details on how to request more disk space on experiment VMs.

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 to avoid this error.

Additionally, if you need more disk space in the Jupyter Hub Container, 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 one of the following options:

• Running JupyterHub Container locally as described here.
• configuring a local Python environment for the FABRIC API as described here, and run the notebooks locally.

Best,

Komal

• This reply was modified 1 month, 2 weeks ago by Komal Thareja.

[Komal Thareja]

Hi Abdulhadi,

Thank you for sharing the details. I was able to reproduce it and have posted a fix. If you try the Beyond Bleeding Edge JH container, this should work. I plan to update the other JH containers with the fix sometime next week.

Thanks,

Komal

[Komal Thareja]

It appears there may be an issue with list_nodes, which could be affecting the display.

However, I suspect the P4 switch you requested at SITE is currently unavailable. You can verify this by checking your slice in the Portal. If your slice is in a Dead or Closed state, enable the “Include Dead/Closing Slices” option.

When you click on your slice, you may see an error message such as “insufficient resources.” 

Please choose a different site or look at the P4 availability via following code or check from Portal-> Resources Overview screen.

p4_column_name = 'p4-switch_available'

[site2] = fablib.get_random_sites(count=1, filter_function=lambda x: x[p4_column_name] > 0)

Thanks,

Komal

[Komal Thareja]

Hi Ajay,

Your slice is currently in a Dead state, and all associated resources have been released.

If you encounter this issue again, please share details of an active slice or VM.

Thanks,

Komal

[Komal Thareja]

Hi,

Could you please share the Slice ID for your slice?

 

Thanks,

Komal

1 user thanked author for this post.

Abdulhadi Sahin

[Komal Thareja]

Hi Arash,

Could you please try deleting the key from the portal and run fablib.verify_and_configure()?

Thanks,

Komal

1 user thanked author for this post.

Arash SARABI

[Komal Thareja]

Peter’s fix should still work Nirmala!

Thanks,

Komal

[Author]

Posts