At $WORK we currently use HP Operations Manager (aka ITO aka OVO aka OML...) to monitor our infrastructure. Because adding new nodes and configuring them can be time consuming and painful I''d like to know: Is anyone using the same product and how much / what exactly do you do with puppet? We currently install the agent software on Linux and Unix with puppet off an NFS share using an exec resource. This tends to be a lot more stable than doing the remote installation the product itself offers. Puppet can now also do the patching of the agents. I also started to write some custom types which will hopefully automate things a bit more. If you want to try them they are available here: https://github.com/stschulte/puppet-hpom So are you using HP OM and what does puppet do in that area? -Stefan
Hi Stefan, I know it''s an old post, but I''ll be happy to hear more about how you''re doing the agent installations with puppet, and maybe even get some code from you if it''s possible. :) Is there an option to contact you? On Monday, November 21, 2011 8:21:33 PM UTC+2, Stefan Schulte wrote:> > At $WORK we currently use HP Operations Manager (aka ITO aka OVO aka > OML...) to monitor our infrastructure. > > Because adding new nodes and configuring them can be time consuming and > painful I''d like to know: Is anyone using the same product and how much > / what exactly do you do with puppet? > > We currently install the agent software on Linux and Unix with puppet off > an NFS share using an exec resource. This tends to be a lot more stable > than doing the remote installation the product itself offers. Puppet can > now also do the patching of the agents. I also started to write some custom > types which will hopefully automate things a bit more. > > If you want to try them they are available here: > https://github.com/stschulte/puppet-hpom > > So are you using HP OM and what does puppet do in that area? > > -Stefan > >-- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you. -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Thu, 4 Apr 2013 02:29:51 -0700 (PDT) roeez@liveperson.com wrote:> Hi Stefan, > I know it''s an old post, but I''ll be happy to hear more about how > you''re doing the agent installations with puppet, and maybe even get > some code from you if it''s possible. :) > Is there an option to contact you? >You can contact me by mail or just replying on this list. The repository https://github.com/stschulte/puppet-hpom is still up if you are interested in custom types. I''m happy to merge in pull request, too. About the installation itself: I do not have the code around right now but I install the agent with an exec resource from a NAS share (something along oainstall.sh -i -a -includeupdates -defer_configure). The same is true for configuration (oainstall.sh -c -a -s $server) and activation (If you have a lot of updates and hotfixes, doing the installation and configuration in seperate steps will be a *a lot* faster) I also have an if clause to check the custom fact opcagtversion against the desired version (with the versioncmp function) and trigger another exec to update the agent if necessary. If you want a more concrete example I''ll check the module at work and will see what I can actually make public. -Stefan -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Thanks for all the information Stefan! I''d be happy to see the module you''re using if it''s possible. Roee. On Sunday, April 7, 2013 1:02:32 AM UTC+3, Stefan Schulte wrote:> > On Thu, 4 Apr 2013 02:29:51 -0700 (PDT) > ro...@liveperson.com <javascript:> wrote: > > > Hi Stefan, > > I know it''s an old post, but I''ll be happy to hear more about how > > you''re doing the agent installations with puppet, and maybe even get > > some code from you if it''s possible. :) > > Is there an option to contact you? > > > > You can contact me by mail or just replying on this list. The > repository https://github.com/stschulte/puppet-hpom is still up if you > are interested in custom types. I''m happy to merge in pull request, too. > > About the installation itself: > > I do not have the code around right now but I install the agent with an > exec resource from a NAS share (something along oainstall.sh -i -a > -includeupdates -defer_configure). The same is true for configuration > (oainstall.sh -c -a -s $server) and activation (If you have a lot of > updates and hotfixes, doing the installation and configuration in > seperate steps will be a *a lot* faster) > > I also have an if clause to check the custom fact opcagtversion against > the desired version (with the versioncmp function) and trigger another > exec to update the agent if necessary. > > If you want a more concrete example I''ll check the module at > work and will see what I can actually make public. > > -Stefan >-- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you. -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Sun, 7 Apr 2013 02:16:07 -0700 (PDT) roeez@liveperson.com wrote:> Thanks for all the information Stefan! > I''d be happy to see the module you''re using if it''s possible. > > Roee. >Ok so I have a hpoml::client class to include at node level. It basically consists of a hpoml::user class where I define the `opc_op` User and the `opcgrp` group (to have consistent uid and gid across machines) and the class hpoml::client::package. I guess I can share that one: class hpoml::client::package ($server = ''your_master_server'', $minversion = ''11.11.025'') { if ! ($::operatingsystem in [ ''Solaris'', ''RedHat'' ]) { fail "operatingsystem ${::operatingsystem} is currently not supported. Must be one of Solaris, RedHat" } $installer = ''/some/nas/share/Agt_11.11.x/oainstall.sh'' $install_arguments = ''-install -agent -includeupdates -defer_configure'' $update_arguments = ''-install -agent -includeupdates'' exec { ''Install_OML'': command => "${installer} ${install_arguments}", creates => [ ''/opt/OV/bin/ovc'', ''/opt/OV/bin/ovconfget'', ], timeout => ''1800'', # 30 minutes } exec { ''Configure_OML'': command => ''/opt/OV/bin/OpC/install/oainstall.sh -configure -agent'', creates => [ ''/var/opt/OV/installation/inventory/HPOvAgtLc.xml'', ''/var/opt/OV/installation/inventory/HPOvBbc.xml'', ''/var/opt/OV/installation/inventory/HPOvConf.xml'', ''/var/opt/OV/installation/inventory/HPOvCtrl.xml'', ''/var/opt/OV/installation/inventory/HPOvDepl.xml'', ''/var/opt/OV/installation/inventory/HPOvEaAgt.xml'', ''/var/opt/OV/installation/inventory/HPOvGlanc.xml'', ''/var/opt/OV/installation/inventory/HPOvPacc.xml'', ''/var/opt/OV/installation/inventory/HPOvPerfAgt.xml'', ''/var/opt/OV/installation/inventory/HPOvPerfMI.xml'', ''/var/opt/OV/installation/inventory/HPOvPerlA.xml'', ''/var/opt/OV/installation/inventory/HPOvSecCC.xml'', ''/var/opt/OV/installation/inventory/HPOvSecCo.xml'', ''/var/opt/OV/installation/inventory/HPOvXpl.xml'', ''/var/opt/OV/installation/inventory/Operations-agent.xml'', ], require => Exec[''Install_OML''], } exec { ''Activate_OML'': command => "/opt/OV/bin/OpC/install/opcactivate -srv ${server} -cert_srv ${server}", unless => "/opt/OV/bin/ovconfget sec.core.auth MANAGER | /bin/grep ${server}", require => Exec[''Configure_OML''], } # only patch if ovo is already installed and if the current version # is below the minversion. We do not downgrade. if $::opcagtversion and versioncmp($::opcagtversion, $minversion) < 0 { exec { ''Patch_OML'': command => "${installer} ${update_arguments}", timeout => ''1800'', # 30 minutes require => Exec[''Install_OML''], } } } works pretty well. If we get a new version I try the installer by hand a couple of times (the class does not downgrade, only upgrade). If it does not fail I bump the $minversion default parameter and puppet will patch all my systems. -Stefan -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Many thanks Stefan! On Monday, April 8, 2013 7:46:53 PM UTC+3, Stefan Schulte wrote:> > On Sun, 7 Apr 2013 02:16:07 -0700 (PDT) > ro...@liveperson.com <javascript:> wrote: > > > Thanks for all the information Stefan! > > I''d be happy to see the module you''re using if it''s possible. > > > > Roee. > > > > Ok so I have a hpoml::client class to include at node level. It > basically consists of a hpoml::user class where I define the `opc_op` > User and the `opcgrp` group (to have consistent uid and gid across > machines) and the class hpoml::client::package. I guess I can share > that one: > > class hpoml::client::package ($server = ''your_master_server'', $minversion > = ''11.11.025'') { > > if ! ($::operatingsystem in [ ''Solaris'', ''RedHat'' ]) { > fail "operatingsystem ${::operatingsystem} is currently not supported. > Must be one of Solaris, RedHat" > } > > $installer = ''/some/nas/share/Agt_11.11.x/oainstall.sh'' > $install_arguments = ''-install -agent -includeupdates -defer_configure'' > $update_arguments = ''-install -agent -includeupdates'' > > exec { ''Install_OML'': > command => "${installer} ${install_arguments}", > creates => [ > ''/opt/OV/bin/ovc'', > ''/opt/OV/bin/ovconfget'', > ], > timeout => ''1800'', # 30 minutes > } > > exec { ''Configure_OML'': > command => ''/opt/OV/bin/OpC/install/oainstall.sh -configure -agent'', > creates => [ > ''/var/opt/OV/installation/inventory/HPOvAgtLc.xml'', > ''/var/opt/OV/installation/inventory/HPOvBbc.xml'', > ''/var/opt/OV/installation/inventory/HPOvConf.xml'', > ''/var/opt/OV/installation/inventory/HPOvCtrl.xml'', > ''/var/opt/OV/installation/inventory/HPOvDepl.xml'', > ''/var/opt/OV/installation/inventory/HPOvEaAgt.xml'', > ''/var/opt/OV/installation/inventory/HPOvGlanc.xml'', > ''/var/opt/OV/installation/inventory/HPOvPacc.xml'', > ''/var/opt/OV/installation/inventory/HPOvPerfAgt.xml'', > ''/var/opt/OV/installation/inventory/HPOvPerfMI.xml'', > ''/var/opt/OV/installation/inventory/HPOvPerlA.xml'', > ''/var/opt/OV/installation/inventory/HPOvSecCC.xml'', > ''/var/opt/OV/installation/inventory/HPOvSecCo.xml'', > ''/var/opt/OV/installation/inventory/HPOvXpl.xml'', > ''/var/opt/OV/installation/inventory/Operations-agent.xml'', > ], > require => Exec[''Install_OML''], > } > > exec { ''Activate_OML'': > command => "/opt/OV/bin/OpC/install/opcactivate -srv ${server} > -cert_srv ${server}", > unless => "/opt/OV/bin/ovconfget sec.core.auth MANAGER | /bin/grep > ${server}", > require => Exec[''Configure_OML''], > } > > # only patch if ovo is already installed and if the current version > # is below the minversion. We do not downgrade. > if $::opcagtversion and versioncmp($::opcagtversion, $minversion) < 0 { > exec { ''Patch_OML'': > command => "${installer} ${update_arguments}", > timeout => ''1800'', # 30 minutes > require => Exec[''Install_OML''], > } > } > } > > works pretty well. If we get a new version I try the installer by hand > a couple of times (the class does not downgrade, only upgrade). If it > does not fail I bump the $minversion default parameter and puppet will > patch all my systems. > > -Stefan >-- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you. -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.