Tuesday, 2018-08-21

*** gkadam has joined #openstack-kayobe07:25
*** yankcrime has joined #openstack-kayobe08:11
openstackgerritMark Goddard proposed openstack/kayobe master: WIP: Test upgrades in CI  https://review.openstack.org/59293209:08
*** mgoddard has joined #openstack-kayobe09:10
*** ktibi has joined #openstack-kayobe10:17
ktibihi mgoddard11:06
ktibiSince I use fernet, the keystone API is very slow. Are you same issue ?11:06
ktibiare you have*11:06
ktibi-_- have you * need to sleep !11:07
yankcrimektibi: i haven't noticed any difference in performance since switching to fernet11:07
mgoddardktibi: I haven't noticed that issue, but also haven't tested it specifically11:08
yankcrimeis it slow to issue tokens or slow in general?11:08
ktibislow when I restart keystone. After 10min, keystone is fast11:10
ktibijust a curl on http://internal:500011:10
ktibidurin 10min, api take 3-4s for answer, after that 30ms11:11
yankcrimekeystone's workers don't spring into life until they've received a request11:23
yankcrimeso it's probably just that11:24
yankcrimeyou don't need to restart keystone often do you?11:24
ktibino11:52
*** ktibi has quit IRC12:56
*** dougsz_ has joined #openstack-kayobe13:34
*** orange_julius has joined #openstack-kayobe14:31
orange_juliusI'm having some issues setting up Kayobe in a KVM environment for testing. Are there are examples I can look at?14:34
mgoddardhi orange_julius, welcome14:35
mgoddardcould you tell us a little about your environment?14:36
mgoddardis it a single node all-in-one environment?14:36
mgoddardor are there multiple KVM VMs?14:36
orange_juliusHello! Sure thing. I'm just trying to set up a basic environment in KVM on my laptop with multiple VMs for different services. My laptop itself will be the seed hypervisor14:37
orange_juliusI'll probably have something simple like 1 controller VM and 1 compute VM14:37
mgoddardthat helps, thanks14:38
mgoddardin that case I would recommend keeping it simple and not using a seed14:38
mgoddardthe seed is normally used to bare metal provision the controller and compute hosts, but in this case you have VMs so this is not required14:39
mgoddardFYI we do have a Vagrant environment, although it's a single all-in-one environment and not been tested with KVM14:40
orange_juliusMy goal was to mirror what may be in production if we decide on Kayobe. Does introducing the seed add that much more complexity?14:41
mgoddardit can be done, but in a virtualised environment you would have to configure the seed's ironic service to manage the VMs as fake bare metal nodes using something like virtualbmc14:42
mgoddardI'd suggest starting with manually provisioned VMs while you get familiar with the tool14:43
orange_juliusIs there a flag for that already or would that be a manual step? I've used tripleO quite a bit and am pretty familiar with using virtualbmc/fakessh to provisiong VMs with Ironic14:43
orange_juliusI think my main issue right now is just following the documentation for any sort of install. `kayobe seed vm provision` is having issues finding some variables in hostvars[seed_host] I think and I'm just a little lost on exactly what I need to configure and where14:45
mgoddardwe don't have a simple recipe right now for using virtualbmc, although I have done it and can dig out resources if you'd like to go that route14:46
mgoddardwhat configuration are you using?14:47
orange_juliusSorry I'm not entirely sure how to answer that. I've been attempting to follow this: https://kayobe.readthedocs.io/en/latest/configuration/kayobe.html#configuring-kayobe14:48
mgoddardwe have a development environment that is geared around a single all-in-one environment, covered here: https://kayobe.readthedocs.io/en/latest/development/index.html14:49
mgoddardthat environment uses this kayobe-config repo, which provides an example of a minimal working environment: https://github.com/stackhpc/dev-kayobe-config14:50
mgoddardit's for a single host, but you could modify the inventory to add a second easily enough14:50
orange_juliusThanks thats very helpful14:51
mgoddardthe scripts under dev/ in the kayobe repo help to automate some things14:52
mgoddardout of interest, what environment are you evaluating kayobe for?14:53
orange_juliusBasically a Redhat Directory / TripleO replacement. We have had major issues with both of these tools and are in the process of evaluating other options. This will be a "production" installation eventually, but we are fine utilizing open source tooling with no enterprise support since we havn't had any success with Redhat Openstack yet14:54
mgoddardinteresting. I think you're come to the right place :)14:55
mgoddardkayobe is still evolving, but is in use in production environments14:57
mgoddardit is really a supporting role though - kolla ansible does the important work of deploying openstack, and kolla ansible is a popular tool with a broad base of support14:59
mgoddard(and lots of production use)14:59
mgoddardone point to note - most kayobe users are currently in Europe, so IRC will be quiet outside of those working hours15:01
orange_juliusGood to know! Thanks for assistance. I'm sure I'll have some more questions for you guys once I get further along15:03
mgoddardsure. have fun!15:06
*** priteau has joined #openstack-kayobe15:13
openstackgerritMark Goddard proposed openstack/kayobe master: WIP: Test upgrades in CI  https://review.openstack.org/59293216:00
*** mgoddard has quit IRC17:01
openstackgerritMark Goddard proposed openstack/kayobe master: WIP: Test upgrades in CI  https://review.openstack.org/59293217:24
*** priteau has quit IRC19:00
*** gkadam has quit IRC20:27
*** gkadam has joined #openstack-kayobe20:43
*** gkadam has quit IRC21:26
*** dougsz_ has quit IRC22:03

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!