344 lines
17 KiB
XML
344 lines
17 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<profiles xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="profileSchema.xsd">
|
|
<!--This is a typical 2 processors by 10 physical cores compute node
|
|
Taken from HP380 -->
|
|
<cpuProfile name="cpu-2x10">
|
|
<processor>
|
|
<!--number of processors on the server-->
|
|
<numberOfProcessor>2</numberOfProcessor>
|
|
<!--number of physical cores in each processor.
|
|
Specify number of the physical cores here.
|
|
To see logical core mapping, turn on the hyper-threading below-->
|
|
<coresPerProcessor>10</coresPerProcessor>
|
|
<!--use optional hyperThreading to enable hyper-thread to the -->
|
|
<!--profile. Enabling hyper-threading will make the profile looks-->
|
|
<!--like what it is as if the host has it hyper-threading enabled. -->
|
|
<hyperThreading>false</hyperThreading>
|
|
</processor>
|
|
|
|
<!--platformCores section defines physical cores assign to platform functions on each processor -->
|
|
<platformCores>
|
|
<!--Each processor tag defines number of physical cores to be assigned to platform function on
|
|
a processor indicated by the index.
|
|
processor index starts from 0 to numberOfProcessor -1.
|
|
Each processor (indicated by index) should only appear once-->
|
|
<processor index="0" numberOfCores="1"></processor>
|
|
</platformCores>
|
|
|
|
<!--vswitchCores section defines physical cores assign to vswitch functions on each processor
|
|
This setting only apply to the compute nodes. -->
|
|
<vswitchCores>
|
|
<!--Each processor tag defines number of physical cores to be assigned to vswitch function on
|
|
a processor indicated by the index.
|
|
processor index starts from 0 to numberOfProcessor -1.
|
|
Each processor (indicated by index) should only appear once-->
|
|
<processor index="0" numberOfCores="2"></processor>
|
|
</vswitchCores>
|
|
|
|
<!--remaining cores on each processor are assigned to guest VMs-->
|
|
</cpuProfile>
|
|
|
|
<!--this setup is taken from HP380 -->
|
|
<memoryProfile name="mem-profile">
|
|
<!--number of CPUs on the motherboard-->
|
|
<numberOfProcessor>2</numberOfProcessor>
|
|
|
|
<!--platformReservedMiB section defines the memory to be reserved for platform functions-->
|
|
<platformReservedMiB>
|
|
<!--Each processor tag defines number of physical cores to be assigned to vswitch function on
|
|
a processor indicated by the index.
|
|
processor index starts from 0 to numberOfProcessor -1.
|
|
Each processor (indicated by index) should only appear once.
|
|
The size is in MB-->
|
|
<processor index="0" size="4000"></processor>
|
|
<processor index="1" size="2000"></processor>
|
|
</platformReservedMiB>
|
|
|
|
<!--vmHugePages2M section defines number of 2M bytes huge page assigned to each processor-->
|
|
<vmHugePages2M>
|
|
<!--Each processor tag defines number of physical cores to be assigned to vswitch function on
|
|
a processor indicated by the index.
|
|
processor index starts from 0 to numberOfProcessor -1.
|
|
Each processor (indicated by index) should only appear once. -->
|
|
<processor index="0" size="29096"></processor>
|
|
<processor index="1" size="30129"></processor>
|
|
</vmHugePages2M>
|
|
|
|
<!--vmHugePages1G section defines number of 1G bytes huge page assigned to each processor-->
|
|
<vmHugePages1G>
|
|
<!--Each processor tag defines number of physical cores to be assigned to vswitch function on
|
|
a processor indicated by the index.
|
|
processor index starts from 0 to numberOfProcessor -1.
|
|
Each processor (indicated by index) should only appear once. -->
|
|
<processor index="0" size="0"></processor>
|
|
<processor index="1" size="0"></processor>
|
|
</vmHugePages1G>
|
|
</memoryProfile>
|
|
|
|
<!--This setup is taken from wildcat7_12-->
|
|
<storageProfile name="storage-profile">
|
|
<!--The disk tags below define each device,
|
|
path: device path
|
|
size: minimum size (in GiB)
|
|
volumeFunc: volume function to be assigned to the device
|
|
For 'osd' function:
|
|
journalSize: the size of the ceph journal in GiB, if absent defaults to journal_default_size in sysinv.conf
|
|
journalLocation: location of the journal partition, mandatory if multiple journal functions are defined,
|
|
if absent defaults to the single available journal drive.
|
|
If no device with journal function is configured then the journals for all OSDs will be collocated on the
|
|
same device with the OSD data (partition #1 is for the data and partition #2 for the journl).
|
|
In this case the size of the journal will be journal_default_size.-->
|
|
<disk path="/dev/sdb" size="223" volumeFunc="osd" journalSize="2" journalLocation="/dev/sdd" />
|
|
<disk path="/dev/sdc" size="223" volumeFunc="osd" journalLocation="/dev/sde" />
|
|
<disk path="/dev/sdd" size="223" volumeFunc="journal" />
|
|
<disk path="/dev/sde" size="223" volumeFunc="journal" />
|
|
</storageProfile>
|
|
|
|
<storageProfile name="storage-profile-coloc-no-tier">
|
|
<!--The disk tags below define each device,
|
|
path: device path
|
|
size: minimum size (in GiB)
|
|
volumeFunc: volume function to be assigned to the device
|
|
For 'osd' function:
|
|
journalSize: the size of the ceph journal in GiB, if absent defaults to journal_default_size in sysinv.conf
|
|
journalLocation: location of the journal partition, mandatory if multiple journal functions are defined,
|
|
if absent defaults to the single available journal drive.
|
|
tier: storage tier for OSDs. If this is not specified, then the
|
|
primary system default tier, 'storage', is used.
|
|
If no device with journal function is configured then the journals for all OSDs will be collocated on the
|
|
same device with the OSD data (partition #1 is for the data and partition #2 for the journl).
|
|
In this case the size of the journal will be journal_default_size.
|
|
-->
|
|
<disk path="/dev/disk/by-path/pci-0000:00:0d.0-ata-2.0" size="50" volumeFunc="osd"/>
|
|
<disk path="/dev/disk/by-path/pci-0000:00:0d.0-ata-3.0" size="50" volumeFunc="osd"/>
|
|
</storageProfile>
|
|
|
|
<storageProfile name="storage-profile-journal-no-tier">
|
|
<!--The disk tags below define each device,
|
|
path: device path
|
|
size: minimum size (in GiB)
|
|
volumeFunc: volume function to be assigned to the device
|
|
For 'osd' function:
|
|
journalSize: the size of the ceph journal in GiB, if absent defaults to journal_default_size in sysinv.conf
|
|
journalLocation: location of the journal partition, mandatory if multiple journal functions are defined,
|
|
if absent defaults to the single available journal drive.
|
|
tier: storage tier for OSDs. If this is not specified, then the
|
|
primary system default tier, 'storage', is used.
|
|
If no device with journal function is configured then the journals for all OSDs will be collocated on the
|
|
same device with the OSD data (partition #1 is for the data and partition #2 for the journl).
|
|
In this case the size of the journal will be journal_default_size.
|
|
-->
|
|
<disk path="/dev/disk/by-path/pci-0000:00:0d.0-ata-2.0" size="50" volumeFunc="osd"/>
|
|
<disk path="/dev/disk/by-path/pci-0000:00:0d.0-ata-3.0" size="50" volumeFunc="journal"/>
|
|
</storageProfile>
|
|
|
|
<storageProfile name="storage-profile-coloc-two-tiers">
|
|
<!--The disk tags below define each device,
|
|
path: device path
|
|
size: minimum size (in GiB)
|
|
volumeFunc: volume function to be assigned to the device
|
|
For 'osd' function:
|
|
journalSize: the size of the ceph journal in GiB, if absent defaults to journal_default_size in sysinv.conf
|
|
journalLocation: location of the journal partition, mandatory if multiple journal functions are defined,
|
|
if absent defaults to the single available journal drive.
|
|
tier: storage tier for OSDs. If this is not specified, then the
|
|
primary system default tier, 'storage', is used.
|
|
If no device with journal function is configured then the journals for all OSDs will be collocated on the
|
|
same device with the OSD data (partition #1 is for the data and partition #2 for the journl).
|
|
In this case the size of the journal will be journal_default_size.
|
|
-->
|
|
<disk path="/dev/disk/by-path/pci-0000:00:0d.0-ata-2.0" size="50" volumeFunc="osd" tier="storage"/>
|
|
<disk path="/dev/disk/by-path/pci-0000:00:0d.0-ata-3.0" size="50" volumeFunc="osd" tier="gold"/>
|
|
</storageProfile>
|
|
|
|
<localstorageProfile name="localstorage-profile_localimage">
|
|
<!--The disk tags below define each device,
|
|
node: device node
|
|
size: minimum size (in GiB).
|
|
The lvg tags below define the local volume group
|
|
lvm_vg_name: local volume group name
|
|
instance_backing: image, or remote
|
|
concurrent_disk_operations: number of parallel I/O intensive disk operations
|
|
-->
|
|
<disk path="/dev/sdb" size="223" />
|
|
<lvg lvm_vg_name="nova-local" instance_backing="image" concurrent_disk_operations="2" />
|
|
</localstorageProfile>
|
|
|
|
<localstorageProfile name="localstorage-profile_remote">
|
|
<!--The disk tags below define each device,
|
|
node: device node
|
|
size: minimum size (in MB).
|
|
The lvg tags below define the local volume group
|
|
lvm_vg_name: local volume group name
|
|
instance_backing: image, or remote
|
|
concurrent_disk_operations: number of parallel I/O intensive disk operations
|
|
-->
|
|
<disk path="/dev/sdb" size="223" />
|
|
<lvg lvm_vg_name="nova-local" instance_backing="remote" concurrent_disk_operations="2" />
|
|
</localstorageProfile>
|
|
|
|
|
|
<interfaceProfile name="if-hp380-profile">
|
|
<!--This is a typical Ethernet interface definition.
|
|
It defines:
|
|
'ifName', name of the interface
|
|
'mtu', mtu of the interface, and
|
|
Ethernet port associated to this Ethernet interface (see port section below)
|
|
-->
|
|
<ethernetInterface ifName="eth0" mtu="1500" >
|
|
<!--An Ethernet port is identified by its class, device and pciAddress in order to match to a physical
|
|
Ethernet port on a host when the profile is applied to it.
|
|
Alternatively, port name can be chosen as a replacement of pciAddress.
|
|
Note that the pciAddress is directly associated with the hardware, it is the recommended identifier.
|
|
Each Ethernet port must have its pciAddress unless Ethernet port name is chosen for the matching,
|
|
in which case each Ethernet port must have its name defined.
|
|
If both pciAddress and port name are provided for each Ethernet port, only pciAddress will be used
|
|
for matching the physical Ethernet port when the profile is applied to a host.
|
|
name: Ethernet port name
|
|
pciAddress: pci address of the Ethernet port, formed in 4 section of hexadecimal digits as:
|
|
XXXX:XX:XX.X
|
|
note: each 'X' represents a hexadecimal digit.
|
|
class: pci class, valid values are:
|
|
Ethernet controller
|
|
Network controller
|
|
device: name of the device
|
|
-->
|
|
<port name="eth0" pciAddress="0000:03:00.0" class="Ethernet controller" device="NetXtreme BCM5719 Gigabit Ethernet PCIe" />
|
|
</ethernetInterface>
|
|
<ethernetInterface ifName="data0" mtu="1500" >
|
|
<port name="eth1" pciAddress="0000:03:00.1" class="Ethernet controller" device="NetXtreme BCM5719 Gigabit Ethernet PCIe" />
|
|
<!--An ethInterface can be used as data, infra, oam, mgmt, pci-passthrough or pci-sriov networks. Network
|
|
type can be specified by adding the network type in the networks section.
|
|
An ethInterface can also be setup as combination of 2 network types. Only mgmt/data, infra/data network can
|
|
be combined.
|
|
-->
|
|
<networks>
|
|
<dataNetwork>
|
|
<!--one or more provider network is required for a dataNetwork-->
|
|
<providerNetworks>
|
|
<providerNetwork name="group0-data0" />
|
|
<providerNetwork name="group0-data0b" />
|
|
</providerNetworks>
|
|
<!--specify ipv4 address mode, valid values are:
|
|
disabled,
|
|
pool,
|
|
dhcp, and
|
|
static-->
|
|
<ipv4 mode="disabled"></ipv4>
|
|
<!--specify ipv4 address mode, valid values are:
|
|
automaticAssignment
|
|
disabled,
|
|
pool,
|
|
linkLocal, and
|
|
static-->
|
|
<ipv6 mode="link-local"></ipv6>
|
|
</dataNetwork>
|
|
</networks>
|
|
</ethernetInterface>
|
|
|
|
<ethernetInterface ifName="eth2" mtu="1500" >
|
|
<port name="eth2" pciAddress="0000:03:00.2" class="Ethernet controller" device="NetXtreme BCM5719 Gigabit Ethernet PCIe" />
|
|
</ethernetInterface>
|
|
|
|
<ethernetInterface ifName="passthrough-0" mtu="1500" >
|
|
<!--This ethernetInterface is defined as pci-passthrough network. See networks section-->
|
|
<port name="eth3" pciAddress="0000:03:00.3" class="Ethernet controller" device="NetXtreme BCM5719 Gigabit Ethernet PCIe" />
|
|
<networks>
|
|
<pciPassthrough>
|
|
<providerNetworks>
|
|
<providerNetwork name="data1" />
|
|
</providerNetworks>
|
|
</pciPassthrough>
|
|
</networks>
|
|
</ethernetInterface>
|
|
|
|
<ethernetInterface ifName="eth4" mtu="1600" >
|
|
<!--This ethernetInterface is defined as pci-sriov network. See networks section-->
|
|
<port name="eth4" pciAddress="0000:04:00.0" class="Ethernet controller" device="82599ES 10-Gigabit SFI/SFP+ Network Connection" />
|
|
</ethernetInterface>
|
|
|
|
<ethernetInterface ifName="eth5" mtu="1500" >
|
|
<port name="eth5" pciAddress="0000:04:00.1" class="Ethernet controller" device="82599ES 10-Gigabit SFI/SFP+ Network Connection" />
|
|
<networks>
|
|
<mgmtNetwork/>
|
|
</networks>
|
|
</ethernetInterface>
|
|
|
|
<ethernetInterface ifName="data1" mtu="1500" >
|
|
<port name="eth6" pciAddress="0000:07:00.0" class="Ethernet controller" device="82599ES 10-Gigabit SFI/SFP+ Network Connection" />
|
|
<networks>
|
|
<dataNetwork>
|
|
<providerNetworks>
|
|
<providerNetwork name="group0-data1" />
|
|
</providerNetworks>
|
|
<ipv4 mode="disabled"></ipv4>
|
|
<ipv6 mode="disabled"></ipv6>
|
|
</dataNetwork>
|
|
</networks>
|
|
</ethernetInterface>
|
|
|
|
<ethernetInterface ifName="eth7" mtu="1500" >
|
|
<port name="eth7" pciAddress="0000:07:00.1" class="Ethernet controller" device="82599ES 10-Gigabit SFI/SFP+ Network Connection" />
|
|
</ethernetInterface>
|
|
|
|
<!--A vlan interface is defined with:
|
|
ifName, name of the vlan
|
|
interface, name of an Ethernet or an aggregrated Ethernet interface on which to run the vlan
|
|
vlanId, vlan id, valid value between 1 and 4094
|
|
mtu, mtu of the vlan interface-->
|
|
<vlanInterface ifName="infra0" interface="eth4" vlanId="303" mtu="1500">
|
|
<!--A vlanInterface can be defined as data, infra, oam, or mgmt networks by adding
|
|
the network type in the networks section.-->
|
|
<networks>
|
|
<infraNetwork/>
|
|
</networks>
|
|
</vlanInterface>
|
|
|
|
<!--A aggregrated Ethernet interface is defined with:
|
|
ifName, name of the vlan
|
|
mtu, mtu of the vlan interface-->
|
|
<aeInterface ifName="ae0" mtu="1500">
|
|
<!--Aggregated Ethernet interface need to define 1 or more interfaces that it uses.
|
|
Add an interface used by this aeInterface by adding a interface section in the interfaces section,-->
|
|
<interfaces>
|
|
<!--An interface being used by the aggregrated ethernet interface. Identified by 'name'-->
|
|
<interface name="eth0"/>
|
|
<interface name="eth2" />
|
|
</interfaces>
|
|
<!--Specify one of the 3 valid aggregated Ethernet modes below-->
|
|
<aeMode>
|
|
<!--valid aggregated Ethernet mode values are:
|
|
activeStandby,
|
|
balanced, and
|
|
ieee802.3ad
|
|
txPolicy is required when ieee802.3ad or balanced is chosen. valid txPolicy values are:
|
|
layer3+4
|
|
layer2
|
|
layer2+3
|
|
-->
|
|
<ieee802.3ad txPolicy="layer3+4" />
|
|
</aeMode>
|
|
</aeInterface>
|
|
|
|
<vlanInterface ifName="vlan11" interface="ae0" vlanId="11" mtu="1600">
|
|
<networks>
|
|
<dataNetwork>
|
|
<!--This dataNetwork uses ip address pools. See ipv4 and ipv6 tag below
|
|
-->
|
|
<providerNetworks>
|
|
<providerNetwork name="group0-ext0" />
|
|
</providerNetworks>
|
|
<ipv4 mode="pool">
|
|
<!--pool needs to be specified with its name. The pool will not verified until the profile is applied
|
|
to a host.-->
|
|
<pool name="pool-1" />
|
|
</ipv4>
|
|
<ipv6 mode="pool">
|
|
<pool name="pool-2" />
|
|
</ipv6>
|
|
</dataNetwork>
|
|
</networks>
|
|
</vlanInterface>
|
|
</interfaceProfile>
|
|
</profiles>
|