emulab-devel issueshttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues2020-11-18T14:19:42-07:00https://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/607Selection for which frotend to use in Powder2020-11-18T14:19:42-07:00Robert Ricciricci@cs.utah.eduSelection for which frotend to use in PowderAt some locations, it will be possible (and necessary) for users to be able to select between different RF frontends, such as FDD and TDD. The immediate need is for users to be able to tell us which one they want, so that we can configur...At some locations, it will be possible (and necessary) for users to be able to select between different RF frontends, such as FDD and TDD. The immediate need is for users to be able to tell us which one they want, so that we can configure things appropriately. Eventually, (according to @alex_orange) it may be necessary to make sure that multiple experiments using incompatible frontend settings cannot run at the same location at the same time.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/606Support for new sensors in endpoints2020-11-18T14:16:54-07:00Robert Ricciricci@cs.utah.eduSupport for new sensors in endpointsThe new power control board will also have a number of sensors on it, and these will need to be integrated into our monitoring framework. The first step is for @sazzach to produce a spreadsheet showing what sensors are available, so that...The new power control board will also have a number of sensors on it, and these will need to be integrated into our monitoring framework. The first step is for @sazzach to produce a spreadsheet showing what sensors are available, so that others (@johnsond ? @amaricq ?) can work on ingesting the data.https://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/605Power control for endpoints2020-11-18T14:11:25-07:00Robert Ricciricci@cs.utah.eduPower control for endpointsThe new power/sensor board design will need to get support in `power` and friends for powering on/off/cycling devices. In some ways this is a follow up to #428 .The new power/sensor board design will need to get support in `power` and friends for powering on/off/cycling devices. In some ways this is a follow up to #428 .Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/603Add ordering to the Examples page2020-11-13T09:08:49-07:00Leigh StollerAdd ordering to the Examples pageAlex requested ordering the the examples pageAlex requested ordering the the examples pageLeigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/598IG Event daemon stops delivering events2021-10-21T08:13:14-06:00Leigh StollerIG Event daemon stops delivering eventsAfter a long time running, the IG event daemon will stop posting events back to the Mothership. Typically happens after a period of instability in the network, and it will be able to reconnect most of the time. But sometimes it just whig...After a long time running, the IG event daemon will stop posting events back to the Mothership. Typically happens after a period of instability in the network, and it will be able to reconnect most of the time. But sometimes it just whigs out.
I've tried to track it down, but no success.
I think a simple workaround is to wrap with daemon_wrapper, and when it gets itself into this state, just exit and let the wrapper restart it. Well, perhaps a bit more complicated, but something along these lines.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/597Button to send us parameter list for debugging2020-10-12T08:10:57-06:00Leigh StollerButton to send us parameter list for debuggingUsers often have a problem with a parameterized profile, and some of our profiles have a lot of options. I think we need a button to save/email us the parameter list so we can quickly start from that point.Users often have a problem with a parameterized profile, and some of our profiles have a lot of options. I think we need a button to save/email us the parameter list so we can quickly start from that point.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/596Jacks Site tags problem and feature request.2020-10-09T08:32:26-06:00Leigh StollerJacks Site tags problem and feature request.I know you have a million things to do, but if you could maybe put this on your todo list; is it possible to keep the label with the blob? But the real request, is a callback when clicking the site label so I can draw a menu. I might be ...I know you have a million things to do, but if you could maybe put this on your todo list; is it possible to keep the label with the blob? But the real request, is a callback when clicking the site label so I can draw a menu. I might be able to fake it for now by just looking for right jquery selector, assuming they do not change or get remade while the topology is showing.
![Screen_Shot_2020-10-09_at_7.08.04_AM](/uploads/8e9fd1f6225f36441d9f83158cc4dd38/Screen_Shot_2020-10-09_at_7.08.04_AM.png)Jonathon DuerigJonathon Duerighttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/595mkextrafs failure on second 1TB disk2020-10-06T11:31:25-06:00Mike Hiblermkextrafs failure on second 1TB diskThe command:
```
sudo /usr/testbed/bin/mkextrafs -s 1 -r /dev/sdb /mnt1
```
on our CentOS 7 image creates a filesystem that is only 27GB instead of 900+GB.
The culprit seems to be the line:
```
echo '2048,1953525168' | sfdisk --force /de...The command:
```
sudo /usr/testbed/bin/mkextrafs -s 1 -r /dev/sdb /mnt1
```
on our CentOS 7 image creates a filesystem that is only 27GB instead of 900+GB.
The culprit seems to be the line:
```
echo '2048,1953525168' | sfdisk --force /dev/sdb
```
which should correctly create the 900+GB partition one, but instead says:
```
[root@node1 ~]# echo '2048,1953525168' | sfdisk --force /dev/sdb
Checking that no-one is using this disk right now ...
OK
Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track
Old situation:
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 2048 5520- 3473- 27896024 83 Linux
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 83 Linux
Warning: given size (1953525168) exceeds max allowable size (119553)
New situation:
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 2048 1953527215 1953525168 15691690911960 83 Linux
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
Warning: partition 1 extends past end of disk
Successfully wrote the new partition table
Re-reading the partition table ...
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
```
and then produced the tiny partition instead, which appears to be some sort of default.
Note that this is only a 1TB drive and should not trigger the DOS partition 2TB problem. But I would not doubt that it is related.
Note also that we parse out the disk size from fdisk (1953525168) and then want to use that size, offset by 2048, to create the new partition. Seems like we should be subtracting 2048 from the size before we do that. I tried that manually, but it did not seem to affect the outcome. But maybe there is some rounding going on that caused it to still be too big.https://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/586Rationalize the two versions of libtestbed.pm2020-09-17T13:27:41-06:00Leigh StollerRationalize the two versions of libtestbed.pmWe have two partially overlapping versions, one for the clientside install. I need to clean this up and remove the duplicate stuff. Finally bothering me enough to do something.We have two partially overlapping versions, one for the clientside install. I need to clean this up and remove the duplicate stuff. Finally bothering me enough to do something.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/581small-lan profile fails when selecting a BW and default image2020-09-14T17:00:23-06:00Leigh Stollersmall-lan profile fails when selecting a BW and default imageSee https://www.cloudlab.us/memlane.php?uuid=2450f99c-f2a5-11ea-b1eb-e4434b2381fcSee https://www.cloudlab.us/memlane.php?uuid=2450f99c-f2a5-11ea-b1eb-e4434b2381fcLeigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/580Add a boot time check for working radio and try power cycle2020-09-16T07:51:14-06:00Leigh StollerAdd a boot time check for working radio and try power cycleI have a check that does this on my periodic spectrum monitoring experiment, we need to work this into boot on any node with a B210. @hibler and I will beat on this.I have a check that does this on my periodic spectrum monitoring experiment, we need to work this into boot on any node with a B210. @hibler and I will beat on this.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/578Per experiment, cross aggregate root ssh2020-08-17T15:10:23-06:00Leigh StollerPer experiment, cross aggregate root sshRegarding experiment wide ssh, we currently generate a per-aggregate root ssh key pair and optionally push that out to all nodes in an experiment, but it is a different key pair for each aggregate in the experiment.
Instead, we should ...Regarding experiment wide ssh, we currently generate a per-aggregate root ssh key pair and optionally push that out to all nodes in an experiment, but it is a different key pair for each aggregate in the experiment.
Instead, we should derive an ssh key from the ssl private key that we generate for every portal experiment and send over to the aggregates. Then all the nodes across all aggregates in the experiment, would be able to root ssh to each other.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/575Fix Powder range table on the Resource Availability table2020-07-27T13:08:00-06:00Leigh StollerFix Powder range table on the Resource Availability tableNeed to add currently running experiments to the table, like we do on the reserve
page, since users can now use ranges with out reservations.Need to add currently running experiments to the table, like we do on the reserve
page, since users can now use ranges with out reservations.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/569Allow project leader to delete any dataset in their project2020-07-22T06:54:10-06:00Leigh StollerAllow project leader to delete any dataset in their projectCurrently only the owner or admins can delete a dataset.Currently only the owner or admins can delete a dataset.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/564Missing local blockstore desires2020-06-29T15:30:07-06:00Leigh StollerMissing local blockstore desiresNoticed this morning, when a user tried to create a local blockstore that was too big for the node (m400, disk size from the previous century). Turns out that we need to add a ?+disk_xxx desire for local blockstores, which is currently d...Noticed this morning, when a user tried to create a local blockstore that was too big for the node (m400, disk size from the previous century). Turns out that we need to add a ?+disk_xxx desire for local blockstores, which is currently done in the NS parser on the CLassic path. So we need to generate that in geni-lib or in the CM.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/561Fix snmpit error after DeleteNodes()2020-06-26T10:14:43-06:00Leigh StollerFix snmpit error after DeleteNodes()Seen this a couple of times, deleting all nodes but a single node, which means deleting the vlan, results in this error:
```
stack::findVlans calling ms-chassis9-switchb
*** snmpit:
No vlanid 67208 in the DB!
Failed to setup vlans: F...Seen this a couple of times, deleting all nodes but a single node, which means deleting the vlan, results in this error:
```
stack::findVlans calling ms-chassis9-switchb
*** snmpit:
No vlanid 67208 in the DB!
Failed to setup vlans: Failed to synchronize vlans
```
See https://www.utah.cloudlab.us/spewlogfile.php3?logfile=1b1d96adb75be1ec12725cda2145a751Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/555Eliminate tipserver mounts on ops2020-06-08T09:12:42-06:00Mike HiblerEliminate tipserver mounts on opsOur remaining `tipserv*` nodes are getting old and flaky and if one of them goes down for an extended period of time, it (eventually) takes `ops` with it because we NFS mount the tipserv nodes on ops. Even though the mounts are interrupt...Our remaining `tipserv*` nodes are getting old and flaky and if one of them goes down for an extended period of time, it (eventually) takes `ops` with it because we NFS mount the tipserv nodes on ops. Even though the mounts are interruptible (intr) and set to timeout (soft), neither seems to work. A 30 minute reboot of ops because a tipserv node fails is not acceptable.
Why are tipserv nodes mounted on ops? Originally, it was so that users could get to the log/run files for captures. But now that users can no longer login to ops directly, maybe that is not needed. @stoller confirms that the portal interface accesses logs by `ssh`ing directly to the tipserv nodes. The remaining concern is that `ops` does directly access the `.acl` file for authentication. A reasonably simple solution for this is to reverse the mounts so that tipserv nodes mount `ops` instead of the other way around. We would want to isolate the `.acl` files so that they are the only thing being exported to `ops`; we do not want to have every tipserv node writing the console logs themselves across NFS to `ops`. `ops` does not need more NFS load.Mike HiblerMike Hiblerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/547Trying to use emulab-xen sliver type fails at Cloudlab Utah cause of image al...2020-05-04T11:35:50-06:00Leigh StollerTrying to use emulab-xen sliver type fails at Cloudlab Utah cause of image aliasesUsing /tmp/stitcher.hWZoPG for stitcher
Stitcher command: /usr/testbed/gcf/src/stitcher.py --fileDir /tmp/stitcher.hWZoPG --cred /tmp/stitcher.hWZoPG/speaksforcred.xml --slicecredfile /tmp/stitcher.hWZoPG/slicecred.xml --usercredfile /tm...Using /tmp/stitcher.hWZoPG for stitcher
Stitcher command: /usr/testbed/gcf/src/stitcher.py --fileDir /tmp/stitcher.hWZoPG --cred /tmp/stitcher.hWZoPG/speaksforcred.xml --slicecredfile /tmp/stitcher.hWZoPG/slicecred.xml --usercredfile /tmp/stitcher.hWZoPG/slicecred.xml --al2scredfile /tmp/stitcher.hWZoPG/al2scred.xml --debug --GetVersionCacheName=/tmp/stitcher.hWZoPG/get_version_cache.json --AggNickCacheName=/tmp/stitcher.hWZoPG/agg_nick_cache --scsURL http://scs.scs.scs.emulab.net:8081/geni/xmlrpc --speaksfor urn:publicid:IDN+emulab.net+user+thedeu2e -V3 allocate urn:publicid:IDN+emulab.net:sdnnfvlab+slice+attempt5 /tmp/stitcher.hWZoPG/rspec.xml
Allocation of slivers in slice urn:publicid:IDN+emulab.net:sdnnfvlab+slice+attempt5 at utah-clab3 failed: Error from Aggregate: code 2. protogeni AM code: 28: *** WARNING: mapper:
*** nodejailosid: Could not map [ImageAlias emulab-ops,UBUNTU16-64-STD
*** 123456] on [vnode:Relay-node]
*** ERROR: mapper:
*** Can't call method "osid" on an undefined value at
*** /usr/testbed/lib/libvtop_test.pm line 2510.
(PG log url - look here for details on any failures: https://www.utah.cloudlab.us/spewlogfile.php3?logfile=f754c12071ae77e24945263997708068)..Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/542Portal based policies2020-04-24T13:01:02-06:00Leigh StollerPortal based policiesWe need a way to restrict node/types on a portal basis. We have kicked around ideas
like extending the group_policy tables or adding a portal_policies table. @hibler is
super interesting in this ticket.We need a way to restrict node/types on a portal basis. We have kicked around ideas
like extending the group_policy tables or adding a portal_policies table. @hibler is
super interesting in this ticket.Leigh StollerLeigh Stollerhttps://gitlab.flux.utah.edu/emulab/emulab-devel/-/issues/538Watchdog for "shutting off" RF if we lose contact for an extended period of time2020-07-14T16:07:28-06:00Robert Ricciricci@cs.utah.eduWatchdog for "shutting off" RF if we lose contact for an extended period of timeThe idea is to shut off RF transmissions if we lose contact with central control for a long period of time, since we can't tell if the panic button has been pressed.
@alexo suggested that we control the RF switch to move the inputs to a...The idea is to shut off RF transmissions if we lose contact with central control for a long period of time, since we can't tell if the panic button has been pressed.
@alexo suggested that we control the RF switch to move the inputs to an unamplified output, as a simple way of preventing significant radiation from occurring.