[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: OpenStack PEP



The longer this gets, the more comments I have :) I left line comments at https://github.com/openshift/openshift-pep/pull/7
Easier to see the document at https://github.com/calfonso/openshift-pep/blob/369a659fa0708c71176bed53185623b1c116f6ef/openshift-pep-openstack.md but of course you can't see or leave line notes there and the commit may change...

More below -

----- Original Message -----
> From: "Clayton Coleman" <ccoleman redhat com>
> To: "Michael McGrath" <mmcgrath redhat com>
> Cc: dev lists openshift redhat com
> Sent: Monday, July 29, 2013 9:20:49 PM
> Subject: Re: OpenStack PEP
> 
> The auth pep will probably point to this pep where openstack keystone
> integration is concerned.  To me feels more natural to put the bulk
> here, simply because not every Openshift deployment would be on
> openstack.

Err, that seems to me a reason to put the bulk at the auth PEP, and just point there. The only thing that I see needing to be here is the part about Keystone integration and perhaps a brief synopsis of the roles.

> On Jul 29, 2013, at 3:09 PM, Michael McGrath <mmcgrath redhat com>
> wrote:
> 
> > ----- Original Message -----
> >> From: "Chris Alfonso" <calfonso redhat com>
> >> To: dev lists openshift redhat com
> >> Sent: Monday, July 29, 2013 3:27:47 PM
> >> Subject: OpenStack PEP
> >> 
> >> I would like to get folks looking at the OpenStack PEP draft.
> >> Please leave
> >> any comments you might have in the commit. Thanks!
> >> 
> >> https://github.com/openshift/openshift-pep/pull/7
> > 
> > Looks great Chris thanks for writing this up (and to those who
> > helped), a question and a comment:
> > 
> > 1)
> >> Initial Install -> The Second Example:
> >> "The second example template should include the ability to scale
> >> brokers which would include a component to monitor broker
> >> utilization, bringing brokers in and out of rotation using Heat's
> >> load balancing (haproxy), and cross broker node capacity checking
> >> (to avoid duplicate scale events). The job scheduling
> >> implementation the brokers use to track scaling events should be
> >> used to ensure no duplicate scale up or down events are sent to
> >> Heat."
> > 
> > "Using heat's load balancing" is this something provided by
> > OpenStack or something that would exist on one of the broker
> > virtual machines?
> > 
> > 2)
> > The abstract is missing notes about authentication and user/group
> > management which will likely be covered in a different pep and
> > should link to that pep.  This actually looks like it's about
> > 2/3rds of the PEP and I'm a little confused why it's grouped in
> > with the OpenStack PEP.
> > 
> >    -Mike
> > 
> > _______________________________________________
> > dev mailing list
> > dev lists openshift redhat com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]