Age | Commit message (Collapse) | Author | Files | Lines |
|
This change proposes addition of a new optional parameter to
PDF schema to add port to remote management parameters so one
can use none-default ports if needed.
Apart from the PODs that use none-default ports for remote
managamene, n example to this use case is the virtual deployments
that use virtualbmc for simulating BMC which requires calculation
of ports on the fly which could be messy. By adding the port into
PDF, it is straightforward to configure the tools to use none-default
ports if needed.
Change-Id: I4ce41c3977470576296a13dc668dec246fc29314
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
This change proposes addition of a new optional parameter to
PDF schema to make setting different privilege level for remote
access possible via PDF.
In certain cases, the users of a specific POD may not be granted
ADMIN privileges to use remote management capabilities and instead
they may be granted lower privileges such as OPERATOR. Even though
this type of situations could be hanled in provisioning frameworks
and can perhaps be pushed into IDF, it is more appropriate to put
the privilege level setting into PDF next to other remote management
parameters.
Change-Id: I8486c0f8867d8dd54d1731876e0ffef33fb36a96
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
- extend check-{jinja2,schema}.sh to scan vPDFs and construct
proper IDF path for vPDFs;
- add support for '/' in PDF fields, by default filtered by j2
template rendering;
SPEC changes:
- extend remote_management 'type' enum with 'libvirt';
SCHEMA changes:
- add new enum value 'libvirt' according to SPEC update;
- add separate handling of 'remote_management' for baremetal/virtual;
- remote_management 'versions' and 'mac_address' are mandatory for
all but 'libvirt' (used to be mandatory for all);
Change-Id: Ib3f711cae807c3ab27920391402ba74844f155c3
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>
|
|
zte-pod3 and ericsson-pod1 define their disk interfaces as (i)SCSI.
Change-Id: I97945f7a41eec4e8a38de544af95ce4af82df200
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
ssd and nvme drives are static, so extend the list of accepted
disk_rotation values to accomodate this.
Use '0' so the enum can still be parsed as a numeric value.
Change-Id: Ib8ef8cceb495c7eb588c68d151690747463167f5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- create new YAML schema for PDF validation;
- add basic python script for checking a PDF against the schema;
- add bash wrapper for checking all PDFs in Pharos, to be leveraged
later via a new verify CI job;
Change-Id: I47e02642756b7a231138dec3d5258b100b4db72b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|