Skip to end of metadata
Go to start of metadata

Subject: 2010/01/06 Weekly operations meeting

Agenda:

  • Purchasing of immediately requested items (document to be circulated by John 'shortly')
  • Recap of recently requested activities (describe and estimate scope)
  • [Matt] iRODS prototype support
  • [John] Blogging for John Orcutt with Drupal
  • Iteration 2 activities
  • Process discussion (do we want to allow new tasks to be added to the 'baseline'?)
  • Review of activities (a visit to Jira to confirm we're all on that page)
  • Prioritizing Sys Admin activities
  • Other Issues/Matt's Issues

Notes:

Purchasing of immediately requested items

  • document circulated by John just before meeting

Conclusions:

  • can't buy software that is 'shared', it must be be fully owned by OOI
  • OK if it gets used also by someone else, but it needs to be able to 'leave' with OOI
  • need list of common elements on every host
  • need list of host types (management, developer, ... )
  • this is just a low-cost testing solution, not the first version of the long-term configuration
  • need to focus on OOI CI grant as the sole world, we're just hosted here – separate concerns
  • OK to buy 1, 2, 3, and 5
  • what does Cirrus provide? version control of switch configuration, highlighting of changes
  • need to investigate OOI policy for us to spend spot maintenance for items on share infrastructure

Recap of recently requested activities (describe and estimate scope)

[Matt] iRODS prototype support

  • do we have access to suport this? enough disk space? not sure, let's look at it
  • how much space is in (a) actual images, (b) running images, (c) ghost images, (d) data
  • how much can we get for the time being, that we could use for 4 weeks?
  • may want to open up access for this in the next 5 days
    [John] Blogging for John Orcutt with Drupal
  • want the domain name to be carefully selected

Iteration 2 activities

  • Process discussion (do we want to allow new tasks to be added to the 'baseline'?)
  • Review of activities (a visit to Jira to confirm we're all on that page)
  • Prioritizing Sys Admin activities
  • Password enforcement policy (writing confluence plugin, this also
    needs to be discussed)
  • Test and help implement time and expense reporting system
  • Evaluate and upgrade collaboration tools
  • Blogging service
  • Set up availability (outage) notifications for all operational systems
  • Evaluate automated recovery operations when operating on the cloud.
  • Evaluate mail services operations when operating on the cloud.
  • Provide developers controlled access to EC2
  • Design cloud-based developer testing platform.
  • Design cloud-based deployment staging platform.
  • Discuss CT startup procedures with Ocean Leadership

Other Issues/Matt's Issues

Review of Practices
Was this process for purchasing useful?

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.