Jason Hennessey

That works! I wouldn't mind some redundancy in this area (constructor & schema) either.

You could also implement this for `project_delete`

Could you give an example or 2 of better ways to do constraints? Are you thinking DB triggers/constraints?

Since this isn't a security issue like #804, I'm not convinced we need to address it; it's more about forcing a certain way of using HIL, which is debatable. The...

The [README](https://github.com/CCI-MOC/hil/blob/master/README.rst) says that we require python 2.7, so that portion is solved, but I like the thoughts from @zenhack for slowly transitioning to python 3, so let's make this...

In theory, I totally agree with this. The "admin" check was a stop-gap until we had something better (which happened to agree with what OpenStack does by default IIRC). My...

Now that we have set_bootdev(), I agree that it's no longer necessary to set a default boot device (to support that, the [deployment guide](https://github.com/CCI-MOC/hil/blob/master/docs/deployment.md) recommends having a particular boot order...

FYI - from [api.py/show_node()](https://github.com/CCI-MOC/hil/blob/af98ba26f79bc884c9189341210e21f05c6b1b3d/hil/api.py#L1139), it looks like any user can do a show_node() on a free node. So I think storing it as a metadata item is viable.

The issue here is that nodes can differ on what they support, so HIL needs a per-node way of representing that. If we go with @Izhmash 's suggestion where we...

From [what I can tell](https://docs.travis-ci.com/user/reference/trusty/), one only gets a single .travis.yml, which has a single global "sudo" statement. Another option would be to add another CI service like CircleCI, though...