On Friday, 21 November 2014 19:11:37 UTC, James Peltier wrote:
>
> You are talking about merging provisioning and management of machines in 
> such a way that Puppet would control all aspects of the infrastructure, 
> including what OS would be provisioned on the bare metal and then how it 
> would be maintained throughout its lifecycle using Puppet.  It sounds like 
> you're interested in Puppet Razor (
> https://docs.puppetlabs.com/pe/latest/razor_intro.html). 


To be honest I'm not sure is it what I'm looking for.
Intro describing how razor works mention about new node identification. 
There is no even single word how it works. Is it don by boot on new host 
some stub system which identifies physical attributes? It catches some data 
from DCP srver about new/unknown MAC addresses?
Node tagging with node identification: to be hones I'm not sure do i need 
it.
I don't want to start ANY installation if for example some newly appeared 
physical host would be manually assigned to some exact template so all what 
I need is only list of new/unidentified hosts. Appearance of new/unknown 
host requesting to install something (DHCP requests) should be even treated 
as alarm.

To be hones all what I need is transforming some puppet per host 
description to DHCP config entry and generate some files: one in tftproot 
in pxeboot,cfg/ directory and second one injecting files in http served 
directory like kickstart file or in case Solaris profile and manifest. I'm 
not going to use full aminstall because it is only frontend on maintain 
DHCP configuration and assign profile/manifest. In other words I'm not 
going to organize using puppet aminstall frontend.

>From point of view maintaining kickstart or Solaris profile/manifests I 
need only some generator of those files basing on data like used software 
repositories, ability to describe used authentication, storage layout 
setup, system setup like used DNS servers, etc

Tomasz

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/66dfe7f4-86fb-4589-8192-7b4d689b138e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to