Jump to: navigation, search

Difference between revisions of "Personas-page-prototype-Daichi"

(Created page with "== <font color="#A061A8">Testing Daichi </font>== <table border=0 width=100%><tr valign=top> <td> CNBB Securities * Calvin * Chuck * End user persona TBD </td> <td> ===== Com...")
 
 
Line 1: Line 1:
== <font color="#A061A8">Testing Daichi </font>==
+
== <font color="#A061A8">Daichi Nakamura</font>==
 
<table border=0 width=100%><tr valign=top>
 
<table border=0 width=100%><tr valign=top>
<td>
+
 
CNBB Securities
 
* Calvin
 
* Chuck
 
* End user persona TBD
 
</td>
 
 
<td>
 
<td>
 
===== Company =====
 
===== Company =====
CNBB Securities, a large financial services company
+
Mid-sized Research University
 
===== Job Title =====
 
===== Job Title =====
Developer/Cloud Administrator
+
Cloud Engineer
 
===== Daily Horizon Usage =====
 
===== Daily Horizon Usage =====
2 hours
+
Less than 1 hour
 
===== Location =====  
 
===== Location =====  
New York City
+
Ibaraki, Japan
 
</td>
 
</td>
 
<td>
 
<td>
 
<gallery>
 
<gallery>
File:Example.jpg|Caption1
+
File:Photo_of_Daichi.jpg|Caption1
 
</gallery>
 
</gallery>
 
</td>
 
</td>
 
</table>
 
</table>
  
 +
<h4><font color="#29A0C1">What are your main responsibilities?</font></h4>
 +
He is responsible for operating an OpenStack based private cloud that provides compute and storage resources to researchers at the university. He loves hiking, watching movies and karaoke.
 +
 +
==== <font color="#29A0C1">How do you use Horizon Today?</font> ====
 +
Hmmmm, I don’t use Horizon all that much, there are a few things  that are easy to do in the GUI - like getting an overview of things. For most things, I use the CLI. The end users do use Horizon quite a bit, for things like spinning up instances and uploading files.
 +
 +
==== <font color="#29A0C1">How does your company use OpenStack today?</font> ====
 +
We use it to analyze lots of research data. We’re a university and have a lot of physicists and other scientists working with huge amounts of data that need a lot of compute resources. We’re also testing some production workloads.
  
<h4><font color="#29A0C1"> How do you use Horizon Today? </font></h4>
+
==== <font color="#29A0C1">Tell us about the users of your cloud.</font> ====
Not really, other than just to play with it. From what I’ve seen, I’m not sure Horizon’s
+
So, there’s maybe 75 right now? Some of them submit their jobs to an admin, and we make sure it gets done. Some of the other users have access through Horizon, so they can experiment a bit more -- these are the more developers types, not the scientists. People really appreciate the service; those who use it are really starting to depend on it, which is exciting for us to see.
something I’m going to use a lot, even once we get more vested in OpenStack.
 
Our developers have a small test and development cloud that they use for development
 
projects, and I think some of the more casual users tend to use Horizon.
 
  
==== <font color="#29A0C1">What are your main responsibilities?</font> ====
+
==== <font color="#29A0C1">Are you involved in the OpenStack Community?</font>====
Blah, blah, blah
+
I wouldn’t say I’m ‘involved.’ I follow the [operator’s] mailing list and some blogs. I’ve contributed code before -- when we found a bug and patched it. But other than that, I’m not all that involved.
  
==== <font color="#29A0C1">What do you think about working with the OpenStack Community?</font> ====
+
==== <font color="#29A0C1">What are the key obstacles that you see with OpenStack today?</font>====
Frankly, I sort of understand how some people may find the whole “community” thing
+
We’ve had a few bumps along the way with issues that come up that are new to us. There isn’t always documentation, probably because OpenStack is new, so some of the problems we see haven’t been seen by a lot of other people. That means I have to experiment on my own to solve problems, but you can usually get help from the mailing lists. I do wish sometimes there was more documentation of specific solutions, especially around networking.
appealing, but it’s not a big draw for me, at least in terms of participating myself. I just
 
don’t have the time at work, and I’d rather spend my free time with my family. I’m not
 
some kid that spends his or her evenings coding.
 
  
==== <font color="#29A0C1">What are the key obstacles that you see with OpenStack Today? </font>====
+
==== <font color="#29A0C1">When do you think your company will adopt OpenStack?</font>====
The general consensus in my team is that OpenStack isn’t a mature technology.
+
It’s not so much a matter of when, it’s going to be gradual. We’ll run our workloads where they work best for both the technology and the skills we have on staff. As we become more expert in OpenStack, and begin building new apps in a ‘cloudy’ way, we’ll move more stuff into our private cloud and grow that. It’ll be gradual, I don’t know if we’ll ever be 100% OpenStack. We’ll see.
We’re interested in tracking its progress, but using it within our own IT infrastructure,
 
at least right now, in my mind exposes us to too much risk. This is a conservative industry
 
that’s traditionally slow to change, especially when there is any chance of a negative
 
impact on security or disaster recovery. That’s just not something we can afford.
 
And open source is a different ball game for us. We have a lot of clout with our vendors
 
given our size, but when you get to something like OpenStack, the only way to influence
 
direction is through contributing code, and that’s certainly not how I want to spend my days.
 

Latest revision as of 21:04, 14 July 2014

Daichi Nakamura

Company

Mid-sized Research University

Job Title

Cloud Engineer

Daily Horizon Usage

Less than 1 hour

Location

Ibaraki, Japan

What are your main responsibilities?

He is responsible for operating an OpenStack based private cloud that provides compute and storage resources to researchers at the university. He loves hiking, watching movies and karaoke.

How do you use Horizon Today?

Hmmmm, I don’t use Horizon all that much, there are a few things that are easy to do in the GUI - like getting an overview of things. For most things, I use the CLI. The end users do use Horizon quite a bit, for things like spinning up instances and uploading files.

How does your company use OpenStack today?

We use it to analyze lots of research data. We’re a university and have a lot of physicists and other scientists working with huge amounts of data that need a lot of compute resources. We’re also testing some production workloads.

Tell us about the users of your cloud.

So, there’s maybe 75 right now? Some of them submit their jobs to an admin, and we make sure it gets done. Some of the other users have access through Horizon, so they can experiment a bit more -- these are the more developers types, not the scientists. People really appreciate the service; those who use it are really starting to depend on it, which is exciting for us to see.

Are you involved in the OpenStack Community?

I wouldn’t say I’m ‘involved.’ I follow the [operator’s] mailing list and some blogs. I’ve contributed code before -- when we found a bug and patched it. But other than that, I’m not all that involved.

What are the key obstacles that you see with OpenStack today?

We’ve had a few bumps along the way with issues that come up that are new to us. There isn’t always documentation, probably because OpenStack is new, so some of the problems we see haven’t been seen by a lot of other people. That means I have to experiment on my own to solve problems, but you can usually get help from the mailing lists. I do wish sometimes there was more documentation of specific solutions, especially around networking.

When do you think your company will adopt OpenStack?

It’s not so much a matter of when, it’s going to be gradual. We’ll run our workloads where they work best for both the technology and the skills we have on staff. As we become more expert in OpenStack, and begin building new apps in a ‘cloudy’ way, we’ll move more stuff into our private cloud and grow that. It’ll be gradual, I don’t know if we’ll ever be 100% OpenStack. We’ll see.