Open Stack

In previous conversations, my understanding was the UI implementation had
to be very scheduler dependent to be very effective. Is my understanding
accurate? If so, the complexity grows with the number supported.

David

On Thu, Jun 4, 2015 at 1:59 PM, Bradley Jones (bradjone) <bradjone at cisco.com
> wrote:

>  It’s difficult to put a quantifiable figure on how big a work item this
> is but I can try to give an overview of the steps required.
>
>  The first step will be to extend the Horizon API to include CRUD
> operations that we need to perform with Magnum. Assuming that there are no
> issues here and API changes/additions are not required at this point, we
> can begin to flesh out how we would like the UI to look. We will aim to
>  reduce the amount of Magnum specific UI code that will need to be
> maintained by reusing components from Horizon. This will also speed up the
> development significantly.
>
>  In version 1 of Magnum UI a user should be able to perform all normal
> interactions with Magnum through the UI with no need for interaction with
> the python client.
>
>  Future versions of Magnum UI would include admin specific views and any
> additional Magnum specific UI components we may want to add (maybe some
> visualisations).
>
>  That is a brief overview of my vision for this effort and I believe that
> version 1 should comfortably be achievable this release cycle.
>
>  Thanks,
> Brad Jones
>
>   On 4 Jun 2015, at 19:49, Brad Topol <btopol at us.ibm.com> wrote:
>
> How big a work item is this?
>
>
> Brad Topol, Ph.D.
> IBM Distinguished Engineer
> OpenStack
> (919) 543-0646
> Internet:  btopol at us.ibm.com
> Assistant: Kendra Witherspoon (919) 254-0680
>
>
>
> From:        Thai Q Tran/Silicon Valley/IBM at IBMUS
> To:        "OpenStack Development Mailing List \(not for usage
> questions\)" <openstack-dev at lists.openstack.org>
> Date:        06/04/2015 02:20 PM
> Subject:        Re: [openstack-dev] [magnum][horizon] Making a dashboard
> for Magnum - need a vote from the core team
> ------------------------------
>
>
>
> I am interested but not sure how much time I have this release cycle. I
> can take on a more hands-off approach and help review to make sure that
> magnum-ui is align with future horizon directions.
>
> -----"Steven Dake (stdake)" <stdake at cisco.com> wrote: -----
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> From: "Steven Dake (stdake)" <stdake at cisco.com>
> Date: 06/04/2015 11:03AM
> Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum -
> need a vote from the core team
>
> Hey folks,
>
> I think it is critical for self-service needs that we have a Horizon
> dashboard to represent Magnum.  I know the entire Magnum team has no
> experience in UI development, but I have found atleast one volunteer
> Bradley Jones to tackle the work.
>
> I am looking for more volunteers to tackle this high impact effort to
> bring Containers to OpenStack either in the existing Magnum core team or as
> new contributors.   If your interested, please chime in on this thread.
>
> As far as “how to get patches approved”, there are two models we can go
> with.
>
> Option #1:
> We add these UI folks to the magnum-core team and trust them not to +2/+A
> Magnum infrastructure code.  This also preserves us as one team with one
> mission.
>
> Option #2:
> We make a new core team magnum-ui-core.  This presents special problems if
> the UI contributor team isn’t large enough to get reviews in.  I suspect
> Option #2 will be difficult to execute.
>
> Cores, please vote on Option #1, or Option #2, and Adrian can make a
> decision based upon the results.
>
> Regards
> -steve
>
> __________________________________________________________________________
> 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*
> <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
>
> __________________________________________________________________________
> 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
>
>
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150604/bcaa8a31/attachment.html>