This part contains workflows modifications.

Threat Slave Instance as same as Software Instance in this case.

Add role to allow a Software Instance access and edit the Slave Instance installed in the same computer partition and software release.

Add new transitions to follow the same design of Software Instance and the scripts to each transition

Add transitions to start and stop a Slave Instance and the scripts used to each transition. The goal is to follow the same design of Software Instance

Do not try to request start not fully installed computer partition, and wait
until instance setup packing list is stopped, before trying to create hosting
one.

Beside of setting state on Software instance by start/stop requested methods
setup in activities real request. Thanks to this *after* computer partition is
installed (instance setup packing list == stopped) the request becomes
synchronous (...a bit later -- in sense -- just once called).

Keep backward compatibility and start automatically just after partition become
available.

Implement start_requested and stop_requested states in order to have stateful
information about software instance requested state.

Asynchronously read software instance state and take proper actions in such
case (only after .available() call for now).

Note: Done in one big commit, as changes are interrelated, and impact system
functionality.

Use by default checkUserCanChangePassword, but as in ERP5 users do not have
such persmission to Person document which defines them, check if logged in user
login is same as document reference.

- Added portal type Slave Instance;
- Created SlaveInstance_view without ssl_key and ssl_certificate
- Created slave_instance_slap_interface_workflow and associated it to Slave Instance

It allows to get/revoke certificates for Person. Protected in same way as setting Person's password.

SLA XML is stored on Software Instance, but in many place the dictionary have
to be used.

Later is shall be used in order to being followed.

Whenever software instance is begin started or destroyed new packing list have
to be created. But in both cases it is not desirable to have more then one
active packing list related to current step of state. So dissallow it by
passing tag and checking for its existence. Even more -- serialize in order to
lock operation on one Software Instance in transaction.

As Hosting Subscription is common document for all Software Instances used in
request process, use it to find common parameters of all deliveries.

SoftwareInstance_createSalePackingList shall be able to work for requested
software instances.

Previous location: https://gitorious.org/vifib/slapos-master