On 05/26/2015 09:29 AM, Flavio Percoco wrote: > Greetings, > > TL;DR: Thanks everyone for your feedback. Based on the discussed plans > at the summit - I'll be writing more about these later - Zaqar will > stick around and play its role in the community. > > Summit Summary > ============== > > I'm happy to say that several use cases were discussed at the summit > and the difference from previous summits is that we left the room with > some action items to make them happen. > > Cross-project user-facing notifications > ======================================= > > https://etherpad.openstack.org/p/liberty-cross-project-user-notifications > > Besides brainstorming a bit on what things should/should not be > notified and what format should be used, we also talked a bit about > the available technologies that could be used for this tasks. Zaqar > was among those and, AFAICT, at the end of the session we agreed on > giving this a try. It'll likely not happen as fast as we want but the > action item out of this session was to write a cross-project spec > describing the things discussed and the technology that will be > adopted. > > Heat + Zaqar > ============ > > The 2 main areas where Zaqar will be used in Heat are Software Config > and Hooks. The minimum requirements (server side) for this are in > place already. There's some work to do on the client side that the > team will get to asap. > > > Sahara (or other guest agent based services) + Zaqar > ==================================================== > > We discussed 3 different ways to enable services to communicate with > their guest agents using Zaqar: > > 1) Using notification hooks: Assuming the guest agents doesn't need to > communicate with the controller, the controller can register a > notification hook that will push messages to the guest agent. > > 2) Inject keystone credentials: The controller would inject keystone > credentials into the VM to allow the guest agent to send/receive > messages using Zaqar. > > 3) PreSigned URLs: The controller injects a PreSigned URL in the > controller that will grant the guest agent access to a specific > tenant/queue with either read or read&write access.
I think it is important to note that these 3 options are for a sub set of guest agent based services. It was agreed that Zaqar would look at a oslo_messaging driver for the services that did not agree with the 3 options presented. > > > Hallway Discussions > =================== > > We had a chance to talk to some other folks from teams like Horizon > that were also interested in doing some actual integration work with > Zaqar as well. Not to mention that some other folks from the puppet > team showed interest in helping out with the creation of these > manifests. > > > Next Steps > ========== > > In light of the above, and as mentioned in the TL;DR, Zaqar will stick > around and the team, as promised, will focus on making those > integrations happen. The team is small, which means we'll carefully > pick the tasks we'll be spending time on. > > As a first step, we should restore our meetings and get to work right > away. To favor our contributors in NZ, next week's meeting will be at > 21:00 UTC and we'll keep it at that time for 2 weeks. > > For the Zaqar team (and folks interested), I'll be sending out further > emails to sync on the work to do. > > Special thanks for all the folks that showed interest, participated in > sessions and that are committed on making this happen. > > Lets now make it happen, > Flavio > -- *Graham Hayes *Software Engineer DNS as a Service HP Public Cloud - Platform Services GPG Key: 7D28E972 graham.ha...@hp.com <mailto:graham.ha...@hp.com> M +353 87 377 8315 P +353 1 524 2175 Dublin, Ireland HP <http://www.hp.com/> __________________________________________________________________________ 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
