What is the rationale of replacing cobbler, what are the scalability issues with cobbler?

Asked by Alexander List

Cobbler is a well-established provisioning tool in the RPM world.


MAAS used cobbler relabeled as maas-provision to provide provisioning services for Ubuntu environments.

There is a blueprint that describes scalability issues with cobbler, proposing to drop cobbler.


What is the rationale behind replacing cobbler with something home-written, given the established code base and user base of a well established tool?

What exactly are the scalability issues observed with cobbler?

Was fixing these scalability issues considered as an alternative to dropping cobbler and reinventing the wheel?

The full spec is only available as a protected Google document.

Question information

English Edit question
Ubuntu cobbler Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Warren Hill (warren-hill) said :

Have you considered contacting Julian Edwards


he Drafted and Approved the blueprint.

Can you help with this problem?

Provide an answer of your own, or ask Alexander List for more information if necessary.

To post a message you must log in.