GitLab

The reason for the duplicate profile happens when you instantiate a
version of the profile, then terminate. That takes you back to the
instantiate page with default=uuid-of-profile, and if that is a version
uuid, we end up with a duplicate cause the list is based on the profile
uuid.

This closes issue #190.

I ALMOST got sucked into making big changes that would have required
a version change.

lists on the genirack control switch, to block access to the ILOs. Would
need to be localized to the rack network of course, and I vaguely
remember that some of the switches had different firmware and so the
commands had to be changed. Also note the netmasks are inverted from
what we normally think they should be. OH HP ...

Added PortalProfiles to the systems project list

See merge request !19

placement==SYSVOL blockstores would not work on Linux because of this.

command to set the push url.

before instantiating.

when they have leaked.

take out line with the string SupportAssist

instructions about what to do and stern warnings.

The main point of the changes are to require that the old password is
provided when changing your password. This holds true even for admins
changing their own password in red-dot. Note though, that when an admin
changes another user's password in red-dot, old password is not
required, which is somewhat in conflict with the overall goal, but hey,
we want to be practical too.

I ended up removing password modification from the profile page, and
use the already existing changepswd page, which I cleaned up and turned
into a first class ajax citizen to make the page operate smoother.

If the portal pages are wrapped in an iframe, they notify the outer page as the user navigates around the portal. They also notify the outer page when the user navigates away from the portal.

When invoked by a subboss, returns key=value pairs from subboss_attributes
for all services for that subboss. Will be used to configure subbosses,
eliminating the need to customize startup scripts per-subboss.

expt_expires slot in the experiments table whenever we set the slice
expiration time. In addition, do this in GetTicket() so that the
mapper sees the proper expiration time; we do not set the slice
expiration until the ticket is redeemed, and this throws off admission
control.

Required to avoid possible inconsistencies if any optimistic concurrent
readers are inspecting the state.