[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

[Komal Thareja]

Hi,

Please refer to the site details to view the available GPU models. For instance, the STAR site offers RTX600 and Tesla T4 GPUs. You can verify this information at [STAR site details](https://portal.fabric-testbed.net/sites/STAR).

Thanks,

Komal

[Komal Thareja]

Hi Yuanjun,

I suspect your bastion keys have expired. Could you please re-run the notebook to regenerate your bastion keys jupyter-examples-rel1.7.0/configure_and_validate.ipynb ?

Please let us know if you still run into errors.

Thanks,

Komal

[Komal Thareja]

Hi Tianrui,

Users do not have sudo access on the JupyterHub container. To install Python packages, please use the command pip install <package name> --user.

Thanks,

Komal

[Komal Thareja]

Please consider checkingthe 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]

Hi Sourya,

You will need permission for FabNetv*Ext services to enable public connections to your VMs. This request can be made by your Project Lead. For more details, please check here!

Thanks,
Komal

[Komal Thareja]

Hi Prateek,

This looks like a bug, we have a race condition which is preventing the updates to the Slice Graph Model. I will work on addressing this. For now as a workaround, you can determine the IP Addresses via slice commander using show commands. Refer https://learn.fabric-testbed.net/knowledge-base/using-slicecommander-with-fabric/ for slice-commander usage.

Alternatively, you can get the sliver information also via

for s in slice.get_slivers():

print(s._sliver) # This is a json object will provide the needed information

Thanks,

Komal

[Komal Thareja]

Hi Prateek,

Could you please share your slice ID?

Thanks,

Komal

[Komal Thareja]

Hi Kriti,

This looks like a version mismatch for the fabrictestbed-extensions. Are you running into this any of the JH containers? If so, please ensure you have no entries in /home/fabric/work/fabric_config/requirements.txt and then restart your JH container via File -> Hub Start Control Panel -> Stop My Server -> Start My Server.

 

If you are running into this on you local environment, please consider updating to the latest fablib via

pip install fabrictestbed-extensions==1.7.3

Thanks,

Komal

[Komal Thareja]

Thank you, @yoursunny, for the excellent suggestion!

@Jestus,

In addition to @yoursunny’s point, the Project Lead for your project will need to request permissions to enable FabNetv*Ext services. You can find more details here.

Additionally, we recommend avoiding the use of the management interface for data transfer and instead utilizing the FABNetv4Ext/FABNetv6Ext services. Please feel free to reach out if you have any questions or comments.

Thanks,
Komal

[Komal Thareja]

Just closing the loop here as the issue was resolved over a short zoom call.

The error message “The token is not yet valid (iat)” indicates that the token’s “issued at” (iat) timestamp is set in the future compared to the current time. This can happen if there is a clock discrepancy between the system where the token was generated and the system validating the token.

Time on the server was behind current time, synching the clock with NTP server resolved the error.

Thanks,

Komal

[Komal Thareja]

Hi Yu,

I created a token and successfully validated it using the Credential Manager, but I am unable to reproduce the issue you’re experiencing. This error can sometimes occur due to stale cookies in the browser. Could you please try opening https://cm.fabric-testbed.net/ in an incognito window, then generate and validate the token? Let me know if the error persists.

Thanks,

Komal

• This reply was modified 1 year, 7 months ago by Komal Thareja.

[Komal Thareja]

Also, could you please post queries in this channel instead https://learn.fabric-testbed.net/forums/forum/fabric-general-questions-and-discussion/

Thanks,

Komal

[Author]

Posts