On 8 July 2016 at 07:48, Praveen Kumar <[email protected]> wrote: > On Fri, Jul 8, 2016 at 12:09 AM, Lalatendu Mohanty <[email protected]> > wrote: >> >> Hi Clayton, >> >> I have not tried minishift or "oc cluster up" yet . So I am little confused >> at this point. Not sure if these two methods competes with each other or >> not. What is your opinion on this? > > > I did try both, minishift is for creating the environment (on > different platform) then running openshift binary (as of now). Now we > can use 'oc cluster up' once we have have endpoints of deployed > openshift server using minishift which currently is not working[0] but > I think this is the idea.
The idea is that you shouldn't need to run `oc cluster up` as `minishift start` is the equivalent command. Right now it does a bit less than `oc cluster up`, not installing registry/router which may see like overkill for most dev tasks where you can simply use the VM's Docker daemon for image builds, etc & perhaps relying on NodePort services for connecting in to your service from the host. This keeps footprint as small as possible (running a registry & router obviously requires resources) while allowing most dev tasks, at the expense of the full production style deployment. I feel that's a reasonable trade off for a local dev kit. > > [0] https://github.com/jimmidyson/minishift/issues/2 This is now fixed btw - try out v0.1.1 (https://github.com/jimmidyson/minishift/releases/tag/v0.1.1). > > -- > Praveen Kumar > https://fedoraproject.org/wiki/User:Kumarpraveen _______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
