- Tim
From: Dmitry Mescheryakov
[dmescherya...@mirantis.com<mailto:dmescherya...@mirantis.com>]
Sent: Wednesday, December 18, 2013 11:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] My thoughts on the
> From: Tim Simpson [tim.simp...@rackspace.com]
> Sent: Wednesday, December 18, 2013 11:34 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
>
> Thanks for the summary Dmitry. I
om]
Sent: Wednesday, December 18, 2013 4:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
On 12/18/2013 12:27 PM, Tim Simpson wrote:
Please provide proof of that assumption or at least a general hypothesis
and how it's written and explained, has changed a lot over the past ten years.
Thanks,
Tim
-Original Message-
From: Steven Dake [mailto:sd...@redhat.com]
Sent: Wednesday, December 18, 2013 4:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openst
nks,
Tim
From: Clint Byrum [cl...@fewbar.com]
Sent: Wednesday, December 18, 2013 11:36 AM
To: openstack-dev
Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
Excerpts from Tim Simpson's message of 2013-12-18 07:34:14 -0800:
I
___
From: Tim Simpson [tim.simp...@rackspace.com]
Sent: Wednesday, December 18, 2013 11:34 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
Thanks for the summary Dmitry. I'm ok with these ideas, an
n out a bit before being too concerned.
>
> - Tim
>
>
> --
> *From:* Dmitry Mescheryakov [dmescherya...@mirantis.com]
> *Sent:* Wednesday, December 18, 2013 11:51 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
>
> *Su
herya...@mirantis.com]
Sent: Wednesday, December 18, 2013 11:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
Tim,
The unified agent we proposing is based on the following ideas:
* the core agent has
nts
to pursue using / developing an agent that was written in C++.
Thanks,
Tim
________________________
From: Clint Byrum [cl...@fewbar.com]
Sent: Wednesday, December 18, 2013 11:36 AM
To: openstack-dev
Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
Ex
lunch here, just a
question of who does the work.
Thanks,
Kevin
From: Clint Byrum [cl...@fewbar.com]
Sent: Wednesday, December 18, 2013 9:38 AM
To: openstack-dev
Subject: Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent
Excerpts from Ste
2013/12/18 Steven Dake
> On 12/18/2013 08:34 AM, Tim Simpson wrote:
>
> I've been following the Unified Agent mailing list thread for awhile now
> and, as someone who has written a fair amount of code for both of the two
> existing Trove agents, thought I should give my opinion about it. I like
Tim,
The unified agent we proposing is based on the following ideas:
* the core agent has _no_ functionality at all. It is a pure RPC
mechanism with the ability to add whichever API needed on top of it.
* the API is organized into modules which could be reused across
different projects.
* th
Excerpts from Steven Dake's message of 2013-12-18 08:05:09 -0800:
> On 12/18/2013 08:34 AM, Tim Simpson wrote:
> > I've been following the Unified Agent mailing list thread for awhile
> > now and, as someone who has written a fair amount of code for both of
> > the two existing Trove agents, thou
Excerpts from Tim Simpson's message of 2013-12-18 07:34:14 -0800:
> I've been following the Unified Agent mailing list thread for awhile
> now and, as someone who has written a fair amount of code for both of
> the two existing Trove agents, thought I should give my opinion about
> it. I like the i
On 12/18/2013 08:34 AM, Tim Simpson wrote:
I've been following the Unified Agent mailing list thread for awhile
now and, as someone who has written a fair amount of code for both of
the two existing Trove agents, thought I should give my opinion about
it. I like the idea of a unified agent, but
I've been following the Unified Agent mailing list thread for awhile now and,
as someone who has written a fair amount of code for both of the two existing
Trove agents, thought I should give my opinion about it. I like the idea of a
unified agent, but believe that forcing Trove to adopt this ag
16 matches
Mail list logo
