yahoo-eng-team team mailing list archive

[Armando Migliaccio <1239902@xxxxxxxxxxxxxxxxxx>]

Joe,

neutron-server is not strictly just API handling, it implements all
sorts of things: authN/authZ, server-side RPC communication handling
with agents (for those plugins that use agents), DB management etc.

Changing a name to be consistent across the board is the least of a
deployer's worry if OpenStack projects keep add/removing/moving tons of
options per release (let me tell you that I have been there and it's not
fun!). Also, since there's a counter-example (keystone), what does
changing neutron-server's name buy a deployer anyway?

Don't get me wrong, I don't have anything particular against the name
change, but I'd rather avoid the ripple effect caused by the name
change, unless we absolutely have too (i.e. we go down the path of
rearchitecting the server to align more with other Openstack projects',
in which case I am all in for it).

Cheers,
Armando

** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1239902

Title:
  neutron-server should be called neutron-api to conform with the rest
  of OpenStack

Status in devstack - openstack dev environments:
  New
Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  The rest of OpenStack calls its api server *-api, so to make things
  more uniform neutron should rename neutron-server as neutron-api

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1239902/+subscriptions