CritPath Move

We have an open ticket to discuss these plans.

CritPath currently uses a Cpanel-based system installed on a CentOS server to manage thousands of email accounts, hundreds of lists, and dozens of web sites. Our goal is to transition them to using the May First/People Link control panel on a Debian-based server.

We need a system that achieves the following goals:

  • Allows CritPath to create and delete services on their dedicated server (not just control panel items, but being able to create new memberships and hosting orders as well)
  • Maintain identity of CritPath within May First/People Link
  • Coherently transition from CritPath's model, in which individual contacts are assigned different services as requested, but they are not organized by parent organization, to MFPL's model.

Following are changes to the MFPL system that I think we'll need:

  • MFPL extends our Control Panel to include a special server-maintainer section. The server-maintainer section allows certain authorized users the ability to add/delete/modify memberships and hosting orders on a given server.
  • MFPL extends our Control Panel so that when users log on, they can get a different theme depending on the server they are hosted on. CritPath and MFPL can collaborate on a theme that incorporates both organizations
  • MFPL adds a new field in the ticket tracker for partner which defaults to MFPL, but CritPath is an option. Users who fill out tickets can choose CritPath, or anyone can re-code the ticket based on the content of the ticket. CritPath support people subscribe to an RSS feed of all tickets coded to CritPath. Either MFPL or CritPath answer queries.

Following are steps to take for the transition:

  • MFPL creates a virtual server on ottorene dedicated to CritPath (this option will use less electricity and be much easier for us than using the IBM given to us for this purpose).
  • We fully test the system for creating new accounts before we transition anything
  • Transition: DNS, mailman, web/email accounts
  • Reformat axiom and transfer all services to axiom

Following is a use case for a new CritPath user requesting services:

  • User fills out form on CritPath page
  • CritPath receives email and decides to provide service
  • CritPath admin logs on to MFPL Control Panel and creates membership/hosting order
  • New user is notified with canned email (written by CritPath) that explains our relationship
  • Email includes link to MFPL control panel. When user logs onto control panel, they see CritPath/MFPL theme

Following is use case for an existing CritPath user requesting additional service

  • If they want a new email list, DNS entry, or email address then they use the MFPL Control Panel to create it themselves (as many as they want)
  • If they want a new web site, they contact CritPath and CritPath creates a new hosting order for them.

Following is a use case for a CritPath user request support

  • They fill out a ticket on the MFPL support system.
  • They don't bother with the partner field
  • MFPL member sees ticket and re-codes to CritPath and leaves a question/comment on the ticket
  • CritPath support person gets RSS feed, sees ticket and contributes to the solution
  • Either MFPL or CritPath person resolves ticket.

Please post all tickets with the critpath-transition keyword.

Last modified 13 years ago Last modified on Nov 28, 2008, 5:01:42 PM