[openstack-dev] [neutron][taas] Proposal of Dashboard for TaaS

Anil Rao anil.rao at gigamon.com
Tue Mar 8 22:29:33 UTC 2016

Thanks Soichi and Kaz for your work on implementing Horizon (dashboard) support for TaaS. The proposal (with screen shots) discussed in our recent IRC meeting look very nice. Here are some additional suggestions for improvement.

1.       General

a.       When a port is being selected (for a tap-service instance or a tap-flow) it would be nice to also provide some extra information associated with that port, such as the VM it belongs to and the IP address.  This will look very similar to what is being done today when associating a floating IP with a VM vNIC. The extra context will allow users to identify their source and destination end-points with more ease. If a VM is not currently associated with a port then the extra information is not necessary.

b.      When selecting the traffic monitoring direction, it would be nice to provide two check boxes, one for 'ingress' and the other for 'egress'. A user wishing to monitor a port in both directions can select both check boxes. I feel this looks better than having an option  called 'both'.

2.       Using the Tap Services Tab

a.       Allow tap-flow-create and tap-flow-delete operations to also be carried out from here. This will let users who prefer working in this fashion get everything done from the same place.

b.      Provide a way to list tap flows currently associated with a tap service.

c.       Allow multiple tap-flows to be created at the same time. Let the user pick multiple source ports (and traffic monitoring directions) and have all of them attached to a designated tap-service.

3.       Using the Network Topology Tab

a.       Allow tap-create and tap-delete operations to be also carried out from here. This will allow users who prefer working in this fashion get everything done from the same place. The user can pick the destination port (from one of the existing VMs) in the same way that a source port is picked when creating a tap-flow.

b.      Color code the VM whose vNIC is attached to the destination port of a tap-service.

c.       BONUS: Allow the user to click on a VM that is serving as the destination side of a tap-service and highlight all the VMs that are attached to tap-flows associated with that tap-service.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160308/185bd597/attachment.html>

More information about the OpenStack-dev mailing list