driver

package
v0.16.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Mar 19, 2024 License: Apache-2.0 Imports: 16 Imported by: 0

Documentation

Overview

Package provider contains the cloud provider specific implementations to manage machines

Package provider contains the cloud provider specific implementations to manage machines

Index

Constants

This section is empty.

Variables

View Source
var Decoder = serializer.NewCodecFactory(install.Install(runtime.NewScheme())).UniversalDecoder()

Decoder is a decoder for a scheme containing the mcm-openstack APIs.

Functions

func DecodeProviderSpec

func DecodeProviderSpec(decoder runtime.Decoder, raw runtime.RawExtension) (*openstack.MachineProviderConfig, error)

DecodeProviderSpec can decode raw to a MachineProviderConfig.

func NewOpenstackDriver

func NewOpenstackDriver(decoder runtime.Decoder) driver.Driver

NewOpenstackDriver returns a new instance of the Openstack driver.

Types

type OpenstackDriver

type OpenstackDriver struct {
	// contains filtered or unexported fields
}

OpenstackDriver implements and handles requests via the Driver interface.

func (*OpenstackDriver) CreateMachine

CreateMachine handles a machine creation request

OPTIONAL IMPLEMENTATION LOGIC It is optionally expected by the safety controller to use an identification mechanism to map the VM Created by a providerSpec. These could be done using tag(s)/resource-groups etc. This logic is used by safety controller to delete orphan VMs which are not backed by any machine CRD

func (*OpenstackDriver) DeleteMachine

DeleteMachine handles a machine deletion request

func (*OpenstackDriver) GetMachineStatus

GetMachineStatus handles a machine get status request

func (*OpenstackDriver) GetVolumeIDs

GetVolumeIDs returns a list of Volume IDs for all PV Specs for whom an provider volume was found

func (*OpenstackDriver) ListMachines

ListMachines lists all the machines possibly created by a providerSpec Identifying machines created by a given providerSpec depends on the OPTIONAL IMPLEMENTATION LOGIC you have used to identify machines created by a providerSpec. It could be tags/resource-groups etc

Directories

Path Synopsis

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL