SysAdmin Persona: Sam

Jeremy Perry jeperry at redhat.com
Tue Nov 6 15:37:22 UTC 2012


I like it. The Personal bit is just enough, and the Environment section was sorely missing from the existing personas.

Your call for thoughts on the Needs/Wants section ties directly into what is currently under "Cloud-based responsibilities."

https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Personas#System-Administrator

I actually think we need two things

1. Key Goals
These should deliberately state what AND how he needs to do his job well. I think this would probably an action-oriented re-write of the current "Cloud-based responsibilities" into succinct statements that sound like actual goals, i.e: 
* Respond quickly to incidents and outages in services

2. instead of Needs/Wants, how about Challenges? 
Challenges makes this section a bit broader. It still allows us to express needs and wants, but puts more emphasis on acute problems that the tool needs to solve. Focusing on challenges helps us define the value proposition of the tool. A challenge might sound like:
* Needs a way to be alerted about incidents that require immediate response even when not at a computer

Note that one starts with "need" - they don't all have to. The challenges list shouldn't try to be a list of solutions either, It should just describe pain points which will then help us determine what the tool can provide to address.

Thoughts?

Jeremy



On Nov 6, 2012, at 9:13 AM, Justin Clift <jclift at redhat.com> wrote:

> Hi all,
> 
> This is the text for the "SysAdmin" Persona (Sam), presented a
> few minutes ago.
> 
> Trying to think of how to specify needs/wants, but nothing's
> coming to mind.  Any suggestions?
> 
> + Justin
> 
> **************************************************************
> 
> Sysadmin Persona: Sam
> 
> Personal background
> *******************
> 
> * Sam is a 35 year old male from Hanoi, Vietnam, who migrated
>  to east coast US about 10 years ago.
> 
> * He is the sole breadwinner in his family, happily married to
>  his wife of 8 years, and has a 3 year old child.
> 
> * Sam works as the Aeolus SysAdmin for "T-Bone", a large
>  monopoly style Telco in his area.
> 
> * He previously worked on Enterprise Class Solaris Systems for
>  many years, and moved to working with Linux (mostly RHEL), a
>  few years ago.
> 
> Environment
> ***********
> 
> * "T-Bone" has dedicated NAS, SAN and network teams, with a 2
>  week+ (min) turn around time for requests.
> 
> * Aeolus runs on a single server in this environment, a dual
>  cpu (2 x quad core) HP DL380 with 24 GB RAM, and 2TB of
>  local RAID 0 SATA storage.
> 
> * Aeolus is hooked up to a small vSphere 5.x cluster.  vCenter
>  is running on a server identical to the Aeolus one, and 4 x
>  hosts (also HP DL 380's) with 96GB RAM and 4TB of shared
>  NetApp storage (a fast NAS).
> 
> * Sam's team also use Aeolus with EC2, for giving their
>  partners access to selected builds of their applications,
>  for testing and qualification (not prod).
> 
> * The Aeolus environment is used by the developers in a part
>  of T-Bone's business and government division.  About 40
>  people.
> 
> * The standard development platform the developers write for
>  is RHEL 6.x, JBoss (various releases), and Oracle 10g/11g.
> 
> * NetBackup is the enterprise backup solution, so Sam wrote
>  custom shell scripts to do backups of Aeolus nightly.
> 
>  They don't back up generated Aeolus images, but do backup
>  up everything else (Aeolus state, XML templates, etc).
> 
> * Sam has a ToDo list item to investigate RHEV, and has been
>  toying around with oVirt on a spare desktop box.  Not in
>  depth with it yet.
> 
> Needs / wants
> *************
> 
> * ???
> 
> **************************************************************
> 
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/aeolus-devel/attachments/20121106/3d6b372d/attachment.html>


More information about the aeolus-devel mailing list