Comment 5 for bug 1448254

Sorry, lost track of the bug as it fell into 100 papercuts...

if it helps I solved my ordering problem by modifying the
    /lib/systemd/sysytem/openvswitch-nonetwork.service
as follows

    [Unit]
    Description=Open vSwitch Internal Unit
    PartOf=openvswitch-switch.service

    # Without this all sorts of looping dependencies occur doh!
    DefaultDependencies=no

    #precedants pulled from isup@ service requirements
    After=apparmor.service local-fs.target systemd-tmpfiles-setup.service

    #subsequent to this service we need the network to start
    Wants=network-pre.target openvswitch-switch.service
    Before=network-pre.target openvswitch-switch.service

    [Service]
    Type=oneshot
    RemainAfterExit=yes
    EnvironmentFile=-/etc/default/openvswitch-switch
    ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \
          --system-id=random $OPTIONS
    ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop

This pulled up the services and allowed my configuration to work

openvswitch-nonetwork.service
● ├─openvswitch-switch.service
● └─network-pre.target
● ├─<email address hidden>
● ├─<email address hidden>
● ├─<email address hidden>
● ├─<email address hidden>
● ├─networking.service
● └─network.target
● ├─mysql.service
● ├─openvswitch-switch.service
● ├─rabbitmq-server.service
● ├─rc-local.service
● ├─ssh.service
● └─network-online.target
● ├─apache2.service
● ├─dns-clean.service
● └─kerneloops.service

(the dots are green :) )

There is lots of noise on the net about chickens and eggs, so I do not know if it solves some other case
The thing that took me so long to solve it (besides unfamiliarity of systemd) was the AUTOMATIC inclusion of dependencies, who on earth dreamt that up?