Re: [Container-tools] profiles
Hi, > > > so our docs are horrible > > Are we talking about upstream minishift docs here? I don't believe "minishift > profile" is in the latest CDK. Yes, Minishift aka upstream. Profiles are not in the CDK yet. I created https://github.com/minishift/minishift/issues/1485 to improve the profile docs. I think the whole concept of profiles needs to be motivated more. There is definitely context missing, especially around the level of isolation between profiles. --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] profiles
On Tue, 03-Oct-2017 14:28, Burr Sutter wrote: > any thoughts how the workaround for addons + profiles? See the comments on the issue you created. You are using the commands wrong. You issue 'config set' and 'addon enable' commands against the currently active profile, but then you start a new profile. If you want to set the config and add-ons prior to starting the profile you need to do something like: $ minishift --profile bar addon enable anyuid resp $ minishift --profile test config set memory 6144 --Hardy ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
[Container-tools] Minishift 1.0.0
The Minishift team is happy to announce Minishift 1.0.0 [1]. Thank you, everyone, who made this release possible, either through coding, testing, documenting, reporting issues or requesting a new feature. We welcome all contributions. Minishift 1.0.0 is a big milestone for us, since it completes the switch to ‘oc cluster up’ [2] for OpenShift provisioning. However, that’s not all. Along the way we added a whole range of new features. The two biggest features are the new addons and hostfolder commands: * ‘minishift addons’ [3] introduces a framework for OpenShift customization using a Minishift specific DSL. * ‘minishift hostfolder’ [4] introduces a more explicit way of managing mounted host folders, in particular the ability to define multiple host folders which can be mounted on request. Another new command is ‘openshift’ which loosely groups some OpenShift related commands together: * ‘minishift openshift registry’ [5] exposes the host and port of the OpenShift registry * ‘minishift openshift patch’ [6] allows you to patch the OpenShift configuration and * ‘minishift openshift version’ prints the current OpenShift version. By default, it is OpenShift 1.5.0. And lastly, we added the ‘oc-env’ [7] command, which allows you to configure your shell to use the oc binary that is downloaded to your host during ‘minishift start’. In addition to the new commands, Minishift 1.0.0 includes other new features, such as HTTP(S) proxy support, persistent volume provisioning, and the creation of a minishift CLI profile [8] for easier usage of oc. To help you adopt all of these new Minishift features, we are planning to create a series of blog posts and video tutorials that showcase the full Minishift workflow. In the meantime, you can review the Minishift documentation [9]. There is still a lot of work to do and we have many great ideas for new features. Stay tuned and check out the Minishift Roadmap [10] if you want to know where we are heading next. Feel free to join us on #minishift on irc.freenode.net if you have questions or ideas. Last but not least, if you find a bug or have an idea for a new feature, please take the time to create an issue in the Minishift GitHub issue tracker [11]. We really do appreciate your feedback. Happy Minishifting! [1] https://github.com/minishift/minishift/releases/tag/v1.0.0 [2] https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md [3] https://docs.openshift.org/latest/minishift/using/addons.html [4] https://docs.openshift.org/latest/minishift/using/host-folders.html [5] https://docs.openshift.org/latest/minishift/using/accessing-the-openshift-docker-registry.html [6] https://docs.openshift.org/latest/minishift/using/interacting-with-openshift.html#update-openshift-config [7] https://docs.openshift.org/latest/minishift/using/interacting-with-openshift.html#openshift-client-binary [8] https://docs.openshift.org/latest/cli_reference/manage_cli_profiles.html [9] https://docs.openshift.org/latest/minishift/index.html [10] https://github.com/minishift/minishift/blob/master/ROADMAP.adoc [11] https://github.com/minishift/minishift/issues ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] CDK issue with different home_directory
Hi, > > I was not aware that you could specify a different directory. That must be > > a new feature of RC2? No, that has been there all the time. > This we did for our integration test purpose to run it in a CI env. This is not only for integration testing. It works actually quite well. So, per default Minishift installs and uses ~/.minishift. Using the --minishift-home forces the setup to install into the specified directory. This is, however, only one part of the equation. Once you have done this, you need to make sure that at runtime (when you are executing minishift commands), Minishift uses this custom home directory. You do this by exporting MINISHIFT_HOME. See also https://docs.openshift.org/latest/minishift/using/managing-minishift.html#environment-variables Bottom line, you can use Minishift community as well as the CDK with a home directory different to ~/.minishift. Regarding having multiple instances, that's possible with some caveats. I can explain more if you want to. --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] new minishift CDK
Hi, > > We had a situation where a route was misbehaving. My investigation > > strategy is to get inside the VM, oc get services and curl the IP address. We are providing oc on the host, so you can skip the step of logging into the VM. You can execute 'oc get service' on the host. Even better, we have a Minishift specific command (there is a bug we are fixing atm), so that you can do 'minishift openshift service list -n myproject' and you get a list of all routes. > > And I transfer in files that I need via > > vagrant rsync The aim is to do as much as possible on the host. Also, as we are getting closer to a consistent solution for host folders, there should be no need for rsyncing anything. > > Do we have an Asher for that? What's that? > With Minishift we have not taken that route as we want to keep the ISO as > much as light weighted. But I think we need to provide some sort of way for > advance users who want to play with the VM more. And what would you have in mind there? --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
[Container-tools] Minishift 1.0.0-beta.4 is out
Hi,
The train towards Minishift 1.0.0 is running full steam ahead. Today we are
happy to announce Minishift 1.0.0-beta.4 [1].
In total we have squashed 38 issues and you can view all the gory details on
the GitHub milestone for this release [2].
For now we would like to highlight two specific new features.
First, there is the new HTTP/HTTPS proxy support. If you are sitting behind a
proxy, configuring Docker and OpenShift to work with the proxy is now as easy
as:
$ minishift start --openshift-version=1.5.0-alpha.2 --http-proxy
http://YOURPROXY:PORT --https-proxy https://YOURPROXY:PORT
Note the specific OpenShift version. For proxy support to work you will need to
use a OpenShift version >=1.5.0-alpha.2 (Minishift’s default is still 1.4.1).
You can find more details around proxy support in the Minishift documentation
[3].
A second feature we would like to highlight, is the ability to patch the
OpenShift master or node configuration. Take Cross-origin resource sharing
(CORS) as an example.
Per default, OpenShift will only allow cross origin resource requests from the
IP of the cluster as well as localhost. You can change this now via the
‘openshift config set’ command. For the CORS case you could for example issue
the following command which will allow CORS from all domains:
$ minishift openshift config set --patch '{"corsAllowedOrigins": [".*"]}'
This functionality is based on OpenShift’s ‘openshift ex config patch’ command
and takes a JSON document targeting the configuration items to update.
More details again in the Minishift documentation [4].
We also released new versions of the Boot2Docker (v1.0.1) [5] and CentOS
(v1.0.0-rc.2)[6] based ISO images. In both cases we added cifs per default.
This allows you to mount Windows shares as host folders. At the moment this is
a manual process, but we are working on automating this [7].
Besides the release we are also excited to share some other news with you.
First, Minishift is now OpenShift’s preferred solution for creating a local
OpenShift single node cluster and the old Vagrant based all-in-one VM has been
deprecated [8].
Also note that the Minishift team has started to hang out on the #minishift
channel on irc.freenode.net. Here we discuss everything Minishift related. Come
and join!
Last but not least, keep the feedback coming. It is much appreciated. If you
want to report a bug or request a new feature, head over to the Minishift
GitHub issue tracker [9].
Enjoy!
[1] https://github.com/minishift/minishift/releases/tag/v1.0.0-beta.4
[2] https://github.com/minishift/minishift/milestone/9?closed=1
[3]
https://github.com/minishift/minishift/blob/master/docs/using.md#httphttps-proxies
[4]
https://github.com/minishift/minishift/blob/master/docs/using.md#updating-openshift-configuration
[5] https://github.com/minishift/minishift-b2d-iso/releases/tag/v1.0.1
[6] https://github.com/minishift/minishift-centos-iso/releases/tag/v1.0.0-rc.2
[7]
https://github.com/minishift/minishift/blob/master/docs/using.md#mounting-custom-shared-folders
[8] https://www.openshift.org/minishift/
[9] https://github.com/minishift/minishift/issues
___
Container-tools mailing list
Container-tools@redhat.com
https://www.redhat.com/mailman/listinfo/container-tools
[Container-tools] Minishift 1.0.0-beta.3
Hi, We are happy to announce the next Minishift release - Minishift 1.0.0-beta.3 [1]. The two main highlights of this version are, that we are now aligning with OpenShift Origin 1.4.1 [2] and that we overhauled the persistent configuration options [3]. We also made sure to finally document this [4]. The persistent configuration allows you to save the flags you most often use in a configuration file and get them applied transparently. For example, if you always want to use VirtualBox, you can run: $ minishift config set vm-driver virtualbox Now you can just run the start command without specifying the driver option: $ minishift start Starting local OpenShift cluster using 'virtualbox' hypervisor... We also did a general review of the documentation and error messages, aiming for a more consistent terminology describing the various aspects of Minishift. Hopefully this will provide a better user experience. In total we addressed 26 issues and a lot of bigger features (proxy support, ability to configure the OpenShift master configuration, etc) are mid-air. Expect the next release to be a big one :-) When it comes to the virtual machine ISOs, we released minishift-centos-iso 1.0.0-rc.1 [5]. Most noteable it has now SELinux enabled and contains an updated version of Docker (1.12). When using Minishift 1.0.0-beta.3, make sure to use the latest ISO release as well, since older versions won’t work anymore. Feedback is always welcome. If you want to report a bug or request a new feature, please use the Minishift GitHub issue tracker [6]. Enjoy! [1] https://github.com/minishift/minishift/releases/tag/v1.0.0-beta.3 [2] https://github.com/minishift/minishift/issues/328 [3] https://github.com/minishift/minishift/issues/278 [4] https://github.com/minishift/minishift/blob/master/docs/using.md#persistent-configuration [5] https://github.com/minishift/minishift-centos-iso/releases/tag/v1.0.0-rc.1 [6] https://github.com/minishift/minishift/issues signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
[Container-tools] Minishift 1.0.0-beta.2 release
Hi, We are happy to announce the second Minishift beta release - Minishift 1.0.0-beta.2 [1]. While the previous release focused on the initial switch to ‘oc cluster up’ for provisioning, we worked hard in this beta.2 release fixing some of the issues this switch introduced. Most importantly, we broke persistence of the OpenShift configuration. This meant each time you stopped and then re-started Minishift, OpenShift got re-provisioned. This issue [2] is now resolved. OpenShift configuration will persist until ‘minishift delete’ is called. On a side note, if you are using ‘minishift start’ with explicit flags for ‘--iso-url’ and ‘--vm-driver’, you will need to specify the same parameters on each re-start. If parameters don’t match, the virtual machine won’t start. This is a usability issue and we are discussing various solutions as part of issue #179 [3]. Feel free to weigh in, if you have a preference for any of the discussed solutions. In the meantime, you can set the environment variables MINISHIFT_ISO_URL and MINISHIFT_VM_DRIVER ensuring that the respective command line flags are set on each call to ‘minishift start’. You can read more about environment variables in the documentation [4]. Two other important issues #206 [5] and #221 [6] affected Windows users. In both cases the intended caching mechanism failed and is now fixed. Last but not least, we disabled any automatic updates of Minishift and its default ISO. Automatic updates have been broken by Minishift 1.0.0-beta.1 due to the fact that we are now releasing archive bundles instead of single binaries [7]. This resulted in the creation of issue #204 [8]. Since we in parallel got various bug reports indicating that the automatic update algorithm was causing issues hitting the GitHub API rate limit, we decided for now to completely disable any automatic updates [9] and rethink the current approach in an upcoming release. Please follow the manual installation instructions as provided by the documentation [10] in the meantime. If you are interested to use the CentOS based ISO, there is a new release as well - minishift-centos-iso 1.0.0-beta.1 [11]. You will need to use this ISO if you want to make sure your OpenShift configuration is persistent with the CentOS VM. Enjoy the new release and please keep the feedback flowing, Hardy [1] https://github.com/minishift/minishift/releases/tag/v1.0.0-beta.2 [2] https://github.com/minishift/minishift/issues/210 [3] https://github.com/minishift/minishift/issues/179 [4] https://github.com/minishift/minishift/blob/master/docs/using.md#environment-variables [5] https://github.com/minishift/minishift/issues/206 [6] https://github.com/minishift/minishift/issues/221 [7] https://github.com/minishift/minishift/issues/171 [8] https://github.com/minishift/minishift/issues/204 [9] https://github.com/minishift/minishift/issues/246 [10] https://github.com/minishift/minishift#installing-minishift [11] https://github.com/minishift/minishift-centos-iso/releases/tag/v1.0.0-beta.1 signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] Atomic Developer Bundle videos available in Youtube
Hi, I had a quick look at the videos and imo they are too long. I think the maximum is 10 minutes with a sweet spot around 5 to 7 minutes. Instead of a 30 minutes all in one, I'd suggest to do short dedicated vidoes - Start CDK - Configure TLD - Connect to Docker - Build application - etc This also helps people who are looking for specific information. If I am beginner and now some basics, but would like to know how to connect to the Docker service, I don't want to watch 30 minutes of video where 25 minutes are irrelevant to me. I think the videos on the OpenShift blog are usually also around the 5 to 10 minute mark. --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] [Devtools] openshift is way too permissive in the CDK/ADB
Hi, On Wed, 18-May-2016 07:10, Clayton Coleman wrote: > It was a deliberate choice, predicated on other changes coming to > Docker (user namespaces) plus the desire to ensure demos run. > > Ultimately, the CDK is a playground. Putting up chain link fences > around the playground sends the wrong message. > > I'd prefer to have it easier to go between the levels in the short > term than to ratchet it back. +1 to all the above. My understanding was anyways that in with the upcoming user namespaces things would change and the problem would "go away". Where do things stand regarding this feature? --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] Prepackaged OpenShift template with CDK
Hi, > > On Wed, 10-Feb-2016 13:33, Pete Muir wrote: > > > 1) eap64-mysql-persistent-s2i > > > > Did you mean to only include the EAP + MYSQL template. Right now, > > the plain EAP template (no database) is gone which seems wrong to me. Is > > it? > > > > I just saw eap64-basic-s2i in the installation I just ran Sure, that's because you most likely use the Beta5 release. I was talking about a build I received yesterday which contains the changes since Beta5. This release has the basic eap template removed. But fear not, it is bound to make a reappearance - https://github.com/projectatomic/adb-utils/pull/100 :-) --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] Prepackaged OpenShift template with CDK
Hi, Sorry to come back to this so late, but I tested the latest CDK build and noticed several changes to the available templates, so I wanted to bring this up again. On Wed, 10-Feb-2016 13:33, Pete Muir wrote: > 1) eap64-mysql-persistent-s2i Did you mean to only include the EAP + MYSQL template. Right now, the plain EAP template (no database) is gone which seems wrong to me. Is it? Also is it really eap64-mysql-persistent-s2i (which is available now) or should it be eap64-mysql-ephermeral-s2i. The reason I am asking is, that the persistent template makes a persistent volume claim and we have not even setup any (there is an outstanding pull request to do so). I have not tried to use this template yet, but I am wondering whether it works. AFAIK no one has tested it. > 2) jws30-tomcat7-mysql-persistent-s2i > 3) nodejs-mongodb-example > 4) cakephp-mysql-example Another thing is that we still have builders for Python, Ruby and Perl showing up. Maybe not such a bad thing, but it was not in the list we initially defined. The reason for this is that we import the RHEL 7 image stream un-modified. I think we really need to take control over this and hand-roll our own streams and templates. That said, I am not sure whether there is still time to do much about the imported resources. Maybe we just need to fly with what we have, even though imo it is a bit confusing to the users. At least the EAP issue should be investigated though. --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] New and improved vagrant-sshfs
Hi, > So I've been told that asking users to forward an ssh-agent or provide > a password to get synced folders working isn't good enough :( > > Fair enough. I've done some research and found out how we can achieve > the mount without any of that (see [1]). Nice > I have some code ready and I'm hoping to cast a wide net to get kinks > worked out before I release. Can I please get everyone to try it out: I'll check it out asap > First uninstall the existing vagrant-sshfs plugin that you may have > installed: > > ``` > $ vagrant plugin uninstall vagrant-sshfs > Uninstalling the 'vagrant-sshfs' plugin... > ``` > > Then install a custom build that I have done: > > ``` > $ vagrant plugin install vagrant-sshfs --plugin-source > https://dustymabe.fedorapeople.org/gemrepo/ > ``` > > And test it out by adding a line to your Vagrantfile: > > ``` > config.vm.synced_folder "/path/on/host", "/path/on/guest", type: "sshfs" > ``` What's are the prerequisites on Windows? --Hardy signature.asc Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] sshfs progress - try it out
Hi, Here is an update from my attempts to get the sshfs to work on Windows. > I am curious how this would work on Windows. Not quite sure how to start sshd > yet. > We are trying to avoid cygwin in favour of mingw. Not sure whether it > includes a sshd. > I try to do some research. If anyone knows, let me know :-) Installing the plugin worked fine. I decided for the ssh PowerShell port as a solution for the sshd on Windows - https://github.com/PowerShell/Win32-OpenSSH I followed the instructions to install the sshd and got it started. The I added the synced folder in the Vagrantfile and did a 'vagrant up'. I provided the password when asked for it and then got that: ==> default: Installing SSHFS client... ==> default: Detected host IP address is '10.0.2.2' default: SSHFS password for 'IEUser': ==> default: Mounting SSHFS shared folders... ==> default: Mounting folder via SSHFS: C:/Users/IEUser/tmp => /mount/windows Mounting SSHFS shared folders failed. This is most often caused by either an SSH Daemon not running on the host or invalid credentials being provided. Please make sure an SSH daemon is running on the host and proper credentials were provided to be able to authenticate via SSH. The command and output are: echo 'Passw0rd!' | sshfs -p 22 -o StrictHostKeyChecking=no -o allow_other -o noauto_cache -o password_stdin IEUser@10.0.2.2:'C:/Users/IEUser/tmp' /mount/windows Stdout from the command: Stderr from the command: read: Connection reset by peer When I vagrant ssh into the VM and execute a 'ssh IEUser@10.0.2.2' it works fine. But the above sshfs command fails with "Connection reset by peer". No idea how to get more information than that for now. AFAIU the PowerShell ssh port is work in progress. I am wondering whether sshfs uses some options which are not available yet. If that is the case the question is how to get sshd to run. There is the cygwin approach, but as mentioned we are trying to ditch cygwin. Thoughts? --Hardy pgpPqnKzEk90I.pgp Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
Re: [Container-tools] sshfs progress - try it out
Hi, > I guess Lala is referring to this: > https://www.redhat.com/archives/container-tools/2016-February/msg00172.html Ahh, thanks. I missed that. --Hardy pgpj_Jueze2sM.pgp Description: PGP signature ___ Container-tools mailing list Container-tools@redhat.com https://www.redhat.com/mailman/listinfo/container-tools
