|
2 | 2 |
|
3 | 3 | ## Personas
|
4 | 4 |
|
5 |
| -| Name | Title | Notes | |
6 |
| -|------|-------|-------| |
7 |
| -| Oscar | Operations Chief | Knows of Chef or Puppet. Likely has some experience. Comfortable and likes Linux. Can work with network configuration, but does not own network. Has used VMware. | |
8 |
| -| Charlie | CIO | Concerned about time to market and ROI. Is working on commercial offering based on OpenStack. | |
9 |
| -| Denise | Cloud Developer | Working on adding features to OpenStack. Working on services to pair with OpenStack. Comfortable with Ruby code. | |
10 |
| -| Quick | Data Center Worker | Can operate systems. Can Power On/Off when supervised by Susan. In charge of rack and replacement of gear. Can Intiate Automation when directed and supervised, but not create automation. | |
11 |
| -| Sally | Support Center Worker | Person who takes calls about the installation. | |
12 |
| -| Susan | System Administrator | Responsible for the OS installation, tuning, config, the works. Knows of Chef/Puppet but decided they were not there yet, so wrote her own. Responsible for the Application Installation, but not the tuning or more than the base config. Responsible for Network connectivity to some point, but works with Networking Ops to ensure right. | |
13 |
| -| Albert | Security Analyst/Operations | Goal to prevent any Interaction with any Machine/OS/Application, unless the proper information/justification is supplied.| |
| 5 | +<TABLE border=0> |
| 6 | + <TBODY> |
| 7 | + <TR> |
| 8 | + <TH>Name</TH> |
| 9 | + <TH>Title</TH> |
| 10 | + <TH>Notes</TH></TR> |
| 11 | + <TR> |
| 12 | + <TD>Oscar</TD> |
| 13 | + <TD>Operations Chief</TD> |
| 14 | + <TD>Knows of Chef or Puppet. Likely has some experience. Comfortable and likes Linux. Can work with network configuration, but does not own network. Has used VMware.</TD> |
| 15 | + </TR> |
| 16 | + <TR> |
| 17 | + <TD>Charlie</TD> |
| 18 | + <TD>CIO</TD> |
| 19 | + <TD>Concerned about time to market and ROI. Is working on commercial offering based on OpenStack.</TD></TR> |
| 20 | + <TR> |
| 21 | + <TD>Denise</TD> |
| 22 | + <TD>Cloud Developer</TD> |
| 23 | + <TD>Working on adding features to OpenStack. Working on services to pair with OpenStack. Comfortable with Ruby code.</TD></TR> |
| 24 | + <TR> |
| 25 | + <TD>Quick</TD> |
| 26 | + <TD>Data Center Worker</TD> |
| 27 | + <TD>Can operate systems. Can power on/off when supervised by Susan. In charge of rack and replacement of gear. Can initiate automation when directed and supervised, but cannot create automation.</TD> |
| 28 | + </TR> |
| 29 | + <TR> |
| 30 | + <TD>Sally</TD> |
| 31 | + <TD>Support Center Worker</TD> |
| 32 | + <TD>Person who takes calls about the installation.</TD></TR> |
| 33 | + <TR> |
| 34 | + <TD>Susan</TD> |
| 35 | + <TD>System Administrator</TD> |
| 36 | + <TD>Responsible for the OS installation, tuning, configuration, the works. Knows of Chef/Puppet but decided they were not there yet, so wrote her own. Responsible for the application installation, but not the tuning or more than the base configuration. Responsible for network connectivity to some point, but works with Networking Ops to ensure right.</TD></TR> |
| 37 | + <TR> |
| 38 | + <TD>Albert</TD> |
| 39 | + <TD>Security Analyst/Operations</TD> |
| 40 | + <TD>Goal is to prevent any interaction with any machine/OS/application, unless the proper information/justification is supplied.</TD></TR></TABLE> |
14 | 41 |
|
15 | 42 | ## Use cases
|
16 | 43 |
|
|
0 commit comments