prompt for license key during installer
|Status:||Needs More Information||Start date:||05/04/2011|
|Assignee:||Garrett Honeycutt||% Done:|
|Branch:||Affected PE version:|
I would like to see functionality similar to the following in the installer.
Please specify the path to your Puppet Enterprise license.key [leave blank for Evaluation]:
if left blank, have some text describing the evaluation period, node limit, etc.
if the path exists, do whatever license.key checking we do and perhaps show the output of ‘puppet license’ or something similar.
#6 Updated by Garrett Honeycutt over 2 years ago
The workflow you have stated makes sense for someone who is evaluating Puppet. The other case is where someone knows they want Puppet and wants to install it in a fresh environment.
So they skip to:
- Buy License
- Install Puppet Enterprise from scratch
- Figure out how to deploy the license file
Currently the installer does not have the ability to install a license file. I want the ability to specify in the answers file the location (local file system, HTTP, or HTTPS) of the license file for automation purposes.
#11 Updated by Nigel Kersten over 1 year ago
Garrett Honeycutt wrote:
I have at least one and possible many. Especially if you have separate puppet masters for each environment as opposed to using Puppet’s internal idea of environments.
Why are justifying automation anyways? :)
That wasn’t quite the question by the way. You only have to have the license file on your CA. How many deployments are you running across where you have multiple CAs ?
#12 Updated by Garrett Honeycutt over 1 year ago
Infrastructures where you need a separate master for each environment due to network segregation are quite common among enterprise users. In these infrastructures, each environment needs a CA and nodes in one environment cannot speak to another environment.