[Blueprint server-o-ubuntu-orchestra-server] Ubuntu Orchestra Meta-Package

[Robbie Williamson]

Blueprint changed by Robbie Williamson:

Whiteboard changed:
- 
  Work Items:
  ubuntu-orchestra-server MIR: TODO
  manpage: TODO
  wiki page: TODO
  
  
  === SESSION NOTES ===
  Ubuntu Orchestra Server
  A collection of the best free software services useful in hosting enterprise data center infrastructure services, based on the Ubuntu Server
  
  https://launchpad.net/orchestra
  bzr lp:orchestra
  ppa:orchestra/ppa
  
  Provisioning Server ( Cobbler, PXE, tftp, ... )
  
  Caching/Proxy/Mirroring ( squid-deb-proxy, debmirror )
  
  Management ( puppet, ensemble?, chef?, etc. )
  
  Orchestration ( mcollective, ... )
  `
  Monitoring ( rsyslog, collectd, nagios? )
  
  Power Management ( powernap, IPMI?, fence-agents, NUT )
   - PowerNap Server, overtime, should handle IPMI/UPS/etc. Up for discussion in PowerNap session.
   - fence-agents
   - IPMI integrates full power-down, beyond WOL, CPU Idle, etc.
   - Network UPS Tools (NUT) already handles UPS and PDU natively, and IPMI/ALOM/ILO through  PowerMan
  
  *Remote Web UI ( Landscape? )
  
  = Requests / Other items =
   * request from Spads in IRC for gpxe support in cobbler
       * Swapping out tftp for http allows you greater debugging and control in your autoinstall behaviors.
       * Many problems reduced to "write a web app"
   * smoser thinks that cloud-init might need some changes that make it more consumable here.  Some of the upstart jobs that it does to make it run "really early" might cause issues with networking being less reliable or predictable. this is really just a warning / admission that there might be issues.  i *do* think that there needs to be one single thing that does initial first boot installation.
    * It might be useful to allow at the cobbler (or provisioning level) user-data that then would get to cloud-init.
    * somewhat obvious thought... would potentially be nice if there was an ec2-like api cobbler/orchestra
   * cloud-init should be treated as the "configuration management bootloader", i.e., the gateway to being managed by puppet/chef/ensemble/rightscale/etc
   * initial pxe boot image on the network should be a "collect data and report it" image.  Then, when a new system is plugged into the network it will boot that image, and report back its mac and cpu/meminfo/disk...
  
  == Actions ==
  - pre-execution environment ( boot, collect data about system, report to cobbler )
  - discovery step
  - hardware configuration

-- 
Ubuntu Orchestra Meta-Package
https://blueprints.launchpad.net/ubuntu/+spec/server-o-ubuntu-orchestra-server