Open Stack

Thanks Anusha!

I agree that moving the congress_dashboard code to its own repo is a
good idea.

As a workaround, it was suggested to me that I could clone the congress
repo on the same server as horizon, copy the 3 files to the horizon
directory, and then delete the congress code that we don't need (ie,
everything but congress_dashboard). I don't really like that suggestion.
As many companies are moving towards containerized installations, I
think Anusha's suggestion is the best solution.

Please let me know how I can help.


Aimee Ukasick, AT&T


On 12/08/2016 10:41 PM, Anusha Ramineni wrote:
> Hi Tim, Aimee,
>
> Yes, ideally only congress_dashboard is required on the same server as
> horizon for horizon to discover the plugin, but right now
> congress_dashboard is also part of congress repo, so congress needs to
> be installed on the same server.
>
> I'm thinking for a while to move the repo to separate project, maybe
> its high time we move the congress_dashboard repo to separate project
> like other projects do? wdyt?
> http://docs.openstack.org/developer/horizon/plugin_registry.html
>
>
> Best Regards,
> Anusha
>
> On 9 December 2016 at 03:24, Tim Hinrichs <tim at styra.com
> <mailto:tim at styra.com>> wrote:
>
>     I wouldn't expect Congress needs to be on the same server as
>     Horizon.  Anusha, do you know for sure?
>
>     Tim
>
>
>     On Thu, Dec 8, 2016 at 1:20 PM Aimee Ukasick
>     <aimeeu.opensource at gmail.com <mailto:aimeeu.opensource at gmail.com>>
>     wrote:
>
>         All - we are looking into deploying Congress in its own container,
>         separate from the container that OpenStack is in. I know which
>         Congress
>         dashboard files need to be copied to Horizon, and from what I
>         can tell,
>         it looks like Congress and Horizon must be running on the same
>         server
>         for the Congress dashboard to work. Is this assumption correct?
>
>
>         Thanks!
>
>
>         Aimee Ukasick, AT&T
>
>
>
>
>
>         __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>         <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>         <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev