August 2017 - Minishift Mailing List - Minishift List Archives

by Hardy Ferentschik

Hi, I wanted to circle back to the roll-out of the profile feature. I think we agreed that from a user point of view there should always be a profile. So even if none is explicitly set or specified, a `minishift profile list` would report that the 'default' profile is in use (or 'minishift' tbd). Also from an implementation point of view there should always be a profile. The profile is discovered and set in root.go at the beginning of the bootstrap. This avoids having code branches based on profile existence at any other place than root.go. The interesting question is, how profiles and in particular the default profile reflect on the file system. There are two main approaches. The first one is the one which is also taken by Minikube. The default profile uses the existing structure (no profile sub-directory). The benefit would be that if one does not use profiles nothing is going to change on a file system level. Everything will look the same. The other benefit is, that it is truly backwards compatible and an existing VM and configuration is continue to work. In this cases one would need to do a translation in root.go where the default profile would map to "just" MINISHIFT_HOME. The downside is that once one uses profiles the structure is not completely consistent. The default profile is not just another directory in the profiles directory. The alternative is to make profiles consistent and also move the default profile into the profiles sub-directory. This means existing Minsihfit setups will break. In our discussion we said that we in this case can add something in root.go which allows the user to migrate at least config and cache into the new default location. An existing VM would need to be delete, since files cannot just be moved. Note, that we give the user not much of a choice. If the user wanted to keep the existing VM, he would have to download an earlier version of Minishift. Thinking about semantic versioning, one could almost argue that rolling out profiles would harbor a 2.0.0 release. As much as I like consistency, I have to admit that the first option is growing on me. It allows us to roll out profiles without having to add code for migration. If we really wanted, we could then clean up the structure further down the track when we potentially have some other changes which are not backwards compatible. Thoughts? --Hardy

5 years, 8 months

4
13
0 / 0

Minishift-1.5.0 release announcement

by Budh Ram Gurung

Hi All, The Minishift team is pleased to announce the release of Minishift 1.5.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: * Multi-line description in add-on file You can now write a multi-line description of the add-on which describes well about the add-on. * --memory flag accepts values in GB/MB Now, --memory flag during start command accepts human readable values for memory like 5 GB, 2048 MB etc. 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 [4] 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.5.0 [3] https://docs.openshift.org/latest/minishift [4] https://lists.minishift.io/admin/lists/minishift.lists.minishift.io Regards, Budh Ram Gurung Software Engineer - Devtools

5 years, 9 months

1
0
0 / 0

Support for NAT and npipe on Windows

by lucastheisen＠pastdev.com

Hi All, I have really wanted to get started using minishift for my teams development efforts, but there are currently 2 major issues preventing it. My development staff mostly uses Windows laptops, and Docker for Windows has already solved both of them. The first, and most important is the networking issue. Without NAT support (https://github.com/minishift/minishift/issues/418), we would have to stop/reconfigure/start every time we switch from wired ethernet to wireless due to corporate restriction that the laptop is only on one network at a time. Further, when working remote we are behind a VPN as our external network and I cannot figure out how to setup a VMSwitch that goes through the VPN. NAT support would resolve this. The second has to do with our corporate VPN. Due to security requirements, the laptop itself is not allowed to be dual-homed, so the VPN actively prevents this by stealing ALL of the routes. This includes all of the reserved IP's (10.x, 192.168.x, ...) that are used to communicate with the hyper-v image that runs minishift. I am not sure of the inner details, but Docker for Windows uses npipe for the docker command which allows us a way around this problem. And since docker then exports the ports back to localhost, we can access all of the running containers using loopback ips. Without this feature, none of my staff can work with minishift while on the VPN. As mentioned above, Docker for Windows provides NAT, and npipe, so we can and are using it for our current effort to containerize our entire infrastructure. However, our final deployment is to OpenShift. This means we typically develop using Docker infra (Dockerfile, docker-compose, ...) but then have to also provide OpenShift infra (s2i, Kompose, ...). It would be really nice to remove the Docker part altogether. Anyway, thanks for doing all of this, and thank you for considering this request. Lucas Theisen

5 years, 9 months

3
3
1 / 0

Necromancer

by Hardy Ferentschik

Hi, seems we forgot to decide who is doing it this week. Given that I forgot to follow up and the fact that I am waiting for feedback from containers/image I will take the role. Moving forward, shall we decide whose turn it is over the next few weeks. At least until we had a full rotation. Amit and Andreas, do you want to be part of the rotation? Shall I integrate this into Minibot? We basically use hubot-auth (that's what drives who is part of the standup) to define a 'neromancer' role. After standup we "shout out" the current necormancer and every Monday the next person with the role becomes the active necromancer. --Hardy

5 years, 9 months

4
3
0 / 0

Cool stuff

by Hardy Ferentschik

Hi, this one is hot - http://www.telepresence.io For developing micro-services this is the way to go. Deploy the dependency services in Kubernetes/OpenShift, while the micro service you are working on is developed and run locally. --Hardy

5 years, 9 months

1
0
0 / 0

oc cluster version X not able to provision version X-1

by Hardy Ferentschik

Hi, there is a very important issue raised in the origin repo - https://github.com/openshift/origin/issues/15731 The ability of cluster up to provision earlier versions of OpenShift is causing issues (surprise surprise). There is a request to remove this feature. Originally we also aligned oc version when provisioning earlier OpenShift versions as the current baseline. However, due to issues we encountered we went over to an approach where earlier versions of the baseline are provisioned with the baseline version of oc. I cannot remember which exact issues we were facing. Maybe someone can refresh my memory. How do we stand towards this issue? How important is this feature to us? --Hardy

5 years, 9 months

3
4
0 / 0

Re: [Container-tools] [container-tools] Minishift-1.4.1 release announcement

by Gerard Braad

Hi, On Thu, Aug 10, 2017 at 6:11 PM, Max Rydahl Andersen <manderse(a)redhat.com> wrote: > minishift update > Error: unknown command "update" for "minishift" > Run 'minishift --help' for usage. > F0810 12:10:20.646212 17352 root.go:95] unknown command "update" for > "minishift" > > dammit - I'm behind! :) Quite far behind, this means you are several releases behind (pre 1.3.0 for sure). The update should look like this: $ minishift update Nothing to update. Already using the latest version: 1.4.1. Do a manual update once, and then in the future we will take care of it. regards, Gerard

5 years, 10 months

1
0
0 / 0

Re: [Container-tools] [container-tools] Minishift-1.4.1 release announcement

by Budh Ram Gurung

On Thu, Aug 10, 2017 at 3:41 PM, Max Rydahl Andersen <manderse(a)redhat.com> wrote: > On 10 Aug 2017, at 11:49, Gerard Braad wrote: > > Hi Max, > > On Thu, Aug 10, 2017 at 5:31 PM, Budh Ram Gurung bgurung(a)redhat.com wrote: > > On Thu, Aug 10, 2017 at 2:31 PM, Max Rydahl Andersen manderse(a)redhat.com > > One thing I noticed - shouldn't minishift delete ask for confirmation ? > > You are absolutely correct here and we agree and hence we have issue [1] to > handle it. It will come with --force > flag to skip confirmation. > > Right. This is an issue I personally filed somewhere in February. And > we have marked it as an 'easyfix', which means that the community can > have a go at it, as an intro or low hanging fruit. But this kind of > excludes us from working on it... until someone deems this very high > priority. Although I lost a test setup with this command, the > frustration hasn't been high enough to escalate and work on it. ;-) > > We will be posting more recordings, and maybe even short videos about > the usage of Minishift. If you have a suggestion what you would like > to see being covered, just let us know. > > will do. > > Again, great stuff - I need to update and retry minishift now :) > > Do not forget, updating is easy now: > > $ minishift update > > minishift update > Error: unknown command "update" for "minishift" > Run 'minishift --help' for usage. > F0810 12:10:20.646212 17352 root.go:95] unknown command "update" for "minishift" > > dammit - I'm behind! :) > Yes :), 'update' command added from v1.1.0 onwards which released on June 6. > /max > http://about.me/maxandersen > Regards, Budh Ram Gurung Software Engineer - Devtools

5 years, 10 months

1
0
0 / 0

Re: [Container-tools] [container-tools] Minishift-1.4.1 release announcement

by Budh Ram Gurung

Hi Max, On Thu, Aug 10, 2017 at 2:31 PM, Max Rydahl Andersen <manderse(a)redhat.com> wrote: > On 8 Aug 2017, at 15:52, Gerard Braad wrote: > > Hi All, > > > On Tue, Aug 8, 2017 at 8:44 PM, Budh Ram Gurung <bgurung(a)redhat.com> > wrote: > > Release Highlights > - Improvements to user feedback during Minishift startup > - Introduction of the environment variable MINISHIFT_ENABLE_EXPERIMENTAL > to pass extra flags to “oc cluster up” > > I made a small asciinema recording[0] that shows what these features do. > Feedback welcome... > > regards, > > > Gerard > > [0] := https://asciinema.org/a/132591 > > Gerard, that is very nice and informative! > > One thing I noticed - shouldn't minishift delete ask for confirmation ? > You are absolutely correct here and we agree and hence we have issue [1] to handle it. It will come with --force flag to skip confirmation. > And what does the the y do in MINISHIFT_ENABLE_EXPERIMENTAL=y minishift > start --service-catalog ? > Here, 'y' indicate 'yes' in shorter form. You can use : - y or yes - on - true - 1 See more details in the implemented PR here [2]. > Again, great stuff - I need to update and retry minishift now :) > Cool. Looking forward to your feedback :). > /max > http://about.me/maxandersen > [1] https://github.com/minishift/minishift/issues/405 [2] https://github.com/minishift/minishift/pull/1185#issue-245891986 > _______________________________________________ > Container-tools mailing list > Container-tools(a)redhat.com > https://www.redhat.com/mailman/listinfo/container-tools > > Regards, Budh Ram Gurung Software Engineer - Devtools

5 years, 10 months

2
1
0 / 0

Fwd: Minishift on JBoss asylum

by Lalatendu Mohanty

FYI. ---------- Forwarded message ---------- From: Max Andersen Date: Wed, Aug 9, 2017 at 11:05 PM Subject: Minishift on JBoss asylum Hey, I just realized I missed sharing this minishift asylum podcast made a late night before my pto. http://in.relation.to/2017/07/26/minishift/ Feel free to share :) /max http://about.me/maxandersen

5 years, 10 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

Minishift Mailing List August 2017