osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[openstack-dev][magnum] Using Fedora Atomic 29 for k8s cluster


pá 23. 8. 2019 v 20:59 odesílatel <feilong at catalyst.net.nz> napsal:

> On 2019-08-24 02:58, Mohammed Naser wrote:
> > On Thu, Aug 22, 2019 at 11:46 PM Feilong Wang <feilong at catalyst.net.nz>
> > wrote:
> >>
> >> Hi all,
> >>
> >> At this moment, Magnum is still using Fedora Atomic 27 as the default
> >> image in devstack. But you can definitely use Fedora Atomic 29 and it
> >> works fine. But you may run into a performance issue when booting
> >> Fedora Atomic 29 if your compute host doesn't have enough entropy.
> >> There are two steps you need for that case:
> >>
> >> 1. Adding property hw_rng_model='virtio' to  Fedora Atomic 29 image
> >>
> >> 2. Adding property hw_rng:allowed='True' to flavor, and we also need
> >> hw_rng:rate_bytes=4096 and hw_rng:rate_period=1 to get a reasonable
> >> rate limit to avoid the VM drain the hypervisor.
> >>
> >> We are working on a patch for Magnum devstack to support FA29 out of
> >> box. Meanwhile, we're starting to test Fedora CoreOS 30. Please popup
> >> in #openstack-containers channel if you have any question. Cheers.
> >
> > Neat!  I think it's important for us to get off Fedora Atomic given
> > that RedHat seems to be ending it soon.  Is the plan to move towards
> > Fedora CoreOS 30 or has there been consideration of using something
> > like an Ubuntu-base (and leveraging something like kubeadm+ansible to
> > drive the deployment?)-
> >
>
> Personally, I would like we can stay at Fedora Atomic/CoreOS since
> Magnum has already been benefited from the container-based readonly
> operating system. But we did have the discussion about using
> kubeadm+ansible, however, as you can see, it's a quite big refactoring,
> I'm not sure if we can get it done with current limited resources.
>
>
According to some notes from Magnum Train PTG meeting there is plan to move
all drivers out of tree. Despite there is no time schedule for that we
started to work on Ubuntu K8s driver which is completely independent to
openstack/magnum project and which is based on kubeadm, Heat SW Deployments
and external Openstack cloud provider. So we do not think there is much
refactoring needed. At the moment it is under heavy development, however,
at some point we plan to open the source and we will certainly appreciate
any help.


> >>
> >>
> >> --
> >> Cheers & Best regards,
> >> Feilong Wang (ç??é£?é¾?)
> >>
> --------------------------------------------------------------------------
> >> Head of R&D
> >> Catalyst Cloud - Cloud Native New Zealand
> >> Tel: +64-48032246
> >> Email: flwang at catalyst.net.nz
> >> Level 6, Catalyst House, 150 Willis Street, Wellington
> >>
> --------------------------------------------------------------------------
>
>


Jakub Slíva

Ultimum Technologies s.r.o.
Na PoÅ?íÄ?í 1047/26, 11000 Praha 1
Czech Republic

jakub.sliva at ultimum.io
*https://ultimum.io <https://ultimum.io>*

LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter
<https://twitter.com/ultimumtech> | Facebook
<https://www.facebook.com/ultimumtechnologies/timeline>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190830/3e6adf9b/attachment.html>