On 08/01/2016 01:53 PM, Vineet Reynolds Pereira wrote:
Hello list,
I tried out CDK 2.1 on a brand new Macbook, to test drive the
installation experience. An installation was also attempted on a Linux
box by someone in my team; he eventually installed CDK on a Debian
host instead of a RHEL 7 VM on the same host. I'll focus on Mac, since
we're looking at Windows and Mac users primarily. There are some
suggestions to improve this experience.
We have tested CDK on RHEL 7. So if does not work then we need to
findout the issues. Can you please request your team member to send the
issues.
* Vagrant version issues (Mac)
I started with Vagrant 1.8.5 (the latest), then ran into this bug
with SSH keys [1] when bringing up the CDK vagrant box. Tried
downgrading to 1.8.4, and ran into this one [2] involving installation
of local gems supplied by CDK. Ultimately, I downgraded all the way
down to 1.8.1, because the CDK version "appeared" to have been tested
against it.
* Virtualbox version issues (Mac)
Vagrant 1.8.5 supports Virtualbox 5.1.x (latest) [3], but on
downgrading vagrant to 1.8.1, it proceeds to download Virtualbox 5.0
when bringing up the Vagrant box. Vagrant fails to download and
install Virtualbox for some reason (I didn't bother to debug any more
vagrant issues at this point), and went and manually downgraded
Virtualbox to 5.0.26. That's three downgrades in one installation session.
* Documentation for Linux users
I'm a bit lost on this area, since there might a product direction
I'm unaware of. I see that the documentation references
Vagrant+VirtualBox as something that can be installed on any Linux OS,
by talking about deps and rpms. But, the rest of the documentation is
specific on RHEL 7 Server. I have a few open questions here -
** Why is there focus on RHEL 7 Server, when developers on Linux
are unlikely to use this for day-to-day development tasks? For someone
using Ubuntu or Fedora with Virtualbox, the Linux docs are only
partially useful, given they address libvirt on RHEL 7.
** Is there any open issue to ensure we address other prominent
Linux distros?
* OSE client (oc executable)
The documentation on obtaining the OpenShift client, is present in
an RST in CDK.zip, but not in the docs. I think this was discussed
previously in some other thread, but I thought I'd mention it again
incase it wasn't.
Suggestions follow:
* Publish the testing matrix prominently on what versions of
pre-requisites users need to get CDK up and running without issues. If
it's already written down somewhere, it needs to be prominent in the
installation pre-requisites section of the doc.
+1. As we already have the matrix we definitely should improve the
visibility.
* Have nightly builds against our OS targets and possibly multiple
versions of pre-requisites, so we know about issues involving
pre-requisites even before our users do.
We are aware of these issues with recent Vagrant versions. That's the
reason our support matrix does not list them. But as you suggested we
need to do a better job of communicating the information.
* Expand the documentation for Linux users, and bring in clarity on
multiple vagrant providers. If we are going to support only libvirt
usage for Linux users in our docs, we should declare this as a
pre-requisite.
We need to support both. But +1 for better documentation for this. I
think the action item for the team is to go through the documentation
and provide suggestion to documentation team.
Thanks for your time in reading this.
Regards
Vineet
[1]: https://github.com/mitchellh/vagrant/issues/7631
[2]: https://github.com/mitchellh/vagrant/issues/7493
[3]: https://github.com/mitchellh/vagrant/issues/7411
_______________________________________________
Devtools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/devtools
_______________________________________________
Devtools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/devtools
