Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Netstack

[Quantum][Nova] requested_id and port spec

 

 

OpenStack netstack RSS feed   Index | Next | Previous | View Threaded


nachi at nttmcl

Jul 30, 2012, 5:33 PM

Post #1 of 3 (156 views)
Permalink
[Quantum][Nova] requested_id and port spec

Hi Dan,folks

As we talked in netstack IRC meetins, I submit this as bug.
https://bugs.launchpad.net/nova/+bug/1031096

I tried to write this, but the code looks very ugly in order to keep
backward compatibility.
So I wanna propose an alternative design.
In this design, we will use fixed_ip as a temporary identifier of the port.

1. create port
fixed_ip assigned

2. specify the fixed_ip in nova boot

3. If the fixed_ip is specified,
nova.network.quantumv2.api.API will check existing port who use the fixed_ip.

if there are existing port and device_id is None
use the port_id.

if there are no existing port.
create new port with the fixed_ip

This approach needs no client side change.

Thank you in advance
Nachi Ueno

--
Mailing list: https://launchpad.net/~netstack
Post to : netstack [at] lists
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp


gongysh at cn

Jul 30, 2012, 7:15 PM

Post #2 of 3 (145 views)
Permalink
Re: [Quantum][Nova] requested_id and port spec [In reply to]


Hi Nachi,
It is seemingly a way to make it work, but I think we are thinking to provide 'port-id' or just 'port' to specify the top resource in quantum API. fix ip is not one.

Besides, Port can be assigned to more than one fixed IP.

Imagine in horizon, we created many networks, ports and subnets, but when booting a VM, we use a fixed_ip to specify our resource indirectly.

By the way, we should use openstack-dev [at] list

Thanks
Yong Sheng Gong

-----netstack-bounces+gongysh=cn.ibm.com [at] lists wrote: -----To: openstack [at] lists, netstack [at] lists
From: Nachi Ueno
Sent by: netstack-bounces+gongysh=cn.ibm.com [at] lists
Date: 07/31/2012 08:33AM
Subject: [Netstack] [Quantum][Nova] requested_id and port spec

Hi Dan,folks

As we talked in netstack IRC meetins, I submit this as bug.
https://bugs.launchpad.net/nova/+bug/1031096"]https://bugs.launchpad.net/nova/+bug/1031096

I tried to write this, but the code looks very ugly in order to keep
backward compatibility.
So I wanna propose an alternative design.
In this design, we will use fixed_ip as a temporary identifier of the port.

1. create port
fixed_ip assigned

2. specify the fixed_ip in nova boot

3. If the fixed_ip is specified,
nova.network.quantumv2.api.API will check existing port who use the fixed_ip.

if there are existing port and device_id is None
use the port_id.

if there are no existing port.
create new port with the fixed_ip

This approach needs no client side change.

Thank you in advance
Nachi Ueno

--
Mailing list: https://launchpad.net/%7Enetstack"]https://launchpad.net/~netstack
Post to : netstack [at] lists
Unsubscribe : https://launchpad.net/%7Enetstack"]https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp"]https://help.launchpad.net/ListHelp



nachi at nttmcl

Jul 30, 2012, 8:38 PM

Post #3 of 3 (144 views)
Permalink
Re: [Quantum][Nova] requested_id and port spec [In reply to]

Hi Yong

> Hi Nachi,
> It is seemingly a way to make it work, but I think we are thinking to
> provide 'port-id' or just 'port' to specify the top resource in quantum API.
> fix ip is not one.
>
> Besides, Port can be assigned to more than one fixed IP.

Ah, It it true.
OK I'll implement port id version.

> Imagine in horizon, we created many networks, ports and subnets, but when
> booting a VM, we use a fixed_ip to specify our resource indirectly.

> By the way, we should use openstack-dev [at] list

Sorry, I changed my mail address recently. But launchpad rejects new
mail to receive.
I'll find way to fix this.

Thanks
Nachi

> Thanks
> Yong Sheng Gong
>
> -----netstack-bounces+gongysh=cn.ibm.com [at] lists wrote: -----
> To: openstack [at] lists, netstack [at] lists
> From: Nachi Ueno
> Sent by: netstack-bounces+gongysh=cn.ibm.com [at] lists
> Date: 07/31/2012 08:33AM
> Subject: [Netstack] [Quantum][Nova] requested_id and port spec
>
> Hi Dan,folks
>
> As we talked in netstack IRC meetins, I submit this as bug.
> https://bugs.launchpad.net/nova/+bug/1031096
>
> I tried to write this, but the code looks very ugly in order to keep
> backward compatibility.
> So I wanna propose an alternative design.
> In this design, we will use fixed_ip as a temporary identifier of the port.
>
> 1. create port
> fixed_ip assigned
>
> 2. specify the fixed_ip in nova boot
>
> 3. If the fixed_ip is specified,
> nova.network.quantumv2.api.API will check existing port who use the
> fixed_ip.
>
> if there are existing port and device_id is None
> use the port_id.
>
> if there are no existing port.
> create new port with the fixed_ip
>
> This approach needs no client side change.
>
> Thank you in advance
> Nachi Ueno
>
> --
> Mailing list: https://launchpad.net/~netstack
> Post to : netstack [at] lists
> Unsubscribe : https://launchpad.net/~netstack
> More help : https://help.launchpad.net/ListHelp
>

--
Mailing list: https://launchpad.net/~netstack
Post to : netstack [at] lists
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp

OpenStack netstack RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.