+1, I just ran through the install this weekend and I think rhel-ose
is the 80% right choice. If you want to learn Kubernetes: 80%, if you
want to learn OSE: 80%, if you want to build an app: 80% (you have
Docker and OSE).
One bit of information that I haven't seen in this discussion, but I
want to make sure is "on the table" are the differences in networking
between 'rhel-docker-eclipse' and 'rhel-ose' (as seen in the CDK beta
builds):
rhel-docker-eclipse: The vagrant box (VM) has an isolated network,
only specific
ports are forwarded to enabling tooling from the host.
rhel-ose: The box's network is exposed to the host and has a fixed IP
(IIRC, 10.1.2.2)
(The network configuration for the box is in the Vagrantfile)
Following Scott's point, the rhel-ose approach of making the box's
network
accessible from the host probably covers 80% of the desirable getting
started
use cases. Host based tooling, browsing web consoles and web apps
should
all work if you get the IP address right, which
vagrant-service-manager should
do for you. (So I give a +1 for the rhel-ose Vagrantfile, if anyone
cares.)
Another reason why rhea-docker-eclipse should simply just die - it is
just not
setup for non-ssh usage.
I believe there are some gotchas with the fixed IP that are probably
not obvious
to many developers:
- can only run a single box at a time.
- possible conflict if you are using the same RFC1918 private network
numbers.
(possible though improbable?)
Changing the box's IP can be tricky because the TLS/SSL certificates
have
the IP address in them. I think the certs are generated during first
provisioning
or first boot. (I haven't dug into it since trying to make
docker-machine
work a few months back.)
If there are instructions on editing the Vagrantfile there may need to
be
some pointers that the Vagrantfile configures the network, and if you
change the network config, you need to regenerate the certs, which
might
be straightforward, but they need a clue how to do it.
I could be off-base/out-of-date, but I wanted to throw this out there
to make sure it gets consideration.
afaik, if you change the ip in the vagrant file and run provisioning
again
it should work - if it does not I would consider that a bug.
/max
http://about.me/maxandersen
_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools
