Description of problem: In very big environments where over 800 Subnets and hundreds of Domains exist it is a very big overhead to be forced to configure Domains & Subnets in the Satellite Server when an IP Address Management system (IPAM) is already in place having all those information. Version-Release number of selected component (if applicable): 6.1.1 Actual results: User is forced to configure Domains & Subnets to be able to use Satellite Provisioning Expected results: Add the possibilty to specify Domain & Network information freely not having to create/manage hundreds of Domains & Subnets on host creation level. This would ease the integration of Satellite 6 to other provisioning frameworks where Satellite is only one of several tools being used to provisiong systems.
Created redmine issue http://projects.theforeman.org/issues/11622 from this bug
in that case dhcp / dns functionality will be turned off?
Upstream bug component is DHCP & DNS
Upstream bug component is Hosts
I tested this and it seems you always have to create a domain first to use it in the rest call: curl -k -u ${USER}:${PASS} -d "host[name]=test" -d "host[organization_id]=1" -d "host[location_id]=2" -d "host[hostgroup_id]=9" -d "host[mac]=11:11:11:11:11:11" -d "host[root_pass]=12345678" -d "host[domain_id]=1" -d "host[ip]=192.168.25.1" https://${SATELLITE_SERVER}/api/hosts It would be nice to either provide a fqdn to the host[name] field or create the domain automatically if it does not exist. An option host[domain_name] would then be required and you have to set either host[domain_name] or host[domain_id]. With the tested rest call it was not necessary to create a network first.
I tested some more and it seems you need to define a subnet to be able to create a bootdisk. If no subnet is defined for the new system i get this error message: Failed to render boot disk template: ERF42-7776 [Foreman::Exception]: Host has no subnet defined
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.