| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
For non-dpdk scenarios we define as cpu config:
0,1 for OS
2-7 for nova
For dpdk scenarios we define as cpu config:
0,1 for OS,
2,3 for DPDK drivers and processes
4-7 for nova
Dpdk config is also provided for the 3 thunderx nodes which currently
serve as KVM nodes. The config is similar to the config above with
cores 4-47 being used for nova.
JIRA: ARMBAND-364
Change-Id: I761aa8e73935b7180f4f377841cc93c9d81cf4d7
Signed-off-by: Charalampos Kominos <charalampos.kominos@enea.com>
Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
|
|
For non-dpdk scenarios we define as cpu config:
0,1 for OS
2-7 for nova
For dpdk scenarios we define as cpu config:
0,1 for OS,
2,3 for DPDK drivers and processes
4-7 for nova
JIRA: ARMBAND-364
Change-Id: Icc976e8511fed221b71a348afda3cbe4e0556b1a
Signed-off-by: Charalampos Kominos <charalampos.kominos@enea.com>
|
|
- Enea lab has infra IPs in public networks, similar to ericsson-pod1
so start assigning public IPs from .100 onwards;
- since most Fuel PODs have public (and mgmt) IPs starting at .100,
align this across all PODs for uniformity;
- align all mgmt networks start to .10;
JIRA: ARMBAND-365
Change-Id: I9df4083c9e2e4c15da5ce6a2cb24df560808161a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I03098ca3d4a90f6420cee64985c2853931a6a870
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Constructs based on reclass interpolation (e.g. '${_param:x}') do
not work when parameters are passed via reclass.storage templating,
so change reclass interpolation syntax with classic YAML anchors.
Change-Id: Ia974d45fc6a5869f4b30b31b947df088ea3aaf0c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
In order to enable DPDK for OVS scenarios in Armband, we need DPDK
specific configuration to be parameterizable.
The default DPDK configuration values will remain in Fuel repo and
will be overriden with the values defined in IDF (only if present).
Since hugepage config and CPU pinning also apply to non-DPDK
scenarios, handle them together for 'common', respectively 'dpdk'.
To keep things simple, we will reuse the format expected by Fuel's
reclass model, so we can pass the whole config block as-is.
- IDF schema: fuel: Add strict checking of new block's structure,
while allowing the rvalues to be more or less freestyle;
- arm-pod6 IDF: Add initial config block implementation;
JIRA: ARMBAND-342
Change-Id: I9224f06bb6b9fb2387414eb2a1be35461c27fb99
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
MaaS timeouts should be configurable on per-POD basis, since nodes
in some labs take longer to comission/deploy than our default values.
IDF SCHEMA:
- add new properties to Fuel IDF section;
Change-Id: Ife5ff85faeae683a8c1781cae8b29f09c1f07b82
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
There is no easy way to determine automatically if a PDF/IDF set is
compatible with a specific installer adapter.
Most common incompatibilities are caused by:
- installer adapters hardcode more network ports than nodes have
defined in PDF;
- installer adapters hardcode more nodes than PDF defines;
Previous attempt at handling this dynamically (cd54edf) fails for
recently added PODs, so let's handle this explicitly per-pod via a
new optional IDF property, 'idf.installer'.
If 'idf.installer' is defined, it will be used by `check-jinja2.sh`
as a filter-in list of installer adapters to check against.
The default (no 'idf.installer' present) is to check all IAs.
Leverage the new property for:
- arm-pod5: not enough network ports on computes for Compass, Joid;
- arm-pod7: same as arm-pod5;
- bii-pod1: no 'storage' network defined in IDF for Daisy;
- zte-pod9: 3 cluster nodes are only supported by Daisy for now;
SPEC changes:
- net_config (previously mandatory for IDF version '0.1') is now
mandatory only if 'idf.fuel' or 'idf.daisy' is defined;
Fixes: cd54edf
Change-Id: I706c05519e5491ad631069d7cc090e9c8bfd3011
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- add 'version: 1.0' to PDF spec;
- add 'version: 1.0' to all existing lab PDFs;
- extend schema with new property;
- add workaround for value-based decision-making in schema version
selection via `validate-template.py`;
- add support for multiple schema versions;
- add versions for all schema blocks defined so far;
- fix PDF schema pattern for disk size decimals (e.g. '1.8T');
Change-Id: Ie8f768803ec19f1f9a7982fe5ca59df80764fc4a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- net_config is moved to IDF file;
- rename 'disk' to 'disks';
- add 'name: nicN' to interface;
- add 'disk_rotation: 0' for ssd drivers;
Change-Id: I1ea91a65abeb9db4f2f73f25ce51cd059b4b4753
Signed-off-by: ting wu <ting.wu@enea.com>
|
|
- disk_rotation: 0 for SSD drives;
- rename 'disk' to 'disks';
- add 'name: nicN' to jumpserver & node interfaces;
Change-Id: I17d8e64f9b7c5b236d2494566e24bac91f1fc914
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, drop 'fixed_ips', which is a leftover from early
net_config implementation and is not currently used by the Fuel
installer (only Daisy seems to use 'fixed_ips', but falls back
to using 'address' of the first interface when 'fixed_ips' is not
present).
Keep 'address: 192.168.11' on jumpserver first interface for Daisy
compatibility.
Change-Id: I83455a45a2a19fde6b9fb8b7f0fa8872b1291ab0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Although current YAML files in Pharos are all valid according to
yamllint, the resulting YAMLs after PDF/IDF + IA interpolations
still have a lot of violations, which need to be addressed.
PDF changes:
- bii/pod1:
+ fix typo in disks_A reference;
IDF changes:
- replace empty strings with `~` keyword (will be expanded to 'None');
IA (installer adapter) changes:
- apex:
+ add missing document start;
- compass4nfv:
+ too few spaces before comment;
+ missing starting space in comment;
+ replace '\t' with spaces;
- daisy:
+ None;
- fuel:
+ check conf.idf is defined first (fix parse for PODs without IDF);
+ move document start outside conf.idf condition
- joid:
+ None;
This is not an exhaustive change, some yamllint issues are still there
but require either refactoring IAs or changing the PDF/IDF files in a
way that needs the respective maintainer's input.
Change-Id: I26743e265217e892b6a94de96a016c295ea24fb5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: PHAROS-298
Change-Id: Ied56d4e1fdf09d3361de5aae64088e65cb5125ad
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Inline encrytion of yaml files allows us to make away with securedlab's
restrictions
Going forward, anyone will be able to see Lab PDFs
See:
https://github.com/opnfv/pharos/blob/master/config/utils/README.eyaml.rst
If you are the reviewer on this changeset it is becasue
git blamed showed you to be the author of the pdf in this review.
Encrypting ipmi password is optional. I have scrubbed the password from
this change. If you do not need the password to be hidden, please let me
know in the comment, and I will put it back.
If you do need the password hidden, please follow the readme above and
ammend this patch to include the encrypted value that you create on your
pods jumphost.
Change-Id: Ic2db523e7f82a0fb48e462a1fbe1402267f22618
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
Alexandru Avadanii
Charalampos Kominos
Cristina Pauna
ting wu
agardner