Hi,
The reviews of the implementation have brought up a number of issues
(https://review.openstack.org/#/c/8101). These are namely the management
of the various configuration files and paths. I am sorry for bring this
up now. I was under the impression that we want to try and keep the same
files and support as of today, but this was a bit naive in retrospect.
I would like to suggest a solution and if possible get some feedback
prior to addressing all of the issues/comments. I would like to suggest
the following:
There will be 2 configuration files:
1. quantum.conf - this will be used by both the agents and the quantum
service. The file will contain all of the key value pair used by either
the agents and plugin. The installation packages for the quantum
agent/service can create or modify the files accordingly.
For example:
Common for both:-
debug
verbose
logging ...
rpc fields (for up and coming scaling bp)
Quantum service:-
port
listing address
database configuration if necessary
...
Quantum agent:-
root wrapper
polling interval
...
2. api-paste.ini - this is only used by the quantum service (similar
support in nova, keystone and glance)
Thanks
Gary
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
The reviews of the implementation have brought up a number of issues
(https://review.openstack.org/#/c/8101). These are namely the management
of the various configuration files and paths. I am sorry for bring this
up now. I was under the impression that we want to try and keep the same
files and support as of today, but this was a bit naive in retrospect.
I would like to suggest a solution and if possible get some feedback
prior to addressing all of the issues/comments. I would like to suggest
the following:
There will be 2 configuration files:
1. quantum.conf - this will be used by both the agents and the quantum
service. The file will contain all of the key value pair used by either
the agents and plugin. The installation packages for the quantum
agent/service can create or modify the files accordingly.
For example:
Common for both:-
debug
verbose
logging ...
rpc fields (for up and coming scaling bp)
Quantum service:-
port
listing address
database configuration if necessary
...
Quantum agent:-
root wrapper
polling interval
...
2. api-paste.ini - this is only used by the quantum service (similar
support in nova, keystone and glance)
Thanks
Gary
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp