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

RE: OpenStack PEP

-------- Original message --------
From: Michael McGrath <mmcgrath redhat com>
Date: 07/29/2013 3:08 PM (GMT-07:00)
To: Chris Alfonso <calfonso redhat com>
Cc: dev lists openshift redhat com
Subject: Re: OpenStack PEP

----- 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:

> 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?

It's a separate host managed by openstack, configured by heat.

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.

I just gathered info from the authentication thread and overlapped what keystone could do. This PEP has definitely grown in scope.


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