Similar to the "product" script there also needs to be in the products directory a "product-network" script where additional networking requirements can be defined for the deployment. Currently, a few networking steps are coded into the orabuntu-services-4.sh script for specific products, but these should not be in the main orabuntu-services deployment scripts. Instead, a script should be called for each product that takes care of setting up additional network requirements for each product. For example, Oracle Grid Infrastructure 18c deployment in Orabuntu-LXC deploys 6 extra OpenvSwitch networks, 4 for private interconnect, and 2 for Flex ASM cluster network. This has to occur much later in the deployment than the main product prerequisite steps, so an additional script is needed for each product that specifies add-on networking to the basic Orabuntu-LXC two-network standard deployment.
Similar to the "product" script there also needs to be in the products directory a "product-network" script where additional networking requirements can be defined for the deployment. Currently, a few networking steps are coded into the orabuntu-services-4.sh script for specific products, but these should not be in the main orabuntu-services deployment scripts. Instead, a script should be called for each product that takes care of setting up additional network requirements for each product. For example, Oracle Grid Infrastructure 18c deployment in Orabuntu-LXC deploys 6 extra OpenvSwitch networks, 4 for private interconnect, and 2 for Flex ASM cluster network. This has to occur much later in the deployment than the main product prerequisite steps, so an additional script is needed for each product that specifies add-on networking to the basic Orabuntu-LXC two-network standard deployment.