Comment 3 for bug 1606741
Revision history for this message
| Zhixin Li (lizhixin) wrote Re: Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hi, Swaminathan:
Honestly, I am not so agree running a dvr_snat-mode l3-agent on a compute node. But I still consider it as a bug.
First, we permit a l3-agent runs in a compute node with dvr_snat and it works well for most services unless metadata proxy, so we should make metadata proxy service available as it may.
Second, many developers like building openstack test environment with all-in-one mode for a convenience. If we run dvr_snat l3-agent on compute node (all-in-one), we can simplify our deployment in building our l3-ha and dvr environment, otherwise we should add 2 extra network nodes, which is wasteful in time and compute resource.
Finally, should we separate network and computer nodes so strictly? We can also enable snat in a computer-node l3-agent, like dragonflow. In that case, we can have more ha routers and average snat traffics within each nodes, which may be useful in a small-scale environment.
Maybe running dvr_snat mode in a compute-node l3-agent is a terrible thought in technological, but I think it is useful in some case and there may be someone use it with some reason. Therefore, I think it's necessary to fix this bug.
Cheers.