As part of the ongoing performance work, the following changes are happening on the devel branch.
-- Consolidation of XMLRPC ports
Previously cobbler operated two XMLRPC endpoints:
http://server/cobbler_api_rw --> maps to 127.0.0.1:25152
http://server/cobbler_api --> maps to 127.0.0.1:25150
In newer versions, both of these endpoints will continue to work but they will map to the same port (25150)
Both read-write and read-only operations will be able to be done on the same port.
This means cobblerd startup involves half as much CPU and IO.
In addition, James Laska and Bill Peck's work on the upgraded Anaconda monitoring system means cobblerd will no longer listen for UDP syslog information and log it -- if Anaconda monitoring is desired, and enabled, it will log /much/ more. This also eliminates a extra fork() in cobblerd.
Cobbler also published itself via avahi if enabled, which is a feature I don't suspect too many people were using. Koan is still avahi aware, though if you want to publish the presence of Cobbler, cobblerd will currently /not/ do that for you. Since cobbler sets up a profiles.d file now that tells koan where the cobbler server that installs it is, that's a much better way to do discovery.
All in all, cobblerd will be down from 3-4 processes to just 1, and now requires two less API handles. Actual performance implications TBD but it will be nice to have.
This is all in progress and should be testable soon.
If you have an existing script, continue to use the Apache-proxied http endpoints instead of direct communication to the HTTP ports and things will work as normal. If you are using port numbers, replace any instance of "25151" with "25150" in your code, and things will also continue to work as normal. If your code referenced "cobbler_api" or 25151, nothing changes, that still works as before also.
--Michael
Michael DeHaan wrote:
As part of the ongoing performance work, the following changes are happening on the devel branch.
-- Consolidation of XMLRPC ports
Previously cobbler operated two XMLRPC endpoints:
http://server/cobbler_api_rw --> maps to 127.0.0.1:25152
http://server/cobbler_api --> maps to 127.0.0.1:25150
Correction, the port used for api was 25151 before. This will be the only port used by cobblerd going forward.
In newer versions, both of these endpoints will continue to work but they will map to the same port (25150)
Both read-write and read-only operations will be able to be done on the same port.
This means cobblerd startup involves half as much CPU and IO.
In addition, James Laska and Bill Peck's work on the upgraded Anaconda monitoring system means cobblerd will no longer listen for UDP syslog information and log it -- if Anaconda monitoring is desired, and enabled, it will log /much/ more. This also eliminates a extra fork() in cobblerd.
Cobbler also published itself via avahi if enabled, which is a feature I don't suspect too many people were using. Koan is still avahi aware, though if you want to publish the presence of Cobbler, cobblerd will currently /not/ do that for you. Since cobbler sets up a profiles.d file now that tells koan where the cobbler server that installs it is, that's a much better way to do discovery.
All in all, cobblerd will be down from 3-4 processes to just 1, and now requires two less API handles. Actual performance implications TBD but it will be nice to have.
This is all in progress and should be testable soon.
If you have an existing script, continue to use the Apache-proxied http endpoints instead of direct communication to the HTTP ports and things will work as normal. If you are using port numbers, replace any instance of "25151" with "25150" in your code, and things will also continue to work as normal. If your code referenced "cobbler_api" or 25151, nothing changes, that still works as before also.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Michael DeHaan wrote:
Michael DeHaan wrote:
As part of the ongoing performance work, the following changes are happening on the devel branch.
-- Consolidation of XMLRPC ports
Previously cobbler operated two XMLRPC endpoints:
http://server/cobbler_api_rw --> maps to 127.0.0.1:25152
http://server/cobbler_api --> maps to 127.0.0.1:25150
Correction, the port used for api was 25151 before. This will be the only port used by cobblerd going forward.
In newer versions, both of these endpoints will continue to work but they will map to the same port (25150)
Both read-write and read-only operations will be able to be done on the same port.
This means cobblerd startup involves half as much CPU and IO.
In addition, James Laska and Bill Peck's work on the upgraded Anaconda monitoring system means cobblerd will no longer listen for UDP syslog information and log it -- if Anaconda monitoring is desired, and enabled, it will log /much/ more. This also eliminates a extra fork() in cobblerd.
Cobbler also published itself via avahi if enabled, which is a feature I don't suspect too many people were using. Koan is still avahi aware, though if you want to publish the presence of Cobbler, cobblerd will currently /not/ do that for you. Since cobbler sets up a profiles.d file now that tells koan where the cobbler server that installs it is, that's a much better way to do discovery.
All in all, cobblerd will be down from 3-4 processes to just 1, and now requires two less API handles. Actual performance implications TBD but it will be nice to have.
This is all in progress and should be testable soon.
If you have an existing script, continue to use the Apache-proxied http endpoints instead of direct communication to the HTTP ports and things will work as normal. If you are using port numbers, replace any instance of "25151" with "25150" in your code, and things will also continue to work as normal. If your code referenced "cobbler_api" or 25151, nothing changes, that still works as before also.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
New findings: having the same cobbler_api_rw endpoint pointing to the same port as cobbler_api brings up a Apache warning on restarting the service, so, rather than have to answer questions about why that is actually ok, we may just only offer cobbler_api as a endpoint and supress the warning.
This would mean the cobbler_api_rw endpoint would also go away.
--Michael
cobbler@lists.fedorahosted.org