Puppet Cloud Provisioner with AWS Instances with DNS Names instead of Hostnames

asked 2013-10-21 18:14:23 -0600

louis gravatar image

updated 2013-10-21 18:16:04 -0600

Hi,

We are testing the puppet node_aws command line to provision a new puppet enterprise master instance and also a puppet enterprise agent instance. At the moment we used the ${HOSTNAME} environment variable on the answers file....

q_all_in_one_install=y
q_database_host=localhost
q_database_install=y
q_database_port=5432
q_database_root_password=F6SBIUAHb3CsqmuFaAev
q_database_root_user=pe-postgres
q_install=y
q_pe_database=y
q_puppet_cloud_install=y
q_puppet_enterpriseconsole_auth_database_name=console_auth
q_puppet_enterpriseconsole_auth_database_password=OKlRzsfUvBft7nBkmiLr
q_puppet_enterpriseconsole_auth_database_user=console_auth
q_puppet_enterpriseconsole_auth_password=root
q_puppet_enterpriseconsole_auth_user_email=root@mycompany.com
q_puppet_enterpriseconsole_database_name=console
q_puppet_enterpriseconsole_database_password=hUiQjobxOt7UCVKXMNuv
q_puppet_enterpriseconsole_database_user=console
q_puppet_enterpriseconsole_httpd_port=443
q_puppet_enterpriseconsole_install=y
q_puppet_enterpriseconsole_master_hostname=${HOSTNAME}
q_puppet_enterpriseconsole_smtp_host=nont
q_puppet_enterpriseconsole_smtp_password=
q_puppet_enterpriseconsole_smtp_port=25
q_puppet_enterpriseconsole_smtp_use_tls=n
q_puppet_enterpriseconsole_smtp_user_auth=n
q_puppet_enterpriseconsole_smtp_username=
q_puppet_symlinks_install=y
q_puppetagent_certname=${HOSTNAME}
q_puppetagent_install=y
q_puppetagent_server=${HOSTNAME}
q_puppetdb_database_name=pe-puppetdb
q_puppetdb_database_password ...
(more)
edit retag flag offensive close merge delete