Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-09-29

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

All times shown according to UTC.

Time Nick Message
00:01 EinstCrazy joined #fuel
00:01 josephillips joined #fuel
00:02 ZeroByte_ joined #fuel
00:14 sergmelikyan joined #fuel
00:50 tzn joined #fuel
00:51 ZeroByte_ sameissue
00:51 ZeroByte_ no network
00:51 ZeroByte_ on external interface
00:52 glavni_ninja joined #fuel
00:53 h6w ZeroByte_: Same issue as what?
00:53 ZeroByte_ ok
00:53 ZeroByte_ i use fuel
00:53 ZeroByte_ to configure public interface
00:53 ZeroByte_ i perform vlan taggin on it
00:53 ZeroByte_ the controller its on the public interface and works great
00:53 ZeroByte_ but all the vms
00:53 ZeroByte_ can get access to internet
00:53 ZeroByte_ if i check openstack network configuracion
00:53 ZeroByte_ configuration
00:53 ZeroByte_ the external interface dont have tag assigned
00:54 h6w I presume Fuel network tests came back ok?
00:54 ZeroByte_ if i try to create a new network with vlan i get a error error:unable to create network
00:54 gongysh joined #fuel
00:54 ZeroByte_ the test fail on neutron when try to do a private network cuz i dont configure the STP yet on the switch
00:55 ZeroByte_ but the problem its n the external
00:55 ZeroByte_ public interface
00:55 h6w Yes, did you do the network tests before deployment?
00:55 ZeroByte_ yes
00:55 ZeroByte_ the problem ints not the access to the vlan
00:56 ZeroByte_ because the public interface where horizon runs
00:56 ZeroByte_ can be acceced without problem
00:56 h6w Yes, and that's one of the tests that's performed in the pre-deployment phase.
00:56 ZeroByte_ ok i will create a new cloud enviroment and try it
00:56 ZeroByte_ hold on
00:56 h6w Have you run a health check on the deployed cloud?
00:57 ZeroByte_ no
00:57 ZeroByte_ let me try it
00:57 h6w You don't have to run the whole lot.  There's a "network" section that I'd try first.
00:58 ZeroByte_ Check network connectivity from instance via floating IP
00:58 ZeroByte_ i will going to doit with this
00:59 ZeroByte_ can i get a log
00:59 ZeroByte_ from this?
01:00 zhangjn joined #fuel
01:01 EinstCrazy joined #fuel
01:04 xarses joined #fuel
01:06 ZeroByte_ still runing health check
01:07 h6w Yes.  There are tonnes of logs in the log tab.
01:07 ZeroByte_ yeah im checking
01:08 ZeroByte_ i have to wait until end
01:08 h6w When the test completed, if it finds errors, it makes a recommendation as to which logs to check.
01:08 ZeroByte_ and its very weird cuz the vlans works perfect
01:08 ZeroByte_ im just have 1 interface on the compute node
01:09 ZeroByte_ and storage , managment vlans works fine
01:16 ZeroByte_ 9. Check connectivity to the floating IP using ping command.
01:16 ZeroByte_ lol
01:16 ZeroByte_ whats i get that
01:16 ZeroByte_ something that i already know
01:16 ZeroByte_ the point is
01:16 ZeroByte_ i dont understand
01:16 ZeroByte_ why in openstack the network dont look tagged
01:16 ZeroByte_ for external
01:17 ZeroByte_ and why i cant create a new network :(
01:17 ZeroByte_ with a vlan associated
01:17 zhangjn_ joined #fuel
01:27 h6w In my experience, it's usually a pre-deployment configuration problem.  We can't always test every scenario, but the pre-deployment tests cut out >80% of the basic network errors, and the health check usually catches almost all the rest.
01:28 h6w The PD check also tests to make sure that your switches are VLAN compatible, etc.  For example, some switches have ports that add a VLAN tag to clear traffic in one direction and strip it in the other direction.
01:28 h6w Obviously, if OpenStack attempts to send data this way, it's going to end up in the wrong place.
01:32 ZeroByte_ i guess i need configure
01:32 ZeroByte_ the l2 neutron
01:32 ZeroByte_ for private
01:32 ZeroByte_ im not sure
01:32 ZeroByte_ about it yet
01:32 ZeroByte_ or its not requiered
01:32 ZeroByte_ ?
01:33 h6w You have the "Use VLAN tagging" checkbox ticked in Public, yes?
01:35 ZeroByte_ yes
01:35 ZeroByte_ and also i can access to the public ip
01:35 ZeroByte_ for horizon
01:35 h6w Because the "Tunnel ID" under L2 config is for GRE tunnels, not VLAN tags.
01:36 ZeroByte_ well its enable for vlan
01:36 ZeroByte_ and like i said . horizon works on the public interface
01:36 h6w ok.
01:36 ZeroByte_ storage network work also
01:36 ZeroByte_ and managment
01:36 h6w So what did the health check say?
01:36 ZeroByte_ 9. Check connectivity to the floating IP using ping command.
01:36 ZeroByte_ im reading the logs
01:37 ZeroByte_ can i ask you something
01:37 h6w Ok.  ssh into a compute node and see if you can ping the public network from there.
01:38 h6w ovs-vsctl show is your friend, too. :-)
01:38 ZeroByte_ ok
01:38 ZeroByte_ give me one sec
01:38 ZeroByte_ the other thing
01:38 ZeroByte_ ok let me check
01:38 ZeroByte_ hold on
01:38 ZeroByte_ ah the other thing
01:39 ZeroByte_ i dont assing public ip to each node
01:39 ZeroByte_ im just assing to the controller
01:39 h6w That means that you'll only be able to communicate with other VMs.
01:40 h6w You need an IP on the Public IP range to access the VM externally.
01:41 ZeroByte_ well
01:41 ZeroByte_ i cant ping
01:41 ZeroByte_ the vm
01:41 ZeroByte_ but the problem its the VM its not taking the ip neither
01:41 ZeroByte_ i have assigned a IP Address
01:41 ZeroByte_ on the vm
01:41 ZeroByte_ but if i do ifconfig
01:41 ZeroByte_ dont have any ip associated to the computer
01:45 h6w Yep.  So Neutron is not able to assign an IP.  I'd be looking in the compute logs to see if there's an error, and I'd be looking in the Neutron logs to see if Neutron isn't configured correctly.
01:48 ZeroByte_ but the question
01:48 ZeroByte_ is
01:48 ZeroByte_ on openstack
01:48 ZeroByte_ if i saw networks
01:48 ZeroByte_ and select the external
01:48 ZeroByte_ i get this
01:48 ZeroByte_ known
01:48 ZeroByte_ Provider Network
01:48 ZeroByte_ Network Type: local
01:48 ZeroByte_ Physical Network: -
01:48 ZeroByte_ Segmentation ID: -
01:48 ZeroByte_ in segmentation id should not have the vlan where is the public network
01:48 ZeroByte_ ?
01:52 h6w Yep.  I strongly believe you have a Neutron configuration error.
01:53 h6w Nova is asking Neutron for an IP, and Neutron is chucking a hissy fit.  Nova then continues without the IP.  I've seen it many times.
01:56 ZeroByte_ the error should be
01:57 ZeroByte_ on the compute node
01:57 ZeroByte_ right
01:57 ZeroByte_ neutron run there
01:58 h6w Neutron runs everywhere.  It's what organises all the network connections.  If you have an HA deployment like I do, then everything disappears into a black whole and magically appears out the other side of the controller nodes on an IP that nobody owns. :-p
01:59 h6w And MAC that nobody owns, either.  It's breathtaking. :-p
02:00 h6w But yes, technically Neutron runs on Network nodes and terminates at compute nodes.
02:05 ZeroByte_ ok
02:05 ZeroByte_ but one question
02:05 ZeroByte_ on fuel
02:05 ZeroByte_ the neutron l2 configuration
02:05 ZeroByte_ for private network its requiered
02:05 ZeroByte_ ?
02:06 h6w Yes.  You can't get to an L3 without going through an L2.
02:07 ZeroByte_ i know
02:07 ZeroByte_ but its the part of private network configuration
02:07 h6w L2 = GRE.  So you can have VMs on different nodes think they're on the same network.
02:08 h6w Private for the VMs, yes.  Private for the nodes, no.
02:10 ZeroByte_ i upgrade to 7.0
02:10 ZeroByte_ and now everything is screw up
02:10 ZeroByte_ now i cant upload images neither
02:10 ZeroByte_ im going to home
02:10 ZeroByte_ im tired of this
02:12 h6w Yeah.  7.0's not yet released.  I've still seen bugs submitted as of yesterday.
02:12 h6w Upgrade path certainly not tested.  If I'm going to use it, I'd start with a clean install only.
02:13 h6w (Well, I'm sure it's been tested, but just not well enough, and not in enough real-world environments yet.)
02:23 ZeroByte_ yeah im testing it
02:23 ZeroByte_ but i cant sole the issue
02:23 ZeroByte_ with 6.1
02:23 ZeroByte_ about network
02:24 ZeroByte_ i make few changes
02:24 ZeroByte_ to see whats going on
02:36 eliqiao left #fuel
02:38 h6w Based on the description you've given me, I'm pretty sure you'll find the same behaviour in 7.0 as in 6.1, but in 7.0 you'll be dealing with less-tested code.
03:16 tzn joined #fuel
03:44 fedexo joined #fuel
04:04 vsedelnik joined #fuel
04:10 zhangjn joined #fuel
04:16 dcs_ joined #fuel
04:20 vsedelnik joined #fuel
04:31 ZeroByte_ well
04:32 ZeroByte_ im already fix my problems with l2 neutron , im deploying to see if work or not
04:50 lucasPR joined #fuel
04:53 zhangjn joined #fuel
05:21 pradiprwt joined #fuel
05:26 vsedelnik joined #fuel
05:42 neophy joined #fuel
05:45 sergmelikyan joined #fuel
06:04 pradiprwt joined #fuel
06:06 pradiprw_ joined #fuel
06:06 sergmelikyan joined #fuel
06:27 e0ne joined #fuel
06:38 sergmelikyan joined #fuel
06:41 mgrohar joined #fuel
06:45 neilus joined #fuel
06:53 v1k0d3n joined #fuel
06:53 severion joined #fuel
06:59 mkwiek joined #fuel
07:07 e0ne joined #fuel
07:08 pal_bth joined #fuel
07:17 hyperbaba joined #fuel
07:20 sergmelikyan joined #fuel
07:21 e0ne joined #fuel
07:37 xarses joined #fuel
07:50 mgrohar joined #fuel
08:07 pradiprwt joined #fuel
08:14 tzn joined #fuel
08:30 JoeStack joined #fuel
08:37 vsedelnik joined #fuel
08:38 julien_ZTE joined #fuel
08:46 saibarspeis joined #fuel
08:49 devvesa joined #fuel
08:51 HeOS joined #fuel
08:56 keyz182 joined #fuel
08:58 pradiprwt joined #fuel
09:04 pradiprw_ joined #fuel
09:05 sergmelikyan joined #fuel
09:22 sergmelikyan joined #fuel
09:26 julien_ZTE joined #fuel
09:27 neophy joined #fuel
09:30 sergmelikyan joined #fuel
09:30 tzn joined #fuel
09:30 vsedelnik joined #fuel
09:35 sergmelikyan joined #fuel
09:43 vsedelnik joined #fuel
09:48 vsedelnik joined #fuel
09:58 sergmelikyan joined #fuel
10:17 vsedelnik joined #fuel
10:20 neilus joined #fuel
10:22 pradiprwt joined #fuel
10:31 Chlorum joined #fuel
10:43 sergmelikyan joined #fuel
10:45 vsedelnik joined #fuel
11:01 sergmelikyan joined #fuel
11:04 EinstCrazy joined #fuel
11:07 az__ joined #fuel
11:22 mgrohar joined #fuel
12:09 osryan Will Fuel 7.0 still have the Calico plugin? In one of the nightly builds I tried, it had it as an option without a plugin but I don't see it anymore.
12:10 neilus joined #fuel
12:10 dklepikov joined #fuel
12:12 aarefiev joined #fuel
12:16 pradiprwt joined #fuel
12:27 mgrohar joined #fuel
12:28 vsedelnik joined #fuel
12:40 EinstCrazy joined #fuel
12:45 goukos joined #fuel
13:02 pradiprwt joined #fuel
13:02 vsedelnik joined #fuel
13:12 pal_bth_ joined #fuel
13:18 vsedelnik joined #fuel
13:32 vsedelnik joined #fuel
13:37 vsedelnik joined #fuel
13:46 julien_ZTE joined #fuel
13:47 vsedelnik joined #fuel
13:49 jaypipes joined #fuel
13:51 mgrohar joined #fuel
13:52 neophy joined #fuel
13:54 sergmelikyan joined #fuel
13:57 vsedelnik joined #fuel
14:08 xarses joined #fuel
14:26 claflico joined #fuel
14:27 az__ osryan: there'll still be calico plugin for fuel 7
14:28 az__ osryan: I'm not sure how you were able to see some calico specific options without plugin
14:28 az__ I haven't seen such build personally
14:28 osryan az__: thank you. i saw it as one of the options when you choose the type of networking when you first create your cloud
14:31 vsedelnik joined #fuel
14:34 az__ osryan: hm, that's strange, I'm sure it shouldn't have been there
14:36 osryan i wish i could remember how i saw it. i am pretty certain it was a nightly build. maybe im going crazy
14:36 osryan which is just as likely really
14:40 thansen joined #fuel
14:48 sergmelikyan joined #fuel
14:59 angdraug joined #fuel
15:01 vsedelnik joined #fuel
15:11 julien_ZTE joined #fuel
15:19 jobewan joined #fuel
15:24 vsedelnik joined #fuel
15:29 blahRus joined #fuel
15:32 lucasPR joined #fuel
15:42 vsedelnik joined #fuel
15:49 julien_ZTE joined #fuel
15:55 youellet joined #fuel
16:04 vsedelnik joined #fuel
16:10 EinstCrazy joined #fuel
16:19 thansen joined #fuel
16:27 mkwiek joined #fuel
16:30 sbfox joined #fuel
16:34 angdraug joined #fuel
16:39 sergmelikyan joined #fuel
17:07 richoid joined #fuel
17:44 championofcyrodi interesting.  so the red herring that was binding host_id for neutron port being a decommissioned node, was actually solved by removing the network adapter from the VM, and adding it back. (Windows 7 N VM)
17:44 championofcyrodi i figured it was VM related, because although some of the other instances show the decommissioned node as the binding:host_id in the database, their connectivity worked fine.
17:45 championofcyrodi *works
17:45 championofcyrodi i should probably migrate them as well though.
17:49 sbfox joined #fuel
18:27 HeOS joined #fuel
18:34 xarses joined #fuel
18:40 tobiash joined #fuel
18:52 neophy_ joined #fuel
19:03 sbfox joined #fuel
19:23 vsedelnik joined #fuel
19:31 vsedelni_ joined #fuel
19:36 sergmelikyan joined #fuel
19:39 neophy joined #fuel
19:39 angdraug joined #fuel
19:59 az__ joined #fuel
20:00 vsedelnik joined #fuel
20:14 e0ne joined #fuel
20:27 az__ joined #fuel
20:32 nurla joined #fuel
20:32 bdudko joined #fuel
20:33 sbfox joined #fuel
20:35 aglarendil_ joined #fuel
20:48 aglarendil_ joined #fuel
20:55 sergmelikyan joined #fuel
21:19 sbfox joined #fuel
21:59 nurla joined #fuel
22:05 aglarendil_ joined #fuel
22:35 xarses joined #fuel
23:07 CheKoLyN joined #fuel
23:13 julien_ZTE joined #fuel
23:27 Zer0Byte__ joined #fuel
23:27 Zer0Byte__ hey
23:31 glavni_ninja_ joined #fuel
23:33 preilly joined #fuel
23:33 zimboboyd joined #fuel
23:33 tkhno joined #fuel
23:34 pbrzozowski joined #fuel
23:34 charz joined #fuel

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