| *** LinuxMe has joined #kata-general | 00:21 | |
| *** LinuxMe has quit IRC | 00:26 | |
| *** LinuxMe has joined #kata-general | 01:21 | |
| *** LinuxMe has quit IRC | 01:26 | |
| *** LinuxMe has joined #kata-general | 02:17 | |
| *** stackedsax has joined #kata-general | 02:21 | |
| *** LinuxMe has quit IRC | 02:22 | |
| kata-irc-bot | <torque_wrexer> i have another question : kata/k8s can provision and commission network seperated machines? | 02:34 |
|---|---|---|
| *** LinuxMe has joined #kata-general | 04:18 | |
| *** LinuxMe has quit IRC | 04:23 | |
| *** lpetrut has joined #kata-general | 04:39 | |
| *** LinuxMe has joined #kata-general | 04:50 | |
| *** LinuxMe has quit IRC | 04:55 | |
| *** lpetrut has quit IRC | 05:08 | |
| kata-irc-bot | <raravena80> not really. kata and k8s don't provision machines. You can run kata/k8s and the machines you provision (regardless of the method on how you provision them) :slightly_smiling_face: keep in mind that the machines need to either nested virt or be bare-metal for kata to work. | 05:33 |
| *** LinuxMe has joined #kata-general | 06:49 | |
| *** LinuxMe has quit IRC | 06:53 | |
| *** LinuxMe has joined #kata-general | 07:28 | |
| *** LinuxMe has quit IRC | 07:33 | |
| *** sameo has joined #kata-general | 08:09 | |
| *** gwhaley has joined #kata-general | 09:32 | |
| kata-irc-bot | <torque_wrexer> @raravena80, ahhh, so that is a reason why maas maybe should be used as a privisioning agenti would guess. | 10:36 |
| *** lpetrut has joined #kata-general | 11:43 | |
| *** stackedsax has quit IRC | 13:38 | |
| *** LinuxMe has joined #kata-general | 14:12 | |
| *** lpetrut has quit IRC | 15:10 | |
| *** LinuxMe has quit IRC | 15:37 | |
| *** LinuxMe has joined #kata-general | 16:04 | |
| *** gwhaley has quit IRC | 18:05 | |
| *** sameo has quit IRC | 19:35 | |
| *** openstack has joined #kata-general | 20:18 | |
| *** ChanServ sets mode: +o openstack | 20:18 | |
| *** stackedsax has joined #kata-general | 20:30 | |
| *** LinuxMe has quit IRC | 20:54 | |
| kata-irc-bot | <razvan.rosca> > yes cgroups will allow you to throttle the CPU: `--cpu-shares=0`, `--cpu-period`,` --cpu-quota` in Docker. CPU Request and Limit in a pod in k8s. Keep in mind that, you have to make sure that your VM in Kata has enough resources for whatever you are trying to accomplish. Ok, so basically I can limit all 3 main resources - cpu, ram and io - for any given docker container? I'm thinking at a combination between the benefits of a | 22:30 |
| kata-irc-bot | docker ct combined with the isolation (software and resources) of a KVM VM. | 22:30 |
| kata-irc-bot | <razvan.rosca> Aka "a faster, easier VM". Is that valid? | 22:31 |
| kata-irc-bot | <eric.ernst> Yeah, we have all the usual benefits of a container (image/bundling your workload, orchestration, first layer of isolation) combined with a second layer of isolation (hardware virtualization —> a vm) | 23:17 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!