Bug 1186617

Summary:	Document how to provision a machine on a specific subnet/dns with a specific profile.
Product:	Red Hat Satellite	Reporter:	David O'Brien <daobrien>
Component:	Documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	satellite-doc-list
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.4	CC:	adahms, dmacpher, lzap, rdickens
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-11 14:40:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David O'Brien 2015-01-28 07:06:21 UTC

Describe the issue: 

Need background info and a procedure for how to achieve $summary.


Additional information: 

Using component=documentation until we establish which book this belongs in.

See https://www.youtube.com/watch?v=52K7gYAR84k for a demo.

SME = lzap

Comment 2 Lukas Zapletal 2015-01-28 15:47:51 UTC

What you mean by profile here?

Do you want me to record a video how to do that?

Comment 3 David O'Brien 2015-01-29 00:08:54 UTC

I believe "profile" means Host Group. Based on various facts from the discovered host, in this case subnet, then provision the host with a predetermined Host Group.

I haven't looked at the youtube recording in the description yet, but if you can do another or more complete video, that would be great, thanks :-)

David

Comment 4 Lukas Zapletal 2015-01-29 15:45:45 UTC

Oh that? It's easy.

1) Discovery a host
2) Find it (we have nice searching capabilities)
3) Click on Provision
4) You are taken to the New Host screen and the rest is exactly same as for New Host, except the MAC address is already filled in so you don't need to fill it.

Then we have this auto-provisioning which has some basics covered here:

http://theforeman.org/media.html -> Sprints > 31.

We should have a docs for auto-provisioning as well... I will be writing upstream docs soon. That could be a help! It will land here:

http://theforeman.org/plugins/foreman_discovery/2.0/

Comment 5 David O'Brien 2015-02-16 05:59:42 UTC

Cleaning up flags for easier reporting.

Comment 6 RHEL Program Management 2015-02-16 06:03:13 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 12 Dan Macpherson 2016-07-06 01:45:48 UTC

Hi Lukas,

Would the content here in the new Provisioning Guide cover the requirements for this BZ:

https://access.stage.redhat.com/documentation/en/red-hat-satellite/6.2-beta/provisioning-guide/#Provisioning_Bare_Metal_Hosts-Creating_New_Hosts_from_Discovered_Hosts

Was there anything else we should add to this section?

Comment 13 Lukas Zapletal 2016-07-08 08:06:14 UTC

Finish template is not required, other than that +1

Comment 14 Dan Macpherson 2016-07-11 03:22:25 UTC

Hi Lukas,

Removed the finish template:

https://access.stage.redhat.com/documentation/en/red-hat-satellite/6.2-beta/provisioning-guide/#Provisioning_Bare_Metal_Hosts-Creating_New_Hosts_from_Discovered_Hosts

Is there's nothing else, I'll close this BZ.

Comment 15 Lukas Zapletal 2016-07-11 09:55:25 UTC

OK TY