===========================
#openstack-meeting-3: Zaqar
===========================


Meeting started by flaper87 at 15:01:31 UTC.  The full logs are
available at
http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-11-17-15.01.log.html
.



Meeting summary
---------------

* Roll Call  (flaper87, 15:01:45)

* Agenda  (flaper87, 15:02:37)
  * LINK:
    https://wiki.openstack.org/wiki/Meetings/Zaqar#Weekly_Zaqar_.28queuing.29_Team_Meeting
    (flaper87, 15:02:39)
  * LINK:
    https://wiki.openstack.org/wiki/Meetings/Zaqar#Weekly_Zaqar_.28queuing.29_Team_Meeting
    (flaper87, 15:03:28)

* Persistent Transport https://review.openstack.org/#/c/134567/
  (flaper87, 15:04:01)
  * ACTION: vkmc to add cpallares as a secondary contact  (flaper87,
    15:10:51)
  * ACTION: cpallares and vkmc to coordinate on the things to do on that
    spec  (flaper87, 15:11:08)
  * ACTION: kgriffs to say something related to that spec ;)  (flaper87,
    15:11:34)
  * LINK: https://avro.apache.org/docs/current/#compare  (kgriffs,
    15:12:24)
  * LINK: http://kentonv.github.io/capnproto/  (flaper87, 15:12:32)
  * LINK: http://jparyani.github.io/pycapnp/  (kgriffs, 15:13:56)
  * ACTION: vkmc to evaluate serialization protocols for the websocket
    transport  (flaper87, 15:18:50)

* https://review.openstack.org/#/c/129192/ Notifications  (flaper87,
  15:19:03)
  * LINK: https://review.openstack.org/#/c/129192/  (flaper87, 15:20:16)
  * ACTION: to clarify how notifications will be pushed to clients
    (flaper87, 15:31:09)
  * ACTION: flaper87 to clarify how notifications will be pushed to
    clients  (flaper87, 15:32:58)
  * LINK:
    http://docs.openstack.org/developer/taskflow/engines.html#parallel
    (flaper87, 15:33:11)

* Open Discussion  (flaper87, 15:53:02)



Meeting ended at 15:59:29 UTC.



Action items, by person
-----------------------

* cpallares
  * vkmc to add cpallares as a secondary contact
  * cpallares and vkmc to coordinate on the things to do on that spec
* flaper87
  * flaper87 to clarify how notifications will be pushed to clients
* kgriffs
  * kgriffs to say something related to that spec ;)
* vkmc
  * vkmc to add cpallares as a secondary contact
  * cpallares and vkmc to coordinate on the things to do on that spec
  * vkmc to evaluate serialization protocols for the websocket transport



People present (lines said)
---------------------------

* flaper87 (220)
* kgriffs (71)
* vkmc (63)
* jeffrey4l (7)
* cpallares (6)
* openstack (5)
* zhiyan (3)
* exploreshaifali_ (1)



Generated by `MeetBot`_ 0.1.4