There is no limit to
the number of global
that you can attach to a global service template.
to make widespread changes is beneficial for simplified management, but it is
not best for all environments. Consider the ramifications of a single
disruptive change to the environment. Determine how many resources you can
safely attach to an updating global
template. One mistake could cause a significant outage. Consider reducing the
potential for damage. For example, you could decide that a ratio of 100 global
attached to each
template is the maximum limit.
consideration is the number of
For example, if you have ten global
templates, with 100 global service profiles attached, that represents 1,000
blades or servers. If you had all ten templates accessing the same disruptive
policies, you could have a single policy that could potentially disrupt 1,000
blades or servers. To reduce the possibilities for failure, it is best to scale
templates, and multiple policies. It is acceptable to have more than one policy
that contains the same settings, but is used by different templates.
If you have too many
attached to too few templates, you can clone the global
template. Then unbind some of the profiles from the original template and bind
them to the clone. The system is flexible in design and operations. You can
balance and scale accordingly.
testing this scenario before deploying it in a production environment.
Although this guide
discusses reducing the number of global
for ease of management, do not attach too many global
to a template. Also, do not use a single policy for too many global
and profiles. This sounds contradictory; however, consider balancing reduction
of templates for improved OPEX, with the widespread damage that could be caused
by having too many service profiles accessing a template, or policy.