From bsutter at redhat.com Sat Apr 1 15:42:18 2017 From: bsutter at redhat.com (Burr Sutter) Date: Sat, 1 Apr 2017 11:42:18 -0400 Subject: [Devtools] JBDS & Mobile/Cordova Message-ID: This video is one of my most popular but it has been so long since I used the Cordova tooling inside of JBDS that I can't remember the answer to a simple question...is the iOS sim available on Windows? https://www.youtube.com/watch?v=H5ry5WpziVw&feature=gp-n-y&google_comment_id=z125xb04pw2vdtnod04cdvroiuqitpx4m34 If you have an answer, please respond to the comments :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From gercan at redhat.com Sun Apr 2 03:38:48 2017 From: gercan at redhat.com (Gorkem Ercan) Date: Sat, 01 Apr 2017 23:38:48 -0400 Subject: [Devtools] JBDS & Mobile/Cordova In-Reply-To: References: Message-ID: <20FE0DFC-326E-41E2-8C08-9B4A27C897B7@redhat.com> iOS simulator is not available but CordovaSim can be used instead. Also replied to the comments. -- Gorkem On 1 Apr 2017, at 11:42, Burr Sutter wrote: > This video is one of my most popular but it has been so long since I > used > the Cordova tooling inside of JBDS that I can't remember the answer to > a > simple question...is the iOS sim available on Windows? > > https://www.youtube.com/watch?v=H5ry5WpziVw&feature=gp-n-y&google_comment_id=z125xb04pw2vdtnod04cdvroiuqitpx4m34 > > If you have an answer, please respond to the comments :-) > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Sun Apr 2 13:23:50 2017 From: bsutter at redhat.com (Burr Sutter) Date: Sun, 2 Apr 2017 09:23:50 -0400 Subject: [Devtools] JBDS & Mobile/Cordova In-Reply-To: <20FE0DFC-326E-41E2-8C08-9B4A27C897B7@redhat.com> References: <20FE0DFC-326E-41E2-8C08-9B4A27C897B7@redhat.com> Message-ID: Thank you! On Sat, Apr 1, 2017 at 11:38 PM, Gorkem Ercan wrote: > > iOS simulator is not available but CordovaSim can be used instead. > Also replied to the comments. > > -- > Gorkem > > On 1 Apr 2017, at 11:42, Burr Sutter wrote: > > This video is one of my most popular but it has been so long since I used > the Cordova tooling inside of JBDS that I can't remember the answer to a > simple question...is the iOS sim available on Windows? > > https://www.youtube.com/watch?v=H5ry5WpziVw&feature=gp-n-y& > google_comment_id=z125xb04pw2vdtnod04cdvroiuqitpx4m34 > > If you have an answer, please respond to the comments :-) > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hferents at redhat.com Mon Apr 3 20:22:25 2017 From: hferents at redhat.com (Hardy Ferentschik) Date: Mon, 3 Apr 2017 22:22:25 +0200 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: <20170403202225.GB26222@ovpn-116-136.ams2.redhat.com> Hi, > Still eats all the CPU :-) :-( Just to make sure we are on the same line. What exactly are you trying to deploy. The MSA demo? If so, what are your settings for cpus and memory? I'd like to do a couple of experiments myself and want to make sure that we are talking about the same thing. > And this is with VirtualBox...so at this moment, Beta3 is not really usable. I take it you use the CDK Minishift version. Could you try the latest community version https://github.com/minishift/minishift/releases/tag/v1.0.0-rc.1 and see whether it has the same problem. Make sure to run 'minishift delete' and run 'minishift config view' to make sure you are not defining a custom setting for iso-url. If so unset it. I am interested in whether you see the same problem using the default Boot2Docker ISO. The latest Minihift community release is also interesting for you for other reasons. It has not an addon mechanism which solves some of the other issues, for example developer with cluter-admin role, we have been discussing recently. --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From bsutter at redhat.com Mon Apr 3 21:56:13 2017 From: bsutter at redhat.com (Burr Sutter) Date: Mon, 3 Apr 2017 17:56:13 -0400 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: <20170403202225.GB26222@ovpn-116-136.ams2.redhat.com> References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> <20170403202225.GB26222@ovpn-116-136.ams2.redhat.com> Message-ID: On Mon, Apr 3, 2017 at 4:22 PM, Hardy Ferentschik wrote: > Hi, > > > Still eats all the CPU :-) > > :-( Just to make sure we are on the same line. What exactly are you trying > to > deploy. The MSA demo? If so, what are your settings for cpus and memory? > 2 cpus 6000 memory It seems to be the MSA demo that is causing it to go nuts https://docs.google.com/document/d/12NDWT_k6vgePaoD6gpihAqtpdQcyNXAKLVDtdS4eEXU/edit > I'd like to do a couple of experiments myself and want to make sure that > we are talking about the same thing. > > > And this is with VirtualBox...so at this moment, Beta3 is not really > usable. > > I take it you use the CDK Minishift version. Could you try the latest > community > version https://github.com/minishift/minishift/releases/tag/v1.0.0-rc.1 > and see > whether it has the same problem. Make sure to run 'minishift delete' and > run > 'minishift config view' to make sure you are not defining a custom setting > for > iso-url. If so unset it. I am interested in whether you see the same > problem > using the default Boot2Docker ISO. > I will give it a try. > > The latest Minihift community release is also interesting for you for other > reasons. It has not an addon mechanism which solves some of the other > issues, > for example developer with cluter-admin role, we have been discussing > recently. > > --Hardy > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmohanty at redhat.com Tue Apr 4 04:57:03 2017 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 4 Apr 2017 10:27:03 +0530 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> <20170403202225.GB26222@ovpn-116-136.ams2.redhat.com> Message-ID: On Tue, Apr 4, 2017 at 3:26 AM, Burr Sutter wrote: > > > On Mon, Apr 3, 2017 at 4:22 PM, Hardy Ferentschik > wrote: > >> Hi, >> >> > Still eats all the CPU :-) >> >> :-( Just to make sure we are on the same line. What exactly are you >> trying to >> deploy. The MSA demo? If so, what are your settings for cpus and memory? >> > > 2 cpus > 6000 memory > > It seems to be the MSA demo that is causing it to go nuts > > https://docs.google.com/document/d/12NDWT_k6vgePaoD6gpihAqtpdQcyNXAKLVDt > dS4eEXU/edit > > > Basically if you are able to run the demo in CDK 2.4 or CDK 2.3 with same resources and but seeing the issue with CDK 3.0 (performance issue) then it is a regression for CDK 3.0 and is of high priority. We need to find out if it is blocker or not. Thanks, Lala > >> I'd like to do a couple of experiments myself and want to make sure that >> we are talking about the same thing. >> >> > And this is with VirtualBox...so at this moment, Beta3 is not really >> usable. >> >> I take it you use the CDK Minishift version. Could you try the latest >> community >> version https://github.com/minishift/minishift/releases/tag/v1.0.0-rc.1 >> and see >> whether it has the same problem. Make sure to run 'minishift delete' and >> run >> 'minishift config view' to make sure you are not defining a custom >> setting for >> iso-url. If so unset it. I am interested in whether you see the same >> problem >> using the default Boot2Docker ISO. >> > > I will give it a try. > > >> >> The latest Minihift community release is also interesting for you for >> other >> reasons. It has not an addon mechanism which solves some of the other >> issues, >> for example developer with cluter-admin role, we have been discussing >> recently. >> >> --Hardy >> >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Tue Apr 4 12:34:29 2017 From: bsutter at redhat.com (Burr Sutter) Date: Tue, 4 Apr 2017 08:34:29 -0400 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: Adding devtools back to the thread. On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad wrote: > On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter wrote: > > Still eats all the CPU :-) > > du is the culprit according to top > > @lalatenduM @praveenkumar when do we issue a `du` command? I do not > remember this being part of the provisioner flow... > > @burr when did you notice `du` was the culprit of consuming the CPU as > a resource? during the `oc cluster up`, or after? > I tested with the upstream version overnight and Helloworld MSA, no problems Minishift version: 1.0.0-rc.1 it had no problems. Retesting with Minishift version: 1.0.0-beta.5 CDK Version: 3.0.0-beta.3 > > you could start `minishift start` and when the actually `provisoning > oc cluster` is shown, you could already issue `minishift ssh` from > another terminal and use `top` to investigate when this happens. > > > Gerard > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgurung at redhat.com Tue Apr 4 12:38:34 2017 From: bgurung at redhat.com (Budh Gurung) Date: Tue, 4 Apr 2017 18:08:34 +0530 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: On Tue, Apr 4, 2017 at 6:04 PM, Burr Sutter wrote: > Adding devtools back to the thread. > > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad wrote: > >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter wrote: >> > Still eats all the CPU :-) >> > du is the culprit according to top >> >> @lalatenduM @praveenkumar when do we issue a `du` command? I do not >> remember this being part of the provisioner flow... >> >> @burr when did you notice `du` was the culprit of consuming the CPU as >> a resource? during the `oc cluster up`, or after? >> > > I tested with the upstream version overnight and Helloworld MSA, no > problems > Minishift version: 1.0.0-rc.1 > it had no problems. > Good to know that. Thanks for update. > > Retesting with > > Minishift version: 1.0.0-beta.5 > CDK Version: 3.0.0-beta.3 > > Eagarly waiting for feedback. Well this should not have problem too but we will have next version beta.4 somwhere next monday if you are looking for latest feature like "addons". > > >> >> you could start `minishift start` and when the actually `provisoning >> oc cluster` is shown, you could already issue `minishift ssh` from >> another terminal and use `top` to investigate when this happens. >> >> >> Gerard >> > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > Regards, Budh Ram Gurung Software Engineer - Devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From gbraad at redhat.com Tue Apr 4 14:37:13 2017 From: gbraad at redhat.com (Gerard Braad) Date: Tue, 4 Apr 2017 22:37:13 +0800 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: Hi Burr, On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: > Adding devtools back to the thread. > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad wrote: >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter wrote: >> > Still eats all the CPU :-) >> > du is the culprit according to top >> @burr when did you notice `du` was the culprit of consuming the CPU as >> a resource? during the `oc cluster up`, or after? > I tested with the upstream version overnight and Helloworld MSA, no problems > Minishift version: 1.0.0-rc.1 > it had no problems. great to hear... mostly, Minishift tries to stay out of the way of the actual OpenShift deployment. In that sense, we prepare the environment and allow configuration, and dealing with OpenShift when the deployment happened. From this perspective, I am interested in how 'it seems to use more memory/cpu'. Minishift itself should not cause this directly. But of course, our foundation (the Operating System/ISO) could be a problem. So, if you have any quantifiable metrics, please ;-). It might be helpful to also test different OpenShift versions with a release of the Minishift (CDK) binary+ISOs. Sorry, to make you have to consider a lot of testing... but this information can be valuable to track down the actual root cause. And yes, we have several in recent time which should improve the quality and performance of deploying using Minishift. Looking forward to more feedback... Gerard From bsutter at redhat.com Wed Apr 5 03:42:07 2017 From: bsutter at redhat.com (Burr Sutter) Date: Tue, 4 Apr 2017 23:42:07 -0400 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: After lots of testing on the CDK variant, is no longer demonstrating the crazy du processes eating all the CPU. I see one or two du processes spike up but not to the point where it is overly problematic. I did have to turn on metrics (which doesn't work anyway) to see the du process via top. Minishift version: 1.0.0-beta.5 CDK Version: 3.0.0-beta.3 On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad wrote: > Hi Burr, > > On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: > > Adding devtools back to the thread. > > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad wrote: > >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter > wrote: > >> > Still eats all the CPU :-) > >> > du is the culprit according to top > >> @burr when did you notice `du` was the culprit of consuming the CPU as > >> a resource? during the `oc cluster up`, or after? > > I tested with the upstream version overnight and Helloworld MSA, no > problems > > Minishift version: 1.0.0-rc.1 > > it had no problems. > > great to hear... mostly, Minishift tries to stay out of the way of the > actual OpenShift deployment. In that sense, we prepare the environment > and allow configuration, and dealing with OpenShift when the > deployment happened. From this perspective, I am interested in how 'it > seems to use more memory/cpu'. Minishift itself should not cause this > directly. But of course, our foundation (the Operating System/ISO) > could be a problem. So, if you have any quantifiable metrics, please > ;-). It might be helpful to also test different OpenShift versions > with a release of the Minishift (CDK) binary+ISOs. > > Sorry, to make you have to consider a lot of testing... but this > information can be valuable to track down the actual root cause. And > yes, we have several in recent time which should improve the quality > and performance of deploying using Minishift. > > Looking forward to more feedback... > > > Gerard > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdyson at redhat.com Wed Apr 5 07:27:20 2017 From: jdyson at redhat.com (Jimmi Dyson) Date: Wed, 5 Apr 2017 08:27:20 +0100 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: What is du used for? iirc it's used by cadvisor (embedded in openshift) to track container disk usage but i thought with devicemapper docker storage, which i thought should be used in centos/rhel hosts, then it uses dm tools to track writable layer usage? Maybe there's another use of du I'm not aware of somewhere? On 5 Apr 2017 04:42, "Burr Sutter" wrote: > After lots of testing on the CDK variant, is no longer demonstrating the > crazy du processes eating all the CPU. I see one or two du processes spike > up but not to the point where it is overly problematic. I did have to turn > on metrics (which doesn't work anyway) to see the du process via top. > > Minishift version: 1.0.0-beta.5 > > CDK Version: 3.0.0-beta.3 > > > > > On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad wrote: > >> Hi Burr, >> >> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: >> > Adding devtools back to the thread. >> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad wrote: >> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >> wrote: >> >> > Still eats all the CPU :-) >> >> > du is the culprit according to top >> >> @burr when did you notice `du` was the culprit of consuming the CPU as >> >> a resource? during the `oc cluster up`, or after? >> > I tested with the upstream version overnight and Helloworld MSA, no >> problems >> > Minishift version: 1.0.0-rc.1 >> > it had no problems. >> >> great to hear... mostly, Minishift tries to stay out of the way of the >> actual OpenShift deployment. In that sense, we prepare the environment >> and allow configuration, and dealing with OpenShift when the >> deployment happened. From this perspective, I am interested in how 'it >> seems to use more memory/cpu'. Minishift itself should not cause this >> directly. But of course, our foundation (the Operating System/ISO) >> could be a problem. So, if you have any quantifiable metrics, please >> ;-). It might be helpful to also test different OpenShift versions >> with a release of the Minishift (CDK) binary+ISOs. >> >> Sorry, to make you have to consider a lot of testing... but this >> information can be valuable to track down the actual root cause. And >> yes, we have several in recent time which should improve the quality >> and performance of deploying using Minishift. >> >> Looking forward to more feedback... >> >> >> Gerard >> > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Wed Apr 5 13:41:19 2017 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 5 Apr 2017 09:41:19 -0400 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: Aha...left it running overnight (machine sleeping), woke it up this morning and Virtualbox is using 197% of CPU https://www.screencast.com/t/u2TuTzut Lots of du processes, working on the CPU https://www.screencast.com/t/JhG3mGMdRkYO now, this with Helloworld MSA and metrics ./minishift --metrics true start On Tue, Apr 4, 2017 at 11:42 PM, Burr Sutter wrote: > After lots of testing on the CDK variant, is no longer demonstrating the > crazy du processes eating all the CPU. I see one or two du processes spike > up but not to the point where it is overly problematic. I did have to turn > on metrics (which doesn't work anyway) to see the du process via top. > > Minishift version: 1.0.0-beta.5 > > CDK Version: 3.0.0-beta.3 > > > > > On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad wrote: > >> Hi Burr, >> >> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: >> > Adding devtools back to the thread. >> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad wrote: >> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >> wrote: >> >> > Still eats all the CPU :-) >> >> > du is the culprit according to top >> >> @burr when did you notice `du` was the culprit of consuming the CPU as >> >> a resource? during the `oc cluster up`, or after? >> > I tested with the upstream version overnight and Helloworld MSA, no >> problems >> > Minishift version: 1.0.0-rc.1 >> > it had no problems. >> >> great to hear... mostly, Minishift tries to stay out of the way of the >> actual OpenShift deployment. In that sense, we prepare the environment >> and allow configuration, and dealing with OpenShift when the >> deployment happened. From this perspective, I am interested in how 'it >> seems to use more memory/cpu'. Minishift itself should not cause this >> directly. But of course, our foundation (the Operating System/ISO) >> could be a problem. So, if you have any quantifiable metrics, please >> ;-). It might be helpful to also test different OpenShift versions >> with a release of the Minishift (CDK) binary+ISOs. >> >> Sorry, to make you have to consider a lot of testing... but this >> information can be valuable to track down the actual root cause. And >> yes, we have several in recent time which should improve the quality >> and performance of deploying using Minishift. >> >> Looking forward to more feedback... >> >> >> Gerard >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdyson at redhat.com Wed Apr 5 13:45:57 2017 From: jdyson at redhat.com (Jimmi Dyson) Date: Wed, 5 Apr 2017 14:45:57 +0100 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: Ah I see that minishift isn't using a centos VM so the du processes are almost definitely cadvisor checking aufs writable layer usage. Why there's so many du processes I don't know though... On Wed, Apr 5, 2017 at 2:41 PM, Burr Sutter wrote: > Aha...left it running overnight (machine sleeping), woke it up this > morning and > Virtualbox is using 197% of CPU > https://www.screencast.com/t/u2TuTzut > Lots of du processes, working on the CPU > https://www.screencast.com/t/JhG3mGMdRkYO > > now, this with Helloworld MSA and metrics > ./minishift --metrics true start > > > > On Tue, Apr 4, 2017 at 11:42 PM, Burr Sutter wrote: > >> After lots of testing on the CDK variant, is no longer demonstrating the >> crazy du processes eating all the CPU. I see one or two du processes spike >> up but not to the point where it is overly problematic. I did have to turn >> on metrics (which doesn't work anyway) to see the du process via top. >> >> Minishift version: 1.0.0-beta.5 >> >> CDK Version: 3.0.0-beta.3 >> >> >> >> >> On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad wrote: >> >>> Hi Burr, >>> >>> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: >>> > Adding devtools back to the thread. >>> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad >>> wrote: >>> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >>> wrote: >>> >> > Still eats all the CPU :-) >>> >> > du is the culprit according to top >>> >> @burr when did you notice `du` was the culprit of consuming the CPU as >>> >> a resource? during the `oc cluster up`, or after? >>> > I tested with the upstream version overnight and Helloworld MSA, no >>> problems >>> > Minishift version: 1.0.0-rc.1 >>> > it had no problems. >>> >>> great to hear... mostly, Minishift tries to stay out of the way of the >>> actual OpenShift deployment. In that sense, we prepare the environment >>> and allow configuration, and dealing with OpenShift when the >>> deployment happened. From this perspective, I am interested in how 'it >>> seems to use more memory/cpu'. Minishift itself should not cause this >>> directly. But of course, our foundation (the Operating System/ISO) >>> could be a problem. So, if you have any quantifiable metrics, please >>> ;-). It might be helpful to also test different OpenShift versions >>> with a release of the Minishift (CDK) binary+ISOs. >>> >>> Sorry, to make you have to consider a lot of testing... but this >>> information can be valuable to track down the actual root cause. And >>> yes, we have several in recent time which should improve the quality >>> and performance of deploying using Minishift. >>> >>> Looking forward to more feedback... >>> >>> >>> Gerard >>> >> >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmohanty at redhat.com Wed Apr 5 13:52:07 2017 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Wed, 5 Apr 2017 19:22:07 +0530 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: On Wed, Apr 5, 2017 at 7:15 PM, Jimmi Dyson wrote: > Ah I see that minishift isn't using a centos VM so the du processes are > almost definitely cadvisor checking aufs writable layer usage. Why there's > so many du processes I don't know though... > I do not think we have added any du process. I am not aware of this. -Lala > > On Wed, Apr 5, 2017 at 2:41 PM, Burr Sutter wrote: > >> Aha...left it running overnight (machine sleeping), woke it up this >> morning and >> Virtualbox is using 197% of CPU >> https://www.screencast.com/t/u2TuTzut >> Lots of du processes, working on the CPU >> https://www.screencast.com/t/JhG3mGMdRkYO >> >> now, this with Helloworld MSA and metrics >> ./minishift --metrics true start >> >> >> >> On Tue, Apr 4, 2017 at 11:42 PM, Burr Sutter wrote: >> >>> After lots of testing on the CDK variant, is no longer demonstrating the >>> crazy du processes eating all the CPU. I see one or two du processes spike >>> up but not to the point where it is overly problematic. I did have to turn >>> on metrics (which doesn't work anyway) to see the du process via top. >>> >>> Minishift version: 1.0.0-beta.5 >>> >>> CDK Version: 3.0.0-beta.3 >>> >>> >>> >>> >>> On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad wrote: >>> >>>> Hi Burr, >>>> >>>> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: >>>> > Adding devtools back to the thread. >>>> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad >>>> wrote: >>>> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >>>> wrote: >>>> >> > Still eats all the CPU :-) >>>> >> > du is the culprit according to top >>>> >> @burr when did you notice `du` was the culprit of consuming the CPU >>>> as >>>> >> a resource? during the `oc cluster up`, or after? >>>> > I tested with the upstream version overnight and Helloworld MSA, no >>>> problems >>>> > Minishift version: 1.0.0-rc.1 >>>> > it had no problems. >>>> >>>> great to hear... mostly, Minishift tries to stay out of the way of the >>>> actual OpenShift deployment. In that sense, we prepare the environment >>>> and allow configuration, and dealing with OpenShift when the >>>> deployment happened. From this perspective, I am interested in how 'it >>>> seems to use more memory/cpu'. Minishift itself should not cause this >>>> directly. But of course, our foundation (the Operating System/ISO) >>>> could be a problem. So, if you have any quantifiable metrics, please >>>> ;-). It might be helpful to also test different OpenShift versions >>>> with a release of the Minishift (CDK) binary+ISOs. >>>> >>>> Sorry, to make you have to consider a lot of testing... but this >>>> information can be valuable to track down the actual root cause. And >>>> yes, we have several in recent time which should improve the quality >>>> and performance of deploying using Minishift. >>>> >>>> Looking forward to more feedback... >>>> >>>> >>>> Gerard >>>> >>> >>> >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdyson at redhat.com Wed Apr 5 13:53:50 2017 From: jdyson at redhat.com (Jimmi Dyson) Date: Wed, 5 Apr 2017 14:53:50 +0100 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: On Wed, Apr 5, 2017 at 2:52 PM, Lalatendu Mohanty wrote: > > > On Wed, Apr 5, 2017 at 7:15 PM, Jimmi Dyson wrote: > >> Ah I see that minishift isn't using a centos VM so the du processes are >> almost definitely cadvisor checking aufs writable layer usage. Why there's >> so many du processes I don't know though... >> > > I do not think we have added any du process. I am not aware of this. > No I'm almost 100% sure this is cadvisor du processes caning CPU on sleep. IIRC that should have been limited and processes nice'd so as to not kill box... Wonder if sleep has messed up that throttling somehow. > > -Lala > > >> >> On Wed, Apr 5, 2017 at 2:41 PM, Burr Sutter wrote: >> >>> Aha...left it running overnight (machine sleeping), woke it up this >>> morning and >>> Virtualbox is using 197% of CPU >>> https://www.screencast.com/t/u2TuTzut >>> Lots of du processes, working on the CPU >>> https://www.screencast.com/t/JhG3mGMdRkYO >>> >>> now, this with Helloworld MSA and metrics >>> ./minishift --metrics true start >>> >>> >>> >>> On Tue, Apr 4, 2017 at 11:42 PM, Burr Sutter wrote: >>> >>>> After lots of testing on the CDK variant, is no longer demonstrating >>>> the crazy du processes eating all the CPU. I see one or two du processes >>>> spike up but not to the point where it is overly problematic. I did have >>>> to turn on metrics (which doesn't work anyway) to see the du process via >>>> top. >>>> >>>> Minishift version: 1.0.0-beta.5 >>>> >>>> CDK Version: 3.0.0-beta.3 >>>> >>>> >>>> >>>> >>>> On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad >>>> wrote: >>>> >>>>> Hi Burr, >>>>> >>>>> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter >>>>> wrote: >>>>> > Adding devtools back to the thread. >>>>> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad >>>>> wrote: >>>>> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >>>>> wrote: >>>>> >> > Still eats all the CPU :-) >>>>> >> > du is the culprit according to top >>>>> >> @burr when did you notice `du` was the culprit of consuming the CPU >>>>> as >>>>> >> a resource? during the `oc cluster up`, or after? >>>>> > I tested with the upstream version overnight and Helloworld MSA, no >>>>> problems >>>>> > Minishift version: 1.0.0-rc.1 >>>>> > it had no problems. >>>>> >>>>> great to hear... mostly, Minishift tries to stay out of the way of the >>>>> actual OpenShift deployment. In that sense, we prepare the environment >>>>> and allow configuration, and dealing with OpenShift when the >>>>> deployment happened. From this perspective, I am interested in how 'it >>>>> seems to use more memory/cpu'. Minishift itself should not cause this >>>>> directly. But of course, our foundation (the Operating System/ISO) >>>>> could be a problem. So, if you have any quantifiable metrics, please >>>>> ;-). It might be helpful to also test different OpenShift versions >>>>> with a release of the Minishift (CDK) binary+ISOs. >>>>> >>>>> Sorry, to make you have to consider a lot of testing... but this >>>>> information can be valuable to track down the actual root cause. And >>>>> yes, we have several in recent time which should improve the quality >>>>> and performance of deploying using Minishift. >>>>> >>>>> Looking forward to more feedback... >>>>> >>>>> >>>>> Gerard >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://www.redhat.com/mailman/listinfo/devtools >>> >>> >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccoleman at redhat.com Wed Apr 5 14:53:58 2017 From: ccoleman at redhat.com (Clayton Coleman) Date: Wed, 5 Apr 2017 16:53:58 +0200 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> Message-ID: <2536920768340385855@unknownmsgid> Could be clock skew after sleep, if something is calculating a schedule for runs and sees it has fallen behind (all the time the box was asleep?) and then tries to run all the missing du executions. One way to test - set the clock forward a few hours and see if you get a spike in du On Apr 5, 2017, at 3:52 PM, Lalatendu Mohanty wrote: On Wed, Apr 5, 2017 at 7:15 PM, Jimmi Dyson wrote: > Ah I see that minishift isn't using a centos VM so the du processes are > almost definitely cadvisor checking aufs writable layer usage. Why there's > so many du processes I don't know though... > I do not think we have added any du process. I am not aware of this. -Lala > > On Wed, Apr 5, 2017 at 2:41 PM, Burr Sutter wrote: > >> Aha...left it running overnight (machine sleeping), woke it up this >> morning and >> Virtualbox is using 197% of CPU >> https://www.screencast.com/t/u2TuTzut >> Lots of du processes, working on the CPU >> https://www.screencast.com/t/JhG3mGMdRkYO >> >> now, this with Helloworld MSA and metrics >> ./minishift --metrics true start >> >> >> >> On Tue, Apr 4, 2017 at 11:42 PM, Burr Sutter wrote: >> >>> After lots of testing on the CDK variant, is no longer demonstrating the >>> crazy du processes eating all the CPU. I see one or two du processes spike >>> up but not to the point where it is overly problematic. I did have to turn >>> on metrics (which doesn't work anyway) to see the du process via top. >>> >>> Minishift version: 1.0.0-beta.5 >>> >>> CDK Version: 3.0.0-beta.3 >>> >>> >>> >>> >>> On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad wrote: >>> >>>> Hi Burr, >>>> >>>> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter wrote: >>>> > Adding devtools back to the thread. >>>> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad >>>> wrote: >>>> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >>>> wrote: >>>> >> > Still eats all the CPU :-) >>>> >> > du is the culprit according to top >>>> >> @burr when did you notice `du` was the culprit of consuming the CPU >>>> as >>>> >> a resource? during the `oc cluster up`, or after? >>>> > I tested with the upstream version overnight and Helloworld MSA, no >>>> problems >>>> > Minishift version: 1.0.0-rc.1 >>>> > it had no problems. >>>> >>>> great to hear... mostly, Minishift tries to stay out of the way of the >>>> actual OpenShift deployment. In that sense, we prepare the environment >>>> and allow configuration, and dealing with OpenShift when the >>>> deployment happened. From this perspective, I am interested in how 'it >>>> seems to use more memory/cpu'. Minishift itself should not cause this >>>> directly. But of course, our foundation (the Operating System/ISO) >>>> could be a problem. So, if you have any quantifiable metrics, please >>>> ;-). It might be helpful to also test different OpenShift versions >>>> with a release of the Minishift (CDK) binary+ISOs. >>>> >>>> Sorry, to make you have to consider a lot of testing... but this >>>> information can be valuable to track down the actual root cause. And >>>> yes, we have several in recent time which should improve the quality >>>> and performance of deploying using Minishift. >>>> >>>> Looking forward to more feedback... >>>> >>>> >>>> Gerard >>>> >>> >>> >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > _______________________________________________ Devtools mailing list Devtools at redhat.com https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Wed Apr 5 15:03:02 2017 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 5 Apr 2017 11:03:02 -0400 Subject: [Devtools] Subscriptions are expiring Message-ID: Attempting a yum install (which worked earlier today) fails with This system is not registered... https://www.screencast.com/t/vMsufYiX So, visit developers.redhat.com and login, see Additional Action Required, agree to Ts&Cs https://www.screencast.com/t/7TjjuFXtoLR Google "how to use rhel subscription-manager" https://access.redhat.com/solutions/253273 sudo subscription-manager register --username $SUB_USERNAME --password $SUB_PASSWORD --auto-attach https://www.screencast.com/t/Yixi7kg5sFx Then re-enable your repos...which I have not figured out what repos I had before the expiration. https://www.screencast.com/t/WAubLcs9aY -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Wed Apr 5 19:57:08 2017 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 5 Apr 2017 15:57:08 -0400 Subject: [Devtools] video installing the CDK Message-ID: https://www.youtube.com/watch?v=VR-diXSowEM&feature=youtu.be -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Wed Apr 5 20:17:45 2017 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 5 Apr 2017 16:17:45 -0400 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: <2536920768340385855@unknownmsgid> References: <20170328202825.GA61742@nineveh.local> <20170329202439.GH76587@nineveh.local> <2536920768340385855@unknownmsgid> Message-ID: So, I left it running just to see what it would do...eventually the "du" processes seem to quiet down and virtualbox went quiet....and it seems that openshift crashed. The VM is still up but I can't find an openshift process. oc login error: dial tcp 192.168.99.104:8443: getsockopt: connection refused and after a "minishift ssh" ps -ef | grep openshift docker 10876 10855 0 16:05 pts/0 00:00:00 grep --color=auto *openshift* On Wed, Apr 5, 2017 at 10:53 AM, Clayton Coleman wrote: > Could be clock skew after sleep, if something is calculating a schedule > for runs and sees it has fallen behind (all the time the box was asleep?) > and then tries to run all the missing du executions. > > One way to test - set the clock forward a few hours and see if you get a > spike in du > > On Apr 5, 2017, at 3:52 PM, Lalatendu Mohanty wrote: > > > > On Wed, Apr 5, 2017 at 7:15 PM, Jimmi Dyson wrote: > >> Ah I see that minishift isn't using a centos VM so the du processes are >> almost definitely cadvisor checking aufs writable layer usage. Why there's >> so many du processes I don't know though... >> > > I do not think we have added any du process. I am not aware of this. > > -Lala > > >> >> On Wed, Apr 5, 2017 at 2:41 PM, Burr Sutter wrote: >> >>> Aha...left it running overnight (machine sleeping), woke it up this >>> morning and >>> Virtualbox is using 197% of CPU >>> https://www.screencast.com/t/u2TuTzut >>> Lots of du processes, working on the CPU >>> https://www.screencast.com/t/JhG3mGMdRkYO >>> >>> now, this with Helloworld MSA and metrics >>> ./minishift --metrics true start >>> >>> >>> >>> On Tue, Apr 4, 2017 at 11:42 PM, Burr Sutter wrote: >>> >>>> After lots of testing on the CDK variant, is no longer demonstrating >>>> the crazy du processes eating all the CPU. I see one or two du processes >>>> spike up but not to the point where it is overly problematic. I did have >>>> to turn on metrics (which doesn't work anyway) to see the du process via >>>> top. >>>> >>>> Minishift version: 1.0.0-beta.5 >>>> >>>> CDK Version: 3.0.0-beta.3 >>>> >>>> >>>> >>>> >>>> On Tue, Apr 4, 2017 at 10:37 AM, Gerard Braad >>>> wrote: >>>> >>>>> Hi Burr, >>>>> >>>>> On Tue, Apr 4, 2017 at 8:34 PM, Burr Sutter >>>>> wrote: >>>>> > Adding devtools back to the thread. >>>>> > On Tue, Apr 4, 2017 at 2:13 AM, Gerard Braad >>>>> wrote: >>>>> >> On Thu, Mar 30, 2017 at 10:47 PM, Burr Sutter >>>>> wrote: >>>>> >> > Still eats all the CPU :-) >>>>> >> > du is the culprit according to top >>>>> >> @burr when did you notice `du` was the culprit of consuming the CPU >>>>> as >>>>> >> a resource? during the `oc cluster up`, or after? >>>>> > I tested with the upstream version overnight and Helloworld MSA, no >>>>> problems >>>>> > Minishift version: 1.0.0-rc.1 >>>>> > it had no problems. >>>>> >>>>> great to hear... mostly, Minishift tries to stay out of the way of the >>>>> actual OpenShift deployment. In that sense, we prepare the environment >>>>> and allow configuration, and dealing with OpenShift when the >>>>> deployment happened. From this perspective, I am interested in how 'it >>>>> seems to use more memory/cpu'. Minishift itself should not cause this >>>>> directly. But of course, our foundation (the Operating System/ISO) >>>>> could be a problem. So, if you have any quantifiable metrics, please >>>>> ;-). It might be helpful to also test different OpenShift versions >>>>> with a release of the Minishift (CDK) binary+ISOs. >>>>> >>>>> Sorry, to make you have to consider a lot of testing... but this >>>>> information can be valuable to track down the actual root cause. And >>>>> yes, we have several in recent time which should improve the quality >>>>> and performance of deploying using Minishift. >>>>> >>>>> Looking forward to more feedback... >>>>> >>>>> >>>>> Gerard >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://www.redhat.com/mailman/listinfo/devtools >>> >>> >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgurung at redhat.com Thu Apr 6 02:54:55 2017 From: bgurung at redhat.com (Budh Gurung) Date: Thu, 6 Apr 2017 08:24:55 +0530 Subject: [Devtools] video installing the CDK In-Reply-To: References: Message-ID: Nice video and editing! Regards, Budh Ram Gurung Software Engineer - Devtools On Thu, Apr 6, 2017 at 1:27 AM, Burr Sutter wrote: > https://www.youtube.com/watch?v=VR-diXSowEM&feature=youtu.be > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hferents at redhat.com Thu Apr 6 10:54:00 2017 From: hferents at redhat.com (Hardy Ferentschik) Date: Thu, 6 Apr 2017 12:54:00 +0200 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <2536920768340385855@unknownmsgid> Message-ID: <20170406105400.GA74041@ovpn-117-225.ams2.redhat.com> Hi, On Wed, 05-Apr-2017 16:17, Burr Sutter wrote: > So, I left it running just to see what it would do...eventually the "du" > processes seem to quiet down and virtualbox went quiet....and it seems that > openshift crashed. The VM is still up but I can't find an openshift > process. Ok, thanks for all the updates. I am planning to spend some time on testing MSA on various Minishfit versions over the next week or so. I'll hopefully have something to report back. At least it seems we are making progress :-) --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From bsutter at redhat.com Thu Apr 6 13:55:56 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 6 Apr 2017 09:55:56 -0400 Subject: [Devtools] oc cli Message-ID: where does someone get the correct oc cli for minishift-cdk beta3? -------------- next part -------------- An HTML attachment was scrubbed... URL: From degolovi at redhat.com Thu Apr 6 14:03:36 2017 From: degolovi at redhat.com (Denis Golovin) Date: Thu, 6 Apr 2017 07:03:36 -0700 Subject: [Devtools] oc cli In-Reply-To: References: Message-ID: First you do minishift setup-cdk then you should have oc in %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 On Thu, Apr 6, 2017 at 6:55 AM, Burr Sutter wrote: > where does someone get the correct oc cli for minishift-cdk beta3? > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Thu Apr 6 14:06:38 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 6 Apr 2017 10:06:38 -0400 Subject: [Devtools] oc cli In-Reply-To: References: Message-ID: well the is cool, let me give it a try! My current document says "brew install openshift-cli" but that doesn't work on Windows :-) On Thu, Apr 6, 2017 at 10:03 AM, Denis Golovin wrote: > First you do > > minishift setup-cdk > > then you should have oc in > > %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > > > On Thu, Apr 6, 2017 at 6:55 AM, Burr Sutter wrote: > >> where does someone get the correct oc cli for minishift-cdk beta3? >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Thu Apr 6 14:08:06 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 6 Apr 2017 10:08:06 -0400 Subject: [Devtools] oc cli In-Reply-To: References: Message-ID: by the way "minishift version" should work even before "setup-cdk", otherwise how do I know that somebody passed me the right .exe version :-) On Thu, Apr 6, 2017 at 10:06 AM, Burr Sutter wrote: > well the is cool, let me give it a try! > > My current document says "brew install openshift-cli" but that doesn't > work on Windows :-) > > On Thu, Apr 6, 2017 at 10:03 AM, Denis Golovin > wrote: > >> First you do >> >> minishift setup-cdk >> >> then you should have oc in >> >> %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 >> >> >> On Thu, Apr 6, 2017 at 6:55 AM, Burr Sutter wrote: >> >>> where does someone get the correct oc cli for minishift-cdk beta3? >>> >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://www.redhat.com/mailman/listinfo/devtools >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From degolovi at redhat.com Thu Apr 6 14:13:05 2017 From: degolovi at redhat.com (Denis Golovin) Date: Thu, 6 Apr 2017 07:13:05 -0700 Subject: [Devtools] oc cli In-Reply-To: References: Message-ID: it works ;) C:\Users\eskimo>minishift version You need to run 'minishift.exe setup-cdk' first to install required CDK components. C:\Users\eskimo>minishift setup-cdk Setting up CDK 3 on host using 'C:\Users\eskimo\.minishift' as Minishift's home directory Copying minishift-rhel7.iso to 'C:\Users\eskimo\.minishift/ cache/iso/minishift-rhel7.iso' Copying oc.exe to 'C:\Users\eskimo\.minishift/cache/oc/v3.4.1.2/oc.exe' Creating configuration file 'C:\Users\eskimo\.minishift/config/config.json' Creating marker file 'C:\Users\eskimo\.minishift/cdk' CDK 3 setup complete. C:\Users\eskimo>minishift version Minishift version: 1.0.0-beta.5 CDK Version: 3.0.0-beta.3 C:\Users\eskimo> On Thu, Apr 6, 2017 at 7:08 AM, Burr Sutter wrote: > by the way "minishift version" should work even before "setup-cdk", > otherwise how do I know that somebody passed me the right .exe version :-) > > On Thu, Apr 6, 2017 at 10:06 AM, Burr Sutter wrote: > >> well the is cool, let me give it a try! >> >> My current document says "brew install openshift-cli" but that doesn't >> work on Windows :-) >> >> On Thu, Apr 6, 2017 at 10:03 AM, Denis Golovin >> wrote: >> >>> First you do >>> >>> minishift setup-cdk >>> >>> then you should have oc in >>> >>> %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 >>> >>> >>> On Thu, Apr 6, 2017 at 6:55 AM, Burr Sutter wrote: >>> >>>> where does someone get the correct oc cli for minishift-cdk beta3? >>>> >>>> _______________________________________________ >>>> Devtools mailing list >>>> Devtools at redhat.com >>>> https://www.redhat.com/mailman/listinfo/devtools >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From prkumar at redhat.com Thu Apr 6 14:38:27 2017 From: prkumar at redhat.com (Praveen Kumar) Date: Thu, 6 Apr 2017 20:08:27 +0530 Subject: [Devtools] oc cli In-Reply-To: References: Message-ID: On Thu, Apr 6, 2017 at 7:38 PM, Burr Sutter wrote: > by the way "minishift version" should work even before "setup-cdk", > otherwise how do I know that somebody passed me the right .exe version :-) Yes, right now we force user to run setup-cdk before any command, will see if we can have some improvement around it but can't promise right now :) > > On Thu, Apr 6, 2017 at 10:06 AM, Burr Sutter wrote: >> >> well the is cool, let me give it a try! >> >> My current document says "brew install openshift-cli" but that doesn't >> work on Windows :-) >> >> On Thu, Apr 6, 2017 at 10:03 AM, Denis Golovin >> wrote: >>> >>> First you do >>> >>> minishift setup-cdk >>> >>> then you should have oc in >>> >>> %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 >>> >>> >>> On Thu, Apr 6, 2017 at 6:55 AM, Burr Sutter wrote: >>>> >>>> where does someone get the correct oc cli for minishift-cdk beta3? >>>> >>>> _______________________________________________ >>>> Devtools mailing list >>>> Devtools at redhat.com >>>> https://www.redhat.com/mailman/listinfo/devtools >>>> >>> >> > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen From bsutter at redhat.com Thu Apr 6 14:41:11 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 6 Apr 2017 10:41:11 -0400 Subject: [Devtools] oc cli In-Reply-To: References: Message-ID: On Thu, Apr 6, 2017 at 10:38 AM, Praveen Kumar wrote: > On Thu, Apr 6, 2017 at 7:38 PM, Burr Sutter wrote: > > by the way "minishift version" should work even before "setup-cdk", > > otherwise how do I know that somebody passed me the right .exe version > :-) > > Yes, right now we force user to run setup-cdk before any command, will > see if we can have some improvement around it but can't promise right > now :) > I understand I like running "version" on CLI tools just so I know that I have the right one. The average .NET/Windows developer dislikes doing things at a command line to begin with. And I find many developers are unclear on how the PATH really works, so having the "version" option available to know that I have the right binary is pretty important part of the getting started experience. > > > > > On Thu, Apr 6, 2017 at 10:06 AM, Burr Sutter wrote: > >> > >> well the is cool, let me give it a try! > >> > >> My current document says "brew install openshift-cli" but that doesn't > >> work on Windows :-) > >> > >> On Thu, Apr 6, 2017 at 10:03 AM, Denis Golovin > >> wrote: > >>> > >>> First you do > >>> > >>> minishift setup-cdk > >>> > >>> then you should have oc in > >>> > >>> %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > >>> > >>> > >>> On Thu, Apr 6, 2017 at 6:55 AM, Burr Sutter > wrote: > >>>> > >>>> where does someone get the correct oc cli for minishift-cdk beta3? > >>>> > >>>> _______________________________________________ > >>>> Devtools mailing list > >>>> Devtools at redhat.com > >>>> https://www.redhat.com/mailman/listinfo/devtools > >>>> > >>> > >> > > > > > > _______________________________________________ > > Devtools mailing list > > Devtools at redhat.com > > https://www.redhat.com/mailman/listinfo/devtools > > > > > > -- > Praveen Kumar > https://fedoraproject.org/wiki/User:Kumarpraveen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Thu Apr 6 15:46:40 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 6 Apr 2017 11:46:40 -0400 Subject: [Devtools] Created Issues Message-ID: 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) https://github.com/minishift/minishift/issues/695 2) Need an admin/admin user https://github.com/minishift/minishift/issues/696 3) Disk size? https://github.com/minishift/minishift/issues/697 4) --metrics true does not seem to work https://github.com/minishift/minishift/issues/698 5) config set and view are out of order https://github.com/minishift/minishift/issues/699 6) version should be available prior to setup-cdk https://github.com/minishift/minishift/issues/700 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgurung at redhat.com Thu Apr 6 17:31:37 2017 From: bgurung at redhat.com (Budh Gurung) Date: Thu, 6 Apr 2017 23:01:37 +0530 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: Hi Burr, Comments inline. On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: > 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) > https://github.com/minishift/minishift/issues/695 > I doubt you actually hit by this issue https://issues.jboss.org/browse/CDK-70. This happens when you don't have ssh.exe binary set in your *PATH*. We have observed that installing OpenSSH for Windows resolve this issue. Investigation is undergoing to know the actual reason. > > 2) Need an admin/admin user > https://github.com/minishift/minishift/issues/696 > This I am not sure as we given 'developer' user a 'sudoer' role by default and all admin operations can be run with "--as system:admin". > 3) Disk size? > https://github.com/minishift/minishift/issues/697 > With `--disk-size` option in "start" command. Check in more detail here https://docs.openshift.org/latest/minishift/command-ref/minishift_start.html > > 4) --metrics true does not seem to work > https://github.com/minishift/minishift/issues/698 > We had similar issue here https://github.com/minishift/minishift/issues/606 . > 5) config set and view are out of order > https://github.com/minishift/minishift/issues/699 > We couldn't find the value in the order of config values. Would definitely like to hear if ordering config values achieve any specific use case here. > 6) version should be available prior to setup-cdk > https://github.com/minishift/minishift/issues/700 > AFAIR, we did that in order detect whether binary is CDK binary or upstream minishift binary. We might need to find another way if we really want to see version before "setup-cdk". We checks the existance of cdk marker file in CDK binary which contains information like cdk version (also used by devstudio). "setup-cdk" step creates that marker file and hence you get expected version after that. We don't do this check in upstream minishift binary. > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > Regards, Budh Ram Gurung Software Engineer - Devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Thu Apr 6 22:39:01 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 6 Apr 2017 18:39:01 -0400 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: On Thu, Apr 6, 2017 at 1:31 PM, Budh Gurung wrote: > Hi Burr, > > Comments inline. > > On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: > >> 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) >> https://github.com/minishift/minishift/issues/695 >> > > I doubt you actually hit by this issue https://issues.jboss. > org/browse/CDK-70. > > This happens when you don't have ssh.exe binary set in your *PATH*. > We have observed that installing OpenSSH for Windows > resolve this issue. > > Investigation is undergoing to know the actual reason. > That sounds like it. I am out of CDK on Windows testing time for several days but I might be able to try a beta 4 when it becomes available. > > >> >> 2) Need an admin/admin user >> https://github.com/minishift/minishift/issues/696 >> > > This I am not sure as we given 'developer' user a 'sudoer' role by > default and all > admin operations can be run with "--as system:admin". > Right, but as a human, I need to be able to login to the console as admin :-) Damn humans/users. > > >> 3) Disk size? >> https://github.com/minishift/minishift/issues/697 >> > > With `--disk-size` option in "start" command. > Check in more detail here > https://docs.openshift.org/latest/minishift/command-ref/ > minishift_start.html > Why is that not a "minishift config set disk-size 20gb" like memory and CPUs? > > > >> >> 4) --metrics true does not seem to work >> https://github.com/minishift/minishift/issues/698 >> > > We had similar issue here https://github.com/ > minishift/minishift/issues/606 . > > >> 5) config set and view are out of order >> https://github.com/minishift/minishift/issues/699 >> > > We couldn't find the value in the order of config values. > Would definitely like to hear if ordering config values achieve any > specific use case here. > As a user, I expect 2 ordering schemes: 1) The order is consistent for every time I use "minishift config view", right not the order jumps around based on what was last "set this" or "set that". Basically the order is currently "random" from what I can tell or 2) The order based on my various "set this" and "set that". So if I use "set memory 6000" then "set cpus 2" and then "set vm-driver virtualbox" then "config view" should display those same settings in that same order. Either approach would work for me :-) > > >> 6) version should be available prior to setup-cdk >> https://github.com/minishift/minishift/issues/700 >> > > AFAIR, we did that in order detect whether binary is CDK binary > or upstream minishift binary. We might need to find another way > if we really want to see version before "setup-cdk". > > We checks the existance of cdk marker file in CDK binary which contains > information like cdk version (also used by devstudio). > "setup-cdk" step creates that marker file and hence you > get expected version after that. > > We don't do this check in upstream minishift binary. > > I understand, it is just very weird for the end-user. one of the biggest problems with any cli is "how do I know that I have the right one?" > >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > Regards, > Budh Ram Gurung > Software Engineer - Devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgurung at redhat.com Fri Apr 7 03:43:43 2017 From: bgurung at redhat.com (Budh Gurung) Date: Fri, 7 Apr 2017 09:13:43 +0530 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: Hi Burr, On Fri, Apr 7, 2017 at 4:09 AM, Burr Sutter wrote: > > > On Thu, Apr 6, 2017 at 1:31 PM, Budh Gurung wrote: > >> Hi Burr, >> >> Comments inline. >> >> On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: >> >>> 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) >>> https://github.com/minishift/minishift/issues/695 >>> >> >> I doubt you actually hit by this issue https://issues.jboss.org >> /browse/CDK-70. >> >> This happens when you don't have ssh.exe binary set in your *PATH*. >> We have observed that installing OpenSSH for Windows >> resolve this issue. >> >> Investigation is undergoing to know the actual reason. >> > > That sounds like it. I am out of CDK on Windows testing time for several > days but I might be able to try a beta 4 when it becomes available. > > >> >> >>> >>> 2) Need an admin/admin user >>> https://github.com/minishift/minishift/issues/696 >>> >> >> This I am not sure as we given 'developer' user a 'sudoer' role by >> default and all >> admin operations can be run with "--as system:admin". >> > > Right, but as a human, I need to be able to login to the console as admin > :-) > > Damn humans/users. > > >> >> >>> 3) Disk size? >>> https://github.com/minishift/minishift/issues/697 >>> >> >> With `--disk-size` option in "start" command. >> Check in more detail here >> https://docs.openshift.org/latest/minishift/command-ref/mini >> shift_start.html >> > > Why is that not a "minishift config set disk-size 20gb" like memory and > CPUs? > You can run exactly same command except 20gb and it will work :). "gb" is not used as unit here. Valid units are b, k, m or g maps to Bytes, KB, MB, or GB respectively. Actual command is "minishift config set disk-size 20g" In fact, you can use "config set" command to all the options/properties listed here https://docs.openshift.org/latest/minishift/command-ref/minishift_config.html Hope it helps. > >> >> >>> >>> 4) --metrics true does not seem to work >>> https://github.com/minishift/minishift/issues/698 >>> >> >> We had similar issue here https://github.com/minish >> ift/minishift/issues/606 . >> > >> >>> 5) config set and view are out of order >>> https://github.com/minishift/minishift/issues/699 >>> >> >> We couldn't find the value in the order of config values. >> Would definitely like to hear if ordering config values achieve any >> specific use case here. >> > > As a user, I expect 2 ordering schemes: > 1) The order is consistent for every time I use "minishift config view", > right not the order jumps around based on what was last "set this" or "set > that". Basically the order is currently "random" from what I can tell > or > 1st approach has been used as part of version 1.0.0-rc1. You might want to look into it. > 2) The order based on my various "set this" and "set that". So if I use > "set memory 6000" then "set cpus 2" and then "set vm-driver virtualbox" > then "config view" should display those same settings in that same order. > > Either approach would work for me :-) > > >> >> >>> 6) version should be available prior to setup-cdk >>> https://github.com/minishift/minishift/issues/700 >>> >> >> AFAIR, we did that in order detect whether binary is CDK binary >> or upstream minishift binary. We might need to find another way >> if we really want to see version before "setup-cdk". >> >> We checks the existance of cdk marker file in CDK binary which contains >> information like cdk version (also used by devstudio). >> "setup-cdk" step creates that marker file and hence you >> get expected version after that. >> >> We don't do this check in upstream minishift binary. >> >> > >>> >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://www.redhat.com/mailman/listinfo/devtools >>> >>> >> Regards, >> Budh Ram Gurung >> Software Engineer - Devtools >> > > Regards, Budh Ram Gurung Software Engineer - Devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From prkumar at redhat.com Fri Apr 7 05:09:25 2017 From: prkumar at redhat.com (Praveen Kumar) Date: Fri, 7 Apr 2017 10:39:25 +0530 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: On Fri, Apr 7, 2017 at 4:09 AM, Burr Sutter wrote: > > > On Thu, Apr 6, 2017 at 1:31 PM, Budh Gurung wrote: >> >> Hi Burr, >> >> Comments inline. >> >> On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: >>> >>> 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) >>> https://github.com/minishift/minishift/issues/695 >> >> >> I doubt you actually hit by this issue >> https://issues.jboss.org/browse/CDK-70. >> >> This happens when you don't have ssh.exe binary set in your PATH. >> >> We have observed that installing OpenSSH for Windows resolve this issue. >> >> Investigation is undergoing to know the actual reason. > > > That sounds like it. I am out of CDK on Windows testing time for several > days but I might be able to try a beta 4 when it becomes available. > >> >> >>> >>> >>> 2) Need an admin/admin user >>> https://github.com/minishift/minishift/issues/696 >> >> >> This I am not sure as we given 'developer' user a 'sudoer' role by >> default and all >> admin operations can be run with "--as system:admin". > > > Right, but as a human, I need to be able to login to the console as admin > :-) > > Damn humans/users. Recently we added addons features[0], using that it's now easy achievable. Matter of fact we add this as default addon so in next internal release (Mostly on Tuesday next week) will not have this kind of issues. [0] https://docs.openshift.org/latest/minishift/command-ref/minishift_addons.html > >> >> >>> >>> 3) Disk size? >>> https://github.com/minishift/minishift/issues/697 >> >> >> With `--disk-size` option in "start" command. >> Check in more detail here >> >> https://docs.openshift.org/latest/minishift/command-ref/minishift_start.html > > > Why is that not a "minishift config set disk-size 20gb" like memory and > CPUs? >> >> >> >>> >>> >>> 4) --metrics true does not seem to work >>> https://github.com/minishift/minishift/issues/698 >> >> >> We had similar issue here >> https://github.com/minishift/minishift/issues/606 . >> >> >>> >>> 5) config set and view are out of order >>> https://github.com/minishift/minishift/issues/699 >> >> >> We couldn't find the value in the order of config values. >> Would definitely like to hear if ordering config values achieve any >> specific use case here. > > > As a user, I expect 2 ordering schemes: > 1) The order is consistent for every time I use "minishift config view", > right not the order jumps around based on what was last "set this" or "set > that". Basically the order is currently "random" from what I can tell > or > 2) The order based on my various "set this" and "set that". So if I use > "set memory 6000" then "set cpus 2" and then "set vm-driver virtualbox" then > "config view" should display those same settings in that same order. > > Either approach would work for me :-) > >> >> >>> >>> 6) version should be available prior to setup-cdk >>> https://github.com/minishift/minishift/issues/700 >> >> >> AFAIR, we did that in order detect whether binary is CDK binary >> or upstream minishift binary. We might need to find another way >> if we really want to see version before "setup-cdk". >> >> We checks the existance of cdk marker file in CDK binary which contains >> information like cdk version (also used by devstudio). >> "setup-cdk" step creates that marker file and hence you >> get expected version after that. >> >> We don't do this check in upstream minishift binary. >> > > I understand, it is just very weird for the end-user. one of the biggest > problems with any cli is "how do I know that I have the right one?" > > >>> >>> >>> >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://www.redhat.com/mailman/listinfo/devtools >>> >> >> Regards, >> Budh Ram Gurung >> Software Engineer - Devtools > > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen From lmohanty at redhat.com Fri Apr 7 06:49:39 2017 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Fri, 7 Apr 2017 12:19:39 +0530 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: On Fri, Apr 7, 2017 at 4:09 AM, Burr Sutter wrote: > > > On Thu, Apr 6, 2017 at 1:31 PM, Budh Gurung wrote: > >> Hi Burr, >> >> Comments inline. >> >> On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: >> >>> 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) >>> https://github.com/minishift/minishift/issues/695 >>> >> >> I doubt you actually hit by this issue https://issues.jboss.org >> /browse/CDK-70. >> >> This happens when you don't have ssh.exe binary set in your *PATH*. >> We have observed that installing OpenSSH for Windows >> resolve this issue. >> >> Investigation is undergoing to know the actual reason. >> > > That sounds like it. I am out of CDK on Windows testing time for several > days but I might be able to try a beta 4 when it becomes available. > > >> >> >>> >>> 2) Need an admin/admin user >>> https://github.com/minishift/minishift/issues/696 >>> >> >> This I am not sure as we given 'developer' user a 'sudoer' role by >> default and all >> admin operations can be run with "--as system:admin". >> > > Right, but as a human, I need to be able to login to the console as admin > :-) > > Damn humans/users. > Hi Burr, Please check the issues you had raised. It has several comments which will be useful to you and on some issues we need information from you. Regarding the system:admin user I think you are comparing the UX with CDK 2.x. We have done things little differently in CDK 3 but have done it in a right way as developer user should not have by default the cluster-admin role. It is like making any user in Linux as root. However we have discussed in the issue that we might want to have a separate user who will have cluster-admin role by default. Thanks, Lala > > >> >> >>> 3) Disk size? >>> https://github.com/minishift/minishift/issues/697 >>> >> >> With `--disk-size` option in "start" command. >> Check in more detail here >> https://docs.openshift.org/latest/minishift/command-ref/mini >> shift_start.html >> > > Why is that not a "minishift config set disk-size 20gb" like memory and > CPUs? > >> >> >> >>> >>> 4) --metrics true does not seem to work >>> https://github.com/minishift/minishift/issues/698 >>> >> >> We had similar issue here https://github.com/minish >> ift/minishift/issues/606 . >> > >> >>> 5) config set and view are out of order >>> https://github.com/minishift/minishift/issues/699 >>> >> >> We couldn't find the value in the order of config values. >> Would definitely like to hear if ordering config values achieve any >> specific use case here. >> > > As a user, I expect 2 ordering schemes: > 1) The order is consistent for every time I use "minishift config view", > right not the order jumps around based on what was last "set this" or "set > that". Basically the order is currently "random" from what I can tell > or > 2) The order based on my various "set this" and "set that". So if I use > "set memory 6000" then "set cpus 2" and then "set vm-driver virtualbox" > then "config view" should display those same settings in that same order. > > Either approach would work for me :-) > > >> >> >>> 6) version should be available prior to setup-cdk >>> https://github.com/minishift/minishift/issues/700 >>> >> >> AFAIR, we did that in order detect whether binary is CDK binary >> or upstream minishift binary. We might need to find another way >> if we really want to see version before "setup-cdk". >> >> We checks the existance of cdk marker file in CDK binary which contains >> information like cdk version (also used by devstudio). >> "setup-cdk" step creates that marker file and hence you >> get expected version after that. >> >> We don't do this check in upstream minishift binary. >> >> > I understand, it is just very weird for the end-user. one of the biggest > problems with any cli is "how do I know that I have the right one?" > > > >> >>> >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://www.redhat.com/mailman/listinfo/devtools >>> >>> >> Regards, >> Budh Ram Gurung >> Software Engineer - Devtools >> > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Fri Apr 7 12:47:54 2017 From: bsutter at redhat.com (Burr Sutter) Date: Fri, 7 Apr 2017 08:47:54 -0400 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: On Fri, Apr 7, 2017 at 2:49 AM, Lalatendu Mohanty wrote: > > > On Fri, Apr 7, 2017 at 4:09 AM, Burr Sutter wrote: > >> >> >> On Thu, Apr 6, 2017 at 1:31 PM, Budh Gurung wrote: >> >>> Hi Burr, >>> >>> Comments inline. >>> >>> On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: >>> >>>> 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) >>>> https://github.com/minishift/minishift/issues/695 >>>> >>> >>> I doubt you actually hit by this issue https://issues.jboss.org >>> /browse/CDK-70. >>> >>> This happens when you don't have ssh.exe binary set in your *PATH*. >>> We have observed that installing OpenSSH for Windows >>> resolve this issue. >>> >>> Investigation is undergoing to know the actual reason. >>> >> >> That sounds like it. I am out of CDK on Windows testing time for several >> days but I might be able to try a beta 4 when it becomes available. >> >> >>> >>> >>>> >>>> 2) Need an admin/admin user >>>> https://github.com/minishift/minishift/issues/696 >>>> >>> >>> This I am not sure as we given 'developer' user a 'sudoer' role by >>> default and all >>> admin operations can be run with "--as system:admin". >>> >> >> Right, but as a human, I need to be able to login to the console as admin >> :-) >> >> Damn humans/users. >> > > Hi Burr, > > Please check the issues you had raised. It has several comments which will > be useful to you and on some issues we need information from you. > > Regarding the system:admin user I think you are comparing the UX with CDK > 2.x. We have done things little differently in CDK 3 but have done it in a > right way as developer user should not have by default the cluster-admin > role. It is like making any user in Linux as root. However we have > discussed in the issue that we might want to have a separate user who will > have cluster-admin role by default. > Right in the old CDK it was "admin, admin" > > Thanks, > Lala > >> >> >>> >>> >>>> 3) Disk size? >>>> https://github.com/minishift/minishift/issues/697 >>>> >>> >>> With `--disk-size` option in "start" command. >>> Check in more detail here >>> https://docs.openshift.org/latest/minishift/command-ref/mini >>> shift_start.html >>> >> >> Why is that not a "minishift config set disk-size 20gb" like memory and >> CPUs? >> >>> >>> >>> >>>> >>>> 4) --metrics true does not seem to work >>>> https://github.com/minishift/minishift/issues/698 >>>> >>> >>> We had similar issue here https://github.com/minish >>> ift/minishift/issues/606 . >>> >> >>> >>>> 5) config set and view are out of order >>>> https://github.com/minishift/minishift/issues/699 >>>> >>> >>> We couldn't find the value in the order of config values. >>> Would definitely like to hear if ordering config values achieve any >>> specific use case here. >>> >> >> As a user, I expect 2 ordering schemes: >> 1) The order is consistent for every time I use "minishift config view", >> right not the order jumps around based on what was last "set this" or "set >> that". Basically the order is currently "random" from what I can tell >> or >> 2) The order based on my various "set this" and "set that". So if I use >> "set memory 6000" then "set cpus 2" and then "set vm-driver virtualbox" >> then "config view" should display those same settings in that same order. >> >> Either approach would work for me :-) >> >> >>> >>> >>>> 6) version should be available prior to setup-cdk >>>> https://github.com/minishift/minishift/issues/700 >>>> >>> >>> AFAIR, we did that in order detect whether binary is CDK binary >>> or upstream minishift binary. We might need to find another way >>> if we really want to see version before "setup-cdk". >>> >>> We checks the existance of cdk marker file in CDK binary which contains >>> information like cdk version (also used by devstudio). >>> "setup-cdk" step creates that marker file and hence you >>> get expected version after that. >>> >>> We don't do this check in upstream minishift binary. >>> >>> >> I understand, it is just very weird for the end-user. one of the biggest >> problems with any cli is "how do I know that I have the right one?" >> >> >> >>> >>>> >>>> _______________________________________________ >>>> Devtools mailing list >>>> Devtools at redhat.com >>>> https://www.redhat.com/mailman/listinfo/devtools >>>> >>>> >>> Regards, >>> Budh Ram Gurung >>> Software Engineer - Devtools >>> >> >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmohanty at redhat.com Thu Apr 13 13:53:58 2017 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Thu, 13 Apr 2017 19:23:58 +0530 Subject: [Devtools] Created Issues In-Reply-To: References: Message-ID: On Fri, Apr 7, 2017 at 6:17 PM, Burr Sutter wrote: > > > On Fri, Apr 7, 2017 at 2:49 AM, Lalatendu Mohanty > wrote: > >> >> >> On Fri, Apr 7, 2017 at 4:09 AM, Burr Sutter wrote: >> >>> >>> >>> On Thu, Apr 6, 2017 at 1:31 PM, Budh Gurung wrote: >>> >>>> Hi Burr, >>>> >>>> Comments inline. >>>> >>>> On Thu, Apr 6, 2017 at 9:16 PM, Burr Sutter wrote: >>>> >>>>> 1) Fails on Windows 10 (clean machine, newly installed VirtualBox) >>>>> https://github.com/minishift/minishift/issues/695 >>>>> >>>> >>>> I doubt you actually hit by this issue https://issues.jboss.org >>>> /browse/CDK-70. >>>> >>>> This happens when you don't have ssh.exe binary set in your *PATH*. >>>> We have observed that installing OpenSSH for Windows >>>> resolve this issue. >>>> >>>> Investigation is undergoing to know the actual reason. >>>> >>> >>> That sounds like it. I am out of CDK on Windows testing time for >>> several days but I might be able to try a beta 4 when it becomes available. >>> >>> >>>> >>>> >>>>> >>>>> 2) Need an admin/admin user >>>>> https://github.com/minishift/minishift/issues/696 >>>>> >>>> >>>> This I am not sure as we given 'developer' user a 'sudoer' role by >>>> default and all >>>> admin operations can be run with "--as system:admin". >>>> >>> >>> Right, but as a human, I need to be able to login to the console as >>> admin :-) >>> >>> Damn humans/users. >>> >> >> Hi Burr, >> >> Please check the issues you had raised. It has several comments which >> will be useful to you and on some issues we need information from you. >> >> Regarding the system:admin user I think you are comparing the UX with >> CDK 2.x. We have done things little differently in CDK 3 but have done it >> in a right way as developer user should not have by default the >> cluster-admin role. It is like making any user in Linux as root. However we >> have discussed in the issue that we might want to have a separate user who >> will have cluster-admin role by default. >> > > Right in the old CDK it was "admin, admin" > > Thanks to Praveen [1] , now we have an addon which which creates an user "admin" with custer-admin role. For upstream you have to explicitly enable it and for downstream we need to make it enabled by-default. [1] https://github.com/minishift/minishift/pull/741 Thanks, Lala -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Thu Apr 13 23:49:26 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Apr 2017 19:49:26 -0400 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: <20170406105400.GA74041@ovpn-117-225.ams2.redhat.com> References: <2536920768340385855@unknownmsgid> <20170406105400.GA74041@ovpn-117-225.ams2.redhat.com> Message-ID: i think Clayton was right...i suspect the du processes go bonkers after the laptop has spun down and when I wake it back up https://screencast.com/t/FsxdFkwX openshift systemd du findmnt using the most cpu according to top I also have very little free/available memory https://screencast.com/t/HAEQC4YCa1u9 In Linux land, what is the difference between free and available? And what is a good amount to have free? On Thu, Apr 6, 2017 at 6:54 AM, Hardy Ferentschik wrote: > Hi, > > On Wed, 05-Apr-2017 16:17, Burr Sutter wrote: > > So, I left it running just to see what it would do...eventually the "du" > > processes seem to quiet down and virtualbox went quiet....and it seems > that > > openshift crashed. The VM is still up but I can't find an openshift > > process. > > Ok, thanks for all the updates. I am planning to spend some time on > testing MSA on various Minishfit versions over the next week or so. > I'll hopefully have something to report back. > > At least it seems we are making progress :-) > > --Hardy > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Fri Apr 14 00:01:00 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Apr 2017 20:01:00 -0400 Subject: [Devtools] why is Mac OSX called Darwin? Message-ID: https://screencast.com/t/0Ty2uvDn and is the Windows version AMD only, no Intel? My 2 dumb questions of the day :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmancini at redhat.com Fri Apr 14 00:08:40 2017 From: tmancini at redhat.com (Todd Mancini) Date: Thu, 13 Apr 2017 17:08:40 -0700 Subject: [Devtools] why is Mac OSX called Darwin? Message-ID: <2211170267995818316@unknownmsgid> 64 bit "80x86" as we know it today was originally created by AMD, not Intel. Intel was trying to push Itanium at that time for 64 bit. So it's normal to refer to 64 bit apps on Windows as amd64. Intel had to change course and adopt the AMD model. (Which was basically the same as the 16->32 bit model that Intel did in the 32 bit days. Itanium was their New Coke.) Sent from my phone, so anticipate hilarious autocorrects ------------------------------ From: Burr Sutter Sent: ?4/?13/?2017 8:01 PM To: devtools Subject: [Devtools] why is Mac OSX called Darwin? https://screencast.com/t/0Ty2uvDn and is the Windows version AMD only, no Intel? My 2 dumb questions of the day :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Devtools mailing list Devtools at redhat.com https://www.redhat.com/mailman/listinfo/devtools From langdon at redhat.com Fri Apr 14 00:26:23 2017 From: langdon at redhat.com (Langdon White) Date: Fri, 14 Apr 2017 00:26:23 +0000 Subject: [Devtools] why is Mac OSX called Darwin? In-Reply-To: <2211170267995818316@unknownmsgid> References: <2211170267995818316@unknownmsgid> Message-ID: And Darwin is the open source "core" of OS X https://en.m.wikipedia.org/wiki/Darwin_(operating_system) On Thu, Apr 13, 2017, 20:09 Todd Mancini wrote: > 64 bit "80x86" as we know it today was originally created by AMD, not > Intel. Intel was trying to push Itanium at that time for 64 bit. So it's > normal to refer to 64 bit apps on Windows as amd64. Intel had to change > course and adopt the AMD model. (Which was basically the same as the 16->32 > bit model that Intel did in the 32 bit days. Itanium was their New Coke.) > > Sent from my phone, so anticipate hilarious autocorrects > ------------------------------ > From: Burr Sutter > Sent: ?4/?13/?2017 8:01 PM > To: devtools > Subject: [Devtools] why is Mac OSX called Darwin? > > https://screencast.com/t/0Ty2uvDn > > and is the Windows version AMD only, no Intel? > > My 2 dumb questions of the day :-) > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmaury at redhat.com Fri Apr 14 07:03:26 2017 From: jmaury at redhat.com (Jean-Francois Maury) Date: Fri, 14 Apr 2017 09:03:26 +0200 Subject: [Devtools] CDK 2.4 and Minishift CDK uses lots of CPU In-Reply-To: References: <2536920768340385855@unknownmsgid> <20170406105400.GA74041@ovpn-117-225.ams2.redhat.com> Message-ID: avail is the amount of physical memory that is available for new application (without swapping) On Fri, Apr 14, 2017 at 1:49 AM, Burr Sutter wrote: > i think Clayton was right...i suspect the du processes go bonkers after > the laptop has spun down and when I wake it back up > > https://screencast.com/t/FsxdFkwX > > openshift > systemd > du > findmnt > > using the most cpu according to top > > I also have very little free/available memory > https://screencast.com/t/HAEQC4YCa1u9 > > In Linux land, what is the difference between free and available? And > what is a good amount to have free? > > > On Thu, Apr 6, 2017 at 6:54 AM, Hardy Ferentschik > wrote: > >> Hi, >> >> On Wed, 05-Apr-2017 16:17, Burr Sutter wrote: >> > So, I left it running just to see what it would do...eventually the "du" >> > processes seem to quiet down and virtualbox went quiet....and it seems >> that >> > openshift crashed. The VM is still up but I can't find an openshift >> > process. >> >> Ok, thanks for all the updates. I am planning to spend some time on >> testing MSA on various Minishfit versions over the next week or so. >> I'll hopefully have something to report back. >> >> At least it seems we are making progress :-) >> >> --Hardy >> >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -- JEFF MAURY Red Hat jmaury at redhat.com @redhatjobs redhatjobs @redhatjobs -------------- next part -------------- An HTML attachment was scrubbed... URL: From rct+redhat at r-t.org Fri Apr 14 15:24:43 2017 From: rct+redhat at r-t.org (Robert Terzi) Date: Fri, 14 Apr 2017 11:24:43 -0400 Subject: [Devtools] why is Mac OSX called Darwin? In-Reply-To: References: <2211170267995818316@unknownmsgid> Message-ID: Not sure if this helps, but on most *nix systems code/scripts, such as installers, could (mostly) figure out what type of system it was being run on using 'uname -a'. On OS X, uname reports "Darwin" for OS type. Note: as far as processor architecture, it currently shows x86_64 on "modern" systems, as opposed to i686 for 32 bit x86 systems. IIRC, In the past it used to report amd64 as opposed to i386 or i686. On windows, the PROCESSOR_ARCHITECTURE env. variable contains 'amd64' From bsutter at redhat.com Sun Apr 16 01:38:13 2017 From: bsutter at redhat.com (Burr Sutter) Date: Sat, 15 Apr 2017 21:38:13 -0400 Subject: [Devtools] why is Mac OSX called Darwin? In-Reply-To: References: <2211170267995818316@unknownmsgid> Message-ID: Interesting...feels a little "inside baseball" but I guess our types of users are the uber geeks who are into this kind of stuff. Mac OSX Windows 64-bit would be more obvious to the average folks :-) On Fri, Apr 14, 2017 at 11:24 AM, Robert Terzi wrote: > Not sure if this helps, but on most *nix systems code/scripts, such as > installers, could (mostly) figure out what type of system it was being run > on using 'uname -a'. On OS X, uname reports "Darwin" for OS type. > > Note: as far as processor architecture, it currently shows x86_64 on > "modern" systems, as opposed to i686 for 32 bit x86 systems. IIRC, In the > past it used to report amd64 as opposed to i386 or i686. > > On windows, the PROCESSOR_ARCHITECTURE env. variable contains 'amd64' > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Mon Apr 17 14:47:32 2017 From: bsutter at redhat.com (Burr Sutter) Date: Mon, 17 Apr 2017 10:47:32 -0400 Subject: [Devtools] Fwd: [openshift-sme] JBDS Server Adapter and Openshift deployment In-Reply-To: <58F252CD.8010104@redhat.com> References: <58F252CD.8010104@redhat.com> Message-ID: any of you on this email list? ---------- Forwarded message ---------- From: jgammon Date: Sat, Apr 15, 2017 at 1:05 PM Subject: [openshift-sme] JBDS Server Adapter and Openshift deployment To: openshift-sme Hi Folks: Trying to work with JBDS and OpenShift and specifically the ServerAdapter so I can demo roundtrip developer interaction with Openshift and an ide, specifically JBDS; Following these directions for publishing an app to Openshift 3.4 via the server adapter ( http://tools.jboss.org/documentation/howto/os3_ startusing.html -- How to deploy an application using Server Adapter) but I keep getting this error even though I HAVE configured the "demouser" Openshift connection: *Could not sync /home/keyvan/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/demoproject at jboss-eap70-openshift/deploy to all pods running the service jboss-eap70-openshift* *OpenShiftBinaryCapability process exited: error: auth info "demouser1" does not exist* Looking for some ideas here. Thanks Have a question? First, check the FAQ: https://mojo.redhat.com/docs/DOC-943081 Next, check the archives: http://post-office.corp. redhat.com/archives/openshift-sme/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmaury at redhat.com Tue Apr 18 06:59:57 2017 From: jmaury at redhat.com (Jean-Francois Maury) Date: Tue, 18 Apr 2017 08:59:57 +0200 Subject: [Devtools] Fwd: [openshift-sme] JBDS Server Adapter and Openshift deployment In-Reply-To: References: <58F252CD.8010104@redhat.com> Message-ID: Hello, seems this error has been caused by a change in the oc client brought by OCP 3.4. Which version of JBDS are you using because it should have been fixed by JBDS 10.3 Jeff On Mon, Apr 17, 2017 at 4:47 PM, Burr Sutter wrote: > any of you on this email list? > > ---------- Forwarded message ---------- > From: jgammon > Date: Sat, Apr 15, 2017 at 1:05 PM > Subject: [openshift-sme] JBDS Server Adapter and Openshift deployment > To: openshift-sme > > > Hi Folks: > > Trying to work with JBDS and OpenShift and specifically the ServerAdapter > so I can demo roundtrip developer interaction with Openshift and an ide, > specifically JBDS; > > Following these directions for publishing an app to Openshift 3.4 via the > server adapter ( http://tools.jboss.org/documen > tation/howto/os3_startusing.html -- How to deploy an application using > Server Adapter) but I keep getting this error even though I HAVE configured > the "demouser" Openshift connection: > > *Could not sync > /home/keyvan/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/demoproject at jboss-eap70-openshift/deploy > to all pods running the service jboss-eap70-openshift* > *OpenShiftBinaryCapability process exited: error: auth info "demouser1" > does not exist* > > Looking for some ideas here. > > Thanks > > Have a question? > First, check the FAQ: https://mojo.redhat.com/docs/DOC-943081 > Next, check the archives: http://post-office.corp.redhat > .com/archives/openshift-sme/ > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -- JEFF MAURY Red Hat jmaury at redhat.com @redhatjobs redhatjobs @redhatjobs -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmalina at redhat.com Wed Apr 19 12:38:02 2017 From: mmalina at redhat.com (Martin Malina) Date: Wed, 19 Apr 2017 14:38:02 +0200 Subject: [Devtools] why is Mac OSX called Darwin? In-Reply-To: References: <2211170267995818316@unknownmsgid> Message-ID: <550C295F-2D65-4AE1-92E8-20F4459D9EEE@redhat.com> This question previously came up when we were releasing CDK 3 Beta and Mike Guerette was confused by Darwin on the cdk download page just like you are now :) https://projects.engineering.redhat.com/browse/RCM-12713?focusedCommentId=470919&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-470919 We requested that we need more user friendly names for the cdk download, so that is fixed. https://developers.redhat.com/products/cdk/download/ But I wouldn't mind switching darwin to macos everywhere. > On 16 Apr 2017, at 03:38, Burr Sutter wrote: > > Interesting...feels a little "inside baseball" but I guess our types of users are the uber geeks who are into this kind of stuff. > > Mac OSX That's so pre-2016! :) Now it's macOS. -Martin > Windows 64-bit > > would be more obvious to the average folks :-) > > > On Fri, Apr 14, 2017 at 11:24 AM, Robert Terzi > wrote: > Not sure if this helps, but on most *nix systems code/scripts, such as installers, could (mostly) figure out what type of system it was being run on using 'uname -a'. On OS X, uname reports "Darwin" for OS type. > > Note: as far as processor architecture, it currently shows x86_64 on "modern" systems, as opposed to i686 for 32 bit x86 systems. IIRC, In the past it used to report amd64 as opposed to i386 or i686. > > On windows, the PROCESSOR_ARCHITECTURE env. variable contains 'amd64' > > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdrage at redhat.com Wed Apr 19 13:31:55 2017 From: cdrage at redhat.com (Charlie Drage) Date: Wed, 19 Apr 2017 09:31:55 -0400 Subject: [Devtools] Docker is now github.com/moby/moby and the CE and EE split grows Message-ID: <20170419133154.GA14@aed8427d7507> https://github.com/docker/docker https://github.com/moby/moby/pull/32691 Huge news from Docker. docker/docker has been moved to moby/moby and it will essentially be a large build / development tool. Essentially, the TLDR is: Moby: Open Source Development. Docker will continue to "split" each component to it's own separate project (libnetwork, InfraKit, etc.) Essentially, Moby takes all these projects and builds "Docker CE" Docker CE: Free product based on Moby Docker EE: Commercial product based on Docker EE (non-Moby) -- Charlie Drage Software Engineer Red Hat (Canada) From cdrage at redhat.com Wed Apr 19 16:47:03 2017 From: cdrage at redhat.com (Charlie Drage) Date: Wed, 19 Apr 2017 12:47:03 -0400 Subject: [Devtools] 0.1.0 release of OpenCompose Message-ID: <20170419164702.GA16@d39a2a448268> We've gone ahead with a new release of OpenCompose, officially our first one (since alpha) 0.1.0! There's a lot of changes since the alpha, and I've gone ahead and outlined this on https://github.com/redhat-developer/opencompose/releases Otherwise, here is a list of changes brought by this release: The first official (non-alpha) release of OpenCompose! If you haven't yet heard of OpenCompose, it's a higher level abstraction for Kubernetes resources. Here's a simple example of running an external/public-facing container with NGINX. ```yaml version: 0.1-dev services: - name: helloworld containers: - image: tomaskral/nonroot-nginx ports: - port: 8080:80 type: external ``` This release ecompasses 42 commits and changes between v0.1.0 and v0.1.0-alpha.0. New changes: - A majority of the changes is new documentation, including updated examples - Added support for passing in input from STDIN (https://github.com/redhat-developer/opencompose/pull/72) - Ingress support (https://github.com/redhat-developer/opencompose/pull/69) - Allow URL support (https://github.com/redhat-developer/opencompose/pull/64) - Replica support (https://github.com/redhat-developer/opencompose/pull/66) New ingress support: You're now able to supply both `host` and `path` when providing port information: ```yaml ports: - port: 8080:80 type: internal host: domain.tld path: /admin ``` URL support: You're now able to pass in an external URL to OpenCompose. ```sh opencompose convert -f https://raw.githubusercontent.com/redhat-developer/opencompose/master/examples/hello-nginx.yaml ``` Replica support: Each service can now be defined by how many replicas. ```yaml # name: foo replicas: 4 containers: - ``` Many thanks for those who have contributed to this release! -- Charlie Drage Software Engineer Red Hat (Canada) From bsutter at redhat.com Fri Apr 21 00:51:05 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 20 Apr 2017 20:51:05 -0400 Subject: [Devtools] Fwd: [openshift-sme] CDK 3 In-Reply-To: References: Message-ID: FYI ---------- Forwarded message ---------- From: Tim Gaillard Date: Thu, Apr 20, 2017 at 4:11 PM Subject: [openshift-sme] CDK 3 To: openshift-sme SME?s I have a customer trying to use the CDK 3 beta and he is getting the error below. I have gone through the installation steps with him and everything works correctly except for the start. He is on a Mac and installed the Xhyve driver and updated the permissions and we also validated the RHN user/password is not a problem. One other strange item is no log files get generated so this is the only information we get (possible it is permission issue to log location but I don?t have those logs either and my install and start works fine). Any information would be helpful. Thanks ? Tim *MTVL149c85f13:minishift amazumder1$ ./minishift --username --password start* *Starting local OpenShift cluster using 'xhyve' hypervisor...* *Registering machine using subscription-manager* *E0417 13:30:21.742671 44351 start.go:150] Error starting the VM: Error registering the VM: ssh command error:* *command : sudo subscription-manager register --auto-attach --username --password * *err : exit status 70* *output : Registering to: subscription.rhsm.redhat.com:443/subscription * *Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.* *. Retrying.* *Registering machine using subscription-manager* *E0417 13:30:35.805988 44351 start.go:150] Error starting the VM: Error registering the VM: ssh command error:* *command : sudo subscription-manager register --auto-attach --username --password * *err : exit status 70* *output : Registering to: subscription.rhsm.redhat.com:443/subscription * *Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.* *. Retrying.* *^C* Tim Gaillard Red Hat Solutions Architect Southwest Region 480-717-7767 <(480)%20717-7767> Cell Have a question? First, check the FAQ: https://mojo.redhat.com/docs/DOC-943081 Next, check the archives: http://post-office.corp. redhat.com/archives/openshift-sme/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Fri Apr 28 02:29:36 2017 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 27 Apr 2017 22:29:36 -0400 Subject: [Devtools] minishift promotion Message-ID: Besides bit.ly/msa-instructions (our primary demo/tutorial) we also have bit.ly/kubernetes-lab and Rafael may be aware of some other "tutorials" that people might follow and learn more about key technologies and leverage minishift. Can someone on the engineering/QA side scan bit.ly/kubernetes-lab and see if it makes sense? also, we need to be pushing the Java S2I, this is how we documented it when it launched in Feb 2017 oc create -f https://gist.githubusercontent.com/tqvarnst/3ca512b01b7b7c1a1da0532939350e23/raw/3869a54c7dd960965f0e66907cdc3eba6d160cad/openjdk-s2i-imagestream.json but I am not sure if that is the 'proper' way to get average end-users to load it up. Any ideas about how we should promote the usage of the s2i and getting people to try it on minishift? And is there is another email list for this sort of thing...let me know...my brain is weary of trying to track all these different email lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgurung at redhat.com Fri Apr 28 03:01:36 2017 From: bgurung at redhat.com (Budh Gurung) Date: Fri, 28 Apr 2017 08:31:36 +0530 Subject: [Devtools] minishift promotion In-Reply-To: References: Message-ID: Hi Burr, On 28 Apr 2017 7:59 a.m., "Burr Sutter" wrote: > > Besides bit.ly/msa-instructions (our primary demo/tutorial) we also have > bit.ly/kubernetes-lab This looks awesome. I was looking for such content from long time. > and Rafael may be aware of some other "tutorials" that people might follow and learn more about key technologies and leverage minishift. Please share those as well. This would help in demoing Minishift effectively. > Can someone on the engineering/QA side scan bit.ly/kubernetes-lab and see if it makes sense? I will go through these when I get time. > also, we need to be pushing the Java S2I, this is how we documented it when it launched in Feb 2017 > oc create -f https://gist.githubusercontent.com/tqvarnst/3ca512b01b7b7c1a1da0532939350e23/raw/3869a54c7dd960965f0e66907cdc3eba6d160cad/openjdk-s2i-imagestream.json > > but I am not sure if that is the 'proper' way to get average end-users to load it up. Any ideas about how we should promote the usage of the s2i and getting people to try it on minishift? We will discuss and come up with plan. > And is there is another email list for this sort of thing...let me know...my brain is weary of trying to track all these different email lists. Well I don't think as far as I know. However, if you have any queries related to Minishift, we have devtools-cdk ML where we can talk minishift related. > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: