Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1066830

Summary: [RFE] Adding hosts to openstack foreman the easy way
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: foreman-installerAssignee: Gilles Dubreuil <gdubreui>
Status: CLOSED WORKSFORME QA Contact: Omri Hochman <ohochman>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0CC: aberezin, dcleal, hbrock, morazi, oblaut, ohochman, rhos-maint, yeylon
Target Milestone: ---Keywords: FutureFeature, UserExperience
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Cause: Consequence: Fix: Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-19 03:09:50 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:
Attachments:
Description Flags
foreman_client.sh none

Description Ofer Blaut 2014-02-19 07:55:36 UTC 
Description of problem:

When openstack foreman is not used to provision hosts 

We must have fast and easy way to add hosts to openstack deployment.

The current operation require user to login to the hosts and 

1. copy foreman_client.sh from foreman server
2. run it on the host

or start adding many different parameters that can be taken from the host like:

ip/mac/OS/.......

we must add in foreman server ability to add host with two clicks 

user will do:
1. add new host
2. provide only ipaddress / user /password of the new hosts
3. select host group to host 
the foreman will do:
4. push the client script to the new host
5. run the script on the hosts and report installation log
6. update the host with the new host group details 

This is how it is being done by RHEVM as well when adding new host with only OS


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Dominic Cleal 2014-02-19 13:58:35 UTC 
Some related work is being done in Foreman upstream to improve this, but not by connecting from Foreman to the client.  Instead it's a client registration tool, a bit like the foreman_client.sh script shipped in openstack-foreman-installer.

http://projects.theforeman.org/issues/3506
Comment 3 Gilles Dubreuil 2014-08-15 02:35:55 UTC 
Created attachment 926956 [details]
foreman_client.sh
Comment 4 Gilles Dubreuil 2014-08-15 02:54:04 UTC 
The generated /tmp/foreman_client.sh script (see attachment) not needed when:

1. A puppet DNS alias is assigned to The Foreman server
2. Hosts are built with puppet installed and activated by default

Let me explain:
- Puppet agents search for a host named 'puppet' by default unless the server parameter is set. Just by adding a DNS alias to the Foreman server will automatically make all nodes to register.

- 'Pluginsync = true' is the default (I believe from Puppet 3.x):
https://docs.puppetlabs.com/references/latest/configuration.html#pluginsync

Above two makes augeas package and associated augtool rules not needed.

- Puppet is required (prerequisite) to be installed on any host to work with Foreman/Puppetmster(Foreman-proxy). 
If foreman is provisioning the hosts,
then puppet should be added in the package list 
otherwise it's assumed it's already there.

In the case someone doesn't or can't use 'puppet' alias then the hosts would have to built with the puppet server defined in /etc/puppet/puppet.conf

I think thee default behavior is the most flexible approach.
Unless someone disagree, I'm tempted to close this RFE.
Comment 5 Gilles Dubreuil 2014-09-19 03:09:50 UTC 
Closing it.

Please reopen if needed.