Age | Commit message (Collapse) | Author | Files | Lines |
|
In order to fully utilize all available resources (88 CPU threads,
256GB RAM) in Fuel virtual deployments, add basic PDF/IDF files
based on ericsson-virtual1 templates.
IDF is mostly unchanged compared to idf-virtual1 from Ericsson lab.
PDF allocates more disk capacity for the first node (controller role
in Fuel deployments), as well as more vCPUs/RAM for the last 2 nodes
(compute role in Fuel virtual deployments).
While at it, align ericsson vPOD definitions to match the new format
(2 disks should be defined for each compute node; account for HT).
Change-Id: Iac8ee857a3297084ea9f087ba8007950413fda25
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
ethtool reports the link speed as 'unknown' for said devices.
The only (current) consumer of this information is Fuel's new VPP
support, which detects all these interfaces as 'Gigabit', so align
our definitions in order to be able to dynamically construct the
VPP interface names based on PDF (link speed) + IDF (PCI bus).
While at it, add a new j2 macro helper to be used by Fuel installer.
Change-Id: Id6a52bbb7b86bbe3db2a81bb91ac378c6876ffc0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I20e70ec3264e807fb85585441d51752b13f5389d
Signed-off-by: mting <dianfeng.du@ericsson.com>
|