Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2017-03-07

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

All times shown according to UTC.

Time Nick Message
00:09 acormier joined #fuel
00:22 johnavp1989 joined #fuel
00:53 acormier joined #fuel
00:54 acormier joined #fuel
02:25 acormier_ joined #fuel
02:31 fatdragon joined #fuel
02:48 ilbot3 joined #fuel
02:48 Topic for #fuel is now Fuel 9.0 (Mitaka) https://www.fuel-infra.org/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
03:56 Vijayendra joined #fuel
04:55 mdnadeem joined #fuel
05:30 Openstuck joined #fuel
05:38 fatdragon joined #fuel
09:40 fatdragon joined #fuel
11:59 johnavp19891 joined #fuel
12:18 johnavp1989 joined #fuel
12:50 pava joined #fuel
12:54 cffr joined #fuel
13:00 cffr Hi all. Is it possible to add an extra external network using on the same "physnet1" that fuel creates in openstack ? Does each external network require their own device ? Or how would one do that ?
13:10 acormier joined #fuel
13:37 cffr_ joined #fuel
13:38 GMAzrael I did it through routing tables and adding a router to the external network
13:41 acormier joined #fuel
14:11 mbuil joined #fuel
14:12 johnavp19891 joined #fuel
14:46 cffr joined #fuel
14:53 cffr But subnets doesn't seem to support to segregate the access to the network on a tenant level? The reason i ask is that a have a small subnet on a vlan that are for the nodes and some administrative machines and then a larger subnet on a different vlan for tenants to use.
14:57 marc_blabla joined #fuel
15:04 Julien-zte joined #fuel
15:11 marc_blabla left #fuel
15:15 mpjetta joined #fuel
15:19 acormier joined #fuel
15:20 mwik I've applied Mirantis 8.0 maintenance updates on a bunch of nodes successfully, but afterwards when I run apt upgrade, it wants to downgrade all opentack components that was previously upgraded. It only happens on some of the hosts. Any ideas what might be wrong?
15:23 marc_blabla joined #fuel
15:42 fatdragon joined #fuel
16:03 xarses_ joined #fuel
16:05 fatdragon joined #fuel
16:05 mwik Hmm, it seems that the culprit is the /apt/preferences.d/mos.pref having the same pin-priority as mos-updates. If I lower it to 950 the upgrade works as expected.
16:06 andreww joined #fuel
16:06 mwik Is this a known issue? Google gave me nothing.
16:06 andreww joined #fuel
16:10 marc_blabla joined #fuel
16:25 Julien-zte joined #fuel
16:27 Julien-zte joined #fuel
16:28 Julien-zte joined #fuel
16:28 Julien-zte joined #fuel
16:38 mwik After further investigation it turns out the /etc/apt/preferences.d/mos-updates.pref Pin: line is wrong. It doesnt match the update packages. It should have n=mos8.0 instead of n=mos8.0-updates
16:47 GK___1wm____SU joined #fuel
19:53 marc_blabla joined #fuel
21:52 andreww joined #fuel
21:53 xarses_ joined #fuel
22:00 byrdog55 joined #fuel
23:42 johnavp1989 joined #fuel

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