Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Denis Makogon
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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Ed Cranford
; -- > *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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Tim Simpson
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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Ed Cranford
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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Denis Makogon
* 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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Tim Simpson
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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Denis Makogon
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 >> >> -- >>

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Tim Simpson
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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Denis Makogon
-- > *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

Re: [openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Tim Simpson
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

[openstack-dev] [trove] Dropping connectivity from guesagent to Trove back-end

2013-12-20 Thread Denis Makogon
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