7d3d7824c9
Implemented Orhcestrator task DeployNode (only network config for now) Implemented Driver task ApplyNodeNetworking Refactored Driver task CreateNetworkTemplate to fix design that left network in a state that wouldn't support node configs Updated the YAML example with some changes to support network refactoring - HostProfile field 'primary_network' specifies the network a node should use for default gateway - NetworkLinks now must list all allowed networks for that link and a Network is allowed only on a single link Updated YAML ingester to accept schema changes
MaaS Node Driver
This driver will handle node provisioning using Ubuntu MaaS 2.1. It expects the Drydock config to hold a valid MaaS API URL (e.g. http://host:port/MAAS/api/2.0) and a valid API key for authentication.
Drydock Model to MaaS Model Relationship
Site
Will provide some attributes used for configuring MaaS site-wide such as tag definitions and repositories.
Network Link
Will provide attributes for configuring Node/Machine interfaces
Network
MaaS will be configured with a single 'space'. Each Network in Drydock will translate to a unique MaaS fabric+vlan+subnet. Any network with an address range of type 'dhcp' will cause DHCP to be enabled in MaaS for that network.
Hardware Profile
A foundation to a Baremetal Node definition. Not directly used in MaaS
Host Profile
A foundation to a Baremetal Node definition. Not directly used in MaaS
Baremetal Node
Defines all the attributes required to commission and deploy nodes via MaaS
- bootdisk fields and partitions list - Define local node storage configuration to be implemented by MaaS
- addressing and interface list - Combined with referenced network links and networks, define interface (physical and virtual (bond / vlan)) configurations and network addressing
- tags and owner data - Statically defined metadata that will propagate to MaaS
- base_os - Select which stream a node will be deployed with
- kernel and kernel params - Allow for custom kernel selection and parameter definition