Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Mission: Facilitate

Campus’

Cornell's transition to the cloud while encouraging modern

devops

DevOps practices.

Guiding Principles

  • Sharers - We don’t keep information to ourselves. We always think about how a system, process, etc. needs to be run without us involved.
  • Systems Thinkers - We think about how the entire system is created, not just the infrastructure, not just the application code, not just the configuration, not just the database. Everything. We look at optimizing the whole system, not just sub-optimizing a part of the system.
  • Automation - We constantly seek ways to automate repetitive activities. We also realize that automation can lead to more than just tactical improvements. When applying systems thinking to problems, we seek to create automation systems for the entire software systems lifecycle versus a series of scripts and tactical improvements
  • Collaborative and Encouraging - The goal is to create a peer network of high performance collaborative system teams that inter-work and cause the environments to ever improve, while creating positive, fun work interactions that foster excellence.
  • Humble - Realize there is more than one way to do something. You can be right without being a jerk about it or “You can disagree without being disagreeable”
  • Continuous everything - We think that everything in a software system can run through a continuous process.
  • Continuous Improvement - We are curious and are constantly learning. We constantly tweak processes, systems, software to improve
  • Continuous feedback - The quicker people get useful feedback, the better. We’re seeking to reduce process times and wait times so that they get feedback quicker.
  • User Experience - We focus on user experience: we think about where coworkers, stakeholders, customers, etc. are coming from and this guides many other traits.
  • Self-Service - We seek to make all systems we create self-service for our customers.
  • Root-cause analysis - We are constantly seeking the root cause of problems rather than just the symptoms

Space contributors

Contributors
modelist
scopedescendants
limit5
showLastTimetrue
orderupdate



Panel
titleColor#ffffff
titleBGColor#b31b1b
titleCornell Cloud Questions?
  1. If you are a Cornell staff/faculty/student, login to Confluence to get access to pages that are private to Cornell.
  2. Search this wiki for answers. Use the side bar search → → →
  3. Send your question to cloud-support@cornell.edu
  4. Connect with cloud practitioners. See Connecting with the CIT Cloud Team and Cornell's Cloud Community
  5. Request support


Panel
titleFeatured Info

Content by Label
showLabelsfalse
max24
showSpacefalse
excerpttrue
excerptTypesimple
cqllabel = "highlight"


Panel
titlePublic Topics

Children Display
depth1
pagePublic
sorttitle




Panel
titleSearch within Cloud Support
Panel
titleSearch within Cloudification Space

Livesearch
spaceKeycloud
id1

Recent space activity


Panel
titleLogin Links

Button Hyperlink
titleAWS Web Console - Traditional
typeprimary
urlhttps://signin.aws.cucloud.net/

Button Hyperlink
titleAWS Web Console - AWS SSO
typeprimary
urlhttps://cornell-sso.awsapps.com/start

Button Hyperlink
titleAzure Portal
typeprimary
urlhttps://portal.azure.com

Button Hyperlink
titleCloudCheckr - SSO
typeprimary
urlhttps://shibidp.cit.cornell.edu/idp/profile/SAML2/Unsolicited/SSO?providerId=https://auth-us.cloudcheckr.com/auth&target=https://app-us.cloudcheckr.com/


Recently Updated
typespage, comment, blogpost
max5hideHeadingtrue10
themesocial

 

concise