Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
David, You're completely right, The main problem is that ceilometer has possibility to create samples, but not to delete. Because of that there is no possibility to remove OSTF created data. Actually another way is to use time_to_live, but as you sad As an operator, I’d expect that my data is retained even for items that have been removed(c) 2014/1/17 David Easter deas...@mirantis.com I’d like to make sure I understand the question. Is this the scenario? - A user installs Mirantis OpenStack - The user runs the Mirantis OpenStack Health Check (OSTF) against Ceilometer - The Health Check creates a VM against which ceilometer can collect data - Ceilometer collects the data from this VM for an amount of time and stores the data in mySQL - The Health Check then ends the test, removing the VM - The data collected about this sample VM is retained in mySQL and is not removed. Is this basically correct? If so, I’d ask if Ceilometer removes data from VM’s or nodes that have been deleted from OpenStack during normal operation or if the data is retained in the run-time scenarios as well? If so, wouldn’t this be a general requirement to remove data about entities that no longer exist in the environment vs. an issue specific to Health Check (OSTF)? As an operator, I’d expect that my data is retained even for items that have been removed, but I agree that there should be a way for an operator to make a decision to remove stale data – either based on time or as a manually executed operation. Removing data automatically right away could lead to a loss of historical information that could be used for longer term analysis and billing. Or am I misinterpreting the situation and Ceilometer already allows for deletion of data – and the question is just whether we should remove the data collected during the test? If that is the only question, then yes – we should remove the data after the test is done. Thanks, -Dave Easter From: Dmitry Iakunchikov diakunchi...@mirantis.com Date: Friday, January 17, 2014 at 5:10 AM To: Nadya Privalova nprival...@mirantis.com, OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, Dmitry Iakunchikov diakunchi...@mirantis.com, Mike Scherbakov mscherba...@mirantis.com, Vladimir Kuklin vkuk...@mirantis.com, fuel-...@lists.launchpad.net fuel-...@lists.launchpad.net Subject: Re: [Fuel-dev] [openstack-dev] [OSTF][Ceilometer] ceilometer meters and samples delete For now in Fuel we keep samples forever In case if we will use time_to_live, how long we should keep this data? 2014/1/17 Julien Danjou jul...@danjou.info On Fri, Jan 17 2014, Nadya Privalova wrote: I would ask in another way. Ceilometer has a mechanism to add a sample through POST. So it looks not consistent not to allow user to delete a sample. IMHO, insertion and deletion through REST looks a little bit hacky: user always has an ability to fake data collected from OpenStack services. But maybe I don't see any valuable usecases. Anyway, it seems reasonable to have both add_sample and delete_sample in API or not to have neither. From the user PoV, that totally makes sense, agreed. -- Julien Danjou # Free Software hacker # independent consultant # http://julien.danjou.info -- With Best Regards QA engineer Dmitry Iakunchikov -- Mailing list: https://launchpad.net/~fuel-dev Post to : fuel-...@lists.launchpad.net Unsubscribe : https://launchpad.net/~fuel-devMore help : https://help.launchpad.net/ListHelp -- With Best Regards QA engineer Dmitry Iakunchikov ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
On 01/20/2014 01:29 PM, Dmitry Iakunchikov wrote: David, You're completely right, The main problem is that ceilometer has possibility to create samples, but not to delete. Because of that there is no possibility to remove OSTF created data. 1) What is current DB backend for Ceilometer? Can we use the separate database for OSTF and just drop while doing teardown? 2) IIRC from Ceilometer PoC performance results, the main DB with Galera must never be used as backend for ceilometer because of performance issues? Actually another way is to use time_to_live, but as you sad As an operator, I’d expect that my data is retained even for items that have been removed(c) 2014/1/17 David Easter deas...@mirantis.com mailto:deas...@mirantis.com I’d like to make sure I understand the question. Is this the scenario? * A user installs Mirantis OpenStack * The user runs the Mirantis OpenStack Health Check (OSTF) against Ceilometer * The Health Check creates a VM against which ceilometer can collect data * Ceilometer collects the data from this VM for an amount of time and stores the data in mySQL * The Health Check then ends the test, removing the VM * The data collected about this sample VM is retained in mySQL and is not removed. Is this basically correct? If so, I’d ask if Ceilometer removes data from VM’s or nodes that have been deleted from OpenStack during normal operation or if the data is retained in the run-time scenarios as well? If so, wouldn’t this be a general requirement to remove data about entities that no longer exist in the environment vs. an issue specific to Health Check (OSTF)? As an operator, I’d expect that my data is retained even for items that have been removed, but I agree that there should be a way for an operator to make a decision to remove stale data – either based on time or as a manually executed operation. Removing data automatically right away could lead to a loss of historical information that could be used for longer term analysis and billing. Or am I misinterpreting the situation and Ceilometer already allows for deletion of data – and the question is just whether we should remove the data collected during the test? If that is the only question, then yes – we should remove the data after the test is done. Thanks, -Dave Easter From: Dmitry Iakunchikov diakunchi...@mirantis.com mailto:diakunchi...@mirantis.com Date: Friday, January 17, 2014 at 5:10 AM To: Nadya Privalova nprival...@mirantis.com mailto:nprival...@mirantis.com, OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org mailto:openstack-dev@lists.openstack.org, Dmitry Iakunchikov diakunchi...@mirantis.com mailto:diakunchi...@mirantis.com, Mike Scherbakov mscherba...@mirantis.com mailto:mscherba...@mirantis.com, Vladimir Kuklin vkuk...@mirantis.com mailto:vkuk...@mirantis.com, fuel-...@lists.launchpad.net mailto:fuel-...@lists.launchpad.net fuel-...@lists.launchpad.net mailto:fuel-...@lists.launchpad.net Subject: Re: [Fuel-dev] [openstack-dev] [OSTF][Ceilometer] ceilometer meters and samples delete For now in Fuel we keep samples forever In case if we will use time_to_live, how long we should keep this data? 2014/1/17 Julien Danjou jul...@danjou.info mailto:jul...@danjou.info On Fri, Jan 17 2014, Nadya Privalova wrote: I would ask in another way. Ceilometer has a mechanism to add a sample through POST. So it looks not consistent not to allow user to delete a sample. IMHO, insertion and deletion through REST looks a little bit hacky: user always has an ability to fake data collected from OpenStack services. But maybe I don't see any valuable usecases. Anyway, it seems reasonable to have both add_sample and delete_sample in API or not to have neither. From the user PoV, that totally makes sense, agreed. -- Julien Danjou # Free Software hacker # independent consultant # http://julien.danjou.info -- With Best Regards QA engineer Dmitry Iakunchikov -- Mailing list: https://launchpad.net/~fuel-dev Post to : fuel-...@lists.launchpad.net mailto:fuel-...@lists.launchpad.net Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp -- With Best Regards QA engineer Dmitry Iakunchikov -- Best regards, Bogdan Dobrelya, Researcher TechLead, Mirantis, Inc. +38 (066) 051 07 53 Skype bogdando_at_yahoo.com Irc #bogdando 38, Lenina ave. Kharkov, Ukraine www.mirantis.com www.mirantis.ru bdobre...@mirantis.com
[openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
Hi, Ceilometer's tests creates some data which could not be deleted. For example: after creation new instance, ceilometer creates new meters for this instance and there is no possibility to delete them. Even after instance deletion they would not be deleted. Should we take attention to this? And find some way to delete all data, for example database wipe or patch to ceilometer client... Or just to skip this? -- With Best Regards QA engineer Dmitry Iakunchikov ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
On Fri, Jan 17 2014, Dmitry Iakunchikov wrote: Ceilometer's tests creates some data which could not be deleted. For example: after creation new instance, ceilometer creates new meters for this instance and there is no possibility to delete them. Even after instance deletion they would not be deleted. Should we take attention to this? And find some way to delete all data, for example database wipe or patch to ceilometer client... Or just to skip this? Why would you delete this? There's a time-to-live mechanism in Ceilometer to delete old samples. -- Julien Danjou // Free Software hacker / independent consultant // http://julien.danjou.info signature.asc Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
Hi guys, I would ask in another way. Ceilometer has a mechanism to add a sample through POST. So it looks not consistent not to allow user to delete a sample. IMHO, insertion and deletion through REST looks a little bit hacky: user always has an ability to fake data collected from OpenStack services. But maybe I don't see any valuable usecases. Anyway, it seems reasonable to have both add_sample and delete_sample in API or not to have neither. Thanks, Nadya On Fri, Jan 17, 2014 at 3:50 PM, Julien Danjou jul...@danjou.info wrote: On Fri, Jan 17 2014, Dmitry Iakunchikov wrote: Ceilometer's tests creates some data which could not be deleted. For example: after creation new instance, ceilometer creates new meters for this instance and there is no possibility to delete them. Even after instance deletion they would not be deleted. Should we take attention to this? And find some way to delete all data, for example database wipe or patch to ceilometer client... Or just to skip this? Why would you delete this? There's a time-to-live mechanism in Ceilometer to delete old samples. -- Julien Danjou // Free Software hacker / independent consultant // http://julien.danjou.info ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
On Fri, Jan 17 2014, Nadya Privalova wrote: I would ask in another way. Ceilometer has a mechanism to add a sample through POST. So it looks not consistent not to allow user to delete a sample. IMHO, insertion and deletion through REST looks a little bit hacky: user always has an ability to fake data collected from OpenStack services. But maybe I don't see any valuable usecases. Anyway, it seems reasonable to have both add_sample and delete_sample in API or not to have neither. From the user PoV, that totally makes sense, agreed. -- Julien Danjou # Free Software hacker # independent consultant # http://julien.danjou.info signature.asc Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
Hi, In my opinion it would be better to let the user to define a ttl value for his/her own samples. I do not see the use case, where it is needed to delete samples, also if the user is able to randomly delete some data, then the statistics functions will not generate a valid output for that data set, which was affected by the deletion. As the original question was about testing, I do not have a deeper knowledge about how testing works now regarding to generating and storing the samples. Maybe if there is a need for deleting data there, it can be considered that how we can handle that particular case. How would we identify the samples, which should be deleted? If it is allowed to delete any samples from the system via the API, it does not sound good either. So if it is an all or nothing situation, I would say nothing. Best Regards, Ildiko -Original Message- From: Julien Danjou [mailto:jul...@danjou.info] Sent: Friday, January 17, 2014 1:35 PM To: Nadya Privalova Cc: fuel-...@lists.launchpad.net; OpenStack Development Mailing List (not for usage questions); Vladimir Kuklin Subject: Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete On Fri, Jan 17 2014, Nadya Privalova wrote: I would ask in another way. Ceilometer has a mechanism to add a sample through POST. So it looks not consistent not to allow user to delete a sample. IMHO, insertion and deletion through REST looks a little bit hacky: user always has an ability to fake data collected from OpenStack services. But maybe I don't see any valuable usecases. Anyway, it seems reasonable to have both add_sample and delete_sample in API or not to have neither. From the user PoV, that totally makes sense, agreed. -- Julien Danjou # Free Software hacker # independent consultant # http://julien.danjou.info ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete
For now in Fuel we keep samples forever In case if we will use time_to_live, how long we should keep this data? 2014/1/17 Julien Danjou jul...@danjou.info On Fri, Jan 17 2014, Nadya Privalova wrote: I would ask in another way. Ceilometer has a mechanism to add a sample through POST. So it looks not consistent not to allow user to delete a sample. IMHO, insertion and deletion through REST looks a little bit hacky: user always has an ability to fake data collected from OpenStack services. But maybe I don't see any valuable usecases. Anyway, it seems reasonable to have both add_sample and delete_sample in API or not to have neither. From the user PoV, that totally makes sense, agreed. -- Julien Danjou # Free Software hacker # independent consultant # http://julien.danjou.info -- With Best Regards QA engineer Dmitry Iakunchikov ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
