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

Re: OpenStack PEP



It might even make sense for this to be a frequently updated pep, where we leave a number of topics (like *aaS integration) to be filled out later.

On Jul 29, 2013, at 7:40 PM, Joe Fernandes <jofernan redhat com> wrote:

> The Abstract and Motivation sections talk only about installation and autoscaling of OpenShift infrastructure on OpenStack.  But the PEP actually covers other topics like Authentication integration with Keystone, LBaaS integration, etc.
> 
> I think it makes sense to have a broad PEP that covers all the possible OpenShift/OpenStack integration points in one document, but you just need to update the Abstract/Motivation sections to reflect that.  Then maybe clearly delineate each integration point as a separate section and propose a priority (i.e. which ones should be tackled first).
> 
> In the Futures section I might also add Ceilometer integration for usage metering, chargeback and monitoring OpenShift infrastructure & apps.  I am also interested where OpenStack is going in areas like Linux Containers support and Heat for application orchestration and how those potentially complement/overlap with OpenShift.
> 
> 
> -Joe
> 
> 
> ----- 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.
>> 
>> 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]