Re: [openstack-dev] [security] [api] Script injection issue

Based on my understanding. the BASIC LIMITATION in the API here is only a guidance or suggestion from community. It defines the default API behaviour and also configurable. BTW, OpenStack now doesn't have an explicit rule for valid user input (such as name and description), and this is

Re: [openstack-dev] [security] [api] Script injection issue

But the filtering requirements are going to be different for different front ends, and we can't hope to catch them all. Trying to do any filtering at the cinder/nova API level just provides a false sense of security - horizon and other UI *have* to get their escaping right. If you put incomplete

Re: [openstack-dev] 回复： [manila] Nominating Zhong Jun (zhongjun) for Manilacore

+1. Jun has been making valuable contributions to Manila for a long time. Very well deserved! Xing On Sun, Nov 19, 2017 at 9:06 PM, jiaopengju wrote: > +1 for zhongjun! > > 原始邮件 > *发件人:* Goutham" > *收件人:* OpenStack Development

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG

On Sun, Nov 19, 2017 at 11:39 PM, Chandan kumar wrote: > Hello, > > On Sun, Nov 19, 2017 at 7:44 PM, Ghanshyam Mann > wrote: >> On Sat, Nov 18, 2017 at 12:41 AM, Andrea Frittoli >> wrote: >>> >>> >>> On Fri, Nov 17, 2017

Re: [openstack-dev] [security] [api] Script injection issue

Our API service is open to any client or any API consumer. We can not guarantee every frontend has the ability to protect themself from script injections. Although the specific cases would differ, the security issue is the same. If we have to keep asking them to add this support repeatedly, Can we

Re: [openstack-dev] [security] [api] Script injection issue

The special character is allowed in default, tested in nova's and cinder's master branch. And I guess most of the projects allow those characters as the community doesn't have a explicit red line for this :) Adam Heczko 于2017年11月17日周五 下午8:33写道： > Thanks TommyLike for this

[openstack-dev] 回复： [manila] Nominating Zhong Jun (zhongjun) for Manilacore

+1 for zhongjun! 原始邮件 发件人:Goutham" goutham.pachar...@netapp.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 发送时间:2017年11月20日(周一) 07:29 主题:[openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manilacore Hello Manila developers, I

Re: [openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manila core

+1 if I can vote:) Zhongjun is always a nice and hard working people. She keeps making a hug and continual contribution to Manila. Thanks TommyLike.Hu Ravi, Goutham 于2017年11月20日周一 上午7:30写道： > Hello Manila developers, > > > > I would like to nominate Zhong Jun

Re: [openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manila core

On 11/19/2017 06:29 PM, Ravi, Goutham wrote: Hello Manila developers, I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit) to be part of the Manila core team. Zhongjun has been an important member of our community since the Kilo release, and has, in the past few releases

Re: [openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manila core

A big plus 1 from me! Zhong as core is well deserved and exactly what our project needs! On Nov 19, 2017 6:31 PM, "Ravi, Goutham" wrote: > Hello Manila developers, > > > > I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit) > to be part of

Re: [openstack-dev] [tripleo] Migrating TripleO CI in-tree tomorrow - please README

Quick update - our plan worked quite well. https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3 Here's what has been done: - Migrate most of TripleO projects to zuul layout in-tree + backports to stable branches. - Some projects have broken gate and I plan to take a look on Monday -

Re: [openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manila core

+1! Zhong Jun has been a valuable member of the manila community and has contributed a lot to improving manila. On Sun, Nov 19, 2017 at 9:29 PM, Ravi, Goutham wrote: > Hello Manila developers, > > > > I would like to nominate Zhong Jun (zhongjun on irc,

[openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manila core

Hello Manila developers, I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit) to be part of the Manila core team. Zhongjun has been an important member of our community since the Kilo release, and has, in the past few releases made significant contributions to the

[Openstack] [heat] AutoScalingGroup and dependents

I am using OS::Heat::AutoScalingGroup in the following type of scenario resources: my_vm: type: SOME_TEMPLATE_WITH_A_VM_CONNECTED_TO_MULTIPLE_NETWORKS properties: networks: { get_attr: [my_networks, outputs_list, my_network] } my_networks: type:

Re: [Openstack] haproxy LB on Newton

On 19 Nov 2017, at 12:08, Turbo Fredriksson wrote: > So … “something” internally in OS changed. Any suggestions to what > or how to debug this? Ok, now that one works. I have not touched A THING! I left everything be and watched "Star Trek - Into Darkness”. So if I just leave

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG

Hello, On Sun, Nov 19, 2017 at 7:44 PM, Ghanshyam Mann wrote: > On Sat, Nov 18, 2017 at 12:41 AM, Andrea Frittoli > wrote: >> >> >> On Fri, Nov 17, 2017 at 12:33 PM Thierry Carrez >> wrote: >>> >>> Andrea Frittoli

Re: [Openstack-operators] [openstack-dev] [Neutron] Debug tool

Forwarding the mail to openstack-operator ML. I believe the operator list is a better to place to discuss this topic. This is about 'neutron-debug' command. https://github.com/openstack/neutron/blob/master/setup.cfg#L48 Thanks, Akihiro 2017-11-19 21:24 GMT+09:00 Gary Kotton

Re: [openstack-dev] [Neutron] Debug tool

Forwarding the mail to openstack-operator ML. I believe the operator list is a better to place to discuss this topic. This is about 'neutron-debug' command. https://github.com/openstack/neutron/blob/master/setup.cfg#L48 Thanks, Akihiro 2017-11-19 21:24 GMT+09:00 Gary Kotton

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG

On Sat, Nov 18, 2017 at 12:41 AM, Andrea Frittoli wrote: > > > On Fri, Nov 17, 2017 at 12:33 PM Thierry Carrez > wrote: >> >> Andrea Frittoli wrote: >> > [...] >> > during the last summit in Sydney we discussed the possibility of >> > creating an

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG

Hi It will be happy to participate and help in driving this effort Thanks Ofer On Sun, Nov 19, 2017 at 3:57 PM, Ofer Blaut wrote: > Hi > > On Fri, Nov 17, 2017 at 11:25 PM, Rochelle Grober < > rochelle.gro...@huawei.com> wrote: > >> First off, let me say I think this is a

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG

Hi On Fri, Nov 17, 2017 at 11:25 PM, Rochelle Grober < rochelle.gro...@huawei.com> wrote: > First off, let me say I think this is a tremendous idea. And, it's > perfect for the SIG concept. > > Next, see inline: > > Thierry Carrez wrote: > > Andrea Frittoli wrote: > > > [...] > > > during the

[openstack-dev] port mirroring to instance with openstack

Hi I built OpenStack environment using OPNFV. I started the instance on the compute node and confirmed the connection success. I implemented IDS on my instance. I want to do port mirroring other traffic to instances, but it does not go well. Succeeded to add flow entry to br-int and mirror

[openstack-dev] [Neutron] Debug tool

Hi, Out of interest is anyone using this tool? If so can you please let us know. This was marked as deprecated in about 18months ago in favor of a tool that was an idea that never actually materialized. Thanks Gary __

[Openstack] haproxy LB on Newton

I’m setting up (Open)LDAP on my old Newton installation (and no, I’m *NOT* upgrading!! Last time I did that, it took me two, three months to get back to a somewhat-working state), with the LDAP servers behind a HAProxy LB. I’m trying to have one at a time enabled to see if I can get them working

[openstack-dev] [heat] Split tempest plugin from heat

Hi All, As part of community goal[1] for Queens, we've completed the repo split and created the new project[2]. The next objective to is to use the new plugin in our jobs. As we've merged some changes after the split, I've synced them and fixed some minor issues before using it in the gate jobs.