Missing node_aws sub-command in puppet using Puppet Enterprise 2015.3.1-el-7-x86_64

60 views
Skip to first unread message

Deepak Agarwal

unread,
Jan 7, 2016, 9:35:59 AM1/7/16
to Puppet Users
Hello,

The node_aws cloud provisioning sub-command is missing in puppet.


I have installed Puppet Enterprise 2015.3.1-el-7-x86_64 (TRAIL version tar) with q_puppet_cloud_install='y'

The OS is 64 bit CentOS 7. The SELinux is disabled

I have searched a lot and Puppet Enterprise is expected to have cloud_provisioning inbuilt with q_puppet_cloud_install='y'.
But I am not seeing node_aws in my setup.


Please suggest what is missing and why puppet enterprise is not having node_aws on CentOS 7?

---------------------------------------------------------------------------------------------------------

$ puppet help | grep node
  node              View and manage node definitions.
  resource_type     View classes, defined resource types, and nodes from all manifests.


--------------------------------------------------------------------------------------------------------------

$ puppet help node_aws
Error: Could not load help for the face node_aws.
Please check the error logs for more information.

Detail: "Could not find Puppet Face node_aws"

Error: Try 'puppet help help help' for usage


--------------------------------------------------------------------------------------------------------------

answer file:
q_activity_database_name='pe-activity'
q_activity_database_password='cisco123'
q_activity_database_user='pe-activity'
q_all_in_one_install='y'
q_classifier_database_name='pe-classifier'
q_classifier_database_password='cisco123'
q_classifier_database_user='pe-classifier'
q_database_install='y'
q_database_port='5432'
q_database_root_password='cisco123'
q_database_root_user='root'
q_fail_on_unsuccessful_master_lookup='y'
q_install='y'
q_orchestrator_database_name='pe-orchestrator'
q_orchestrator_database_password='cisco123'
q_orchestrator_database_user='pe-orchestrator'
q_pe_check_for_updates='y'
q_pe_database='y'
q_puppet_cloud_install='y'
q_puppet_enterpriseconsole_auth_password='cisco123'
q_puppet_enterpriseconsole_httpd_port='443'
q_puppet_enterpriseconsole_install='y'
q_puppet_enterpriseconsole_master_hostname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
q_puppetagent_install='y'
q_puppetdb_database_name='pe-puppetdb'
q_puppetdb_database_password='cisco123'
q_puppetdb_database_user='pe-puppetdb'
q_puppetdb_install='y'
q_puppetdb_plaintext_port='8080'
q_puppetdb_port='8081'
q_puppetmaster_dnsaltnames='ip-172-31-14-31,ip-172-31-14-31.us-west-2.compute.internal,puppet,puppet.us-west-2.compute.internal'
q_puppetmaster_enterpriseconsole_hostname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
q_puppetmaster_enterpriseconsole_port='443'
q_puppetmaster_install='y'
q_rbac_database_name='pe-rbac'
q_rbac_database_password='cisco123'
q_rbac_database_user='pe-rbac'
q_skip_backup='y'
q_skip_master_verification='n'
q_use_application_services='y'
q_vendor_packages_install='y'

Thanks,
Deepak

Lindsey Smith

unread,
Jan 7, 2016, 1:21:44 PM1/7/16
to puppet...@googlegroups.com
On Thu, Jan 7, 2016 at 6:30 AM, Deepak Agarwal <deepak....@gmail.com> wrote:
Hello,

The node_aws cloud provisioning sub-command is missing in puppet.


I have installed Puppet Enterprise 2015.3.1-el-7-x86_64 (TRAIL version tar) with q_puppet_cloud_install='y'

The OS is 64 bit CentOS 7. The SELinux is disabled

I have searched a lot and Puppet Enterprise is expected to have cloud_provisioning inbuilt with q_puppet_cloud_install='y'.
But I am not seeing node_aws in my setup.


Please suggest what is missing and why puppet enterprise is not having node_aws on CentOS 7?

Hi Deepak. Cloud Provisioner was deprecated in the PE 3.8 release and removed in the PE 2015.2 release as noted here http://docs.puppetlabs.com/pe/3.8/cloudprovisioner_overview.html

As a replacement, we recommend using the puppetlabs/aws module instead. See https://puppetlabs.com/blog/puppet-aws-module-now-supported-puppet-enterprise for an introduction.

 

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bc409262-0ba1-4e56-aa19-c8f1e8f81d2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Deepak Agarwal

unread,
Jan 8, 2016, 5:44:48 AM1/8/16
to Puppet Users
I have installed puppetlabs-aws as steps given in github below.


The puppet aws module is installed at below path:

$ pwd
/home/centos/.puppet/modules/aws

$ ls
bin           checksums.json  CONTRIBUTING.md  fixtures  Guardfile  LICENSE        Rakefile   spec
CHANGELOG.md  contrib         examples         Gemfile   lib        metadata.json  README.md  tests



But puppet subcommand node_aws is still missing ....
Is there any PATH environment variable needs to be setup to get node_aws in puppet sub-command?

$ puppet help | grep node
  node              View and manage node definitions.
  resource_type     View classes, defined resource types, and nodes from all manifests.

Thanks,
Deepak

Lindsey Smith

unread,
Jan 11, 2016, 3:03:37 PM1/11/16
to puppet...@googlegroups.com
On Thu, Jan 7, 2016 at 11:06 PM, Deepak Agarwal <deepak....@gmail.com> wrote:
I have installed puppetlabs-aws as steps given in github below.


The puppet aws module is installed at below path:

$ pwd
/home/centos/.puppet/modules/aws

$ ls
bin           checksums.json  CONTRIBUTING.md  fixtures  Guardfile  LICENSE        Rakefile   spec
CHANGELOG.md  contrib         examples         Gemfile   lib        metadata.json  README.md  tests



But puppet subcommand node_aws is still missing ....

That's expected as the way of interacting with AWS has changed. The AWS module provides for Puppet DSL-style creation of infrastructure rather than a command-line driven "puppet node" operation. See https://github.com/puppetlabs/puppetlabs-aws#getting-started-with-aws for an example.
 
Reply all
Reply to author
Forward
0 new messages