Adding the whole top-level available IPv6 range to the local table
conflicts with tun/tap usage. Instead, add only the IPv6 subranges
actually allocated to a partition.

This was introduced in 081e745e and I don't see how it could have been
useful.

See merge request !494

    It was used on OrderBuilder_generateUnrelatedInvoiceList but the code dont relies on it anymore.

See merge request !492

An error slipped in 92da569e (slapos_jio: Drop Handlebars, 2022-06-08)

    The forms were removed long ago, and those actions werent removed

See merge request !488

  Most liketly a copy and paste mistake

    Whenever you define a slave, the option_index inst the software-type but the property of the dict/object.

See merge request !487

  This category is used whenever the user wants disallow allocation for the time been. It do not intend to re-open again after a procedure or do not intend to terminate the machine, just dont want anything be allocated on it.

See merge request !486

   category close and not closed, and do not auto cancel upgrades for computers for termination.

   This should be handled by setting never on upgrade scope.

   Those actions were dropped from ancient site and forgotten to be removed.

   Only Monitor Scope should be taken into account.

   Whenever allocation scope changes, the capacity is close, and the proper alarm will re-open it later a moment after. This prevents when you change from close to open, to get a miss-updated window, and something is allocated before it capacity is calculated.

     Do not touch on monitor scope, except when it is None or allocation is "Close Forever", this allow the user to keep monitoring closed computers (Maintenance, termination...), since ONLY allocation is closed, and the computer is supposed to work normally with whatever is inside.

  ... to decide which computers to select for check for upgrades