You are viewing a plain text version of this content. The canonical link for it is here.
Posted to olio-user@incubator.apache.org by Vasileios Kontorinis <bk...@gmail.com> on 2010/02/25 02:47:37 UTC
Running ssh from as an olio tool.
Shanti and Akara,
I am probably trying something bold :-). I want to start a script on the
Dom0 (I use Xen) when the steady state starts so that I do not get to
measure the initial setup. In other words, instead of simply vmstat or
mpstat on the SUT or the master/clients I would like to run something like
"ssh <Dom0_ip> vmstat <args>".
Unfortunately, in that case Olio will consolidate all the logs in one file
"ssh.log.<master_machine>" and it's not clear how the logs get merged.
A workaround would be to have separate scripts like "remote_vmstat_<Dom0_ip>
<args>" . This should resolve the naming problem.
However, Olio still does not appear able to handle ssh properly....
Any ideas?
Thanks
P.s. I could send you some stacktraces if you feel like it :-)
-------------------------------------------------------------------
Kontorinis Vasileios
Phd student, University of California San Diego
San Diego, CA 92122
Cell. phone: (858) 717 6899
bkontorinis@gmail.com, vkontori@ucsd.edu
-------------------------------------------------------------------
Re: Running ssh from as an olio tool.
Posted by Akara Sucharitakul <Ak...@Sun.COM>.
Sorry for the delay. You need a Faban 1.0.1 feature that allows you to
specify the managedHost field. This will be the systems being managed as
opposed to the systems the load is driven to. Sometimes the latter can
be a load balancer. Also a minor change in the submission form is needed
to show this field.
-Akara
Vasileios Kontorinis wrote:
> Akara hi,
> To my understanding if I specify <dom0> in the run.xml file like:
> <fa:hostConfig>
> <fa:host>machine1_ip dom0_ip </fa:host>
> ....
> </fa:hostConfig>
>
> Then there will be clients started in both machine1 and dom0 that will
> be driving the olio workload. Right?
> However, I want the clients to be driving the workload only from
> machine1 not dom0.
>
> Specifically I have the virtual machines as the SUT, those virtual
> machines are hosted on dom0 and I drive the workload from a completely
> different machine.
> Therefore, I just want to run vmstat, sar, mpstat and other tools on the
> physical machine dom0, which is not driving the workload or is directly
> part of the SUT. (it is indirectly cause there are vms runnign on it but
> the physical machine does not have a webserver or dbserver or filestore.
> Those are inside the vms)
> Is this clear? How exactly can I do that?
>
> Thanks
> -------------------------------------------------------------------
> Kontorinis Vasileios
> Phd student, University of California San Diego
> San Diego, CA 92122
> Cell. phone: (858) 717 6899
> bkontorinis@gmail.com <ma...@gmail.com>, vkontori@ucsd.edu
> <ma...@ucsd.edu>
> -------------------------------------------------------------------
>
>
> 2010/2/24 Akara Sucharitakul <Akara.Sucharitakul@sun.com
> <ma...@sun.com>>
>
> It should start such collection automatically for you. Just specify
> the hosts you're driving as <dom0> and <dom1>. The harness will
> contact those systems and start the tools automatically.
>
> But perhaps I'm missing something. Please let me know. Thanks.
>
> -Akara
>
> Vasileios Kontorinis wrote:
>
> Shanti and Akara,
> I am probably trying something bold :-). I want to start a
> script on the Dom0 (I use Xen) when the steady state starts so
> that I do not get to measure the initial setup. In other words,
> instead of simply vmstat or mpstat on the SUT or the
> master/clients I would like to run something like "ssh <Dom0_ip>
> vmstat <args>".
> Unfortunately, in that case Olio will consolidate all the logs
> in one file "ssh.log.<master_machine>" and it's not clear how
> the logs get merged.
> A workaround would be to have separate scripts like
> "remote_vmstat_<Dom0_ip> <args>" . This should resolve the
> naming problem.
> However, Olio still does not appear able to handle ssh properly....
>
> Any ideas?
>
> Thanks
> P.s. I could send you some stacktraces if you feel like it :-)
> -------------------------------------------------------------------
> Kontorinis Vasileios
> Phd student, University of California San Diego
> San Diego, CA 92122
> Cell. phone: (858) 717 6899
> bkontorinis@gmail.com <ma...@gmail.com>
> <mailto:bkontorinis@gmail.com <ma...@gmail.com>>,
> vkontori@ucsd.edu <ma...@ucsd.edu>
> <mailto:vkontori@ucsd.edu <ma...@ucsd.edu>>
> -------------------------------------------------------------------
>
>
>
Re: Running ssh from as an olio tool.
Posted by Vasileios Kontorinis <bk...@gmail.com>.
Akara hi,
To my understanding if I specify <dom0> in the run.xml file like:
<fa:hostConfig>
<fa:host>machine1_ip dom0_ip </fa:host>
....
</fa:hostConfig>
Then there will be clients started in both machine1 and dom0 that will be
driving the olio workload. Right?
However, I want the clients to be driving the workload only from machine1
not dom0.
Specifically I have the virtual machines as the SUT, those virtual machines
are hosted on dom0 and I drive the workload from a completely different
machine.
Therefore, I just want to run vmstat, sar, mpstat and other tools on the
physical machine dom0, which is not driving the workload or is directly part
of the SUT. (it is indirectly cause there are vms runnign on it but the
physical machine does not have a webserver or dbserver or filestore. Those
are inside the vms)
Is this clear? How exactly can I do that?
Thanks
-------------------------------------------------------------------
Kontorinis Vasileios
Phd student, University of California San Diego
San Diego, CA 92122
Cell. phone: (858) 717 6899
bkontorinis@gmail.com, vkontori@ucsd.edu
-------------------------------------------------------------------
2010/2/24 Akara Sucharitakul <Ak...@sun.com>
> It should start such collection automatically for you. Just specify the
> hosts you're driving as <dom0> and <dom1>. The harness will contact those
> systems and start the tools automatically.
>
> But perhaps I'm missing something. Please let me know. Thanks.
>
> -Akara
>
> Vasileios Kontorinis wrote:
>
>> Shanti and Akara,
>> I am probably trying something bold :-). I want to start a script on the
>> Dom0 (I use Xen) when the steady state starts so that I do not get to
>> measure the initial setup. In other words, instead of simply vmstat or
>> mpstat on the SUT or the master/clients I would like to run something like
>> "ssh <Dom0_ip> vmstat <args>".
>> Unfortunately, in that case Olio will consolidate all the logs in one file
>> "ssh.log.<master_machine>" and it's not clear how the logs get merged.
>> A workaround would be to have separate scripts like
>> "remote_vmstat_<Dom0_ip> <args>" . This should resolve the naming problem.
>> However, Olio still does not appear able to handle ssh properly....
>>
>> Any ideas?
>>
>> Thanks
>> P.s. I could send you some stacktraces if you feel like it :-)
>> -------------------------------------------------------------------
>> Kontorinis Vasileios
>> Phd student, University of California San Diego
>> San Diego, CA 92122
>> Cell. phone: (858) 717 6899
>> bkontorinis@gmail.com <ma...@gmail.com>, vkontori@ucsd.edu<mailto:
>> vkontori@ucsd.edu>
>> -------------------------------------------------------------------
>>
>
>
Re: Running ssh from as an olio tool.
Posted by Akara Sucharitakul <Ak...@Sun.COM>.
It should start such collection automatically for you. Just specify the
hosts you're driving as <dom0> and <dom1>. The harness will contact
those systems and start the tools automatically.
But perhaps I'm missing something. Please let me know. Thanks.
-Akara
Vasileios Kontorinis wrote:
> Shanti and Akara,
> I am probably trying something bold :-). I want to start a script on
> the Dom0 (I use Xen) when the steady state starts so that I do not get
> to measure the initial setup. In other words, instead of simply vmstat
> or mpstat on the SUT or the master/clients I would like to run something
> like "ssh <Dom0_ip> vmstat <args>".
> Unfortunately, in that case Olio will consolidate all the logs in one
> file "ssh.log.<master_machine>" and it's not clear how the logs get merged.
> A workaround would be to have separate scripts like
> "remote_vmstat_<Dom0_ip> <args>" . This should resolve the naming problem.
> However, Olio still does not appear able to handle ssh properly....
>
> Any ideas?
>
> Thanks
> P.s. I could send you some stacktraces if you feel like it :-)
> -------------------------------------------------------------------
> Kontorinis Vasileios
> Phd student, University of California San Diego
> San Diego, CA 92122
> Cell. phone: (858) 717 6899
> bkontorinis@gmail.com <ma...@gmail.com>, vkontori@ucsd.edu
> <ma...@ucsd.edu>
> -------------------------------------------------------------------