Camelia, the Perl 6 bug

IRC log for #fuel, 2013-11-01

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

All times shown according to UTC.

Time Nick Message
00:05 rmoe joined #fuel
00:36 rmoe joined #fuel
01:14 xarses joined #fuel
01:23 rmoe joined #fuel
01:34 tonyha joined #fuel
02:21 archon_ joined #fuel
02:37 dhblaz joined #fuel
03:09 dhblaz joined #fuel
03:27 ArminderS joined #fuel
03:47 teran joined #fuel
06:39 tonyha joined #fuel
06:41 iscsi left #fuel
06:41 iscsi joined #fuel
06:56 IlyaE joined #fuel
07:04 oguz joined #fuel
07:04 ogzy joined #fuel
07:05 ogzy At my nodes, when i boot them via PXE, and choose bootsplash, i can not see them at the fuel interface as unallocated nodes, here is the /var/log/nailgun-agent.log log
07:05 ogzy http://paste.openstack.org/show/50376/
07:10 e0ne joined #fuel
07:10 e0ne_ joined #fuel
07:25 sanek ogzy: supervisorctl restart nailgun on master node
07:27 mrasskazov joined #fuel
07:27 ogzy sanek: still same
07:28 ogzy sanek: strangely fuel web is not ablt to discover pxe booted nodes but i can see warning saying  Node 'Untitled (16:6D)' is back online
07:39 e0ne joined #fuel
07:41 e0ne_ joined #fuel
07:45 sanek ogzy: curl http://<master>:8000/api
08:11 e0ne joined #fuel
08:15 e0ne_ joined #fuel
08:28 evgeniy_l joined #fuel
08:28 evgeniy_l left #fuel
08:30 ChanServ joined #fuel
08:33 mihgen joined #fuel
08:33 mihgen left #fuel
08:35 mihgen joined #fuel
08:35 evgeniyl joined #fuel
09:11 LLIakaJI joined #fuel
09:16 LLIakaJI exit
09:25 teran joined #fuel
09:26 aglarendil joined #fuel
09:28 mihgen joined #fuel
10:02 MichaelKr joined #fuel
10:10 vkozhukalov joined #fuel
10:10 r0mikiam joined #fuel
10:58 ogzy sanek: not found
11:08 ogzy sanek: seems the api is not accesible
11:10 vnaboychenko_ joined #fuel
11:12 VladNaboychenko_ joined #fuel
11:13 ogzy on the fuel node http://master_node_id:8000/api giving not found error
11:13 ogzy What can be the reason
11:25 DmitriyN joined #fuel
11:44 sanek ogzy: check nailgun.log on master node
12:10 ogzy sanek: what should be the eth1 ip address of the nodes booted via pxe?
12:11 ogzy sanek: do they need to connect internet?
12:20 e0ne joined #fuel
12:41 ogzy Node "Untitled (5A:77)": "public", "management", "storage"
12:41 ogzy how many interfaces do i need on the nodes?
12:41 ogzy i have two
12:42 ogzy one is used for pxe
12:42 ogzy the othere are assigned for public sotrage and management
12:42 ogzy which causes conflict
12:54 ogzy do i need three network interfaces on compute and controller node?
12:57 mattymo ogzy, for VLAN yes
12:57 mattymo if you use flatdhcp or neutron with GRE you can get by with only 2
12:59 ogzy i choosed GRE
12:59 ogzy mattymo: so i need help about ip configuration a bit
12:59 ogzy mattymo: i have fuel machine, eth1 10.102.235.x/24, abl connect internet
13:00 ogzy mattymo: eth1: 10.102.237.x, for pxe
13:00 ogzy mattymo: now i am trying to set my control and compute nodes
13:00 mattymo admin is for PXE, then you need 1 interface for public + floating IP, then another interface for management + private
13:01 mattymo with those two as vlans
13:01 ogzy mattymo: for each node?
13:01 mattymo but if you use vlanmanager or neutron with vlans you need a dedicated interface
13:01 mattymo of course
13:02 ogzy mattymo: anyway to handle the issue with two interfaces?
13:02 ogzy mattymo: like defining eth0:1 ?
13:02 mattymo you can do it with 2
13:03 mattymo admin network must be separate
13:03 mattymo when you configure interfaces, you can pick which network is on which interface
13:03 ogzy mattymo: one will be pxe, and the other one is for public + management + storage?
13:04 mattymo yes
13:04 mattymo it's not recommended, but it works
13:04 ogzy mattymo: network settings says conflicts when i do it but let me try again
13:05 ogzy mattymo:
13:05 ogzy Intersection between network address spaces found:
13:05 ogzy management, storage
13:09 e0ne joined #fuel
13:09 mattymo ogzy, which networking scheme did you pick?
13:10 ogzy GRE
13:11 mattymo sorry, my specialization ends here
13:12 ogzy mattymo: ok thank you
13:13 ogzy mattymo: one more question, how does the nodes assign IP to eth1 after booting from eth0 and getting IP
13:14 mattymo during installation only 1 interface gets configured (the one used for install from master node)
13:14 mattymo the others are all disabled
13:15 mattymo then all the config is set by astute to place /etc/astute.yaml on the node, which includes network configuration
13:15 mattymo during puppet apply, l23network configures each IP address statically
13:33 e0ne joined #fuel
14:00 MiroslavAnashkin ogzy: Please check Networks tab in Fuel UI, Neutron L3 Configuration settings. We have a bug - Floating IP range settings does not updated automatically when you use custom network settings for public network.
14:01 ogzy MiroslavAnashkin: ohh, i have a different range of public network
14:02 MiroslavAnashkin Then, please correct Neutron L3 settings.
14:08 MiroslavAnashkin BTW, Neutron+GRE may not work under VirtualBox and VMware due to broadcast network traffic optimizations. It works under KVM.
14:08 MiroslavAnashkin And works on bare-metal.
14:09 ogzy MiroslavAnashkin: i am not using virtualbox installation
14:57 teran joined #fuel
15:22 dhblaz joined #fuel
15:30 IlyaE joined #fuel
15:32 tonyha joined #fuel
15:37 alan_ joined #fuel
15:51 tonyha Hi I tried building iso following this instruction http://docs.mirantis.com/fuel-dev/de​velop/env.html#building-the-fuel-iso
15:51 tonyha I got make error 1 during the yumdownloader
15:51 tonyha http://paste.openstack.org/show/50393/
15:51 tonyha Did I miss something ?
16:01 jsergent joined #fuel
16:17 tonyha_ joined #fuel
16:20 rmoe joined #fuel
16:21 e0ne_ joined #fuel
16:30 IlyaE joined #fuel
16:37 angdraug joined #fuel
16:59 MiroslavAnashkin joined #fuel
16:59 aglarendil joined #fuel
17:00 xdeller joined #fuel
17:03 mattymo joined #fuel
17:04 dpyzhov joined #fuel
17:04 meow-nofer joined #fuel
17:07 xarses joined #fuel
17:16 korn__ joined #fuel
17:17 jsergent joined #fuel
17:27 IlyaE joined #fuel
17:28 jsergent joined #fuel
17:31 alex_null joined #fuel
17:44 ArminderS joined #fuel
17:54 vk joined #fuel
17:56 ArminderS joined #fuel
18:16 albionandrew joined #fuel
18:19 e0ne joined #fuel
18:22 ArminderS joined #fuel
18:22 rmoe joined #fuel
18:23 jsergent joined #fuel
18:26 ArminderS joined #fuel
18:32 ArminderS joined #fuel
18:35 ArminderS joined #fuel
18:44 ArminderS joined #fuel
19:18 rmoe joined #fuel
19:28 angdraug joined #fuel
19:29 angdraug joined #fuel
19:40 mihgen joined #fuel
20:45 dhblaz Our Public Network is our DMZ
20:46 dhblaz It has hosts on it other than those that involved in our cluster.
20:46 dhblaz How do we exclude them?
20:47 dhblaz I tried using the fuel command line tool to download the network settings and adjust the network range for the private network
20:49 dhblaz but when I uploaded them then downloaded the settings again it reverts to the original:
20:49 dhblaz "ip_ranges": [
20:49 dhblaz [
20:49 dhblaz "192.168.62.2",
20:49 dhblaz "192.168.62.254"
20:49 dhblaz ]
20:53 dhblaz I feel like I have asked this question many times many ways but still don't know how to resolve the issue.
20:56 albionandrew xarses are you there?
20:57 xarses albionandrew: yes
20:58 xarses dhblaz: we are now accepting launchpad bugs https://bugs.launchpad.net/fuel/+bugs this sounds like one
20:59 albionandrew dhblaz has popped out - I was wondering about the ip range question he asked
20:59 albionandrew re adjusting the network
21:04 teran joined #fuel
21:06 IlyaE joined #fuel
21:35 dhblaz What is the launchpad tag for the web gui?
21:36 albionandrew joined #fuel
21:44 dhblaz decided it was ui
21:45 dhblaz couldn't find a tag for orchestrator either -- I'll figure this out yet
21:49 albionandrew joined #fuel
22:01 jkyle joined #fuel
22:15 xarses astute
23:08 archon1st joined #fuel
23:09 archon1st hi, how to recover from systemwide power failure?
23:12 xarses you need to start fuel/DNS -> Controller [1], verify rabbitmq, galera -> controller 2,3 if present -> storage / cinder / ceph nodes -> computes
23:14 xarses most important to make sure rabbit, galera is OK after fist then all controllers before attempting to start others
23:14 tonyha_ joined #fuel
23:14 archon1st thx xarses
23:16 archon1st ok this is what i got from checking crm : http://paste.openstack.org/show/50414/
23:16 xarses http://docs.mirantis.com/ has material related to this, just make sure you are reading a version for the fuel version you are using as it changes some
23:16 xarses search for galera
23:17 archon1st yes, we use 3.2, somehow i cannot restart galera, permission denied
23:18 xarses yes service is managed by crm
23:18 archon1st does "crm resource cleanup p_mysql_monitor_60000" will solve this?
23:19 xarses should be able to tell crm to start mysql
23:19 archon1st ok will test it, on which node should I execute it? primary controller or last controller?
23:20 archon1st node-5 and node-8 wsrep status synced, but both stated that they are primary, node-7 out of sync
23:20 xarses if it was a whole cluster failure, it wont work
23:21 xarses erm
23:21 xarses wont matter
23:21 archon1st alright
23:21 xarses if they where shutdown on purpose then it should be last controller shutdown
23:22 archon1st yeah, we suffer from unexpected power failure in the datacenter
23:22 xarses it happens
23:22 xarses you can maybe check node-7 again, it might be in sync now
23:24 archon1st crm resource cleanup p_mysql_monitor_60000 result: Error performing operation: No such device or address
23:31 tonyha xarses what is the official procedure to contact mirantis support if you have support subscriptions ?
23:45 xarses tonyha: I think it's documented on http://support.mirantis.com

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