-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm very much interested in talking with some Keystone folks about this auth issue. I would be willing to dedicate a Barbican Working Session to this discussion if there is a time slot that works for all the interested parties.
- - Douglas Mendizabal On 5/14/15 3:13 PM, Fox, Kevin M wrote: > If there's a free session, can we dedicate a session specifically > to the zaqar, barbican, sahara, heat, trove, guestagent, keystone > auth thingy so everyone's all together? > > Thanks, Kevin ________________________________________ From: Flavio > Percoco [fla...@redhat.com] Sent: Thursday, May 14, 2015 12:15 PM > To: Sergey Lukjanov Cc: OpenStack Development Mailing List (not for > usage questions) Subject: Re: [openstack-dev] [trove][zaqar] Trove > and Zaqar integration. Summit working session > > On 14/05/15 10:07 -0700, Sergey Lukjanov wrote: >> Hey, >> >> in Sahara we're looking on using Zaqar as a transport for agent >> some day as well. Unfortunately this section overlaps with Sahara >> sessions. > > Sergey, > > We still have some free sessions, we'd be happy to dedicate one to > Sahara. Any slot that looks good for you? > > http://libertydesignsummit.sched.org/overview/type/design+summit/Zaqar #.VVT0CvYU9hE > > Thanks, Flavio > >> >> On Thu, May 14, 2015 at 12:19 AM, Flavio Percoco >> <fla...@redhat.com> wrote: >> >> On 13/05/15 18:06 +0000, Fox, Kevin M wrote: >> >> Sahara also has the same problem, but worse, since they currently >> only support ssh with their agent, so its either assign floating >> ip's to all nodes, or your sahara controller must be on your one >> and only network node so it can tunnel. :/ >> >> Should we have a chat with them too? >> >> >> We've scheduled a discussion with Trove's team on Thursday at >> 5pm. It'd be great to have this discussion once and together to >> know what the common issues are and what things need to be done. >> >> I'll ping folks from both teams to invite them to this session. >> If they can't make it, I'm happy to use another working session >> slot. >> >> Cheers, Flavio >> >> http://libertydesignsummit.sched.org/event/59dc6ec910a732cdbf5970b679 2e1cef >> >> #.VVRL0PYU9hE >> >> >> >> >> Thanks, Kevin ________________________________________ From: Zane >> Bitter [zbit...@redhat.com] Sent: Wednesday, May 13, 2015 10:26 >> AM To: openstack-dev@lists.openstack.org Subject: Re: >> [openstack-dev] [trove][zaqar] Trove and Zaqar integration. >> Summit working session >> >> On 11/05/15 05:49, Flavio Percoco wrote: >> >> On 08/05/15 00:45 -0700, Nikhil Manchanda wrote: >> >> 3) The trove-guest-agent is in vm. it is connected by >> taskmanager by rabbitmq. We designed it. But is there some >> prectise to do this? how to make the vm be connected in >> vm-network and management network? >> >> >> Most deployments of Trove that I am familiar with set up a >> separate RabbitMQ server in cloud that is used by Trove. It is >> not recommended to use the same infrastructure RabbitMQ server >> for Trove for security reasons. Also most deployments of Trove >> set up a private (neutron) network that the RabbitMQ server and >> guests are connected to, and all RPC messages are sent over this >> network. >> >> >> We've discussed trove+zaqar in the past and I believe some folks >> from the Trove team have been in contact with Fei Long lately >> about this. Since one of the projects goal's for this cycle is to >> provide support to other projects and contribute to the adoption, >> I'm wondering if any of the members of the trove team would be >> willing to participate in a Zaqar working session completely >> dedicated to this integration? >> >> >> +1 >> >> I learned from a concurrent thread ("[Murano] [Mistral] SSH >> workflow action") that Murano are doing exactly the same thing >> with a separate RabbitMQ server to communicate with guest agents. >> It's a real waste of energy when multiple OpenStack projects all >> have to solve the same problem from scratch, so a single answer >> to this would be great. >> >> In that thread I suggested (and Murano developers agreed with) >> making the transport pluggable so that operators could choose >> Zaqar instead. I would strongly support doing the same here. >> >> >> +1 :) >> >> Flavio >> >> >> >> >> cheers, Zane. >> >> >> It'd be a great opportunity to figure out what's really needed, >> edge cases and get some work done on this specific case. >> >> Thanks, Flavio >> >> >> >> _____________________________________________________________________ _____ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org? >> subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> >> >> ________________________________________________________________________ __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org? >> subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> ________________________________________________________________________ __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org? >> subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> - -- >> @flaper87 Flavio Percoco >> >> _____________________________________________________________________ _____ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> >> >> >> - -- >> Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack >> Data Processing) Principal Software Engineer Mirantis Inc. > > -- @flaper87 Flavio Percoco > > ______________________________________________________________________ ____ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVVSaFAAoJEB7Z2EQgmLX7n/UP/12bkw4AYg+JrSh1WcgAYvxV XUB6yEaNv/I363OdY0pu6VQYW7w9IkCR3a0hkLGc6zBATab0gUVpnyWGBa+NWvMe HcyMTx82KgGIQ3uLW6NCyzmyW+CE5R5gEHnR/UhXLZmtyeiiTF4tgMN+pdTONF46 PfpoZzVkP3YRufvfCV7f1RdiZuavPD/m1VS29If0l70VEeYxUM5mPqKFwbrqhvfs 52HdzNUcb2xMiy71xfCZ9wosTGf2JzdVLy+Di5kJCACx2EYRL45VzIZzeNU37z70 AAcky6jN5mXn47/THQ+4D1su79/zQ6Ue9MVQWn4QA/IzBB/TMUWDC/1sGN4T4dXw Lfvq7BnLDzVmX39ei+Ae9kpYppiCkLwdm7j7FEu6W8QfCwH8JcRXsHFkY/6GwkPz gr7XylUtBnzv3oFU6GB63EAjsuDOOx+CZB1IAUZFjwtLEP+Gr04jcCMgkXc9Z7Bj l80NEkJ0ezqZUSQHPB0bZxcWBxP21xm72t6UGvWwmtE1qILwjE3o3o8G3sX+zVWT yJwT1wMgp79NfB1Mwl3OsV3DGIONraHU0lsFTIZwiHnUlagBiJir8i/SGbTfB6T2 dvQuBjArj+qKhQU7ohrK+TPhMMeGIcHnzzF1uwjKM+v0qu9ob1LbMYGyvm92PkBy 8dZgefSM5m3DqYJqwQ2w =SpuM -----END PGP SIGNATURE----- __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
