Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-06-30

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:04 docaedo joined #fuel
00:07 xarses joined #fuel
00:19 rmoe joined #fuel
01:39 LiJiansheng joined #fuel
03:00 Longgeek joined #fuel
03:08 kevinbenton joined #fuel
03:37 Longgeek joined #fuel
04:00 LucasPR joined #fuel
04:06 Longgeek joined #fuel
04:11 rmoe joined #fuel
04:38 rmoe joined #fuel
04:45 saibarspeis joined #fuel
04:51 LanceHaig joined #fuel
05:24 LiJiansheng joined #fuel
06:06 ub joined #fuel
06:08 stamak joined #fuel
06:48 saibarspeis joined #fuel
06:52 aliemieshko_ joined #fuel
06:54 dancn joined #fuel
06:54 aliemieshko_ joined #fuel
06:55 rmoe joined #fuel
07:20 samuelBartel joined #fuel
07:22 dkusidlo joined #fuel
07:33 e0ne joined #fuel
07:47 subscope joined #fuel
07:49 nix___ joined #fuel
07:50 nix___ When will Fuel plugins available for 6.1
08:01 LiJiansheng joined #fuel
08:02 sergmelikyan joined #fuel
08:12 subscope joined #fuel
08:15 sergmelikyan joined #fuel
08:20 rmoe joined #fuel
08:21 LiJiansheng joined #fuel
08:23 TiDjY35 joined #fuel
08:26 sergmelikyan joined #fuel
08:36 rmoe joined #fuel
08:36 xarses joined #fuel
08:37 xarses joined #fuel
08:39 subscope joined #fuel
08:39 LiJiansheng joined #fuel
08:40 HeOS joined #fuel
08:50 sc-rm joined #fuel
08:52 sc-rm Hi, I’m I the only one experincing that one of the controller nodes running mysql is creating really big mysql-bin.0000xxx files and not rotating them?
08:53 sc-rm I know how to fix it on a normal cluster, but I find it a bit of a problem, that it does so out of the box
09:00 sergmelikyan joined #fuel
09:02 e0ne joined #fuel
09:09 HeOS joined #fuel
09:22 rmoe joined #fuel
09:29 eliqiao joined #fuel
09:29 e0ne joined #fuel
09:35 monester_laptop joined #fuel
10:01 subscope joined #fuel
10:08 rmoe joined #fuel
10:11 LiJiansheng joined #fuel
10:11 sergmelikyan joined #fuel
10:12 stamak joined #fuel
10:37 sergmelikyan joined #fuel
10:45 stamak joined #fuel
11:11 LiJiansheng joined #fuel
11:14 sergmelikyan joined #fuel
11:17 monester_laptop joined #fuel
11:19 dkusidlo joined #fuel
11:37 rmoe joined #fuel
11:38 tobiash_ Hi, is there a way to remove old releases from fuel? E.g. I don't need the icehouse releases from 5.x anymore on a fuel which was upgraded to 6.1
11:47 subscope joined #fuel
12:11 monester_laptop joined #fuel
12:17 dhblaz joined #fuel
12:25 LucasPR joined #fuel
12:26 sc-rm tobiash_: I don’t know the answer for your question. But I’m considering to upgrade from 6.0 to 6.1. Did it upgrade your allready deployed openstack?
12:35 dancn joined #fuel
12:38 dkusidlo joined #fuel
12:39 sergmelikyan joined #fuel
13:03 sergmelikyan joined #fuel
13:14 sergmelikyan joined #fuel
13:20 sergmelikyan joined #fuel
13:30 youellet__ joined #fuel
13:39 saibarspeis joined #fuel
13:43 dkusidlo joined #fuel
13:46 e0ne joined #fuel
13:56 LiJiansheng joined #fuel
13:59 sergmelikyan joined #fuel
14:04 julien_ZTE joined #fuel
14:09 saibarspeis joined #fuel
14:12 dkusidlo joined #fuel
14:20 julien_ZTE joined #fuel
14:39 rmoe joined #fuel
14:41 julien_ZTE joined #fuel
14:49 sergmelikyan joined #fuel
14:52 subscope joined #fuel
14:52 dkusidlo joined #fuel
14:54 claflico joined #fuel
14:58 sergmelikyan joined #fuel
15:52 julien_ZTE joined #fuel
16:01 sergmelikyan joined #fuel
16:10 julien_ZTE joined #fuel
16:26 jaypipes joined #fuel
16:28 sergmelikyan joined #fuel
16:29 dontalton joined #fuel
16:36 e0ne joined #fuel
16:45 saibarspeis joined #fuel
16:48 tatyana joined #fuel
17:10 sergmelikyan joined #fuel
17:10 julien_ZTE joined #fuel
17:38 hammondr_ joined #fuel
17:39 hammondr_ should I be able to access the openstack api deployed by fuel 6.1 via the public interface?  I think so, but there seems to be some kind of internal redirection happening because my python openstack client says “Unable to establish connection to http://192.168.0.2:35357/v2.0/tenants” (which is on the internal/mgmt LAN)
17:39 MiroslavAnashkin sc-rm:
17:39 MiroslavAnashkin 1) Edit /etc/mysql/conf.d/wsrep.cnf on each controller. Add the following under the [mysqld] section:
17:39 MiroslavAnashkin expire-logs-days=3
17:39 MiroslavAnashkin 2) On each controller, run "mysql" and run the following queries:
17:39 MiroslavAnashkin PURGE BINARY LOGS BEFORE DATE(NOW() - INTERVAL 10 DAY) + INTERVAL 0 SECOND;
17:39 MiroslavAnashkin SET GLOBAL expire_logs_days = 10;
17:39 MiroslavAnashkin That's it. This will cleanup existing logs and change MySQL's expiry time on new logs. You will not need to restart MySQL for this to go into effect.
17:40 hammondr_ OS_AUTH_URL="http://10.80.0.2:5000/v2.0" … but something is telling the client to try to connect to 192.168.0.2, the mgmt IP for the api node
17:45 MiroslavAnashkin hammondr_: It is possible with Keystone API v3 only. http://docs.openstack.org/developer/keystone/http-api.html
17:46 v1k0d3n joined #fuel
17:47 hammondr_ so the openrc file produced by juno horizon references api v2, but I should use api v3?
17:49 MiroslavAnashkin You may re-configure Keystone http://docs.openstack.org/developer/keystone/configuration.html
17:49 xdeller joined #fuel
17:50 hammondr_ so yes?  I need to reconfigure keystone deployed by fuel 6.1 in order to use keystone api v3, which allows clients to connect via the public interface?
17:52 MiroslavAnashkin Both Keystone admin and user interfaces in v3 API are virtually equal and only single port configured is enough for all operations.
17:52 jobewan joined #fuel
17:54 MiroslavAnashkin For v2.0 you need 2 ports.
17:54 MiroslavAnashkin You may try the following solution in order to eliminate port 35357
17:54 MiroslavAnashkin 1. Exchange API v2.0 port bindings in /etc/keystone/keystone-paste.ini so Keystone admin interface listen on the port 5000 and Keystone public interface listen port 35357.
17:54 MiroslavAnashkin 2. Use only port 5000, since Keystone Admin interface in v2.0 API contains all the functionality of the Public interface.
17:54 MiroslavAnashkin 3. Optional. Restrict incoming connections to the port 35357 on the firewall.
17:55 hammondr_ ok; I can try that.  are you confirming that keystone, as deployed by fuel 6.1, requires this change before clients can use the api via the public network?
17:56 hammondr_ I’m not trying to limit ports, etc (though I will if I need to). I’m just trying to use functionality that the docs seem to indicate should already work (API access over public network)
17:56 angdraug joined #fuel
17:58 e0ne joined #fuel
18:04 MiroslavAnashkin By default Keystone API v2.0 is acceccible via Public network - but only User interface (that one bound to port 35357) So, not all API functions available. Admin v2.0 interface is bound to port 5000 and accessible by internal network.
18:18 hammondr_ joined #fuel
18:32 samuelBartel joined #fuel
18:46 xarses joined #fuel
18:58 Longgeek joined #fuel
18:59 julien_ZTE joined #fuel
19:02 MiroslavAnashkin FYI. https://online.mirantis.com/hubfs/Technical_Bulletins/Mirantis-Technical-Bulletin-18-Upgradeto6_1-1.pdf
19:07 hammondr_ thanks for providing that TB, Miroslav
19:33 HeOS joined #fuel
20:13 sergmelikyan joined #fuel
20:17 hammondr_ joined #fuel
20:18 sergmelikyan joined #fuel
20:24 serg_melikyan joined #fuel
20:25 Topic for #fuel is now Fuel 6.1 (Juno) https://software.mirantis.com | WARNING if you upgrade the masternode to 6.1 https://online.mirantis.com/hubfs/Technical_Bulletins/Mirantis-Technical-Bulletin-18-Upgradeto6_1-1.pdf | https://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
20:34 sergmelikyan joined #fuel
20:48 julien_ZTE joined #fuel
20:50 monester_laptop joined #fuel
21:35 dhblaz joined #fuel
21:36 teran joined #fuel
21:41 angdraug joined #fuel
21:49 julien_ZTE joined #fuel
22:19 sergmelikyan joined #fuel
22:35 rmoe joined #fuel
23:05 julien_ZTE joined #fuel
23:39 xarses joined #fuel

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary