[Container-tools] Why do we have "rhel-docker-eclipse"?
Burr Sutter
bsutter at redhat.com
Sat Feb 6 16:01:04 UTC 2016
One Vagrantfile would best from a user experience perspective.
The RHEL team really want an option that “turns off Openshift” and “turns on pure Kubernetes” Now, this k8s user is definitely more “hardcore” and he/she would be comfortable with some work on the linux command line to perform this trick.
Can we have one Vagrantfile that defaults to a “docker + oc” experience and offers a command line switch to go to pure k8s?
If so, does the command line switching tool have to be a Vagrant plugin and executed at the host (e.g. Windows) OR can it simply be a script that is run inside the VM after the user has used “vagrant ssh”? The k8s focused user should know Linux well enough I think, after all their experience will mostly focus on JSON file editing since that is how k8s is to be used.
The result of the switch would be “docker + kubectl”.
On February 6, 2016 at 3:51:36 AM, Max Rydahl Andersen (manderse at redhat.com) wrote:
One primary was the goal.
The rest removed or put in docs/examples.
/max
http://about.me/maxandersen
On 05 Feb 2016, at 16:24, Burr Sutter <bsutter at redhat.com> wrote:
For the GA, I believe we should be down to 2 Vagrantfiles, not 3, right?
http://screencast.com/t/srBVqOVxtZi
Can we just eliminate “rhel-docker-eclipse”?
_______________________________________________
Container-tools mailing list
Container-tools at redhat.com
https://www.redhat.com/mailman/listinfo/container-tools
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20160206/e8774237/attachment.htm>
More information about the Container-tools
mailing list