[OFI] Initial foreman provisioning setup design

Marek_Hulan · March 12, 2014, 3:58pm

Hello

I uploaded the design of two ways how can we setup provisioning in foreman. I
think we are deciding between option A and B, others are just not to forget
them.

Me and Dan prefer option A but I'd like to hear your opinions. You can read
the design here [1]. Let me know if anything is unclear.

[1]

github.com

ares/OFI/blob/install_design/doc/staypuft_foreman_init.md

# Staypuft Foreman initial setup design

## What we need (ordered by priority):

* automatic setup with minimal user interaction (max 1 answer whether he wants automatic setup or advanced configuration wizard)
* wizard must be easy to use for people who don't know foreman
* it must be possile to run in advanced mode (post April) to customize all values
* it should be easy to change configuration after initial setup
* must work disconnected

## What we need to setup

* Subnet 
  * create a subnet that does not exist yet (free IP validation) - we need unassigned NIC or should we try to create new one?
  * allow to skip if user want to use existing (post April)
  * selection of any existing subnet*
* Domain
  * based on machine domain
  * do we need to allow using other domain (post April)
* DHCP, DNS, TFTP parameters (based on Subnet and Domain)

This file has been truncated. show original

···

-- Marek

Petr_Chalupa · March 14, 2014, 9:38am

(A) sounds good to me. I think user will be supplying only few values so
we do not need (B) with UI.

···

On 12.03.14 16:58, Marek Hulan wrote: > Hello > > I uploaded the design of two ways how can we setup provisioning in foreman. I > think we are deciding between option A and B, others are just not to forget > them. > > Me and Dan prefer option A but I'd like to hear your opinions. You can read > the design here [1]. Let me know if anything is unclear. > > [1] > https://github.com/ares/OFI/blob/install_design/doc/staypuft_foreman_init.md >