Forum Replies Created
-
AuthorPosts
-
I did not see your recent message with the error while typing my message, so that’s actually a problem caused by the available IPv4 addresses. I hope the information I posted can be useful. Also, we are working with MAX, MASS and TACC sites to switch to IPv6 management subnets. This will be possible in the next few weeks and we will announce.
Hi Bruce,
I cannot see the specific error on your message, but as I can see, MAX is loaded with VMs to consume all floating IP address space on it. On FABRIC Testbed, majority of the sites (nodes) are configured with IPv6 management (ssh to VMs) network. Some sites (nodes) have IPv4 connectivity for management. On the IPv4 sites, number of VMs that can be provisioned is limited with the available IPv4 addresses in the subnet. On IPv6 sites, we don’t have any such limitation for the number of VMs caused by the addresses. I will suggest using IPv6 sites and I will add a list below.
- Sites with IPv4 management network: MAX, TACC, MASS, UCSD, FIU, SRI, BRIST, TOKY (upcoming)
- Sites with IPv6 management network: STAR, MICH, UTAH, NCSA, WASH, DALL, SALT, GPN, CLEM, GATECH, LOSA, NEWY, KANS, ATLA, SEAT, PRIN, INDI, PSC, RUTG, CERN, AMST, HAWI
Note: Among the IPv4 sites, MAX, TACC, MASS, BRIST have smaller IPv4 subnets. (MAX, TACC, MASS are already loaded, BRIST has space to accommodate VMs). UCSD, FIU, SRI have fairly larger subnets.
FABRIC-PSC is back online, available for experiments.
Hello Fengping,
VMs on your slice are started and their dataplane interfaces are re-attached.
Hello Fengping,
We are working on this problem. We will post updates about the VMs.
Hello Nirmala,
Problem on FABRIC-NEWY is fixed. You should be able to create your slices. Please let us know if you receive any other errors.
Hello Jacob, Vaiden,
Testbed is open for experiments – https://learn.fabric-testbed.net/forums/topic/testbed-under-maintenance/#post-6497
Problem was not directly related to anything about JupyterHub that would cause invalid certificate error, but you should try now. Please let us know if you have issues. It can be better to create a new entry.
Dear Experimenters,
Problem is resolved, testbed is open for experiments.
Hello Jacob,
We are working on an issue. We will send status updates, currently we don’t have an ETA.
January 26, 2024 at 8:04 am in reply to: Maintenance (disruptive) on MAX and UTAH for dataplane switch upgrades #6428Dear Experimenters,
Maintenance on FABRIC-MAX is completed. MAX is available for experiments.
January 23, 2024 at 8:40 am in reply to: Maintenance (disruptive) on MAX and UTAH for dataplane switch upgrades #6385Dear Experimenters,
Maintenance on FABRIC-UTAH is completed.
As a reminder, we will perform maintenance on FABRIC-MAX on Wednesday (1/24). FABRIC-MAX will be unavailable starting from 8am tomorrow, all slivers will be deleted on FABRIC-MAX. Details were posted on the first entry on this thread.Dear Experimenters,
Network issues affecting FABRIC-TACC are resolved. FABRIC-TACC is no longer in maintenance and available for experiments.
January 18, 2024 at 12:33 pm in reply to: Maintenance (disruptive) on MAX and UTAH for dataplane switch upgrades #6364FABRIC-GPN is taken out of maintenance.
FABRIC-UTAH remains in maintenance. We are still working on the dataplane integration.January 17, 2024 at 7:42 am in reply to: Maintenance (disruptive) on MAX and UTAH for dataplane switch upgrades #6361FABRIC-GPN will remain in maintenance mode until the dataplane connections and services on UTAH node are re-established
Hello Amanda,
Can you check the information on https://learn.fabric-testbed.net/forums/topic/fabric-testbed-is-open-and-ready-for-use/
about the requirements.txt file and fablib update (fabrictestbed-extensions) ?
-
AuthorPosts