1. 29 Apr, 2014 1 commit
  2. 24 Apr, 2014 1 commit
  3. 22 Apr, 2014 3 commits
  4. 17 Apr, 2014 6 commits
  5. 15 Apr, 2014 1 commit
  6. 10 Apr, 2014 1 commit
  7. 09 Apr, 2014 2 commits
  8. 07 Apr, 2014 4 commits
  9. 03 Apr, 2014 2 commits
  10. 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
  11. 20 Mar, 2014 1 commit
  12. 19 Mar, 2014 1 commit
  13. 13 Mar, 2014 2 commits
  14. 07 Mar, 2014 5 commits
  15. 06 Mar, 2014 2 commits
  16. 05 Mar, 2014 1 commit
  17. 03 Mar, 2014 1 commit
  18. 27 Feb, 2014 2 commits