The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #7399

prompt for license key during installer

Added by Garrett Honeycutt over 3 years ago. Updated about 2 years ago.

Status:Needs More InformationStart date:05/04/2011
Priority:NormalDue date:
Assignee:Garrett Honeycutt% Done:

0%

Category:-
Target version:-
Keywords: Affected URL:
Branch: Affected PE version:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the ENTERPRISE project on JIRA using the button below:


Description

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.

History

#1 Updated by Anonymous over 3 years ago

This will also require a change to the CloudPack install process, since it represents another piece of data required for installation.

#2 Updated by James Turnbull over 3 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

#3 Updated by Garrett Honeycutt over 3 years ago

Path should be either on the filesystem or a URL, so you can grab the license file via HTTP or HTTPS, which is how I currently bootstrap PE systems.

#4 Updated by Nigel Kersten over 3 years ago

What does adding this step do for the user Garrett?

Isn’t our expected workflow for users something like:

  • Download PE to evaluate
  • Decide they like it
  • Buy it
  • Install license

?

#5 Updated by Jeff McCune over 3 years ago

  • Status changed from Needs Decision to Needs More Information

Bump.

Garrett, I notice there’s a request for more information in this ticket.

#6 Updated by Garrett Honeycutt over 3 years ago

Nigel,

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.

#7 Updated by Nigel Kersten over 3 years ago

I’m not quite convinced.

How many different CAs are you deploying that you want to automate license file installation on?

Do you really want to distribute the license file to all nodes?

#8 Updated by Garrett Honeycutt over 3 years ago

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? :)

#9 Updated by Nigel Kersten over 3 years ago

We’re not. We’re justifying what’s actually valuable to work on.

#10 Updated by Garrett Honeycutt over 3 years ago

To put this in perspective, it is a feature that I would like to have, but lacking this feature is not a blocking function. Currently, I just wget the license key as part of the provisioning process.

#11 Updated by Nigel Kersten over 2 years 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 2 years 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.

#13 Updated by Nigel Kersten over 2 years ago

So you’ve done lots of these yourself? I’m looking for a sense of how much this is actually affecting real world deployments.

#14 Updated by Nigel Kersten about 2 years ago

  • Assignee changed from Nigel Kersten to Garrett Honeycutt

Also available in: Atom PDF