1. 15 Aug, 2013 1 commit
    • Gary Wong's avatar
      Add tmcd support for the proposed "geni-get" GENI client side. · f1120a88
      Gary Wong authored
      This allows nodes in GENI slices to retrieve information about their
      sliver and slice via tmcc (or equivalent client-side support).  The
      set of queries available and their names were agreed upon in GEC 17
      sessions and subsequent discussions.
  2. 13 Aug, 2013 1 commit
  3. 23 Jul, 2013 18 commits
  4. 22 Jul, 2013 1 commit
  5. 01 Jul, 2013 1 commit
  6. 27 Jun, 2013 1 commit
  7. 17 Jun, 2013 1 commit
  8. 13 Jun, 2013 2 commits
    • Leigh Stoller's avatar
    • Leigh Stoller's avatar
      Changes for XEN container loadinfo call, to support whole disk images · 533f7030
      Leigh Stoller authored
      and more efficient space usage.
      When loading a whole disk image, we need to know what partition is
      going to be the boot partition, since we do not get that info from
      Lets be more efficient with space/time; there is no reason to unzip
      the image on the client until we create the container. Instead, tell
      frisbee to write the raw ndz file to its lvm. Later, we unzip from
      that into the target lvm. But to do that, we need to know how many
      chunks the file is in advance, and that is easy to figure out in tmcd.
  9. 04 Jun, 2013 1 commit
    • Leigh Stoller's avatar
      No longer return tunnel info to containers; just plain interfaces. · bd2964e2
      Leigh Stoller authored
      Neither OpenVZ or XEN containers can do anything with the tunnel info,
      since tunnels are created in the root context and all the container
      sees is an interface. We have a hack in the client side for openvz,
      but rather then try to duplicate that hack for every XEN guest, lets
      do this the right way, and return plain ifconfig lines from tmcd and
      config them like any other interface. Since we rely on MAC addresses
      to do this, we now return MACs to the root context when it gets the
      tunnel info.
      To do this we need to know the difference between the root context
      asking for info *about* the container, and the container asking for
      its *own* info. Since both XEN and OpenVZ containers are redirected
      through the tmcc proxy, I changed the protocol so tmcd can tell who is
      asking. This is imperfect, since we might someday want the container
      to bypass the proxy, but for now it will do.
      The other consideration is that a XEN container might have requested a
      public IP, in which case it could actually do all of the tunnel stuff
      itself, but then again we have to worry about all of the guests being
      able to do tunnels, and so the easiest thing to do is just always do
      it in the root context for the container.
  10. 28 May, 2013 1 commit
    • Leigh Stoller's avatar
      Woeful genirack hack; return mounts on the 172 network to avoid going · ce3d8572
      Leigh Stoller authored
      through the 172 phony router we have setup on the control node. This
      is silly to do for local traffic, but getting XEN guests to not do it,
      turned into a pit that I didn't want to enter. We want this so that
      arplockdown works properly; the mac address is really the client not a
      router. Revisit later.
  11. 22 May, 2013 2 commits
  12. 15 May, 2013 1 commit
  13. 14 May, 2013 1 commit
    • Leigh Stoller's avatar
      Add new script to do arp lockdown on boss. · f5cc889a
      Leigh Stoller authored
      The other version is only for the client side (subboss,ops), but does
      not work on real boss. Also hooked into tbswap so that the arps are
      updated during swapin/swapout. Also change tmcd to return arp
      directives for all containers, not just on shared nodes.
  14. 10 May, 2013 1 commit
  15. 02 May, 2013 1 commit
  16. 01 May, 2013 1 commit
  17. 30 Apr, 2013 3 commits
    • Kirk Webb's avatar
      Add complete local node storage support from parser down to tcmd. · dab52801
      Kirk Webb authored
      Doing this required adding columns to the virt and physical blockstores
      tables to mark the attributes that will be considered for mapping.
      Unmarked entries just flow through to the client-side.
      This commit also introduces filesystem support in the form of passing
      through a mount point to the client-side.  It is left to the client to
      decide what filesystem and fs options to use to setup the space, including
      any logical volume aggregation required to support the request.
    • Mike Hibler's avatar
      Avoid redundent output in hwinfo command. · d468c60f
      Mike Hibler authored
    • Mike Hibler's avatar
      Implement the "hwinfo" call. · 636e6436
      Mike Hibler authored
      This call returns info about the HW on the node (duh!) for the benefit
      of the upcoming "nodetest". It returns whatever info about the CPU, memory,
      disks and network interfaces is in the DB. The info comes from a variety of
        node_attributes, node_type_attributes, blockstores, blockstore_attributes,
        blockstore_type_attributes, and interfaces
      at last count.
      We will need to add some new node_type_attributes for cpu/memory.
      Even though some of the info exists already (e.g., "memory", "frequency"),
      I chose to use uniformly prefixed attributes (hw_cpu_*, hw_mem_*) to
      make my tmcd-life easier.
  18. 09 Apr, 2013 1 commit
  19. 29 Mar, 2013 1 commit