similar to: Take out hosts from load balancer while deploying with Puppet

Hi, following this<https://puppetlabs.com/blog/managing-f5-big-ip-network-devices-with-puppet/>tutorial, I finally made it till the part where I see the SSL cert request from my f5 load balancer. Then I signed it and configured in nodes.pp the same pool and irule as suggested in the tutorial. BUT when I run on the proxy: # puppet device --deviceconf

Hello, when I run on my proxy server: # puppet device --debug --deviceconf /etc/puppet/device/F5-lb-test.conf I get this error: info: starting applying configuration to F5-lb-test at https://operating:operating4lbtest@F5-lb-test/Common debug: Puppet::Device::F5: connecting to F5 device F5-lb-test. debug: Puppet::Device::F5: connecting to partition Common. *err: Can''t load f5 for

Is there any documentation on doing the ssl termination on the F5? The only thing I found is http://projects.puppetlabs.com/projects/puppet/wiki/Load_Balancing_F5 which is only providing the iRule and not suggested configurations or starting points? I currently use an F5 to load balance my puppet masters but its just a pass through and I was wondering if cookie persistence would be useful in

How can I configure F5 load balancer to be infront of multiple puppet masters? The SSL will break as the server name if different, hostname of the VIP on the LB vs hostnames of each masters, right? Can you shed some light? Thanks. -- Hai Tao -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

>>>>> "Kishore" == Kishore Potnuru <kishore.reachme at gmail.com> writes: Kishore> I have the dovecot version 2.0.9 installed on RHEL linux 6.10 Kishore> version. It's a single/standalone Live server.? You should really upgradr your setup. Kishore> Now I have created another server with the same configuration Kishore> for the resilince purpose. I

Hi John, Thank you for the reply. Actually it was setup like this by another member, who left the team/company recently. Now it came to me to handle that responsibility. That's how I got in to this. At present I am not able to migrate/upgrade immediately. Because it sends emails around 100K+ emails everyday and I do not want to disturb that. Coming back to your question, Actually the

Hi All, I need your help on one of the issue in Dovecot. I have the dovecot version 2.0.9 installed on RHEL linux 6.10 version. It's a single/standalone Live server. Now I have created another server with the same configuration for the resilince purpose. I also tested and I am able to send the emails to both of the dovecot servers separately/individually. They are working fine. Now I have

Hi All, I need your help on one of the issue in Dovecot. I have the dovecot version 2.0.9 installed on RHEL linux 6.10 version. It's a single/standalone Live server. Now I have created another server with the same configuration for the resilince purpose. I also tested and I am able to send the emails to both of the dovecot servers separately/individually. They are working fine. Now I have

Has anyone successfully puppetized BigIP (F5)? I''m specifically trying to figure out a path in making our BigIP instances be under puppet so all the VIPs, pools, profiles, etc. are all under puppet control. My requirements are probably going to be fulfilled even with just uploading a rules file if a delta''s detected. The main issue I have now is figuring out when to reload the

Hi Team, Tried following the steps here http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows for deploying an agent on windows (windows server 2008 r2) but really finding it hard to make it work (the agent deployment itself went fine after following the steps). I have a working puppet-server on RH 6 and have tested few RH clients which work fine. The very first hurdle is that i

I''m happy to announce the release of version 2.0 of the Puppet Labs OpenStack modules to the Puppet Forge. These modules handle the deployment and management of the latest Grizzly releases of OpenStack, including Keystone, Swift, Glance, Cinder, Nova, and Horizon. Additionally, an OpenStack module is provided for single or multi-node deployments. Here is a set of links to the Forge

All, There are now development package repos located at yum.puppetlabs.com and apt.puppetlabs.com. Moving forward, these repos will contain Release Candidate packages of Puppet, Facter, Puppet Dashboard, MCollective and Hiera, including the soon to be released RCs of Puppet 3.0 and its dependencies, Facter 2.0 and Hiera 1.0. Packages are available to easily add these repos to yum and apt

I have installed puppet from puppet-labs yum repository on OEL familiy of Red Hat Enterprise Linux Server release 5.9 (Tikanga) ---------------------------------------------------------------------------- [root@oel-puppet-master modules]# yum list facter Loaded plugins: rhnplugin, security This system is not registered with ULN. You can use up2date --register to register. ULN support will be

Hi, I would like to set up an additional puppet master but have the CA server handled by only 1 puppet master. I have set this up as per the documentation here: http://docs.puppetlabs.com/guides/scaling_multiple_masters.html I have configured my second puppet master as follows: [main] ... ca = false ca_server = puppet-master1.test.net I am using passenger so I am a bit confused how the

Hi all It''s been a while since we introduced our professional services team to the community. They lurk on the list quite a bit and help answer questions and queries (their elite skills are also available for hire!). They are (in alphabetical order): Dan Bode (dan@puppetlabs.com) Hunter Haugen (hunter@puppetlabs.com) Cody Herriges (cody@puppetlabs.com) Garrett Honeycutt

Puppet 2.7.22 is now available. 2.7.22 addresses a security vulnerability discovered in the 2.7.x series of Puppet. This vulnerability has been assigned Mitre CVE number CVE-2013-3567. All users of Puppet 2.7.21 and earlier who cannot upgrade to the current version of Puppet, 3.2.2, are strongly encouraged to upgrade to 2.7.22. For more information on this vulnerability, please visit

Puppet 2.7.18 is a security release in the 2.7.x branch. The security changes in 2.7.18 address CVEs 2012-3864, 2012-3865, 2012-3866 and 2012-3867. All users of Puppet 2.7.x are encouraged to upgrade when possible to Puppet 2.7.18. More information available at http://puppetlabs.com/security or visit http://puppetlabs.com/security/cve/cve-2012-3864,

Team, I am trying to setup new Puppet master server on Centos 5.4. I am getting the below error which running yum install puppet-server puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems --> Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems --> Missing

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

Puppet Dashboard 1.2.23-rc3 is a maintenance release candidate of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23-rc3.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For