Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2015-09-01

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

All times shown according to UTC.

Time Nick Message
00:18 teran joined #fuel-dev
00:21 teran_ joined #fuel-dev
00:53 luqas joined #fuel-dev
01:04 bookwar joined #fuel-dev
01:18 sylwesterB joined #fuel-dev
01:20 dims joined #fuel-dev
02:10 tzn joined #fuel-dev
02:12 tzn joined #fuel-dev
02:34 _tzn joined #fuel-dev
03:07 sylwesterB joined #fuel-dev
03:28 gongysh joined #fuel-dev
04:00 HeOS_ joined #fuel-dev
04:25 tzn joined #fuel-dev
04:45 sylwesterB joined #fuel-dev
05:59 dims joined #fuel-dev
06:27 stamak joined #fuel-dev
06:29 alex_bh joined #fuel-dev
06:40 mkwiek joined #fuel-dev
06:59 ddmitriev joined #fuel-dev
07:07 hyperbaba joined #fuel-dev
07:12 sylwesterB joined #fuel-dev
07:18 pbrooko joined #fuel-dev
07:30 amnk joined #fuel-dev
07:32 aliemieshko_ joined #fuel-dev
07:53 stamak joined #fuel-dev
08:08 pbrooko joined #fuel-dev
08:13 e0ne joined #fuel-dev
08:33 HeOS joined #fuel-dev
08:42 dims joined #fuel-dev
08:48 e0ne joined #fuel-dev
08:52 romcheg joined #fuel-dev
08:54 romcheg1 joined #fuel-dev
08:54 tzn joined #fuel-dev
09:06 gongysh joined #fuel-dev
09:20 mkwiek hi, where can I find code for fuel-createmirror?
09:21 tzn joined #fuel-dev
09:21 SergK mkwiek, please check https://github.com/stackforge/fuel-mirror
09:21 degorenko joined #fuel-dev
09:22 mkwiek thanks!
09:23 ogelbukh it's getting much attention
09:36 dims joined #fuel-dev
09:50 ikalnitsky mkwiek: i hope you're not working with fuel-createmirror issue. i have information that it's probably fixed
09:51 mkwiek ikalnitsky: no, I was just curious :)
10:13 skolekonov joined #fuel-dev
10:30 dims joined #fuel-dev
10:38 curioswati joined #fuel-dev
10:58 tzn joined #fuel-dev
11:13 dkusidlo joined #fuel-dev
11:14 jaypipes joined #fuel-dev
11:22 dkusidlo_ joined #fuel-dev
11:25 dims joined #fuel-dev
11:30 ekosareva joined #fuel-dev
11:34 pbrooko joined #fuel-dev
11:39 ddmitriev1 joined #fuel-dev
11:47 amnk joined #fuel-dev
12:00 tzn joined #fuel-dev
12:10 pbrooko joined #fuel-dev
12:18 e0ne joined #fuel-dev
12:25 dkusidlo joined #fuel-dev
12:33 dims joined #fuel-dev
13:00 alex_bh joined #fuel-dev
13:00 tzn joined #fuel-dev
13:04 samuelBartel joined #fuel-dev
13:17 romcheg joined #fuel-dev
13:52 rgowrishankar Hello, I have a couple of questions on the role as a plugin feature for 7.0. I work for Nuage Networks and I am working on integrating Nuage SDN solution into Fuel. For the Nuage integration with OpenStack we have a monolithic plugin and replace ML2 and OVS completely. Previously, with the pre-deployment/post-deployment hooks we would have to completely undo
13:52 rgowrishankar the installation and configuration of ML2 plugin/OVS agent/DHCP agent/L3Agent done by core fuel on the controller and OVS done on the computes and then inject Nuage plugin on the controller and VRS (which is our OVS replacement) on the computes.
13:54 rgowrishankar With the plugin as a role concept, I have looked at the examples and the documentation and it looks like this is a way to completely define a new role and if we wanted to go this route, we would maintain the whole lifecycle of the controller including Nova, Cinder, Keystone installation. Is my understanding correct?
13:54 mwhahaha yes
13:54 rgowrishankar I would just like to hook into the Neutron configuration process and OVS installation process and install Nuage components instead. Is that feasible?
13:55 mwhahaha in theory it should be possible
13:55 rgowrishankar As us maintaining the lifecycle of other openstack services is not optimal..
13:56 rgowrishankar We are in the process of upstreaming some code to puppet-neutron to make configuration easier (similar to the way other vendors have plugins in puppet-neutron)
13:56 aglarendil_ joined #fuel-dev
13:57 rgowrishankar I don't see a hook in the GUI to specify which neutron core_plugin should be used. The selection upfront by the user is to choose between nova networking or neutron networking with vlans or vxlans or gre.
13:57 rgowrishankar Maybe it is in the code/CLI..
13:58 rgowrishankar ?
13:58 pbrooko joined #fuel-dev
14:02 mwhahaha so the gui settings automatically configures which type to use
14:02 mwhahaha if you need a different option that would be something you'd have to do via your plugin
14:03 pbrooko joined #fuel-dev
14:06 julien_ZTE joined #fuel-dev
14:14 angdraug joined #fuel-dev
14:21 sylweste_ joined #fuel-dev
14:21 rgowrishankar Ok. Is there a hook for plugin to be called to make the changes without having fuel configure and plugin undoing it
14:23 dkusidlo joined #fuel-dev
14:26 mwhahaha so in the newer plugin versions you can skip tasks
14:26 mwhahaha and you would have to write a replacement
14:27 mwhahaha so rather than the fuel task running, you would create your own to provide that functionatily
14:27 mwhahaha one of the main issues you're going to run into with the networking is fitting it into the complex network functionality we have and you may need to talk to someone else about those problems
14:27 mwhahaha but as far as wedging in your own tasks, let me provide you an example
14:28 mwhahaha https://github.com/stackforge/fuel-plugin-detach-rabbitmq
14:28 mwhahaha that plugin replaces the rabbitmq that sits on the controller with it's own role that can be assigned elsewhere
14:29 mwhahaha hmm that one doesn't turn off existing tasks, let me find a different example
14:29 mwhahaha that one is good for a simple adding new role only and disabling some functionality via hiera if supported by fuel
14:29 rgowrishankar Tasks within a module? So for example I can create a task for replacing configuration of ml2 with nuage plugin?
14:30 mwhahaha you'd have to skip whatever task does that and replace it with your own
14:30 mwhahaha https://github.com/stackforge/fuel-plugin-detach-keystone
14:30 mwhahaha that one actually skips existing tasks
14:30 mwhahaha specifically https://github.com/stackforge/fuel-plugin-detach-keystone/blob/master/deployment_tasks.yaml#L84-L92
14:30 mwhahaha then it would replace those skipped tasks with it's own
14:31 rgowrishankar Ah, ok.. Is there a master list of these tasks or any pointer to code from where I can find all tasks defined for neutron?
14:32 mwhahaha I don't believe so, you can pull the list of tasks
14:32 mwhahaha sec
14:32 mwhahaha fuel graph --env 1 --download
14:32 rgowrishankar Ok, will try that out. Much thanks mwhahaha
14:32 mwhahaha then you can go look in the code to figure out which tasks you'd need to replace
14:33 rgowrishankar I run the fuel graph command on the installed fuel node right?
14:34 mwhahaha on the fuel master
14:34 mwhahaha this is new functionality for 7 and i think the docs are still being put together, so there may be some additional docs coming soon
14:35 rgowrishankar ok, I already pulled the nightly 7.0 build and have it up and running.. I will run the command on that and dig through the code..
14:36 romcheg1 joined #fuel-dev
14:39 mwhahaha you can also use ./utils/task_graph/task_graph.py against the fuel-library code to see what tasks get executed for a given role
14:39 mwhahaha https://github.com/stackforge/fuel-library/blob/master/utils/task_graph/task_graph.py
14:48 pbrooko joined #fuel-dev
14:51 alex_bh2 joined #fuel-dev
14:52 dkusidlo joined #fuel-dev
14:55 rmoe joined #fuel-dev
14:57 rgowrishankar ok, I will try it out.. running fuel graph did not give enough information but it is a good start..
14:58 rgowrishankar Thanks once again..
14:58 angdraug_ joined #fuel-dev
15:01 tzn joined #fuel-dev
15:06 mattymo_ rgowrishankar, if you deploy a controller, you can see all the tasks in order by running grep manifest /etc/astute.yaml
15:06 mattymo_ (run from the controller itself, obviously)
15:06 alex_bh joined #fuel-dev
15:07 mattymo_ neutron requires cluster, cluster-haproxy, virtual_ips, database, rabbitmq, keystone, and openstack-controller (nova)
15:11 alex_bh2 joined #fuel-dev
15:11 pbrooko joined #fuel-dev
15:13 rgowrishankar mattymo: I am looking to figure out if the tasks are granular within neutron installation for me to insert replacement tasks.. I see the tasks being defined at module level but not at a more granular level when I run the fuel graph command..
15:14 mattymo_ rgowrishankar, what do you want to replace?
15:16 romcheg joined #fuel-dev
15:16 rgowrishankar For example, instead of setting core_plugin as ml2 and going down the path of configuring things associated with ml2 such as l3agent and dhcp agent and ovs agent, I want to set core plugin to something else and then in the fuel plugin that I write I want to hook in some other configuration.. I can do a rip and replace after fuel has done the default
15:16 rgowrishankar configuration but that is not as clean
15:24 amnk joined #fuel-dev
15:39 neophy joined #fuel-dev
15:48 sylwesterB joined #fuel-dev
15:55 amnk joined #fuel-dev
16:02 tzn joined #fuel-dev
16:05 dims joined #fuel-dev
16:11 RageLtMan joined #fuel-dev
16:12 RageLtMan Is there a known issue with running fuel against a KVM node for the controller services? Fuel 6 and fuel 7 both screw up the public IPs such that services dont work - fuel thinks the master is at the first ip in the given range, and it always falls to the 2nd or 3rd.
16:18 enikanorov__ joined #fuel-dev
16:27 jaypipes joined #fuel-dev
16:33 tzn joined #fuel-dev
16:48 tzn joined #fuel-dev
16:51 aignatov folks, could you please take a look on https://review.openstack.org/#/c/219316/
16:51 aignatov really appreciated :)
16:56 amnk joined #fuel-dev
17:31 neophy joined #fuel-dev
17:59 neophy joined #fuel-dev
18:29 e0ne joined #fuel-dev
18:32 amnk joined #fuel-dev
18:40 tzn joined #fuel-dev
18:40 dims joined #fuel-dev
18:42 jobewan joined #fuel-dev
18:47 jfluhmann joined #fuel-dev
18:47 neophy_ joined #fuel-dev
18:49 sylwesterB joined #fuel-dev
18:55 e0ne joined #fuel-dev
18:59 HeOS joined #fuel-dev
19:09 dims joined #fuel-dev
19:18 dims joined #fuel-dev
19:19 mkwiek joined #fuel-dev
19:25 pbrooko joined #fuel-dev
19:28 julien_ZTE joined #fuel-dev
19:29 xarses joined #fuel-dev
19:32 tzn joined #fuel-dev
19:34 kat_pimenova joined #fuel-dev
19:34 sc68cal joined #fuel-dev
19:34 higgins joined #fuel-dev
19:35 HeOS joined #fuel-dev
19:35 neophy_ joined #fuel-dev
19:35 RageLtMan joined #fuel-dev
19:35 dims joined #fuel-dev
19:42 tzn joined #fuel-dev
19:46 julien_ZTE joined #fuel-dev
19:51 stamak joined #fuel-dev
19:52 HeOS joined #fuel-dev
19:52 neophy_ joined #fuel-dev
19:52 RageLtMan joined #fuel-dev
19:55 e0ne joined #fuel-dev
20:11 julien_ZTE joined #fuel-dev
20:19 julien_ZTE joined #fuel-dev
20:25 jfluhmann joined #fuel-dev
20:45 tzn joined #fuel-dev
21:05 julien_ZTE joined #fuel-dev
21:16 e0ne joined #fuel-dev
22:00 julien_ZTE joined #fuel-dev
22:14 e0ne joined #fuel-dev
22:28 xarses RageLtMan: No, almost all of the CI testing is done in KVM vm's there are no inherent issues with KVM
22:29 xarses what settings are you passing for the network with issues?
22:40 RageLtMan xarses: i've set public subnet to 192.168.0.0/22 with allocation at 192.168.1.1-50 and floating IPs at 192.168.1.51-250
22:41 xarses RageLtMan: how many controllers?
22:41 RageLtMan 1
22:41 RageLtMan the last time the controller ended up at 192.168.1.8
22:41 RageLtMan with SSH exposed and all services broken
22:42 xarses gateway ip?
22:42 RageLtMan 192.168.0.1
22:42 xarses what did you end up setting for public, mangement networks?
22:43 xarses sorry, storage and management
22:43 RageLtMan public is on NIC1 VLAN 252. all others are are on NIC 0 as VLANs too
22:43 xarses did you change them from 192.168.1.0/24 and 192.168.0.0/24 respectively?
22:43 RageLtMan only native interface is NIC0 for PXE
22:44 RageLtMan huh?
22:44 RageLtMan the subnet is /22
22:44 RageLtMan 192.168.1.1/22 should be able to reach 192.168.0.1 without routing
22:45 xarses on the network page, what value do you have for the management and storage network CIDR's?
22:45 RageLtMan you mean the default internal IPs? yes
22:45 RageLtMan they're both in the 10 range
22:45 RageLtMan all internal is on 10's public is the only 192
22:46 RageLtMan What i find somewhat troubling is that it happens on Fuel 6.1 and 7.0 (current) and only started when i migrated from using virtualbox for fuel and management to kvm for both.
22:48 RageLtMan Luckily i back storage with ZVOLs so i'm trying to boot both Fuel and the management node in Virtualbox with the existing volumes
22:49 xarses RageLtMan: http://snag.gy/6B8Z2.jpg
22:50 RageLtMan yes, those are 10.2.10.0/24 and 10.2.11.0/24
22:54 RageLtMan What could cause the IPs to relocate?
22:54 RageLtMan should i not use the virtio NIC type in the VM?
22:54 xarses nic type will have nothing to do with the IP address allocation
22:54 julien_ZTE joined #fuel-dev
22:54 xarses virtio and e1000 should work well
22:55 xarses as I stated, we use KVM this way in nearly all of the CI
22:55 xarses I you may be seeing something wrong with the address allocation because of the supernet
22:55 rmoe joined #fuel-dev
22:56 RageLtMan is it abnormal to specify beyond a /24?
22:57 xarses for public, not really
22:57 xarses dosen't mean that there isn't some edge case in the code
22:59 xarses can you share the yaml from `fuel --env <id> network --download` and if your controller is in error state, I need the network_scheme section of the yaml generated by `fuel --env <id> deployment --default` (other sections contain secrets if you share the whole file)
23:01 xarses so in my attempt to reproduce I have controller IP set to 192.168.1.1, public_vip set to 192.168.1.2 and public_vrouter_vip set to 192.168.1.3
23:02 xarses which appears to be correct
23:02 xarses (I haven't actually deployed, just verifying the data in the files I asked from you to see if we need to go further down the stack to find the issue)
23:02 RageLtMan Not presently, i've reset the environment in hopes of fixing this. likely will have one in a few hours
23:03 xarses you can do the network download at any point
23:03 xarses the deployment default only works right when there are pending changes, or the node is in error state
23:03 xarses otherwise you can grab the same data directly from the node in /etc/astute.yaml
23:04 xarses I'll re-iterate again that astute.yaml (node yaml) contains secrets
23:06 RageLtMan this is a lab, but right now all nodes are in pre-deployment, freshly reset. You're saying i can acquire this from the fuel master?
23:06 youellet_ joined #fuel-dev
23:12 neophy_ joined #fuel-dev
23:24 dims__ joined #fuel-dev
23:47 julien_ZTE joined #fuel-dev

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