slapos_cloud: HostingSubscription_view: Add links to access elements from columns in instances list.

Typo fix of commit 7467ef4c

/reviewed-on nexedi/slapos.core!87

If there is not changes in slapformat.xml, current slapformat will not dump computer
resources (as well as partition resources).

For compatibility with olders version of slapformat, dump partition resources
if it's not created yet event if the file slapformat.xml didn't change.

/reviewed-on nexedi/slapos.core!88

https://docs.python.org/dev/whatsnew/3.2.html python3 warns about not unclosed files and sockets.

Use context managers with files to close them.

Use context manager to close socket to supervisor on python 3. On python 2 these sockets remain not closed as before.

There are a few warnings left, but output starts to be readable again.

/reviewed-on nexedi/slapos.core!78

tap_ipv6 option let you chose if you want IPv6 on the taps or not. Some
customers may decide to have only IPv4 inside their VMs.

We put only 1 address on the tap itself (e.g.
2001:67c:1254:e:89:69b0:ffff:ffff/128 instead of
2001:67c:1254:e:89:69b0:ffff:ffff/96) otherwise, when we assign the
address 2001:67c:1254:e:89:69b0::/96 inside the VM, the address has
"dadfailed" status (dad = "Duplicate Address Detection"). The problem
appears only with address "0" (ending in ::) but not with others
addresses. We had 2 solutions:
 * put only one address on the tap (the solution we choose)
 * forbid address "0" inside the VM

The chosen solution has the advantage that the host machine won't
answer the ping on behalf of the VM since the tap has only 1 address
(its own).

/cc @alain.takoudjou

/reviewed-on nexedi/slapos.core!86

This indicates on the transaction and on indexation that a payment was created for the invoice. This allow us to avoid duplicated creation due race conditions on activities.

slapos_payzen: Skip invoice if payment was created on the same transaction or if the payment wasn't indexed yet

  Otherwise it will lead to random failures caused by some race conditions

Update tests to follow up changes on the UI and replace repeated parts by macros.

There ins't a major change of behavious here

Speed up the rendering and only do xhr to update if the user stays long enough on the page.

This change will significally drop the number of xhr on the site.

It is not ideal, but it works quite fine (since 994d836996f8e762924b2898ef3a6385ad7d5759). Callable scripts should be used to avoid extra queries or calculations.

Reimplement the wrapper to follow up this change:

nexedi/erp5@f9c408f7

Implement a backend automated logic for Ticket management on hateoas UI. This interaction workflow replaces script calls, and custom inits for the portal type.

This inteaction workflow could be explited per impacted business template or moved into slapos_hal_json_style to be more consistent.

The call to web_message stop was replaced by an interaction workflow entry along with the dummy sets with values hardcoded on the UI.

In general, UI should be cleaned up to contain its minimal necessary for API and all the deeper logic should be implemented exclusively on the backend.

Update the fork of slapos with ERP5 Code.

Make it return to Home

This bt5 is not present on production, however, it is helpfull to have this script on a development machine.

 Follow up changes from ERP5 after the rebase

  This shouldn't be tested on this project scope.

  This test lacks the use case of same user transaction

 The Base.reindexObject is not called directly anymore, so patch a deeper level

reorganise a bit the code so that resources that we cleanup in finally:
happens just before the try:

Also, remove the handler in finally case, partitions that where failing
again and again apparently added handler again and again.

by using it getSupervisorRPC in a context manager which on python 3
automatically closes.
This needs fix from https://github.com/Supervisor/supervisor/issues/1184
we assume that this fix is only on python 3.
On python2, we keep this same behavior of not closing socket explicitly
and leaving it to destructors.

Also re-raise a few error cases that were ignored.

They will be closed in __del__, probably soon enough, but it's cleaner
to close explicity. This also stops the ResourceWarning on python3