computer_install_command_line allows you configure the installation command for a computer (per website)

slapos_master_api allows you define where computers may connect to this master specifically.

This reverts commit 18ee7dad

/reviewed-on nexedi/slapos.core!107

configure local: Generate slapproxy conf for supervisord first, then supervisord certainly start slapproxy. Before this commit, slapproxy often did not start after "slapos configure local", that was because slapproxy conf did not exist when supervisord was launched.

See e02b451e for original commit

On some systems netmask can already contain /<bits>, so just use the
nu.me.ri.cal value.

/reviewed-on nexedi/slapos.core!106

Update the API to remove the additional get to get monitoring status information, this may cause a major improvement in speed, as the most of the queries to master are removed.

The initial "news" information is passed as parameter

  Indicate when instance is Slave, Stopped or Destroyed on the News Dict
  Display monitor url and more information on the monitor gadget

This API is deprecated, replaced by appropriated one

slapos_jio: Send connection parameters as part of the API for Hosting Subscriptions and Software Instances

The information can come to listbox or come as RAW to the query, allowing us to hight light some informations.

Since the compatibility with PY3.

This makes dev instance and production the similar.

Keep consistency with others alarms enabled related to upgrade.

This allow admin destroy software installations which are failing for example.

slapos_accouting: Don't split the Packing Lists with Consumption information like in Subscription Request

The Consumption Information should SUM always until the packing list be stopped. The Subscription Request however should be kept separated.

Some tools are using directly slapproxy sqlite database and they stopped working when table number was increased in nexedi/slapos.core!76 .

We made a quick improvement to the tools so that they can autodetect the current table names instead of hardcoding ( nexedi/slapos@b8c895cd ) but this failed, because slapproxy remove did not remove the old tables after migration. This branch is about removing the table, to quickly repair these tools.

The long term plan is (hopefully) to improve these tools so that they don't use the private tables like this.

/reviewed-on nexedi/slapos.core!105

Because we want to trigger an upgrade that will remove old tables.

Note that re-dumping database_dump_version_current fixed the column
order in software table - the dump was incorrect (this also change
output of `proxy show` for this test)

Create a test for each previous versions to current version (starting
from version 10, earlier versions are not really supported).

Procedure to add test for new version can be:
 * update table structure and increase version in slapos/proxy/schema.sql
 * use generate_dump.sh script to generate
   slapos/tests/test_slapproxy/database_dump_version_$NEW_VERSION.sql
   from slapos/tests/test_slapproxy/database_dump_version_$PREVIOUS_VERSION.sql
   (with computer_id "computer")
 * add TestMigrateVersion$(NEW_VERSION)ToLatest in
   slapos/tests/test_slapproxy/__init__.py
 * use generate_dump.sh script to update in-place
   slapos/tests/test_slapproxy/database_dump_version_current.sql
   (with computer_id "slaprunner")

Instead of keeping old tables which cause confusion for humans and tools
directly operating on the database, remove old tables and create a
separate backup file.