Re: [openstack-dev] [tc][security] Item #5 of the VMT

Rob, Thanks! -steve From: Rob C mailto:hyaku...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Friday, June 3, 2016 at 4:40 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:opensta

[openstack-dev] [security][infra][tc] security-analysis repo needs +1 from Robert to be merged by Infrastructure

Robert, The infrastructure team will only merge new repos that are going into big tent repositories if the PTL +1s it (as in takes responsibility for it). The review is here: https://review.openstack.org/#/c/325049/ If you click through, the needs-by you will see how it relates to the VMT sect

Re: [openstack-dev] [nova] [placement] conducting, ovo and the placement api

> There was a conversation earlier this week in which, if I understood > things correctly, one of the possible outcomes was that it might make > sense for the new placement service (which will perform the function > currently provided by the scheduler in Nova) to only get used over its > REST API,

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, OK, please keep me posted once you done, thanks very much. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To:

[openstack-dev] [nova] [placement] conducting, ovo and the placement api

(Warning, there might be crazy ideas ahead, mostly sending this out to engender some discussion and if these ideas are indeed crazy use their debunking as ways to strengthen and clarifying existing plans.) There was a conversation earlier this week in which, if I understood things correctly, one

Re: [openstack-dev] [OpenStack-Infra] [Infra][tricircle] patch not able to be merged

Thank you for investigation and some manual operations to fix out the problem. If there would be anything to prevent such as unexpected behaviour, please let us know. Cheers, Shinobu On Fri, Jun 3, 2016 at 11:04 PM, Jeremy Stanley wrote: > On 2016-06-03 03:45:31 + (+), joehuang wrote: >

Re: [openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Kolla] About kolla-ansible reconfigure

Hu, Comments inline. From: "hu.zhiji...@zte.com.cn" mailto:hu.zhiji...@zte.com.cn>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Saturday, June 4, 2016 at 12:11 AM To: "OpenStack Developm

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

On 06/04/2016 01:53 AM, Morgan Fainberg wrote: > > On Jun 3, 2016 12:42, "Lance Bragstad" > wrote: >> >> >> >> On Fri, Jun 3, 2016 at 11:20 AM, Henry Nash > wrote: >>> >>> On 3 Jun 2016, at 16:38, Lance Bragstad

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Kolla] About kolla-ansible reconfigure

Hi Steven, Thanks for the information. Some further questions: > Reconfigure was not designed to handle changes to globals.yml. I think its a good goal that it should be able to do so, but it does not today. So waht is the prefered method to change kolla_internal_vip_address and make it effe