Re: [Puppet Users] Q: Maintaining installation profiles and privisioning using puppet

2014-12-07 Thread Tomasz Kloczko
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.


Re: [Puppet Users] Q: Maintaining installation profiles and privisioning using puppet

2014-12-07 Thread James A. Peltier
| 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

If you don't know what you want to accomplish then asking us for help is going 
to be an exercise in futility. It sounds like you need to write a puppet module 
that will generate all the configuration necessary to make a machine install. 
Razor can do that. If that wouldn't work then you need to write the puppet code 
to do it yourself. 

-- 
James A. Peltier 
IT Services - Research Computing Group 
Simon Fraser University - Burnaby Campus 
Phone : 778-782-6573 
Fax : 778-782-3045 
E-Mail : jpelt...@sfu.ca 
Website : http://www.sfu.ca/itservices 
Twitter : @sfu_rcg 
Powering Engagement Through Technology 
Build upon strengths and weaknesses will generally take care of themselves - 
Joyce C. Lock 

-- 
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/44519995.10226126.1418004550347.JavaMail.zimbra%40sfu.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Q: Maintaining installation profiles and privisioning using puppet

2014-12-07 Thread Tomasz Kloczko
[..] 

 If you don't know what you want to accomplish then asking us for help is 
 going to be an exercise in futility.  It sounds like you need to write a 
 puppet module that will generate all the configuration necessary to make a 
 machine install.  Razor can do that.  If that wouldn't work then you need 
 to write the puppet code to do it yourself.


Sorry by above contain kind of contradicting sentences. You wrote that I 
need to write my own module and  in the same time razor can be used on what 
I want to accomplish.
???

Whatever install server is using generic services like TFTP and for example 
HTTP. Changing DHCP configuration can be done by regenerating his config 
file and reload dhcpd as service.
New node identification is not done automagically but it must using some 
generic services. 
All these services are using the files so theoretically whatever cap is 
build on top of these services should be kind of generator of exactly what 
I need.
Simple razor description does not says to much about how exactly it works.

If you are using razor you should be able to answer on my questions about 
node tagging/node identification and confirm how exactly is is done 
interaction with TFTP/HTTP/FTP servers :)

Regards

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/daa0e0f1-15d2-492d-bac9-135ef8f753c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Q: Maintaining installation profiles and privisioning using puppet

2014-11-21 Thread Tomasz Kloczko
Hi,

I just stated looking closer on the puppet so please forgive me if my 
questions or dilemmas would be a little not accurate in context of puppet.

I'm trying to solve couple of problems with install infrastructure for more 
than one OS. Let's say that initially would be rpm based Linux and Solaris.
Generally installation infrastructure across many hosts shares some set of 
stages like a choosing set of software which needs to be installed, 
authentication setup, choosing devices(s) used on install etc.
In case Linux to perform such set of operation you must have kickstart 
profile which will do all what is needed. In case Solaris you must have 
personalized AI profile and manifest.
Updating install profiles it is modifying set of KS profiles and for 
example files with PXE bootloader configuration files in pxelinux.cfg/ 
directory served by TFTP server. In case AI installer profiles and 
manifests must be updated and imported to AI database.
Additionally on higher level it would be good to keep track some additional 
settings like guarantee that none of two hosts will be sharing the same 
addresses, updating DNS records, updating firewall settings or switches 
ACLs.

In this case I'm not talking about automate simple installation but whole 
multistage provisioning process which should be not started if some 
dependence will be not fulfilled and/or even committing some new change in 
setup should be refused if some inconsistencies will be not fulfilled.

I know that I can solve such set of problems using quattor and pan 
language. Problem is that IMO quattor community has IMO real problems with 
lack of understanding present days large scale installations in 
heterogeneous envs which makes choosing this software in long term a bit 
risky.
Puppet seems has much healthier community and such risk is IMO way lower.

Questions only is am I will be able to solve all my above problems with 
install infrastructure using puppet using set of templates, with per host 
parameters, dependency rules and checking automatically on updating host(s) 
install settings automatically to start whole cascade of updates in 
provisioning process set of additional actions to update DNS, other files 
on some hosts easier than using quattor?
If such answer would be positive can I ask someone to point on  some needed 
here documentation(s) to dig by myself for necessary details? :) 

I'll be really appreciated any comments or advice If anyone is using puppet 
or other software solving something similar :)

Regards

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/3f749ea3-5e85-4f7b-88d0-61fe00af9041%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Q: Maintaining installation profiles and privisioning using puppet

2014-11-21 Thread James A. Peltier
| Hi,

| I just stated looking closer on the puppet so please forgive me if my
| questions or dilemmas would be a little not accurate in context of puppet.

| I'm trying to solve couple of problems with install infrastructure for more
| than one OS. Let's say that initially would be rpm based Linux and Solaris.
| Generally installation infrastructure across many hosts shares some set of
| stages like a choosing set of software which needs to be installed,
| authentication setup, choosing devices(s) used on install etc.
| In case Linux to perform such set of operation you must have kickstart
| profile which will do all what is needed. In case Solaris you must have
| personalized AI profile and manifest.
| Updating install profiles it is modifying set of KS profiles and for example
| files with PXE bootloader configuration files in pxelinux.cfg/ directory
| served by TFTP server. In case AI installer profiles and manifests must be
| updated and imported to AI database.
| Additionally on higher level it would be good to keep track some additional
| settings like guarantee that none of two hosts will be sharing the same
| addresses, updating DNS records, updating firewall settings or switches
| ACLs.

| In this case I'm not talking about automate simple installation but whole
| multistage provisioning process which should be not started if some
| dependence will be not fulfilled and/or even committing some new change in
| setup should be refused if some inconsistencies will be not fulfilled.

| I know that I can solve such set of problems using quattor and pan language.
| Problem is that IMO quattor community has IMO real problems with lack of
| understanding present days large scale installations in heterogeneous envs
| which makes choosing this software in long term a bit risky.
| Puppet seems has much healthier community and such risk is IMO way lower.

| Questions only is am I will be able to solve all my above problems with
| install infrastructure using puppet using set of templates, with per host
| parameters, dependency rules and checking automatically on updating host(s)
| install settings automatically to start whole cascade of updates in
| provisioning process set of additional actions to update DNS, other files on
| some hosts easier than using quattor?
| If such answer would be positive can I ask someone to point on some needed
| here documentation(s) to dig by myself for necessary details? :)

| I'll be really appreciated any comments or advice If anyone is using puppet
| or other software solving something similar :)

| Regards

| Tomasz

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).

-- 
James A. Peltier
IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone   : 778-782-6573
Fax : 778-782-3045
E-Mail  : jpelt...@sfu.ca
Website : http://www.sfu.ca/itservices
Twitter : @sfu_rcg
Powering Engagement Through Technology

-- 
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/2131372170.97964324.1416597082627.JavaMail.zimbra%40sfu.ca.
For more options, visit https://groups.google.com/d/optout.