This project is mirrored from https://gitee.com/NQL886/scope.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 03 Sep, 2015 1 commit
  2. 28 Aug, 2015 1 commit
  3. 26 Aug, 2015 1 commit
  4. 03 Aug, 2015 1 commit
    • Peter Bourgon's avatar
      Revert to correct edge construction · 0aadf644
      Peter Bourgon authored
      Another implicit invariant in the data model is that edges are always of the
      form (local -> remote). That is, the source of an edge must always be a node
      that originates from within Scope's domain of visibility. This was evident by
      the presence of ingress and egress fields in edge/aggregate metadata.
      
      When building the sniffer, I accidentally and incorrectly violated this
      invariant, by constructing distinct edges for (local -> remote) and (remote ->
      local), and collapsing ingress and egress byte counts to a single scalar. I
      experienced a variety of subtle undefined behavior as a result. See #339.
      
      This change reverts to the old, correct methodology. Consequently the sniffer
      needs to be able to find out which side of the sniffed packet is local v.
      remote, and to do that it needs access to local networks. I moved the
      discovery from the probe/host package into probe/main.go.
      
      As part of that work I discovered that package report also maintains its own,
      independent "cache" of local networks. Except it contains only the (optional)
      Docker bridge network, if it's been populated by the probe, and it's only used
      by the report.Make{Endpoint,Address}NodeID constructors to scope local
      addresses. Normally, scoping happens during rendering, and only for pseudo
      nodes -- see current LeafMap Render localNetworks. This is pretty convoluted
      and should be either be made consistent or heavily commented.
      0aadf644
  5. 30 Jul, 2015 1 commit
    • Peter Bourgon's avatar
      Fixes to NodeMetadata · 3dd59c8b
      Peter Bourgon authored
      NewNodeMetadata -> MakeNodeMetadata. It doesn't return a pointer, so
      Make is more idiomatic.
      
      Invoke MakeNodeMetadata when necessary. The zero value for a
      NodeMetadata is no longer valid.
      
      Split MakeNodeMetadata to two constructors. MakeNodeMetadata when you
      don't have anything to prepopulate; MakeNodeMetadataWith when you do.
      
      Also, a fix to the tests in app. We unmarshal a RenderableNode struct,
      which has a JSON-ignored NodeMetadata field. The zero value is invalid,
      so we need to fix that before performing comparisons.
      3dd59c8b
  6. 16 Jul, 2015 1 commit
  7. 15 Jul, 2015 1 commit
  8. 30 Jun, 2015 1 commit
    • Peter Bourgon's avatar
      Probe re-org · f4b3930a
      Peter Bourgon authored
      - tag/weave* -> package overlay
      - tag/origin_host* -> package host
      - tag/topology* -> package main
      f4b3930a
  9. 29 Jun, 2015 1 commit
  10. 23 Jun, 2015 2 commits