*** yangyapeng has quit IRC | 00:11 | |
*** ddieterly has quit IRC | 00:25 | |
*** ddieterly has joined #openstack-freezer | 00:37 | |
openstackgerrit | gengchc2 proposed openstack/freezer: Correct freezer reraising of exception https://review.openstack.org/360863 | 00:55 |
---|---|---|
*** yangyapeng has joined #openstack-freezer | 01:20 | |
*** zhurong has joined #openstack-freezer | 01:32 | |
*** ddieterly has quit IRC | 01:36 | |
*** ddieterly has joined #openstack-freezer | 01:40 | |
*** EinstCrazy has joined #openstack-freezer | 01:55 | |
*** EinstCrazy has quit IRC | 01:58 | |
*** yangyape_ has joined #openstack-freezer | 02:00 | |
*** yangyapeng has quit IRC | 02:02 | |
*** yangyapeng has joined #openstack-freezer | 02:03 | |
*** EinstCrazy has joined #openstack-freezer | 02:03 | |
*** yangyape_ has quit IRC | 02:04 | |
*** ddieterly has quit IRC | 02:06 | |
*** yangyape_ has joined #openstack-freezer | 02:43 | |
*** yangyapeng has quit IRC | 02:45 | |
*** Marcellin__ has quit IRC | 03:57 | |
*** openstackgerrit has quit IRC | 05:18 | |
*** openstackgerrit has joined #openstack-freezer | 05:19 | |
*** EinstCrazy has quit IRC | 05:30 | |
*** EinstCrazy has joined #openstack-freezer | 05:31 | |
*** EinstCrazy has quit IRC | 06:06 | |
*** EinstCrazy has joined #openstack-freezer | 06:10 | |
*** yangyapeng has joined #openstack-freezer | 06:10 | |
*** yangyap__ has joined #openstack-freezer | 06:10 | |
*** yangyape_ has quit IRC | 06:11 | |
*** yangyapeng has quit IRC | 06:14 | |
*** neilus has joined #openstack-freezer | 06:31 | |
*** yuval has joined #openstack-freezer | 06:34 | |
*** lpetrut has joined #openstack-freezer | 06:48 | |
*** EinstCrazy has quit IRC | 06:54 | |
*** EinstCrazy has joined #openstack-freezer | 07:03 | |
*** EinstCrazy has quit IRC | 07:27 | |
*** EinstCrazy has joined #openstack-freezer | 07:36 | |
*** lpetrut has quit IRC | 07:38 | |
*** lpetrut has joined #openstack-freezer | 07:52 | |
*** EinstCrazy has quit IRC | 08:03 | |
*** EinstCrazy has joined #openstack-freezer | 08:12 | |
*** lpetrut has quit IRC | 08:16 | |
*** openstackgerrit has quit IRC | 08:34 | |
*** EinstCra_ has joined #openstack-freezer | 08:34 | |
*** openstackgerrit has joined #openstack-freezer | 08:34 | |
*** EinstCrazy has quit IRC | 08:37 | |
*** lpetrut has joined #openstack-freezer | 08:44 | |
vnogin | morning guys | 08:53 |
vnogin | could you please tell me which exactly Db tables and schema freezer use? | 08:53 |
*** EinstCra_ has quit IRC | 08:55 | |
*** EinstCrazy has joined #openstack-freezer | 08:56 | |
m3m0 | vnogin: in mysql? | 08:57 |
m3m0 | we don't, we use elasticsearch for everything | 08:57 |
m3m0 | we are debating if we move | 08:57 |
vnogin | m3m0, ok, I see. I'm trying to figure out how to recovery freezer after disaster. As you remember I can't remove duplicated "clients" and also trying to figure out how to do it :) | 09:00 |
m3m0 | vnogin: you have 2 options | 09:10 |
m3m0 | you can use the same client as the ones you already have | 09:10 |
m3m0 | or, use freezer-scheduler -c "your_own_unique_client" | 09:10 |
m3m0 | this will force everything to run under that client id | 09:11 |
m3m0 | vnogin: which version of OpenStack are you using? I just want to know how far we need to backport the client deletion | 09:25 |
*** EinstCrazy has quit IRC | 09:37 | |
*** EinstCrazy has joined #openstack-freezer | 09:39 | |
vnogin | m3m0, sorry :) I'm back. I use OSA - mitaka and newton branches so it seems that you don't need to backport anything :) | 09:40 |
vnogin | m3m0, btw, how I can get running/using configuration for freezer from elasticsearch? | 09:42 |
*** yangyap__ has quit IRC | 09:43 | |
*** yangyapeng has joined #openstack-freezer | 09:43 | |
vnogin | m3m0, also is there any schema with freezer workflow (something like this for ironic file:///home/vnogin/Downloads/states.svg ) | 09:43 |
vnogin | ups, wrong link | 09:43 |
vnogin | http://docs.openstack.org/developer/ironic/_images/states.svg this one | 09:44 |
m3m0 | vnogin: I'm afraid that the only ones we have are here: https://github.com/openstack/freezer#architecture | 09:45 |
m3m0 | don't know if that helps you | 09:46 |
m3m0 | for elasticsearch you need to modify /etc/freezer/freezer-api.conf | 09:46 |
vnogin | m3m0, thx, I'll double check architecture :) as far as I remember it was not enough for my purposes | 09:48 |
m3m0 | vnogin: freezer in general? | 09:49 |
m3m0 | is there something missing? | 09:49 |
vnogin | m3m0, yep freezer-api.conf is the config file. However I mean running config - for instance if I run "freezer-scheduler client-list" I see the list of the client - where do we have this list? | 09:50 |
m3m0 | vnogin: I don't think I'm following this, you mean, where those clients are stored? | 09:51 |
vnogin | m3m0, frankly the following isn't correct from my point of view https://github.com/openstack/freezer/blob/master/specs/Service_Architecture_02.png because freezer API can be used outside cloud instance. | 09:52 |
vnogin | m3m0, Yep, I mean where do you store information regarding clients and other information :) | 09:53 |
m3m0 | yes, although it still require keystone | 09:53 |
*** zhurong has quit IRC | 10:05 | |
vnogin | m3m0, so, where do you store information regarding clients and other information :) ? | 10:37 |
m3m0 | vnogin: everything is stored in Elasticsearch | 10:42 |
*** saggi has joined #openstack-freezer | 10:48 | |
*** yangyapeng has quit IRC | 11:00 | |
*** ddieterly has joined #openstack-freezer | 11:06 | |
openstackgerrit | Merged openstack/freezer: Enable parallel job execution for the scheduler to allow abort signals https://review.openstack.org/358677 | 11:07 |
openstackgerrit | Memo Garcia proposed openstack/freezer-api: Fix client delete does not work https://review.openstack.org/366682 | 11:15 |
m3m0 | vnogin: ^^ :) | 11:15 |
*** ddieterly has quit IRC | 11:28 | |
vnogin | m3m0, wow :) checking, tnx | 11:28 |
m3m0 | this, however, will not work with previous stored clients | 11:35 |
m3m0 | we are discussing if we include this in the v2 of the pai | 11:35 |
m3m0 | api | 11:35 |
m3m0 | what do you think? | 11:35 |
raliev | Hi guys! I'am trying to install freezer in devstack (using plugins) but after installation there is no clients in list and I can't execute actions and jobs. What could be the problem here? | 11:44 |
*** ddieterly has joined #openstack-freezer | 11:51 | |
*** zhurong has joined #openstack-freezer | 11:55 | |
*** Marcellin__ has joined #openstack-freezer | 11:56 | |
*** EinstCrazy has quit IRC | 12:21 | |
*** ddieterly has quit IRC | 12:22 | |
openstackgerrit | Saad Zaher proposed openstack/freezer-api: Implemented: Installation documentation and API Ref https://review.openstack.org/366720 | 12:27 |
szaher_ | salshme m3m0 https://review.openstack.org/#/c/366720/ | 12:29 |
*** szaher_ has quit IRC | 12:30 | |
*** szaher has joined #openstack-freezer | 12:31 | |
*** zhusz has joined #openstack-freezer | 12:38 | |
*** zhusz has quit IRC | 12:39 | |
*** zhusz has joined #openstack-freezer | 12:39 | |
vnogin | m3m0, yep, I see that it doesn't work :) so does it mean that I need to reinstall client as well? | 12:49 |
m3m0 | yes, you may need to use another one with freezer-scheduler -c "new_client_id" or start over after this patch, now I'll fix it the gates | 12:51 |
*** zhusz has quit IRC | 12:51 | |
*** ddieterly has joined #openstack-freezer | 12:52 | |
m3m0 | raliev: what happens if you register a client manually? | 12:53 |
m3m0 | and is there any logs about the actions and jobs? | 12:53 |
raliev | m3m0, if I run 'freezer-scheduler register' then it stuck for some time and exit without any logs and messages | 12:56 |
m3m0 | raliev: proxies maybe? | 12:57 |
*** ddieterly has quit IRC | 12:57 | |
raliev | m3m0, I think no, probably firewall, but all installed on a single machine | 12:59 |
*** yangyapeng has joined #openstack-freezer | 13:00 | |
m3m0 | did you modify /etc/freezer/freezer-api.conf yourself or just let the plugins do everything? | 13:01 |
raliev | I didn't modify freezer-api.conf manually | 13:02 |
m3m0 | could you check that 1) elasticsearch is running, 2) /etc/freezer/freezer-api.conf is pointing to the right ips? | 13:04 |
raliev | just added enable_plugin freezer-api ... enable_plugin freezer ... enable_plugin freezer-web-ui | 13:05 |
raliev | 1. elasticsearch is ok, 2. IPs seems correct, it's local IP, port 9090 | 13:06 |
m3m0 | raliev: mmm I don't have any idea of what could be happening, I've seen this with proxies, even in the same machine, if you are under proxies you need to set up the no_proxy variable, but if that's not the case | 13:14 |
m3m0 | ... | 13:14 |
*** StraubTW has joined #openstack-freezer | 13:20 | |
openstackgerrit | Saad Zaher proposed openstack/freezer-api: Implemented: Installation documentation and API Ref https://review.openstack.org/366720 | 13:23 |
*** zhusz has joined #openstack-freezer | 13:39 | |
vnogin | m3m0, btw, if I want to use freezer for multi node cloud I need to install scheduler and agent to each node, correct? Do I need to configure something (except running freezer-scheduler register)? | 13:44 |
m3m0 | vnogin: yes, install them in each node | 13:46 |
m3m0 | and nothing else should be done besides that | 13:46 |
*** ddieterly has joined #openstack-freezer | 13:49 | |
*** ddieterly has quit IRC | 13:51 | |
*** ddieterly has joined #openstack-freezer | 13:51 | |
*** michauds has joined #openstack-freezer | 13:52 | |
raliev | m3m0: after devstack installation everything should work correctly and I don't need to run smth manually, right? | 13:52 |
m3m0 | raliev: as far as I remember, no, you should not, but is weird what you are seeing | 13:57 |
openstackgerrit | Merged openstack/freezer-api: Implemented: Installation documentation and API Ref https://review.openstack.org/366720 | 13:59 |
*** zhurong has quit IRC | 14:02 | |
zhusz | ddieterly: morning | 14:06 |
ddieterly | morning | 14:06 |
vnogin | m3m0, faced strange behavior. I execute "freezer-scheduler register" - it creates new client, then I execute "freezer-scheduler start" and I see that another client has been created with the same ID. Is it correct behavior or not? | 14:09 |
m3m0 | vnogin: no, this is not the correct behaviour, which version are you using? | 14:09 |
vnogin | m3m0, master (newton) | 14:12 |
vnogin | m3m0, I can try to install mitaka | 14:12 |
m3m0 | if you have time, could you let me know if this is happening in mitaka as well? | 14:12 |
vnogin | maybe it more stable | 14:12 |
vnogin | m3m0, sure, will check | 14:13 |
*** zhusz has quit IRC | 14:20 | |
*** raliev has quit IRC | 14:20 | |
*** EinstCrazy has joined #openstack-freezer | 14:30 | |
*** raliev has joined #openstack-freezer | 14:42 | |
*** EinstCrazy has quit IRC | 15:01 | |
*** yuval has quit IRC | 15:02 | |
*** EinstCrazy has joined #openstack-freezer | 15:27 | |
*** ddieterly is now known as ddieterly[away] | 15:35 | |
*** ddieterly[away] is now known as ddieterly | 15:38 | |
*** lpetrut has quit IRC | 15:42 | |
openstackgerrit | Merged openstack/freezer-web-ui: Updated tox.ini to support new test environment https://review.openstack.org/352501 | 15:48 |
openstackgerrit | Ryan Peters proposed openstack/freezer-web-ui: Retry data not being saved by UI https://review.openstack.org/364411 | 15:56 |
*** saggi has quit IRC | 15:59 | |
*** EinstCrazy has quit IRC | 16:05 | |
*** EinstCrazy has joined #openstack-freezer | 16:07 | |
openstackgerrit | Merged openstack/freezer: failed to start freezer-scheduler https://review.openstack.org/355818 | 16:13 |
*** EinstCrazy has quit IRC | 16:16 | |
*** ddieterly is now known as ddieterly[away] | 16:32 | |
*** ddieterly[away] is now known as ddieterly | 16:35 | |
openstackgerrit | Merged openstack/freezer-web-ui: Retry data not being saved by UI https://review.openstack.org/364411 | 16:40 |
*** ddieterly is now known as ddieterly[away] | 16:53 | |
*** lpetrut has joined #openstack-freezer | 16:54 | |
*** ddieterly[away] is now known as ddieterly | 17:02 | |
*** ddieterly is now known as ddieterly[away] | 17:06 | |
*** Marcellin__ has quit IRC | 17:37 | |
*** ddieterly[away] is now known as ddieterly | 18:26 | |
*** ddieterly is now known as ddieterly[away] | 18:35 | |
*** ddieterly[away] is now known as ddieterly | 18:41 | |
*** StraubTW has left #openstack-freezer | 19:03 | |
*** lpetrut has quit IRC | 19:04 | |
*** clenimar has quit IRC | 19:10 | |
*** ddieterly is now known as ddieterly[away] | 19:21 | |
*** ddieterly[away] is now known as ddieterly | 19:44 | |
*** lpetrut has joined #openstack-freezer | 19:45 | |
*** lpetrut has quit IRC | 19:50 | |
*** lpetrut has joined #openstack-freezer | 20:00 | |
*** openstackgerrit has quit IRC | 20:04 | |
*** openstackgerrit has joined #openstack-freezer | 20:05 | |
*** lpetrut has quit IRC | 20:29 | |
*** michauds has quit IRC | 20:43 | |
*** lpetrut has joined #openstack-freezer | 21:30 | |
*** lpetrut has quit IRC | 22:19 | |
*** ddieterly is now known as ddieterly[away] | 22:50 | |
*** ddieterly[away] has quit IRC | 22:50 | |
*** zhurong has joined #openstack-freezer | 23:49 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!