ctor will complicate things without giving us any benefit.
>>
>> Thanks,
>>
>> Tim
>>
>> ------
>> *From:* Ed Cranford [ed.cranf...@gmail.com]
>> *Sent:* Friday, December 20, 2013 10:13 AM
>>
>> *To:* OpenStack Develop
; --
> *From:* Ed Cranford [ed.cranf...@gmail.com]
> *Sent:* Friday, December 20, 2013 10:13 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [trove] Dropping connectivity from
> guesagent to
OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Dropping connectivity from guesagent to
Trove back-end
Conductor was the first phase of
https://wiki.openstack.org/wiki/Trove/guest_agent_communication whose proposed
future phases include turning co
t;> *From:* Denis Makogon [dmako...@mirantis.com]
>> *Sent:* Friday, December 20, 2013 8:58 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [trove] Dropping connectivity from
>> guesagent to Trove back-end
>>
>&g
* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [trove] Dropping connectivity from
> guesagent to Trove back-end
>
> Unfortunately, Trove cannot manage it's own extensions, so if, suppose,
> i would try to get provisioned cassandr
ty.
Thanks,
Tim
From: Denis Makogon [dmako...@mirantis.com<mailto:dmako...@mirantis.com>]
Sent: Friday, December 20, 2013 7:04 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove
back-end
ommon as possible between
>> datastores should. However I don't agree that trove-taskmanager (by which I
>> assume you mean the daemon) has to only be for common functionality.
>>
>> Thanks,
>>
>> Tim
>>
>> --
>>
usage questions)
Subject: Re: [openstack-dev] [trove] Dropping connectivity from guesagent to
Trove back-end
Thanks for response, Tim.
As i said, it would be confusing situation when database which has no ACL would
be deployed by Trove with root enabled - this looks very strange since user
allow
--
> *From:* Denis Makogon [dmako...@mirantis.com]
> *Sent:* Friday, December 20, 2013 7:04 AM
> *To:* OpenStack Development Mailing List
> *Subject:* [openstack-dev] [trove] Dropping connectivity from guesagent
> to Trove back-end
>
>Goodday, OpenStack DВaaS community.
&g
cember 20, 2013 7:04 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove
back-end
Goodday, OpenStack DВaaS community.
I'd like to start conversation about dropping connectivity from In-VM
guestagent and Trove ba
Goodday, OpenStack DВaaS community.
I'd like to start conversation about dropping connectivity from In-VM
guestagent and Trove back-end.
Since Trove has conductor service which interacts with agents via MQ
service, we could let it deal with any back-end required operations
initialize
11 matches
Mail list logo