[VCL-67] Allow OS, provisioning engine, and other module objects to access each other

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.1
• Component/s: vcld (backend)
• Assignee: Andrew Kurth
• Reporter: Andrew Kurth
• Created: 26/Jan/09 16:03
• Updated: 10/Apr/09 19:30
• Resolved: 26/Feb/09 14:25

Description

State.pm currently handles the creation of OS and provisioning engine objects when a reservation begins to be processed. The state modules (new.pm for example) can access these objects and their subroutines. From within an OS module, a provisioning engine module cannot be accessed and vice versa. This is a limitation.

It would be beneficial if modules could access each other. Consider the following OS module example. Most OS modules contain code to perform a software reboot. If this fails, a hardware reset needs to be attempted. The OS module has no way of calling the provisioning engine module's subroutine which performs this function.