Heat templates of different drivers contain duplicate code for network creation.

[rajiv]

Heat templates has duplicate code for network setup in k8s coreos, fedora atomic and swarm drivers. A customized resource can be created for magnum, which can be reused for all the drivers.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/347858

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/347858
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=10e85ee6cefd5915b8b7eb7f210784cea323b4e2
Submitter: Jenkins
Branch: master

commit 10e85ee6cefd5915b8b7eb7f210784cea323b4e2
Author: Rajiv Kumar <email address hidden>
Date: Wed Jul 27 19:35:41 2016 +0530

    Consolidate heat network resources

    Currently for each driver has following code
      1) Create a fixed Network.
      2) Create a fixed subnet in the network created at step 1.
      3) Create a router
      4) Attach subnet(created at step2) to router(created at step 3)

    A new resource is created for above tasks in network.yaml file.
    New resource does the above tasks and output the fixed network ID
    and fixed subnet id, which is used by other parts of the heat
    template.

    Change-Id: Ib347ce5c54c6566300a43e05b277bf80351a2256
    Closes-Bug: #1606912

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/magnum 4.0.0 release.