[chef] RE: Re: Notifications almost but not quite :immediate ?


Chronological Thread 
  • From: Kevin Keane Subscription < >
  • To: < >
  • Subject: [chef] RE: Re: Notifications almost but not quite :immediate ?
  • Date: Mon, 23 Sep 2013 07:22:04 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=sendgrid.info; h=subject :from:to:mime-version:content-type:in-reply-to:references :sender; q=dns; s=smtpapi; b=tM3sm2c+O2BSYwaN7scG2AIED3T09bkWNqv G4lNXXQUac0VraOAgIhBcyi5mKbrUzsfOeIOhbSmoTxPNQOwjPKsYKL+2OiNrQ6a pt6c3LM4t1LnY7VY+0SyiYA6Dd1j9xrXyirOKrHgyk2uLBUzZSwJbyA1g5uZDMlu pp7bIlJQ=

Title: RE: [chef] Re: Notifications almost but not quite :immediate ?

Yes, I'm actually using the Yum cookbook.

Kevin Keane

The NetTech

760-721-8339

http://www.4nettech.com

Our values: Privacy, Liberty, Justice

See https://www.4nettech.com/corp/the-nettech-values.html


-----Original message-----
From: John Dewey < >
Sent: Sunday 22nd September 2013 9:27
To:
Subject: [chef] Re: Notifications almost but not quite :immediate ?

Have you tried adding repos using the yum cookbook?  This should take care of what you need.

https://github.com/opscode-cookbooks/yum

John

On Sunday, September 22, 2013 at 9:22 AM, Kevin Keane Subscription wrote:

I'm wondering if there is a way to get notifications to be delayed slightly, without having to wait for the end of the run?

Here is the scenario: I add several Yum repositories using a recipe. After the repositories are added, I need to rebuild the Yum cache.

I have two options to do that:

- Send a delayed notification - but then other recipes don't get the benefit of the new repositories until the next run, and thus may break.

- Send an immediate notification - but then the cache gets rebuilt multiple times. Rebuilding the Yum cache is very expensive in terms of time and bandwidth, so I want to avoid that.

Is there a trick I can use to only cause one notification to be sent after all of the repositories have been added?

Thanks!







Archive powered by MHonArc 2.6.16.

§