Our goal is that the Cloud Resource Center (CRC) will become a focal point for an evolving cloud community of practice where campus can share questions, answers, resources, and activities. We extend our thanks to the team who is helping to bring the CRC together: Marlita Kahn in IST-API, Gabriel Gonzalez, the CTO for the Law School, and Rita Rosenthal from OCIO Communications. Their hard work and dedication has made the CRC what it is today!
Here are some ways you can get involved.
- Join the listserve and post to it: firstname.lastname@example.org.
- Attend communities of practice meet-ups:
- IaaS Discussion Group - an informal workgroup to share information about things that are already happening in the world of IaaS, and to try and coordinate the IST related, enterprise wide efforts in that direction. Contact Walter Stokes (email@example.com) if you are interested.
- Research IT Cloud Working Group
- Suggest articles, resources, case studies and activities for the community. Send info to firstname.lastname@example.org and join here.
- Request a targeted discussion. Are you interested in exploring the world of the Public Cloud and just don’t know where to start? Are you interested in leveraging what others have learned? Are you interested in migrating under the UC Wide agreement, in order to achieve a data egress waiver, as well as potentially qualify for volume discounts related to reserved instances? We would love to help facilitate this kind of discussion. Send a request to email@example.com.
As part of the Reimagining IT planning project, the Cloud Strategy Working Group delivered a Cloud Strategy and recommended next steps for campus. The Cloud Strategy was developed primarily by campus CTO William Allison with input from the working group and broad campus input. After extensive review and refinement the strategy was formally adopted.
The UC Berkeley Cloud strategy directs our focus to be University First. We will invest in technology that meets the needs of the campus mission for our faculty, students, and administration -- rather than focusing on technology first. For example, in a meeting of Deans, the discussion should not be driven by a question like "What should we do with cloud computing?" the conversation should be asking "How can we accelerate the pace of our research and tackle problems that today seem impossible?" An administrator seeking to automate the management of a business process should ask: "How can we transform a function (such as student advising, enrollment, travel reimbursement) to make everyone's experience better, faster, and cheaper?" Rather than ask how they can move their workloads to the cloud.
That said, the reason so many institutions have adopted the industry-driven Cloud First strategy, is because it's easy, and if done right, directionally correct. The reality is that when considering a technical solution, the institution should always explore whether a Cloud solution (especially SaaS), makes sense, and adopt cloud solutions where possible and financially sensible given the multi-year trajectory of the IT services market shift to cloud delivery. It is a strategic consideration to avoid being saddled with what will be expensive disjointed legacy technologies down the road. You can become more familiar with the strategy and get a high level view of background, strategy and rationale in UC Berkeley’s Future-Looking Cloud Strategy (PDF).