GitLab

then scattering around. Makes the php pages a lot cleaner, and
reduces code duplication. Its an approach, lets see how it goes.

http://stackoverflow.com/questions/5213753/build-step-progress-bar-css-and-jquery

Simple, but does not really work well enough with bootstrap, it is
going to take more work if we want to use it for more then the imaging
progress modal.

which starts an image capture in the background on behalf of a user
using the APT web interface. The webtask holds the state of the image
capture as to told to us by the aggregate manager, and conferred to
the user via ajax calls which read the state of the webtask.

descriptor updated with the progress of the image capture.

1. web_tasks: This table is to track background processes that we
   start either from the web interface or from the protogeni XMLRPC
   interface. The goal is to not have a bunch of task specific stuff
   in tables, but a more general way to start a process tied to an
   object (say, like taking an image) and record state of the process
   in the descriptor (say, the image size as it grows). A client can
   poll for info about the process; the server just looks for the task
   descriptor associated with the object and returns the (currently)
   adhoc data in JSON format to the client.

   Work in progress, still determining if this general approach is
   worth it.

2. web_sessions: Playing with real PHP sessions, using the DB to store
   the session data (instead of the default, which is data files in
   /var/run). No idea how I am going to use this one, just want to
   play with sessions.

APT profile, it will not exists on the node.

change any links. spewlogfile will operate as before, but if the
logfile is open, instead of a plain text page, use Jon's javascript
code by return that instead, which will then request the real spew
with ajax.

There is no longer any use of the mungelog.js code, it can be flushed
to the archive at some point.

interface_type() should actually be called type().
Inadequate quoting in a SQL query.
And assigning through a reference needs an extra '$'.

Apparently I never tried to install an optional package. GetPackage and
AddPackage did not play nice. Also, you must specify --posix in the new
version of patch to get it to work with (some of) our patch files.

To define, in the defs file:

	IPV6_ENABLED=1
	IPV6_SUBNET_PREFIX="2011:1948:0417:0004"

A /64 network is always assumed, don't do anything else. We generate
appropriate foward and reverse entries in the zone files, but
otherwise rely on the on the upstream router to provide the prefix
when asked for it by nodes when they wish to configure an IPV6
interface.

Important caveats:

1. The infrastructure is ipv4 only. We do not dupport dual stack or
   ipv6 only on any infrastructure.

2. We do not support ipv6 only on the control plane; ipv4 or dual stack.

will correct error (no_bandwidth instead of no_connect).