Bug 1038864

Summary: [Doc] Update Foreman description to include provisioning modes
Product: Red Hat OpenStack Reporter: Summer Long <slong>
Component: doc-Installation_and_Configuration_GuideAssignee: Scott Radvan <sradvan>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: high    
Version: 4.0CC: aberezin, rlandman, sradvan, yeylon
Target Milestone: z2Keywords: Documentation
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-04 00:04:52 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:
Bug Depends On:    
Bug Blocks: 1049118    

Description Summer Long 2013-12-06 00:49:20 UTC
Description of problem:
Provisioning vs non-provisioning modes should be made explicit in the overview section for Foreman.  The customer should be given the system prereqs.


Additional Info:
> > 3) What is the expectation for where the actual RPMs come from?  Are
> > customers expected to initially provision systems via Satellite and then
> > Foreman helps install the rest of the content?  RHN?

From Mike Orazi:
> There are really 2 modes you can set up Foreman to use:
>   - Provisioning mode is where foreman will pxe boot machines from
> scratch and apply all the puppet magic to realize the machine as a
> member of the correct host group.  This can consume content from either
> RHN or Satellite
> 
>   - Non-provisioning mode where the end user is expected to provision
> the machine and register it back to the correct host group in Foreman
> and then applies all the correct puppet magic to the existing machine.
> Non-provisioning mode likewise can pull content from either RHN or
> Satellite depending on how the machine is initially provisioned.
> 
> NOTE:  Non-provisioning mode is easier to develop and debug against so
> we typically run through those scenarios a lot more frequently than
> provisioning mode