I can think of 2 ways of doing this, none of which are terribly nice:
1) use a separate Environment with the new version of the module, and start
running nodes against that. Once you get them all moved over to the new
environment, roll out the new module version to the production environment,
and s
Hi Abbas,
I am wondering if you have found a solution for the requirement yet and if
so, could you please share it.
On Friday, March 8, 2013 9:43:24 AM UTC+11, Mohamed Abbas wrote:
>
> On 3/7/13 1:51 PM, Nan Liu wrote:
>
> On Thu, Mar 7, 2013 at 12:42 PM, Mohamed Abbas
>
> > wrote:
>
>>
On Thu, Mar 7, 2013 at 2:43 PM, Mohamed Abbas wrote:
> On 3/7/13 1:51 PM, Nan Liu wrote:
>
> On Thu, Mar 7, 2013 at 12:42 PM, Mohamed Abbas wrote:
>
>> I'm wondering what is the canonical way of associating "specific"
>> versions of a module to a node? Is there a way of doing this in puppet? Let
On 3/7/13 1:51 PM, Nan Liu wrote:
On Thu, Mar 7, 2013 at 12:42 PM, Mohamed Abbas
mailto:m.magdi.ah...@gmail.com>> wrote:
I'm wondering what is the canonical way of associating "specific"
versions of a module to a node? Is there a way of doing this in
puppet? Let me explain a "Use Ca
On Thu, Mar 7, 2013 at 12:42 PM, Mohamed Abbas wrote:
> I'm wondering what is the canonical way of associating "specific" versions
> of a module to a node? Is there a way of doing this in puppet? Let me
> explain a "Use Case" of what I'm trying to accomplish:
>
> Say we have created a puppet model
Hello All,
I'm wondering what is the canonical way of associating "specific"
versions of a module to a node? Is there a way of doing this in puppet?
Let me explain a "Use Case" of what I'm trying to accomplish:
Say we have created a puppet model called apache to manage and configure
apache w
