- 03 Apr, 2018 7 commits
-
-
Gary Wong authored
Intended to estimate Powder wireless resources to appear on the front page. This is HORRIBLY quick and dirty and definitely needs to be thrown away. It estimates the number of OAI experiments (1 SDR + 1 OTS UE) that could be accommodated as a stopgap measure for the tech preview demo. It must be replaced before we have real wireless sites installed.
-
Leigh B Stoller authored
there is an adminmfs, instead of defaulting to null. The ONIE based switches operate more like normal nodes wrt reload/admin MFSs
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
that image is an *imported* system image, we are almost certainly referring to a version related to the origin image, not the local copy (which is not in sync with the origin wrt the history). In that case, we can use the hash from the image server to track down the local version. Aside; If I were going to redo the import mechanism, I would make image provenance the default for everyone, and make the option be whether to save or delete the image file (that was the entire reason I made provenance optional, most sites especially geni racks, do not have enough storage to maintain old images. And image import would always import the history too, which is something I did later when we thought deltas were going to solve our problems.
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
- 02 Apr, 2018 4 commits
-
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Gary Wong authored
(If the reservation being approved isn't in the list returned by LookupAll(), presumably because it was previously pending, then append it during feasibility checking.)
-
David Johnson authored
pubsubd wasn't restarting, surely because the existing pubsubd was still running and/or socket state was still live in the kernel even after putative death. This took a long time to manifest, and it's not clear exactly what the problem was, but making sure pubsubd is dead (and is no longer holding its specific port) is appropriate even if we assume REUSEADDR is working, and fixes the current problem. This was only observable on the pc3000s and c220g2s, as far as I saw.
-
- 30 Mar, 2018 6 commits
-
-
Kirk Webb authored
-
Mike Hibler authored
-
Mike Hibler authored
-
Mike Hibler authored
-
Mike Hibler authored
We have had issues with uploading images to boss where they are then written across NFS to ops. That seems to be a network hop too far on CloudLab Utah where we have a 10Gb control network. We get occasional transcient timeouts from somewhere in the TCP code. With the convoluted path through real and virtual NICs, some with offloading, some without, packets wind up getting out of order and someone gets far enough behind to cause problems. So we work around it. If IMAGEUPLOADTOFS is defined in the defs-* file, we will run a frisbee master server on the fs (ops) node and the image creation path directs the nodes to use that server. There is a new hack configuration for the master server "upload-only" which is extremely specific to ops: it validates the upload with the boss master server and, if allowed, fires up an upload server for the client to talk to. The image will thus be directly uploaded to the local (ZFS) /proj or /groups filesystems on ops. This seems to be enough to get around the problem. Note that we could allow this master server to serve downloads as well to avoid the analogous problem in that direction, but this to date has not been a problem. NOTE: the ops node must be in the nodes table in the DB or else boss will not validate proxied requests from it. The standard install procedure is supposed to add ops, but we have a couple of clusters where it is not in the table!
-
Leigh B Stoller authored
-
- 29 Mar, 2018 5 commits
-
-
Mike Hibler authored
-
Mike Hibler authored
-
Mike Hibler authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
1) Rework so that instead of relying on swapin__last + autoswap timeout, set expt_expires for classic experiments at the beginning of swapin time. This is cause swapin_last is not set till the end of swapin, and so during swapin the res system is in an inconsistent state since there is no way to determine when the experiment ends. 2) On the Geni path, simplify expiration handling; do not allow a slice modification and expiration change at the same time; the bookkeeping and failure rollback is a pain, especially wrt reservation system, and this rarely ever actually happens, so get rid of a lot of complication.
-
- 28 Mar, 2018 6 commits
-
-
Mike Hibler authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
- 27 Mar, 2018 1 commit
-
-
David Johnson authored
-
- 26 Mar, 2018 11 commits
-
-
David Johnson authored
Also assume debian9 == ubuntu16. Also fix some ubuntu15 install bugs.
-
Leigh B Stoller authored
request (and the https code calls die) we can catch it and return a proper error response.
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
-
Leigh B Stoller authored
infrastructure switch
-
Leigh B Stoller authored
-