[ https://issues.apache.org/jira/browse/YARN-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567558#comment-16567558 ]
Eric Yang commented on YARN-8619: --------------------------------- Each host may need to be configured differently, and using a file approach as parameter might be more scalable to support other type of network driver as well. Therefore, we might use: {code} yarn network -create my-macvlan-net /tmp/network.json {code} Content of json looks like: {code} { "driver": "macvlan", "hosts": [ { "name":"host1.example.com", "subnet": "172.16.86.0/24", "gateway": "172.16.86.1", "parent": "eth0" } ] } {code} For listing networks: {code} yarn network -list {code} For destroy networks: {code} yarn network -destroy my-macvlan-net {code} > Automate docker network configuration through YARN API > ------------------------------------------------------ > > Key: YARN-8619 > URL: https://issues.apache.org/jira/browse/YARN-8619 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-native-services > Reporter: Eric Yang > Priority: Major > Labels: Docker > > Docker supports bridge, host, overlay, macvlan networking. It might be > useful to automate docker network setup through a set of YARN API to improve > management of docker networks. Each type of network driver requires > different type of parameters. For Hadoop use case, it seems more useful to > focus on macvlan networking for ease of use and configuration. It would be > great addition to support commands like: > {code} > yarn network create -d macvlan \ > --subnet=172.16.86.0/24 \ > --gateway=172.16.86.1 \ > -o parent=eth0 \ > my-macvlan-net > {code} > This changes docker configuration to hosts managed by YARN. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org