Hi Erno,
I agree that we must document what all config parameters will be reloaded after
SIGHUP signal is processed, that's the reason why we have added DocImpact tag
to patch https://review.openstack.org/#/c/117988/. We will test what parameters
are reloaded and report them to the Doc team.
Our use case:
We want to use SIGHUP signal to reload filesystem store related config
parameters namely "filesystem_store_datadir" and "filesystem_store_datadirs"
which are very crucial in the production environment especially for people
using NFS. In case, the filesystem is approaching at full capacity,
administrator can add more storage and configured it via the above parameters
which will be taken into effect upon sending SIGHUP signal. Secondly, most of
the OpenStack services uses service framework and it does handle reloading of
configuration files via SIGHUP signal which glance cannot without this patch.
Thanks & Regards,
Abhishek Kekane
________________________________
From: Kekane, Abhishek
Sent: Wednesday, September 03, 2014 9:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [glance][feature freeze exception] Proposal for
using Launcher/ProcessLauncher for launching services
Hi All,
Please give your support me for applying the freeze exception for using
oslo-incubator service framework in glance, based on the following blueprint:
https://blueprints.launchpad.net/glance/+spec/use-common-service-framework
I have ensured that after making these changes everything is working smoothly.
I have done the functional testing for following three scenarios:
1. Enabled SSL and checked requests are processed by the Api service
before and after SIGHUP signal
2. Disabled SSL and checked requests are processed by the Api service
before and after SIGHUP signal
3. I have also ensured reloading of the parameters like
ilesystem_store_datadir, filesystem_store_datadirs are working effectively
after sending the SIGHUP signal.
To test 1st and 2nd I have created a python script which will send multiple
requests to glance at a time and added a chron job to send a SIGHUP signal to
the parent process.
I have tested above script for 1 hour and confirmed every request has been
processed successfully.
Please consider this feature to be a part of Juno release.
Thanks & Regards,
Abhishek Kekane
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: 02 September 2014 19:11
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [glance][feature freeze exception] Proposal for using
Launcher/ProcessLauncher for launching services
Hi All,
I'd like to ask for a feature freeze exception for using oslo-incubator service
framework in glance, based on the following blueprint:
https://blueprints.launchpad.net/glance/+spec/use-common-service-framework
The code to implement this feature is under review at present.
1. Sync oslo-incubator service module in glance:
https://review.openstack.org/#/c/117135/2
2. Use Launcher/ProcessLauncher in glance:
https://review.openstack.org/#/c/117988/
If we have this feature in glance then we can able to use features like reload
glance configuration file without restart, graceful shutdown etc.
Also it will use common code like other OpenStack projects nova, keystone,
cinder does.
We are ready to address all the concerns of the community if they have any.
Thanks & Regards,
Abhishek Kekane
______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
