As promised, here is my final solution:
Three variables (because this is inside a defined type) :
$service _name like "mysql"
$interface_name like "eth0 or eth0:1"
$ip like "192.168.123.100"
--------------
file { "/etc/sysconfig/network-scripts/ifcfg-${interface_name}" :
# stuff
}
exec { "network_interface_${service_name}" :
command => "/sbin/ifup ${interface_name}",
subscribe => File["/etc/sysconfig/network-scripts/ifcfg-${interface_name}"],
notify => Service[$service_name],
onlyif => "/usr/bin/test `/sbin/ip addr show | /bin/grep ${interface_name} |
/bin/grep ${ip} | /usr/bin/wc -l` -eq 0"
}
service { $service_name:
ensure => $service_ensure,
enable => $service_enable,
require => [
Package[ ...],
Package[...],
],
}
I needed to replace the refreshonly parameter with the onlyif command because
it was running ifup every time.
The double-grep is to tell eth0 from eth0:1
It works when the interface is down and it does nothing if the interface is up
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)
On Jan 31, 2015, at 09:00 PM, Dan White <d_e_wh...@icloud.com> wrote:
Thanks.
I will report back with my results - good or bad
On Jan 31, 2015, at 8:54 PM, Christopher Wood <christopher_w...@pobox.com>
wrote:
The service wouldn't start before the exec due to the notify there. The exec
resource will be managed before the service resource. (I don't think it would
mess anything up but I haven't tried adding multiple relationship
metaparameters recently.)
https://docs.puppetlabs.com/puppet/latest/reference/lang_relationships.html#ordering-and-notification
https://docs.puppetlabs.com/references/latest/metaparameter.html#notify
On Sat, Jan 31, 2015 at 11:59:01AM -0500, Dan White wrote:
Another thought :
Unless I chain them together…
file{} -> exec{} -> service{}
what would keep the service from trying to start before the exec has run ?
Would adding “ require => Exec['/sbin/ifup eth0’], “ to the service
resource mess things up ?
On Jan 30, 2015, at 4:18 PM, Dan White <[1]d_e_wh...@icloud.com> wrote:
Thanks.
I was not trying it that way, but I believe I will. I see where my
approach was borked.
Unfortunately, it means some non-trivial refactoring.
But (and thanks a second time for an opportunity to use this line)
"It's like the chicken said, Launchpad, 'You knew the job was dangerous
when you took it' ! "
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)
On Jan 30, 2015, at 03:37 PM, Christopher Wood
<[2]christopher_w...@pobox.com> wrote:
Possibly something like this? If you've already tried this, what was
the result?
file { '/etc/sysconfig/network-scripts/ifcfg-eth0':
# stuff here
}
exec { '/sbin/ifup eth0':
refreshonly => true,
subscribe => File['/etc/sysconfig/network-scripts/ifcfg-eth0'],
notify => Service['mysql'],
}
service { 'mysql':
# stuff
}
(Store the ip information in hiera and template your mysql.cnf as well
as ifcfg-eth0 with the same data.)
On Fri, Jan 30, 2015 at 07:40:38PM +0000, Dan White wrote:
Red Hat / CentOS 6.x with Puppet 3.7.x
Creating a new network interface is easy:
Create the /etc/sysconfig/network-scripts/ifcfg-eth(whatever) file
and then refresh the network service.
Now the problem: If I want to run something off that new interface
-- like a MySQL server -- how do I express the dependency to get the
interface running before trying to start the service to run on it ?
I have been unsuccessful in making it happen in a single puppet
run.
“Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
--
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 [3]puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[4]https://groups.google.com/d/msgid/puppet-users/BDCDE71E-6838-4EA7-85BB-83BAC8E5B4D9%40icloud.com.
For more options, visit [5]https://groups.google.com/d/optout.
References
Visible links
1. mailto:d_e_wh...@icloud.com
2. mailto:christopher_w...@pobox.com
3. mailto:puppet-users+unsubscr...@googlegroups.com
4. https://groups.google.com/d/msgid/puppet-users/BDCDE71E-6838-4EA7-85BB-83BAC8E5B4D9%40icloud.com?utm_medium=email&utm_source=footer
5. https://groups.google.com/d/optout
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/20150201015457.GA24696%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/DF30B747-C1F7-4743-877A-03A0AD0AF24F%40icloud.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/2b734310-8258-48e5-afdc-85294d206df9%40me.com.
For more options, visit https://groups.google.com/d/optout.
