Bug 1041964

Summary: [RFE][horizon]: Spec for "push"-based realtime communication
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/realtime-spec
Whiteboard: upstream_milestone_none upstream_status_started upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:59:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 20:19:58 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/realtime-spec.

Description:

As per discussion at the Grizzly summit, there is agreement that creating a pluggable communication channel for providing push notifications to Horizon is the right way to go. This blueprint is to design and proof-of-concept that spec so that differing backend implementations (e.g. node.js or a python backend) could all communicate seamlessly.

Specification URL (additional information):

None