[openstack-dev] [Cinder] [Nova] Extend attached volume

2017-04-01 Thread TommyLike Hu
There was a time when this feature had been both proposed in Cinder [1] and Nova [2], but unfortunately no one (correct me if I am wrong) is going to handle this feature during Pike. We do think extending an online volume is a beneficial and mostly supported by venders feature. We really don't want

Re: [openstack-dev] [Cinder] [Nova] Extend attached volume

2017-04-03 Thread TommyLike Hu
Hey, Mathieu Thanks for bringing us the solution, Jay and I are willing to help if you are looking for someone to coordinate at the Cinder side. TommyLike.Hu On 2017-04-04 08:50 , Mathieu Gagné Wrote: Hi, On Mon, Apr 3, 2017 at 8:40 PM, Jay S Bryant wrote: > > Thank you for sharing this.   Nice

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

2017-08-02 Thread TommyLike Hu
Thank you Sean and Cinder team. It's my honor to be a member of the big family, looking forward to work with all of you! Sean McGinnis 于2017年8月3日周四 上午9:21写道: > I'm a little late getting back to it, but I have just added TommyLike > to the Gerrit and Launchpad groups. > > Welcome to the Cinder co

[openstack-dev] [security] Script injection issue

2017-11-17 Thread TommyLike Hu
Hey all, Recently when we integrating and testing OpenStack services. We found there is a potential script injection issue that some of our services accept the input with special character [1] [2], for instance we can create an instance or a volume with the name of 'script inside'. One of the

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

2017-11-19 Thread TommyLike Hu
+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 (zhongjun on irc, zhongjun2 on gerri

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

2017-11-19 Thread TommyLike Hu
[api] to make sure the API (SIG?) sees this too >> >> On Fri, Nov 17, 2017 at 3:22 AM, TommyLike Hu >> wrote: >> > Hey all, >> > Recently when we integrating and testing OpenStack services. We >> found >> > there is a potential script injection is

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

2017-11-19 Thread TommyLike Hu
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

2017-11-19 Thread TommyLike Hu
likely that > consumers will assume they don't need to bother. > > On 20 Nov 2017 2:18 am, "TommyLike Hu" wrote: > >> 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

[openstack-dev] [api-wg] [api] [cinder] [nova] Support specify action name in request url

2018-01-18 Thread TommyLike Hu
Hey all, Recently We found an issue related to our OpenStack action APIs. We usually expose our OpenStack APIs by registering them to our API Gateway (for instance Kong [1]), but it becomes very difficult when regarding to action APIs. We can not register and control them seperately because them

Re: [openstack-dev] [api-wg] [api] [cinder] [nova] Support specify action name in request url

2018-01-24 Thread TommyLike Hu
8.html > > [3] > http://lists.openstack.org/pipermail/openstack-dev/2016-December/109248.html > > [4] > https://developer.openstack.org/api-ref/application-container/#manage-containers > > > > Best regards, > > Hongbin > > > > *From:* TommyLike Hu [mai

Re: [openstack-dev] [cinder] [manila] Performance concern on new quota system

2018-03-09 Thread TommyLike Hu
is seems a good idea, but not sure whether it could cover all of the cases we have in our quota system and whether can be easily integrated into cinder, can you share more detail on this? Thanks TommyLike Gorka Eguileor 于2018年3月9日周五 下午8:11写道: > On 09/03, TommyLike Hu wrote: > > Hey all,

[openstack-dev] [cinder] Support share backup to different projects?

2018-03-19 Thread TommyLike Hu
Now Cinder can transfer volume (with or without snapshots) to different projects, and this make it possbile to transfer data across tenant via volume or image. Recently we had a conversation with our customer from Germany, they mentioned they are more pleased if we can support transfer data accros

Re: [openstack-dev] [cinder] Support share backup to different projects?

2018-03-20 Thread TommyLike Hu
n 3/19/2018 10:55 PM, TommyLike Hu wrote: > > Now Cinder can transfer volume (with or without snapshots) to different > projects, and this make it possbile to transfer data across tenant via > volume or image. Recently we had a conversation with our customer from > Germany, they me

Re: [openstack-dev] [cinder] Support share backup to different projects?

2018-03-20 Thread TommyLike Hu
e it as a topic in > tomorrow's team meeting if you wish. > > Jay > > On 3/20/2018 8:54 PM, TommyLike Hu wrote: > > > Thanks Jay, > The question is AWS doesn't have the concept of backup and their > snapshot is incremental backup internally and will be finllay st

Re: [openstack-dev] [cinder] Support share backup to different projects?

2018-03-21 Thread TommyLike Hu
see and read the content of that backup. Gorka Eguileor 于2018年3月21日周三 下午7:15写道: > On 20/03, Jay S Bryant wrote: > > > > > > On 3/19/2018 10:55 PM, TommyLike Hu wrote: > > > Now Cinder can transfer volume (with or without snapshots) to different > > > projects,

[openstack-dev] Fwd: [cinder] OpenStack Hackathon for Rocky release

2018-06-12 Thread TommyLike Hu
Forward the next hackathon session and add cinder tag :) -- Forwarded message - From: Fred Li Date: 2018年6月12日周二 下午4:40 Subject: [openstack-dev] OpenStack Hackathon for Rocky release To: OpenStack Development Mailing List (not for usage questions) < openstack-dev@lists.openstack.o

[openstack-dev] [Cinder] Refactor reset-status command for cinder resources at client side

2016-12-22 Thread TommyLike Hu
Hi cinder members, Eharney recently add a comment about 'resource-reset-status' command here [1] on Dec 22, and I'd like to paste his comment here to get more attention and discussion before the patch can go on. *I'd like to discuss the general design here and get input from others before

[openstack-dev] [cinder] [oslo] privsep socket's client receive thread may crash without attention

2016-09-13 Thread TommyLike Hu
Hello everyone: I found an error when backing up a volume with oslo_privsep,it seems that the client channel use a thread to receive socket message,but the thread may crash with inner exception unhandled while the main procedure continues,so I report a bug and upload a patchset to fix: https://r

[openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

2016-10-17 Thread TommyLike Hu
When I handle some stuff related to Manila recently, I found a case which may be suitable for Oslo, Anyhow I put it in the maillist so it can be discussed before I put it in action. In testcase, we need a function(maybe 2) to generate random ip address (or network), also they should in the range of

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

2016-10-17 Thread TommyLike Hu
It's used in testcase already, and basic codes is from here: https://github.com/openstack/manila/blob/master/manila_tempest_tests/utils.py#L93 Doug Hellmann 于2016年10月17日周一 下午10:13写道: > Excerpts from TommyLike Hu's message of 2016-10-17 09:56:15 +: > > When I handle some stuff related to Manil

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

2016-10-17 Thread TommyLike Hu
Hmm,it's used to generate the ip address for validation or rule checking, Meanwhile add some randomness. Of course it's unreasonable the case you mentioned, please check the existed cases [1] and [2] [1] https://github.com/openstack/manila/blob/master/manila_tempest_tests/tests/api/base.py#L828 [2

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

2016-10-17 Thread TommyLike Hu
> > > http://docs.openstack.org/developer/designate/developer-guidelines.html#example-dns-names-and-ip-space > Thanks, > Kiall > > > On 17/10/16 10:56, TommyLike Hu wrote: > > When I handle some stuff related to Manila recently, I found a case which > may be suitable for Osl

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

2016-10-18 Thread TommyLike Hu
Thanks for your explicit explanations,I even misunderstand(maybe superficial understand) the intentions of the random IP when I set up this thread :) Ihar Hrachyshka 于2016年10月19日周三 上午12:05写道: > (To clarify for those not part of the neutron dev team, ‘fullstack’ in > neutron gate is not devstack/t

Re: [openstack-dev] [Cinder] No weekly meeting

2016-10-19 Thread TommyLike Hu
Cool, wish I could join the next Summit~ Sean McGinnis 于2016年10月19日周三 下午4:57写道: > Hello all, > > I know there are a lot of folks travelling for the Summit already. There > are no agenda items added to the weekly meeting wiki, so I am going to > cancel this weeks meeting. > > If there are any impo

Re: [openstack-dev] [Cinder] Proposed logo

2016-10-26 Thread TommyLike Hu
Vroom! Looks like a Ferrari in OpenStack Sean McGinnis 于2016年10月26日周三 下午3:55写道: > Hey team, > > Attached is the proposed new logo for the Cinder project. I think some > have already seen this, so making sure everyone gets a chance to see it > before it's finalized. > > Sean > (smcginnis)_

[openstack-dev] [manila] spec detail of IPv6's export locations

2016-11-13 Thread TommyLike Hu
Hey manila memebers and driver maintainers, I wanna set up an new thread to talk about the proper and better exprienced way for both end users and drivers who want use or support IPv6 in manila, and I wish this can be discussed and optimised before the spec[1] can get ready to the next re