On Wednesday, April 25, 2018 at 6:22:39 AM UTC-5, Thomas Müller wrote:
>
>
>
>>
>>>
>>> Another usecase could be to have a async puppetdb connection from the
>>> second datacenter. If the connection between the datacenters is not stable
>>> enough to use a single puppetdb I would need to
>
>
>>
>> Another usecase could be to have a async puppetdb connection from the
>> second datacenter. If the connection between the datacenters is not stable
>> enough to use a single puppetdb I would need to add a puppetdb per DC.Then
>> I also would want to sync data to the central
On 4/19/18 4:46 AM, Thomas Müller wrote:
HI
I've got some prod puppetserver/puppetdb and some dev
puppetserver/puppetdb. But to have the complete overview over all
nodes with the prod puppetdb I'd like to import the reports from the
dev puppetserver (stored by reports=store config) into the
On Thursday, April 19, 2018 at 2:30:11 PM UTC-5, Thomas Müller wrote:
>
>
>
> Am Donnerstag, 19. April 2018 19:18:34 UTC+2 schrieb Christopher Wood:
>>
>> To challenge an assumption, what are you gaining from having more than
>> one puppet infrastructure (puppetservers+puppetdb)?
>>
>> Could
Am Donnerstag, 19. April 2018 19:18:34 UTC+2 schrieb Christopher Wood:
>
> To challenge an assumption, what are you gaining from having more than one
> puppet infrastructure (puppetservers+puppetdb)?
>
> Could you perhaps handle your dev stuff with another environment or set of
>
To challenge an assumption, what are you gaining from having more than one
puppet infrastructure (puppetservers+puppetdb)?
Could you perhaps handle your dev stuff with another environment or set of
puppetservers under the same CA with the same puppetdb?
Is there any reason for a separate
HI
I've got some prod puppetserver/puppetdb and some dev
puppetserver/puppetdb. But to have the complete overview over all nodes
with the prod puppetdb I'd like to import the reports from the dev
puppetserver (stored by reports=store config) into the prod puppetdb.
is there some hidden tool
