(#18285) Disable JMX network connector

We were previously exposing JMX information over the network, to no real
end. Nobody was using that feature, and in fact the feature causes
issues on Ubuntu where remote RMI listener threads bind to all
interfaces by default.

We already expose JMX information via REST, and if people want to get at
more detailed stuff they can always use JConsole or the like.

As a bonus, this should result in a few less active threads and a little
less memory used.

Signed-off-by: Deepak Giridharagopal <deepak@puppetlabs.com>
Update docs to mention how to setup remote JMX port

Signed-off-by: Deepak Giridharagopal <deepak@puppetlabs.com>
Add pe-puppetdb package building for acceptance

This adds another set of rpm package builds to the
acceptance rpm package build script for PE packages.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>

Conflicts:
	ext/test/build_packages_rpm.sh

Conflicts:
	ext/test/build_packages_rpm.sh
Put rpm build logic into functions

This commit wraps some of the various repeated rpm build tasks into
defined functions in the ssh call out to rpm-builder. This paves the
way for more easily adding another case for PE package building.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge pull request #389 from grimradical/disable-jmx-connector

(#18285) Disable JMX network connector
[packaging] Add wheezy to list of cows, remove lenny

We are now building PE packages for debian wheezy. This commit adds
it to the build targets for pe-puppetdb. This commit also removes
lenny, which we are no longer building packages for because it is
EOL.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
[packaging] Add cow update prior to pe deb build in Rakefile

Currently building debs for PE often fails the first time, because the cows in
use were previously used for FOSS products, and do not have the PE freight
repository enabled for dependency resolution. This has always been handled by
manually updating the cows, and then re-running the task. This begs the
question - why don't we automate that? This commit does so. It also allows the
arch on the cow build to be overridden with an environment variable, and
removes ENV['DIST'], which isn't really necessary since we explicitly set the
variable in the update call.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
[packaging] Correct tabbing in cow build call

Also replace 'i386' hardcoded with the correct variable
[packaging] Clear up @pe_version variable for PE deb building

We want to be able to override the default PE version we're building against
with an environment variable, and the current setup does not allow this (the
environment variable is always set to the hardcoded version). With this commit,
we use the ENV['PE_VER'] when available, otherwise default to 2.7. PE 2.7 is
the first version with wheezy PE packages built, thus it is the first one that
will be able to satisfy PE dependencies.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
[packaging] Remove override-configs from cow build call

This is now done in the update call, so we don't need to refresh the config
again with another override-config, and othermirror is now handled in the
pbuilderrc.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
[acceptance] Add Puppet Enterprise debs to automated packages

This commit updates the acceptance debian package build script to also build
debs for Puppet Enterprise. Since our current target is 2.7, that is the
default. We will likely want to pass this information in via jenkins jobs, so
that is enabled as an override.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>