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
Joshua Harlow wrote:
Ihar Hrachyshka wrote:
In Neutron, we have a need to allocate random but unique addresses and
such. For that matter, we have a concept of exclusive resources:
https://github.com/openstack/neutron/tree/master/neutron/tests/common/exclusive_resources
Ihar Hrachyshka wrote:
In Neutron, we have a need to allocate random but unique addresses and
such. For that matter, we have a concept of exclusive resources:
https://github.com/openstack/neutron/tree/master/neutron/tests/common/exclusive_resources
that are relying on locks and shared file based
Excerpts from Joshua Harlow's message of 2016-10-17 20:59:23 -0700:
> I think doug (he can correct me if I am wrong) was more wondering the
> question of 'why would you want to use random data' in a test vs using
> known fixed data. When a test fails it can be quite hard to identify the
>
In Neutron, we have a need to allocate random but unique addresses and
such. For that matter, we have a concept of exclusive resources:
https://github.com/openstack/neutron/tree/master/neutron/tests/common/exclusive_resources
that are relying on locks and shared file based resource
I think doug (he can correct me if I am wrong) was more wondering the
question of 'why would you want to use random data' in a test vs using
known fixed data. When a test fails it can be quite hard to identify the
reason if certain data that the test uses is randomized for each run.
Ha,thanks for your link, it's absolutely much clearer and more correct
here, and how do you think of this util function itself?
Kiall Mac Innes 于2016年10月18日周二 上午12:03写道:
> We tend to try stick with the various TEST-NET CIDRs etc as well in
> Designate, and document them here:
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
We tend to try stick with the various TEST-NET CIDRs etc as well in
Designate, and document them here:
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
Excerpts from TommyLike Hu's message of 2016-10-17 14:46:36 +:
> 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
OK, I guess the real question I had is why use *random* addresses.
Because that
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
Excerpts from TommyLike Hu's message of 2016-10-17 09:56:15 +:
> 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)
12 matches
Mail list logo