Work out what fields and properties we need on servers

Hostmaster 6.x-1.x has the concept of a server, with some associated fields in the DB, we should work out what they are, and then work out if they should be properties or fields on the entities, and then we should work out which modules they should live in.

Currently 6.x-1.x stores the following about each server:

• Server hostname (Node title).
  
  The host name of the server. This is the address that will be used by Hostmaster to connect to the server to issue commands.
• IP addresses (hosting_ip_addresses db table).
  
  A list of IP addresses this server is publicly available under.
• Context name: (hosting_context db table)
  
  This is the backend context name for the frontend object.
• Services (hosting_service db table).
  
  This stores the available services on each server, as well as options for each service.

Proposed structure for D7

• Front end name.
  
  Field.
  
  We should decouple the hostname from the name displayed in the frontend UI, essentially making this field just be a text field in which you can pop tokens, and we default to the Server hostname.
• Server hostname.
  
  Field.
  
  This should just be a simple text field.
• IP addresses.
  
  Field.
  
  This should be a multi-valued text field with some validation to validate addresses are IPv4 or IPv6.
• Context name.
  
  Field.
  
  This should be a global field shared by all objects that need representation in the backend, we should be able to specify that server context names start with ‘server’. This should not be editable by end users, but should get its value from a token maybe?
• Services.
  
  Field.
  
  Should this be a reference, or some other magic? Not sure about this one. The main thing is that we want to store what services a server provides, there may be options for the different services and we need to able to get, for example, all servers that provide a certain service.