Forum Replies Created
-
Posts
-
Hello Yuanjun.
I don’t have the details of your slice request, but from the STAR status page on the portal, host resources for hosts that have the RTX6000 GPUs (star-w1 and star-w2) have one GPU available. Host star-w2 has a very little amount of RAM. I checked slice creation on both hosts with their available GPUs and it works well. Just, for the VM that would be placed on star-w2, I selected very small amount of RAM and CPU to fit in it.
Slice modification is supported on FABRIC. Yes you can remove the SRI VM and re-create VMs etc. It should be straightforward, but you can also check the link below for examples
MICH VM (2607:f018:110:11:f816:3eff:fe98:ba32) is online. I confirmed connection over the management network (through FABRIC bastion hosts) works well. It has an ssh key with alias “slice_key” in it (under user ubuntu)
SRI VM (192.5.67.209) is online (responding to pings), but it does not allow SSH connections that it’s supposed to allow from the controller node. SSH keys might have been modified somehow. I don’t have much to do with this VM.
Dear Experimenters,
FABRIC-UTAH is back online.
We could not recover the slivers during the interventions, following slices were affected (their slivers on UTAH node are deleted).
- Slice latency_monitoring_slice_20240724(d37afde4-137d-4139-9da3-20734bf46357
- Slice monitoring(5c4927ac-27a0-4462-b7ae-7f8d99b2d444
- Slice ServiceX_NDN_Proxy_udp_4nodes(8a096617-4998-41d6-867c-fec9dcdd31bc
- Slice latency_monitoring_slice_20240919(f0b30035-f516-4c37-b37f-2e9f40159d75
Hello Fatou,
Problem should be corrected now. You can try again.
1 user thanked author for this post.
Tejas,
From the screenshots you attached, it looks like your diskspace is full. You might also consider removing unused files. That might be related to the problem you’re having, second screenshot reveals that problem.
Best regards,
MertHello Tejas,
You can try again. It might be due to the hosting cloud platforms scaling in progress at that time.
Best regards,
MertFor some reason all your VMs management network interfaces are offline. If you share the notebook with us, we can understand if something in the flow might be causing an issue.
