1. 29 Jun, 2017 6 commits
  2. 27 Jun, 2017 4 commits
  3. 26 Jun, 2017 5 commits
  4. 25 Jun, 2017 1 commit
  5. 24 Jun, 2017 5 commits
  6. 23 Jun, 2017 11 commits
  7. 21 Jun, 2017 4 commits
  8. 20 Jun, 2017 4 commits
    • network: new network parser part II · f9373e40
      Christian Brauner authored
      Serge and I discussed the new network parser we've merge a couple of days ago.
      He pointed out that a bunch of use-cases we're currently supporting in the old
      network parser would be broken by the new parser. As we've pointed out many
      times before, we're strongly commited to backwards compatibility and not
      breaking existing use-cases. That's why we decided to take a new approach.
      Instead of trying to mangle the old parser and new parser to come up with
      something that allows a smooth transition we will simply deprecate the old
      configuration keys with LXC 3.0. In the meantime we will support the full-blown
      old legacy parser and the new network parser. Specifically, this means that
      we're deprecating:
      
          lxc.network.*
      
      in favor of
      
          lxc.net.*
      
      With LXC 2.1. defining networks using lxc.network.* keys will cause a
      deprecation warning to be shown/logged. We strongly suggest that users upgrade
      their existing configuration files to switch to the new network configuration
      parser. Starting with LXC 3.0 we will remove all lxc.network.* keys and will
      only support lxc.net.* style network configurations.
      
      Note that the new network configuration parser will only accept index based
      configuration keys, i.e. we are only support lxc.net.[i].* keys without an
      index such as lxc.net.type are not supported anymore. The advantages of this
      approach are vast. Not just internally, but also user-facing since it is much
      clearer what configuration key belongs to what network.
      Signed-off-by: 's avatarChristian Brauner <christian.brauner@ubuntu.com>