Skip to end of metadata
Go to start of metadata

Condos

Many of the Shared Computing Resources we operate will have more processor cores online than are actually available to all users in the commons.  These extra processor cores are typically part of a private/group Research Condo.  Partners that choose to invest in a condo executes a memorandum of understanding (MOU) that stipulates operational parameters, and agree to the following basic terms:

  • Partner will pay published condo discounted user fees (User Fees) that cover the cost of infrastructure that Partner’s condo leverage but has not paid for. Shared infrastructure leveraged but not paid for by Partner condo acquisition includes but are not limited to:
    • Research computing networking and interconnect infrastructure.
    • Research computing lights out management infrastructure.
    • Research computing homes and project storage infrastructure (subject to quota limits).
    • Research computing shared fast scratch storage infrastructure.
    • Research computing shared software licenses.
    • Service contracts on above listed infrastructure and services.
  • Partner will let the Center for Research Computing integrate condo into Rice’s shared research computing infrastructure.
  • Partner will let the Center for Research Computing supports and manage the hardware for the term of the agreement.
  • Partner permits the Center for Research computing to scavenge CPU cycles using a 4-hour non-preemptive “queue”.
  • Partner can request queue configuration (implemented as a separate queue or as a quality of service) for resources in the private condo. o Partner will work with Center for Research Computing to specify the desired queuing parameters.
  • User Fees

Partner Responsibilities

  • Execute MOU
  • Provide funding for Condo procurement.
  • Define queue characteristics of any resources Partner opt to assign to a dedicated queue and approve users that should have access to Condo.
  • License discipline-specific software as needed (Condo will automatically have access to software that is already part of the shared research competing at Rice).
  • Direct requests for user accounts to: Apply.
  • Provide timely reports for problems related to Condo to CRC using helpdesk@rice.edu.
  • Monitor email announcements from CRC and routinely check http://oit.rice.edu for IT Alerts regarding maintenance schedules and changes that may affect the operation of Partner’s Condo.

CRC Responsibilities

  • Work with Partner to specify hardware and obtain quotes from vendors.
  • Coordinate placing Condo orders in a timely manner.
  • Facilitate rack space, power, cooling and networking.
  • Configure job submission queues and create user accounts.
  • Provide system administration and maintain hardware and supported software stack.
  • Provide a base software stack including compilers, operating system software, and some applications and libraries, not to exceed limits provided in our current licensing agreements with vendors.
  • Install and provide best-effort support for commercial and public-domain packages and libraries beyond the base software stack. Additional applications will be provided by the faculty partner and installed in accordance with licensing agreements. However, primary responsibility for support of discipline-specific application software will remain with the research team.
  • Provide facilities status via IT Alerts at http://oit.rice.edu and send e-mail to mailing lists maintained by CRC for all Partners and users.
  • Notify Partners annually of Condo anniversary helping prepare for end-of-life and Condo decommissioning.
  • Provide usage reports to Partners on request.
  • Provide technical support as needed by responding to requests submitted to helpdesk@rice.edu
  • Infrastructure will be operated for at most five (5) years.

To inquire about the purchase of a Condo for your research group please contact Erik Engquist, Director, Center for Research Computing.

  • No labels