RESEARCH AND EDUCATIONAL TECHNOLOGY COMMITTEE MEETING AGENDA Thursday, April 18, :00-9:15 a.m. FAC 228D

Size: px
Start display at page:

Download "RESEARCH AND EDUCATIONAL TECHNOLOGY COMMITTEE MEETING AGENDA Thursday, April 18, 2013 8:00-9:15 a.m. FAC 228D"

Transcription

1 RESEARCH AND EDUCATIONAL TECHNOLOGY COMMITTEE MEETING AGENDA Thursday, April 18, :00-9:15 a.m. FAC 228D I. LIFT Recipients Present a. APPSOMA (Pei Chen, Zach Booth-Simpson, Scott Hunicke-Smith) b. TXPolitics (James Henson, Joe TenBarge) II. Box Update (Cam Beasley, Brad Englert)

2 Appsoma Zack Booth Simpson Fellow, Center for Systems and Synthetic Biology University of Texas at Austin

3 The Problem It is extremely difficult and time consuming to......maintain development environments...port them to other servers...reproduce results from others...scale the operation to many servers...setup non-developer's machines

4 appsoma.austin.utexas.edu Two audiences: Developers: Novice to intermediate programmers who are not professional software engineers. End-users: People who run apps made by developers (probably technical but not coders).

5 End-user view End-users see "Apps" They run the apps on one or more machines They can leave a job and reconnect at will The apps will typically have some web-based user-interface such as a form

6 End-user view End-users see "Apps" They run the apps on one or more machines The apps will typically have some web-based user-interface such as a form They can leave a job and reconnect at will

7 Developer's view Code is stored on centralized server (like Google docs) Default to read by anyone, writable by friends to promote collaboration and sharing (more specific permissions if needed) Simple, automatically version control

8 Language agnostic Currently supporting: Python Perl Ruby R Bash Javascript IPython Notebook Easy to add more

9 Architecture

10 Execute Servers Code is always run remotely on a "execute servers" Execute servers install easily Meant to be placed near data "move code, not data" Sandboxes can have limits (disk space, bandwidth, etc) Shell access at a single click (no need for SSH)

11 "State Independent of View" Go to work Login into Appsoma Start a job on execute server Don't even bother to shut down browser Go home Login to Appsoma Your job appears instantly and is up to date Having more than one browser looking at the same job simultaneously is fine!

12 Stateful HTML UI Programming on the web is very hard because HTTP is stateless Appsoma allows you to have stateful HTML UI. More like print() / getch() a_form = '''<form>... </form>''' while True: send_html( a_form ) reply = await_reply() if reply['error']: send_html( "You have an error", "#error" ) else: break SO MUCH EASIER!

13 Scaling Appsoma implements a cluster manager that will... Boot servers on demand Automatically connect to them Monitor state on many nodes Package up the results Stdout of each node monitored in real-time All results in the "results" folder are packaged

14 Box Common Good Proposal James Lewis Executive Summary Box is a cloud-hosted file service recommended by the AIC as a replacement for many existing file services used by the university. 25GB of Box storage is proposed as a Common Good for every faculty and staff member, for individual use. Units are expected to fund additional storage for group-based use (collaborative research labs, administrative staff groups, etc). 5-year total costs with reallocations of existing services are projected to be $600K $330K of which is expected to be funded by units. (Without reallocations and unit funding, the 5-year total costs are $1.1M.) Benefits to Campus Box has distinct benefits over existing campus file services: Sync: provides the ability to sync folders between multiple devices (computers, mobile, web) Access: provides Mac & Window client integration, ios/android apps, & web access Collaboration: provides an easy means to interact with both internal & external users Ease of Use: Access to Box does not require additional actions by users once the client is installed. Other current campus offerings require configuring a VPN client or IPSEC, which increase complexity and are barriers to users. Integration: provides integration with several popular cloud-based services such as Google Docs, Evernote, and Confluence. It also provides applications or works with third-party applications that allow for editing of a variety of documents (including Microsoft Office, AutoCAD, and others) from mobile devices. Security: unlike most other cloud-hosted file service offerings, is ISO approved for Category I data (in most usage cases). Dropbox, a similar service that many faculty and staff are already using, does not meet these requirements. Demand: widespread from faculty and staff for a collaborative, cloud-based file storage solution. Comparison of Available Campus File Storage Services to Box Webspace: an ITS service that allows access to an individual file share via web browser or Mac/Windows/Linux operating systems, as well as allowing for web publishing. It is expected that Box would completely replace the file-sharing component of Webspace. Users who are publishing web content from their Webspace accounts would require migration to alternate web publishing services available from ITS or individual departments. Users of Green Printing on Webspace would require migration to Austin Disk. Austin Disk: an ITS service that allows access to a file share via Mac/Windows operating systems. A substantial portion of existing Austin Disk users are anticipated to migrate to Box. Present usage of Austin Disk is 45 TB of 60 TB available; the top 6 non-its departmental users of the service currently use 27 TB these users have indicated their intention of moving to Box. UT-EBS: an ITS service that allows units to purchase large amounts of back-end data storage for departmental usage. EBS requires that individual departments provide their own front-end file server. Typically, UT-EBS is not used for general user file storage, as such, Box is not expected to have a significant impact on UT-EBS. 1

15 Box Common Good Proposal James Lewis Departmental File Servers: Many departments provide their own file services to their users. Cost, security, and means of access vary greatly, depending on the individual unit choices. A significant quantity of file storage currently on existing departmental file servers is anticipated to migrate to Box. Several large units, including McCombs, Education, and Liberal Arts intend on deprecating substantial portions of their existing file services once their users are migrated to Box. Impact on Existing Services Box is expected to have a large impact on existing file services provided by ITS and individual units. It is anticipated that the resources allocated to Webspace, can be reallocated to Box. Number of Users Box has been approved for usage by faculty and staff, and the vendor has been engaged to meet accessibility requirements in order to make it available to the student population. It is estimated that 50% of faculty/staff (12,000 users), and 10% of the student population (5,000 users) would ultimately take advantage of Box. Note that students have access to Google Drive, and their usage of Box would only be promoted for collaboration with faculty/research. Resource Requirements This proposal recommends that the Box service be managed by ITS. The primary resource required from Box is dedicated staff; no hardware and minimal software is required. Specific staffing requirements are indicated in the cost projection spreadsheet. Funding Requirements See attached cost projections. 2

16 Box Cost Projections James Lewis $ $ $ $ $17 Total Projected5Participants pilot fac/staff everyone everyone everyone Faculty/Staff , , , , ,000 Students ; ; , , ,000 Total , , , , ,000 Storage Box* Common6Good6(Individual6Storage)** $ ; $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 Departmental6(Dept/Research/Group6Storage) $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 Subtotal $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 Webspace Reallocation6of6Webspace6Storage6Expense $ ; $ ; $ (90,000) $ (90,000) $ (90,000) $ (270,000) Reallocation6of6Xythos6Software6Expense $ (30,000) $ (30,000) $ (30,000) $ (90,000) Subtotal $ ; $ ; $ (120,000) $ (120,000) $ (120,000) $ (360,000) Total6Storage6Costs $ ,000 $ ,000 $ (20,000) $ ,000 $ ,000 $ ,000 Support ITS6Support6Personnel ITS6;6Project/Service6Manager6(.336FTE6ramp;up,6.26FTE6steady6state) $ ,900 $ ,930 $ ,060 $ ,060 $ ,060 $ ,009 ITS6;6User6Services6(.56FTE) $ ,900 $ ,800 $ ,800 $ ,800 $ ,800 $ ,100 ITS6;6Applications6(.336FTE6ramp;up,6.16FTE6steady6state) $ ,900 $ ,415 $ ,030 $ ,030 $ ,030 $ ,404 Subtotal $ ,699 $ ,144 $ ,890 $ ,890 $ ,890 $ ,513 Reallocation6of6Existing6ITS6Support6Personnel Webspace6Administrator $ ; $ ; $ ; $ (50,000) $ (50,000) $ (100,000) Subtotal $ ; $ ; $ ; $ (50,000) $ (50,000) $ (100,000) Total6Support6Costs $ ,699 $ ,144 $ ,890 $ ,890 $ ,890 $ ,513 Network5Bandwidth Bandwidth6(Box) $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 Total6Bandwidth6Costs $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 Total6Costs6(no6Reallocations) $ ,699 $ ,144 $ ,890 $ ,890 $ ,890 $ ,061,513 Total6Reallocations $ ; $ ; $ (120,000) $ (170,000) $ (170,000) $ (460,000) TOTAL $ ,699 $ ,144 $ ,890 $ ,890 $ ,890 $ ,513 ITS6COMMON6GOOD6FUNDING $ ,699 $ ,144 $ ,890 $ ,890 $ ,890 $ ,513 DEPARTMENTAL6FUNDING $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 $ ,000 *Assumes6continued6Internet26participation,6expected6purchase6commitment6to6vendor6is6$50K6in62013,6increasing6in6$50K6increments6each6year. **6Based6on656GB6average6storage6used6of6the6256GB6allocated6per6individual

17 File Storage Options James Lewis Service Cost/GB/Yr CAT11 Audience Capacity Webspace $2.00,(Common,Good) no faculty,,staff,, students Austin,Disk,'personal' $2.80, yes,,but,no, ITAR Austin,Disk,'departmental' $2.80, yes,,but,no, ITAR faculty,,staff,, students home,directory,, 1GB,,no, expansion. EID1 Authentication Protection Retention/Restores Add?ons yes 99% 6,weeks,retention,,restores, thru,its up,to,10gb yes 99.99%,,data,center, failover,,data,replication. Departments Up,to,1TB yes 99.99%,,data,center, failover,,data,replication. selfprecovery.,,daily, snapshots. selfprecovery.,,daily, snapshots. Web,accessible.,,Remote,sharing,thru, WebDav. Web,accessible.,,Remote,sharing,thru, WebDav,and,SMB. Web,accessible.,,Remote,sharing,thru, WebDav,and,SMB.,,Typically,managed, by,local,technical,support,contacts. UT,Enterprise,Bulk,Storage,(UTEBS) $0.40 yes,(if,within, UDC) UT,Research,Data,Repository, (UTRDR) Departments,, Researchers $0.25 no Qualified, researchers,only Box.Net,'personal' $1.00,(Common,Good) yes,,but,no, ITAR Box.Net,'departmental' $1.00, yes,,but,no, ITAR faculty,,staff,, students Departments,, Researchers minimum,1tb 99.99%,,data,center, failover,,data,replication, available.,,multiple,10gb, connections,within,udc. minimum,1tb Data,center,failover,(TACC, and,arlington).,,data,is, replicated.,,connection,to, campuses,is,varied. set,by, deparment set,by, deparment/unit no,limit Campus,wide,availability,in,Fall,2012.,, Local,server,capable,of,accessing,ISCSI, volumes,is,necessary.,,local, management,required no,limit Accesses,is,thru,UTRDR,only,servers, (irods).,,researchers,has,to,be,pi, qualified. yes cloud,service file,revisions Web,,mobile,,and,OS,client,accessible.,, Remote,sharing. yes cloud,service file,revisions Web,,mobile,,and,OS,client,accessible.,, Remote,sharing.

18 Box Standard Operating Procedures Draft James Lewis Individual (Common Good) Storage all individually provisioned accounts will receive 25 GB quota (hard limit) faculty and staff (which includes most graduate students) can auto provision an account student accounts will be manually provisioned upon request of TSCs to Box Project team (pending vendor accessibility compliance); student accounts mayonly be provisioned if they will be collaborating on dept/group storage users requiring more than 25 GB must be allocated dept/group storage Dept/Group Storage Support Individual units may choose to purchase Box storage in 1 TB or larger allocations at $1/GB Units desiring dept/group storage are encouraged to purchase their storage for the year during the annual renewal (start of the FY) Additional dept/group storage may be purchased in 1 TB allocations via request to the Box Project team (Box will require allocations in 10 TB units if we need to add to our total available storage) No reduction in allocated dept/group storage will be allowed except at the annual renewal Best Practices for Dept/Group Storage create a resource EID request provisioning of resource EID, along with requested allocation from Box Project team login to Box with resource EID Create a folder Share folder/invite collaborators (future: establish group, and share folder with group) Dept/Group Storage - support by local TSC, with escalation to Box Project team (via Footprints), as required Individual (Common Good) Storage - support by Help Desk, with escalation to Box Project team, as required Communication Establishment of a service website: basic information contained in this SOP, as well as links to Box-provided documentation and support, link to (or transition documentation from) UT Box Wiki