Forgot to add the link for the reference: [1] https://code-ready.github.io/crc/ - section 1.4
On Sun, Sep 22, 2019 at 3:35 PM Just Marvin < marvin.the.cynical.ro...@gmail.com> wrote: > Daniel, > > TBH, I didn't follow a lot of that. But the bit that I did get was > your recommendation to try the full OCP install instead of CRC. I'll give > that a try. > > FYI, I did enable nested virtualization on GCP, and progressed quite a > bit further. I will note that the install instructions [1] need to list > qemu-kvm as a packaged to be installed on Centos7. But in the end, I failed > at this point: > > INFO Loading bundle: crc_libvirt_4.1.11.crcbundle ... > INFO Extracting bundle: crc_libvirt_4.1.11.crcbundle ... > INFO Creating VM ... > INFO Verifying validity of the cluster certificates ... > INFO Check internal and public dns query ... > INFO Copying kubeconfig file to instance dir ... > INFO Adding user's pull secret and cluster ID ... > ERRO Error occurred: Failed to update user pull secret or cluster ID: ssh > command error: > command : timeout 80 bash -c 'until oc --config /tmp/kubeconfig replace -f > /tmp/pull-secret.yaml 2>/dev/null 1>&2; \ > do echo "Waiting for recovery apiserver to come up."; sleep 1; done' > err : exit status 124 > output : Waiting for recovery apiserver to come up. > Waiting for recovery apiserver to come up. > Waiting for recovery apiserver to come up. > > Not sure what is going on. Probably, as you mentioned, networking > hasn't been set up in a fashion that allows the ssh to work. > > Regards, > Marvin > > On Sat, Sep 21, 2019 at 3:36 AM Daniel Veillard <veill...@redhat.com> > wrote: > >> On Fri, Sep 20, 2019 at 04:47:09PM -0400, Just Marvin wrote: >> > Daniel, >> > >> > I appreciate the insights into the challenges. The goal that you >> > stated, though, is going to be hard to achieve with a limitation of >> > bare-metal only for developers. See the other thread in this forum for >> the >> > service mesh. The kind of resource requirements, as stated in that >> thread, >> > needed to do something like that on CRC will rarely be found on a >> developer >> > laptop. So, for someone like me, the choice really boils down to >> running a >> > full-fledged OCP on a dedicated machine / VM if I want to try out / >> > experience something like the OpenShift Service Mesh. And such dedicated >> > machines / VMs are hard to come by unless one uses the public cloud. >> So, I >> > hope that running in such an environment becomes easier for CRC. >> > >> > Regards, >> > Marvin >> >> Hi Marvin, >> >> Hum, there is something I don't understand, >> if you are going to use a dedicated machine to run your OCP workload, why >> not run the full install then. We made a number of choice to be able to >> adapt to the laptop situation: >> - single node, hence only one VM to minimize the memory footprint >> and trashing between competing VMs >> - pre-baked installation, so that CRC is usable nearly immediately >> after download compared to the time it would take to run the installer >> fetch everything and run the install process on a laptop hard drive >> - disable a number of operators which are part of a full fledged install >> of OCP to reduce the memory footprint, most notably the telemetry >> part. >> >> Some of those I would avoid if I were to install my devel cluster on >> a 64 GB tower I have laying around in my office. The install would have to >> be done once, not on my main machine so no big deal if it takes one hour, >> it would be closer in behaviour to a full cluster on AWS too. >> >> We added back last year the minishift --remote for those use case >> because >> TBH running the Ansible playbook for 3.x on a random Linux install was a >> bit >> of a challenge. But for CRC that's not really possible, we don't run the >> installer, it's pre-cooked, and requires the CoreOS base, so I don't see >> how we could ever do this. >> >> One of the scenario we could try is to take the installed bundle VM >> content >> and try to run it inside a container instead of a VM, but that means no >> guarantee on the kernel behaviour, nor system library, and sorting out >> networking would likely be case by case. >> >> I wonder if the real solution isn't for those case to make it easier >> for people to run the libvirt side of the installer directly. Another >> option >> is the Ansible route, though TBH I don't know how well that's supported >> in 4.x >> >> Hope this makes sense, >> >> Daniel >> >> > On Fri, Sep 20, 2019 at 9:21 AM Daniel Veillard <veill...@redhat.com> >> wrote: >> > >> > > On Thu, Sep 19, 2019 at 10:00:40PM -0300, Fernando Lozano wrote: >> > > > Yes, bare-metal only. >> > > >> > > Hi, >> > > >> > > I'm the manager for the CRC group. >> > > We indeed tested it only on bare metal. The goal is really to provide >> > > a quick and easy way for a developer to run OCP 4.x on their laptop. >> > > That said as Joel suggested you may try to enable nested >> virtualization >> > > this will likely allow to boot the VM. Then it's a question of >> networking >> > > usually, virt takes 20% of the effort, networking is the 75% of the >> > > remaining problems <grin/> >> > > >> > > Daniel >> > > >> > > > On Thu, Sep 19, 2019 at 8:50 PM Just Marvin < >> > > > marvin.the.cynical.ro...@gmail.com> wrote: >> > > > >> > > > > Fernando, >> > > > > >> > > > > Is CRC only expected to run on bare-metal? I tried running it >> on a >> > > VM >> > > > > in GCP and it didn't work, complaining about virtualization >> problems >> > > (sorry >> > > > > - forget the exact error). It runs find on my laptop, but I'd >> really >> > > like >> > > > > to not muddy up my laptop with all kinds of experimental things. >> > > > > >> > > > > Regards, >> > > > > Marvin >> > > > > >> > > > > On Wed, Sep 18, 2019 at 12:35 PM Fernando Lozano < >> floz...@redhat.com> >> > > > > wrote: >> > > > > >> > > > >> Hi Joel, >> > > > >> >> > > > >> Yes, CRC requires virtualization. It creates and manages a VM, >> using >> > > the >> > > > >> hypervisor provided by your laptop OS, and runs OpenShift inside >> that >> > > VM. >> > > > >> AFAIK there is no more all-in-one containerized support for >> OpenShift >> > > so >> > > > >> more 'oc cluster up' for OpenShift 4.x. >> > > > >> >> > > > >> []s, Fernando Lozano >> > > > >> >> > > > >> >> > > > >> On Wed, Sep 18, 2019 at 9:44 AM Joel Pearson < >> > > > >> japear...@agiledigital.com.au> wrote: >> > > > >> >> > > > >>> With CodeReady Container, it's not possible to use it without >> > > > >>> virtualisation right? Because it needs CoreOS, and can't >> startup on >> > > an >> > > > >>> existing docker installation like you can with "oc cluster up"? >> > > > >>> >> > > > >>> I'm only asking because I almost got OKD 3.11 running on >> Windows 10 >> > > WSL >> > > > >>> (windows subsystem for linux) v2. But if it's a full VM, then >> > > running >> > > > >>> inside WSL 2 doesn't really make sense (and probably doesn't >> work >> > > anyway). >> > > > >>> >> > > > >>> On Sat, 14 Sep 2019 at 02:35, Daniel Comnea < >> comnea.d...@gmail.com> >> > > > >>> wrote: >> > > > >>> >> > > > >>>> Recently folks were asking what is the minishift's alternative >> for >> > > v4 >> > > > >>>> and in case you've missed the news see [1] >> > > > >>>> >> > > > >>>> Hopefully that will also work for OKD v4 once the MVP is out. >> > > > >>>> >> > > > >>>> >> > > > >>>> Dani >> > > > >>>> >> > > > >>>> [1] >> > > > >>>> >> > > >> https://developers.redhat.com/blog/2019/09/05/red-hat-openshift-4-on-your-laptop-introducing-red-hat-codeready-containers/ >> > > > >>>> _______________________________________________ >> > > > >>>> users mailing list >> > > > >>>> users@lists.openshift.redhat.com >> > > > >>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > > >>>> >> > > > >>> >> > > > >>> _______________________________________________ >> > > > >>> users mailing list >> > > > >>> users@lists.openshift.redhat.com >> > > > >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > > >>> >> > > > >> _______________________________________________ >> > > > >> users mailing list >> > > > >> users@lists.openshift.redhat.com >> > > > >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > > >> >> > > > > >> > > >> > > > _______________________________________________ >> > > > users mailing list >> > > > users@lists.openshift.redhat.com >> > > > http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > >> > > >> > > -- >> > > Daniel Veillard | Red Hat Developers Tools >> > > http://developer.redhat.com/ >> > > veill...@redhat.com | libxml Gnome XML XSLT toolkit >> http://xmlsoft.org/ >> > > http://veillard.com/ | virtualization library http://libvirt.org/ >> > > >> >> -- >> Daniel Veillard | Red Hat Developers Tools >> http://developer.redhat.com/ >> veill...@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ >> http://veillard.com/ | virtualization library http://libvirt.org/ >> >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
