Re: [openstack-dev] [TripleO] FreeIPA integration

On Tue, Apr 5, 2016 at 11:36 AM, Steven Hardy wrote: > On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote: > > I finally have enough understanding of what is going on with Tripleo to > > reasonably discuss how to implement solutions for some of the main > security > >

Re: [openstack-dev] [TripleO] FreeIPA integration

On the certificate management side I had presented this blueprint* https://review.openstack.org/#/c/282307/ *which proposes FreeIPA as the reference solution. There the steps are described however, I did leave away where the FreeIPA instance will be

Re: [openstack-dev] [tricircle]weekly meeting of Apr. 6

Hi Chaoyi, Thank you for team mtg every week. One day, we may need to discuss about trust relationship considering secure connection and no-latency issue between top and bottoms over BGP across ASs, in short between DCs. Any thought would be appreciated as usual. Cheers, Shinobu On Tue, Apr 5,

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On Fri, Apr 01, 2016 at 04:39:02PM +, Fox, Kevin M wrote: >Why is imperative programming always brought up when discussing >conditionals in the templates? We are not wanting anything imperative. The >heat engine still picks the final ordering of things. We just want to give >it

[openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

Hi! I'd like to propose Anton to the ironic-inspector core reviewers team. His stats are pretty nice [1], he's making meaningful reviews and he's pushing important things (discovery, now tempest). Members of the current ironic-inspector-team and everyone interested, please respond with your

Re: [openstack-dev] [Fuel][library] Update of astute.yaml fixtures and noop tests

Hi folks, we've merged all the changes related to fixtures update [0] and bugfix to unblock noop tests [1]. So if you see -1 from fuel_noop_tests [2] in tests not related to your patch, then please rebase. Regards, Alex [0] https://review.openstack.org/#/q/topic:update-fixtures-to-9.0 [1]

Re: [openstack-dev] [telemetry] Newton design summit planning

On Tue, 5 Apr 2016, Julien Danjou wrote: Any items/ideas we could discussion in this remaining sessions? Any project we could/should invite to discuss with us? Nova has started work on versioned notifications:

Re: [openstack-dev] [neutron][api] advanced search criteria

Armando M. wrote: On 4 April 2016 at 17:08, Jay Pipes wrote: On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: - why do we even need to control those features with configuration options? can we deprecate and remove them? This would be my choice.

Re: [openstack-dev] FW: Regarding code debug information

There are developers doc which can help you to understand particular component framework and codes. http://docs.openstack.org/developer/openstack-projects.html Depends on project you want to deep dive you can check their doc. For example Nova nova one can be found here -

[openstack-dev] [telemetry] Newton design summit planning

Hi folks, I've started to fill in the blank for our next design summit sessions. The schedule is at: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Telemetry%3A We still have the 2 first work sessions empty, because I ran out of idea. I've used the Etherpad we

[openstack-dev] FW: Regarding code debug information

Dear All, I am newbie for openstack development and trying to understand the flow using code base. As the code base is very huge need your support to understand it. Please let me know if there are any such way to debug the code or analyse it. Any kind of help will be appreciated. Thanks &

[openstack-dev] [Fuel] Help with reviews - modularisation.

Hi Fuelers! I kindly ask you to review my patches [0] and [1]. There is a "big thing" going on there. I'm trying to decouple Volume Manager from Nailgun. It's a first step towards Fuel modularisation, which will also be an example for other developers: "How to implement Nailgun extensions".

[openstack-dev] [cross-project] [all] Quotas and the need for reservation

Hi All, As part of the cross project Quota library effort [1] there has been a discussion around the need for reservations or getting rid of reservations altogether. It is believed that reservation help to to reserve a set of resources beforehand and hence eventually preventing any other

[openstack-dev] [tricircle]weekly meeting of Apr. 6

Hi, We have a very good discussion about cross OpenStack L2 networking last week: https://etherpad.openstack.org/p/TricircleCrossPodL2Networking Let's continue the discussion and other topics in this weekly meeting. IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every

Re: [openstack-dev] [Fuel][Bareon][Ironic] The future of integration module

Hello, At the beginning of the work, we've taken fuel-agent driver from Ironic team and customized it. Here is main features, which were created during development for Cray (all of them are now part of bareon-ironic): 1. deploy-config could be stored in multiple places (image meta,

Re: [openstack-dev] [monasca][release] missing build artifacts

Davanum Srinivas wrote: Please see below: On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann wrote: Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: Hi Doug, You had mentioned issues with three repos: 1. monasca-ceilometer 2. monasca-log-api 3.

Re: [openstack-dev] [TripleO] FreeIPA integration

On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote: > I finally have enough understanding of what is going on with Tripleo to > reasonably discuss how to implement solutions for some of the main security > needs of a deployment. > > > FreeIPA is an identity management solution that can

Re: [openstack-dev] [sahara][release] missing build artifacts

michael mccune wrote: On 04/01/2016 04:48 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2016-04-01 16:27:42 -0400: Sahara team, We noticed in our audit of the links on http://releases.openstack.org/mitaka/index.html that the links to the build artifacts for sahara-extras

Re: [openstack-dev] [vitrage] vitrage topology show

I agree, The client should pass the query Eyal On Tue, Apr 5, 2016 at 9:23 AM, Afek, Ifat (Nokia - IL) wrote: > Hi, > > vitrage topology show has a different behavior for a tree and a graph. > > In case it is called with no query: > * For a tree it returns the node,

Re: [openstack-dev] [OpenStack-Dev][Manila] BP https://blueprints.launchpad.net/manila/+spec/access-group

Hi Everyone, https://wiki.openstack.org/wiki/Manila/design/access_groups Created a wiki page to describe different approaches, their comparison, to achieve the goal. It would be helpful to receive your comments, based on your experiences, which approach suits real life needs better. Thanks

[openstack-dev] [vitrage] vitrage topology show

Hi, vitrage topology show has a different behavior for a tree and a graph. In case it is called with no query: * For a tree it returns the node, zone, host and instances * For a graph it returns everything I don't think that the selected topology representation should affect the type of

<    1   2