Update git submodules

* Update docs/submodules/pharos from branch 'master'
  - Merge changes from topics 'fuel-netmap', 'fix-check-jinja'
    
    * changes:
      [fuel] Add net_map.j2 for net config abstraction
      [fuel] Explicitly blacklist incompatible labs
      [IDF] Add optional 'idf.installer' array
    
  - [fuel] Add net_map.j2 for net config abstraction
    
    This will be leveraged by other j2 templates in Fuel to construct
    scenario-specific network config files.
    
    Change-Id: Iba1fd99b23936fe42abe16af3cd80dce2a63d997
    Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
    
  - [fuel] Explicitly blacklist incompatible labs
    
    Previously, we used to silently refuse to construct 'pod_config'
    for PODs missing mandatory PDF/IDF configuration; and instead
    generated an empty output YAML.
    
    Retire safety checks in Fuel IA and explicitly blacklist Fuel via
    new 'idf.installer' where appropiate.
    
    The following PODs do not yet support Fuel due to missing 'idf.fuel':
    - ericsson-pod2
    - huawei-pod1
    - intel-pod18
    - nokia-pod1
    - zte-pod2
    - zte-pod3
    
    Change-Id: Ief62d62f99a79187303e3f15b83030289e5efdcb
    Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
    
  - [IDF] Add optional 'idf.installer' array
    
    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>
    

1 files changed, 0 insertions, 0 deletions

diff --git a/docs/submodules/pharos b/docs/submodules/pharos
-Subproject ce5cd10b7ce6714124dcdbfc76365ae0854f914
+Subproject 48b9aa5af10deebcda256d74681b1c56f516adc