{"action":"created","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/6705","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/6705/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/6705/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/6705/events","html_url":"https://github.com/systemd/systemd/pull/6705","id":254173876,"number":6705,"title":"networkd: ship a default network file that matches all VRFs","user":{"login":"andir","id":638836,"avatar_url":"https://avatars1.githubusercontent.com/u/638836?v=4","gravatar_id":"","url":"https://api.github.com/users/andir","html_url":"https://github.com/andir","followers_url":"https://api.github.com/users/andir/followers","following_url":"https://api.github.com/users/andir/following{/other_user}","gists_url":"https://api.github.com/users/andir/gists{/gist_id}","starred_url":"https://api.github.com/users/andir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andir/subscriptions","organizations_url":"https://api.github.com/users/andir/orgs","repos_url":"https://api.github.com/users/andir/repos","events_url":"https://api.github.com/users/andir/events{/privacy}","received_events_url":"https://api.github.com/users/andir/received_events","type":"User","site_admin":false},"labels":[{"id":191919611,"url":"https://api.github.com/repos/systemd/systemd/labels/needs-discussion","name":"needs-discussion","color":"fbca04","default":false},{"id":219549709,"url":"https://api.github.com/repos/systemd/systemd/labels/network","name":"network","color":"fad8c7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-08-31T00:31:53Z","updated_at":"2017-08-31T09:10:20Z","closed_at":null,"author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/systemd/systemd/pulls/6705","html_url":"https://github.com/systemd/systemd/pull/6705","diff_url":"https://github.com/systemd/systemd/pull/6705.diff","patch_url":"https://github.com/systemd/systemd/pull/6705.patch"},"body":"This fixes #4308"},"comment":{"url":"https://api.github.com/repos/systemd/systemd/issues/comments/326237570","html_url":"https://github.com/systemd/systemd/pull/6705#issuecomment-326237570","issue_url":"https://api.github.com/repos/systemd/systemd/issues/6705","id":326237570,"user":{"login":"andir","id":638836,"avatar_url":"https://avatars1.githubusercontent.com/u/638836?v=4","gravatar_id":"","url":"https://api.github.com/users/andir","html_url":"https://github.com/andir","followers_url":"https://api.github.com/users/andir/followers","following_url":"https://api.github.com/users/andir/following{/other_user}","gists_url":"https://api.github.com/users/andir/gists{/gist_id}","starred_url":"https://api.github.com/users/andir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andir/subscriptions","organizations_url":"https://api.github.com/users/andir/orgs","repos_url":"https://api.github.com/users/andir/repos","events_url":"https://api.github.com/users/andir/events{/privacy}","received_events_url":"https://api.github.com/users/andir/received_events","type":"User","site_admin":false},"created_at":"2017-08-31T09:10:20Z","updated_at":"2017-08-31T09:10:20Z","author_association":"CONTRIBUTOR","body":"The real issue, for me at least, here is there doesn't seem to be a\ngeneric approach in managing link-state within systemd yet. If there\nwould be a setting allowing people to explicitly set\n`State=Up`/`State=Down` or similar we could probably fix the whole issue\nby documenting an example that also covers the link state.\n\nOn a side note: People can and also might want to add IPs on the VRF\ninterface - to manage VRF internal loopback addresses - which will also\nset the interface up.\n\nOn 01:46 31.08.17, Lennart Poettering wrote:\n> Hmm, this would mean networkd would by default manage all VRF devices. Is this really something we should do by default? People might want to create/manage VRF devices outside of the networkd scope too, no?\n\nThat is an issue that spans more then just VRFs IMO. A `[Match]` block\nthat matches networkd managed links/netdevs could potentially be handy\nhere?.\n\nOn 01:46 31.08.17, Lennart Poettering wrote:\n> So far we didn't ship much default configuration with networkd (with some minor and very specific exceptions), following the logic, that in order to make networkd manage something the user first should tell it so, but by default we stay away. Can you elaborate why it would make sense to depart from that for VRF devices?\n\nI am also not in favor of shipping more default configuration. Should\nThere be a generic way to handle interface state then? People might want\nto explicitly disable a specific interface - since they are just\npreparing a new customer service or whatever that can't be active yet.\n\nAn issue with the proposed change is that networkd will try to do DHCP\non the VRF interface? So setting `DHCP=no`, `AcceptRA=no` would be sane if\nthis PR is to be merged?\n"}}
{"actor":{"display_login":"andir"}}