Open Stack

On Wed, Jan 8, 2014 at 2:35 PM, Anne Gentle <anne at openstack.org> wrote:

> Hi all,
> I wanted to get some input on the os-networks extension documentation as
> it's unclear right now. If you look at
> http://api.openstack.org/api-ref-compute-ext.html#ext-os-networks, you
> see two different POST calls, one disassociates the host from a specified
> network, the other disassociates a specified network from a project. Both
> requests are simple calls with null in the example, but I don't understand
> how these would be used in a real-world scenario. I see it as:
> 1. create network
> 2. boot server connected to that network with POST
> v2/{tenant_id}/os-networks/{id}/action
>
>
> {
>     "associate_host": "testHost"
> }
>
> 3. then disassociate the same server (seems to take a name?) as needed. I
> think the null might be incorrect here, and "testHost" would be a better
> example.
> POST v2/{tenant_id}/os-networks/{id}/action
>
>
> {
>     "disassociate_host": null
> }
>
> 4. And if you ever need to disassociate all the servers from a particular
> tenant, you'd use the second POST call below:
> POST v2/{tenant_id}/os-networks/{id}/action
>
>
> {
>     "disassociate": null
> }
>
>
> Any thoughts? I can explain further if needed.
>

Oh, and one more problem with the examples, it looks like we also have:
POST v2/{tenant_id}/os-networks/{id}/action


{
    "disassociate_project": null
}


Are these two last dissociate examples incorrect? I'll log a doc bug if
someone can confirm.

Thanks,
Anne


> Thanks,
> Anne
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140108/0e83ecdc/attachment.html>