GitLab

Fixed missing '?' in GID link when showing group.

a call to existing routine in showstuff. Also changed the interface
to SHOWGROUPMEMBERS() so that priv people get a "remove from project"
option when showing the default group membership. Yes, project leaders
can now delete users from their project.

in his profile output.

Too noisy.

Add some missing os_features options and op_mode, along with guidelines for setting them properly. Add them to form handler and display as well.

widearea nodes.

The big one.

New look;
most of the changes are in menu.php3.

A lot of the changes in other files are s/<TD>/<TH>/
for table headers.

Also closed some tags, tweaked some table styles, etc..

No actual functionality should have changed.

Will be installing soon...

* Two new fields on the new project page that ask the project leader to
  specify how many ron and pcplab nodes they need. There is a link to a
  page that should describe these nodes, but thats blank.

* The project approval page will add a couple of checkboxes for ron and
  pcplab nodes. This will allow the project to be approved independent of
  the ron/pcplab usage. So, you can approve the project but decline the
  request to use those nodes types (or just one of them).

* The project table in the DB has a "list" of remote node types for which
  accounts should be built. Its implemented as a set and it can contain
  just two node types (pcron, pcplab) right now. The set is created in
  the approval page, and someday we can add a page to operate on that
  set directly if we need it.

This call appears to always reselect the DB, which might be a problem
when the DB is busy.

changes that have to go in now!

* Cleanup! A lot of the structure derived from the early frame days,
  which had a noticable (and bad) effect on how I wrote the stuff.  I
  cleaned up most of that yuckyness.

* In process, optimize a little bit on the queries. The old code did
  about 9 queries just to write out the menu options, and then
  repeated most of those queries again in the page guts. I've
  consolidated the queries as much as possible (to 3) and cache all
  the results.

* Fix up problem with users who forget their passwords before
  verification. Basically, I fixed the more general problem of not
  being able to update your user info before verification/approval;
  users now get that menu option no matter their status.

* Fix up problem of users being able to access pages before
  verification (but after approval) by going around the menu options.
  The page level check (after the menu is drawn) now checks all
  conditions (password expired, unverified, unapproved, timedout, and
  also nologins()).

* Minor change in approveuser; do not show the new account to the
  project leader until the new user has verified his account.

* Change verification method, as reqwuested by Dave.  In addition to
  providing the key, also provide a web link to take the user straight
  to verification. I actually take them direct to the login page, and
  pass the key in as an argument. If the user is already logged in,
  bypass and go directly to the verify page (not the form page of
  course).  If the user is not logged in, let him log in, and then
  forward the key onward to the verify page. Basically, bypass the
  form all the time, and just do the verification.

* Minor change in showuser; Do not show pid/groups not approved in,
  and if the count is zero, do not draw the table headings.

Small change for expts in TBOPSPID (emulab-ops for us): Instead of vname (which isn't usually defined), show when it was reserved to the expt. Great for checking on reloading nodes, hwdown nodes, etc.

to indicate that the kernel is does not touch the disk. Defaults to 1
for all osids so that a disk reload is forced (via the last_reservations
table).

sorting options. I have not done anything with the experiment listing
though since I'm hoping to get better info out of the slothd stuff, so
might as well wait.

"approved" designation is confusing. Changed to reflect group
membership trust!=none instead of user status=active since thats what
people really want to know.

the node control page. Add verbose option to add sharks to list; off
by default.

Update pages appropriately. Also cleanup up a few more sub menus.

supporting autocreating and autoloading images. The imageid form now
sports a field to specify a nodeid to create the image from; If set,
the backend create_image script is invoked. Thats the easy part.
Slightly harder is autoloading images based on the osid specified in
the NS file. To support this, I have added a new DB table called
osidtoimageid, which holds the mapping from osid/pctype to imageid.
When users create images, they must specify what node types that image
is good for. Obviously, the mappings have to be unique or it would be
impossible to figure it out! Anyway, once that image mapping is
in place and the image created, the user can specify that ID in the NS
file. I've changed os_setup to to look for IDs that are not loaded,
and to try and find one in the osidtoimageid. If found, it invokes
os_load. To keep things running in parallel as much as possible,
os_setup issues all the loads/reboots (could be more than a single set
of loads is multiple IDs are in the NS file) at once, and waits for
all the children to exit. I've hacked up os_load a bit to try and be
more robust in the face of PXE failures, which still happen and are
rather troublsesome. Need an event system!

Contained in this revision are unrelated changed to make the OS and
Image IDs per-project unique instead of globally unique, since thats a
pain for the users. This turns out to be very messy, since underneath
we do not want to pass around pid/ID in all the various places its
used. Rather, I create a globally unique name and extened the OS and
Image tables to include pid/name/ID. The user selects pid/name, and I
create the globally unique ID. For the most part this is invisible
throughout the system, except where we interface with the user, say in
the web pages; the user should see his chosen name where possible, and
the should invoke scripts (os_load, create_image, etc) using his/her
name not the internal ID. Also, in the front end the NS file should
use the user name not the ID. All in all, this accounted for a number
of annoying changes and some special cases that are unavoidable.

(somewhat) so that we can do submenu easily in other pages.

	tb-set-node-routertype $node none|gated

Added slots to virt_nodes and nodes table. This stuff is carried
through so that tmcd can get at it and pass it back to client.

request.

check box means. Also add links from the begin experiment page and
from the experiment information page to the FAQ entry. Lets see if
this helps.

stuff so that the web page did not need to do anything except display
and form processing. Add tbsetup/node_control for backend so that it
can be called from the command line too. The virt_nodes table is also
updated (for those values that have virt_nodes equivalents), and this
mostly implies that changes can be applied only to swapped in
experiments since we use the reserved table to map pcXXX to its vname
so that the virt_nodes table can be updated. It is an easy extension
to allow changes based on the pid/eid/vname, but I do not see a reason
to support this ability yet. Note usage:

    Usage: node_control name=value [name=value ...] node [node ...]
           node_control -e pid,eid name=value [name=value ...]
           node_control -l
    For multiword values, use name='word0 ... wordN'
    Use -l to get a list of operational parameters you can change.
    Use -e to change parameters of all nodes in an experiment.

    {824} stoller$ /build/testbed/install//bin/node_control -l
      next_boot_osid            - (administrators only)
      startup_command
      bios_version              - (administrators only)
      rpms                      - (multiple options allowed)
      default_boot_cmdline
      default_boot_path
      default_boot_osid
      next_pxe_boot_path        - (administrators only)
      tarfiles                  - (multiple options allowed)
      pxe_boot_path             - (administrators only)
      next_boot_cmdline         - (administrators only)
      deltas                    - (multiple options allowed)
      next_boot_path            - (administrators only)

pages now show the lastlogin info that is gathered from sshd syslog
reporting to users. That info is parsed by security/genlastlog.c, and
entered into the DB in the nodeuidlastlogin and uidnodelastlogin
tables. If not obvious from the names, for each user we want the last time
they logged in anyplace, and for each node we want the last time anyone
logged into it. The latter is obviously more useful for scheduling
purposes. All of the various images have new /etc/syslog.conf files,
and the 6.2 got new sshd_configs (all cvsup'ed with kill -HUP). There
is an entry in boss:/etc/crontab and users:/etc/syslog.conf. All of
this is decribed in greater detail in security/genlastlog.c.

Remove hot list for osids from big node listing to cut down on the
size of the html that gets spit out.