[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
[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
