On 16/11/17 14:06, Neil Hanlon wrote: > Hey! Great question. > > The "Build Token" is (to my understanding) essentially there to keep > your servers from boot-looping when you PXE/network boot them.
Actually that's not quite true. Sending a GET to /unattended/built is what breaks the boot loop, but it'll work without a token (if you set token_duration to 0 they aren't added to the URL). Tokens exist to identify hosts. In the past, we identified a host by the incoming request IP on the GET - but this doesn't work if you're on a NATed connection from another subnet. In that scenario you only see the incoming IP of the gateway machine. Tokens were added as a way to combat that, and eventually became the default because it's more reliable. On 17/11/17 07:57, andpk wrote: > Hey Neil, thanks for your answer and explanation of the build token. > > i try just pasting the phone_home variable in my user_data template, > but it seems that it has no affect on the build token. After the last > puppet apply it still said: > > It contains just VMware customization settings and in the end the > phone_home. Did i misunderstood something? It's worth knowing that VMWare customization-spec isn't a 1:1 mapping to userdata - it's extremely restrictive, and many people have had problems getting the phone-home bit to work. Searching the archive will find you some hits on the topic, but I don't know exactly home to make it work, sadly. Maybe someone else does. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
