Minishift-1.8.0 release announcement
by Lalatendu Mohanty
Hi All,
The Minishift team is pleased to announce the release of
Minishift 1.8.0.
Minishift [1] is a command-line tool that provisions and manages a
single-node OpenShift cluster. You can run Minishift on GNU/Linux,
Microsoft Windows or macOS.
Release highlights
---------------------------
This release adds new features, enhancements, and bug fixes, including:
- Add a minimum OpenShift version for executing add-ons.
As part of the add-on metadata you can now specify the OpenShift version
which needs to be running in order to apply the add-on. For more
information refer [5].
- A non existent profile can be set as the active profile.
This allows the user to run “profile set” command for the profile the user
wants to create and set persistent configurations against.
For example you can run below commands to create a profile “foo” with 8GB
RAM:
$ minishift profile set foo
$ minishift config set memory 8GB
$ minishift start
This release also includes many changes and bug fixes, which are
detailed in the release notes [2]. For information about getting
started, using, and developing Minishift, see the documentation [3].
Please try the new release. The easiest upgrade path is by simply
running:
$ minishift update
We are looking forward to your feedback.
The Minishift community hangs out at #minishift channel on Freenode
and it is the perfect place to discuss anything Minishift-related.
You can sign up for our mailing list [6] to receive development updates,
questions about Minishift, suggest ideas and talk to the community.
[1] https://github.com/minishift/minishift
[2] <https://github.com/minishift/minishift/releases/tag/v1.7.0>
https://github.com/minishift/minishift/releases/tag/v1.8.0
[3] https://docs.openshift.org/latest/minishift
[4] https://lists.minishift.io/admin/lists/minishift.lists.minishift.io
[5]
https://docs.openshift.org/latest/minishift/using/addons.html#addon-opens...
5 years, 7 months
Probot integrations
by Hardy
Hi there,
just a heads up that I over the last days enabled a couple of GitHub Probot integrations [1]. If you want to know more about this new GitHub API/project, I recommend this podcast [2].
For now WIP and Stale probots are enabled. The former is pretty simple. If just prevents a pull request to be merged (my marking it as failed) while the title contains a [WIP]. Pretty much what we already do, just helping us here to oversee a potential ‘WIP’.
The latter looks for stale issues and marks them to be closed. It does that by adding the status/stale label. After this label is added by the bot, there is a waiting period. If there is no activity during this waiting period, the issue gets closed. Any change to the issue and the bot will remove the label.
Currently the bot marks issues which have been untouched for 2 months as stale and has a waiting period of two weeks. See also stale.yml [3].
Last but not least, one can also add the ‘status/pinned’ label. In this case the bot won’t mark the issue as stale, even if it has been untouched for more than two months.
Happy hacking,
Hardy
[1] https://probot.github.io/
[2] https://changelog.com/podcast/264
[3] https://github.com/minishift/minishift/blob/master/.github/stale.yml
5 years, 7 months
CentOS CI has 8 executors now means 8 parallel jobs
by Budh Ram Gurung
Hi All,
I am very glad to inform that we got 8 executors for CentOS CI which is
doubled than our previous 4 executors.
We definitely can think of having the parallelism of jobs for running our
time-consuming integration tests (30mins+).
Let's discuss the strategy in the issue https://github.com/
minishift/minishift/issues/1396.
Regards,
Budh Ram Gurung
Software Engineer - Devtools
5 years, 7 months
B2D ISO becoming obsolete
by Hardy Ferentschik
Hi,
I wanted to start a discussion on who we want to proceed with the various ISOs we support.
So far the B2D ISO is our default and we always took great care that all features we implement
work on all ISOs.
As of recently we have not features though (the experimental Hyper-V feature to set a fixed IP)
which won't work anymore on the B2D ISO. Unfortunately, the whole B2D project seems to be abandoned
by Docker, so chances are slim to get this fixed.
At the same time we have a new player on the field, the Minikube ISO. It supports all features
(including the Hyper-V one) and is still relatively small, so that it eventually could become our default ISO.
I guess we still need to gain some experience with this ISO and we need to also need to double
check whether it already contains all the hostfolder utilities (sshfs, cifs) we need, but after that
we might want to ask ourselves whether we should not make the Minikub ISO the default.
What are your thoughts around this? Other related questions:
* How long do we wait until we make the switch?
* Should be just make the Minikube ISO the default and keep the B2D as an option?
* If we don't want to keep the B2D ISO, how long do we wait until we remove it from the list of explicitly listed ISOs
* Should we stop working on the B2D ISO repo altogether?
Let's try to come up with a plan on how we want to move this forward.
--Hardy
5 years, 7 months
Minishift-1.7.0 release announcement
by Budh Ram Gurung
Hi All,
The Minishift team is pleased to announce the release of
Minishift 1.7.0.
Minishift [1] is a command-line tool that provisions and manages a
single-node OpenShift cluster. You can run Minishift on GNU/Linux,
Microsoft Windows or macOS.
Release highlights
---------------------------
This release adds several new features, enhancements, and bug fixes,
including:
- Add support for Minikube ISO (Experimental)
You can now start Minishift VM with ISO provided by Minikube Project.
The ISO contains alternate container runtime e.g. cri-o, rkt along
with docker. Check here [2] for more details. You can start using the
ISO using below command.
$ MINISHIFT_ENABLE_EXPERIMENTAL=y minishift start --iso-url minikube
- Assign Static IP address to Minishift VM on Hyper-V (Experimental)
This experimental feature is for Hyper-V driver only. With this
feature enabled, one can able to assign static IP address for VM.
See here [3] for more details.
- Extend status command to provide details about the VM
Now, 'minishift status' will show the other details about VM like
OpenShift version, Disk usage and active profile information other
than VM status.
This release also includes many changes and bug fixes, which are
detailed in the release notes [4]. For information about getting
started, using, and developing Minishift, see the documentation [5].
Please try the new release. The easiest upgrade path is by simply
running:
$ minishift update
We are looking forward to your feedback.
The Minishift community hangs out at #minishift channel on Freenode
and it is the perfect place to discuss anything Minishift-related.
You can sign up for our mailing list [6] to receive development updates,
questions about Minishift, suggest ideas and talk to the community.
[1] https://github.com/minishift/minishift
[2]
https://docs.openshift.org/latest/minishift/using/managing-minishift.html...
[3] https://github.com/minishift/minishift/pull/1391
[4] https://github.com/minishift/minishift/releases/tag/v1.7.0
[5] https://docs.openshift.org/latest/minishift
[6] https://lists.minishift.io/admin/lists/minishift.lists.minishift.io
Regards,
Budh Ram Gurung
Software Engineer - Devtools
5 years, 7 months
A separate lebel for profile feature
by Lalatendu Mohanty
Hi,
I am planning to create a separate label for profile component in
Minishift repository as we are started getting feature requests around
profiles. I am positive that there would be more feedback and feature
request around this as more and more users use this.
Let me know if you disagree on this.
-Lala
5 years, 8 months
Re: A separate label for profile feature
by Lalatendu Mohanty
Re-sending after fixing a typo in the subject.
On Fri, Oct 6, 2017 at 2:07 AM, Lalatendu Mohanty <lmohanty(a)redhat.com>
wrote:
> Hi,
>
> I am planning to create a separate label for profile component in
> Minishift repository as we are started getting feature requests around
> profiles. I am positive that there would be more feedback and feature
> request around this as more and more users use this.
>
> Let me know if you disagree on this.
>
> -Lala
>
5 years, 8 months