Re: [openstack-dev] [vitrage] scenario evaluator not enabled by default

2016-08-14 Thread Yujun Zhang
Thanks for the expanation, Elisha. I understand the design now. But I could not find the statement which enables the evaluator after initial phase. Could you help to point it out? -- Yujun On Thu, Aug 11, 2016 at 11:42 PM Rosensweig, Elisha (Nokia - IL) < elisha.rosensw...@nokia.com> wrote: > T

Re: [openstack-dev] [mistral] Porting security-related utils, Context and dependencies to Mistral-Lib

2016-08-14 Thread Renat Akhmerov
Hi Ryan, Keeping in mind that 'mistral-lib' must not depend on ‘mistral’ below are my comments: I think porting keystone utils over to mistral-lib is OK, I don’t see any other options (‘mistral’ will depend on ‘mistral-lib’ but not the way around) Porting the entire mistral.context is OK too for

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-14 Thread Yingxin Cheng
Hi, I'm concerned with the dependencies between "os-capabilities" library and all the other OpenStack services such as Nova, Placement, Ironic, etc. Rather than embedding the universal "os-capabilities" in Nova, Cinder, Glance, Ironic services that will introduce complexities if the library versi

[openstack-dev] [oslo] RPC call not appearing to retry

2016-08-14 Thread Eric K
Hi all, I'm running into an issue with oslo-messaging PRC call not appearing to retry. If I do oslo_messaging.RPCClient(transport, target, timeout=5, retry=10).call(self.context, method, **kwargs) using a topic with no listeners, I consistently get the MessagingTimeout exception in 5 seconds, with

[openstack-dev] [daisycloud-core] Daisy installer demo is out

2016-08-14 Thread hu . zhijiang
Hi All, Daisycloud-core team are pleased to annonce the first release of Daisy OpenStack Installer. You can download the demo from http://www.daisycloud.org/static/files/installdaisy_el7_noarch.bin. and the corresponding document is here: http://www.daisycloud.org/static/files/demo_how_to.docx

Re: [openstack-dev] [OpenStack-docs] [Magnum] Using common tooling for API docs

2016-08-14 Thread Anne Gentle
Hi Hongbin, Thanks for asking. I'd like for teams to look for ways to innovate and integrate with the navigation as a good entry point for OpenAPI to become a standard for OpenStack to use. That said, we have to move forward and make progress. Is Lars or anyone on the Magnum team interested in th

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

2016-08-14 Thread Patrick East
In-case folks are not following comments on all the various forums for this discussion. We've got changes up to address the concerns raised so far on the immediate problem: Devstack (changing default config option to be shared): https://review.openstack.org/341744 Cinder (release note): https://r

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

2016-08-14 Thread Sean McGinnis
On Sat, Aug 13, 2016 at 08:04:13PM -0700, Joshua Harlow wrote: > Sean McGinnis wrote: > >On Fri, Aug 12, 2016 at 05:55:47AM -0400, Sean Dague wrote: > >>A devstack patch was pushed earlier this cycle around os-brick - > >>https://review.openstack.org/341744 > >> > >>Apparently there are some os-bri

[openstack-dev] [nova][cinder][oslo] Lets move forward on making oslo.privsep logging more sane

2016-08-14 Thread Matt Riedemann
If you hadn't noticed yet, the n-cpu logs are super chatty due to privsep logging everything from debug=True at warning level: http://logs.openstack.org/15/355215/1/check/gate-tempest-dsvm-neutron-src-python-novaclient/b92bced/logs/screen-n-cpu.txt.gz?level=TRACE I opened a bug for this awhile

Re: [openstack-dev] [nova] Thoughts on testing novaclient functional with neutron

2016-08-14 Thread Matt Riedemann
On 8/12/2016 1:03 PM, Dean Troyer wrote: On Fri, Aug 12, 2016 at 10:13 AM, Matt Riedemann mailto:mrie...@linux.vnet.ibm.com>> wrote: Another idea is the base functional test that sets up the client just checks the keystone service catalog for a 'network' service entry, somewhere in h

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-14 Thread Jay Pipes
Word up, Travis :) A few comments inline, but overall I'm looking forward to collaborating with you, Steve, and all the other Searchlight contributors on os-capabilities (or os-caps as Sean wants to rename it ;) On 08/11/2016 08:00 PM, Tripp, Travis S wrote: [Graffit] was originally co-sponsor

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

2016-08-14 Thread Joshua Harlow
Clint Byrum wrote: Excerpts from Joshua Harlow's message of 2016-08-13 20:04:13 -0700: The larger issue here IMHO is that there is now a API around locking that might be better suited targeting an actual lock management system (say redis or zookeeper or etcd or ...). The more I look at this,

Re: [openstack-dev] [cinder][drivers] Backend and volume health reporting

2016-08-14 Thread John Griffith
On Sun, Aug 14, 2016 at 2:11 AM, Avishay Traeger wrote: > Hi all, > I would like to propose working on a new feature for Ocata to provide > health information for Cinder backends and volumes. Currently, a volume's > status basically reflects the last management operation performed on it - > it w

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

2016-08-14 Thread Jay Bryant
I agree with Duncan here. Driver removal has been an important tool to keep only maintained drivers in the tree and a way to get attention to ignored drivers. I hate to see the tag removed but think we need to stay true to the approach we have been taking. Re-addressing the meaning of the tag with

[openstack-dev] [neutron] Newton Midcycle - Tuesday dinner

2016-08-14 Thread John Schwarz
Hi guys, For those of us who'll arrive on Tuesday to Cork, Martin Hickey has arranged a dinner at "Gourmet Burger Bistro" [1], 8 Bridge Street, at 19:30. Last I heard the reservation was for 15 people so this should accommodate all who filled out in [2] that they will arrive on Tuesday. [1]: http

[openstack-dev] [cinder][drivers] Backend and volume health reporting

2016-08-14 Thread Avishay Traeger
Hi all, I would like to propose working on a new feature for Ocata to provide health information for Cinder backends and volumes. Currently, a volume's status basically reflects the last management operation performed on it - it will be in error state only as a result of a failed management operat