Op dinsdag 14 april 2015 14:07:24 UTC+2 schreef akash bhatia: > > > i just want to understand the concept of how to achieve the same on the > AWS, where we dont have liberty to customise domain name while creating a > new instance in AWS EC2. > > It is possible to set your own custom domain name on AWS VPC (not on EC2) via DHCP Option Sets. See http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html.
Also you have the option of providing 'cloud-config' user-data to the instance at creation time, if your distro supports the cloud-init system. Most modern distros support this, on EC2 and VPC. For example: #cloud-config hostname: mynode fqdn: mynode.example.com manage_etc_hosts: true I agree with the other replies though, that it's probably better to rely on facts/tags to specify roles than on hostnames or certnames. We're guilty of the latter though, encoding the role into the node's certname and using that in site.pp to select nodes. We use cloud-init to set the certname via user-data during node creation and automatically connect to our puppet master. Similar to this: http://cloudinit.readthedocs.org/en/latest/topics/examples.html#setup-and-run-puppet. It works, but we're moving toward the tags method. -- 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/fec23506-1074-450f-8944-63e3461b81c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
