The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Feature #17071

Document approaches to more scalable deployes

Added by R.I. Pienaar over 3 years ago. Updated over 2 years ago.

Status:InvestigatingStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Backlog
Target version:-
Keywords:backlog Affected mCollective version:
Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/MCO-58


Description

Currently the state of art regarding complex or large mcollective sites is just to mesh all the activemqs together. This does not work well and is not a good idea given the design of ActiveMQ clustering however it seems the obvious thing so everyone does it.

We need to test, document, benchmark etc a scalable mcollective deploy strategy based on ActiveMQ

History

#1 Updated by eric sorenson over 3 years ago

  • Keywords set to backlog

#2 Updated by Pieter Loubser over 2 years ago

  • Status changed from Unreviewed to Investigating

Also available in: Atom PDF