[openstack-dev] [Quantum] Horizon usecases of subnet/port operation

Dan Wendlandt dan at nicira.com
Wed Jul 25 05:08:24 UTC 2012


On Tue, Jul 24, 2012 at 10:13 AM, Akihiro MOTOKI <motoki at da.jp.nec.com>wrote:

> Hi netstackers,
>
> I would like to ask about what operations are available on Dashboard
> and confirm the status of the work.
>
> (1) Can non-admin tenant/project create a network/subnet?
>
> Quantum v2 API allows non-admin tenants to create a network/subnet.
> When creating a subnet a tenant can assign any ip range to the subnet as it
> wants, so IP address overlapping in diffrent networks may happen.
> If IP address overlapping is not supported in Quantum Folsom, this may lead
> to some troublesome situation in L3 handling such as L3 forwarding, NAT...
>
> dhcp-overlapping-ips blueprint seems to have a good
> progress. This means Quantum allow ip address overlapping.
> In this case we do not need to take care of the issue and
> non-admin tenants can create a subnet as they wants.
>

Yes, that is exactly right.


>
> (2) Can admin tenant create/delete a port from dashboard?
>
> Usually port create/delete operations are not visibile in normal
> situations, e.g., a port is created automatically in a sequence of
> VM launching or subnet creation (with dhcp-agent).
>
> My question is whether port create/delete operations need to be available
> on Horizon?
>
> IMHO, port create/delete operations need not to be available in user panel
> (for normal user), and they are available for admin tenant.
>

For the most common use cases, you are correct.  There is no need for
tenants to explicitly create ports, as a service (e.g., Nova) will do that
on their behalf.

However, there is a use case where the tenant wants to specify some
specific parameters about a port that need to be specified before the VM is
booted (e.g., setting the MAC address or IP address of the port).  For this
use case, we're adding the ability to pass in a Quantum port-id, rather
than just a network-id, when using the --nic CLI command while creating a
VM (Yong is planning on working on this).   However, this is definitely a
more advanced use case, so we had planned on not supporting it in the first
cut of the Horizon/Quantum work.  So for now, I don't see a need for either
tenants or admins to create/delete ports explicitly.

Thanks again for your work on Quantum support in Horizon, I'm so happy to
see this getting more development attention.

Dan



>
>
> For more broader discussion, we post this mail to the list.
> I will appreciate you comments.
>
> Thanks,
> --
> Akihiro MOTOKI <motoki at da.jp.nec.com>
> Cloud System Research Laboratories, NEC Corporation
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20120724/c42ab098/attachment.html>


More information about the OpenStack-dev mailing list