1. Roll Call  East to West

  2. Scribe for call

  3. Agenda Bash

  4. Itana Administration

  5. Cloud with Oren Sreebny (University of Chicago)


From the Adobe Connect attendee list (may not include people who only called in):


  • Scott Fullerton plans to REALLY retire and roll off ITANA … Scott was foundational to ITANA at its beginning and helped drive many ITANA initiatives, Face2Face meetings, and the Steering Committee

  • Next ITANA F2F will be at the EDUCAUSE national conference this Fall … this workshop could include continuing to work on deliverables from the Spring F2F

  • API management group remains active but has no news since the last general call

  • If you are interested in serving on the Itana Steering Committee, send an email to: The ITANA Steering Committee Discussion Listserv itana-steering@LISTSERV.EDUCAUSE.EDU


University of Michigan

  • Continuing to work with the MESA methodology

  • Made strategic goals and initiatives stronger

  • Working on annual review process

  • Initial work focused on individual org silos, and now the team is working on broadening this to classes of technology, regardless of org, for across-the-board technology

  • Room scheduling has come up as a good issue to work on cross-organizationally, to achieve shared goals across orgs that own technologies in different facilities; this will probably lead to a business case and RFP

  • Sometimes the subject of a MESA is a service or it could be a technology focus or anything that helps facilitate the right group of people

Oren Sreebny on Commoditizing Cloud Adoption (PDF of Oren’s talk)

  • Several institutions have worked together on cloud strategy producing some shared materials:

  • Six variables in cloud adoption

    • Payment for services

    • Security

    • Support

    • Administration

    • Infrastructure

    • Institutional responsibility

  • Within these variables you can range from sole end user control, to lots of control by the institution over how resources are utilized -- the continuum from “cloud anarchy” to “cloud fascism”

  • Examples:

    • “Cloud anarchy” examples are people purchasing e.g. Amazon services with personal or institutional credit card without visibility to university security, networking, etc.

    • “Moderate” examples typically have a university contract and the university accepts responsibility (fiscal, liability) by handing out accounts

    • Even more centralized examples may have central university help desk support; shared services in the cloud such as identity

    • “Cloud fascism” could include users being handed preconfigured template accounts without “root” type access, etc.

  • Different institutions will end up in different places on the continuum; and of course it may not be a single spectrum

  • Discussion from the group:

    • In addition to culture and context, is there a maturity progression on the continuum?

    • Other factors could include the type of cloud service (e.g., ERP vs. PaaS for research), and the leadership style/risk tolerance of the institution

    • It sounds like the cloud opportunities give people people a chance to challenge existing decisions about central vs. IT services; should this larger change in IT decision-making be raised higher in the institution as a change in control and risk?

    • Is this a topic Itana should take up?

    • Can different groups within an institution approach this in different modes -- for example, in a more ITIL/service-oriented/”slow” way and also in a more opportunistic/agile/”fast” way


From the Adobe Connect whiteboard:

See the PDF of Oren’s talk


From the Adobe Connect chat window:

Daniel Black - Miami Ohio: Bob & Dana: I private chatted y'all. :)

Dana, Bob and Daniel-Miami U: We are in Hoyt 309 if want to join us

Daniel Black - Miami Ohio: Armstrong. Excel help took longer than I anticipated.

Dana, Bob and Daniel-Miami U: I see.

Jim  Phelps: Hi All

Dana, Bob and Daniel-Miami U: Enjoy retirement Scott!

Dana, Bob and Daniel-Miami U: Anaheim

Scott Fullerton (Fullerton's Emporium of Stuff): Miami folks: thank you.  It has been a joy getting to know you and work with you.

Piet Niederhausen (UWash): The MESA method Michigan is using:

Chris Eagle (Michigan):   more up-to-date info is on our website:

Jim  Phelps: If you are interested in serving on the Itana Steering Committee, send an email to: The ITANA Steering Committee Discussion Listserv <itana-steering@LISTSERV.EDUCAUSE.EDU>

Jim  Phelps: Steering Committee info:

Piet Niederhausen (UWash): Internet2 Cloud Architecture wiki:

Scott Fullerton (Fullerton's Emporium of Stuff): Perhaps also: how do you plan an exit strategy.

Rupert Berk (UWash): pdf from Oren's talk:

Scott Fullerton (Fullerton's Emporium of Stuff): Does it vary across varieties of cloud service?  SAAS / PAAS?

Jim  Phelps: Jump in Aaron

Daniel Black - Miami Ohio: Those polls are aggressively positioned. :)

Piet Niederhausen (UWash): Oren, thanks for these great materials. I was wondering: Many institutions already have both central and distributed IT services, and these represent existing decisions (explicit or implicit) about control and risk. As you talk to institutions about cloud, to what extent do their cloud decisions map to those existing decisions, or are they referring to them at all, re-inventing the wheel, reaching different decisions?

Glenn Donaldson (OhioState): Ohio State is in the similar place for AWS

Jim  Phelps: One of the issues re: decisions is that people will go around decisions or they are acting in complete oblivion to the fact that a decision was made

Daniel Black - Miami Ohio: Jim, to that point, I've got How Universities Work sitting on my desk waiting for me.

Jim  Phelps: :-)  Daniel

Jim  Phelps: Other lenses on this work:  PACE Layers.  SaaS vs. PaaS vs. IaaS.   Core vs. Commodity

Jim  Phelps: Next Call:  Jun  3 - Facilitating Strategic Thinking - Gabriela Redwine, Digital Archivist and Louis King, Enterprise Architect

  • No labels