Open Stack

On 2013年08月07日 22:24, John Garbutt wrote:
> Hey,
>
> On 7 August 2013 14:42, Alex Xu <xuhj at linux.vnet.ibm.com> wrote:
>> On 2013年08月07日 17:38, John Garbutt wrote:
>>> multi-nic added an extra virtual interface on a seprate network, like
>>> adding a port:
>>>
>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi-nics.html
>> That just describe create instance with multinic, that we will support.
>> Still have problem
>> with action add_fixed_ip and remove_fixed_ip in extension multinic. Those
>> action
>> invoke inject_network_info and reset_network.
> Ah, sorry, my bad. That writes network data into xenstore (the new IP
> address), then calls the agent inside the VM to read that data, and
> apply the change in the VM, without the need to reboot.
Thanks for the info. Update the network by guest agent is not good way.
I prefer remove the extension multinic, but we can keep inject_network_info
and reset_network in extensions admin_actions.
>>> I agree we should probably slim down the neturon focused api extension.
>>>
>>> Howerver, it should probably include network-ids and port-ids for each
>>> port, if we still support both:
>>>       nova boot --image <img> --flavor <flavor> --nic net-id=<net1-id>
>>> --nic net-id=<net2-id> <vm-name>
>>> and this:
>>>      nova boot --image <img> --flavor <flavor> --nic port-id=<port-id>
>>> <vm-name>
>> Yes, we still support those. But why we need network-ids?
> I was just thinking about if a user creates their server with a network id:
>      nova boot --image <img> --flavor <flavor> --nic net-id=<net1-id>
> --nic net-id=<net2-id> <vm-name>
> Then nova list only shows port-ids, it seems a bit confusing.
User can get network id by port id. So I still prefer just port id.
> John
>