All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

  1. 04 Apr, 2016 2 commits
  2. 01 Apr, 2016 1 commit
  3. 24 Mar, 2016 1 commit
  4. 10 Feb, 2016 1 commit
  5. 28 Jan, 2016 1 commit
  6. 21 Jan, 2016 1 commit
  7. 16 Nov, 2015 1 commit
  8. 05 Nov, 2015 1 commit
  9. 25 Sep, 2015 1 commit
    • Leigh B Stoller's avatar
      Fix error in duplex link vtop generation, that has been there since at · 543184c7
      Leigh B Stoller authored
      least 2009; change min to max of the bw/rbw values, since the link has to
      satisfy the direction with the higher bandwidth not the lower bandwidth. We
      probably don't run into this very often since people do not often do
      asymmetric links like 100Mb/155Mb, on nodes that have both 1Gb and 100Mb
      Also through in some warning code to catch this before it gets to snmpit,
      which fails when you try to set a 100Mb interface to 1Gb. This might turn
      into a fatal error later.
  10. 08 Sep, 2015 1 commit
  11. 02 Sep, 2015 1 commit
  12. 01 Sep, 2015 1 commit
  13. 24 Aug, 2015 1 commit
  14. 11 Jul, 2015 1 commit
  15. 19 Jun, 2015 1 commit
    • Leigh B Stoller's avatar
      Support for stitch to Lan: · 6c1560d0
      Leigh B Stoller authored
      1. A trivial change in GeniCM; only look at the first two interfaces in the
         link if it references an external node. We already depend on the fact
         that the first two interfaces are in the same order as the two stitch
         points in the stitching section, so as long as we ignore external nodes
         after the second interface, setting up the virtual state for a lan works
         just peachy.
      2. libvtop_test: a bit less trivial, mostly cause of vlan tag pre
         reservation when stitching. When we encapsulate a lan we build another
         lans table entry that is linked. There is no need to do this when the
         encapsulation is vlan, and in fact I had changed links a long time ago
         to not do this, for the exact same reason. Lans are little bit more
         complicated but I think I got it.
  16. 06 May, 2015 1 commit
  17. 01 Apr, 2015 1 commit
  18. 31 Mar, 2015 1 commit
  19. 18 Mar, 2015 1 commit
  20. 09 Mar, 2015 1 commit
  21. 03 Feb, 2015 1 commit
  22. 28 Jan, 2015 1 commit
    • Mike Hibler's avatar
      Implement "plan 1" for dataset sharing: "ephemeral RO snapshots". · 7aefdaa1
      Mike Hibler authored
      You can now simultaneously RW and RO map a dataset because all the RO
      mappings use copies (clones) of a snapshot. Only a single RW mapping
      of course.
      When the RW mapping swaps out it automatically creates a new snapshot.
      So there is currently no user control over when a version of the dataset
      is "published", it just happens everytime you swapout an experiment with
      a RW mapping.
      A new RW mapping does not affect current RO mappings of course as they
      continue to use whatever snapshot they were created with. New RO mappings
      with get the most recent snapshot, which we currently track in the DB via
      the per-lease attribute "last_snapshot".
      You can also now declare a lease to be "exclusive use" by setting the
      "exclusive_use" lease attribute (via modlease). This means that it follows
      the old semantics of only one mapping at a time, whether it be RO or RW.
      This is an alternative to the "simultaneous_ro_datasets" sitevar which
      enforces the old behavior globally. Primarily, I put this attribute in to
      prevent an unexpected failure in the snapshot/clone path from wreaking
      havoc over time. I don't know if there is any value in exposing this to
      the user.
  23. 27 Jan, 2015 1 commit
    • Leigh B Stoller's avatar
      Two co-mingled sets of changes: · 85cb063b
      Leigh B Stoller authored
      1) Implement the latest dataset read/write access settings from frontend to
         backend. Also updates for simultaneous read-only usage.
         The first changes the way that projects and users are treated at the
         CM. When set, we create real accounts (marked as nonlocal) for users and
         also create real projects (also marked as nonlocal). Users are added to
         those projects according to their credentials. The underlying experiment
         is thus owned by the user and in the project, although all the work is
         still done by the geniuser pseudo user. The advantage of this approach
         is that we can use standard emulab access checks to control access to
         objects like datasets. Maybe images too at some point.
         NOTE: Users are not removed from projects once they are added; we are
         going to need to deal with this, perhaps by adding an expiration stamp
         to the groups_membership tables, and using the credential expiration to
         mark it.
         The second new configure option turns on the web login via the geni
         trusted signer. So, if I create a sliver on a backend cluster when both
         options are set, I can use the trusted signer to log into my newly
         created account on the cluster, and see it (via the emulab classic web
         All this is in flux, might end up being a bogus approach in the end.
  24. 12 Jan, 2015 2 commits
  25. 05 Jan, 2015 1 commit
    • Kirk Webb's avatar
      Enforce permissions for dataset leases at mapping time. · bedcb609
      Kirk Webb authored
      * Swapper must have appropriate level of access (RO or RW).
      * If RO is requested, dataset must not be in use RW.
      * If RW is requested, dataset must not be in use at all.
      Also relaxed the checks in the parser; it was considering dynamic lease
      state, which isn't the right thing to do there.
  26. 12 Dec, 2014 1 commit
  27. 05 Nov, 2014 2 commits
  28. 24 Oct, 2014 1 commit
  29. 13 Oct, 2014 1 commit
  30. 08 Oct, 2014 1 commit
  31. 07 Oct, 2014 1 commit
  32. 06 Oct, 2014 1 commit
  33. 09 Aug, 2014 1 commit
  34. 30 Jul, 2014 1 commit
  35. 28 Jul, 2014 1 commit
  36. 14 Apr, 2014 1 commit
  37. 04 Mar, 2014 1 commit