- 05 Sep, 2006 8 commits
-
-
Leigh B. Stoller authored
* Add XMLRPC interface for template swapin,stoprun,startrun,swapout and add the appropriate wrappers to the script_wrapper on ops. * Allow parameter descriptions in NS files. This is probably not in its final form since its a bit confusing as to what has priority; something in the NS file or a metadata item. Anyway, you can do this in your NS file: $ns define-template-parameter GUID "0/0" "The GUID to be analyzed" The rules are currently that the NS file description has priority and is copied to child templates, unless the user has modified a description via the web interface, in which case the NS file description is ignored. I know, sounds awful, but for the most part people are going to use the NS file anyway. * Add "clear" option when starting a new experiment run; the per experiment DB at the logholes are cleared. Note that this is *not* the default behaviour; you have to either check the checkbox on the web form or use the -c option to the script wrapper, or clear=yes if talking directly to the XMLRPC server. * Fix up how email is generated for template_swapin and template_create, so that Kevin can debug tblog/tbreport stuff, but also so that we maintain mail logs as before. I have made some improvements to libaudit so as to centralize the mail goo, and avoid duplicating all that stuff. * Minor fixes to the program agent so that the new environment strings are sent before the program agent exits and reloads them! * Other minor little things.
-
Jonathon Duerig authored
Reverted changes to time format. Added a 'SENSOR_DETAIL' and 'SENSOR_COMPLETE" logging options. 'SENSOR' should now be used for high level information, 'SENSOR_DETAIL' should be used for medium level information, and 'SENSOR_COMPLETE' should be used for low-level information. If SENSOR_DETAIL logging is turned on, then SENSOR logging is also turned on. If SENSOR_COMPLETE logging is turned on, then SENSOR_DETAIL and SENSOR loggin is also turned on. All three of these levels use the 'SENSOR' prefix when outputting logging lines.
-
Leigh B. Stoller authored
-
Leigh B. Stoller authored
detaching from the parent. Also improve the logonly mode by adding a nodelete option, to retain the logfile after the email is sent. Minor improvements to the interface.
-
Leigh B. Stoller authored
next sync (similar to how it works with the archive directive).
-
Dan Gebhardt authored
-
Jonathon Duerig authored
Streamlined logging so that only two fprintf statements are necessary. One for the prefix and one for the variable argument body. This is down from the 5 it was earlier. Also changed the format of timestamps to me more useful. Timestamps are now in a secs:millis format rather than a floating point number. And secs is seconds since the beginning of the run (rounded to the nearest second) rather than seconds since epoch.
-
Robert Ricci authored
rather than signed ones.
-
- 04 Sep, 2006 1 commit
-
-
Russ Fish authored
-
- 01 Sep, 2006 11 commits
-
-
Jonathon Duerig authored
-
Mike Hibler authored
-
Jonathon Duerig authored
Changed order of input file to <src> <dst> <bw> <delay> <loss> to bring it in line with Kevin's request.
-
Mike Hibler authored
-
Mike Hibler authored
-
Jonathon Duerig authored
Changed logCleanup() so that it uses a switch statement rather than a series of if statements. Now if there are more than one flags selected, only the first one encountered will be printed as a prefix. This should make things run faster.
-
Robert Ricci authored
up the max write size to 8k (we still write the correct number of bytes if the app makes a write bigger than this, we just do it in a couple calls to write().)
-
Jonathon Duerig authored
Added an extra field as a placeholder for loss in the initial-conditions format as per Mike's request.
-
Mike Hibler authored
Use '-' for stdout, e.g.: init-elabnodes.pl -o - tbres planetmikelab >> foo
-
Jonathon Duerig authored
Added initial conditions handling to monitor/stub. This should also solve the what does throughput mean when the connection is delay-dominated? problem. Now there are two kinds of bandwidth measurements that the magent can send back to the monitor. There is a throughput measurement which is tentative and which is applied only if it is greater than the last measurement. And there is a bandwidth measurement that is authoritative and is applied regardless.
-
Mike Hibler authored
which, oddly enough, ensures that update does not return immediately.
-
- 31 Aug, 2006 10 commits
-
-
Robert Ricci authored
with a simple malloc()ed buffer, which cut about 20% off our CPU usage. Note, this could probably even be put into a statically-sized structrure, but Jon would have to verify this.
-
Robert Ricci authored
out to burn too much CPU.
-
Robert Ricci authored
and gprof.out go to a place loghole will find them.
-
Kirk Webb authored
Change where the TMCCVNODEID environment variable gets setup. Since vnodesetup is the highest common execution point in the chain (for either initial vserver startup, or subsequent reboot), this is the place to put it. The previous stages don't need it, but just putting it in rc.vinit excludes it from getting set during initial setup and boot.
-
Mike Hibler authored
-
Kirk Webb authored
Change types of latitude and longitude columns in widearea_nodeinfo to float (instead of float(6,5)) to fix problem with values getting adjusted improperly during insert. Apparently the definition of the float(n,m) type is non-standard, and has changed since sql 3.x. Regular float columns will do fine here.
-
Kevin Atkinson authored
Add patch to modify Mysql.pm to allow setting the "InactiveDestroy" in the underlying DB handle. Also avoid disconnecting the file handle explistly on DESTROY as that will be taken care of in the DESTROY method for the the DB handle. Override perl version of fork() to set InactiveDestroy in all open database handles in the child so that it won't send a disconnect when the handle is destroyed as this will also close the database handle for the parent. It will also call tblog_new_child_process in the child process to properly inform tblog of the new process. This will be a NoOp if the libtblog module is not loaded.
-
Robert Ricci authored
things (like finishing writing the gmon.out file when profiling) that don't happen when you control-c or kill the program.
-
Robert Ricci authored
It's not perfect - it doesn't rebuild the dependancy file at the right time, but it should be good enough for our purposes.
-
Leigh B. Stoller authored
* Export the above via the XMLRPC interface and add a wrapper function to the script_wrapper. This allows you do to this on ops: cd /proj/testbed/templates/10023/1 Edit some files template_commit Which creates a new template, using the current directory to infer the template. Otherwise, provide the template GUID on the command line. Hmm, maybe this should be called template_modify? Either way, the name does not quite match * Export template_export via the XMLRPC wrapper. This allows you to export a template (instance) record from the command line on ops. cd /proj/testbed/templates/10023/1 template_export -i 12 Exported to /proj/testbed/export/10000/3/12 Which exports the template record for instance number 12. Again, the GUID is infered, but you can specify one on the command line. The export directory is printed so you know where it went. Note that export does *not* populate a DB on ops with the old DB data.
-
- 30 Aug, 2006 6 commits
-
-
Kirk Webb authored
A node update bugfix and a change to the way nodes with more than two changed attributes are handled. A single message is now sent detailing which nodes need to be looked at, and such nodes to not stop the rest from updating normally during that run. Previously the nodes with multiple changes had to be handled first, then the update script had to be run after that to catch everything.
-
Jonathon Duerig authored
Cleaned up and added a couple of lines of comment about what 'Send' and 'Ack' really mean. All that really matters is distinguishing between outgoing packets and incoming packets. 'Send' and 'Ack' are unfortunate names reflecting my previous muddled thinking about this. So for 'Send' read outgoing, and for 'Ack', read incoming. A low-priority task is to change the naming to reflect this semantic change.
-
Jonathon Duerig authored
-
Robert Ricci authored
didn't get one or more packets from libpcap. I have one trace on PlanetLab that does this a lot, so it could be a sign of a problem - like not checking libpcap freqeuently enough. A pcapper process running at the same time did get the packets...
-
Kirk Webb authored
Change the mode used to create log files to allow world read access. We have determined that there really isn't any risk in doing so. This will stop rsync/loghole from complaining when transfering data from plab nodes. It was failing to transfer some log files created as root.
-
Leigh B. Stoller authored
mixed togther, and port registrations are not made. The one case currently handled is when the syncserver node goes ISUP, but has not reported its port. In this case, it must be an old image and so we place a port registration in for it.
-
- 29 Aug, 2006 4 commits
-
-
Dan Gebhardt authored
A user can set the duration of a measurement set with the -d option in testsend.pl and manager.pl . The change occurs for the given number of seconds. After expiration, the old measurement period is used. The logic behind when/how to change is fairly complex - see bgmon.pl for more details.
-
Robert Ricci authored
-
Kirk Webb authored
bump up plab rootball version
-
Mike Hibler authored
OLD: * Delay specified in ticks. * Drop performed as packets were leaving the delay queue (i.e., leaving dummynet). This is more accurate in terms of calculating time spent in dummynet, and can be used with all strategies of BW/delay shaping (constant values, distributions, table lookup), but required that ultimately-dropped packets get put on the BW queue, changing the timing of things. NEW: * Delay specified in milliseconds. * Drops perfromed as packets enter the bandwidth queue (i.e., arrive in dummynet). Here drops are based on estimates of how long a packet would spend in dummynet and thus only works with constant delay/BW shaping characteristics, but does more accurately reflect queuing behavior. The estimate is done by looking at the length in bytes of the bandwidth queue (including the candidate packet) for the pipe, determining how long it will take to transmit that many bytes, and then adding the delay value for the pipe.
-