1. 08 Mar, 2013 1 commit
  2. 24 Sep, 2012 1 commit
    • Eric Eide's avatar
      Replace license symbols with {{{ }}}-enclosed license blocks. · 6df609a9
      Eric Eide authored
      This commit is intended to makes the license status of Emulab and
      ProtoGENI source files more clear.  It replaces license symbols like
      "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
      blocks that contain actual license statements.
      
      This change was driven by the fact that today, most people acquire and
      track Emulab and ProtoGENI sources via git.
      
      Before the Emulab source code was kept in git, the Flux Research Group
      at the University of Utah would roll distributions by making tar
      files.  As part of that process, the Flux Group would replace the
      license symbols in the source files with actual license statements.
      
      When the Flux Group moved to git, people outside of the group started
      to see the source files with the "unexpanded" symbols.  This meant
      that people acquired source files without actual license statements in
      them.  All the relevant files had Utah *copyright* statements in them,
      but without the expanded *license* statements, the licensing status of
      the source files was unclear.
      
      This commit is intended to clear up that confusion.
      
      Most Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the Affero GNU General Public License, version 3
      (AGPLv3).
      
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      license.
      
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
      (LGPL).
      6df609a9
  3. 15 Feb, 2012 1 commit
  4. 05 Oct, 2011 1 commit
    • Leigh Stoller's avatar
      Fix up IsExpired(); we do not store an expires field in the DB! · 7e4c6e2b
      Leigh Stoller authored
      Instead, lets use the created field, and age out authorities and
      components if they get too stale. This will help to keep sites from
      getting too far out of date with respect to the clearinghouse.
      
      Also, the URL for the certificates now comes from configure: PROTOGENI_URL
      7e4c6e2b
  5. 21 Sep, 2011 1 commit
    • Gary Wong's avatar
      Add support for sub-authorities. · 75f89a35
      Gary Wong authored
      Generate authority certificates for local sub-authorities (i.e. authorities
      corresponding to a local project) on demand.
      
      Map per-project URLs to the same XMLRPC server handled in the context of
      the authority for the specified project.
      
      Make the SA give out per-project credentials when it's asked for a
      GetCredential in a sub-authority.
      75f89a35
  6. 15 Jun, 2011 1 commit
  7. 09 Jun, 2011 1 commit
    • Leigh Stoller's avatar
      Bug Fix: a bunch of fixes to make sure that holders of SFA credentials · ac287e02
      Leigh Stoller authored
      can create slices, and be notified of expiring slices and slivers. The
      problem is the PL credentials do not inclide an email address, so we
      have to get it from the user's registry. This required a bunch of goo
      top find the proper place to do a resolve, since PL credentials do not
      include a URL either.
      ac287e02
  8. 04 Mar, 2011 1 commit
  9. 24 Feb, 2011 1 commit
  10. 17 Feb, 2011 1 commit
  11. 07 Feb, 2011 1 commit
  12. 13 Jan, 2011 1 commit
  13. 06 Jan, 2011 1 commit
  14. 10 Nov, 2010 1 commit
  15. 09 Nov, 2010 1 commit
  16. 29 Sep, 2010 1 commit
  17. 25 May, 2010 1 commit
  18. 12 May, 2010 1 commit
  19. 26 Apr, 2010 1 commit
  20. 04 Feb, 2010 1 commit
    • Leigh Stoller's avatar
      Big cleanup of GeniComponent stuff. Moved Resolve() into GeniComponent · b63cb055
      Leigh Stoller authored
      since it has to be aware of the CM version. Add a Version() call to
      GeniAuthority with goes asks the CM what version it is exporting.
      Based on that, we know how to do a resolve of a component. Refactored
      the code that was used in GeniAggregate when creating tunnels, since
      that is where we have to Resolve components. This also turns up in
      cooked mode.
      
      Continuine moving towards a urn-only world. If a GeniAuthority or a
      GeniComponent does not have the URN set locally in the DB, go back to
      the clearinghouse and get it. Error if it is not known, and go bang on
      the remote site to update and rerun register_resources.
      b63cb055
  21. 25 Jan, 2010 1 commit
  22. 06 Jan, 2010 1 commit
    • Leigh Stoller's avatar
      Slice expiration changes. The crux of these changes: · 5c63cf86
      Leigh Stoller authored
      1. You cannot unregister a slice at the SA before it has expired. This
         will be annoying at times, but the alphanumeric namespace for slice
         ames is probably big enough for us.
      
      2. To renew a slice, the easiest approach is to call the Renew method
         at the SA, get a new credential for the slice, and then pass that
         to renew on the CMs where you have slivers.
      
      The changes address the problem of slice expiration.  Before this
      change, when registering a slice at the Slice Authority, there was no
      way to give it an expiration time. The SA just assigns a default
      (currently one hour). Then when asking for a ticket at a CM, you can
      specify a "valid_until" field in the rspec, which becomes the sliver
      expiration time at that CM. You can later (before it expires) "renew"
      the sliver, extending the time. Both the sliver and the slice will
      expire from the CM at that time.
      
      Further complicating things is that credentials also have an
      expiration time in them so that credentials are not valid forever. A
      slice credential picks up the expiration time that the SA assigned to
      the slice (mentioned in the first paragraph).
      
      A problem is that this arrangement allows you to extend the expiration
      of a sliver past the expiration of the slice that is recorded at the
      SA. This makes it impossible to expire slice records at the SA since
      if we did, and there were outstanding slivers, you could get into a
      situation where you would have no ability to access those slivers. (an
      admin person can always kill off the sliver).
      
      Remember, the SA cannot know for sure if there are any slivers out
      there, especially if they can exist past the expiration of the slice.
      
      The solution:
      
      * Provide a Renew call at the SA to update the slice expiration time.
        Also allow for an expiration time in the Register() call.
      
        The SA will need to abide by these three rules:
        1. Never issue slice credentials which expire later than the
           corresponding slice
        2. Never allow the slice expiration time to be moved earlier
        3. Never deregister slices before they expire [*].
      
      * Change the CM to not set the expiration of a sliver past the
        expiration of the slice credential; the credential expiration is an
        upper bound on the valid_until field of the rspec. Instead, one must
        first extend the slice at the SA, get a new slice credential, and
        use that to extend the sliver at the CM.
      
      * For consistency with the SA, the CM API will changed so that
        RenewSliver() becomes RenewSlice(), and it will require the
        slice credential.
      5c63cf86
  23. 02 Dec, 2009 2 commits
  24. 30 Oct, 2009 1 commit
  25. 10 Aug, 2009 1 commit
  26. 24 Mar, 2009 1 commit
  27. 04 Mar, 2009 1 commit
    • Leigh Stoller's avatar
      Change EMULAB-COPYRIGHT to GENIPUBLIC-COPYRIGHT, for future expansions · 6c8d30fc
      Leigh Stoller authored
      to the Geni Public License at http://www.geni.net/docs/GENIPubLic.pdf,
      whose expansion at this time is:
      
      -----
      Permission is hereby granted, free of charge, to any person obtaining
      a copy of this software and/or hardware specification (the "Work") to
      deal in the Work without restriction, including without limitation the
      rights to use, copy, modify, merge, publish, distribute, sublicense,
      and/or sell copies of the Work, and to permit persons to whom the Work
      is furnished to do so, subject to the following conditions:
      
      The above copyright notice and this permission notice shall be
      included in all copies or substantial portions of the Work.
      
      THE WORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
      OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
      MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
      NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
      HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
      WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
      OUT OF OR IN CONNECTION WITH THE WORK OR THE USE OR OTHER DEALINGS
      IN THE WORK.
      6c8d30fc
  28. 02 Mar, 2009 1 commit
    • Leigh Stoller's avatar
      A bunch of changes for a "standalone" clearinghouse. Presently this · 60f04310
      Leigh Stoller authored
      its really a hugely stripped down Emulab boss install, using a very
      short version of install/boss-install to get a few things into place.
      
      I refactored a few things in both the protogeni code and the Emulab
      code, and whacked a bunch of makefiles and configure stuff. The result
      is that we only need to install about 10-12 files from the Emulab
      code, plus the protogeni code. Quite manageable, if you don't mind
      that it requires FreeBSD 6.X ... Still, I think it satisfies the
      requirement that we have a packaged clearinghouse that can be run
      standalone from a running Emulab site.
      60f04310
  29. 12 Jan, 2009 1 commit
  30. 18 Nov, 2008 1 commit
  31. 03 Nov, 2008 1 commit
  32. 30 Oct, 2008 1 commit
  33. 16 Oct, 2008 1 commit
  34. 22 Aug, 2008 1 commit
  35. 12 Aug, 2008 1 commit
  36. 03 Jun, 2008 1 commit
  37. 29 May, 2008 1 commit
  38. 27 May, 2008 1 commit