Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2016-10-03

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

All times shown according to UTC.

Time Nick Message
00:00 tatyana joined #fuel
00:37 fatdragon joined #fuel
00:51 natarej joined #fuel
01:48 ilbot3 joined #fuel
01: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/
04:41 failart_ joined #fuel
05:09 code-R joined #fuel
05:13 code-R joined #fuel
05:37 raunak joined #fuel
05:52 raunak joined #fuel
05:57 raunak joined #fuel
06:11 raunak joined #fuel
06:48 vvalyavskiy_1 joined #fuel
06:58 tatyana joined #fuel
07:04 nickola joined #fuel
07:44 fatdragon joined #fuel
08:02 code-R joined #fuel
08:04 code-R_ joined #fuel
08:40 dave-johnston joined #fuel
08:45 fatdragon joined #fuel
08:56 fatdragon joined #fuel
09:25 Matti_ joined #fuel
09:39 Alcest joined #fuel
09:43 vkulanov joined #fuel
09:57 fatdragon joined #fuel
10:20 vvalyavskiy vkulanov: hi, could you please check comments in  https://review.openstack.org/#/c/371220/ patch? I just want to clarify concerns.
10:22 vkulanov vvalyavskiy, hi! Ok, need some time
10:48 dancn joined #fuel
11:28 Vijayendra joined #fuel
12:04 ekosareva joined #fuel
12:26 ikalnytskyi hey guys. i wonder, why don't we have stabke/newton branch in fuel? does anybody know?
12:34 ekosareva_ joined #fuel
12:41 GMAzrael joined #fuel
12:48 kaliya joined #fuel
12:54 ekosareva joined #fuel
13:13 goldenfri joined #fuel
13:16 venkat joined #fuel
13:33 vkramskikh ikalnytskyi: because it's not Oct 5 yet :)
13:34 vkramskikh python/nailgun folks, please review/merge https://review.openstack.org/#/c/380215/ - I'd really like this patch to be merged before the freeze
13:34 vkramskikh it's fake keystone API v3
13:51 GMAzrael Any approved method of getting SPICE for console viewing installed?
13:55 kaliya GMAzrael: reconfigure nova manually
13:55 GMAzrael Would the configurations be re-written on a fuel redeploy?
13:56 kaliya of course
13:57 kaliya unless you create a fuel plugin to reconfigure nova
13:58 fatdragon joined #fuel
14:06 null_ref joined #fuel
14:24 GMAzrael Is there a backup procedure for MOS 9.0 Fuel controller? I see there is no guide for it
14:26 kur1j joined #fuel
14:29 kaliya The fuel master node?
14:29 GMAzrael yes
14:31 kur1j what would be an easy way to update libvirt on a compute node with fuel?
14:31 kur1j would like to try something later than 1.2.9
14:37 andreww joined #fuel
14:44 fatdragon joined #fuel
14:45 failart_ joined #fuel
14:47 ekosareva_ joined #fuel
14:56 failart_ joined #fuel
15:01 GMAzrael Can someone update https://wiki.openstack.org/wiki/Fuel/Release_Schedule for new release dates for 9.1 RTM etc.
15:03 cr0wrx joined #fuel
15:08 cr0wrx anyone know how I can change the cidr range for haproxy public stuff (b_public, namespace, wherever)?
15:18 andreww cr0wrx: its taken from the value of the public network on the network settings page
15:22 xarses kozhukalov: ashtokolov ^^
15:33 cr0wrx @andreww I know originally it is. This is post deploy and since deploy I've had to adjust network settings a bit (using my own config managament since fuel doesn't support)
15:34 cr0wrx so I fixed my issue by manually editing route table / interface of b_public within the haproxy namespace. I can't see where those get generated on boot though to ensure it will persist.
15:34 cr0wrx Does it automatically pull from ifcfg-br-ex, which has <addr>/<mask> ?
15:34 xarses cr0wrx: crm configure edit
15:35 ekosareva joined #fuel
15:35 xarses also, you basically cant use fuel any more unless you bring it's data in line to what you changed
15:35 johnavp1989 joined #fuel
15:36 cr0wrx yea, it's starting to be a little more of a pain. I can use fuel to deploy new nodes, but I still need to run my own config management against new nodes after the fact to bring them up to speed
15:36 xarses if this is 9.0, it could re-run tasks on the controller, even when running computes
15:37 cr0wrx thanks for crm configure edit, I think I see mask info and whatnot in here that I should update
15:37 cr0wrx this is 8.0 :/
15:38 cr0wrx I'm not sure how I can bring fuel up to speed unless there is a way to manually override it's network config. I saw that fuel added network templates but it seems you can't use or modify post deploy
15:40 cr0wrx ok, on crm configure, is this shared across the cluster? I'm still not that familiar with crm / pcs / pacemaker stuff. If I edit settings here on this controller, does it take affect on other controllers (which I don't have, 1 controller setup right now) or future added controllers? Or do I need to run crm configure edit on each node once deployed?
15:42 xarses its shared to the cluster once you close it
15:43 xarses if you deploy more controllers, fuel will revert all of the custom changes on this one
15:45 cr0wrx good to know
15:45 cr0wrx does that include these crm configure edit changes?
15:46 cr0wrx or just things like network interfaces? All the network interfaces I have pulled out into ansible so I could just re-run and have it change everything back again :D assuming other issues don't arise (my understanding is it's already deployed in HA mode with single controller)
15:47 xarses everything that fuel would have configured in the first place would be reverted if fuel doesn't know the new desired state
15:48 xarses prior to 8.0, the controllers will only do this if you add/remove another controller
15:48 cr0wrx I'm on 8.0 no
15:48 cr0wrx now
15:48 xarses sorry, prior to 9.0
15:48 cr0wrx what about in 9? It can randomly do it? or other times?
15:48 cr0wrx I actually have a second cluster with 9
15:48 cr0wrx which more or less has the same issue
15:49 xarses this will also cause some tasks on the compute notes to re-execute, but it should only impact the rabbit config
15:49 failart_ joined #fuel
15:49 cr0wrx basically on both networks I've switched to several provider networks, which fuel UI didn't handle (only sets up 1 floating network).
15:49 xarses compute nodes being deployed will generally not do anything to the rest of the cluster, with exception of the /etc/hosts update routine
15:50 cr0wrx If there is a way to hack my current state into fuel, I would. I just don't know where to start and have read/heard it isn't natively supported
15:50 xarses for 9.0, there is the newer ability to update more settings, but it has some bugs that things like compute node provisions may cause tasks to execute on the controllers resetting some config
15:50 cr0wrx yea but it also doesn't allow network changes is my understanding post deploy
15:51 cr0wrx which is our biggest change from fuel deployed state
15:51 xarses probably not, the team never liked the idea of supporting that =(
15:51 xarses https://gist.github.com/xarses/16cd1504c31cb07e8e104b80f200eff5
15:51 xarses was designed for 7.0, but appears to work on 8
15:51 xarses backup your db before using
15:51 cr0wrx I imagine somewhere on fuel master there is something that has the current network state though (db, some file, idk somewhere)...so in theory it SHOULD be allowed to override? but idk
15:52 xarses see the gist
15:54 xarses it goes through the nailgun object orm to update the stored values in the db, if it works against 8, it will update the db using the same code that the api's do, but just ignore the checking
15:55 xarses you could possibly update the db by hand, but that should be avoided, this would follow all of the relations described in the ORM and get them to update the relations correctly
15:56 cr0wrx interesting. Maybe with this or db I can at least update the cidr for the default network group (what I just had to do for haproxy)
15:57 cr0wrx I haven't used other network groups in fuel to really understand how they work to know if I can get our actual network in fuel
15:58 cr0wrx I'm sure our current setup is a bit hacky and not the most optimal or ideal solution :D
16:03 Matti_ joined #fuel
16:09 cr0wrx so for network groups, is that something that coudl be used to add a new provider network? Or...something different? I know the way the default network group ran it set up a floating network (br-floating) using the specified vlan and all
16:10 cr0wrx is the network group what controls creation of interfaces such as br-floating (and mapping between br-ex and br-floating, etc)?
16:11 xarses so network groups are for example the public network
16:12 xarses if you want to use different (more or less) network groups, you need to do that via network templates
16:12 cr0wrx the public network meaning? I was never very clear on what that meant. horizon/APIs/etc. but it also seems to roll up the "public" floating network as well
16:13 xarses it goes like this env -> node groups -> network groups -> network roles -> service endpoints
16:14 xarses with network templates being able to re-assign network groups and roles beyond the default
16:15 cr0wrx yea, I think network templates allow creation of different interfaces / etc. on a lower level, which would support configuring all the things for provider networks. But they must be used pre-deploy of cluster.
16:15 xarses cr0wrx: if you look at the network roles map in the hiera data, you can see all of the endpoints mappings to network group
16:16 cr0wrx it would be nice (although probably a pain to write the network template) if I could create a template (now, post deploy) and then tell fuel to use it for future deploys
16:16 cr0wrx ok, I'll have to track down hiera data :) never seen or used before, looks like a puppet thing
16:17 xarses . /etc/astute.yaml
16:17 xarses on a deployed node
16:18 cr0wrx k, thanks
16:18 xarses (pre 9.0) you can do fuel deployment --env <id> default with nodes not deployed and retrieve it
16:18 xarses post you can do it at any point
16:19 cr0wrx I'm very much a fuel n00b. I've been meaning to try and learn it much more but it's kinda tricky to track down all the right docs I guess for fuel
16:19 xarses here is where the defaults are https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L168-L380
16:19 cr0wrx much easier for openstack, but fuel specific stuff is harder to figure out
16:20 cr0wrx so this far, I've really only used fuel UI to set up a basic config / deploy cluster, and then any changes from that I've gone outside of fuel to do, which certainly will cause some issues (like this)
16:20 xarses but if you have plugins, they can create their own network roles meta, so you can find the combined data in the astute.yaml
16:20 vvalyavskiy left #fuel
16:20 xarses or from that fuel cli command
16:22 cr0wrx thanks
16:27 cr0wrx xarses: is /etc/astute.yaml used post deploy for anything? Or is it just generated and copied over or something as part of deploy process?
16:28 cr0wrx for example, I am adjusting cidr range for public network, I can adjust routes in haproxy namespace, adjust crm configure edit, er..edit values in db using your script to update default, etc....but what about /etc/astute.yaml on deployed node? It also has the old value
16:31 cr0wrx and whatever generates the network_scheme: transformations and interfaces section in astute.yaml looks like exactly what I need to modify for fuel to persist our provider networks on new nodes..I'm guessing that's from network templates or something else though
16:53 xarses cr0wrx: its the config source used to dictate what puppet should configure the state of the node to
16:54 xarses its re-generated every time you run a task via fuel on the node
16:55 cr0wrx ok. I'm not as familiar with puppet as I should be. So essentially fuel generates it, copies it to the node, and puppet loads that config and runs on node
16:56 cr0wrx sounds like for my cidr issue if I update fuel db then any new puppet runs on nodes should copy new astute.yaml and pick up the changes
16:58 ashtokolov xarses: GMAzrael: thanks! I've updated the release page
17:32 raunak joined #fuel
17:44 johnavp1989 joined #fuel
18:02 cr0wrx xarses: for reference your adjust networks script doesn't work against 8.0 due to "NeutronManager80' has no attribuet '_set_ip_ranges'
18:02 cr0wrx but I managed to reference script and update tables as needed I think
18:38 johnavp19891 joined #fuel
18:59 kur1j Is there a newer version of libvirt that is available through mos?
18:59 kur1j newer than 1.2.9
19:15 fatdragon joined #fuel
19:15 tatyana joined #fuel
19:45 fatdragon joined #fuel
19:58 raunak joined #fuel
20:18 fatdragon joined #fuel
21:48 failart_ joined #fuel
22:53 fatdragon joined #fuel

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