CloudInfrastructure

Revision 10 as of 2010-10-27 18:35:19

Clear message

This page is here to collect together proceedings from sessions as part of the 'Cloud Infrastructure' track at the Natty UDS in Orlando, Florida.

Please add proceedings by doing the following:

  • Add a new section with the name of the session.
  • Add the outcomes of the session as a collection of bullet points. The goal of the proceedings is to really focus on decided outcomes, so please try to keep them crisp.

Thanks!

Proceedings

Bootstrap puppet from deployment service (for UEC and more)

cloud-server-n-install-bootstrap-puppet

  • write cron job to pool installation service DB for expected agent requests.
  • upstream to support csr extensions (ie puppet token) for puppet agent.
  • extend puppet ca to validate csr extensions (ie puppet token).
  • extend installation service to include puppet token in installation procedure.

Eucalyptus next steps

natty commitments:

  • ebs root
  • disable api termination
  • instance initiated shutdown behaviory
  • import keypair
  • some user management similar to Identity Access Management
    • improved command line tools for create delete ...
  • tagging (not yet commiting to full aws tagging support)
  • snapshot sharing (user sharing snapshots, not instances)
  • default instance types
    • knowledge of m1.2xlarge ...
    • ephemeral devices for ephemeral1..4
  • CreateImage

  • loader support - up to eucalyptus from ubuntu Ubuntu / Eucalyptus TODOs for natty cycle
  • review of legacy operating systems and virtio disk/network support
  • review of ubuntu patches
  • review of java dependencies
  • euca2ools 2.0 / boto updates (without this most of features above are not exposed)
  • Eucalyptus / Ubuntu to collaborate / share test suitesthank
  • somehow need to get to gwt 2.1 (or 2.0)

How can Ubuntu use awstrial

Improvements to the Ubuntu Cloud Images

cloud-server-n-cloud-images

  • Scott will document how to seed cloud-init from kernel command line
  • Scott and John will get ubuntu cluster compute types to EC2 during Natty Cycle
  • image root fs size for natty resized to 10G

Installation service for physical nodes deployments (UEC and more)

cloud-server-n-install-service

  • Overall architecture outlined.
  • 4 potential projects identified:
    • - fai - cobbler - openqrm - lp:uec-provisioning.
  • More discussion required to gather additional requirements.

On-going maintainance with puppet (for UEC and more)

cloud-server-n-config-mgmt-with-puppet

  • deploy puppet master along installation service.
  • package mcollective to get scalable distributed command infrastructure (eg trigger puppet runs).
  • write puppet modules to configure UEC components (CLC, CC, NC).
    • available in /etc/puppet/modules/.
  • link puppet master to installation service via external_nodes to get classes assigned to each system.
  • tie installation service to puppet master to gather list of available classes.

Openstack packaging

  • Meta packaging to ensure toolkit approach
    • nova-*-mysql, -sqlite, and (pre?)-depend on sane defaults.
  • Packaging branch to be moved to a new team, and Ubuntu ultimately owns the packages.
  • Commits under-go merge proposals for peer review.
  • Upstartify
  • Apport hook
  • Monitoring scripts (collectd / munin)
  • Release cycle alignment
    • Natty freezes February 24; releases April 28.
    • Branch Nova code by Ubuntu feature freeze (Feb 24), backport fixes until FinalFreeze (Apr 14)

  • Current state of Nova and Swift packaging: it works. It's in pretty good shape. NASA is using it.

Components of OpenStack NOVA:

  • Compute
  • API
  • Volume
  • objectstore (simple implementation of S3; it may go away and be replaced by Swift)
  • instancemonitor (monitors loads put on server by virtual machines and graphs them, storing them in the objectstore)
  • scheduler
  • network
  • python-nova
  • nova-common
  • There is no packaging dependency on rabbitmq-server, but there is a runtime dependency. For a DB, sqlite, postgress or mysql will work. Rick considers which DB is packaged and configured to be a Ubuntu decision.
  • SWIFT has a different set of components.
  • Dave: Current default -- sqlite; could we consider mysql?
  • Soren: Wants to make sure install is no-questions; sqlite was "dead simple"
  • Packaging targets single-node use case
  • More complex deployments should be handled through the install service

Issues to handle off line:

  • How to package the databases, authentication packages
  • precede-ability

Rebundling and other cloud utilities

UEC EC2 compatibility

  • Testing framework to ensure EC2 Compatibility
    • - Possibly use txAWS.

Monitoring probes and alerting service (for UEC and more)

cloud-server-n-monitoring-alerting

Actions:

  • move collectd to main.
  • should munin go to universe (probably not yet)
  • find a graphing solution (munin, graphite, reckonater (omniti - not packaged, visage).

Web scale enhancements

Hadoop packaging

Ubuntu desktop cloud images

Handle virtual networking in the cloud

Openstack gap analysis