thanks for the "admin" clarify : )
here is more information about other extensions avoid the problem:
i read the policy.json file, find some other extension meet the same
problem and watch how they impl
for example. the quota api just shows like this
GET v2/{tenant_id}/os-quota-sets/{tenant_id} S
Thanks vish
I think it is better not to modify the wsgi file which is depended by
others, it will not be safe for other extensions
My opinion is that only modify the networks extension, for example, add
project-id along with network-id in body, so the NetworkController.add()
use the project-id fr
thanks
by compare the doc and the source code, i know the api reference is point
to the current stable, which means folsom.
there is no mistiness for me.
but if there is http://api.openstack.org/essex/api-ref.html,
http://api.openstack.org/folsom/api-ref.html,
http://api.openstack.org/grizzly/api-
I just looked at the code and it appears this is not possible through the
os_networks extension. This appears to be an oversight. It should probably
allow a project to be passed in.
Bug report here: https://bugs.launchpad.net/nova/+bug/1161441
That said, the first time a user boots an instance,
hello everyone:
i have a very simple question which confuses me for a long time:
how should i add a network to a project via rest api?
1) i'm admin of the whole cloud env essex, (i think the folsom is same in
this case)
2) using nova-network:vlan (if using flatdhcp, the associate action is
meanle
5 matches
Mail list logo