Update git submodules

Update git submodules

* Update docs/submodules/fuel from branch 'master'
  - Merge "Add NOVCP HA OVS scenario (baremetal, virtual)"
  - Add NOVCP HA OVS scenario (baremetal, virtual)

    Add a new class of scenarios, based on existing baremetal HA
    scenarios, but instead of having a virtualized control plane (VCP),
    all Openstack controller services will run directly on the cluster
    nodes.
    This change adds the common scaffolding, as well as the OVS scenario.

    The new scenario(s) can be used on full-baremetal clusters, soon on
    full-virtual clusters and later on hybrid (virt + bare) clusters.
    This change defines old (current) style scenario definitions for
    both baremetal and virtual, both named:
    - os-nosdn-nofeature-novcp-ha;

    Prerequisites:
    1. Merge-able by name reclass.storage.node definitions
       Each cluster (e.g. database, telemetry) adds its own set of
       reclass storage node defitions, which for novcp scenarios should
       be merged into a single node (kvm) based on the 'name' property.
       This is not currently supported by upstream reclass 'node.sls'
       high state, so add support for it via an early patch (required
       before salt-master-init.sh tries to handle reclass.storage).
    2. common reclass classes for novcp
       Some of the classes in `baremetal-...-common-ha` are not fit for
       novcp as they define VCP-specific config/inheritance, so add new
       versions of said classes with novcp in mind or adapt old classes:
       - parameterize ctl hostname in `openstack_compute.yml`;
       - new `openstack_control_novcp.yml`;
       - new `openstack_init_novcp.yml`;
    3. Handle hard set names in state files for baremetal nodes
       Some of our state files (e.g. maas) hardcodes baremetal node names
       to 'kvm', 'cmp', so we need to align the names in novcp scenario
       with these values to re-use the maas state. As a future improvement
       we should parameterize these names in all state files.
       As a consequence, our baremetal controller nodes will also use
       'kvm*' hostnames (instead of 'ctl*').
    4. Add 'noifupdown' to all interfaces on kvm nodes to prevent duplicate
       IPs/routes created at *any* ifup due to /etc/network/route-br-ex.
       Patch salt-formula-linux to skip network restart on 'noifupdown',
       also when routes are present on that interface.

    JIRA: FUEL-310

    Change-Id: Ic67778f63e5ee0334dbfe9547c7109ec1a938d61
    Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>