Apache VCL logo Apache Software Foundation logo

Provisioning Engine Module Interface Specification

Background

{color:#6600ff}{}Explain: {color:#6600ff}{}define what we mean by "provisioning system" {color:#6600ff}{}give examples of provisioning systems{}{color} {color:#6600ff}{}could be bare metal, virtual, differentiated, undifferentiated, a service, a special piece of hardware, eventually VCL could provision various types of resources{}{color} {color:#6600ff}{}relationships among mgt nodes, computers, provisioning systems (such as computer is assigned 1 prov system at a time) {color:#6600ff}{}computer.provisioningid{}{color} {color:#6600ff}{}provisioning table{}{color} {color:#6600ff}{}future: management node to provisioning mapping{}{color} {color:#6600ff}{}provisioning module implementation is responsible for knowing which OS interactions are necessary{}{color} ** {color:#6600ff}{}image.pm calls provisioner->capture, new.pm calls provisioner->load, it calls OS subs as necessary{}{color}

Provisioning Module Subroutines

It is highly recommended that all provisioning modules implement the following subroutines.  There may be many additional subroutines implemented within a provisioning module.  These will not be called by any of the core VCL modules. #node_status #capture #load #power_off #power_on #power_reset #get_current_image #get_image_size


node_status

** The status key/value tells the vcl system the node is ready or needs to be reloaded.

capture

load

power_off

power_on

get_current_image

get_image_size {anchor:get_image_size}