Service Profiles and Templates

When starting with profiles and templates, it is important to understand the differences between those.
In short, the difference between a Profile and a Template is that a Template describes it globally (as example, get mac address from a pool), the profile makes every part specific for that profile. (as example, get unique mac address from a pool). A Profile is associated with equipment, a physical server.
A template can be associated with a Profile, changes to a Template can update all Profiles that are linked to that Template. This is called an Updating Template.

Service Profile Templates:

Service Profile Templates describes the configuration of a Profile.
For example, it describes how many nics there are, what settings they have and what firmware it use.
You can specify what pools they get MAC or WWPN addresses, but don’t bind them on the nics.
Another nice feauture is that you can clone them. For example, you can create a Service Profile Template for a Server with all your settings, policies, pools, vNIC’s and vHBA’s. Then clone the template to one or more Service Profiles. Each Service Profile gets its own UUID, MAC Addresses and IP Addres(ses) from the pools you created earlier. Once they are cloned, you can associate each Service Profile to servers. This will make sure the configuration on your servers are consistent.

Service Profile:

Service Profiles can be created with a Wizard or manual and are based on a Template.
During the Service Profile wizard you can choose what to do.
A Service Profile is full of options and features. It configures your server the way you want, with the firmware, BIOS settings and type of nics you want.
And the way you configure it makes sense. Just think how a normal physical server looks like.
If you need more nics, add nics, if you need to change the boot order, change it.




View all posts by