Source

Access

Go to https://source.it.cahnrs.wsu.edu

Description

The Source service will be implemented using a software package named gitlab. This product allows for collaboration between multiple contributors on code repositories. Additionally it provides a web interface to make interacting with git more enjoyable. Finally, there are integrations with this service that will allow us to utilize the WSU Active Directory infrastructure.

Availability

  • This is an internally consumed service of the CIT group.

Life cycle

  • OS Patching - This server will be included in the monthly patching cycle performed by the CIT Server Team.
  • Application patching - The patching of this service will be integrated with the OS patching cycle due to integration with the YUM package manager. If there is need for an out of band upgrade that can be requested through the change request process.
  • If the production VM environment is deprecated this service will be archived to Cloud for possible future retrieval.
  • If this service is determined to not be of use any more the repositories will be archived independently to Cloud for future retrieval.
  • The usage of this service should be re-evaluated every two years. (July 2018)

Dependencies

  • This service is dependent on:
    • Production VM infrastructure
    • Central ITS AD infrastructure
    • Central ITS Network infrastructure
  • Services dependent on this service:

Workflows

All service and change requests for this service should come in via the ticketing system or be handled by staff while being noted in the ticketing system.

Service requests

Adding a new user

  • Due to the internal nature this workflow is expected to be completed by the end user
  • Log into a Tier 1 console and activate the OU Administration role.
  • Navigate to the object "CN=Source Authorized Users,OU=Accounts,OU=Lava,OU=Source Control,OU=Services,OU=IT,OU=CAHNRS,OU=WSU,DC=ad,DC=wsu,DC=edu"
  • Add the new user to this group and save the change
  • The user should be able to log in.

Change requests

Out of cycle upgrade

  • Create a ticket in with a brief justification on why we should update out of cycle (i.e. new feature, or major security fix).

Uptime

  • This service will be available during extended business hours (M-F 7AM - 6PM).

Maintenance

Announcements

  • Any maintenance will be coordinated within the CIT group during normal business meetings

Outage policy

  • If there is an outage of this service the user base will be notified verbally
  • I will yell down the hall every hour to update everyone.

SLA

  • Service requests: 8 normal business hours
  • Change requests: Responded to with estimate within 16 hours
  • Service survivability and recovery
    • Service survivability
      • This service is provided from the Hulbert facility on the Pullman Campus. If there is any problem with the network, building, or campus this service will be disrupted.
    • Service Recovery
      • We will recover the repositories and move them to another provider.
  • How will this service be monitored
    • We will perform basic up/down monitoring using Uptime robot on 22, 80, 443.

Data access policy

  • CIT has the right to review any data contained in this service without notification.

Data stewardship

  • Back up
    • We will utilize the cloud data storage offering to back up data for the service. This will be implemented in the underlying OS
  • Retention
    • We will keep daily backups for a week and then weekly backups for a month.
  • Survivability
    • We will utilize the inherent syncing in the cloud service to move the data to our off-site location.

Appropriate use policy

  • This service is meant to be used according to standard best practices.

Budget

  • TCA
    • Implementation:
      24 hours - Server setup, application deployment, AD integration, Setup of backups
    • Running costs:
      1 hour/month - Application and OS updates
      48 hours/2 years - Reimplementation and migration to new OS.
    • De-provisioning:
      24 hours - Export data and make available on Cloud.
  • Recovery
    • This service is expected to be consumed on an internal basis and as such is not subject to cost recovery.

Related