Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-04-06

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

All times shown according to UTC.

Time Nick Message
00:40 IlyaE joined #fuel
01:47 ilbot3 joined #fuel
01:47 Topic for #fuel is now Fuel 4.1 for Openstack: http://fuel.mirantis.com/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
03:14 dteselkin_ joined #fuel
03:39 IlyaE joined #fuel
05:09 rmoe joined #fuel
05:25 rmoe joined #fuel
06:05 mihgen joined #fuel
06:56 dburmistrov joined #fuel
07:03 e0ne joined #fuel
07:26 Connor_ joined #fuel
07:26 Connor_ Hi Folks am newbi using Fuel run into a problem
07:27 Connor_ When I take a snapshort it just gets killed I am using Fuel 4.1 Havana on Ubuntu anyone else had that issue
07:28 mihgen Connor_: hi
07:28 mihgen can you check logs on master node?
07:28 mihgen in /var/log/naily/
07:29 mihgen I don't have running env now… but there is could be a log for shotgun somewhere there.
07:29 Connor_ ok checking the logs now
07:30 mihgen shotgun is actually the component which does snapshot functionality
07:31 Connor_ ok I have controllers as 3 node cluster so am going through each one will also check the compute nodes
07:31 mihgen logs are on master node
07:32 mihgen all of them actually, as they are gathered by rsyslog. From remote nodes it's in /var/log/remote/
07:32 Connor_ Cool thanks mihgen Found the logs looking for shotgun logs now
07:50 mihgen Connor_: diagnostic snapshot should always work actually.. please feel free to file a bug to https://launchpad.net/fuel and attach /var/log/ archive from your master node, so we can dig into it too
07:53 Connor_ ok  will generate and upload all debug data to the launchpad location . Thanks
08:00 Connor_ One of the errors in the Cinder-cinder.log
08:00 Connor_ 2014-04-06T06:09:16.998409+00:00 crit:  CRITICAL: (OperationalError) (2013, "Lost connection to MySQL server at 'reading initial communication packet', system error: 0") None Non
08:18 e0ne joined #fuel
08:29 e0ne joined #fuel
09:16 vk joined #fuel
10:09 bookwar joined #fuel
10:37 e0ne joined #fuel
10:44 e0ne joined #fuel
11:20 piersdd joined #fuel
11:28 piersdd Hi,  Have successfully deployed a HA Neutron 4.1 cloud, and am trying to figure out why my Health Checks failed.  Documentation says one can exceute a nova-manage command on the controller, but I'm unsure exactly how to gain access to the controller.
11:28 piersdd IGNORE last.
13:39 vk joined #fuel
13:43 al_ex joined #fuel
16:18 al_ex joined #fuel
16:45 mihgen joined #fuel
18:51 e0ne joined #fuel
18:54 e0ne joined #fuel
19:12 e0ne joined #fuel
19:30 e0ne joined #fuel
19:46 e0ne joined #fuel
20:02 rnelan joined #fuel
20:02 rnelan 'lo all
20:02 rnelan I understand this is the place to ask questions..
20:03 rnelan anyone?
20:03 mihgen hi rnelan
20:03 mihgen I might help… :)
20:04 rnelan Hi, and thanks! I have a very easy question for you!
20:04 mihgen don't no how many ppl are awake on Sunday)
20:04 rnelan aha!
20:04 rnelan ok, that makes sense
20:04 rnelan so, the question..
20:04 rnelan It has to do with IPMI and HP's ILO interface..
20:05 rnelan The guide tells us to put every node's ILO interface in a separate network.. That is easy..
20:05 rnelan but the confusion is whether or not to put them in the same vlan as the Admin network.. (103)
20:06 mihgen well I would not intersect Admin PXE & IPMI nets ..
20:06 mihgen can you use separate L2 for both?
20:07 rnelan sure.. I have no shortage of ports.. but how does the fuel controller get to the ipmi net when it only sets up 2 networks.. Public (100) and Admin (103)??
20:07 mihgen it's possible to configure using same L2.. but that needs to be accurately done
20:07 mihgen Fuel doesn't deal with IPMI at all at the moment
20:08 rnelan aha!
20:08 mihgen Fuel uses PXE provisioning though
20:08 rnelan that is what I needed to know.. so, the servers rest in standby.. and I have to turn them on manually??
20:08 mihgen so when you configure it, make sure L3 you provide for PXE, and Fuel master node itself, don't intersect with your infra
20:09 mihgen currently yes, you turn them on, but ONCE
20:09 mihgen they load so called bootstrap into the memory
20:09 rnelan not exactly efficient power consumption!
20:10 mihgen it's centos OS, and Fuel has ssh to it. So it will go from this further. It's true, not efficient….. support of ipmi in the roadmap :)
20:10 rnelan thanks for your time! let me tell you what i understood....
20:11 rnelan the controller node is in public and admin... no connection other than its own ILO to ipmi network
20:11 mihgen actually we use Cobbler for provisioning… cobbler uses some ipmi package (don't remember which), so if it's very necessary, it should not be hard to replace ssh to ipmi.
20:11 rnelan the nodes all have vlan connections and their own connection to the ipmi network through their own ILO
20:11 mihgen the this is that for Fuel we must ensure that it will work on all the variety of hardware..
20:12 rnelan No problem.. I have to tell you I have struggled with JUJU for days.. finally gave up.. Fuel has been so much more friendly!
20:12 mihgen thanks, I hope it will solve your particular needs..  don't follow yet on your network setup
20:13 rnelan yes, it helps a lot..  I have 10 HW servers.. each with 4 nics and 1 ilo nic
20:13 rnelan the default configuration for the fuel controller is to have one nic in public and one in admin
20:14 rnelan everything else PXE's and sets up their own nics per the fuel web interface networks
20:15 rnelan Of course the interface lets me reassign nics as I want
20:15 mihgen rnelan: so how you want it?
20:15 rnelan the problem is the cisco switch isnt nearly as freindly at assigning vlans! ;)
20:15 mihgen hmm )
20:16 rnelan no, I am ok with the default setup.. just need to make sure that the switches agree on vlans..
20:16 mihgen there is network verification feature for you for this
20:16 rnelan yes.. it said i was an idiot.. ;)
20:17 mihgen btw, we have some examples in docs on how to configure vlans exactly for cisco.. let me find it
20:17 rnelan I have them.. thanks! but there is a few problems..
20:17 rnelan I am a CCNP..
20:18 mihgen oh wow)
20:18 mihgen then you don't need my stupid buggy docs)
20:18 mihgen so what's the problem?
20:18 rnelan no, but I can help with them if you like..
20:19 rnelan some configurations are for L3 switches, but listed as 2960..
20:19 mihgen I think even without vlans we have enough interfaces on your nodes..
20:19 rnelan other small things like vlan pruning commands have unneccesary spaces that cause the commands to fail
20:19 rnelan no mention of crypto key generation before ssh commands
20:19 rnelan other small things
20:20 mihgen > vlan pruning commands have unneccesary spaces - where is that?
20:20 rnelan also, there is a difference between the sample switch configs and what actually comes up in Fuel.. like interfaces that have multiple vlans that dont agree with access port configurations on the switch
20:22 rnelan you have "switchport trunk allowed 100, 101 102" note the spaces and missing comma.. it should read "switchport trunk allowed 100,101,102"
20:22 rnelan whoops forgot the vlan
20:22 rnelan sorry
20:22 rnelan you have "switchport trunk allowed vlan 100, 101 102" note the spaces and missing comma.. it should read "switchport trunk allowed vlan 100,101,102"
20:23 mihgen where is that?)
20:23 rnelan Mirantis OpenStack 4.1 pre-installation guide.pdf
20:24 rnelan oh, you mean on which ports? all trunks..
20:24 rnelan also, the uplink port to the router should be "spanning-tree portfast" as it is NOT switch to switch..
20:24 rnelan I told you.. I could help! ;)
20:25 mihgen ohh finally found that place
20:25 mihgen it appeared to be we have two places … http://docs.mirantis.com/fuel/fuel-4.1/install-guide.html#configuring-the-network
20:26 rnelan :)
20:26 mihgen thanks dude, what you mention is definitely a bug in docs..
20:27 rnelan its all good.. no problem.. also.. one other thing..
20:27 rnelan NETWORK DRAWINGS! ;) lol
20:28 rnelan especially the relationship between routed networks like admin, ipmi etc..
20:28 mihgen what deployment mode you would like to run? if it's neutron gre, you will need… admin PXE, management, public nets as minimum, right
20:29 rnelan there is also no mention of the relationships between public floating ip's and the vm's
20:29 rnelan in the case I want publicly accessible vms
20:29 rnelan yes, you are correct
20:30 mihgen there is no direct relationship… public and floating are same L3
20:30 rnelan one more bug in the docs... you cant issue the command IP ROUTE on a 2960..
20:30 mihgen and there is DNAT on controller, if you use Neutron, as I know..
20:30 rnelan no, what if I want a vm to have a publicly routable ip?
20:30 mihgen oh without private one?
20:31 rnelan yes.. not firewalled nat/pat
20:31 mihgen don't know how that can be configured with Neutron at the moment
20:31 rnelan ahh
20:33 rnelan so, a customer sets up a vm to serve for his clients.. naturally a vm spins up.. the ip address assigned is from the local non-publicly routable ip pool.. how is that association made with a firewall? manual nat/pat?
20:33 xarses joined #fuel
20:33 rnelan of course the customer wants to access his vm.. but he is on the internet
20:33 rnelan see the problem?
20:33 mihgen you can configure set of publicly routable floating IPs
20:34 mihgen then customer associates IP with VM
20:34 rnelan yes! that is what i need..
20:34 mihgen DNAT/SNAT rules are created to translate
20:34 mihgen to private IP. It's like in EC2
20:34 rnelan ok.. so.. keep that in mind..
20:35 rnelan in the network tab in fuel.. there is a place for public IPs.. I assume those are private ips inside a firewall...
20:35 rnelan the floating ip range is in a section called L3 Neutron.. it is an extension of the same /24
20:36 rnelan so... the way I understand it is that the floating IPs are indeed private but on the inside of the firewall
20:36 rnelan by the way, I am talking about a hardware firewall..
20:36 rnelan ;)
20:36 mihgen wait nope
20:37 mihgen public and floating should actually have publicly routable range
20:37 mihgen if you want your VMs to be accessible from outside
20:37 rnelan then, why do they auto configure in the 172.16.x.x?
20:37 mihgen just as an example :)
20:38 rnelan grrrrrrr.....
20:38 mihgen to be used in Vbox scripts)))
20:38 rnelan nowhere in a document did I find that solution...
20:39 mihgen (sigh) ohh docs..
20:39 e0ne_ joined #fuel
20:39 rnelan back to the drawing board
20:41 rnelan ok, well, thanks for your time.. you have been very helpful! now I need to reconfigure my networks! ;)
20:41 rmoe_ joined #fuel
20:41 mihgen thanks to you for pointing at issues in docs…
20:42 mihgen feel free to file other bugs :) launchpad.net/fuel
20:42 rnelan no problem.. I would love to meet up with the mirantis folks at the next openstack meeting!
20:43 mihgen you mean summit?
20:43 rnelan yes!
20:44 geogdog_ joined #fuel
20:44 mihgen oh that's cool :) I'm likely to miss it this time… but you will a bunch of us there for sure :)
20:47 dteselki- joined #fuel
20:48 sb- joined #fuel
20:48 mattymo joined #fuel
20:54 toha1 joined #fuel
20:55 ogelbukh joined #fuel
20:57 alex_didenko joined #fuel
21:05 vk joined #fuel
21:10 alex_didenko joined #fuel
22:38 e0ne joined #fuel
22:46 e0ne joined #fuel
23:34 e0ne joined #fuel

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