1. 15 Apr, 2014 1 commit
  2. 10 Apr, 2014 1 commit
  3. 09 Apr, 2014 2 commits
  4. 07 Apr, 2014 4 commits
  5. 03 Apr, 2014 2 commits
  6. 02 Apr, 2014 4 commits
    • Jose A. Lopes's avatar
      Add metadata daemon server entry point · acc1eb23
      Jose A. Lopes authored
      ... which starts the configuration and web servers.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      acc1eb23
    • Jose A. Lopes's avatar
      Add metadata daemon configuration server · f007e290
      Jose A. Lopes authored
      The configuration server listens on a Unix socket for connections from
      the node daemon.  The node daemon sends the instance parameters to the
      configuration server so they can be served through the metadata daemon
      web server to the instances which have the communication mechanism
      enabled.
      
      The configuration server reads the instance parameters and, currently,
      it extracts the instance's name and the instance's IP address on the
      instance communication NIC.  The instance's name is used for logging
      and the IP address is used to index the instance parameters, given
      that instances do not authenticate with the metadata daemon, and the
      only thing we know about them is their IP address.
      
      The configuration server also extracts the OS parameters, including
      public, private and secret, and creates an object containing those
      parameters and their visibility.
      
      The configuration is kept internally in an 'MVar' which will be shared
      with the metadata daemon web server.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      f007e290
    • Jose A. Lopes's avatar
      Add metadata daemon types · 80929ecb
      Jose A. Lopes authored
      The metadata daemon will be responsible for receiving the instance
      parameters from the node daemon and keeping them in memory.  The type
      of the instance parameters in defined in a separate module because it
      will be shared between the web server and the configuration server.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      80929ecb
    • Jose A. Lopes's avatar
      Move metadata daemon to its own directory · 57ccc712
      Jose A. Lopes authored
      Currently, the metadata daemon is mainly a web server.  However, a new
      configuration server will be introduced along with other metadata
      related modules.  Therefore, this patch moves the current metadata
      daemon web server to its own directory.  This module is also renamed
      from 'Server' to 'WebServer'.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      57ccc712
  7. 20 Mar, 2014 1 commit
  8. 19 Mar, 2014 1 commit
  9. 13 Mar, 2014 2 commits
  10. 07 Mar, 2014 5 commits
  11. 06 Mar, 2014 2 commits
  12. 05 Mar, 2014 1 commit
  13. 03 Mar, 2014 1 commit
  14. 27 Feb, 2014 2 commits
  15. 26 Feb, 2014 6 commits
  16. 25 Feb, 2014 2 commits
  17. 24 Feb, 2014 3 commits
    • Petr Pudlak's avatar
      Show Haskell dependencies when compiling · f0ac917e
      Petr Pudlak authored
      Instead of showing the long GHC command line, show which file is being
      compiled and what its dependencies are. This gives more meaningful
      information to developers.
      Signed-off-by: default avatarPetr Pudlak <pudlak@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      f0ac917e
    • Petr Pudlak's avatar
      Compile every Haskell object file separately · 9b6d2d92
      Petr Pudlak authored
      This allows parallel compilation of all targets, including the Haskell
      object files. While re-starting GHC for every Haskell source almost
      doubles the total CPU time, allowing it run in parallel at the end cuts
      down the wall-clock time to half.
      
      Haskell targets are split into two: main ones and testing ones.
      The testing targets (starting with "test/") are build with coverage
      automatically. Therefore the testing object and interface files have
      different extensions (this also allows their parallel compilation).
      
      GHC is now used to produce a separate Makefile.ghc with all
      dependencies. This is then included and used for compiling each object
      file separately.
      
      Note that the inclusion + generation of Makefile.ghc is turned off when
      calling clean/ganeti/distclean. For some reason, Makefile infinitely
      recurses when calling "make ganeti", if it includes Makefile.ghc. But
      since using ifneq/endif in Makefile.am conflicts with Automake, it was
      necessary to put the snippet into an Automake variable and substitute it
      into the resulting Makefile.
      Signed-off-by: default avatarPetr Pudlak <pudlak@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      9b6d2d92
    • Petr Pudlak's avatar
      Fix the generation of ListConstants with VPATH · 06929681
      Petr Pudlak authored
      When the build directory differs from the source directory, the
      automatic variable '$<' points to the file found by prepending the path.
      This causes double '../' to be inserted when combined with
      '$(abs_top_srcdir)'. This patch fixes this.
      Signed-off-by: default avatarPetr Pudlak <pudlak@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      06929681