Jeremy Casper and Chris Goodland and friends,

 

Web Hosting 2.0

Think RackSpace.com, Amazon EC2, GoDaddy.com, HostGator.com, MS Azure AppFabric (in fact why don’t we just out-source this?)

 

When I think of Web Hosting 2.0 I want:


Windows Server 2008 64bit (config to use AD.umn.edu) with:

Microsoft Web Platform installer (lots of app choices)

IIS, Apache 2.x, SSL, .Net 2.x – 4.x, ASP Classic, PHP 5.x, WebDAV, Oracle 11g 64bit,  SQL server 2008, and/or mySQL back ends.


LAMP Servers with (config to use AD.umn.edu) with:

PHPMyAdmin , Control Panel (cPanel), Fantastico (lots of app choices)

Redhat 64bit , Apache 2.x, SSL, WebDAV, PHP 5.x, Ruby, Perl, Python, Oracle 11g 64bit, and/or mySQL back ends.


Cloud

Oracle 11g as a SERVICE. - See Andy Wattenhofer’s Oracle SaaS paper 2007.

Something like a modern version of UMFoundary – See Alexander Saint Croix’s ideas at https://wiki.umn.edu/view/UMFoundry/WebHome

RESTful PeopleSoft Web Services Bus

CentralAuth Hub (please keep this around!)

·         Add Shibboleth and OpenID service implementations

CLA’s offering to its units and researchers.


 

Web hotels without DB back ends and language platform support are of no value to me.

 

 

 

Thanks,

 

Craig Gjerdingen

Carlson School of Management

 

 


Sent: Thursday, February 18, 2010 7:42 AM
To: Craig L Gjerdingen-1
Subject: Call for feedback on Web Hosting 2.0

 

Web Hosting 2.0

By Jeremy Casper and Chris Goodland

 

Reduced budgets, the green movement, and the increasing popularity of social media tools are causing University of Minnesota departments to rethink how they do things on the web, including hosting websites. In the Office of Information Technology, we’re rethinking the central hosting options we offer to all departments as well. How can we partner with others to build next generation campus web hosting services?

In the past, the options and features of our several web hosting services have been defined differently. But a team has recently been formed to align these services, provide current and potential customers with a clearer roadmap, and better define partnerships between customers and our staff.

This team is currently documenting existing use, support structure, financial, and architecture information, and gathering requirements for a next generation web hosting service from University stakeholders and internal and external customers.

If you would like to provide feedback to the group, please email [log in to unmask]. The team’s final recommendations and a timeline for implementation will be disseminated at the end of March.